IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

SQLCODE -904 - why the tablespace is not available


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 1:22 pm
Reply with quote

Hi,

One of my job AK1159 is abended with -904 at 20.01.53 hours. I have checked the database and tablespace for all the tables this job uses and everything is RW mode.

I have checked in DB*MSTR job to check whether DB is up and running and also to check whether any DB2 utility is running on this table during the time of abend.

Here is the info I found from DB*MSTR.

Code:
20.01.53  STC84667 DSN3201I  +DB05 ABNORMAL EOT IN PROGRESS FOR 603
603                         USER=ZS01ZI CONNECTION-ID=BATCH CORRELATION-ID=AK1159
603                         JOBNAME=AK1159 ASID=011D TCB=009CC020


How to find out why the tablespace is not available from the above info. Or is there anyway to find why the tablespace is not available.

Please suggest me.

Regards,
Chinni.
Back to top
View user's profile Send private message
GuyC

Senior Member


Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Fri Jun 04, 2010 1:33 pm
Reply with quote

first of all you'll need the reasoncode :
Code:
DSNT501I  - DSNILMCL RESOURCE UNAVAILABLE
           CORRELATION-ID=jobname
           CONNECTION-ID=******
           LUW-ID=****
           REASON 00C9008E                           
           TYPE 00000D01                             
           NAME ********.********

00C9008E for example is a timeout.
with a corresponding DSNT376I :
Code:
DSNT376I  - PLAN=plan WITH 202                                     
        CORRELATION-ID=jobname
        CONNECTION-ID=**
        LUW-ID=**
        THREAD-INFO=*
        IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=plan WITH
        CORRELATION-ID=otherjobname
        CONNECTION-ID=***
        LUW-ID=**
        THREAD-INFO=*
        ON MEMBER ****                       
Back to top
View user's profile Send private message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 4:23 pm
Reply with quote

GuyC,

Thank you very much for quick turn around.

Below is the info I got it from the spool.

Code:
IEA9951I  SYSMPTION DUMP OUTPUT
 USER COMPLETION CODE=3939 REASON CODE=00000BB8
TIME=20.01.53    SEQ=08292    CPU=0000    ASID=001D
PSW AT TIME OF ERROR     078D1000   800D8CCC   ILC  2    INTC   0D
      ACTIVE LOAD MODULE            ADDRESS=000D3810   OFFSET=000054BC
NAME=CEEBINIT
DATA AT PSW   000D8CC6  -  00181610   0A0D47F0    B5A01816


Also I did not find the ones that you have posted in my MSTR jobs (during the time the job was abended except the one that I had mentioned earlier).

At 14.00.51 below is the information.

Code:
14.00.51 STC84667   DSN3201I  +DB05  ABNORMAL EOT IN PROGRESS FOR 272
272                          USER=YTRE67Y CONNECTION-ID=TSO  CORRELATION-ID=YTRE67Y  JOBNAME=YTRE67Y
272                          ASID=01D5   TCB=0095FE88


Regards,
Chinni.
Back to top
View user's profile Send private message
GuyC

Senior Member


Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Fri Jun 04, 2010 4:54 pm
Reply with quote

DSNT501I is found in the normal log, not in any MSTR job.
reasoncode is in SQLCA block at abend.
Back to top
View user's profile Send private message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 5:10 pm
Reply with quote

GuyC,

Confused now...

This is what I found in SYSTSRPT of the abended job -- (1)

Code:
ACF0CC038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES
READY
  DSNECP00 SYSTEM(DB20)
DSNECP00
    RUN PROGRAM (TK125) PLAN(TK125)    PARM()
DSNECP00 ENDED DUE TO ERROR+
USER ABEND CODE 3939  REASON CODE 00000BB8


This is what I found in DB*MSTR job log --- (2)
Code:
14.00.51 STC84667   DSN3201I  +DB05  ABNORMAL EOT IN PROGRESS FOR 272
272                          USER=YTRE67Y CONNECTION-ID=TSO  CORRELATION-ID=YTRE67Y  JOBNAME=YTRE67Y
272                          ASID=01D5   TCB=0095FE88


This is what I found in LOG of the abended job --- (3)

Code:
IEA9951I  SYSMPTION DUMP OUTPUT
 USER COMPLETION CODE=3939 REASON CODE=00000BB8
TIME=20.01.53    SEQ=08292    CPU=0000    ASID=001D
PSW AT TIME OF ERROR     078D1000   800D8CCC   ILC  2    INTC   0D
      ACTIVE LOAD MODULE            ADDRESS=000D3810   OFFSET=000054BC
NAME=CEEBINIT
DATA AT PSW   000D8CC6  -  00181610   0A0D47F0    B5A01816



REASON CODE 00000BB8 is not the actual reason code?
What is that reason code in SQLCA block at abend?

For -811 I used to see the info of what you had mentioned earlier like

CORRELATION-ID
CONNECTION-ID
LUW-ID
THREAD-INFO

etc... but for this abend I could not see anything except for the one I have mentioned above ---- (2).

Please let me know if I am missing anything here in finding out the issue.

Regards,
Kiran.
Back to top
View user's profile Send private message
GuyC

Senior Member


Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Fri Jun 04, 2010 5:19 pm
Reply with quote

USER ABEND CODE 3939 REASON CODE 00000BB8 :this is not a DB2 abend/reasoncode, probably something the program calls when it encounters an SQL-error.

the SYSTEM LOG : Do you have SDSF ? just type LOG on the command line and search therein.

Is it a cobol program ? Are you DB2 developer ? If you don't know what the SQLCA block is, you probably are not or should not be.
Time to google and read some DB2 application programming guides.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Fri Jun 04, 2010 5:26 pm
Reply with quote

why do people not use a CALL to DSNTIAR after an unsuccessful SQL CALL?

you CALL DSNTIAR and display the results in your SYSOUT:

which will tell you EXACTLY what the resource name is
and a REASON CODE which if you look up in the documentation
will tell you why.
Back to top
View user's profile Send private message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 5:40 pm
Reply with quote

GuyC,

We use IOF. The program is PL/1 DB2. Previously we used to use SDSF but moved to IOF recently.

Pls let me know how to find out the reason code in IOF.
Back to top
View user's profile Send private message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 5:43 pm
Reply with quote

By the way we abending program using an utility and the details shows as.

ABEND=S000 U0922 REASON=00000000
Back to top
View user's profile Send private message
GuyC

Senior Member


Joined: 11 Aug 2009
Posts: 1281
Location: Belgium

PostPosted: Fri Jun 04, 2010 5:48 pm
Reply with quote

www.triangle-systems.com/download/IOF@8DQR.PDF

Quote:
The 'LOG' option enters Syslog or Operlog browse. While browsing a log, enter 'L hhmm' to locate a specific hour (hh) and minute (mm). Enter 'IND' to display the Data Indices Menu of indexed SYSLOG events. Then, select specific indices and indexed events.
'LOG O' jumps to Operlog. 'LOG S' jumps to Syslog. 'LOG O -1' jumps to yesterdays Operlog. 'LOG OLD' shows menu of old logs.

never heard of IOF, but googled this under 60seconds
Back to top
View user's profile Send private message
chinnielr

New User


Joined: 11 Jul 2005
Posts: 87

PostPosted: Fri Jun 04, 2010 7:15 pm
Reply with quote

GuyC,

I able to see LOG in IOF but it shows the same reason code and abend code as I had mentioned earlier. Not so lucky icon_sad.gif

we know that this job is abended with resource unavailable...
how to find out the reason of resource unavailable with the reason code?

Chinni.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Fri Jun 04, 2010 8:02 pm
Reply with quote

1. depending upon your db2 log parms, the info could be there.
2. try to run again
3. PUT the CALL to DSNTIAR in you program,
the display will tell you everything you need.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts SQLCODE=-311 in Cobol SP-DB2. COBOL Programming 2
No new posts force tablespace using LISTDEF input DB2 1
No new posts SQLCODE = -122 while using the scalar... DB2 4
No new posts SQLCODE = -16002 when using XMLEXISTS DB2 1
No new posts Map VSAM Dataset to a Table/Tablespace DB2 5
Search our Forums:

Back to Top