Format and explanation of data

Figure 1. MOVE/RENAME/DELETE report: standard format

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

             SMP/E MOVE/RENAME/DELETE REPORT FOR xxxxxxx PROCESSING

ELEMENT   ELEMENT   SYSMOD
 TYPE      NAME      NAME    ACTION                                                   COMMENT

aaaaaaaa  bbbbbbbb  ccccccc  ddddddddddddddddddddddddddddddddddddddddddddddddddddddd  eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
aaaaaaaa  bbbbbbbb  ccccccc  ddddddddddddddddddddddddddddddddddddddddddddddddddddddd  eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
aaaaaaaa  bbbbbbbb  ccccccc  ddddddddddddddddddddddddddddddddddddddddddddddddddddddd  eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
aaaaaaaa  bbbbbbbb  ccccccc  ddddddddddddddddddddddddddddddddddddddddddddddddddddddd  eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
aaaaaaaa  bbbbbbbb  ccccccc  ddddddddddddddddddddddddddddddddddddddddddddddddddddddd  eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

These are the fields in the report:

xxxxxxx

is the command being processed:

ACCEPT
ACCEPT CHECK
APPLY
APPLY CHECK
RESTORE
RESTORE CHECK

ELEMENT TYPE

is the type of element that was changed: MAC, MOD, SRC, or LMOD.

ELEMENT NAME

is the name of an element that was changed.

SYSMOD NAME

identifies the SYSMOD containing the MCS that changed the element.

ACTION

is the type of change that was made:

ALIAS DELETED FROM SYSLIB syslib - alias

The load module alias was deleted from the indicated library during APPLY processing.

Note:

A long alias spans several lines.
An alias is enclosed in apostrophes if it contains a character other than uppercase alphabetic, numeric, national ($, #, or @), slash, plus, hyphen, period, and ampersand, or it spans several lines.

ALIAS NOT DELETED FROM SYSLIB syslib - alias

The load module alias was not deleted from the indicated library during APPLY processing.

Note:

A long alias spans several lines.
An alias is enclosed in apostrophes if it contains a character other than uppercase alphabetic, numeric, national ($, #, or @), slash, plus, hyphen, period, and ampersand, or it spans several lines.

CHANGED DISTLIB FROM distlib1 TO distlib2

The DISTLIB subentry of the element entry was changed during APPLY or RESTORE processing.

CHANGED SYSLIB FROM syslib1 TO syslib2

The SYSLIB subentry of the element entry was changed during ACCEPT processing.

DELETED FROM SYSLIB syslib1

The load module was deleted from the indicated library during APPLY processing.

DISTLIB NOT CHANGED FROM distlib1 TO distlib2

The DISTLIB subentry of the element was not changed during APPLY or RESTORE processing.

LMOD ENTRY NOT RENAMED TO newname

The indicated LMOD entry was not renamed during ACCEPT processing.

LMOD ENTRY RENAMED TO newname

The indicated LMOD entry was renamed during ACCEPT processing.

MOD aaaaaaaa IN ZONE bbbbbbb UPDATED

The indicated cross-zone module is part of a load module renamed by the ++RENAME statement during APPLY or RESTORE processing. The cross-zone MOD entry has been updated to reflect the new load module name.

MOD aaaaaaaa IN ZONE bbbbbbb NOT UPDATED

The indicated cross-zone module is part of a load module renamed by the ++RENAME statement during APPLY or RESTORE processing. The cross-zone MOD entry was not updated to reflect the new load module name.

MOVED FROM DISTLIB distlib1 TO distlib2

The element was moved to a different distribution library during ACCEPT processing.

MOVED FROM SYSLIB syslib1 TO syslib2

The element was moved to a different target library during APPLY or RESTORE processing.

NOT DELETED FROM SYSLIB syslib1

The load module was not deleted from the indicated library during APPLY processing.

NOT MOVED FROM DISTLIB distlib1 TO distlib2

The element was not moved during ACCEPT processing.

NOT MOVED FROM SYSLIB syslib1 TO syslib2

The element or load module was not moved during APPLY or RESTORE processing.

NOT RENAMED TO newname IN SYSLIB syslib1

The load module was not renamed in the indicated library during APPLY or RESTORE processing.

RENAMED TO newname IN SYSLIB syslib1

The load module was renamed in the indicated library during APPLY or RESTORE processing.

SIDE DECK ALIAS DELETED FROM LIBRARY ddname - alias

The side deck alias was deleted from the indicated library during APPLY processing.

SIDE DECK DELETED FROM LIBRARY ddname

The side deck was deleted from the indicated library during APPLY processing.

SIDE DECK NOT RENAMED TO newname IN LIBRARY ddname

The side deck was not renamed in the indicated library during APPLY or RESTORE processing.

SIDE DECK RENAMED TO newname IN LIBRARY ddname

The side deck was renamed in the indicated library during APPLY or RESTORE processing.

SYSLIB NOT CHANGED FROM syslib1 TO syslib2

The SYSLIB subentry of the element was not changed during ACCEPT processing.

SYSLIB syslib1 DELETED FROM LMOD ENTRY

The SYSLIB subentry was deleted from the indicated LMOD entry during ACCEPT processing.

SYSLIB syslib1 NOT DELETED FROM LMOD ENTRY

The SYSLIB subentry was not deleted from the indicated LMOD entry during ACCEPT processing.

COMMENT

provides additional information about processing:

ALIAS(ES) alias…

For ++DELETE processing, the indicated aliases were deleted from the target library. For ++MOVE processing, they were moved to the new target library.

Note:

A long alias spans several lines.
Multiple aliases are separated by a comma followed by a blank (", ").
An alias is enclosed in apostrophes if it contains a character other than uppercase alphabetic, numeric, national ($, #, or @), slash, plus, hyphen, period, and ampersand, or it spans several lines.

ALIAS GREATER THAN 8 CHARACTERS

The ++DELETE statement attempted to delete an alias without deleting the associated load module, which resides in a PDSE. Because the alias to be deleted was more than 8 characters long, it could not be deleted.

ALIAS NOT IN SYSLIB

The alias to be deleted was not in the indicated target library.

ALREADY CHANGED

The DISTLIB or SYSLIB subentries for the element or load module has already been changed.

ALREADY DELETED

The indicated load module has already been deleted.

ALREADY MOVED

The element or load module has already been moved.

ALREADY RENAMED

The indicated load module has already been renamed.

ATTEMPTED UPDATE FAILED

Because of errors during cross-zone processing, the attempted cross-zone update was not made.

COPY FAILED

The copy for a load module or element failed during ++MOVE processing.

CSI RESOURCE UNAVAILABLE

Cross-zone processing was not done, because SMP/E could not obtain access to the CSI data set containing the cross-zone.

DEFERRED XZLINK SPECIFIED

Cross-zone processing was not done, because the XZLINK value of the cross-zone is DEFERRED.

FMID MISMATCH

The FMID of the element to be moved must match either the FMID of the SYSMOD containing the ++MOVE MCS, or an FMID specified on the ++MOVE MCS.

HAS ASSOCIATED SYMBOLIC LINKS

++MOVE or ++RENAME processing for a program element has been terminated, because the program element has symbolic links defined in its link-edit control statements.

LIBRARIES NOT AVAILABLE

Libraries needed for ++MOVE, ++RENAME, or ++DELETE processing were not available.

LINK EDIT FAILED

The link-edit for a load module or element failed during ++MOVE processing.

MISSING ALIAS(ES) alias…

The indicated aliases were missing from the target or distribution library, even though the element or LMOD entry indicated that they should exist.

Note:

A long alias spans several lines.
Multiple aliases are separated by a comma followed by a blank (", ").
An alias is enclosed in apostrophes if it contains a character other than uppercase alphabetic, numeric, national ($, #, or @), slash, plus, hyphen, period, and ampersand, or it spans several lines.

MOD DOES NOT CONTAIN XZLMOD

The LMOD from the set-to zone has an XZMOD subentry indicating that it contains the cross-zone module. SMP/E cannot update the cross-zone module's XZLMOD record to show that the LMOD was renamed, because the cross-zone module does not contain an XZLMOD subentry for the renamed LMOD.

If the LMOD does contain the cross-zone module, use UCLIN to add an XZLMOD subentry for the renamed LMOD to the cross-zone MOD entry. If the LMOD does not contain the cross-zone module, use UCLIN to remove the XZMOD subentry for the cross-zone module from the LMOD entry.

Note: If you use UCLIN to update the cross-zone connections, make sure the TIEDTO subentries of the zone definition entry are still synchronized.

MOD ENTRIES UPDATED

For ++DELETE processing, the LMOD subentries in the MOD entries have been changed and the LMOD entry has been deleted. For ++RENAME processing, the LMOD subentries in the MOD entries have been changed.

NEW NAME EXISTS

An LMOD entry already exists (as either an LMOD entry or in one of the LMOD's SYSLIBs) for the new name specified on a ++RENAME statement.

NOT FOUND

The definition side deck for the named load module was not found in the side deck library, or no entry was found for the element or load module named.

NOT IN ALL SYSLIBS

The load module was not in all the target libraries indicated in the LMOD entry.

NOT IN CURRENT DISTLIB

The element was not in the distribution library named. The DISTLIB on the MCS does not match the DISTLIB subentry in the element entry.

NOT IN CURRENT SYSLIB

The element or load module was not in the target library named. The SYSLIB on the MCS does not match the SYSLIB subentry in the element or LMOD entry.

NOT INSTALLED

The element or load module named was not installed or being installed.

PREVIOUS ERROR

A previous error prevented SMP/E from updating the cross-zone MOD XZLMOD subentry to indicate that the set-to LMOD was renamed. Use UCLIN to update the XZLMOD subentry for the renamed LMOD.

SYSLIB SUBENTRY NOT FOUND

The SYSLIB subentry of the element was not changed, because the SYSLIB subentry was not found in the element entry. This situation is common during ACCEPT processing for elements that are packaged in a totally copied library.

SYSMOD TERMINATED

The SYSMOD containing the ++MOVE, ++RENAME, or ++DELETE statement previously failed.

XZLMOD SUBENTRY REPLACED

Cross-zone processing has been successful and the MOD entry has been updated with the load module name.

Note: The report is limited to reporting on the first 20 aliases processed for a particular element. For example, suppose a load module having 23 aliases is being moved by a ++MOVE statement. The first 20 aliases moved appear in the MOVE/RENAME/DELETE report.