I suspect that this log printer is similar to what IMS used to require, which was considered important for purposes of operation and recovery. (As I recall it, IMS wouldn't even shut down properly unless it could write (and get an ACK) that its final shutdown/checkpoint message was written to this printer).
If this is the case, your current setup seems inadequate to me. I don't know ALCS (at all), but if this logging information is critical to its operation, then I would see if there is a way (an exit?) that would allow you to route to a z/OS logstream. On Fri, Nov 19, 2010 at 3:23 PM, Dana Mitchell <[email protected]> wrote: > On Fri, 19 Nov 2010 15:56:23 -0500, Tony Harminc <[email protected]> > wrote: > > >Wow! How 1980s. > > Unfortunately yes... > > >Is it a requirement that the data end up on this PC? > > Yes, a network directory. we could send the files there via other means > but > some users need to look at the current file real-time. > > >Now, um, this ALCS... Is this the "TPF under MVS" thing? > > Yes exactly > > >Does it not have its own printer exits and such where you could capture > print > >data and redirect it? > > We are looking into that also > > > thanks > Dana > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
