|
|
|
|
|
|
|
If your network is managed by the OpenView DTC Manager, and at least one of the DTCs on the LAN are equipped with a Telnet Access Card, the programs you write may be used to control devices connected to the DTC via a Telnet connection to an HP 9000 or other ARPA machine. Collectively, these devices are called DTC Telnet devices. The Telnet Access Card receives asynchronous character streams over the LAN from an ARPA machine. This section includes information on:
DTC Telnet access is provided to MPE/iX networks through a Telnet Access Card mounted in the DTC or with the Telnet Express Box. An access card takes the place of a terminal connect card in one of the DTC slots for DTC 48 and DTC 72MX (the Telnet card cannot be in slot 0 for DTC 48). The Telnet card cannot coexist with an X.25 Network Access Card in the DTC 48. See DTC Planning Guide for more information on the DTC hardware. Both the DTC and the MPE/iX system accessing it must be connected to a LAN. There must also be a network management workstation on the LAN running the OpenView DTC Manager software that controls all DTC network operations. MPE/iX host names and IP addresses that can use the DTC Telnet support facility is configured through the OpenView DTC Manager. DTC Telnet support information for each MPE/iX host system must be supplied via the NMMGR configuration software. Also, you must configure a sufficient number of non-nailed TIO ports. DTC Telnet support for the network is configured using both the OpenView DTC Manager software on the network management workstation and the NMMGR configuration software on the host. DTC Telnet support parameters for each MPE/iX host system that will allow device connections via DTC Telnet must be defined in the NMMGR configuration, along with the device profiles to be associated with DTC Telnet devices. DTC Telnet devices must be configured as non-nailed TIO terminals. The terminal type for these terminals must be set at 10 or 18. For more information on configuration see both Configuring Systems for Terminals, Printers, and Other Serial Devices and Using the OpenView DTC Manager. Some basic limitations apply to the way transmission occurs and to the operations that are supported over DTC Telnet connections:
Most file system intrinsics can be used to control devices connected to DTC Telnet as if the devices were locally connected. Both the FCONTROL and FDEVICECONTROL intrinsics are supported for DTC Telnet device control. In most cases the device control calls work as they would with non Telnet connections. There are, however, a number of differences in the way device control functions operate over DTC Telnet connections. The individual differences in the operation of each FCONTROL and FDEVICECONTROL call are documented in the Intrinsics Reference chapter of this manual. The following summary is provided here for your convenience. Some FCONTROLs are ignored by DTC Telnet. These are calls that attempt to control some function that is not supported over DTC Telnet, such as changing terminal speed or setting parity. These calls will return a CCE condition code, but no device control action will take place. Any values returned in these calls may not be a true reflection of device control settings. These FCONTROLs include:
Reads following a call to FCONTROL(27), which enables binary mode, return a CCL condition code with the file system error FSERR20 (INVALID OPERATION). All subsequent reads will return an error, until binary mode is disabled (FCONTROL(26)). Calls to FCONTROL(37), to set both terminal type and speed, will change the terminal type setting, but will have no impact on how the device actually operates. A CCE condition code will be returned. Some caution should be taken when using FCONTROL(4), which sets a timeout interval for a read. Keep in mind that some delays may be caused by the LAN over which the DTC Telnet is transmitting. In such cases you may want to add some time to the timeout value you would normally specify for the call. The FDEVICECONTROL intrinsic is also supported on MPE/iX systems with DTC Telnet connections. However, there are also several limitations on the device control operations they perform. The following FDEVICECONTROL parm1 values, with 192 specified as the controlcode, will return a CCE condition code but have no effect on the operation of the device or the transmission of data:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||
|
|
|
|||||||||
|
|||||||||
