In a recent note, "Shmuel Metz (Seymour J.)" said:
> Date: Thu, 11 May 2006 10:27:17 -0300
>
> >o Provide explicit assertion of default values for all
> > keyword options, such as "TYPRUN=NORMAL", or even
> > simply "TYPRUN=".
>
> That's in there.
>
I stand corrected by experiment. z/OS 1.5 cheerfully accepted
and ran a job containing "TYPRUN=".
... contrary to RTFM:
Title: z/OS V1R5.0 MVS JCL Reference
Document Number: SA22-7597-07
20.27.1 Syntax
TYPRUN= {COPY }
{HOLD }
{JCLHOLD}
{SCAN }
... and:
4.1 Notation Used to Show Syntax
{ } (braces)
Braces surround *required*, related items and
indicate that you must code one of the
enclosed items. Never code { or } on a
control statement.
Don't believe everything you read. Have I overlooked a
general statement about nullifying parameters? It would
seem not, since I do find the caution:
5.4.2.1 Defining and Nullifying JCL Symbols
* Do not nullify JCL symbols that appear on JCL keywords that
do not accept NULL values. The syntax descriptions of the
individual keywords specify whether the keywords allow NULL
values.
... and the description of TYPRUN quoted above does not admit a
null value.
RCF coming.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
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
