Re: SPTP Problem when running in Batch

Thanks Bryan. I did not know that. I think I am OK in my original
configuration then.

I want no more than one sftp job running at a time. My jobq then can be
single thread. The number of jobs allowed in the subsystem should be
sufficient for the sftp, spawned jobs and whatever 'normal' jobs are
running.


Gord



On Tue, Feb 7, 2012 at 6:44 AM, Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

It sounds to me like you think the spawned jobs from the sFTP program
will "submit" its jobs to the same jobq from whence it came.
That is incorrect, when a PASE or QSHELL jobs spawns others they are
BCI(Batch Immediate) jobs and as such do not "go through" a jobq to get
to an active state, they "just show up".
I worry that if you have 8 slots for your sftp jobq you could
potentially have 8 of your sftp jobs running at a time(plus spawned
jobs). Depending on what each sftp job does it could present problems.

I suggest you leave the SBSd max jobs at *nomax, but limit the number of
jobs that can be active at the jobq level.
for instance:
qbatch max 1
qbatch1 max 2
multi max 4
etc. to fit your needs

Bryan


GordM1 Hutchinson said the following on 2/6/2012 3:05 PM:

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

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