SCS spool file fails to load with no message 88

[Joe Wolken]

We have a spool file report created daily at about 3:00am and sent to the OnDemand iSeries monitored output queue.  The report processes successfully six days a week, but the Sunday morning report always gets sent to the Error output queue in HELD status and No message 88 (failed load) get generated in the System Log.  If later in the week the file gets released and moved back to the monitored output queue then it loads without issue.

Is there any scenario where a spool file load can fail from the monitored output queue without generating a message 88?  Given that this only happens on the weekend, could there be any system events that we should look at?

We have a ticket open with IBM support and the response so far has just been to look for message 88 records, which do not exist.

Thanks,

[Darrell Bryant]

What messages are in the monitor joblog?  You might try starting the monitor with LOG(*YES) which will write more information into the joblog.

[Joe Wolken]

I think we are finding that on Sunday only the QUSROND Server job is not yet started before the MONOUTQ job, so the MONOUTQ job is trying to process the spool file from the outq before the server job is ready.  Would this cause the spool file to be sent to the Error outq in Error status?

[Darrell Bryant]

In a quick test, the spooled files were sent in a HLD status.  The monitor joblog contained OND2798 ARS1106E Connection cannot be established for the >QUSROND< server.
I suggest that the monitor be started with the parameter STRSVR(*YES).  That should fix the issue going forward.  If the server is already active, then the only overhead is a couple milliseconds verifying that is it active.