RE: Bunch of QPWFSERVSD & QZDASRVSD jobs sitting on jobq

Thanks for the reply!  Can you tell me what it is these jobs do?  In their
current state, I do not seem to be impacted in my daily routine.

>startup program<
This is fine and good, but sometimes the subsystems will be taken down and
then brought back up without an IPL.  That is why I have it on the job
scheduler.

Dan Bale
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of PWeyer@compures.com
Sent: Wednesday, March 20, 2002 2:34 PM
To: midrange-l@midrange.com
Subject: Re: Bunch of QPWFSERVSD & QZDASRVSD jobs sitting on jobq



<snip>
Hmmm, I schedule a STRHOSTSVR *ALL job to run every day at 6 a.m. so that I
can be sure my Client Access can log on to the system, and this job submits
the other two jobs.
<end snip>

Try adding the STRHOSTSVR *ALL to your start-up program.  That way, anytime
you start the controlling subsystem host servers will automatically start.
***NOTE***  Keep in mind that when you upgrade your operating system that
host servers will start when TCP/IP starts.

<snip>
Should I delete the jobs?  Or release the jobq (after
deleting all but the last submission of these two jobs) so that these two
jobs do their thing?
<end snip>

FROM THE CONSOLE -- (1)  End the jobs from the jobq, (2) ENDHOSTSVR *ALL,
and (3) STRHOSTSVR *ALL.  Also, make sure that the jobq the other two jobs
are being submitted to is released.

Paul R. Weyer
Senior Solutions Architect
Computech Resources, Inc.