We run multiple apps, needed to be to control both interactive and batch for all apps.
We created an interactive (INTER_**) and a batch (BATCH_**) subsystem for each app.
We chose BATCH_** so when one does an WRKACTJOB, you'll see any batch jobs running on page 1.
An app can easily be controlled by ending their two subsystems.
We do not start qinter, qbatch is started, but only for system default jobs.
All interactive subsystems use the *INTERACT memory pool.
We use wild card workstation entries so interactive users start in the proper subsystem.
All batch subsystems use the *SHRPOOL1.
Performance adjuster keeps every tuned as need. Batch *SHRPOOL1 will have little memory if no batch jobs running.



Work Station Name Entries


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Wednesday, February 19, 2014 11:13 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Controlling Job Types


What you say about memory allocation is true; however I suspect it's not going to be much of an issue on this box since they have been working in a simpler environment for at least some time. Managing the performance related system values will eliminate 90% of the potential land mines.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, February 19, 2014 9:52 AM
To: Midrange Systems Technical Discussion
Subject: Re: Controlling Job Types

Correct. If you change your controlling subsystem from QBASE to QCTL it will break it up as desired.
A controlling subsystem of QBASE is the default. This should probably be changed to QCTL for all installations running a 'traditional' application such as ERP and whatnot with the old setup of 5250 users and batch jobs.

If your lpar is different, like all Domino (like many of my lpars), or almost no 5250 use but all web use, then a different setup is recommended.
Frankly I leave my "all Domino" partitions at QBASE. I have some lpars where it may be days in between when a single user signs in using 5250.
Other lpars where it may be weeks before more than 2 do. These lpars use QBASE.
One lpar where DSPSYSSTS shows 470 signed on users. That one (and a few
others) uses QCTL.

One caveat about breaking the subsystem out is memory tuning. Yes, there is an auto performance adjuster built into the system that if you leave running will shift memory around to the right pool. However, if the whistle blows at 5pm and 90+% of your users sign off of all their 5250 applications and a large quantity of intensive batch jobs kicks off then it may take awhile to properly shift memory from interactive to batch. And only slowly change it back when the starting bell sounds the next morning.
There are products to shift this faster. Some people have job schedule entries like DAY or NIGHT which shift that memory around in one big chunk at these times also.

Rob Berendt
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755

From: "Laine, Rogers" <Rogers.Laine@xxxxxxxxxxxxxxx>
To: "'MIDRANGE-L@xxxxxxxxxxxx'" <MIDRANGE-L@xxxxxxxxxxxx>
Date: 02/19/2014 10:26 AM
Subject: Controlling Job Types
Sent by: midrange-l-bounces@xxxxxxxxxxxx


I'm running v6.1 and have some questions on how to control what subsystem Batch and Interactive jobs are processed.
What I'm trying to accomplish is to control access to the system for all application type users by stopping their subsystem(QINTER).

We currently have QCTLSBSD set at QBASE which is the shipped default.
From what I have read all job types are run under this subsystem. This
appears to be true for our current work load.
The application users profiles have Job Description of RMS61 with Library of QGPL.
Now if I changed QCTLSBSD to QCTL it will start the below subsystems...

QINTER ==== Interactive Started with QCTL
QBATCH ==== Batch Started with QCTL
QSPL ==== Spooling Started with either QBASE or QCTL
QCMN ==== Communication Started with QCTL
QSERVER === File Server Started with either QBASE or QCTL

So will my Interactive users now run under QINTER and the Batch jobs run under QBATCH without changes the Job Description?

This E-Mail transmission (and/or the documents accompanying it) may contain information belonging to the sender which is confidential, privileged and/or exempt from disclosure under applicable law. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this E-Mail transmission in error, please immediately notify us by return E-Mail or telephone to arrange for return of its contents including any documents.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact