The REPORT SYSMODS command compares the SYSMOD content of an input target or distribution zone to that of a comparison target or distribution zone. The resulting output can be used to determine which SYSMODs might need to be installed in the comparison zone to make its function and service content more equivalent to that of the input zone.

SMP/E first checks the REPORT SYSMODS command to determine the zones to be compared and whether SMPPUNCH output should be produced. The zones are then opened for read access along with the global zone. If NOPUNCH was not specified, the SMPPUNCH data set is also opened.

Next, SMP/E determines the matching SREL values from the zone definitions of the zones being compared. Matching values are saved to be put in the header of the SYSMOD Comparison report.

SMP/E then determines whether or not the zones to be compared contain SYSMOD entries. If they both contain SYSMOD entries, SMP/E looks for SYSMODs that are installed in the input zone but not in the comparison zone, and checks whether those SYSMODs are applicable to the comparison zone.

1. First, SMP/E reads sequentially through the SYSMOD entries in the input zone to determine which SYSMODs should be included in the report. For each SYSMOD entry that is not a superseded-only entry or deleted-only entry and is not in error, SMP/E checks the comparison zone to see if the SYSMOD also exists there. The SYSMOD exists in the comparison zone if one of the following is true:
   • There is a SYSMOD entry with the ERROR indicator off.
   • There is a SYSMOD entry with the DELBY subentry.
   • There is a SYSMOD entry with the SUPBY subentry.

   If the SYSMOD does not exist in the comparison zone, SMP/E includes it in the SYSMOD Comparison report.

   If the SYSMOD exists in the comparison zone and is a function, it may still be included in the SYSMOD Comparison report. This can happen when the function in the input zone has been service-updated. A service-updated function may be at a higher service level than the function currently installed in the comparison zone. Therefore, SMP/E does additional checking for a function that exists in both the input and comparison zones.

   If a function in the input zone has been service-updated, it supersedes the service integrated into it. To determine whether a service-updated function should be reinstalled in the comparison zone, SMP/E checks whether all the SYSMODs superseded by the function exist in the comparison zone. If any of the superseded SYSMODs do not exist in the comparison zone, the service-updated function can be reinstalled and is included in the report.

   Note: When SMP/E checks the global zone to determine whether a service-update is available to be reinstalled, it also checks the superseded information in the global zone SYSMOD entry against the input zone SYSMOD entry. This is done to ensure that the function in the global zone is not at a lower service level than the SYSMOD in the input zone.
2. Next, SMP/E determines whether the SYSMODs included in the report are applicable to the comparison zone.
   • If the SYSMOD is a service-updated function that can be reinstalled, it is applicable to the comparison zone.
   • If the SYSMOD is a base function, it is applicable to the comparison zone if it meets either of these conditions:
     • All the SRELs supported by the input zone are also supported by the comparison zone.
     • Any of the SRELs defined for the SYSMOD are supported by the comparison zone.
       Note: SMP/E checks the global zone SYSMOD entry to determine which SRELs are defined for the SYSMOD. If there is no entry for the SYSMOD in the global zone, SMP/E cannot determine the SYSMOD's SREL.

       If there is at least one SREL in the input zone that is not in the comparison zone and there is no SYSMOD entry in the global zone, the SYSMOD may or may not be applicable to the comparison zone. In this case, SMP/E indicates in the report that the applicability of the SYSMOD is unknown.

   • If the SYSMOD is not a base function, it is applicable to the comparison zone if its FMID meets either of these conditions:
     • It exists in the comparison zone.
     • It has already been deemed applicable during this run of the REPORT SYSMODS command. (If the applicability of the FMID is unknown, the applicability of this SYSMOD is also unknown.)

SMP/E saves all the information gathered in the preceding processing and uses it in the SYSMOD Comparison report and SMPPUNCH output after checking all the SYSMOD entries in the input zone.

If a SYSMOD is identified in the SYSMOD Comparison Report, and SYSTEM or USER HOLDDATA entries exist for that SYSMOD in the global zone for the input zone, those HOLDs are reported in the SYSMOD Comparison HOLDDATA Report.

It is possible for an internal SYSTEM HOLD to appear in the SYSMOD Comparison HOLDDATA Report even though the originating SYSMOD does not appear in the SYSMOD Comparison Report. This situation would occur if the originating SYSMOD is a superseded-only SYSMOD in the input zone and it does not exist in the comparison zone but one of its superseding SYSMODs (which also contains the internal SYSTEM HOLD) is reported in the SYSMOD Comparison Report.

Likewise, it is possible for a SYSMOD to appear in the SYSMOD Comparison Report, but its internal SYSTEM HOLDs are not reported in the SYSMOD Comparison HOLDDATA Report. This situation would occur when the SYSMOD supersedes the originating SYSMOD for an internal SYSTEM HOLD, but the originating SYSMOD already exists in the comparison zone.