Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Triggering JCL job from other job

1,856 views
Skip to first unread message

Malli

unread,
Apr 11, 2006, 9:20:09 PM4/11/06
to
Hello,

Can any one help me advicing about triggering one JCL from another
JCL....

thanks,malli

William M. Klein

unread,
Apr 11, 2006, 11:31:18 PM4/11/06
to
Write out the "new" JCL stream to the INTR.

--
Bill Klein
wmklein <at> ix.netcom.com
"Malli" <malli...@yahoo.com> wrote in message
news:1144804808.9...@v46g2000cwv.googlegroups.com...

docd...@panix.com

unread,
Apr 12, 2006, 3:14:03 AM4/12/06
to
In article <1144804808.9...@v46g2000cwv.googlegroups.com>,

Malli <malli...@yahoo.com> wrote:
>Hello,
>
>Can any one help me advicing about triggering one JCL from another
>JCL....

Ummmmm... this is usually the province, on an IBM mainframe, of something
called a PROCedure; are you familiar with such?

DD

Gerry Palmer

unread,
Apr 12, 2006, 9:43:20 PM4/12/06
to
On 11 Apr 2006 18:20:09 -0700, "Malli" <malli...@yahoo.com> wrote:

>Can any one help me advicing about triggering one JCL from another JCL....

Any of these will do the trick:

==> Use IEBGENER (or ICEGENER) to send it to the JES internal reader

//********************************************************************
//* SUBMIT A JOB TO JES INTERNAL READER FOR EXECUTION *
//********************************************************************
//SUBMIT EXEC PGM=IEBGENER
//SYSUT1 DD DISP=SHR,DSN=YOUR.JCL.PDS(NEXTJOB)
//SYSUT2 DD SYSOUT=(B,INTRDR) //SYSPRINT DD DUMMY //SYSIN DD
DUMMY //*

==> Run a "Batch TSO" job to execute the SUBMIT command

//********************************************************************
//* SUBMIT JOB(S) TO JES INTERNAL READER FOR EXECUTION *
//********************************************************************
//SUBMIT EXEC PGM=IKJEFT1A
//SYSTSPRT DD SYSOUT=* //SYSTSIN DD * SUBMIT
'YOUR.JCL.PDS(THISJOB)'
SUBMIT 'YOUR.JCL.PDS(THATJOB)'
/*
//*


==> FTP the JCL to JES

//*====================================================================
//* FTP - SUBMIT JOB TO JES INTERNAL READER
//*====================================================================
//SUBMIT EXEC PGM=FTP,PARM='(EXIT'
//SYSPRINT DD SYSOUT=* //OUTPUT DD SYSOUT=* //INPUT DD *
123.123.123.123
YourUserName
YourPassword
SITE FILETYPE JES
PUT 'YOUR.JCL.PDS(NEXTJOB)'
SITE FILETYPE=SEQ QUIT /*
//*


Gerry Palmer

unread,
Apr 12, 2006, 9:54:05 PM4/12/06
to
On Thu, 13 Apr 2006 01:43:20 GMT, Gerry Palmer <gpa...@pobox.com>
wrote:

>On 11 Apr 2006 18:20:09 -0700, "Malli" <malli...@yahoo.com> wrote:
>
>>Can any one help me advicing about triggering one JCL from another JCL....
>
>Any of these will do the trick:

I seem to have lost some line breaks... let's try it again.


==> Use IEBGENER (or ICEGENER) to send it to the JES internal reader

//********************************************************************
//* SUBMIT A JOB TO JES INTERNAL READER FOR EXECUTION *
//********************************************************************
//SUBMIT EXEC PGM=IEBGENER
//SYSUT1 DD DISP=SHR,DSN=YOUR.JCL.PDS(NEXTJOB)
//SYSUT2 DD SYSOUT=(B,INTRDR)
//SYSPRINT DD DUMMY
//SYSIN DD DUMMY
//*


==> Run a "Batch TSO" job to execute the SUBMIT command

//********************************************************************
//* SUBMIT JOB(S) TO JES INTERNAL READER FOR EXECUTION *
//********************************************************************
//SUBMIT EXEC PGM=IKJEFT1A
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
SUBMIT 'YOUR.JCL.PDS(THISJOB)'
SUBMIT 'YOUR.JCL.PDS(THATJOB)'
/*

==> FTP the JCL to JES

Arnold Trembley

unread,
Apr 13, 2006, 2:55:30 AM4/13/06
to
Malli wrote: > Hello, > Can any one help me advicing about triggering one JCL from another > JCL.... Apart from the useful suggestions for adding a jobstep to submit to the internal reader, this kind of thing is normally done outside of jobs using the job scheduling system. In CA7 (originally named UCC7) this was called triggering, as in job A "triggers" job B. In IBM's OPC (Operational Procedure Control?), now renamed TWX/OPC (Tivoli Workload Scheduler/OPC) the nomenclature is different. Job A is the "predecessor" to job B, or Job B is the "successor" to job A. Any single job might have multiple predecessors and/or multiple successors, depending on how you write your job schedule or plan. And that's not addressing the problem of restricting "mutually exclusive" jobs... With kindest regards, http://arnold.trembley.home.att.net/
0 new messages