View previous topic :: View next topic
|
Author |
Message |
Ajay Bisht
New User
Joined: 12 Sep 2006 Posts: 6
|
|
|
|
Hi parikshit sir oooppsss HI parikshit,,,
As per ur mail i am again posting my doubt in this forum regarding sysprint and sysout.
I hope u don't mind it sir..
a) Can u plz tell me here again abut sysprint and sysout. For what purpose they are used.
For eg.
//sysprint dd sysout=*
//sysout dd sysout=*
I am still confused that if we mentioned both of them in our jcl then why not both of them get displayed in our o/p spool ??
And both statement signifies that output will go to the output class assigned in msgclass..
b) Is it possible in any situation that we can see both in our output spool.??
sir ji plz ab to reply de dena........
Regards
Ajay |
|
Back to top |
|
|
shreevamsi
Active User
Joined: 23 Feb 2006 Posts: 305 Location: Hyderabad,India
|
|
|
|
//SYSPRINT DD SYSOUT=*
IS USED WHEN THERE IS ANY MESSAGE FROM THE UTILITY.
//SYSOUT DD SYSOUT=*
IS USED WHEN THERE IS ANY MESSAGE FROM THE PROGRAM.
I WILL TRY TO EXPLAIN WITH EXAMPLE.
WHEN WE ARE USING IEFBR14 UTILITY, THIS UTILITY WONT PERFORM ANY OPERATION. THIS IS A DUMMY UTILITY.
THIS UTILITY WONT GENERATE ANY MESSAGE.
SO WE DONT NEED
//SYSPRINT DD SYSOUT=*
WHEN USING THE IEFBR14
WHEN WE USE IEBGENER UTILITY,
THIS UTILITY GENERATES A MESSAGE THAT
GENARATE AT EOF i.e. end of file, etc
SO THIS MESSAGE IS GENERATED BY THE UTILITY
WE NEED
//SYSPRINT DD SYSOUT=*
WHEN USING IEBGENER UTILITY.
IF WE ARE NOT CODING THIS , WE WILL SURELY GET ERROR THAT SYSPRINT DD STATEMENT IS MISSING.
I THINK IT MUST BE CLEAR NOW.
IF I AM WRONG SOMEWHERE PLEASE CORRECT ME |
|
Back to top |
|
|
surya_pathaus
Active User
Joined: 28 Aug 2006 Posts: 110
|
|
Back to top |
|
|
|