× 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.


  1.  Home
  2. MIDRANGE-L
  3. October 2012

Re: Trapping a QSHELL command error in CL

On Wed, 24 Oct 2012 14:47:43 +0000, Alan Shore wrote:

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.

Had a similar problem recently, running a shell script in PASE. Maximum
jobs was 10 in qbatch. Does your script initiate any background commands?
How about executing sleep? Do you run anything within backquotes? That
and probably lots of other stuff too, run in a new shell, which counts as
another job. I saw messages in STDERR about being unable to fork. I was
lucky, it was a low resource job late at night. I just moved it to the
qsysnomax job queue, and everything was happy.

Pete

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.