> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin
>
> In a recent note, Chase, John said:
>
> > Date: Fri, 13 May 2005 08:05:55 -0500
> >
> > > -----Original Message-----
> > > From: IBM Mainframe Discussion List On Behalf Of Taddei, Cathy
> > >
> > > [ snip ]
> > > If a programmer wanted to receive a parm via DD, they could have
> > > done it already. One of the advantages of PARM= is that you can
> > > stick it in a proc, where DD * will not work.
> >
> > //A PROC
> > //.....
> > //SYSIN DD DDNAME=SYSIN
> > // PEND
> > //BB EXEC A
> > //.....
> > //BB.SYSIN DD *
> > ...
> > ...
> > /*
> >
> > Works here....
> >
> But not here:
>
> //A PROC OPT1=DEFAULT1,OPT2=DEFAULT2,OPT3=DEFAULT3
> //.....
> // PEND
> //BB EXEC A,OPT2='Overriding value 2'
> ...
> /*
>
> ... You'd require the programmer to reassert the default
> values of PARM options not overridden.
If that were true, none of my compile procs would work (they all work just
fine, structured exactly as your example).
-jc-
----------------------------------------------------------------------
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
