CIMS Mainframe Modernization Guide

CIMS Mainframe provided detailed information for chargeback, capacity planning, and invoicing based on resource consumption. It tracked CPU usage, batch jobs, CICS transactions, and IMS transactions.

CIMS Mainframe collected data from SMF records generated by the z/OS and z/VSE operating systems. It then processed and aggregated this data into reports and analyses.

CIMS Mainframe used configuration files to define parameters such as SMF record types to process, reporting periods, and chargeback rates. These files were typically maintained by system administrators.

CIMS Mainframe could generate various reports, including CPU utilization reports, batch job accounting reports, CICS transaction reports, and IMS transaction reports. These reports could be customized based on specific criteria.

CIMS Mainframe primarily relied on SMF (System Management Facilities) data for its accounting information. It processed SMF records generated by z/OS and z/VSE to track resource usage.

CIMS Mainframe did not expose standard APIs like REST or SOAP. Integration typically involved direct access to the CIMS database or custom-developed interfaces.

The main components of CIMS Mainframe included the data collection module, the data processing module, the reporting module, and the database. These components communicated through internal interfaces and data stores.

CIMS Mainframe stored its data in a relational database, such as DB2 on z/OS. The database schema included tables for storing resource usage data, chargeback rates, and reporting definitions.

CIMS Mainframe provided valuable insights into IT resource consumption, enabling organizations to implement chargeback mechanisms, optimize resource allocation, and improve capacity planning.

By accurately tracking resource usage, CIMS Mainframe helped organizations identify cost savings opportunities, such as optimizing batch processing schedules or consolidating underutilized resources.

CIMS Mainframe's reporting capabilities allowed organizations to generate invoices based on actual resource consumption, ensuring fair and transparent billing practices.

CIMS Mainframe leveraged the security features of the underlying z/OS and z/VSE operating systems. It supported authentication methods such as RACF, ACF2, and Top Secret.

CIMS Mainframe employed an access control model based on user IDs and roles. Access to specific functions and data was controlled through security profiles defined in the security system.

CIMS Mainframe did not provide built-in encryption capabilities. However, organizations could implement encryption at the database level or through network security protocols.

CIMS Mainframe provided audit logging capabilities, recording user access, configuration changes, and report generation activities. These logs could be used for security monitoring and compliance purposes.

CIMS Mainframe was administered through a combination of ISPF panels and batch jobs. System administrators used ISPF panels to configure the system and submit batch jobs for data processing and reporting.

User management was handled through the underlying z/OS or z/VSE security system (e.g., RACF, ACF2, Top Secret). CIMS Mainframe relied on these systems for user authentication and authorization.

CIMS Mainframe provided monitoring capabilities through SMF data and system logs. Administrators could monitor system performance, resource utilization, and error conditions using these data sources.