How about //ddname DD DISP=(NEW,DELETE,DELETE), // DCB=(DSORG=PS[only],RECFM=F/FA/FM/V/VA/VM/U?/UA?/UM?/[no B]),BLKSIZE=nnnnn), // PIPES=(PROGNAME,'100/32k byte parm to select or modify records', // ddname1,ddname2,...,ddnameN), and the OPEN (ddname,OUTPUT) loads the PIPES program in (sub)task memory) and sets up the PUT/WRITE to DDNAME to call the program instead? The close unloads the PIPES program in (subtask memory). VSAM writes accepted like a DSORG=PS? Any other parameters possible?
A pipes DDNAME can use a PIPES parameter for a subsequent program. Of course, ddnames can only be used by the EXEC PGM= or one of the pipes programs. And all pipes programs remain in memory until step end. In case of abend / restart the checkpoint is taken in EXEC PGM= and abandon updates / writes in any pipes program after the checkpoint. On Mon, Sep 20, 2021 at 9:12 PM Paul Gilmartin <[email protected]> wrote: > > On Mon, 20 Sep 2021 19:10:16 -0500, Mike Schwab wrote: > > >So, in a sense, instead of pipes, the programs could be modified so > >that instead of outputting a record, call the next program passing the > >record as input. > > > No. > Rather than requiring every utility to be modified in order to use the > capability, it should be provided at the access method level or lower, > transparent, so the top programs are oblivious to it. > > And there should be provision for inserting filters between a producer > and a consumer to convert incompatible data formats. > > And ... what am I thinking? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
