***ERROR READING JES SYSOUT FILE - OPERATOR REPLIED 'DELETE'.
In addition to the error message JMR does not archive all of the task output.
Release : 4.6
This is normal if you have the PKXTGERR user exit installed.
This is documented as the PK46UM07 exit for invalid sysout.
PKXTGERR uses register one (R1). CA-JMR calls the PKXTGERR
exit immediately after it finds an error while trying to read a JES
SYSOUT file, but before issuing the JMR030A message. As
distributed, this exit will prevent the JMR030A message from
being issued and automatically cause the invalid SYSOUT data
set to be deleted.
Performs special processing when invalid
SYSOUT data sets are encountered during the collection
In the JMR getting Started Guide see chapter 6 on Using Exit Routines
Usermod name is PK46U07 Invalid Sysout Exit
A circumvention would be to run the sysout in question to a physical dataset.
To prove that the exit is doing what you expect you can create a simple test like this S806 abend and route all the dump output to sysout. The expected results would be that one or all of the sysout files will be considered invalid and the messages expected would be the result. In this example the SYSMDUMP is the invalid sysout. Once you swap the SYSMDUMP from a sysout file to a physical IPCS dataset all works well. You still get the S806 but you will not get the "***ERROR READING JES SYSOUT FILE - OPERATOR REPLIED 'DELETE'."