On Wed, 13 Jun 2007 08:38:52 -0500, McKown, John wrote:
>>
>> You can, of course, pass the required symbols as parm to the program:
>> //PGM EXEC PMG=PROG1,PARM='SYMBOL1=&SYMBOL1,SYMBOL2=&SYMBOL2,...."'
>> Kees.
>
>Very true. But I got the idea that the original person may have wanted
>to write a subroutine or something to find out which "variables" have
>been "set" and their associated "value". He didn't really say. The other
>problem could be that old 100 character limit on the length of a PARM.
>
Ah, but Ed G. is arguing at this moment in another forum that 100
is not widely perceived as a serious restriction and should be
preserved for safety. Notwithstanding the 3 consecutive mentions
of it in this thread.
>Like passing a UNIX file name into something. UNIX file names can be up
>to 255 characters in length, assuming that I am remembering correctly.
>
From:
#14.5 "z/OS V1R7.0 UNIX System Services User's Guide"
______________________________________________________________
14.5 Path and pathname
A pathname can be up to 1023 characters long, including all
directory names, filenames, and separating slashes.
I don't know why JCL imposes a harsher limit. Just doing JCL's
thing, I guess. Likewise, I don't see why DYNALLOC imposes a
harsher limit, since I see in IEFZB4D0:
S99TULNG DS XL2 LENGH OF 1ST (OR ONLY) PARAMETER
which would easily accommodate a pathname lengh of 1023 characters.
-- 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
