On Sun, 19 Sep 2021 11:53:18 -0500, Hobart Spitz wrote:
> ...
>Concerning EXECIO:
> - Pipes can read from or write to either a DD or a dataset. z/OS EXECIO
> can only use a DD.
>
o Can that DD be allocated to a UNIX file, with FILEDATA any of BINARY, TEXT,
or RECORD?
o Is it savvy to files tagged with FILEDATA and/or CCSID?
o Does it restrict concurrent use of UNIX files as ISPF does?:
<https://www.ibm.com/docs/en/zos/2.1.0?topic=integrity-zos-unix-file-enqueue>
> ... - I would be glad to
> hear from someone knowledgeable that I'm wrong on this and that I missed
> some access method change that has made the concern unnecessary.
>
As I mentioned earlier, the SPFEDIT member ENQs with DISP=SHR
avoid the need to lock an entire PDS in order to update a single member:
<https://www.ibm.com/docs/en/zos/2.1.0?topic=integrity-member-name-enqueue>
> - Pipes lets you read member(s) through a DD and names(s) specified in
> the pipe stage or by feeding member names to certain stages.
> you must put the member name on the allocation. If you've ever read a
> large number of members from a PDS/E
>
Does this support mixed concatenations of PDS, PDSE and UNIX directories?
(It should. This is intrinsic to BPAM.) What happens if the UNIX files have
unlike tags?
Does Pipelines support the "other side" of DDNAMEs? I.e. can Pipelines
output connectors be associated with input DDs of Classic utilities such as
OLD and NEW of ISRSUPC, or SYSUT2 of an arbitrary Classic utility be
associated with a Pipeline input cnonector. I could do this with a Rube
Goldberg of SYSCALL PIPE, BPXWDYN, SYSCALL SPAWN, ...
It would be nice to have it in an opaque package.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
