CICS Sys62 -sys62_name(group_name)

APPLID Apply Attach Copy Delete Description Dump Group List In Service Language LU Alias Mode Table Name | Net Name Oper ID Oper Priority Partner Alias Priority Resource Keys, 1 - 24 Resource Keys, all Session Max Session Name Transaction User ID

CICS Sys62 - sys62_name (group_name)

  Use this page to view and edit the Sys62 sys62, selected from the CICS Group group_name page. A Sys62 is a definition of an LU6.2 system connection.

  The title bar gives details of the Sys62 you are editing and the resource group it belongs to.

  Top

Group List

  Click this to display the CICS Group group_name page.

  Top

Apply

  Click this to save changes you have made to the page and refresh the page. This button is displayed only if you have permission to edit the group in which the Sys62 resides.

  Top

Name

  Shows the name of this Sys62.

  Top

Description

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

  Top

LU Alias

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

  Top

Mode Table

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

  Top

Partner Alias

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

  Top

APPLID

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

  Top

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.

  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.

  Top

Session Max

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

  Top

Transaction

  Specify the permanent four character transaction code to be attached to handle unsolicited input.

  Top

Priority

  Specify the facility related priority to be used for work that is running with this as the primary facility.

  Top

In Service

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

  Top

User ID

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

  Top

Language

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

  Top

Session Name

  Specify the name for the session.

  Top

Attach

  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.

  Top

Oper ID

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

  Top

Oper Priority

  Specify the operator-related priority for transactions running against this facility.

  Top

Resource Keys, all

  Choose a setting to apply to all the resource keys:

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

  Top

Resource Keys, 1 - 24

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

  Top

Delete

  Click this to delete this Sys62. You only see this button if you have editing permissions for the group to which the Sys62 belongs.

  Top

Copy

  Click this to create a new Sys62, using the values set on this page as the basis for the new Sys62.

  Top

Dump

  Click this to create and view dump information for this Sys62.

  Top