sysprint and sysout



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

sysprint and sysout

Postby deppquestcage » Wed Dec 15, 2010 2:39 pm

What is the difference between sysprint and sysout in jcl?
deppquestcage
 
Posts: 7
Joined: Mon Nov 22, 2010 12:21 pm
Has thanked: 0 time
Been thanked: 0 time

Re: sysprint and sysout

 

Re: sysprint and sysout

Postby MrSpock » Wed Dec 15, 2010 2:45 pm

They're different DD names, used by default for different programs as required by those programs.
User avatar
MrSpock
Global moderator
 
Posts: 810
Joined: Wed Jun 06, 2007 9:37 pm
Location: Raleigh NC USA
Has thanked: 0 time
Been thanked: 2 times

Re: sysprint and sysout

Postby deppquestcage » Wed Dec 15, 2010 3:47 pm

Would you pls provide an example for that ie can you specify where exactly they are used?
would yo please give a good description about them.
deppquestcage
 
Posts: 7
Joined: Mon Nov 22, 2010 12:21 pm
Has thanked: 0 time
Been thanked: 0 time

Re: sysprint and sysout

Postby NicC » Wed Dec 15, 2010 3:53 pm

They are just 'print' ddnames and you use them when the program requires them which will be documented in the manual for the program. programs/utilities write their messages to them. User reports for programs written by you would go to your own user-defined ddnames. Sometimes you need SYSPRINT and SYSOUT for your own programs - SYSPRINT is required by PL/1 programs and SYSOUT by COBOL programs.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2749
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisies (almost)
Has thanked: 4 times
Been thanked: 110 times

Re: sysprint and sysout

Postby Robert Sample » Wed Dec 15, 2010 5:26 pm

We cannot specify exactly when they are used because there is no one answer to that question. System utilities, such as IEBGENER, tend to use SYSPRINT but any program can use it, or SYSOUT, or PRINTOUT, or whatever DD name they want to for output.

You've already gotten the best possible description for them from MrSpock.
Robert Sample
Global moderator
 
Posts: 3443
Joined: Sat Dec 19, 2009 8:32 pm
Location: Dubuque, Iowa, USA
Has thanked: 1 time
Been thanked: 242 times

Re: sysprint and sysout

Postby deppquestcage » Thu Dec 16, 2010 3:05 pm

THANK YOU VERY MUCH
deppquestcage
 
Posts: 7
Joined: Mon Nov 22, 2010 12:21 pm
Has thanked: 0 time
Been thanked: 0 time

Re: sysprint and sysout

Postby steve-myers » Thu Dec 16, 2010 7:23 pm

//SYSPRINT DD  SYSOUT=(A,WRITER,FORM)
//SYSOUT    DD  SYSOUT=*
In JCL, SYSPRINT is always a DD name. A DD name is just one to 8 characters that are used to identify a particular DD statement, the character string is chosen by the programmer when he writes a program. Many programs use SYSPRINT to indicate the data set is intended to be printed, SYSPUNCH to indicate the data set is to be punched on a card punch machine. The major sort programs (IBM's DFSORT, Syncsort, and CA-SORT) all use SYSOUT to specify a message data set.

SYSOUT can be a DD name; it is also a JCL parameter that provides up to 3 sub-parameters. The first sub-parameter is an output class. Back in the 1960s, output class A generally sent the output to a printer, and output class B generally sent the output to a card punch machine. Originally, the second sub-parameter specified the name of a program used when writing output to a printer or card punch, but it has been hi-jacked for other purposes since then. Writer program name INTRDR, for example, now generally indicates the output data is intended for the JES2 or JES3 "internal reader," which allows a program to submit another job. The third sub-parameter specifies a form name, which in turn relates to the paper used when printing output, or the particular card stock used when punching output.
steve-myers
Global moderator
 
Posts: 1917
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 206 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post