RE: Fun with the PSDS

Here's some fun things you can do with the PSDS

1.  Make the DDS for it so you can Externally define the D/S   (not change
it to Courier Font))

D  P1DS        E S DS EXTNAME(ETPFP1)


   R      ETRFP1         TEXT('Program Status Information')

     P1PGM          10        TEXT('Program Name *PROGRAM')
     P1STAT     5 S 0    TEXT('Status Code *STATUS')
     P1PRVS     5 S 0    TEXT('Previous Status Code')
     P1STMT     8        TEXT('Source Statement Number')
     P1RTNE     8        TEXT('Routine Where Error Occurred +
                         Same as *ROUTINE')
     P1PARM     3 S 0    TEXT('Number of Parms *PARMS')
     P1EMSG     7        TEXT('Exception Error Message ID  ')
     P1ODT          4         TEXT('MI/ODT Number')
     P1MSGW    30        TEXT('Message Work Area')
     P1OLIB    10        TEXT('Program Object Library')
     P1REXD    80        TEXT('Retrieved Exception Data')
     P1IDEN     4        TEXT('ID of the Exception That  +
                         Caused RPG9001')
     P1XXXX    26        TEXT('Unused -  By IBM')
     P1FILE     8        TEXT('File Name Last Used')
     P1FSTS    35        TEXT('Status Info. on the Last +
                         File used')
     P1JOB          10        TEXT('Job Name - CRT of Interactive +
                         Job')
     P1USER    10        TEXT('Current User ID')
     P1JOBN     6 S 0    TEXT('Job Number')
     P1DTEN     6 S 0    TEXT('Date Job Entered System')
     P1DTEX     6 S 0    TEXT('Date of Program Execution')
     P1TMEX     6 S 0    TEXT('Time of Program Execution')
     P1DTPC     6 S 0    TEXT('Date Program Was Compiled')
     P1TMPC     6 S 0    TEXT('Time Program Was Compiled')
     P1CLVL     4        TEXT('Level of Compiler')
     P1SFIL    10        TEXT('SRC File Name')
     P1SLIB    10        TEXT('SRC Library Name')
     P1SMBR    10        TEXT(('SRC Member Name')
     P1ZZZZ    96        TEXT('Unused -  By IBM')



---------------------

2.  Try some error logging in your apps
     Note: after calling the logging program you should handle the error
     as per your shop standards.

------------------------
C    *PSSR     BEGSR
                                                        |
C         CALL 'ETRP9000'                                    | Log Error
via the
C         PARM           P1DS                           | the Utility
Program
                                                        |
C         BEGSR


-----------------------

3. Error logging pgm  ETRP1000
-----------------

F ETPFP1   O   E         DISK

D P1DS         E  DS          EXTNAME(ETPFP1)


C    *ENTRY    PLIST                          | Put Parm into P1DS
C              PARM      P1DS            | To Break Up Fields
                                         |-----------------------------
C              WRITE     ETRFP1               | Log Error Record
                                         |-----------------------------
C              EVAL *INLR       =  *ON        | Turn on Last Record
C              RETURN


------------------------------------------

Now after collecting records in the ETPFP1 file for a while
you will know,

Which message ID's your programs blow up for most
Which programs blow up most
Which users have the the programs blow up on them most

By date, program, user, MSGID, etc.


John Carr

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---