HP 3000 Manuals HP 3000 Manuals
PAD Terminal Profile (Host-Based) The PAD Terminal Profilescreen, as shown in Figure 7-8 is used to define the characteristics associated with a PAD terminal profile.Note that this screen is used for host-based management only. For PC-based management, you should use the regular PC-Based Terminal Profile screen shown in Figure 7-4 for PAD terminals.Figure 7-8. PAD Terminal Profile Screen (Host-Based) Fields Terminal type The terminal type being associated with the profile. The only valid terminal type for PAD terminal profiles is terminal type 24. Terminal ltype file A terminal type name file created with the Workstation Configurator utility (TTUTIL.PUB.SYS),to be associated with the profile instead of the system-supplied terminal type. Enter the fully qualified file name (filename.group.account). Refer to the Customizing Terminal and Printer Type Files with Workstation Configurator for more information on TTUTIL.PUB.SYS. Record width The number of characters for each record.For HP terminals, the record width is usually 80 (the width of the screen). Allow :HELLO logon? Specifies whether :HELLO logon will be accepted from the terminals. Reset HP terminalsl? Specifies whether or not the terminal will be reset after the DTC is powered on or after the connection is aborted or re-established (for HP terminals only). NLIO device? Specifies whether native language devices will be used. PAD test requested? Specifies whether the DTC will set and read several X.29 parametersat connection establishment time to determine the PAD's behavior. Send initial Specifies whether at connection establishment, the profile? PAD is set to default X.3 terminal parameter values. X.3 setting Specifies whether changes to X.3 parametersmay be requested? made after connection establishment. Forced data Specifies whether the Data Forwarding Parms #3 and forwarding? #4 will be allowed to change after connection establishment. If this field is N then data forwarding parms #3 and #4 can change if the port changes from a normal read to VPLUS mode or if an Alternate End of Record (AEOR) is set. If this field is Y then the data forwarding parms #3 and #4 setting established at connection time is always used. Data forwarding parm This setting tells the PAD when a packet must be #3 and #4 sent to the PDN. Parm #3 selects the set of characters that will signal the PAD to forward data to the PDN. Parm #4 sets the idle timer in 1/20 second increments. The idle timer will signal the PAD to forward data if the time between successive characters from the terminal exceeds the idle timer value. When the data forwarding parameter is 10 and a normal read is sent, parm #3 is 2 (data forwarding character is a carriage return) and parm #4 is 0 (no idle time set). In VPLUS mode, parm #4 is 10 (idle timeout is 1/2 sec). If the data forwarding parameter is 1 or 2, parm #4 is 1 (idle timeout is 1/20 sec) or parm #4 is 2 (idle timeout is 1/10 sec), respectively, and parm #3 is 0 (no data forwarding character). If the data forwarding parameter is 0, parm #3 is 127 (all characters are data forwarding) and parm #4 is 0 (no idle time set). The following four parameters will be ignored when a profile is configured for non-nailed devices: PAD test requested, send initial profile, X.3 setting requested, and data forwarding parm #3 and #4. For non-nailed devices, the first three parameters will be set to Y and the last parameter set to 0. The four parameters will also be ignored for connections made through public PADs because the connections are made to non-nailed ldevs. Device class names Device classesprovide a means of accessing devices associated with a profile. Each device class name is up to eight alphanumeric characters beginning with a letter. Up to 450 device class names may be used for a printer profile; the total number of supported, configured device classes defined in all profiles is 1000. Use the [Go To CLASSES] key to go to an Additional Device Class Names screen for entering additional device class names. __________________________________________________ NOTE If you are changing profile characteristics, you can see which ldevs and DTCs will be affected by the change by pressing the [Assoc Ldevs] function key on the profile screen corresponding to the profile you are changing. After pressing this key, you will see a list of all ldevs using this profile in the DTCs configured in DTS. __________________________________________________
![[]](../../pic3k/M015956/FFN353c50.gif)