×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Methinks that it would be easier in batch than interactive. In batch a
message would go to QSYSOPR and to the DSPLOG. Any decent messaging
software should be able to analyze those and alert someone. But if I run
this simple program interactively nothing goes to QSYSOPR or DSPLOG:
PGM
DLTF ROB/D78HJ87
SNDMSG MSG(DONE) TOUSR(ROB)
END:
Even though my joblog has:
call rob/a
Object D78HJ87 in ROB type *FILE not found.
CPF2105 received by A at 1700. (C D I R)
? C
I don't think there's a "pie in the sky" monitor you can start up to log
all these without customizing software. I've heard of assigning an
initial program to users but not an ending program. But there's an idea.
Use a command exit point program on SIGNOFF (and OFF if you have that) to
analyze the joblog and if you find any "Escape" messages that were not
immediately followed by CPA0701 - "CPF2105 received by A at 1700. (C D I
R)" then you could alert the troops. You can even see the "C". Quite
easily done. Might even encourage you to start replacing this excrement:
DLTF ROB/D78H787
MONMSG CPF0000
with this:
DLTF ROB/D78H787
MONMSG CPF2105 EXEC(DO) /* Object does not exist */
/* Remove message from cluttering joblog */
RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES) KEYVAR(&KEYVAR) +
MSGDTA(&DATA) MSGID(&MSGID)
EndDo
Rob Berendt
midrange.com
