On May 23, 2005, at 9:33 AM, Vernooy, C.P. - SPLXM wrote:
"Joe Zitzelberger" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
On May 23, 2005, at 6:57 AM, Peter Hunkeler wrote:
All I'm saying is that it takes two objects to create this error.
Your
production program must do things incorrectly today AND your
production
JCL must change. If it works today, then only a change to one of
these
two (hopefully) controlled objects can break it.
Unless you just let your production JCL be changed willy-nilly you are
at no risk of exposure.
You don't have to change the JCL to change the PARM if it is specified
by
the operator on the Start-command, or is built from symbolics.
S TOOL,PARM='A NUMBER OF COMMANDS AND PARAMETER GIVEN TO THE TOOL'
//T EXEC PGM=TOOL,PARM='&VALUE1,&VALUE2,&VALUE3'
I thought one of the concurrent complaints about start was that it
currently only accepts 61-chars. I might have misunderstood that.
But you cannot change you symbolics without a change to the JCL stream,
be it a SET statement in an INCLUDE member or a whatever. If you have
exits that might import other symbols you might get something variable
length, but for standard IBM JCL the final lengths are all know at the
time the JCL is written.
[EMAIL PROTECTED]
Q: How many Marxist revolutionaries does it take to change a
proletarian lightbulb?
A: None.� A proletarian lightbulb contains the seeds of its own
revolution.
----------------------------------------------------------------------
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
