|
|
|
|
The information required for two programs to communicate is stored in CPI-C side information entries in the SNAP-IX configuration file. You will need to coordinate with your System Administrator to ensure that it contains what you need. For additional information about configuration, refer to the SNAP-IX Administration Guide.
Each side information entry is identified by a Symbolic Destination Name, which is the sym_dest_name parameter specified by the Initialize_Conversation call. The parameter sym_dest_name is an 8-byte ASCII character string and can contain any displayable characters.
If you are developing commercial programs or programs that will be installed on multiple machines within your organization, you may want to include logic to use a different sym_dest_name for each copy of the program.
Each side information entry contains the following fields:
Local LU alias
Partner LU name
Partner program type and name
Mode name
Conversation security type
Security user ID and password
Application-specified side information
This is the alias of the local LU to be used to allocate conversations. It consists of up to eight ASCII characters. For the allowed characters, see Set_Local_LU_Name (cmslln).
This is the name by which the partner 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 (cmspln).
These fields indicate whether the partner program is an application program or SNA service program, and the partner program name. An application program name can contain up to 64 ASCII characters. A service program can contain up to four characters. For the allowed characters, see Set_TP_Name (cmstpn).
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 (cmsmn).
This field indicates whether security will be used and if so, what type. The security type can specify that CPI-C must send a user ID and password when allocating 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 (cmscst).
If the remote program uses conversation security, and does not accept
an already verified
indication, a valid combination of user
ID and password is required to access the invoked program. The user ID and
password can be up to 10 ASCII characters. For the allowed characters, see Set_Conversation_Security_User_ID (cmscsu) and Set_Conversation_Security_Password (cmscsp).
The functions described in this section are not available in Java CPI-C. A Java CPI-C application cannot maintain its own CPI-C side information entries. However, it can override individual parameters in the side information, or determine their values, by using Set_* or Extract_* functions for each required parameter.
An application can override the side information stored in the configuration file to maintain its own side information entries, using the following calls:
Set_CPIC_Side_Information (to define a side information entry associated with a specified sym_dest_name; if the sym_dest_name is already defined in the configuration file, the new information overrides the configuration file)
Delete_CPIC_Side_Information (to indicate that an entry defined by the application, or one defined in the configuration file, is no longer available for use by this application)
Extract_CPIC_Side_Information (to return the contents of a side information entry-either an entry defined by the application, or one defined in the configuration file)
The modified information then applies only to this application; it does not affect other applications, and does not change the configuration file. The modified information is discarded when the application ends.
These calls are not part of IBM CPI-C 2.0; they are provided for compatibility with X/Open CPI-C. In addition, in the side information structure used by these calls, the user ID and password parameters are defined as eight characters (as in X/Open CPI-C) instead of 10 (as in IBM CPI-C 2.0). This leads to the following restrictions:
If the partner application requires a user ID or password of more than eight characters, you cannot specify it using Set_CPIC_Side_Information. You must either use a side information entry defined in the configuration file, or define one using Set_CPIC_Side_Information and then override the user ID or password using the Set_Conversation_Security_User_ID or Set_Conversation_Security_Password call.
If the side information entry in the configuration file contains a user ID of more than eight characters, you cannot extract it using Extract_CPIC_Side_Information. You must use the Extract_Security_User_ID call. (This does not apply to the password, because CPI-C does not allow the application to extract it.)
|
|
|
 |
|