Looking Up Some Of Those Error And Reason Codes

[Ed_Arnold]

Q: If you have a CEEDUMP, how do you look up the following error codes?

   Thread Id .... 1972B00000000000 Errno ...... 129 Errnojr .... 0594003D 
CEE3846I CEEDUMP Processing completed.                                   


A1:  The 129 comes from the errno.h file:

(From a USS command line):

>grep 129 /usr/include/errno.h
          #define ENOENT          129  /* No such file or directory  */

A2:  The Errnojr you can look up via the BPX Message Text TSO command

(From an ISPF command prompt):

Command ===> tso bpxmtext 0594003D

BPXFVLKP 04/23/09                                      
JRDirNotFound: A directory in the pathname was not found

Action: One of the directories specified was not found.  Verify that the name
specified is spelled correctly.  


Another example - say you're running arsload and you get the following:

arsload: 11/10/11 17:27:34 -- Loading started, --UNKNOWN-- bytes to
process
error- Unable to write 18868906 bytes, file
/fooTEST/foo_INTEG/ars/tmp/Nov1020111727365032101F30000000000.001,
errno 133 errno2 ef07604a, line 946
Loaded 0 rows into the database
arsload: 11/10/11 17:27:36 Loading failed
arsload: Processing failed for file



>grep 133 /usr/include/errno.h                               
         #define ENOSPC          133  /* No space left on device    */
        #define EDQUOT         1133  /* Reserved.                  */

(Yeah, two hits, but the 133 is the one we're worried about)

(Then we check that 8 character hexadecimal code)

Command ===> tso bpxmtext ef07604a

Description: General file write error.                         
                                                               
Action: Check the return code to determine why the write failed.

(In this case the errno.h reason code is more descriptive of the problem)