Re: SPTP Problem when running in Batch

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

Gord,

In addition to the recommendations below, make sure the activity level 
on the shared pool the job runs in is high enough for the number of 
threads.  Adjust memory as needed although these jobs typically do not 
use all that much memory, just lots of threads.

The easiest way to determine how many threads are running in that pool 
is with System i Navigator.  Open Work management, Memory pools, and 
Active pools.  You should see current threads in that display.  If not 
use F12 (or right click on Active pools and choose "customize this view" 
and then "columns")  and pick "Current Threads" and move it into the 
current columns.

Alternatively you can use WRKACTJOB and F11 twice to see the threads in 
each job.  Add them up for the shared pool and you'll have your number.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/6/2012 8:06 AM, Jeff Young wrote:
> Gord,
> I found that for my job, it spawned 3 additional jobs.
> I had to increase the maximum jobs from the job queue and the maximum jobs
> in the subsystem to handle it.
>
>
>
>
> On Mon, Feb 6, 2012 at 8:45 AM, GordM1 Hutchinson<gordm1@xxxxxxxxxxxxxxx>wrote:
>
> > >  Scott,  How many jobs in the sftp/qshell jobq would you recommend?  How
> > >  many jobs does qshell spawn?
> > >
> > >
> > >  Gord
> > >
> > >
> > >
> > >  On Fri, Feb 3, 2012 at 7:46 PM, Scott Klement
> > >  <midrange-l@xxxxxxxxxxxxxxxx>wrote:
> > >
> > > >  >  hi Jeff,
> > > >  >
> > > >  >  QShell needs to be able to spawn additional jobs.  (It is not like a
> > > >  >  normal program that runs in all one job.)
> > > >  >
> > > >  >  Please make sure that the batch jobq is "multi-threaded" (allows more
> > > >  >  than one simultaneous job)
> > > >  >
> > > >  >  Your message says that you're getting errno 3489 which is "System
> > > >  >  resources not available to complete request".  There are probably a
> > > >  >  hundred things that could cause that error, but attempting to run in a
> > > >  >  single-threaded jobq is one of them.  And the fact that it works
> > > >  >  interactive but not batch seems to fit, too.
> > > >  >
> > > >  >  To display what an errno means, you can do:
> > > >  >       DSPMSGD CPExxxx
> > > >  >  where xxxx is the errno.  (In your example, CPE3489)
> > > >  >
> > > >  >  Good luck!
> > > >  >
> > > >  >
> > > >  >  On 2/3/2012 6:38 PM, Jeff Young wrote:
> > > > >  >  >  Thanks John,
> > > > >  >  >  I tried that, but it still does not work,
> > > > >  >  >  I have found what appears to be the issue, but do not understand it.
> > > > >  >  >  When running in Batch, the program receives the following message
> > > > >  >  >                                         Message . . . . :   Error found
> > > >  >  with
> > > > >  >  >  QSH session, reason code 4, errno 3489.
> > > >  >  --