When a program error occurs

1. a message is displayed to the end-user
2. an e-mail message is sent to the appropriate developer, with some indications about the error
3. the message sent also allows to display via HTTP the joblog and the source of the failing program

• File EPOLICEDTA/LIBRARIES
  For each application program library enter (see Figure 1):
  • the library name
  • the developer's name
  • the developer's e-mail address
  • if you want to use the MMAIL SMS support, the person ID as specified in the MMAIL SMS phone book MMAILDATA/CLICKABOOK (see this page).
  Note 1- You can enter multiple records (multiple developers) for a given application program library.
  Note 2- You do not have to specify all the application program libraries. You may enter *ALL (uppercase, please!) as an application program library name. When a program error occurs for a program belonging to a library not documented in this list, it will default to application library name *ALL.
  Note 3- You can enter multiple records (multiple developers) also for application program library *ALL.

1. include the following statements (see figure 2 as an example):
   • in each file specification, add the keyword
     infsr(*pssr)
   • after the file specifications, add the following statements
     /COPY EPOLICE/QRPGLESRC,Q_USEC
     /COPY EPOLICE/QRPGLESRC,Q_PSDS
     See figure 2 as an example.
     
   • at the end of the source
     /COPY EPOLICE/QRPGLESRC,Q_PSSR
   These statements generate a Program Error Subroutine (*PSSR), which receives control in case of program error. See later for the behavior of this subroutine.
2. be compiled with the following parameter:
   • for ILE-RPG modules and ILE-RPG bound programs
     OPTION(*SRCSTMT)
   • for SQL-RPG modules or programs
     COMPILEOPT('OPTION(*SRCSTMT)')

The E-Police program error subroutine *PSSR calls program EPOLICE/Q_FILEERR which does the following:

1. The joblog level is changed to (4 0)
2. A program error information record is added to file EPOLICEDTA/ERRORS. The information includes:
   • system name
   • timestamp of when the error occurred
   • qualified job name
   • qualified name of the program in error
   • qualified name of the source member the program was compiled from
   • number of the program statement in error (see compile options above)
   • name of the file where the last I/O was performed
   • ID and text of the error message
   • full program status data structure
3. A notification of the program error is sent to the user:
   • if the program is running under HTTP, an HTML page is sent to the remote browser (see figure 3)
   • if the program is running in interactive mode, a display file screen is sent to the display file device (see figure 4)
   • if the program is running in batch mode, a break message is sent to the job user profile message queue (see figure 5) and a program message is sent to the *EXT message queue (so that it is displayed in the joblog).
4. An e-mail message is sent to the program developer(s), according to the data found in file EPOLICEDTA/LIBRARIES. See the example in figure 6.
   Acting from the e-mail message, the developer may then display via HTTP
   1. the joblog (see figure 7)
   2. the program source (see figure 8).

• program EPOLICE/SAMPLE1 (see figure 8)
• or program EPOLICE/SAMPLE2 (see figure 9).

• Command EPOLICE/RCVJL (receive joblog) receives the joblog entries of an active job into file QTEMP/JLOG (which is automatically created). It could be useful for other local applications.