View previous topic :: View next topic
|
Author |
Message |
pravle
New User
Joined: 06 Jun 2006 Posts: 8
|
|
|
|
Hi,
This is my first post in this forum.
My run of program is not producing any SYSOUT in the SDSF(Spool). I have taken the program from PRODUCTION and compiled and linked to my personal LOAD and have mentioned the same in STEPLIB.
When a run the same program with production load, SYSOUT is coming.
What could be the problem here? |
|
Back to top |
|
|
Manuneedhi K
Active User
Joined: 07 May 2008 Posts: 115 Location: Chennai
|
|
|
|
Have you coded //SYSOUT DD SYSOUT=* in the run jcl of the program? |
|
Back to top |
|
|
pravle
New User
Joined: 06 Jun 2006 Posts: 8
|
|
|
|
Yes, SYSOUT has been code. Along with it many other are coded.
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//LOGFILE DD SYSOUT=*
//SYSOUT DD SYSOUT=*
The problem is that the same step with PRODUCTION load is giving SYSOUT but when I compile the program in my personal load and run it, it is not giving SYSOUT. On top of that RC is returned as 0. |
|
Back to top |
|
|
Manuneedhi K
Active User
Joined: 07 May 2008 Posts: 115 Location: Chennai
|
|
|
|
Are you running the code from your load lib against the same prod data?
Isn't there a chance that the logic of the program and the input data works in a way that it bypasses all the display statements? |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
by using sysout=* you are defaulting to the jobcard class. is this class held, printed, deleted???
your job output could very well be in two or more classes, which means you have to find them in the spool. |
|
Back to top |
|
|
pravle
New User
Joined: 06 Jun 2006 Posts: 8
|
|
|
|
Thanks for your input.
The program is the same in both the cases and it is run against the same
data.
I will try tomorrow by putting the display statement at the
top below the PROCEDURE DIVISION, to validate your point. |
|
Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
|
|
|
|
Check the msgclass in your JOB CARD with sysout=* that is where all your sysout would be going. |
|
Back to top |
|
|
pravle
New User
Joined: 06 Jun 2006 Posts: 8
|
|
|
|
Thanks all for the ideas.
Manu you were right. When I put the display at the top of procedure division, the SYSOUT came. The code was calling some common module
after which the SYSOUT did not come.
I commented the call to the common module and in-lined the code in the program and SYSOUT came. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Hello PNR and welcome to the forums,
Quote: |
The program is the same in both the cases and it is run against the same data. |
Quote: |
The code was calling some common module after which the SYSOUT did not come.
I commented the call to the common module and in-lined the code in the program and SYSOUT came. |
Is this some new call or is it also in the original production version of the program? If it is in the production verson. . . .?
It is good to hear that it is working - as long as it will work in all cases |
|
Back to top |
|
|
mitha
New User
Joined: 01 Dec 2021 Posts: 19 Location: India
|
|
|
|
Same I am too facing this problem.I mentioned SYSOUT in my program.But in spool I couldn't able to check my output. Can anyone share what I need to do ? |
|
Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015 Posts: 1341 Location: Bamberg, Germany
|
|
|
|
mitha wrote: |
Same I am too facing this problem.I mentioned SYSOUT in my program.But in spool I couldn't able to check my output. Can anyone share what I need to do ? |
Yes, open a new topic and don't resurrect 13(!) year old posts! |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3076 Location: NYC,USA
|
|
|
|
Locked |
|
Back to top |
|
|
|