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
 

 

/*ouput CAn it be coded to effect all sysout.

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

New User


Joined: 21 Jun 2006
Posts: 9

PostPosted: Mon Aug 03, 2009 3:28 pm    Post subject: /*ouput CAn it be coded to effect all sysout.
Reply with quote

Is it possible to code the /*output statment so that it effects all SYSOUT in the job, without having to amend the sysout statments themselves?
Back to top
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Aug 03, 2009 3:41 pm    Post subject:
Reply with quote

What does it say about DEFAULT in the manual, what happened when you tried it.
Back to top
View user's profile Send private message
mark loftus

New User


Joined: 21 Jun 2006
Posts: 9

PostPosted: Mon Aug 03, 2009 3:50 pm    Post subject:
Reply with quote

All i can see in the manuals is

/*OUTPUT code parameter[,parameter]...

code
Identifies the /*OUTPUT statement. The code is 1 through 4 alphanumeric characters. To refer to a /*OUTPUT statement, the DD statement SYSOUT parameter must specify this code in its code-name subparameter. The referenced /*OUTPUT statement specifies processing options for the sysout data set defined in the referencing DD statement.
A code of * indicates that this /*OUTPUT statement is a continuation of the previous /*OUTPUT statement.

This seems to indicate that you have to point each sysout statment back to the output statment.
My problem is im converting several thousand JCL members from JES3 to JES2 and want to do a like for like replacement of the JES3 //*Format card with the /*output card.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Aug 03, 2009 3:58 pm    Post subject:
Reply with quote

Are we talking
/* JES2 OUTPUT or
//name OUTPUT statement here.
Back to top
View user's profile Send private message
mark loftus

New User


Joined: 21 Jun 2006
Posts: 9

PostPosted: Mon Aug 03, 2009 4:11 pm    Post subject:
Reply with quote

JES2 /*output
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Aug 03, 2009 4:20 pm    Post subject:
Reply with quote

To be honest, I've not played with these for more years than I care to remember, but would guess that if the JES parameters are the same as they are on JES3 it should work just by changing the //* to /*

a) Can you try it and see what happens.
b) One of our sysprogs normally rises around this time, and he will probably offer you a lot more help than I can.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Mon Aug 03, 2009 4:57 pm    Post subject:
Reply with quote

I haven't done anything with JES2 in more years than I care to remember. However, the JCL Language Reference manual (link at the top of the page) explicitly recommends using the OUTPUT statement instead of /*OUTPUT due to increased flexibility. And the OUTPUT statement in the manual specifically states that using DEFAULT=YES allows implicit reference to the OUTPUT statement by SYSOUT statements.
Back to top
View user's profile Send private message
mark loftus

New User


Joined: 21 Jun 2006
Posts: 9

PostPosted: Wed Aug 05, 2009 6:02 pm    Post subject: Reply to: /*ouput CAn it be coded to effect all sysout.
Reply with quote

Thanks, that works a treat. icon_biggrin.gif
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Wed Aug 05, 2009 6:06 pm    Post subject:
Reply with quote

Great! Glad to hear it's working.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed Aug 05, 2009 6:08 pm    Post subject:
Reply with quote

Another satiisfied customer icon_biggrin.gif , and thank's for letting us know it went well.
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
No new posts Syncsort - Hard coded Value in output PORYES SYNCSORT 1 Thu Nov 03, 2016 9:23 am
No new posts Single COPY CICS TS datasets and when... Kyle Carroll CICS 2 Tue Oct 11, 2016 9:47 pm
No new posts $AJ behaviour when $PXEQ is in effect. vasanthz JCL & VSAM 2 Thu Feb 18, 2016 3:51 am
No new posts Find the total of this field in SYSOUT karz DFSORT/ICETOOL 3 Thu Nov 13, 2014 2:59 pm
No new posts Re-write queries to minimize the effe... Anil Khanna DB2 6 Mon Aug 04, 2014 1:49 pm


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