Use this page to create a new Sys62 resource.
A Sys62 is a definition of an LU6.2 system connection.
ACTIVE to make this resource active.
DELETE to delete this Sys62 resource.
COPY to create a new Sys62 resource, using the values set on this page as the basis for the new Sys62 resource.
DUMP to create and view dump information for this Sys62.
APPLY to save your changes to the Sys62.
- Specify a short description of the Sys62. Acceptable characters are A through Z, 0 through 9, $, @ and #.
- Logical Unit Alias
- Specify the parameter used to connect this definition to the LU6.2 protocol stack definition for this connection.
- Model Table
- Specify the parameter that tells the LU6.2 protocol stack which Mode Table (or session characteristics) to use for this connection.
- Partner Alias
- Specify the parameter required to associate this definition with a peer server's definition within the LU6.2 protocol stack
- Specify the SNA Application ID of the peer partner server for this connection.
- Net Name
- Specify the network name that identifies the remote system. The name can be up to eight characters in length. The name follows
assembler language rules. It must start with an alphabetic character. The acceptable characters are: A-Z 0-9 $ @ and #. Lower-case
characters are converted to upper-case except when using the CREATE command. The Net Name is the APPLID of the remote system
or region, unless you are defining an APPC or LUTYPE6.1 link to a VTAM generic resource group. If you are defining an LUTYPE6.1
link to a generic resource, Net Name must specify the generic resource name, not the APPLID of one of the group members. If
you are defining an APPC link to a generic resource, Net Name can specify either the group's generic resource name or the
APPLID (member name) of one of the group members. Note: If you specify a member name, and this CICS is not itself a member
of a CICS Transaction Server for OS/390 generic resource, the connection must always be acquired by this CICS. For VTAM, the
APPLID is the label of the remote ACF/VTAM VBUILD TYPE=APPL statement. If you do not supply a Net Name, the CONNECTION name
is used by default. You cannot have two or more APPC links with the same Net Name.
- Fully Qualified Partner
- Identifies a fully qualified partner name for LU62 connection definitions. This field is formed of a NETWORK ID and a Partner
LU name. Both must be no longer than eight characters, separated by a period ('.'). For example, BBNET1.CICSDEV1.If the Fully
Qualified Partner name in the connection is validated and installed, it is used at run time on the APPC Allocate verb, whereas
the PARTNER LU Alias is set to binary zeroes.
- Session Maximum
- Specifies the maximum number of parallel sessions permited to be active on this LU.
- Transaction Code
- Specify the permanent four-character transaction code to be attached to handle unsolicited input.
- Specify the facility-related priority to be used for work that is running with this as the primary facility.
- Specifies whether two-phase commit (level 2) is required on the connection or not (level 1).
- In Service
- Check this to enable this facility to default to (or start initially as) being "in service".
- User ID
- Specify the permanent user ID for this LU. Any work running against this facility will inherit the permissions of this user
- Session Name
- Specify the name for the session.
- Operator ID
- Specify the three-character Operator ID associated with the permanent User ID - returned on ASSIGN OPID() command for transaction
attached to this facility.
- Operator Priority
- Specify the operator priority for transactions run from this terminal. Specify this for a terminal that cannot be signed on,
such as a printer. If you specify it for a terminal that can be signed on, it is overridden by the operator priority specified
in the user's sign-on table entry. The default value is 0 (zero). Operator priority is one factor in determining a transaction's
execution priority, which is the sum of:
- Terminal priority
- Transaction priority
- Operator priority (this field)
Note: The sum cannot be greater than 255.
- Specifies the default language for user interfaces connected to this facility.
- Attach-time User Security
- Specifies the level of attach-time user security required for the connection:
- Incoming attach requests must specify a user identifier. IDENTIFY is used when the connecting system has a security manager,
for example, if it is another CICS system.
- The authority of the user is taken to be that of the link itself, and you rely on link security alone to protect your resource.
Local must be specified if the PROTOCOL attribute on the CONNECTION definition is LU6.1.
- Incoming attach requests may be using either or both IDENTIFY or PERSISTENT security types. The security type actually used
depends on the incoming attach request.
- Incoming attach requests must specify a user identifier and a user password on the first attach request. Subsequent attach
requests require only the user identifier. This should be used only between a PWS (programmable workstation, for example,
an IBM Personal System/2) and CICS.
- Incoming attach requests must specify a user identifier and a user password. Enter Verify when the connecting system has no
security manager and hence cannot be trusted. Do not specify Verify for CICS-to-CICS communication, because CICS does not