Configuring for System Currency
As you make changes to your operating system and vendor software, you may also need to make changes to BMC product configurations. When upgrading z/OS subsystems, there are customization and reconfiguration tasks need to be performed to ensure Code Debug CICS continues to function correctly.
This task involes following roles:
- Code Debug CICS Installer
- Db2 DBA
- IMS DBA
Task 19.1 Upgrading CICS
The following person is required:
- Code Debug CICS Installer
Perform the following tasks when upgrading CICS (not Code Debug CICS).
Task 19.1.1 Install the New FMID
If the SMP/E FMID for the new CICS release is not already installed, follow the instructions in the BMC Installer Mainframe Products SMP/E Installation space to install Code Debug CICS.
Task 19.1.2 Restart the Code Debug Service Provider with Updated SMXDAUTH
The updated SMXDAUTH could be from the new FMID or a previously installed FMID with maintenance applied to support the new CICS. Messages issued during Service Provider startup include:
XSP0031I Highest supported release = CICS TS version.release (CICS nn.nn.nn)
Verify that the message shows your new CICS release, or a higher release.
Task 19.1.3 Update the CICS Startup JCL
Change your site’s CICS startup JCL as follows:
- Make the CSS load library accessible to Code Debug CICS by adding it to the DFHRPL concatenation in the CICS startup JCL. The CSS load library is named CPWR.LCXnnn.SLCXLOAD (nnn is the release of CSS) and is included in the installation of Enterprise Common Components.
Add the appropriate Code Debug CICS load library listed in the following table to the DFHRPL concatenation.
Code Debug CICS Load Library Data setsCICS Release
Data set Name
CICS TS 5.6
CPWR.VMXD170.SMXDO73L
CICS TS 6.1
CPWR.WMXD170.SMXDO74L
CICS TS 6.2
CPWR.XMXD170.SMXDO75L
CICS TS 6.3 CPWR.YMXD170.SMXDO76L
Task 19.2 Upgrading Db2
The following person is required:
- Db2 DBA
Perform the following tasks when upgrading Db2 (not Code Debug CICS).
Task 19.2.1 Update Support for the Db2 File Utility
The DBRM members for the Db2 File Utility have been updated in release 17.02 of Code Debug CICS. If you are using the Db2 File Utility, the bind for plan (MXDPLAN) needs to be rerun. The default bind package name has changed in this release to reflect the product code and release (MXD0170).
Perform the following steps to bind the plan:
- Modify the JCL in member DBBIND10 as described in the comments within that member.
- The JCL in DBBIND10 must be executed by an authorized Db2 user. Submit the JCL and ensure it completes successfully.
- The plan bound above must have EXECUTE authorization granted to PUBLIC. Use SPUFI (or whatever Db2 utility is used at your site) to execute the following SQL statement:
GRANT EXECUTE ON PLAN MXDPLAN TO PUBLIC
If you changed the plan name in the JCL above, substitute that plan name in place of MXDPLAN before executing the SQL statement.
Task 19.3 Upgrading IMS
The following person is required:
- IMS DBA
Perform the following task when upgrading IMS (not Code Debug CICS).
Task 19.3.1 Update Support for the IMS File Utility
If you have implemented the Code Debug CICS IMS File Utility, you will need to update to the new Code Debug CICS APF authorized library in the DLISAS and IMS control region STEPLIB. The default authorized library is SMXDAUTH.