Setting Up a Region That Supports CICS Resources › CICS Connections Implementation › PPI Connection Definitions › PPI Explicit Connection Definitions

PPI Explicit Connection Definitions

You define explicit PPI connections for one of the following reasons:

• A region on the same system is already using dynamic registration.
• The region is using dynamic registration, but you want to change the characteristics of specific connections.

Explicit PPI connections are defined on the third page of the CICSCNTL parameter group. The following is an example of the panel:

     Specific CICS Link Definitions: These statements define which specific
     CICS systems are to be linked to SOLVE and allow the specification of
     filters other than the DEFAULT filter. The syntax for CICS definitions is:

     < CICS JOBNAME= jobname  SYSID= system-id
            < FILTER= { DEFAULT | name } >
            < UNSOL= { YES | NO } >
            < CACHE= { YES | NO } > >

LINE   ----+----10---+----20---+----30---+----40---+----50---+----60---+----70-
****** ***************************** TOP OF DATA ******************************
000001 CICS JOBNAME=CICSA SYSID=SC01
****** **************************** BOTTOM OF DATA ****************************

Press F10 or F11 to scroll through the panels. When you are defining filters or explicit connections, press F7 or F8 to scroll the lines.

You can set the following characteristics in an explicit connection definition:

• Filter to use for unsolicited CICS messages
• Whether to receive unsolicited CICS messages

  Notes:

  • If you are supporting CICS on more than one region on the same system, only one of these regions can specify UNSOL=YES, which is the default.
  • If more than one region specified UNSOL=YES, only the first region that turns on the unsolicited message flow receives the messages. The other regions do not receive these messages.
• Whether to use a cache to speed up the discovery of CICS resource statuses when the connection is first established. The cache is useful only if all or most of the resources defined in CICS are also defined in this product. Do not use the cache if only a small percentage of the CICS resources is defined.

Example: PPI Connection with CICSA

The following example defines a PPI connection between this product and CICSA. The connection uses the DEFAULT filter to pass unsolicited CICS messages.

CICS JOBNAME=CICSA
SYSID=SC01

Note: This product uses the system ID of the CICS region to derive the PPI receiver ID of the CICS agent.

Example: PPI Connection Using CICSAMSG Filter

The following PPI connection uses the CICSAMSG filter to pass unsolicited messages from CICSA.

CICS JOBNAME=CICSA
SYSID=SC01 FILTER=CICSAMSG

Example: CICS Command and Response Flow

The following PPI connection supports CICS command and response flow only.

CICS JOBNAME=CICSB
SYSID=SC02 UNSOL=NO