Re: SPTP Problem when running in Batch

Thanks Scott. Our QShell requirements right now are strictly for sftp for
one EDI partner. I've set up a job queue only for this with a maximum of 8
jobs. The subsystem has a maximum of 11.

I guess I could set the job queue to *NOMAX but I hesitate to have a
subsystem at *NOMAX.


Gord



On Mon, Feb 6, 2012 at 1:19 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

It's not a fixed number, Gord. Whenever QShell needs to run two tasks
simultaneously, it creates an additional job.

For example, if you did this:

ls -l | grep ^- | pr | Rfile -wQ mylib/myfile

It has to run multiple jobs, because ls, grep, pr and Rfile all run
simultaneously. I don't know exactly which things run in their own jobs
and which do not, so I'm not sure if this spawns 3 or 4 jobs? (one to
run ls, one to run grep, one to run pr, and one to run Rfile, or does
one of them run in the current job?)

Plus, any given program can potentially fork additional jobs. (I doubt
ls, grep, pr or Rfile does this, but sftp might...?)

So, I don't know the exact number of jobs needed... honestly, never
really thought about it before. I always my QShell in a *NOMAX queue.


On 2/6/2012 7:45 AM, GordM1 Hutchinson wrote:

Scott, How many jobs in the sftp/qshell jobq would you recommend? How
many jobs does qshell spawn?

Gord

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.