Relating this back to the OP's question, it seems to me that this approach might work:
- A Unix process could be writing output to a named pipe. - A CICS task could use BPX1SEL (select) and BPX1RED to read from the pipe. - A CICS wait can be used with BPX1SEL's ECB to prevent blocking. Kirk Wolf Dovetailed Technologies http://dovetail.com On Thu, Jan 28, 2010 at 3:39 PM, Binyamin Dissen <bdis...@dissensoftware.com> wrote: > On Thu, 28 Jan 2010 08:58:24 -0600 Paul Gilmartin <paulgboul...@aim.com> > wrote: > > :>My naive understanding of the OS/360 multiprocessing > :>paradigm is that when one unit of work WAITs, another > :>is dispatched. How does CICS manage to subvert this? > :>Why was it ever allowed? > > :>What happens when a CICS transaction must do something > :>like: > > :> Invalid PIN number; please re-enter > > :>??? Does that spawn a separate transaction? > > One issues a CICS wait. With an ECB. That returns control to the CICS > dispatcher. > > -- > Binyamin Dissen <bdis...@dissensoftware.com> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
