David, Thank you for you opinion, totally agree. The STC is a tad heavy on I/O , it does provisioning and I would like to less the I/O ..
Scott On Tue, Feb 14, 2017 at 8:38 AM David Crayford <[email protected]> wrote: > You can roll your own stream capability into an API simply by buffering. > > Change your assembler routines to buffer and return segmented results. > > > > I'm not sure I understand what you want to do. I would use pipes if > > there were two address spaces communicating with each other in a > > uni-directional way. I would use Unix domain sockets for bi-directional > > communications. I would use type=memory only with > > type=memory(hiperspace) when I want to use lots of memory in a 31-bit > > program. > > > > > > On 13/02/2017 11:01 PM, scott Ford wrote: > > > All: > > > > > > I have the following: > > > > > > 1. Cobol STC > > > 2. It calls an Assembler subroutine with does a RACF extract of the > > > database for all > > > userids and then writes to an output file. > > > 3. Is it possible to have the Assembler routine place the extracted data > > > into a unix > > > pipe or a C type=memory file and then i can retrieve it ? > > > > > > Or is that to Mickey Mouse ..?? > > > > > > Scott > > > IDMWORKS > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > -- Scott Ford IDMWORKS z/OS Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
