When processing ++SRC/++SRCUPD and ++MAC/++MACUPD elements, it is assumed that previous updates are still there and will be incorporated with the current update. Therefore, a SYSMOD need not state a relationship (PRE or SUP) to a previous update. The SYSMOD being installed need not specify on the PRE or SUP operand the UMIDs associated with the corresponding target system element. If any element UMIDs in the target system are not specified in the SUP or PRE operands, a MODID check warning condition is raised and is reported to the user.

The MODID check warning does not result in the termination of the SYSMOD being installed, and the update is installed on the target system. The warning is given because SMP/E is unable to determine with certainty that the two modifications in fact have a relationship or that there is an intersection. Thus, it is the responsibility of the developer or the service team (that is, whoever supplies the update type SYSMOD) to make sure that this SYSMOD specifies the correct relationships with all previous SYSMODs.

When processing ++JAR/++JARUPD elements, the SYSMOD must identify as a prerequisite or supersede the SYSMOD that last replaced the most recently selected ++JAR element (the RMID for the element). Therefore, the SYSMOD must specify as a PRE or SUP, the SYSMOD that last supplied a ++JAR for the element.

In addition, the SYSMOD supplying the ++JAR/++JARUPD elements must identify as a prerequisite or supersede all SYSMODs which have previously updated the most recently selected ++JAR element (the UMID for the element). In other words, the current SYSMOD must specify as a PRE or SUP, all SYSMODs that have supplied ++JARUPDs for the element since it was last replaced.