On Sun, 12 Jan 2020 14:49:20 -0600, Al Ferguson wrote:
>
>Access to MVS Files from OMVS via "//‘your.filename.goes.here’” only works for
>some commands. Pre-Allocated DD’s are not available to the OMVS thread
>(usually). But you might try a stream … try
>
> [cat | cp] "//‘your.filename.goes.here’” | cksum
>
Almost. I'd use:
cp "//‘your.filename.goes.here’” /dev/fd1 | cksum
Depending on presence or absence of "-B" option this may miss
differences in record boundaries or conflate x'15' with record
bouldaries.
>I believe you can cat (copy to stdout) or cp (copy to stdout) using the
>"//‘your.filename.goes.here’” format. And then Pipe it to “cksum”. In this
>case I do not think you will see a major performance hit (as you are tossing
>out the copy anyway). Try both and pick the best performing one.
>
The Ref. does not list "cat" as supporting Classic data sets. It might by
happenstance work, but if it breaks you just get to keep both pieces.
BPXWUNIX can use allocated DDNAMEs as stdin, stdout, and stderr.
They will be treated as text, not binary.
How about IEBGENER with:
bpxwdyn( alloc dd(sysut1) dsn(...) ... )
bpxwdyn( alloc dd(sysut2) path(/dev/fd/1) filedata(record) ... )
to preserve record boundary awareness.
Can ICSF geneate a secure hash from a Classic data set and detect
record boundary differences?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
