Folks, thanks for you advise on this one...

--- On Mon, 8/4/08, Paul Gilmartin <[EMAIL PROTECTED]> wrote:

> From: Paul Gilmartin <[EMAIL PROTECTED]>
> Subject: Re: INLINE JCL PROC Question
> To: [email protected]
> Date: Monday, August 4, 2008, 6:31 PM
> On Mon, 4 Aug 2008 16:31:18 -0500, Mark Zelden wrote:
> 
> >>--- On Mon, 8/4/08, Howard Rifkind wrote:
> >>>
> >>> //SYSIN    DD 
> SYSOUT=(,),OUTPUT=(*.OUT1,*.STD)
> >>>
> That's kinda scary.  But I've occasionally
> allocated
> a temp DS to SYSIN; EXECIO DISKW to it; then used as
> input to the next command.
> 
> >You can't execute an "inline" / instream
> CLIST / REXX exec from SYSPROC
> >or SYSEXEC.  However, you can (and I do) execute it
> from a temp PDS by
> >adding a prior step that copies the source to the temp
> PDS.   Two examples
> >on my website are RACFUDEL and LOGRREXX.  URL below...
> >
> I have sometimes cut this down to a single step by starting
> the
> SYSTSIN with a REPRO.  Has anyone ever submitted a
> Requirement
> for support of instream data in PROCs?  Or for instream
> Rexx/
> CLIST source?
> 
> >Mark's MVS Utilities:
> http://home.flash.net/~mzelden/mvsutil.html
> 
> BTW, did I lately notice by accident that PEND is now
> optional
> in library JCL PROCs (used to be forbidden)?  This would be
> a
> major courtesy to customers who want to alternate between
> INCLUDE
> and EXEC of the same member.  (Ah!  I RTFM.  Optional now. 
> I
> suppose someone will complain about the change.)
> 
> -- gil
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access
> instructions,
> send email to [EMAIL PROTECTED] with the message: GET
> IBM-MAIN INFO
> Search the archives at
> http://bama.ua.edu/archives/ibm-main.html


      

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to