Comments on: Exception handling in CL without Command level MONMSG http://itknowledgeexchange.techtarget.com/itanswers/exception-handling-in-cl-without-command-level-monmsg/ Fri, 24 May 2013 17:13:17 +0000 hourly 1 By: hardywan http://itknowledgeexchange.techtarget.com/itanswers/exception-handling-in-cl-without-command-level-monmsg/#comment-49626 hardywan Fri, 08 Apr 2005 12:06:08 +0000 #comment-49626 rchevalier had already provided you a perfect solution. I just want to highlight that most CL commands allow R=Retry choice after clearing the encountered error. It may not be a good idea (especially from production support point of view) to have a “MONMSG ALL” CL job.

]]> By: krisdv http://itknowledgeexchange.techtarget.com/itanswers/exception-handling-in-cl-without-command-level-monmsg/#comment-49627 krisdv Mon, 28 Mar 2005 08:55:24 +0000 #comment-49627 If I recall well, you can restrict the monmsg also to a range f.e. MONMSG CPF4000 will catch all errors in the 4001-4999 range. Combined with the CL you should be able to catch messages and treat them accordingly

]]> By: wlt000 http://itknowledgeexchange.techtarget.com/itanswers/exception-handling-in-cl-without-command-level-monmsg/#comment-49628 wlt000 Wed, 23 Mar 2005 11:30:10 +0000 #comment-49628 PGM
DCL VAR(&PROCESS) TYPE(*CHAR) LEN(20) +
VALUE(‘Start up’)
DCL VAR(&ERRORMSG) TYPE(*CHAR) LEN(80)

MONMSG MSGID(CPF0000) EXEC(GOTO ERROR)

CHGVAR VAR(&PROCESS) VALUE(‘Initialize Tape’)
INZTAP DEV(TAP01)

CHGVAR VAR(&PROCESS) VALUE(‘Save Library ABC’)
SAVLIB LIB(ABC) DEV(TAP01)

GOTO CMDLBL(ENDPGM)

ERROR:
RCVMSG MSGTYPE(*EXCP) RMV(*NO) MSG(&ERRORMSG)
SNDPGMMSG MSG(‘An error occured during:’ |> + &PROCESS)
SNDPGMMSG MSG(&ERRORMSG)

ENDPGM: ENDPGM

]]>