• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Proper CL Error-Handling

    May 5, 2004 Hey, Ted

    When a CL program produces an unexpected error, we find the problem, fix it, and take option “I” (ignore) or “R” (retry) in response to the error message. However, when a user runs a program and encounters an unexpected error, we run into problems. The user might call us. The user might not call us. The user may pick the wrong option and really mess things up. What can we do?

    –Sandra

    You can prevent the user from seeing an inquiry message when something goes wrong. The first thing you need is a global monitor message (MONMSG) command that branches to an error routine. The other thing you need is an error routine that sends an escape message.

    Here is a CL program template I like to use:

    pgm                                                               
                                                                      
       dcl   &Abending      *lgl                                      
       dcl   &MsgID         *char      7                              
       dcl   &MsgDta        *char    256                              
       dcl   &MsgF          *char     10                              
       dcl   &MsgFLib       *char     10                              
       dcl   &MsgKey        *char      4                              
       dcl   &MsgType       *char     10                              
       dcl   &RtnType       *char      2                              
       dcl   &PgmName       *char     10                              
       dcl   &Sender        *char     80                              
                                                                      
       monmsg cpf0000 exec(goto abend)                                
                                                                      
       /* retrieve the program name */                                
       sndpgmmsg msg(' ') topgmq(*same) msgtype(*info) keyvar(&msgkey)
       rcvmsg    pgmq(*same) msgtype(*info) sender(&sender) rmv(*yes) 
       chgvar    &PgmName   %sst(&Sender 56 10)                       
                                                                      
       /* begin regular routine */
                                                                             
       /* normal end of job */                                               
          sndpgmmsg  msgid(cpf9898) msgf(qcpfmsg) msgtype(*comp) +           
                       msgdta('Program' *bcat &PgmName *bcat +               
                              'completed normally')                          
          return                                                             
                                                                             
       /* Routine to handle unexpected errors */                             
    Abend:                                                                   
          if &Abending then(return)                                          
          chgvar   &Abending '1'        
                                         
          rcvmsg     msgtype(*last) msgdta(&msgdta) msgid(&msgid) +          
                        rtntype(&RtnType) +                                  
                        msgf(&msgf) sndmsgflib(&msgflib)                     
          if ((&RtnType *eq '15') *or (&RtnType *eq '17')) do  /* *escape */ 
             sndpgmmsg  msgid(&msgid)  msgf(&msgf)   msgtype(*diag) +        
                       msgdta(&msgdta)                                       
          enddo                                                              
    Escape:                                                                  
       sndpgmmsg  msgid(cpf9898) msgf(qcpfmsg) msgtype(*escape) +            
                    msgdta('Program' *bcat &PgmName *bcat +                  
                           'ended abnormally')
    endpgm                                    
    

    To use this template, you will have to declare any variables or files you use after the PGM command and before the global MONMSG. Then put the commands that you want to run after the comment that indicates the beginning of the regular routine. The rest of the program remains as is.

    If an unmonitored error occurs in the regular routine, control branches to the ABEND label. The first two calculations make sure that the program doesn’t go into a loop if something goes wrong in the ABEND routine. The next lines, up to but not including the ESCAPE label, read the escape message that was unmonitored and send the message back to the caller, as a diagnostic message. The SNDPGMMSG (Send Program Message) command cancels the program by sending an escape message.

    In many shops, the typical CL program contains nothing but overrides and a CALL. I encourage you to make it a standard in your shop that CL programs must include commands to handle unexpected errors.

    –Ted

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    Racksquared

    It’s time for IBM Power in the Cloud!

    Stop buying hardware and make the move to the cloud. It’s easier and more cost effective than you might think.

    • IBM Power in the Cloud
    • IBM Power Backup Solutions
    • IBM Power High Availability and DR solutions
    • IBM Power Colocation with Management and Monitoring

    Let’s talk about your business needs.

    Call: 855-380-7225

    Email: Sales@racksquared.com

    www.racksquared.com/ibmsolutions

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    JBM Systems Adds Form Design Tool to Document Suite IBM eServer i5 and i5/OS Announcement Roundup

    Leave a Reply Cancel reply

Volume 4, Number 15 -- May 5, 2004
THIS ISSUE
SPONSORED BY:

T.L. Ashford
Guild Companies
GST
WorksRight Sofware
Damon Technologies

Table of Contents

  • Using RPG As Your ASP Language, Part 2
  • Proper CL Error-Handling
  • Closing Files in ILE Service Programs
  • Admin Alert: Hitting the Limits of the QNTC File System
  • OS/400 Alert: Fix Central Is Now Firewall-Enabled

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • IBM Mulls Using DataMigrator as Cloud Warehouse Pipeline
  • PowerTech AV Automatically Detects Ransomware Activity
  • Infor Puts CM3 Project On Hold
  • Four Hundred Monitor, June 29
  • IBM i PTF Guide, Volume 24, Number 26
  • Guild Mortgage Takes The 20-Year Option For Modernization
  • IBM i Licensing, Part 3: Can The Hardware Bundle Be Cheaper Than A Smartphone?
  • Guru: The Finer Points of Exit Points
  • Big Blue Tweaks IBM i Pricing Ahead Of Subscription Model
  • We Still Want IBM i On The Impending Power E1050

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2022 IT Jungle

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.