CICS Sys62

Click this to display the CICS Group group_name page.

Click this to save changes you have made to the page, refresh the page and add the new Sys62 to the group you specify in Grp. The button changes to Apply.

Specify the name of this Sys62. Can be up to four characters: the first character must be A-Z, @, #, or $; trailing characters can be any of these, or 0-9. The name is forced to upper case.

Choose a group to which this Sys62 will belong. The list of groups from which you can choose include only those which can be edited by you.

Specify a short description of the Sys62. Acceptable characters are A through Z, 0 through 9, $, @ and #.

Specify the parameter used to connect this definition to the LU6.2 protocol stack definition for this connection.

Specify the parameter that tells the LU6.2 protocol stack which Mode (or session characteristics) Table to use for this connection.

Specify the parameter required to associate this definition with a peer server's definition within the LU6.2 protocol stack definitions.

Specify the SNA Application ID of the peer partner server for this connection.

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.

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. However, 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.

Specify the maximum number of parallel sessions allowed to be active on this LU.

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.

Check this to enable this facility to default to (or start initially as) being “in service”.

If the Fully Qualified Partner name in the connection is validated and installed, it will be used at run time on the APPC Allocate verb, whereas the PARTNER LU Alias is set to binary zeroes.

Specify the permanent user ID for this LU. Any work running against this facility will inherit the permissions of this user ID.

Specify the default language for user interfaces connected to this facility.

Specify the name for the session.

Specify the level of attach-time user security required for the connection:

• Identify - 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.
• Local - 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.
• Mixed - 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.
• Persistent - 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.
• Verify - 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 send passwords.

Specify the three-character Operator ID associated with the permanent User ID - returned on ASSIGN OPID() command for transaction attached to this facility.

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. Defaults to 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)

The sum cannot be greater than 255.

Choose a setting to apply to all the resource keys:

• On - enables all of the resource keys
• Off - disables all of the resource keys

Check any of the boxes 1 through 24 to activate that resource key.

Click this to delete this Sys62. This button is displayed only after you click Add.

Click this to create a new Sys62, using the values set on this page as the basis for the new Sys62. This button is displayed only after you click Add.

Click this to create and view dump information for this Sys62. This button is only displayed after you click Add.