MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

RE: Controlling Job Types



fixed

Laine,

ADDJOBQE for each jobq assigns a jobq to a subsystem.
Also sets the jobq for single or multi threaded.
Most are always single threaded, we have a few multi threaded, (CM_MUTLI)

Add Job Queue Entry (ADDJOBQE)

Type choices, press Enter.

Subsystem description . . . . . Name
Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
Job queue . . . . . . . . . . . Name
Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
Maximum active jobs . . . . . . 1 0-1000, *NOMAX
Sequence number . . . . . . . . 10 1-9999

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Laine, Rogers
Sent: Wednesday, February 19, 2014 12:09 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Controlling Job Types

Jim,

The Job Description for my application has Job Queue of QBATCH and Routing Data of QCMDI.
So the QBATCH tells the job what queue to place it on, but the QCMDI tells it what type of job to use?
So what determines the subsystem to use?

Rogers


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

Laine:

The answer to your question is yes you should change that system value and reboot IBM i. It will come up with QCTL as the controlling subsystem and QINTER and QBATCH will be started.

As suggested below the article Bryan is still very valid.

You will find your ability to manage the jobs on your system will be significantly enhanced by that small but very significant change.

You should also check to be sure the following system values are set:

QPFRADJ is set to 3 - automatic adjustment QDYNPTYADJ is set to 1 - On QDYNPTYSCD is set to 1 - On.

Those are the defaults so they most likely still are set that way. That will avoid some memory allocation issues right after the change.

More advanced memory management etc. will be available to you after these changes.



--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of TheBorg
Sent: Wednesday, February 19, 2014 9:38 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Controlling Job Types

Old, but still valid:
http://iprodeveloper.com/systems-management/crash-course-work-management-par
t-1

-sjl


"Laine, Rogers" wrote in message
news:mailman.2900.1392823558.25182.midrange-l@xxxxxxxxxxxx...

Hello,

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?

Thanks,
Rogers
************************************************
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

************************************************
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.






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

This mailing list archive is Copyright 1997-2014 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