Thanks for the replies! Just for the record, I _am_ trapping errors at the command level. At least those I _know_ about. And that's the key. The global MONMSG points to an error routine which runs a DSPJOBLOG *print and sends a message to my user message queue. I get the message in the morning, check the job log, and modify my program as appropriate. This particular application is NOT mission critical, so if it bombs in ANY way, shape, or manner, it absolutely MUST NOT tie up the job queue. Mission critical apps are a different animal altogether. Intelligent decisions must be made when designing the app when encountering an error not expected. - Dan Bale ________________________ Original Message __________________________ Dan, CPF0000 will catch them all. MCH, SQL, RPG, etc messages if not caught (monmsg'd) will cause a CPF9999 message..and that will get caught by the CPF0000. BUT PLEASE BE CAREFULL! What you are talking about doing is VERY dangerous! <<< BIG SNIP >>> +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.