If CA-OPS/MVS issues error messages from any AOF/REXX then the offending AOF/REXX and if possible failing line should be given in the error message.
It already does this for some error messages
An example would be:
OPS1040O ERROR 40 RUNNING USERMSG.IOS078I, LINE 62: INCORRECT CALL TO ROUTINE
Which gived both the AOF rule and the offending line.
But not for all
OPS1941E Syntax error in parameter: OUTPUT/NOOUTPUT
OPS1959E --- Invalid operand S035I. Valid operands are:
There are no details of where these error was created, no AOF/REXX line number etc.
If the AOF/REXX and Line number can be added to these error messages, we could diagnose and fix much easier.