MHT Compare Modernization Guide

MHT Compare is a suite of utilities designed for comparing data sets and program source code on z/OS systems. It includes MHTCOMPR for comparing QSAM, BDAM, and VSAM files, and SRCCOMPR for comparing program source code.

MHTCOMPR compares QSAM, BDAM, and VSAM files. SRCCOMPR compares program source code. Both utilities provide detailed reports on the differences found between the compared files or source code.

MHT Compare is primarily used in batch processing environments on z/OS. It is invoked through JCL (Job Control Language) and produces reports that can be analyzed to identify differences between datasets or source code versions.

MHT Compare provides detailed comparison reports, highlighting the differences between files or source code. These reports can be used for auditing, debugging, and ensuring data integrity.

MHTCOMPR is invoked via JCL using control statements to specify the input datasets and comparison options. For example: ```JCL //STEP1 EXEC PGM=MHTCOMPR //INPUT1 DD DSN=input.dataset1,DISP=SHR //INPUT2 DD DSN=input.dataset2,DISP=SHR //REPORT DD SYSOUT=* //SYSIN DD * COMPARE DS1=INPUT1,DS2=INPUT2,OPTIONS=... ```

SRCCOMPR is also invoked via JCL, similar to MHTCOMPR, but it is tailored for comparing program source code. The SYSIN DD statement is used to pass comparison parameters. ```JCL //STEP1 EXEC PGM=SRCCOMPR //INPUT1 DD DSN=source.dataset1,DISP=SHR //INPUT2 DD DSN=source.dataset2,DISP=SHR //REPORT DD SYSOUT=* //SYSIN DD * COMPARE DS1=INPUT1,DS2=INPUT2,OPTIONS=... ```

MHT Compare uses standard z/OS datasets (QSAM, BDAM, VSAM) for input and output. The comparison reports are typically written to a SYSOUT dataset or a sequential file.

The primary configuration interface is through JCL control statements passed via the SYSIN DD. These statements specify the datasets to compare and various comparison options, such as ignoring case or whitespace.

MHT Compare helps ensure data integrity by identifying discrepancies between datasets. This is crucial for maintaining accurate records and preventing data corruption.

By comparing program source code, MHT Compare helps identify unintended changes or errors introduced during development. This ensures that the correct code is deployed and executed.

MHT Compare can be used to audit data and code changes, providing a record of modifications and ensuring compliance with regulatory requirements.

MHT Compare helps reduce the risk of errors and data corruption, leading to cost savings by preventing system failures and data recovery efforts.

MHT Compare operates within the z/OS security environment. It leverages z/OS security features to control access to the datasets being compared.

MHT Compare relies on z/OS Resource Access Control Facility (RACF) or equivalent security systems to manage access to datasets. Access is controlled at the dataset level.

MHT Compare does not directly encrypt data. However, it can operate on encrypted datasets if the appropriate z/OS encryption facilities are in place and the user has the necessary permissions to access the encrypted data.

MHT Compare generates reports that can be used for auditing purposes. These reports provide a record of the comparisons performed and the differences found.

MHT Compare is typically deployed as part of a standard z/OS environment. It requires access to the datasets being compared and the ability to write reports to SYSOUT or sequential files.

MHT Compare is monitored through standard z/OS monitoring tools and logs. The reports generated by MHTCOMPR and SRCCOMPR provide detailed information about the comparisons performed.

MHT Compare is configured through JCL control statements. These statements specify the datasets to compare and various comparison options.

MHT Compare requires standard z/OS operational procedures for managing JCL jobs, datasets, and security. No specific operational procedures are unique to MHT Compare.