On Wed, Nov 24, 2004 at 05:15:16PM -0500, Peter E. Abresch Jr. - at Pepco wrote: > Yes, QDIO and hipersockets (iQDIO) require VTAM which is part of z/OS's > Communication Server.
To expand on this slightly... For several releases of Comms Server (since about OS/390 2.5, ISTR) VTAM has done all communications I/O on behalf of TCP/IP[1]. For TCP/IP device types that were in existence at the time, the change was done so that TCP/IP device definitions in VTAM were dynamically handled by VTAM "under the covers" and transparently to sysprogs. For the new device types, since it was a "clean slate", perhaps it was easier to have the sysprog do the VTAM work than code the automagics. :) Cheers, Vic Cross [1] With the introduction of Enterprise Extender (HPR over IP) at around OS/390 2.8, there was a neat circular dependency created: TCP/IP had to start after VTAM for TCP/IP devices and links to initialise properly, but TCP/IP had to be up before VTAM for the VTAM EE devices to start properly at VTAM startup... It's all fixed now, though (TCP/IP was altered so that it could start before VTAM, and delay its device starts until VTAM was up). ---------------------------------------------------------------------- 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
