|
|
| Author |
Message |
Anuj D.
Senior Member
Joined: 22 Apr 2006
Posts: 1361
Location: Mumbai, India
|
|
|
|
Hi,
In this statement
| Code: |
| //SYSOUT DD SYSOUT=Y |
I understand 'Y' designates a special class while in
| Code: |
| //SYSOUT DD SYSOUT=* |
SYSOUT class would be defaulted to the respective LPAR.
My concern is, if I used "Y", how differently the system would treat it ?
Can I say, if "Y" is designated to Production classes, then the DASD used for system output in production would be little costlier than a test DASD ? (might be dumb assumption but any how I come up with this thought, Please suggest.) |
|
| Back to top |
|
 |
References
|
 Posted: Wed May 07, 2008 10:59 am Post subject: Re: Diff. between SYSOUT=Y and SYSOUT=* |
|
|
|
|
gcicchet
Senior Member
Joined: 28 Jul 2006
Posts: 365
|
|
|
|
Hi Anuj,
SYSOUT classes are site dependent.
A '*' for SYSOUT class indicates that the class given by the
MSGCLASS= parameter on the job statement is to be used for
this SYSOUT DD statement, so that all the job's SYSOUT will
go to the same output class.
I'm not aware of any intallation where different DASD is used for different output class.
Gerry |
|
| Back to top |
|
|
Anuj D.
Senior Member
Joined: 22 Apr 2006
Posts: 1361
Location: Mumbai, India
|
|
|
|
Hi,
In this
| Code: |
| //SYSOUT DD SYSOUT=Y |
usually, this type of SYSOUT parameter names the output class to which the printed output belongs or the forms on which the data set is to be
printed.
My concern is in case it's (Y) dedicated to some DASD, does that mean that DASD is costlier just because it's in service of Production class..? |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 6983
Location: 221 B Baker St
|
|
|
|
Hi Anuj,
| Quote: |
| My concern is in case it's (Y) dedicated to some DASD, does that mean that DASD is costlier just because it's in service of Production class..? |
Probably not. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 2589
Location: Brussels once more ...
|
|
|
|
And different classes could mean different handling - at the shop I am now, one class is routed into the sysout repository and kept for far longer than it would being left on the JES spool.
I guess it's a case of talking to the people that set it up. |
|
| Back to top |
|
|
|
|
