SAS(R) 9.1.3 Companion for z/OS

Using SAS Data Libraries Pipe Libraries (Experimental) 51
3 SAS does not support a mode of operation in which there are multiple readers or
multiple writers for a pipe library. For example, using two different jobs to
simultaneously write to a pipe that is being read by another SAS job would lead to
errors and/or incorrect results.
3 It is important to monitor and verify that pipe-related jobs are running as
expected. Under normal circumstances, the receiving SAS DATA step or procedure
will read all the member pages sent by the sending SAS DATA step or procedure.
After sending the last member page, the sending step or procedure will close the
pipe library, and the receiving step or procedure will receive an end-of-file
indication after reading the last member page. However, if the receiving step or
procedure encounters an error condition (such as out-of-space on a library or
external file to which it is copying the member data), the receiving step or
procedure will close the pipe library before it has read all the member pages that
the sending step or procedure has sent (or will send). To avoid the sending job
suspending indefinitely in this case, specify the option ERC=DUMMY on the
SUBSYS parameter of the DD statement for the sending job. If the receiving step
or procedure closes the pipe library prematurely, the ERC=DUMMY option will
cause the sending stepor procedure to continue processing. In this case, the
member pages will be discarded instead of sent to the receiving job.
Allocating a SAS Data Library to a Pipe
3 Externally assign the pipe library using a JCL DD statement. On this DD
statement, use the SUBSYS parameter to specify the name of the BatchPipes
subsystem that will be managing the pipe. Within the SAS job, refer to this pipe
library using the DDNAME specified as the libref. Specify the DSN parameter on
the DD statement using a data set name that conforms to the standards for your
installation.
3 Distinguish between the sending and receiving sides of the pipe library using the
LABEL parameter of the DD statement. On the DD statement for the pipe library,
specify LABEL=(,,,OUT) if SAS will be sending SAS data sets to the pipe library.
Specify LABEL=(,,,IN) if SAS will be reading SAS data sets from the pipe library.
3 The DCB attributes for a pipe library vary from those used for other sequential
access bound libraries. Specify DSORG=PS, RECFM=F for both the sending and
receiving sides of the pipe library. Specify an LRECL between 1024 and 32760 for
the pipe library. The values specified for LRECL in the sending and receiving
sides of the pipe library must match exactly.
3 Identify, if necessary, the engine to be used for processing the pipe library. By
default, SAS will use the value of the SEQENGINE option to determine the engine
to use for processing the pipe library. If this value is appropriate and set
identically for both the sending and receiving jobs, it is not necessary to explicitly
identify the engine. To explicitly use another engine, specify a LIBNAME
statement with the libref and engine and no other parameters.
3 No other DD statement parameters other than those described in this section
should be specified unless explicitly described in the IBM documentation.