IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Processing Only Part of a Job Stream


IBM Mainframe Forums -> TSO/ISPF
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Charles Wolters

New User


Joined: 30 Mar 2011
Posts: 48
Location: United States

PostPosted: Wed Aug 29, 2012 12:12 am
Reply with quote

I am going to post this question in the TSO/ISPF but since it also involves SAS I will understand if a moderator tells me to move it but I think my question relates to other applications.

My job starts with the JCL statements and then after the //SYSIN DD * statement I have about two thousand lines of SAS code. When the researchers look at the output from the first 1000 lines of code they may not have interest in looking at any output or listings generated by the last 1000 lines of code. I don't want to delete this code because the researchers may decide to change the criteria of whom to include in the analysis or the analytic data sets may get updated at some point.

My question is whether there is a TSO command that allows you to tell the processor to only consider the first X lines of code and ignore the rest. In looking at the TSO documentation I had noticed the END operand for the SUBMIT command and I wanted to know if this was appropriate to my problem. I know that I can wrap the code I don't want processed in a SAS macro (this may be the most efficient way?) but wanted to explore options using TSO/ISPF.
CW


Charles Wolters
Back to top
View user's profile Send private message
prino

Senior Member


Joined: 07 Feb 2009
Posts: 1306
Location: Vilnius, Lithuania

PostPosted: Wed Aug 29, 2012 12:18 am
Reply with quote

VIEW the job to be submitted and add a label (let's say .LAST) to the last line to be submitted, then do

Code:
SUB .ZF .LAST


or just add

Code:
//


after the last line to be submitted
Back to top
View user's profile Send private message
Charles Wolters

New User


Joined: 30 Mar 2011
Posts: 48
Location: United States

PostPosted: Wed Aug 29, 2012 12:26 am
Reply with quote

Prino,

So you can do that! Intuitively I had thought that would be the natural approach for the TSO developers to come up with but I could not find any reference to it in any of the TSO documentation I looked at. If it is not a struggle for you maybe you could point me to a reference. Thanks for your quick reply.

CW
Back to top
View user's profile Send private message
prino

Senior Member


Joined: 07 Feb 2009
Posts: 1306
Location: Vilnius, Lithuania

PostPosted: Wed Aug 29, 2012 12:35 am
Reply with quote

From the ISPF Tutorial:

Code:
TUTORIAL ------------------ EDIT - 'SUBMIT' COMMAND ------------------ TUTORIAL
COMMAND ===>                                                                   
                                                                               
  The SUBMIT command (may be abbreviated SUB ) is used to submit a job         
  stream.                                                                     
                                                                               
        Command ===> submit              submits the data being edited.       
                                                                               
  The SUBMIT command is used to submit one or more jobs.  The data that is     
  being edited is stored in a temporary data set, and the TSO SUBMIT           
  command is invoked.  The same requirements that exist when using the TSO     
  SUBMIT command directly apply to the edit SUBMIT command.                   
                                                                               
  An optional "range" operand is supported.  You can specify the labels of     
  the first and last lines of the data to be submitted as a job stream.       
                                                                               
  The first line of the data stream that is submitted is logged in the         
  ISPF log file to identify the job being submitted.                           
                                                                               
  Note: Data with a logical record length (LRECL) greater than 80 is           
  truncated to 80 bytes before being passed to the TSO SUBMIT command.         
  Data with a logical record length less than 80 is padded with blanks         
  before being passed to the TSO SUBMIT command.                               
Back to top
View user's profile Send private message
Charles Wolters

New User


Joined: 30 Mar 2011
Posts: 48
Location: United States

PostPosted: Wed Aug 29, 2012 12:47 am
Reply with quote

Prino,

Yep, there it is and it could not be any clearer. This forum is like (to quote George Bush) a thousand points of light and without it I would have been stumbling around for a few days. Thanks again.

CW
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> TSO/ISPF

 


Similar Topics
Topic Forum Replies
No new posts icetool empty file and not empty file... DFSORT/ICETOOL 5
No new posts JCL (SET) variables in input stream data JCL & VSAM 0
No new posts Extract part of data from file and wr... DFSORT/ICETOOL 9
No new posts CICS file processing using applicatio... CICS 3
No new posts Retrieving IMS message processing reg... CLIST & REXX 7
Search our Forums:

Back to Top