|
View previous topic :: View next topic
|
| Author |
Message |
vd120
New User
Joined: 06 Nov 2010
Posts: 24
Location: NYC
|
|
|
|
Hi,
I'm looking for settings in JCL (if any) I can use to avoid printing Job name with job parameters as the first and last page of the print output.
I try IEBGENER and SORT with SORTOUT pointed to SYSDA=A, but when print comes out it is always first and last page with job name and job parameters. I need to print one page information for users and want to avoid print 3 pages every time they need one. Users are fine with this as printed information not private and they know which one which.
I offer to use email instead of print, but user needs actual paper.
Can be anything done to save a paper?
Thanks,
VD. |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Have you tried the JCL manual? There is a paperless one if you click the link at the top of the page. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
VD.
the site could have an exit for the stream to the printer,
and always (SOP) preface and suffix each output with
JOB Name and Number - that way the customer can complain about a Job (that ops-team can use) instead of 'his report' (whose report?).
this is often the case with lasor-printers set-up in different departments.
I don't think you are going to get around it.
But, if anything can shut-it-off,
it would be a JOBcard Parm or possibly a DIST or ROUTE parm.
'sides, if you manage to do it,
then they will want their name printed on the first page........ |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Suggest you talk with your Operations/Systems support about your local configuration.
We handle this by using different output classes for output that is wanted on paper or printed remotely and we queue the stuff the user does not want/need.
There is much to discover in the manual, but the manuals will not know your site-specific implementation. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2546
Location: Silicon Valley
|
|
|
|
Perhaps you meant SYSOUT=A
| Quote: |
| Have you tried the JCL manual? |
Look at the MSGLEVEL and MSGCLASS parameters on the JOBCARD. Use a class that is 'held'. |
|
| Back to top |
|
|
vd120
New User
Joined: 06 Nov 2010
Posts: 24
Location: NYC
|
|
|
|
Thank you to every one for responses.
My work was interrupted by nature (hurricane Sandy). I tried different MSGLEVEL, MSGCLASS, CLASS, and destination: same result everywhere.
It is interesting that people who work here about 20 years ago absolutely sure that they were able to do it.
Will look for way around it or try to convince users to use email as report delivery method. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| It is interesting that people who work here about 20 years ago absolutely sure that they were able to do it. |
Sure they were. Every system i've worked on for more than 30 years has been able to do what you want to do.
Have you talked with the "support" people to learn which class(es) will stay in the queue and not be printed?
On one of the systems i support this:
| Code: |
//PRINTFLE DD SYSOUT=O,DEST=LOCAL
//PRNTFLE1 DD SYSOUT=O,DEST=LOCAL
//SYSOU1 DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSOUT DD SYSOUT=* |
causes the first 2 outputs to be routed to the large local printer and the others to remain in the queue where they may be viewed for a time. They are manually deleted or "roll off" after a few days.
Note that the class and dest are probably different on your system.
You need to find someone who supports your system that understands how to accomplish this on your system. I suspect it is "all there" but possibly no one remembers the details. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Whether your site uses JES2 or JES3, there are exits that can be customized at the site. Some of these exits deal with separator pages between jobs, so you may have to contact your site support group to determine how the JES exits are implemented at your site before getting a final answer to your query. |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
I've never seen a totally stripped report like you're trying to produce. There ALWAYS had to be an ID page for the output of a job. Even if we only routed the report to the print queue, there was a page showing which job it came from.
If you don't have that page, you could end up with several reports that can't be matched up with the job that produced them. You could have test jobs and prod jobs creating he same report, and the folks in the print room would just send them out.
That ID page is IMPORTANT. |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| vd120 wrote: |
Hi,
I'm looking for settings in JCL (if any) I can use to avoid printing Job name with job parameters as the first and last page of the print output.
I try IEBGENER and SORT with SORTOUT pointed to SYSDA=A, but when print comes out it is always first and last page with job name and job parameters. I need to print one page information for users and want to avoid print 3 pages every time they need one. Users are fine with this as printed information not private and they know which one which.
I offer to use email instead of print, but user needs actual paper.
Can be anything done to save a paper?
Thanks,
VD. |
This implies that if you have, e.g., 1,000 users to produce this report for, you will run 1,000 jobs with the user ID as input. Although it may be doubted if anyone in your shop is able or willing to make the necessary changes, have the local powers that be at least contemplated hiring someone to alter the report program so that it would take a list of 1,000 user ID and produce an output of 1,002 pages (header, 1,000 reports, and trailer) instead? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
I may have misunderstood . . .
My understanding was that the goal was to eliminate the JES standard outputs as well as informational "stuff" other than the actual report(s).
The Job Name is always printed on a leading (and trailing -iirc) separator page. As Ed mentioned, it would be unmanagable if the print room had to deal with thousands of reports with no job separators. |
|
| Back to top |
|
|
vd120
New User
Joined: 06 Nov 2010
Posts: 24
Location: NYC
|
|
|
|
Thank you all for your input.
My intent was to find some parameter(s) I can use in the JCL to eliminate header & trailer pages (which is standard for job printout), but this should be only for a particular job (for example JOBPARM parameters). I just learn that our printers is a VPS printers and setting can be changed manually through the printer menu, but this is not what I’m looking for. I don’t want to change global settings (to avoid unmanageable mess), I’m looking for particular job to be able to print without header & trailer pages. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Then do as suggested and learn how to specify your output class/destination for each sysout dataset. . .
The only people who can show what to use are people on your system. We have no idea about your site-specific definitions.
Unless i misunderstand, the jcl i posted earlier should do what you want. . . If it does not, explain why. |
|
| Back to top |
|
|
|
|
