>>-TERMINAL(name)--GROUP(groupname)--+-------------------+------> '-DESCRIPTION(text)-' .-AUTINSTMODEL(NO)-------------------------------------. >--+------------------------------------------------------+-----> '-+-AUTINSTMODEL(ONLY)-+--+--------------------------+-' '-AUTINSTMODEL(YES)--' '-AUTINSTNAME(autinstname)-' .-SOLICITED(NO)--. >--+-------------------+--+----------------+--------------------> '-CONSNAME(console)-' '-SOLICITED(YES)-' .-INSERVICE(YES)-. >--+----------------+--+------------+--+------------------+-----> '-INSERVICE(NO)--' +-NATLANG(E)-+ '-NETNAME(netname)-' '-NATLANG(K)-' >--+----------------+-------------------------------------------> '-POOL(poolname)-' >--+--------------------------------------------------------------------------------------------+--> | .-PRINTERCOPY(NO)--. | '-+------------------+--+------------------+--+--------------------------------------------+-' '-PRINTER(printer)-' '-PRINTERCOPY(YES)-' | .-ALTPRINTCOPY(NO)--. | '-ALTPRINTER(printer)--+-------------------+-' '-ALTPRINTCOPY(YES)-' >--+-----------------------+------------------------------------> '-REMOTESYSNET(netname)-' >--+---------------------------------------------------+--------> '-REMOTESYSTEM(connection)-+----------------------+-' '-REMOTENAME(terminal)-' .-TASKLIMIT(NO)-----. >--+----------------------------+--+-------------------+--------> '-SECURITYNAME(securityname)-' '-TASKLIMIT(number)-' .-TERMPRIORITY(0)--------. >--+------------------------+--+--------------------------+-----> '-TERMPRIORITY(priority)-' '-TRANSACTION(transaction)-' >--TYPETERM(typeterm)--+----------------+-----------------------> +-USERID(userid)-+ +-USERID(*EVERY)-+ '-USERID(*FIRST)-' >--| APPC attributes |----------------------------------------->< APPC attributes .-ATTACHSEC(LOCAL)------. .-BINDSECURITY(NO)--. |--+-----------------------+--+-------------------+-------------> +-ATTACHSEC(IDENTIFY)---+ '-BINDSECURITY(YES)-' +-ATTACHSEC(MIXIDPE)----+ +-ATTACHSEC(PERSISTENT)-+ '-ATTACHSEC(VERIFY)-----' .-USEDFLTUSER(NO)--. >--+--------------------+--+------------------+-----------------| '-MODENAME(modename)-' '-USEDFLTUSER(YES)-'
The printer you name must be owned by the same CICS system that owns this terminal definition.
If you want to specify the hardware COPY feature for the alternative printer, specify YES for ALTPRINTCOPY on this terminal definition.
As in previous releases, IDENTIFY implies a degree of trust between the two systems that allows this system to accept the sign-on logic of the other system. In effect, this is a distributed security manager, with one system doing the sign-on and the other doing the security check.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
You need specify this only if AUTINSTMODEL is YES or ONLY. You can let it default to the terminal name followed by four blanks, as long as this is acceptable to the autoinstall control program. For more information about autoinstall models, autoinstall names, and the autoinstall control program, see Autoinstall control program.
To define a TSO user as a console device, specify CONSNAME(name), where name is the TSO userid. This enables a TSO user authorized to use the TSO CONSOLE command to initiate CICS transactions. The TSO userid does not have to be defined in the CONSOLnn member of SYS1.PARMLIB member.
The equivalent of CONSOLE(00) is CONSNAME(INTERNAL) or CONSNAME(INSTREAM), depending on the service level of CICS and the release of MVS being used; specify this if you want to initiate a CICS transaction and issue a command to it in a JCL statement. For guidance about using JCL to issue CICS commands, see the CICS Operations and Utilities Guide.
Acceptable characters:
Any
lower case characters you enter are converted to upper case. |
The GROUP name can be up to eight characters in length. Lowercase characters are treated as uppercase characters. Do not use group names beginning with DFH, because these characters are reserved for use by CICS.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
For further guidance on the LOGMODE name, see the CICS Transaction Server for z/OS® Installation Guide.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
If you do not specify a name, the NETNAME defaults to the TERMINAL name.
The NETNAME must be unique except in the case of a remote terminal. That is, you cannot install two local terminals with the same NETNAME, or a local terminal and any connection with the same NETNAME. However, the NETNAME for a remote terminal can be the same as the NETNAME for any other terminal or the NETNAME for any connection.
If the CICS region supports VTAM dynamic LU alias (that is, LUAPFX=xx is specified on the CICS region's APPL statement), the terminal with this NETNAME is assumed to be in the same network as the CICS region. If the terminal is in another network, it must be defined to VTAM on a CDRSC definition with a predefined LUALIAS (LUALIAS=netname) to override VTAM dynamic allocation. In this case, netname on the LUALIAS parameter must match the NETNAME defined on this terminal resource definition.
When you define a 3600 pipeline logical unit, you generate a TCTTE that is associated with a pool of TCTTEs. A pool of pipeline TCTTEs can be used by one pipeline logical unit, or it can be shared by a number of pipeline logical units.
The pool name is used only as a method of identifying the related TERMINAL definitions on the CSD file. It is not used within the active CICS system. The name can be up to 8 characters in length.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
For a pipeline terminal, you must specify a TYPETERM with SESSIONTYPE(PIPELINE) specified. You must specify a TASKLIMIT on at least one of the pool of pipeline terminals. You must name the same group for each of the pipeline terminals in a pool.
DEFINE TERMINAL(ttt1) GROUP(g) POOL(poolid)
TYPETERM(xxxxxxxx) NETNAME(nnnnnnn1)...
DEFINE TERMINAL(ttt2) GROUP(g) POOL(poolid)
TYPETERM(xxxxxxxx) NETNAME(nnnnnnn2)...
DEFINE TERMINAL(ttt3) GROUP(g) POOL(poolid)
TYPETERM(xxxxxxxx) NETNAME(nnnnnnn3)...
DEFINE TERMINAL(ttt4) GROUP(g) POOL(poolid)
TASKLIMIT(nn) TYPETERM(xxxxxxxx)
NETNAME(nnnnnnn4)...
DEFINE TYPETERM(xxxxxxxx) GROUP(g)
DEVICE(3650) SESSIONTYPE(PIPELINE)
The printer you name must be owned by the same CICS system that owns this TERMINAL definition.
If you want to specify the hardware COPY feature, specify PRINTERCOPY(YES) on this TERMINAL definition.
Note that SNA character string (SCS) printers accept only 3790 data streams; they do not accept 3270 data streams. They therefore cannot be used to print the contents of a display unit's buffer.
If you use a program attention key (for example, PA1) to print the contents of the screen on an associated VTAM printer, the screen size of the printer is chosen according to the SCRNSIZE operand as defined in the CICS-supplied default profile DFHCICST. This profile is defined with SCRNSIZE(DEFAULT) and, if you want to use the alternate screen size of the printer, you have to change the profile entry for transaction CSPP.
CICS uses the hardware COPY feature of the 3270 to perform the print, unless a task is currently attached to the display.
You need not specify COPY(YES) on the typeterm definition, because this is implied by PRINTERCOPY(YES) on the terminal definition.
If you have named an ALTPRINTER as well as a PRINTER, you may specify ALTPRINTCOPY(YES).
To use the COPY feature, both the printer and the display terminal must be on the same 3270 control unit. Otherwise, either the COPY may fail, raising an error condition or, if the display device address is valid for the printer's control unit, copying might be performed from a different display.
Do not specify PRINTERCOPY(YES) if, in a networking environment, the 3270 control unit is connected to a TCAM system in one domain, and a CICS system in another domain has access to the control unit via VTAM. This is because the hardware COPY address is not available to CICS and cannot therefore be used by terminals attached to such a control unit.
The COPY command is invalid for a 3270 compatibility mode display.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
This is the CONNECTION name on the CONNECTION definition for the intercommunication link. If it is not specified, or if it is specified as the sysid of the local system, this terminal is local to this system. If the name is that of another system, the terminal is remote. You can therefore use the same definition for the terminal in both the local system and a remote system.
If there are intermediate systems between this CICS and the terminal-owning region, REMOTESYSTEM should specify the first link in the path to the TOR. If there is more than one possible path, it should specify the first link in the preferred path.
REMOTESYSTEM is ignored if you specify AUTINSTMODEL(YES) or (ONLY).
In a CICS system with security initialized (SEC=YES or MIGRATE), the security name is used to establish the authority of the remote system.
The security name (or USERID on the sessions definition) must be a valid RACF userid on your system. Access to protected resources on your system is based on the RACF user profile and its group membership.
For further information on defining security for MRO, LUTYPE6.1, and APPC connections, see Intercommunication security.
When you define a 3600 pipeline logical unit, you generate a TCTTE that is associated with a pool of TCTTEs. As messages enter CICS from the 3600 pipeline logical unit, a task is attached to process this message, using as an anchor block one of the TCTTEs from the pool. In this way, consecutive messages sent via the pipeline logical unit can be processed concurrently, the number of concurrent transactions being limited by the number of TCTTEs in the pool. The number of TCTTEs in the pool should represent the high-water mark of inquiry activity. In this way, the pipeline facility allows fewer TCTTEs to be defined to CICS than the total number of pipeline inquiry terminals.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
CEMT INQUIRE TERMINAL(value1,value2)
CEMT SET TERMINAL(value1,value2)
where
the comma serves as a list delimiter. See CICS Supplied
Transactions for information about using lists of resource identifiers.The name specified becomes the name of the TCT entry, when this TERMINAL definition is installed. For this reason, the TERMINAL name should be unique (note that the value CERR is reserved for the identification generated for the error console). If you specify AUTINSTMODEL(ONLY), you need not worry about making the TERMINAL name unique, because it is not used as the name of a TCT entry. If you specify AUTINSTMODEL(YES), the TERMINAL name is used as the name of the TCT entry that is installed in the TCT when the TERMINAL definition is installed; the names of the TCT entries for the autoinstalled terminals are determined by the autoinstall user program.
If the terminal is to be associated with a transient data destination, the terminal name and the destination identification in the DCT must be the same.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
For information on what happens when a transaction is initiated, see the CICS Application Programming Guide.
If you specify this operand for a 3270 display, the only CICS functions the operator can invoke, other than this transaction, are paging commands and print requests.
You are unlikely to specify the TRANSACTION attribute for a 3270 display or SCS printer. It is optional for 3601 logical units, but is mandatory for 3614 logical units.
If this operand is specified for a 3790 Communication System, and multiple sessions are used to connect the same 3791, specify the same TRANSACTION name for all sessions.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
The TYPETERM definition specifies many attributes for a number of similar terminals. For more information, see TYPETERM definition attributes and How resources are defined. This attribute is mandatory for all TERMINAL definitions.
The TYPETERM definition should already be installed when you install this TERMINAL definition.
This is the only way to specify a user identifier for devices such as printers that are unable to sign on using CESN. You can also specify USERID for a display device; if so, the display is permanently signed on. Operators are unable to sign on. All access to protected resources depends on the authorizations permitted by RACF for the specified USERID.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |