On Thu, 24 Sep 2020 10:47:37 -0500, Hobart Spitz wrote:
>They find each other via the name of the pipe.
>
Is there an authority administering names of pipes, lest two
users inadvertently choose the same one? Embedding &SYSUID
in that name could resolve this. RACF? Even so:
//SORTIN DD DSN=INPUT.PIPE,SUBSYS=PIPE, 04
// DCB=(LRECL=60,RECFM=FB,BLKSIZE=32760) 05
INPUT.PIPE seems too generic. And must a user intending to submit
multiple job streams concurrently take care to modify those names to
avoid conflicts?
Some of the same concerns apply to POSIX named pipes, mitigated
somewhat by creating the FIFO in the user's $HOME.
Does this example achieve anything that couldn't be as well done with
POSIX FIFOs in the absence of BatchPipes?
Suppose the programmer wants to include customary Pipeline
stages such as SPECS in the pipeline network. Where would those
be coded?
>On Wed, Sep 23, 2020 at 2:19 PM Martin Packer wrote:
>
>> The pipe name is a data set name.
>>
Could DISP=OLD be used to guarantee serialization?
>> ...
>> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.icea100/ice2ca_Example_11._Sort_with_Pipes_and_OUTFIL_SPLIT.htm
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
