On 11/14/2015 11:28 AM, [email protected] wrote: <SNIPPAGE>
Simple Example: Lets say for this discussion I want to transfer all I/O from a an applications SYSOUT DD with SUBSYS=xxxx to a 64Bit Memory Chunk. Once I have all my exits established, Each I/O from an application with the appropriate SUBSYS statement should be directed to my SubSystem Address Space. Do I understand this correctly ? . How does the subsystem address space receive/obtain the data from the Applications PUT/WRITE statement, so that the SubSystem Address Space can populate the 64Bit Memory Chunk ? .
<SNIPPAGE>
Your subsys will *not* get that I/O. Reason, SYSOUT is already using the subsys interface to communicate with JES* for spooled output (and I think for input "DATA" or "*").
And, if I remember correctly, this is an architectural limitation in the way this was implemented.
I ran into this some years ago when trying to automate something where I was trying to feed output to spool and the ao subsys simultaneously.
There was some astonishment on the support side at IBM that we had hit this particular problem -- because they had missed putting this restriction in the documentation.
I would have thought that the manual(s) involved have this "warning" or "NOTE" in them to state that this restriction prevents one from using SUBSYS with SYSOUT (or "DD [DATA|*],SUBSYS=..." ? ).
* JES being either JES2 or JES3, and depending on how you have things set up, it could even be a secondary JES2 environment.
HTH, Steve Thompson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
