A0 - Alias record type 0

An Alias Record Type 0 (A0) is created for each alias for an element or LMOD processed during APPLY or RESTORE processing. For hierarchical file system elements, the linkname is indicated in the record.

Multiple A0 records may be produced for the same element or LMOD, because more than one alias can exist for the same element or LMOD.

The purpose of the A0 record is to identify the aliases associated with the changed elements or LMODs associated with this execution of the APPLY or RESTORE command.

The format and contents of this record type are shown in Table 1.
Table 1. Alias record type 0
Field name Position (decimal) Length (decimal) Description
Record type 1 2 The characters 'A0'.
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 Alias Record Type 0 are:
  • Data elements
  • Hierarchical file system elements
  • JAR
  • MAC
  • LMOD
  • PROGRAM
  • SIDEDECK
The data is left-justified and padded with blanks.
Action 23 8 The type of action SMP/E took against this alias of 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 A0 record.

For action type DELETE, this field indicates the target library ddname from which the alias has been deleted.

For action type ADDREP, , this field indicates the target library ddname into which the alias has been added or replaced.

An A0 record is created for every unique library that has an alias change. Elements with multiple SYSLIBs will have the appropriate A0 records created for each unique SYSLIB changed. Therefore, it is possible to have the same element have the same change in alias structure in multiple SYSLIBs.

The data is left-justified and padded with blanks.

This field contains the ddname of the associated target library regardless of whether the allocation was done by a DD statement or DDDEF.

Alias 39 1023 This is an alias name associated with this SMP/E element or LMOD. If the element is a hierarchical file system element, then the linkname is placed in this field. The data is mixed-case characters and is left-justified and padded with binary zeros.

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

For example, suppose that SMP/E adds load module LMODA, which has two aliases, LMA and LMDA. Load module LMODA has a side deck. Figure 1 shows the A0 records created for LMODA:
Figure 1. Example of alias record type 0 records
         1         2         3         4         5         6         7         8
----+----0----+----0----+----0----+----0----+----0----+----0----+----0----+----0
A0LMODA   LMOD        ADDREP  LINKLIB LMA
A0LMODA   LMOD        ADDREP  LINKLIB LMDA
A0LMODA   SIDEDECK    ADDREP  SIDELIB LMA
A0LMODA   SIDEDECK    ADDREP  SIDELIB LMDA