Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
sysout=1?? 2
- Thread starter rozzay
- Start date
-
1
- #2
Hi Rozzay,
I think that sysout=1 is simply a sysout class that has been defined as a numeric rather than an alpha character. In most sites, the sysout classes are set up as alpha characters which define printers or SAR listings etc. and I think that sysout=1 is just a variation of sysout=A.
hth
Marc
I think that sysout=1 is simply a sysout class that has been defined as a numeric rather than an alpha character. In most sites, the sysout classes are set up as alpha characters which define printers or SAR listings etc. and I think that sysout=1 is just a variation of sysout=A.
hth
Marc
-
1
- #3
Hi Roz,
Just to add a few comment to what Marc contributed:
sysout=* used to mean that the O/P for that DD is written to the same device that submitted the job. Usually a terminal. With the widespead use of spooling that may have changed.
If I may correct a minor point of Marc's, sysout classes don't define printers, they merely group the sysout. Usually tech support creates a variety of sysout writers that are "start"ed by OPS to create hard copy or disk resident archival copies. Some shops have 3rd Party packages that append delivery info to the sysout. Some sysout are held and never printed; they're just viewed from the Q they were assigned to, and eventually deleted.
All of these processing options must be identified and differentiated. So to determine which sysout is to get what processing, sysout classes are used to indicate the processing required.
Regards, Jack.
Just to add a few comment to what Marc contributed:
sysout=* used to mean that the O/P for that DD is written to the same device that submitted the job. Usually a terminal. With the widespead use of spooling that may have changed.
If I may correct a minor point of Marc's, sysout classes don't define printers, they merely group the sysout. Usually tech support creates a variety of sysout writers that are "start"ed by OPS to create hard copy or disk resident archival copies. Some shops have 3rd Party packages that append delivery info to the sysout. Some sysout are held and never printed; they're just viewed from the Q they were assigned to, and eventually deleted.
All of these processing options must be identified and differentiated. So to determine which sysout is to get what processing, sysout classes are used to indicate the processing required.
Regards, Jack.
Hi Roz,
I should have also mentioned that these classes can be used for ANY kind of differentiation. They can be used to indicate that one contains data for user group x and another for user group y; that another contains a certain type of output; you name it.
The sysout writers I mentioned before can be used to vary the printer, the paper, the forms overlays, the destination, etc., depending on the sysout class it was designed to process.
Jack
I should have also mentioned that these classes can be used for ANY kind of differentiation. They can be used to indicate that one contains data for user group x and another for user group y; that another contains a certain type of output; you name it.
The sysout writers I mentioned before can be used to vary the printer, the paper, the forms overlays, the destination, etc., depending on the sysout class it was designed to process.
Jack
- Status
Similar threads
- Locked
- Question
- Locked
- Question