I had a *lot* of fun coding a SYSLOG server for VM (CMS) using Pipes. We don't make much use of it these days, but it was valuable to those who knew the traffic was there. Pipelines let us fan-in to one place and then fan-out based on content.
With the excellent TCP/IP support in Pipes, the implementation was wide open to legitmate non-mainframe clients. (Unlike the usual SYSLOG strategy where z/OS for example must resort to USS. A Pipelines based SYSLOG server is more courteous to Unixen by not requiring them to run CMS.) And the all-too-often missed point: CMS PIPELINES IS TSO PIPELINES. The same tool exists on MVS and VM. A delightful discovery was/is that many networked printers (HP to note) have SYSLOG built in. All that is needed is to identify a SYSLOG host (by address), which can come from DHCP/bootp. So while the operators are stuffing paper in your 3800, they can also attend to your DeskJet(s). [No offense to operators anywhere.] With Pipes, we could leverage NJE to provide non-IP pathways for the SYSLOG traffic. (Crossing firewalls safely.) I did a SHARE presentation on our VM SYSLOG (or it was mentioned in one discussing something else; I forget the extent of coverage). And there were two other VM/CMS SYSLOG implementations: Neale Ferguson did a port to OpenVM (POSIX), and Arty Ecock did one using REXX/Sockets. Both excellent packages, of course! -- R; ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
