The following list describes statements in the IMSGEN entry:
Defines logical statement that gathers together terminals with similar characteristics. This product looks to IMS as an SLU TYPE 2.
IMS does not verify the VTAM bind image against its own definition tables and will not reject an inconsistent bind. If the virtual terminals are defined as TYPE=3277, IMS assumes an LU type of 0 even when an LU type 2 bind is received. IMS will bind with an LU type of 2, but will assume an LU type of 0 internally, which causes many problems. Therefore, the IMS CA TPX virtual terminals must be defined as TYPE=SLUTYPE2.
Defines each terminal. The n is the IMS model number (01 through 15). Only models 1-8 are supported.
You must specify the correct value in the SIZE parameter for the TYPE that you specify here, but any model of terminal will work if TYPE = 3270A2 and SIZE = 24,80. For more information, see the Size parameter below.
IMS requires non-SNA terminals to have an OUTBUFF value greater than the largest message expected to be sent to the terminal. This is because the LU0 bind image has no MAXRU facility and cannot use chaining. This is not true for LU2, which segments the message according to the BIND MAXRU size. For CA TPX, the BIND MAXRU size is 2 KB, so an OUTBUFF value of 2048 is recommended. The use of LU2 saves valuable IMS virtual storage.
Defaults to (PFK,CARD,PEN), but it is not important to specify them.
Use the value you would normally use when defining an LU type 2 terminal (TRANRESP, FORCRESP, or NORESP).
For BSC 3270 or local non-SNA devices, it is not possible to specify a COPY facility in the IMSGEN. However, for LU2 devices, coding COPY or NOCOPY in the TERMINAL macro will affect the way PF12 is handled by IMS. The default value is COPY, which will cause IMS to intercept PF12. The PF12 will not be passed to the application unless NOCOPY is specified.
OPNDST has no effect because CA TPX cannot accept SIMLOGON requests. NOPNDST prevents an operator who issues the /OPNDST command from acquiring the terminal.
After you set screen SIZE for a certain TYPE, you do not have to specify the SIZE parameter for subsequent references to that type. However, you may want to specify the SIZE parameter in each TERMINAL statement anyway. After a SIZE has been set for a given TYPE, it must be used consistently for the rest of the IMSGEN.
The following values are taken from the IMS Installation Guide. Note that a model 5 terminal is 3270A7 and not 3270A5:
Immediately follows the TERMINAL statement and defines the internal IMS name that is to be associated with the terminal (LTERM or logical terminal name). This name is also the one seen by IMS applications.
In IMS, terminals are known by two names: the PTERM (Physical Terminal) and the LTERM (Logical Terminal). The PTERM name for VTAM terminals is the equivalent of the VTAM LU name. In CA TPX terms, the PTERM is also the virtual terminal ACB name.
Each PTERM has one or more LTERMs associated with it. You use the IMSGEN NAME statement to associate LTERMs with PTERMs. You can also reassign LTERMS from one PTERM to another using the /ASSIGN command.
For an illustration of how a user of the real terminal REALABCD might be using the virtual terminal VIRTPTRM to access IMS, see Representation of Real Terminal to IMS in this chapter. IMS sees the virtual terminal VIRTPTRM as IMS PTERM VIRTPTRM. The IMSGEN NAME statement is used to associate LTERM VIRTLTRM with PTERM VIRTPTRM.
|
Copyright © 2013 CA.
All rights reserved.
|
|