Defining CPI-C Side Information

If you are supporting a CPI-C application that uses CPI-C symbolic destination names, you need to define the CPI-C side information. The side information associates the symbolic destination name with information about the partner TP, partner LU, mode, and security for the conversation.

To determine the symbolic destination name for CPI-C, consult the application developer (or for a third-party application, consult the product documentation).

To configure CPI-C side information, use one of the following methods:

Motif administration program

Select APPC and CPI-C from the Services menu on the Node window.

Command-line administration program

Issue the following command:

define_cpic_side_info

CPI-C Configuration Parameters

For each CPI-C symbolic destination name used by the application, collect the following information:

Name

The symbolic destination name used by the CPI-C applications (also known as TPs) that you want to run. This name can be 1-8 characters in length.

The application developer (or for a third-party application, the product documentation) can provide this name.

Local LU

The local LU for any conversations initiated by TPs using this side information using one of the following methods:

Local LU alias: An alias for a local LU.
Use default LU: Specify this option to use a member of the default pool (if one exists) or the node control point LU (if no default pool is defined).

If the APPCLLU environment variable is set, the local LU information you supply is ignored, and the LU specified for the environment variable is used instead.

Partner LU

Either an alias or the fully qualified partner LU name for conversations initiated by local TPs using this side information. The partner LU must be an LU that is configured on the computer that runs the partner TP.

Mode

The name of the APPC mode that is to be used to access the partner LU. In most cases, the mode is one of the following predefined modes:

A blank name
#BATCH
#BATCHSC
#INTER
#INTERSC
QPCSUPP

Partner TP

The name of the transaction program with which the CPI-C application communicates:

If the TP is a user application, specify the name as normal characters (up to 64 characters in length).
If the TP is a service TP, specify the name in hexadecimal (up to 8 hexadecimal digits, representing 4 bytes).

The application developer (or for a third-party application, the product documentation) can provide this information.

Security

The level of conversation-level security you want to use. The options are as follows:

None: The partner TP does not require security parameters to be checked.
Same: The partner TP uses security, but accepts verification by the local TP of the user ID and password provided by the initiating TP. If you choose a security level of Same, you also need to specify a valid user ID that is accepted by the partner TP.
Program: The partner TP requires a User ID and password. If you choose a security level of Program, you need to specify a valid user ID and password that are accepted by the partner TP.
Program strong: The partner TP requires a user ID and password. Both the local and remote nodes must support security enhancements so that the password is encrypted.

Refer to the documentation for the CPI-C application or consult the application programmer to find out what security parameters to use.

User ID

If you have chosen a security level of Same, Program, or Program strong, specify a user ID to be sent on the initiating message to the remote application. This value must match a user ID that the application is defined to accept.

This user ID is not related to HP-UX login user IDs on either the local or the remote node. If the remote node is running SNAplus2, the user ID must be configured on the remote node using the Conversation Security Configuration dialog.

Password

If the security level is specified as Program or Program strong, specify a password to be sent when the conversation is allocated. This value must match the password defined at the remote application for use with the supplied user name.

This password is not related to HP-UX login passwords on either the local or the remote node.

If the remote node is running SNAplus2, the password must be configured on the remote node using the Conversation Security Configuration dialog.

Additional Configuration

After performing the CPI-C configuration, continue with the following configuration tasks:

To define APPC security, see “Configuring APPC Security”.
To configure 5250 communication, see Chapter 8 “Configuring User Applications”

Defining CPI-C Side Information

Technical documentation

» Table of Contents

» Index

CPI-C Configuration Parameters

Additional Configuration