Can we have an error subroutine in CL?

[nishar]

Hi everyone, I am facing an issue with error capturing in CL

I understood that it is not possible to execute a subroutine inside a Monmsg like this

MONMSG MSGID(CPF0000) EXEC(CALLSUBR SUBR(ERRORSR))

But I need to capture all the errors that are thrown by the CL program into a file. I wrote an error subroutine inside CL like this


SUBR SUBR(ERRORSR)
RCVMSG PGMQ(*SAME) MSGQ(*PGMQ) MSGTYPE(*DIAG) +
WAIT(3) RMV(*NO) MSG(&MSG) +
MSGDTA(&MSGDATA) MSGDTALEN(&MSGLEN) +
MSGID(&MSGID)
CHGVAR VAR(&SQLSTMT) VALUE('INSERT INTO +
QTEMP.ERRFILE VALUES(' || ''''|| +
&MSGID||' '|| &MSG || ''''||')' )

RUNSQL SQL(&SQLSTMT) COMMIT(*NONE) NAMING(*SQL)
CALL PGM(RPTERROR)
ENDSUBR

If a command throw an error, I want to execute this error subroutine and continue the execution . Please let me know how to achieve this since writing subroutine inside monmsg is not an option.

[Peder Udesen]

I haven't tryed it but is it possible to code it like this:

monmsg cpf0000 exec(do)
MONMSG MSGID(CPF0000) EXEC(DO)
     CALLSUBR SUBR(ERRORSR)
ENDDO

[Barbara Morris]

nishar, assuming you want to continue processing after you get an error, you can add the MONMSG after every command.

SOMECMD ...
MONMSG MSGID(CPF0000) EXEC(CALLSUBR SUBR(ERRORSR))

OTHERCMD ...
MONMSG MSGID(CPF0000) EXEC(CALLSUBR SUBR(ERRORSR))​

The rule about EXSR for MONMSG only applies to a MONMSG at the beginning of the program.

BUT ... to me it seems like a very bad idea to continue processing after an error.