Re: Catching errors on user screens

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Oliver,

You wrote:
>Anyway, any general example for such an *PSSR? We sure could use it for 
>our other apps.

Here is the core of such a function. You can add whatever additional functions 
you need (e.g., issue a DUMP, DSPJOB * *PRINT, DSPJOBLOG * *PRINT, page 
someone, 
send a message, display a friendly error screen, etc.) Use the F-spec INFSR 
keyword to set the *PSSR as the file error handler.

---> CSR         *PSSR     BEGSR                         
      *          ------                                  
      * Catch possibility of looping                     
      *   -- if we have been here before then exit       
B1   C           *INLR     IFEQ $ON                      
<=== C                     RETRN                         
E1   C                     ENDIF                         
      * Prepare to exit ...                              
     C                     SETON                     LR  
      * Do stuff to collect diagnostic information
      * Do stuff to notify support
      * Do stuff to inform user
      * Go home                                           
<=== C                     RETRN                          
      *                                                   
<--- CSR                   ENDSR                          

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists       
                                                                  
   http://www.flybynight.com.au/                                  
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   
   Fax:   +61 3 9419 0175   mailto: shc@xxxxxxxxxxxxxxxxx   \ /   
                                                             X    
                 ASCII Ribbon campaign against HTML E-Mail  / \   
--------------------------------------------------------------------