Why we code SYSOUT DD SYSOUT=* in SORT?

SyncSort's Sort Product, SyncTool for z/OS, SYNCINIT and SYNCLIST.
Previous topicNext topic

Topic Author
Technocrat
Registered Member
Posts: 29
Joined: Thu Oct 03, 2013 1:32 pm

Why we code SYSOUT DD SYSOUT=* in SORT?

Post by Technocrat » Wed Oct 09, 2013 12:15 pm

Hi,

I've observed at my shop that only while using Sort/ICEMAN/ utility we use SYSOUT DD SYSOUT = * . Is there some reason for that?


Regards

User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1379
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
Zodiac: Virgo

Re: Why we code SYSOUT DD SYSOUT=* in SORT?

Post by Robert Sample » Wed Oct 09, 2013 4:23 pm

From the September 2013 version of the DFSORT Getting Started manual:
The JCL statements you need for most jobs are as follows.
//jobname JOB
Signals the beginning of a job. At your site, you might be required to
specify information such as your name and account number on the JOB
statement.
//stepname EXEC
Signals the beginning of a job step and tells the operating system what
program to run. To run DFSORT, write the EXEC statement like this:
//stepname EXEC PGM=SORT
//STEPLIB DD
The DFSORT program would typically be in a library known to the
system, so the //STEPLIB DD statement would
not
be needed. However, if
DFSORT is not in a library known to the system, the //STEPLIB DD
statement defines the library containing the DFSORT program
//SYSOUT DD
Defines the data set in which DFSORT messages and control statements are
listed.
//SORTIN DD
Defines the input data set or concatenated input data sets.
//SORTWKdd DD
Defines a work data set for a sort. Typically not needed, because DFSORT
can allocate work data sets for a sort dynamically.
//SORTOUT DD
Defines the output data set.
//SYSIN DD
Precedes or contains the DFSORT program control statements.



User avatar

Anuj Dhawan
Founder
Posts: 2624
Joined: Sun Apr 21, 2013 7:40 pm
Location: Mumbai, India
Zodiac: Sagittarius

Re: Why we code SYSOUT DD SYSOUT=* in SORT?

Post by Anuj Dhawan » Wed Oct 09, 2013 4:35 pm

Robert has given you a very precise explanation, however I believe your question is quite generic. Did you mean why "*" is used in SYSOUT=*?


Thanks,
Anuj

Disclaimer: My comments on this website are my own and do not represent the opinions or suggestions of any other person or business entity, in any way.


Topic Author
Technocrat
Registered Member
Posts: 29
Joined: Thu Oct 03, 2013 1:32 pm

Re: Why we code SYSOUT DD SYSOUT=* in SORT?

Post by Technocrat » Tue Jul 08, 2014 11:02 pm

Anuj Dhawan wrote:Robert has given you a very precise explanation, however I believe your question is quite generic. Did you mean why "*" is used in SYSOUT=*?
Yes. Somtimes, I've seen SYSOUT=Y. What's the meaning of this?


Regards

User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1379
Joined: Fri Jun 28, 2013 1:22 am
Location: Dubuque Iowa
Zodiac: Virgo

Re: Why we code SYSOUT DD SYSOUT=* in SORT?

Post by Robert Sample » Wed Jul 09, 2014 12:14 am

There can be different SYSOUT classes defined to a system -- for example, one may be used exclusively to generate fiche, one for SMTP emails, and so forth. The specific job classes are set by the site as part of their set up of JES and z/OS. SYSOUT=* means to use the job default SYSOUT class (MSGCLASS on the JOB statement or whatever the site default is); SYSOUT=Y means to use class Y (which, again, will depend upon the site for its meaning).



Previous topicNext topic

Return to “SyncSort, SyncTool, SyncGener.”