Editar

Partilhar via

Side Information for CPI-C Programs

  • Artigo

The information required for two Common Programming Interface for Communications (CPI-C) programs to communicate is stored as a table, called the side information table, in memory. The table is derived from the symbolic destination name (configured in Host Integration Server) and from the Set_CPIC_Side_Information, Extract_CPIC_Side_Information, and Delete_CPIC_Side_Information calls.

The side information is maintained by the system administrator.

If you are developing commercial programs or programs that will be installed on multiple computers within your organization, it is recommended that you include logic that enables a user or system administrator to specify configuration information for each copy of the program.

Each side information entry contains the following fields:

Symbolic destination name
This is the sym_dest_name parameter specified by Initialize_Conversation. It is the identifier for the side information entry. The name can be up to eight ASCII characters. See Set_CPIC_Side_Information for the allowed characters.

Partner LU name
This is the name by which the partner logical unit (LU) is known to the local program. It can be an alias of up to eight ASCII characters or a fully qualified network name of up to 17 characters. For the allowed characters, see Set_Partner_LU_Name.

Partner program type and name
These fields indicate whether the partner program is an application transaction program (TP) or an SNA service TP, and provide the partner program name. An application TP name can contain up to 64 ASCII characters. A service TP name can contain up to four characters. For the allowed characters, see Set_TP_Name.

Mode name
This name represents a set of characteristics to be used in an LU-to-LU session. The mode name can contain up to eight ASCII characters. For the allowed characters, see Set_Mode_Name.

Conversation security type
This field indicates whether security will be used and if so, what type.

You can use conversation security to require that the invoking program provides a user identifier and password before CPI-C allocates a conversation with the invoked program.

For an invoked program that in turn invokes another program, the security type can inform the second invoked program that security has already been verified.

For further information about conversation security, see Set_Conversation_Security_Type.

Security user identifier and password
If you intend to use conversation security, a valid combination of user identifier and password is required to access the invoked program. The user identifier and password can be up to 10 ASCII characters. For information about allowed characters, see Set_Conversation_Security_User_ID and Set_Conversation_Security_Password.