MVSFORUMS.com

[vini]

Hi ,

A Job encountered a -904 Sql abend . I am aware its for resource unavailable and normally goes away when Job is re-submitted after some time if a dead lock is its cause. However there was this Job which hit -904 for long time.
Anyone knows where its exact cause be determined from the Sysout or Db2 Master Log ?
If niether , is there any other way to determine the cause or is it best to leave it for the DBA to figure out ?

Job Sysout:
PARAGRAPH : 77200-INSERT-OVERLAPING
SQL ID : 77200
SQL/FILESTAT : -904
KEY : 000000000000750
ERROR MSG : ERR WHILE INSERTIN INTO TRX TABLE
DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE
RESOURCE 00000302, AND RESOURCE NAME WAJIR7DS.WAJIGWTS.X'00770E'
DSNT418I SQLSTATE = 57011 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRUID SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -110 13172746 0 13230791 -639430655 0 SQL DIAGNOSTIC
DSNT416I SQLERRD = X'FFFFFF92' X'00C9000A' X'00000000' X'00C9E2C7' X'D9E3
INFORMATION


Heres how portion of the db2 master log looked ... where the JOB was WADB9009:

DSN3201I -DB3A ABNORMAL EOT IN PROGRESS FOR
USER=WGWS90 CONNECTION-ID=BATCH CORRELATION-ID=WADB9009
JOBNAME=WADB9009 ASID=0113 TCB=007C5AD0
DSN3201I -DB3A ABNORMAL EOT IN PROGRESS FOR
USER=WDFC CONNECTION-ID=BATCH CORRELATION-ID=WRXA9050
JOBNAME=WRXA9050 ASID=00FC TCB=007C2A20
DSN3201I -DB3A ABNORMAL EOT IN PROGRESS FOR
USER=WDFC CONNECTION-ID=BATCH CORRELATION-ID=WRXA9050
JOBNAME=WRXA9050 ASID=00A6 TCB=007C2A20
DSN3201I -DB3A ABNORMAL EOT IN PROGRESS FOR
USER=WGWS90 CONNECTION-ID=BATCH CORRELATION-ID=WADB9001
JOBNAME=WADB9001 ASID=0115 TCB=007C5B58
DSNT375I -DB3A PLAN=RUPUPLAN WITH
CORRELATION-ID=WKKN
CONNECTION-ID=DB2CALL
LUW-ID=USODN101.DB3ADIST.BAB0F4D648BC=20297
THREAD-INFO=WKKN:*:*:*
IS DEADLOCKED WITH PLAN=DSNBIND WITH

Thnks.
Vini.

Note : Could not find any DS by name WAJIR7DS.WAJIGWTS.* in the 3.4 option

[kolusu]

Vini,

The -904 error you are getting is due to the unavailability of the VSAM Cluster of the DB2 table. Ask your DBA about the naming conventions of these db2 clusters. Most shops have the DB2 region name as prefix. your job sysout(customized) is enough for you to figure out the error. If couldn't decipher the error then you might have to look into Db2 Master Log.

Also from your DB2 master log I notice a deadlock situation also. Check this topic for better understanding of resolving deadlock issues.

http://www.mvsforums.com/helpboards/viewtopic.php?t=1228

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu