On Mon, 4 Aug 2008 18:06:56 -0500, William H. Blair wrote:
>
>The rules of continuation for the PARM field would ostensibly
>require that you specify it as follows (that is, the correct
>syntax for continuation would be):
>
> // PARM=('SH echo sftp -b /u/bpxbatch/mccheckftp',
> // 'fis-depot-test.ucdavis.edu |su -s bpxbtch')
>
>where each "piece" is enclosed in apostrophes, and all
>but the last piece is followed by a comma, and all of
>the pieces are enclosed in parentheses.
>
>However, doing so will cause a comma to be included in the
>actual PARM information that will be passed to the program.
>The JCL will work, and the long PARM will be passed to the
>program, but I suspect that the program will not accept the
>resulting embedded comma, or do something else undesirable.
>
>As a consequence, I don't think you will be able to
>specify this type and length of PARM field for this
>program via JCL.
>
This misconception is so prevalent that I wonder whether it
reflects a syntactic rule from days of yore. I know that's
what I was taught in my first brush with JCL decades ago,
and I never learned better until long pathnames in MVS-OE
impelled me to seek a better answer.
-- 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
