BACKUP entries (SMPSCDS)

BACKUP entries are a collection of target zone entries that are copied to the SMPSCDS during APPLY processing before they are updated by inline JCLIN, a ++MOVE MCS, or a ++RENAME MCS, or before they are deleted by an element MCS with the DELETE operand. A BACKUP entry is also created for a MOD entry if a SYSMOD being installed provides a ++MOD statement that either changes the distribution library for the module or adds the module to an existing load module.

As SMP/E processes the inline JCLIN for a given SYSMOD, it determines which entries will be affected by that JCLIN. Before making the changes, it saves a copy of each of those entries on the SMPSCDS.
Likewise, as SMP/E processes the ++MOVE, ++RENAME, and element MCSs in a given SYSMOD, it determines which entries will be updated or deleted. Before updating or deleting the entries, it saves a copy of each of those entries on the SMPSCDS.

Besides saving copies of the affected entries, SMP/E also saves a SYSMOD entry on the SMPSCDS to indicate which entries were added by JCLIN, updated by JCLIN or an MCS statement in the SYSMOD, or deleted by an MCS statement in the SYSMOD. Each entry is associated with only one SYSMOD. The entries associated with a SYSMOD are called the BACKUP entries for that SYSMOD. BACKUP entries consist of:

A SYSMOD entry indicating what entries were added, deleted, or updated
ASSEM entries for updated target zone ASSEM entries
JAR entries for deleted JAR entries
LMOD entries for updated target zone LMOD entries
MAC entries for updated or deleted target zone MAC entries
MOD entries for updated or deleted target zone MOD entries
SRC entries for updated or deleted target zone SRC entries
Data element entries for deleted target zone data element entries
Hierarchical file system entries for deleted target zone hierarchical file system entries
DLIB entries for updated target zone DLIB entries

SMP/E provides access to the BACKUP entries as a group—for example, through the LIST command—but it does not provide access to the individual entries or subentries.

Subentries

The subentries in the BACKUP entries are the same as those in the various entry types that are copied. For more information, see the sub-topic in this topic describing each entry.

LIST Examples

To list the BACKUP entries for all the SYSMODs in the SMPSCDS, you can use the following commands:

SET      BDY(TGT1)          /* Set to requested tgt zone. */.
LIST     BACKUP             /* List all BACKUP entries.   */.

To list the BACKUP entries for a specific SYSMOD, you can use these commands:

SET      BDY(TGT1)          /* Set to requested tgt zone. */.
LIST     BACKUP(UZ12345,    /* List only BACKUP entries   */
                UZ12346)    /* for these two SYSMODs.     */.

The format of the LIST output for each group of BACKUP entries is the same for both of these commands. The only difference is the number of SYSMODs for which BACKUP entries are listed.

When you list the BACKUP entries for a SYSMOD, the first entry in the output is a summary entry for the SYSMOD, which indicates the date and time the SYSMOD was applied, as well as which entries were added or updated as a result of applying the SYSMOD. This is followed by a listing of all the existing target zone entries affected by this SYSMOD, before they were updated. Nothing is listed for added entries, because no entry existed before the SYSMOD was installed.

Figure 1 is a partial example of LIST output for BACKUP entries. It shows the summary records, but not all the backup copies of the entries modified by the SYSMOD. This is because the format of those copies is the same as the format for the original target zone entries.

UCLIN Examples

You can use the DEL UCL statement to delete BACKUP entries from the SMPSCDS. This can be helpful if you plan to do an APPLY followed by ACCEPT when several target libraries have been created from the same distribution library.

When a SYSMOD is accepted into a distribution zone, the entries associated with the SYSMOD are automatically deleted from the SMPSCDS for the RELATED target zone. However, even if the SYSMOD was also applied to other target zones created from the same distribution zone, SMP/E does not clean up the SMPSCDS data sets for the other target zones.

To delete the entries from these data sets, you can accept the SYSMOD and name these other target zones as the RELATED zone. However, this updates the distribution library each time, which is time-consuming and can use up space in the distribution library data set.

Instead, you can use the DEL command to delete these entries without updating the distribution library. To determine which entries to specify, check the SMPLOG data set to see which ones SMP/E deleted during ACCEPT processing.

Note: You can also use the CLEANUP command to delete BACKUP entries without specifying them individually. For more information about the CLEANUP command, see SMP/E for z/OS Commands.

Figure 1. BACKUP entries: sample LIST output

PAGE nnnn  - NOW SET TO zzzzzz ZONE nnnnnnn  DATE mm/dd/yy TIME hh:mm:ss SMP/E 36.nn SMPLIST OUTPUT

SMPSCDS       BACKUP ENTRIES

  NAME

UZ12345   DATE/TIME APP   = 07.100 08:15:00
          ASSEM    (ADD)  = ASSEM01   ASSEM02   ASSEM03
          LMOD     (ADD)  = LMOD01    LMOD02
          MACRO    (ADD)  = MAC01
          MOD      (ADD)  = MOD01     MOD02     MOD03     MOD04
          SRC      (ADD)  = SRC01     SRC02     SRC03
          DLIB     (ADD)  = DLIB01
          ASSEM    (DEL)  = ASSEM04   ASSEM05
          LMOD     (DEL)  = LMOD03    LMOD04    LMOD05
          MACRO    (DEL)  = MAC05     MAC09
          MOD      (DEL)  = MOD10     MOD11     MOD12
          SRC      (DEL)  = SRC11
          ASSEM    (UPD)  = ASSEM91   ASSEM92   ASSEM93
          LMOD     (UPD)  = LMOD9A    LMOD9B
          MACRO    (UPD)  = MAC99
          MOD      (UPD)  = MOD99
          SRC      (UPD)  = SRC99
          DLIB     (UPD)  = DLIB99
...
... deleted entries for ASSEM04 ASSEM05
...                     LMOD03  LMOD05  LMOD05
...                     MAC05   MAC09
...                     MOD10   MOD11   MOD12
...                     SRC11
... updated entries for ASSEM91 ASSEM92 ASSEM93
...                     LMOD9A  LMOD9B
...                     MAC99
...                     MOD99
...                     SRC99
...                     DLIB99
... would follow here - format is as in sample
... for each target zone entry
...