The CIMS Mainframe product is integrated into TDSz 1.8 as the Usage and Accounting Collector feature. Additional support and enhancements will be included in TDSz and not CIMS Mainframe. All CIMS Mainframe implementations must migrate to TDSz. Use this document as a guide to migrate to TDSz.
CIMS Mainframe implemented new record types in 11.5. These 79x record types are the preferred record types. In TDSz, the 79x records are the only types supported. The first thing to research for the TDSz migration is the current record type created by CIMS Mainframe. If the CIMS Mainframe subsystem programs (CIMSACCT, CIMSCMF2, CIMSDB2, CIMSDISK, CIMSTAPE, CIMSUNIV, and CIMSUN02) are creating DDNAME CIMSACT2 and this is the data set that is passed on to other processing, then the 79x records are created and you are in an excellent position to migrate to TDSz
(continue to the JCL Considerations when using 79x records).
Switching to 79x records
The CIMSBILL program is not supported in TDSz. It has been replaced with the DRLCMONY program (the TDSz version of CIMSMONY). Executing program CIMSBILL is another indicator that the 79x records are not being created. The conversion from CIMSBILL to CIMSMONY is documented in the CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide. The documentation will explain the options available and decisions that must to be made to migrate to TDSz and use the DRLCMONY (CIMSMONY) program.
TDSz will not produce the old 99x records. The default processing in TDSz is the creation of 79x records to the DDNAME CIMSACT2. Switching to the 79x records can be done with the migration to TDSz or it can be done while executing the CIMS Mainframe release. In either case, there are JCL changes that must be made and these are documented in the CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide.
JCL Considerations when using 79x records
The CIMS Mainframe programs were all renamed for TDSz. The program names start with DRLC instead of CIMS. For example, in CIMS Mainframe there is a CIMSEXTR program but in TDSz this is now called DRLCEXTR. The TDSz install links the new programs with an ALIAS of the CIMS Mainframe program name. Therefore, JCL that executes the CIMS Mainframe program CIMSEXTR will also work with TDSz because the DRLCEXTR has an alias of CIMSEXTR.
TDSz has made very few changes to the control statements that are entered via the DDNAME CIMSCNTL. The CIMS Mainframe JCL that references CIMS.DATAFILE should also work with TDSz.
The TDSz DDNAMEs have not changed.
CIMS Mainframe JCLs should work with the new TDSz Usage and Accounting Collector as long as the 79x records are were being produced in the CIMS Mainframe JCLs. Changes should be limited to STEPLIB changes to point to the TDSz load library.
TDSz no longer performs password checking. The DDNAME CIMSPASS can be removed from the TDSz JCL, but the presence of passwords will not cause a problem.
The following table outlines the release requirements for migrating to TDSz 1.8:
|Release||Migration to TDSz|
|12.2.1||Ready for migration to TDSz|
|12.2||Ready for migration to TDSz|
|12.1||Upgrade to 12.2.1 . Use directions in 12.2.1 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide .|
|12.0||Upgrade to 12.2.1 . Use directions in 12.2.1 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide .|
|11.6||Upgrade to 12.2.1 . Use directions in 12.2.1 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide .|
|11.5||Upgrade to 12.2.1 . Use directions in 12.0 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide and directions in 12.2.1 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide .|
|11.4||Upgrade to 12.2.1 . Use directions in 12.0 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide and directions in 12.2.1 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide .|
The above Release Considerations are general rules that take into account file conversions. The various files used by CIMS Mainframe must be converted to the 12.2/12.2.1 level before migrating to TDSz. The CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide contains the detailed instructions for upgrading the CIMS Mainframe product. Use the instructions in these manuals to complete the upgrade.
The upgrade procedures for the early releases (11.5 and 11.4) are documented in the 12.0 CIMS Mainframe Data Collector and Chargeback System Installation and Upgrade Guide. This manual is available from the CIMS Mainframe Information Center web page: http://publib.boulder.ibm.com/tividd/td/IBMCIMSMainframe12.2.1.html
All the procedures to convert the older CIMS Mainframe files are included in 12.2.1. The 12.0 manual should be consulted to see the steps required to convert the older releases to 12.0. Then the 12.2.1 manual can be used to complete the upgrade from 12.0 to 12.2.1.
In order to get the CIMS Mainframe 12.2.1 code and further assistance to upgrading to TDSz 1.8, please send your company name, customer number, name and contact number to email@example.com.
New name conventions
The CIMS Mainframe parts are renamed in TDSz to use the TDSz naming conventions. As stated earlier, the load modules have a new name that starts with DRLC (example DRLCEXTR instead of CIMSEXTR). The CIMS.DATAFILE is no longer distributed with TDSz. The sample JCLs are now found in DRL180.SDRLCNTL. The number of JCL members was reduced by including most control statements as instream data instead of separate members.
All CIMS.DATAFILE members were renamed by changing or adding a 4 character prefix. The prefixes are mapped as :
|DRLC||CLIST or REXX|
|DRLM|| Control statements, record definitions, ...etc.
DRLMR – Record descriptions
Use the following table as a cross reference to map the CIMS Mainframe CIMS.DATAFILE member names to the new names in TDSz: