Chapter 23: Test Remote IMS Connection

A utility is provided to test the communications configuration and the installation of Remote IMS. This uses the Remote IMS system in the same way that your IMS Option applications use it. The main difference is that it does not schedule a PSB or make any database calls. The test utility establishes a conversation with the Server; the Requester and Server exchange their configuration information and the conversation ends. Successful completion assures you that the communication systems are defined and working properly and the Requester and Server are installed and configured properly. You see any errors along with the other information in the Remote Test output tab. This tab is created automatically the first time you run a Remote Test. See the chapter Problem Determination if you cannot resolve the problem from the information displayed in the tab. We recommend using this utility prior to using an IMS Option application to access a Remote Database.

23.1 Running the Test

When you start the test utility, it first displays information about your Remote IMS Requester configuration. Once it connects to the Server, it shows its version and configuration settings.

To run the test, select IMS > Remote Test on the Tools menu.

23.2 Ending Return Codes

A return code of zero indicates success. Non-zero return codes categorize the type of error. The table below list and describes these return codes:

Return Code	Description
0	Success
3	Requester connect timeout exceeded
4	Communications error, retry possible
8	Remote IMS configuration error
12	Remote IMS system error. Examples are memory allocation failures and I/O errors
16	Communications failure
24	Remote IMS "cleanup" failure. Needs manual intervention. See the section IMS System Log in the chapter IMS Option Administration Information in the *Administrator's Guide*.
54	IMS Option not installed correctly or command line syntax invalid

Notes:

Return codes of 3 and 4 indicate that you might be successful connecting at a later time. They do not necessarily mean that you have to make any changes to your configuration.

A return code of 3 indicates that a connection could not be established within the configured time period. This time period is set in the RMTIMS.INI file and has a default of 60 seconds. The most likely cause is that there is no dependent region available into which the the Server can be scheduled. Waiting until one is free might result in a successful connection. However, a connect timeout can also occur when the IMS/ESA system does not have any dependent regions running to service the Remote IMS Server CLASS definition. In this case an operator needs to start a dependent region or to change the APPC/MVS definition to assign a new CLASS to the Server transaction.
A return code of 4 is returned when the CPI-C system returns an error to the Requester indicating a retry is possible. These CPI-C return codes are intended to identify temporary conditions which may correct themselves by waiting. For example, APPC/MVS or IMS/ESA are unavailable or an error on the communications line.

However, when you first install Remote IMS these errors are more likely to mean that something is not defined correctly. If this return code persists, review your configuration parameters. Also, see the chapter Problem Determination for additional information.