On Tue, 26 Mar 2013 08:51:48 -0400, Bill Ashton wrote:
>
>..., I would like to use a set statement or a PARM= symbolic to
>generate the name of the load module for my LKED step. So I would like to
>have:
>
>SET EXEPGM=MYPGM
>. . .
>//GENER8 EXEC PGM=?????,PARM=' NAME &EXEPGM(R)'
>
From:
Title: z/OS V1R13.0 MVS Program Management: User's Guide and Reference
Document Number: SA22-7643-11
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2b1b0/3.1.3.1
o A member name can be specified on the SYSLMOD DD statement. ...
Does that not do what you need?
On Tue, 26 Mar 2013 08:12:01 -0500, John Gilmore wrote:
>What you want to do would be easy enough to implement using the internal
>reader (INTRDR)
>
>GIYF.
>
Or not. First hit:
http://www.mainframegurukul.com/ibmmainframeforums/Submit-a-JCL-thru-Cobol-sysout-INTRDR-post37.html
o Posted: Tue May 30, 2006 2:46 pm Post subject: Code for submitting jcl
thru cobol Reply with quote
Hi,
...
After writing cobol program. In JCL give dd1 as below.
//dd1 dd sysout=(INTRDR,*)
Syntax?
o Posted: Thu Jun 29, 2006 4:01 pm Post subject: Reply with quote
Please do NOT do this.
It is bad for so many reasons, change control, audit, Operastions
management, job re-runs...
Can't think of any reason why this is a good idea. In fact have worked at
places where doing this would get you fired.
If you don't have a job scheduler - which is the preffered method then just
jobchain to the previous step by putting a Gener to the interal reader as the
last step. ...
It's not clear that writing to INTRDR with IEBGENER is any safer
than writing with a COBOL program. But he does continue with:
//SYSUT1 DD DSN=DXX.XXXX.XXXX.JCLLIB(AUTO),DISP=SHR
... presumably using a catalogued data set provides the change control
he mentions. But the COBOL program could equally be change controlled.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
