1. Also Vps exit13 should support selective requeueing based on 'Word 3 (+12) 
Address of Dataset Attributes (VPSSDSAT)'.
2. You could always define separate queues for batch and user output pointing 
to the same destination. Then each queue can have tailored REQ* parms.
3. If you are patient, you can ask LRS to add this functionality to a future 
Vps release. They have been receptive to coding exit logic into simple 
parameters with the dataset add Exit 14 precedent. In fact LRS has been my most 
approachable vendor to date.

Cheers,
MARK DOUGLAS 
Senior IT Support Consultant
Mainframe
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Hansen, Dave L - Eagan, MN
Sent: Friday, 30 March 2012 7:29 AM
To: [email protected]
Subject: Printing limits and userids

Group,

  We have a lot of large reports in our MVS spool.  Any suggestions on limiting 
users from printing large reports by their userids, or a way to differentiate 
between valid print processing and potentially erroneous print processing by 
report name with JES2?  A 50,000 page report may be valid if coming from a 
production job but may well be in error if generated by a user/programmer.  
Somehow there would need to be a reference to valid users (userids), valid 
production jobs, valid printers, and number of pages.  The pages may not be 
correct because the APF information has not been converted.

  I contacted the RACF group and it appears there is no option to limit 
printing by userid.

  I contacted our print software vendor (VPS).  I have two choices:
     - Dynamically change the print page limit by printer.  Not userid specific 
and you can print in "sections" which will still get your print printed and not 
exceed the limit of printable pages.
     - Use Exit 22 where we can trap the userid and requeue the large report 
output if it meets specifications.  Then an appropriate operator command will 
need to be issued to JES to make SYSOUT available for printing again.  Sounds 
like big overhead.  

  So, any job can send output to the MVS spool.  Maybe I could dedicate a class 
or job form for the large reports, but I don't know the best way to do this in 
JES2.  From what I've seen you can just change the JES2 resources. and away 
goes the user/programmer's large report to the wrong printer.
   

   Many thanks in advance,  Dave  


Dave Hansen 
Eagan Software Systems Branch 
651-406-1208 
[email protected] 

 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN


***************************** Disclaimer *****************************

The contents of this electronic message and any attachments are intended only 
for the addressee and may contain privileged or confidential information. They 
may only be used for the purposes for which they were supplied. If you are not 
the addressee, you are notified that any transmission, distribution, 
downloading, printing or photocopying of the contents of this message or 
attachments is strictly prohibited. The privilege of confidentiality attached 
to this message and attachments is not waived, lost or destroyed by reason of 
mistaken delivery to you. If you receive this message in error please notify 
the sender by return e-mail or telephone.

Please note: the Department of Public Works carries out automatic software 
scanning, filtering and blocking of E-mails and attachments (including emails 
of a personal nature) for detection of viruses, malicious code, SPAM, 
executable programs or content it deems unacceptable. All reasonable 
precautions will be taken to respect the privacy of individuals in accordance 
with the Information Privacy Act 2009 (Qld). Personal information will only be 
used for official purposes, e.g. monitoring Departmental Personnel's compliance 
with Departmental Policies. Personal information will not be divulged or 
disclosed to others, unless authorised or required by Departmental Policy 
and/or law.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to