There are already several ways that outqs are assigned and Job
Descriptions are clearly the preferred method. Thus it's not a 'way
around it' but the 'way to do it.' :-)
I wouldn't even want an outq parm on a jobq entry as it would be just
another way for some dunderhead to override payroll checks to the work
order printer in the shop!
- Larry "DrFranken" Bolhuis
On 2/28/2014 8:56 AM, Briggs, Trevor (TBriggs2) wrote:
I'm not sure why the OutQ parm is not provided on the ADDJOBQE command
(there's probably a very good but obscure reason), but the way round it
would be to create a JobD with the OutQ you want and specify this JobD
on each schedule entry.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Laine, Rogers
Sent: Friday, February 28, 2014 8:52 AM
To: 'Midrange Systems Technical Discussion'
Subject: Job Scheduler Entry
I'm using the basic job scheduler on v6.1 and would like to have all
entries in the scheduler put the reports in one OUTQ.
I have setup a User Profile just to handle job scheduler and enter this
name in the User parm.
When defining a new entry it does not provide an OUTQ parm to specify
Now if I do an option 10 Submit Immediately it does provide this parm to
specify the Output que that I want.
What am I missing something here or is there another way to handle.
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.