View previous topic :: View next topic
|
Author |
Message |
pshongal
New User
Joined: 14 Jun 2012 Posts: 96 Location: India
|
|
|
|
I am getting value as -502 in RESP2 field and 16 in RESP while reading the file.
Code: |
EXEC CICS
READ DATASET (SWA-XXX-DSID)
INTO (XXX-RECORD)
LENGTH (SWA-XXX-RECORD-LENGTH)
RIDFLD (SWA-XXX-KEY)
GTEQ
RESP (L77-RESP)
RESP2 (L77-RESP2)
END-EXEC.
|
16 is related to INVREQ, but what's -502? |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
Where have you looked for the answer? |
|
Back to top |
|
|
pshongal
New User
Joined: 14 Jun 2012 Posts: 96 Location: India
|
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The CICS Language Reference manual lists valid RESP2 values for an EXEC CICS READ that returns INVREQ RESP as ranging from 20 to 59. Your -502 is way outside those ranges, so the possibilities are:
- you are doing your EXEC CICS READ on a non-system z machine (using Microfocus for example), in which case you need to consult their documentation
- you are incorrectly formatting RESP2 and getting the invalid value that way
- you are mis-interpreting the actual value to be -502
You will need to do additional investigation to figure out what the actual value is and what it tells you about your EXEC CICS READ command. |
|
Back to top |
|
|
pshongal
New User
Joined: 14 Jun 2012 Posts: 96 Location: India
|
|
|
|
Thanks for your insights in to this.
We are executing this transaction in system Z machine itself and I am seeing the value by debugging using Xpeditor.
Looks like I need to check the internal documentation to see if they are formatting the value in some way. |
|
Back to top |
|
|
pshongal
New User
Joined: 14 Jun 2012 Posts: 96 Location: India
|
|
|
|
Finally it is resolved
Internally DB2 code was moved to RESP2. So -502 was DB2 error.
Issue was with END-BROWSE, after start browse, end-browse was not executed due to some wrong condition. Which was corrected and issue got resolved. |
|
Back to top |
|
|
|