View previous topic :: View next topic
|
Author |
Message |
ParagChouguley
Active User
Joined: 03 Feb 2007 Posts: 175 Location: PUNE(INDIA)
|
|
|
|
Hi All,
A batch COBOL execution job has following statement in JCL
Code: |
//SYSOUZ DD SYSOUT=*
|
but sysouz is not shown in spool in production.
What could be the reason and how to resolve it ? |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
what is the reference name of the file in the fd of the program?
if this is for displays, I would think that this is a typo and should be sysout. |
|
Back to top |
|
|
ParagChouguley
Active User
Joined: 03 Feb 2007 Posts: 175 Location: PUNE(INDIA)
|
|
|
|
Quote: |
if this is for displays, I would think that this is a typo and should be sysout.
|
Yes, it is for DISPLAY statements in COBOL program. But this is what all of our other programs use --- "SYSOUZ" |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
then go to your operations people and determine if sysouz is recognized |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
SYSOUZ even if confusing is a perfectly legal ddname by any means
the reason why it does not contain any data, is certainly hidden behind some programming quirk
very little we can do from here
if it &works in one environment and not in another,
analyze the environment differences |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
but sysouz is not shown in spool in production. |
Because the was nothing written to the sysouz dd in the producton run?
Is this ddname documented in your jcl statndards? Is it possibly for debugging and is "turned off" in production for normal use?
You might check with your system support people and ask if they know the "rules" for this ddname. |
|
Back to top |
|
|
|