On Thu, 23 Feb 2017 22:12:00 -0400, Clark Morris wrote:
>
Just read carefully. JCL Ref.; EXEC Statement; PARMDD paramter says ...
>The knowledge center says the processing strips out blanks and
>sequence numbers. I am not certain as to where a sequence number
>would be in format V or VB data sets or Unix files. ...
>
Data set requirements
z/OS UNIX System Services files also provide the appearance of
a physical sequential (PS) data set and are supported.
Record length requirements
... Fixed record length data sets and in-stream data sets are examined to
determine if their records contain sequence numbers.
This would seem to include RECFM=V in-stream data sets. But is an RCF
in order?
If sequence numbers exist, they are assumed to consist of eight contiguous
numeric characters
occupying the last eight bytes of the input record.
Including the last eight characters of each record of RECFM=V in-stream data
sets?
Parameter string requirements
The parameter string that is passed to the job step program is formed by a
simple concatenation
of each input record, up to a maximum of 32760 bytes. Blank records and
trailing blanks on each
record are ignored during the concatenation process.
Note that says *trailing* blanks, not leading nor interior blanks.
>that goes into excruciating detail as to how this works? The JCL
>reference doesn't. You can use symbols and system symbols if the parm
>data is instream. I agree with your example and suspect the only way
>to tell for sure is to run tests which I can't do without a system.
>
There are other rules, described elsewhere, about stretching or compressing
sequences of blanks during symbol substitution.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
