IBM Support

CCV9106E connecting from ISPF client after upgrading to CICS CM 5.2

Question & Answer


Question

Do you know what could cause message CCV9106E when I attempt to connect from the ISPF client after upgrading from CICS Configuration Manager for z/OS (CICS CM) V2.1 to CICS CM V5.2?

I get long message:

CCV9106E The Server and Client APIs are operating at different software releases.

I shutdown the CICS CM V2.1 server and only had the CICS CM V5.2 server up and running and updated my ISPF libraries to the new data sets. I brought the CICS CM V2.1 server back up since I was unable to connect to CICS CM V5.2.

Is there a checklist I can follow to make sure I did not miss a step?

Answer

The CCV9106E message is based on the XML root element passed in the Send buffer to the CICS CM server. For CICS CM V5.2, the root element XML tag is <CCV520>.

You said that the CICS CM V5.2 server is up and running on the same LPAR as the CICS CM V2.1 server. If both have the same hostname and ipaddress then the only other way to differentiate the CICS CM server would be the portnumber specified on the ISPF client main panel. If the portnumber is the same one that the CICS CM 2.1 server is using, and the upgraded ISPF client did pass an XML root element tag <CCV520>, then if this got passed to the CICS CM 2.1 server, it would not understand the <CCV520> root element tag and would return the API release mismatch error.

Before you run your initial command from the ISPF client, you can use the 'Settings' menu action, option 4 'Set XML Trace options', and option 2 to just trace XML to your terminal. After you run the command, the root element in the XML Send Buffer will show the API release level. If this is <CCV520>, then the ISPF client is probably configured ok, but the ipaddress and portnumber are probably going to the CICS CM 2.1 server on the same LPAR.

If you need to run both 2.1 and 5.2 concurrently until you migrate to a single 5.2 CM server, then you will need separate CCVDDD system options data sets. The SCCVSAMP member CCVXSYSO has the system options where you define the ServerIPAddress, and the various portnumbers for use by the CM server. The CICS CM server uses the CCVXSYSO information to create the TCPIPSERVCICEs in the CM server.

As to your question regarding is there an easier checklist than reading entire CCV52 manual, you can probably just focus on these links to upgrade from 2.1 to 5.2.

Upgrading from V2.1 in the CICS CM 5.1 documentation

You follow the upgrading from 2.1 to 5.1 first, then proceed to Upgrading from V5.1 in the CICS CM 5.2 documentation for upgrading from 5.1 to 5.2 (even though you are skipping 5.2).

There is a hyperlink named Information you will need for installation that is a table of what items you need to complete the upgrade.

It provides some form of a checklist approach to the upgrade that might allow you to begin to exploit and test the various features of CM 5.2 without reading all the documentation for CICS CM 5.2.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS2L7A","label":"CICS Configuration Manager for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICSCM CICS CM

Document Information

Modified date:
18 January 2016

UID

dwa1239984