Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

No SYSOUT coming in SPOOL

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
pravle

New User


Joined: 06 Jun 2006
Posts: 8

PostPosted: Thu Jun 12, 2008 6:51 pm    Post subject: No SYSOUT coming in SPOOL
Reply with quote

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
View user's profile Send private message

Manuneedhi K

Active User


Joined: 07 May 2008
Posts: 115
Location: Chennai

PostPosted: Thu Jun 12, 2008 6:59 pm    Post subject:
Reply with quote

Have you coded //SYSOUT DD SYSOUT=* in the run jcl of the program?
Back to top
View user's profile Send private message
pravle

New User


Joined: 06 Jun 2006
Posts: 8

PostPosted: Thu Jun 12, 2008 7:19 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Manuneedhi K

Active User


Joined: 07 May 2008
Posts: 115
Location: Chennai

PostPosted: Thu Jun 12, 2008 7:53 pm    Post subject:
Reply with quote

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
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6968
Location: porcelain throne

PostPosted: Thu Jun 12, 2008 8:37 pm    Post subject:
Reply with quote

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
View user's profile Send private message
pravle

New User


Joined: 06 Jun 2006
Posts: 8

PostPosted: Thu Jun 12, 2008 8:37 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Craq Giegerich

Senior Member


Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA

PostPosted: Thu Jun 12, 2008 9:01 pm    Post subject:
Reply with quote

Check the msgclass in your JOB CARD with sysout=* that is where all your sysout would be going.
Back to top
View user's profile Send private message
pravle

New User


Joined: 06 Jun 2006
Posts: 8

PostPosted: Fri Jun 13, 2008 9:13 am    Post subject:
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Fri Jun 13, 2008 9:48 am    Post subject:
Reply with quote

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 icon_smile.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
This topic is locked: you cannot edit posts or make replies. SDSF multiple spool datasets extracte... PJAlarcon CLIST & REXX 1 Fri Apr 21, 2017 10:50 pm
No new posts REXX cdoe to purge a JOB from spool a... Sulabh Agrawal CLIST & REXX 11 Thu Mar 09, 2017 11:36 am
No new posts Report output in Spool amitc23 JCL & VSAM 4 Tue Apr 26, 2016 4:32 pm
No new posts Extract specific step spool data enrico-sorichetti JCL & VSAM 1 Thu Feb 04, 2016 9:48 am
No new posts XML generated from cobol is displayin... vangeti COBOL Programming 2 Wed Aug 19, 2015 5:16 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us