E0 - Element record type 0

An Element Record Type 0 (E0) is created for each element or LMOD that changed in a target library during APPLY or RESTORE processing. The term changed in this context refers to an element or LMOD that been deleted or replaced in a target library as a result of SMP/E processing. See Valid action types for more information.

The purpose of the E0 record is to identify the changed elements or LMODs in the associated target libraries identified by the L0 and L1 records.

The format and contents of this record type are shown in Table 1.

Table 1. Element record type 0
Field name	Position (decimal)	Length (decimal)	Description
Record type	1	2	The characters 'E0'.
Name	3	8	The name of an SMP/E element or LMOD processed during APPLY or RESTORE processing. The data is left-justified and padded with blanks.
Type	11	12	The type of SMP/E element or LMOD processed during APPLY or RESTORE processing. The valid element types for an Element Record Type 0 are: data elements hierarchical file system elements JAR LMOD MAC PROGRAM SIDEDECK SRC The data is left-justified and padded with blanks.
Action	23	8	The type of action SMP/E took against this element or LMOD during APPLY or RESTORE processing. Valid values are ADDREP and DELETE. This data is left-justified and padded with blanks.
DD name	31	8	The ddname associated with the target library associated with the named element or LMOD in this E0 record. The data is left-justified and padded with blanks. For cross-zone elements, this field indicates the SMP/E generated ddname associated with the SYSLIB for this element. The associated L0 record also contains the related true name for the SYSLIB in the cross-zone. For action type DELETE, this field indicates the target library ddname from which the element has been deleted. For action type ADDREP, this field indicates the target library ddname into which the element has been added or replaced. An E0 record is created for every unique library that has an element change. Elements with multiple SYSLIBs will have the appropriate E0 records created for each unique SYSLIB changed. Therefore, it is possible to have the same element have the same change take place in multiple SYSLIBs. This field contains the ddname of the associated target library regardless of whether the allocation was done by a DD statement or DDDEF.

For LMODs that have an associated side deck, there is one E0 record created for each LMOD (indicated by LMOD in the element type field of the E0 record) and one E0 record created for the LMOD's side deck (indicated by SIDEDECK in the element type field of the E0 record). Both the E0 record with element type LMOD and the E0 record with element type SIDEDECK contain the same name (the LMOD's name) in the name field of the E0 record.

For example, suppose that SMP/E adds load module LMODA, which has a SIDEDECK. Figure 1 shows the E0 records created for LMODA:

Figure 1. Example of element record type 0

         1         2         3         4         5         6         7         8
----+----0----+----0----+----0----+----0----+----0----+----0----+----0----+----0
E0LMODA   LMOD        ADDREP  LINKLIB
E0LMODA   SIDEDECK    ADDREP  SIDELIB