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