Don,
Remember to check the class that is associated with the route in the
subsystem. That determines the initial priority, but also sets the
subsystem memory pool that is used. I strongly suggest you move the
QZDASOINIT and QSQSRVR jobs and the XMLSERVICE jobs into a memory pool
specified for those jobs. Now you have the ability to manage the memory
usage and activity levels for those jobs directly.
The prestart jobs are changed with CHGPJE.
The subsystem memory pools are updated with WRKSHRPOOL and CHGSBSD.
The routing program and class are set with CHGRGTE/ADDRTGE
Use WRKCLS to manage the classes.
Assuming you don't just move the jobs from one place to another (which will
have no real effect on the system good or bad) and allocate memory as
appropriate to those jobs you will help your system as opposed to adversely
affect it.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Don Brown
Sent: Monday, July 02, 2018 7:25 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] XMLSERVICE running in QBATCH
We have Zend server running on a Linux box using ODBC connection to IBMi
V7R3.
Currently all the XMLSERVICE jobs are running in QBATCH and submitted via
the QS36EVOKE job queue.
I presume that this is based on the job description xmlservice/ZSVR_JOBD
that specifies that job queue.
While I expect if I change the job queue entry on this job description that
the XMLSERVICE jobs will then use that job queue and I intend on either
creating a new sub-system description or use the QUSRWRK sub-system.
As this is a production environment I am hoping someone can confirm a change
to the job queue on the job description will not cause any unexpected
results.
Thanks to any responses
Don Brown
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/web400.
midrange.com
