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

Selective execution of Steps in a JCL containing N no. of st


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 8:24 am
Reply with quote

Hi Scherrer

This question arises after going thru the manuals only. As there is no clear description abt that.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


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

PostPosted: Fri Jul 10, 2009 8:35 am
Reply with quote

Hello,

Is there some reason more than the IEBEDIT - "Copy Steps from Three Jobs" example is needed? It appears to be exactly what you want to do. . .

Maybe there is something i misunderstand?
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 8:43 am
Reply with quote

Yeah, actually the thing is that I need to execute some steps from different JCLs for testing (some 5 JCLs are there). The restriction is that I don't have to execute the complete JCLs.
- One way that automatically comes to mind is to copy the steps from different JCLs and merge them into a single one and then submit that JCL. But that is a simple and old wayout, and nothing new to learn.

- IEBEDIT helped in learning in things and in new ways too.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


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

PostPosted: Fri Jul 10, 2009 8:58 am
Reply with quote

Hello,

Quote:
But that is a simple and old wayout, and nothing new to learn.
IEBEDIT is also considered quite old. . .

It is largely there for backward compatibility - some places have used this for over 30 years icon_wink.gif
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 9:07 am
Reply with quote

ok! I was considering the process of copying the steps into a new single JCL.

But considering my problem, no solution is provided.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


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

PostPosted: Fri Jul 10, 2009 9:27 am
Reply with quote

Hello,

Quote:
But considering my problem, no solution is provided.
Sigh, What nonsense. . .

Quote:
Is there some reason more than the IEBEDIT - "Copy Steps from Three Jobs" example is needed? It appears to be exactly what you want to do. . .
Either use the example in the manual or explain why it will not work.
Back to top
View user's profile Send private message
Binop B

Active User


Joined: 18 Jun 2009
Posts: 407
Location: Nashville, TN

PostPosted: Fri Jul 10, 2009 10:44 am
Reply with quote

Hi Vivek,

I am guessing now your problem is that you are having multiple JCLs in different datasets or members of a PDS.

This should probably work...


Code:

//STEP002  EXEC PGM=IEBEDIT                     
//SYSUT1   DD DSN=HLQ.ANUJ.JCL(OUTREC1),DISP=SHR 
//              DD DSN=HLQ.ANUJ.JCL(OUTREC2),DISP=SHR 
//SYSUT2   DD SYSOUT=(*,INTRDR)                 
//SYSPRINT DD SYSOUT=*                           
//SYSIN    DD *                                 
  EDIT  START=JOBA,TYPE=EXCLUDE,STEPNAME=STEP1
  EDIT  START=JOBB,TYPE=INCLUDE,STEPNAME=STEPA
/* 


Please do correct me if my understanding is wrong
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 10:59 am
Reply with quote

Hi Binop,

You are aboslutely correct. But I had already resolved it the same way.

I got a couple of questions here:

1. Some explanation about START parameter. Why and What is its use?
2. If two JCLs contain the same STEPNAME, provided with different results. How are we going to differentiate between them. I hope, the answer to previous question might be the answer to this.
Back to top
View user's profile Send private message
Binop B

Active User


Joined: 18 Jun 2009
Posts: 407
Location: Nashville, TN

PostPosted: Fri Jul 10, 2009 11:47 am
Reply with quote

Hi..

sorry there Vivek... i dont have much knowledge regarding the START parameter. I am sure u will find necessary details in the Manuals... ( look for started tasks )....
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Jul 10, 2009 11:51 am
Reply with quote

Binop B
Quote:
( look for started tasks )....

What have started tasks got to do with IEBEDIT ???

VivekKhanna
Have you tried anything for yourself rather than just waiting for the answer to be posted ???
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 11:55 am
Reply with quote

hi Expat,

I had tried this thing, and not able to understand the START parameter. Whatz the use of it. I simply require some info regarding the START parameter, so that I could have a the complete understanding of the code.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Jul 10, 2009 11:59 am
Reply with quote

Have you read what it says in the manual
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 12:17 pm
Reply with quote

As per the manuals:
START=jobname
specifies the name of the input job to which the EDIT statement applies. (Each EDIT statement must apply to a separate job.) If START is specified without TYPE and STEPNAME, the JOB statement and all job steps for the specified job are included in the output.


To be more precise:
1. Does the START statement auto-submits the job?
2. If not, then what is its use?
3. As per the definition, it specifies the name of the input job, to which the EDIT statement applies, but if we are already specifying the PS/PDS mem ber name containg the job, there will be no use of using the START parameter. Please let me know, if my understanding is correct.

With Binop's code, I had one more question:

1. What-if the two PDS specified in the SYSUT1 contains a member with same and performing different tasks.
2. In this case, how are we going to differentiate between them.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Jul 10, 2009 12:47 pm
Reply with quote

Where in the manual does it say that START will auto submit jobs. Jobs could be auto submitted if you wanted them to be, with or without the START parameter, you just need to code your JCL accordingly.

If you had read the manual properly, you would know how the START parameter is used correctly. In particular see the description of SYSUT1.
Back to top
View user's profile Send private message
VivekKhanna

New User


Joined: 09 Feb 2009
Posts: 57
Location: India

PostPosted: Fri Jul 10, 2009 1:05 pm
Reply with quote

yeah, I tried that without START parameter. It worked, but you will need to have specify the SYSOUT=(*,INTRDR) only then the mentioned step is getting executed. I tried with SYSOUT=*, but it didn't worked.
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 -> JCL & VSAM Goto page 1, 2  Next

 


Similar Topics
Topic Forum Replies
No new posts Capturing Job Execution Information All Other Mainframe Topics 3
No new posts CA7 deleting files in steps after job... CA Products 4
No new posts Selective extract of multi-record-typ... SYNCSORT 4
No new posts Parallel Sysplex - subprogram execution CICS 7
No new posts Prod parallel execution on mainframe ... CICS 1
Search our Forums:

Back to Top