I am running a CL program that calls a QSHELL command from batch. I am getting QSH0002 error code 3489 reason code 4.
I have searched the web and found the following explanation (which makes some sense)
QSHELL message 3489 is ENOSYSRSC. Approximately 95 percent of the time this is caused by trying to run QSH from a subsystem where the subsystem has a only a maximum active job of 1 (one). If you can run the command interactively but not from your CL batch program, it is likely that it is due to the maximum active jobs of the subsystem.
To see the maximum active jobs for a subsystem, on the OS/400 command line type the following (for example, for QBATCH):
Press the Enter key. Then, select Option 1, Operational attributes. Review and increase the maximum number of active jobs parm if needed.
Also, although spawn() (and, therefore, QSHELL) bypass the job queue, if the maximum jobs are changed, typically the maximum active jobs for a job queue also must be changed. This is displayed under --> 6. Job queue entries.
Since this error message is a result of running out of available jobs. The recommendation is to put this job in its own subsystem or increase the number of jobs allowed to be running in the subsystem.
This only happening, on average, once or twice a month, no set pattern or time of day, so by the time I am told about the MSGW and I investigate the problem, nothing is apparent as to the cause.
My question is :- how can the QSH0002 error code be captured within a loop to somewhat (and I am stressing somewhat) ignored.
Hope that question makes sense
As always, ALL responses gratefully accepted
Programmer/Analyst, Direct Response
"If you're going through Hell, keep going" - Winston Churchill
Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.