Program Status Data Structure

[soup_dog]

Re: Program Status Data Structure

Ah! I see it. The first set of fields, the ZZODT and ZZWKMS are fine, it's the ZZDUM1 field and thereafter that is a problem. Here is a link to the IBM manual.

http://publib.boulder.ibm.com/iserie...htm#HDRPSDSDT9

[soup_dog]

Re: Program Status Data Structure

Sorry but I'm fairly sure that the PSDS def you show is wrong from pos. 81.
MI/ODT (4A) and Work Area (30A) for Messages shouldn't indeed be there.
All the subsequent fields are shifted of 34 char, that's why you get wrong values in fields.

Here is a correct def of the PSDS that I use nearly every day

     D                SDS

     D PROC_NAME         *PROC
      *                                                 Procedure name
     D PGM_STATUS        *STATUS
      *                                                 Status code
     D PRV_STATUS             16     20S 0
      *                                                 Previous status
     D LINE_NUM               21     28
      *                                                 Src list line nu
     D ROUTINE           *ROUTINE
      *                                                 Routine name
     D PARMS             *PARMS
      *                                                 Num passed parms
     D EXCP_TYPE              40     42
      *                                                 Exception type
     D EXCP_NUM               43     46
      *                                                 Exception number
     D PGM_LIB                81     90
      *                                                 Program library
     D EXCP_DATA              91    170
      *                                                 Exception data
     D EXCP_ID               171    174
      *                                                 Exception Id
     D DATE                  191    198
      *                                                 Date (DATE fmt)
     D YEAR                  199    200S 0
      *                                                 Year (YEAR fmt)
     D LAST_FILE             201    208
      *                                                 Last file used
     D FILE_INFO             209    243
      *                                                 File error info
     D JOB_NAME              244    253
      *                                                 Job name
     D USER                  254    263
      *                                                 User name
     D JOB_NUM               264    269S 0
      *                                                 Job number
     D JOB_DATE              270    275S 0
      *                                                 Date (UDATE fmt)
     D RUN_DATE              276    281S 0
      *                                                 Run date (UDATE)
     D RUN_TIME              282    287S 0
      *                                                 Run time (UDATE)
     D CRT_DATE              288    293
      *                                                 Create date
     D CRT_TIME              294    299
      *                                                 Create time
     D CPL_LEVEL             300    303
      *                                                 Compiler level
     D SRC_FILE              304    313
      *                                                 Source file
     D SRC_LIB               314    323
      *                                                 Source file lib
     D SRC_MBR               324    333
      *                                                 Source file mbr
     D PROC_PGM              334    343
      *                                                 Pgm Proc is in
     D PROC_MOD              344    353
      *                                                 Mod Proc is in
     D CURR_USER             358    367
      *                                                 Mod Proc is in 

Actually the 34 positions are ok. (Notice the gap between excp_num and pgm_lib in your version? But the 26 character dummy field is definitely a problem.

[Mercury]

Re: Program Status Data Structure

yes I didn't notice the gap of 34 char as I need stronger glasses sorry for this, but the dummy fld starting in pos 191 is indeed definitely a problem.

[FaStOnE]

Re: Program Status Data Structure

I would say call the vendor and have him fix his (insert your favorite descriptive word here)!