On Sat, 18 Oct 2008 09:26:14 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>On Fri, 17 Oct 2008 10:55:04 -0500, Chase, John wrote: <snip> >Of course. But why does supplying one null positional subparameter, >"SYSOUT=()", still constitute a null override, while supplying two >null positional subparameters, "SYSOUT=(,)", asserts the SYSOUT >parameter? Are there any other JCL keywords with similar behavior? > >And this provokes a further question. Suppose I'm overriding a DD >SYSOUT statement in a PROC which specifies both class and writer. >I might variously want to do each of the following. How can I: > >o Nullify class and leave writer unchanged? > >o Nullify writer and leave class unchanged? > >o Nullify both class and writer? > >(It's plausible that a PROC might have "//SYSUT2 DD SYSOUT=(B,INTRDR)", >but for testing I'd want not to submit a job, but keep the SYSOUT in >the spool and browse with SDSF, for example. How do I nullify INTRDR?) > >Or is it simply impossible to nullify positional subparameters? > >-- gil > Use a JCL PROC symbolic to override SYSOUT sub-parameter(s); for an STC, you can enter the START command with your desired symbolic value(s). Also, regarding the treatment of null parameter values, I don't know why but the EXPDT= parameter cannot be specified as a null value -- a JCL error occurs with the message: nnn IEF646I REQUIRED POSITIONAL PARAMETER MISSING IN THE EXPDT SUBPARAMETER OF THE LABEL FIELD Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- 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
