SMP/E for z/OS Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Format and explanation of data

SMP/E for z/OS Commands
SA23-2275-01

Figure 1. GZONEMERGE 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 GZONEMERGE REPORT

ENTRY         ENTRY             SUBENTRY      SUBENTRY
TYPE          NAME              TYPE          VALUE     ACTION        REASON

aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff
aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff
aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff
aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff
aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff
aaaaaaaaaaaa  bbbbbbbbbbbbbbbb  cccccccccccc  dddddddd  eeeeeeeeeeee  ffffffff

These are the fields in the report:

ENTRY TYPE
is the entry type.
Value
Description
DDDEF
designates a DDDEF entry
FEATURE
designates the FEATURE entry
FMIDSET
designates an FMIDSET entry
GLOBALZONE
designates a GLOBALZONE entry
HOLDDATA(E)
designates a HOLDDATA entry with a hold category of ERROR
HOLDDATA(F)
designates a HOLDDATA entry with a hold category of FIXCAT
HOLDDATA(S)
designates a HOLDDATA entry with a hold category of SYSTEM
HOLDDATA(U)
designates a HOLDDATA entry with a hold category of USER
OPTIONS
designates an OPTIONS entry
ORDER
designates an ORDER entry
PRODUCT
designates the PRODUCT entry
SYSMOD
designates a SYSMOD entry
UTILITY
designates a UTILITY entry
ZONESET
designates a ZONESET entry
ENTRY NAME
is the name of the entry. This field is blank for the GLOBALZONE entry. This field contains the SYSMOD ID specified on the ++HOLD MCS when the entry is HOLDDATA(E), HOLDDATA(F), HOLDDATA(S), or HOLDDATA(U).
SUBENTRY TYPE
is generally blank but contains a subentry designation when the ENTRY TYPE is GLOBALZONE or one of the HOLDDATA types. For a GLOBALZONE entry, the following values may appear:
  • FMID
  • OPTIONS
  • SREL
  • ZDESC
  • ZONEINDEX

For a HOLDDATA type entry, the only value that can appear is HOLDREASON.

SUBENTRY VALUE
is the value of the field identified by the SUBENTRY TYPE field. This field is generally blank but contains a value for the following subentry types:
  • FMID
  • OPTIONS
  • SREL
  • ZDESC
  • ZONEINDEX
  • HOLDREASON

When HOLDREASON is the subentry type, the subentry value is the reason-id specified in the HOLDDATA entry. For other subentry types, the subentry value is one that was found in the GLOBALZONE entry in the originating global zone.

ACTION
describes what SMP/E did with that entry.
MERGED
The specified entry or subentry was in the FROM GLOBAL ZONE but not in the TO GLOBAL ZONE; so SMP/E added it to the TO GLOBAL ZONE.
NOT FOUND
The specified entry was not found in the FROM GLOBAL ZONE.
NOT MERGED
The specified entry or subentry was in both the FROM GLOBAL ZONE and the TO GLOBAL ZONE.
NOT SELECTED
The specified entry was not a valid FMIDSET name.
RENAMED
The specified entry was renamed.
REPLACED
The specified entry was in both the FROM GLOBAL ZONE and the TO GLOBAL ZONE. Because the level of the FEATURE, PRODUCT, or SYSMOD was higher in the originating global zone than was in the destination global zone, the entry was replaced.
REASON
is the reason associated with the action.

The following table depicts the various ACTION values with their associated REASON values and an explanation of each.

Table 1. GZONEMERGE report REASON values
ACTION REASON Explanation
MERGED blank The entry was merged from the originating global zone into the destination global zone.
NOT FOUND FORFMID VALUE NOT FOUND IN GZONE FMID LIST The entry was not found in the originating global zone's GZONE FMID subentry, but was selected previously by SMP/E as a valid FMID on the FORFMID operand.
NOT MERGED DUPLICATE ENTRY NAME IN TO GLOBAL ZONE The entry was found in both the originating global zone and the destination global zone.
NOT SELECTED FORFMID VALUE NOT A VALID FMIDSET NAME The value specified on the FORFMID operand was not a valid FMIDSET name in the originating global zone.
REPLACED REWORK LEVEL IS GREATER IN FROM GLOBAL ZONE. The SYSMOD, FEATURE, or PRODUCT entry was found in both the originating and destination global zones. Because the level of the SYSMOD, FEATURE, or PRODUCT was higher in the originating global zone than was in the destination global zone, the entry was replaced.

The following table depicts the various ACTION values with their associated REASON values when the ENTRY TYPE is GLOBALZONE. All other reason values are covered in Table 1 and Table 3.

Table 2. GZONEMERGE report REASON values for GZONE entry and subentries
Subentry of GZONE entry ACTION REASON Explanation
FMID NOT MERGED DUPLICATE SUBENTRY VALUE IN TO GZONE ENTRY The subentry value was found in both the originating global zone and the destination global zone.
OPTIONS NOT MERGED DUPLICATE SUBENTRY VALUE IN TO GZONE ENTRY The subentry value was found in both the originating global zone and the destination global zone.
SREL NOT MERGED DUPLICATE SUBENTRY VALUE IN TO GZONE ENTRY The subentry value was found in both the originating global zone and the destination global zone.
ZDESC NOT MERGED DUPLICATE SUBENTRY VALUE IN TO GZONE ENTRY The subentry value was found in both the originating global zone and the destination global zone.
ZONEINDEX NOT MERGED DUPLICATE ZONE INDEX NAME WITH DIFFERENT DSN The subentry value was found in both the originating global zone and the destination global zone. This occurs when the name of the zone index is the same in both global zones, but the associated dsn is different.

The following table depicts the various ACTION values with their associated REASON values when the ENTRY TYPE is ORDER. All other reason values are covered in Table 1 and Table 2.

Table 3. GZONEMERGE report REASON values for ORDER entry
ACTION REASON Explanation
NOT MERGED DUPLICATE ORDERID IN TO GLOBAL ZONE The ORDERID subentry value was found in an existing ORDER entry in the destination zone.
NOT MERGED UNIQUE ORDER ENTRY NAME CANNOT BE GENERATED An ORDER entry was found in the destination zone which has the same name as the ORDER entry in the originating zone. SMP/E was not able to generate a unique ORDER entry name in the destination zone.
RENAMED DUPLICATE ENTRYorigname IN TO GLOBAL ZONE An ORDER entry was found in the destination zone which has the same name as the ORDER entry in the originating zone. SMP/E was able to generate a new ORDER entry name to be used in the destination zone.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014