General snapshot utility codes

08

Unrecognized component

12

1004

Snapshot facility not active. To correct this problem, define and activate a management set that contains a snapshot template and ensure that the management set is active before attempting to use a snapshot-enabled utility to process snapshots.

12

1008

Snapshot facility not found. A management set containing snapshot definitions is not currently active.

12

1012

Snapshot internal error due to possible storage exhaustion in the XBM region. For assistance, contact BMC Customer Support.

12

1016

Data set not registered for snapshot. An attempt to restart a data set for a snapshot job failed. The restart failed because the data set is not restartable or the data set has been terminated for snapshot processing.

12

1020

Component component Name is not active. Activate the named component and retry the attempted action.

12

1024

The snapshot component is not active. Start the component before attempting snapshot processing.

12

1028

This version of XBM does not support the requested snapshot function or feature. Upgrade XBM to a release that contains the necessary support. For assistance, contact BMC Customer Support.

12

1032

Data set not registered for snapshot. For assistance, contact BMC Customer Support.

12

1036

Data set already registered for snapshot. An attempt was made to begin snapshot processing of a data set that was already active in another snapshot job.

12

1040

Snapshot internal error. For assistance, contact BMC Customer Support.

12

1044

Snapshot internal error due to possible storage exhaustion. For assistance, contact BMC Customer Support.

12

1048

Component componentName not found. Check to make sure that the XBM version and the BMC utility version are compatible. For assistance, contact BMC Customer Support.

12

1052

Data set not registered for snapshot for this job. Verify that the snapshot job completed successfully. For assistance, contact BMC Customer Support.

12

1056

Snapshot not allowed in simulate mode. Simulate mode must be disabled before snapshot processing is initiated.

12

1060

Configuration changed during snapshot processing. Snapshot processing might not be successful.

12

1064

Snapshot processing not supported or currently disabled. Ensure the required components, such as the DB2 component, are authorized and active and that all hooks are enabled. Use the DISPLAY XBM command to ensure that the components are authorized and active. For assistance, contact BMC Customer Support.

12

1068

Component componentName stopped during snapshot processing. The named component was forcibly stopped during the execution of the snapshot job. Consequently, the snapshot job might not be successful.

12

1072

No active configuration defined for use by snapshot processing. You must activate a configuration before a snapshot job can be initiated.

12

1076

No cache defined for use by snapshot processing. You must activate a configuration with an appropriately specified cache before a snapshot job can be initiated.

12

1080

One of the following reasons:

• Data set is Data Shared but PSS support is not available (PSS Component not Active or has suffered a failure).
• Data set is an IMS RECON data set.
• Data set is an IMS OSAM data set with a block size less than 512 bytes.

12

1084

Data set is not pending restart. The data set cannot be restarted because it is already active.

12

1088

Data set cannot be restarted on this XBM subsystem. Make sure the data set is being started on the correct XBM subsystem.

12

1092

Extended format data set not supported. XBM cannot cache extended format data sets.

12

1093

Snapshot internal error. For assistance, contact BMC Customer Support.

12

1096

Snapshot-enabling hardware not available. The SSI component was stopped during a hardware snapshot, or XBM searched for supported intelligent storage devices but could not find any. Make sure the intelligent storage devices in use are supported by XBM.

12

1097

Data set name is invalid or migrated. Verify the data set name is valid and the data set has not been migrated. The data set name must be fully qualified.

12

1098

Snapshot application ended without performing STOP. XBM did not receive STOP notification from the snapshot utility. Check with the snapshot utility to determine whether the snapshot was successful. For assistance, contact BMC Customer Support.

12

1099

Data set deleted. The data set was deleted while in restart pending mode. The snapshot cannot successfully complete without the data set.

12

1101

XBM detected an error situation in which a snapshot STOP request was being processed that had originated from the non-owning XBM subsystem. The snapshot STOP request was ignored.

12

1104

The data set does not support update monitoring requests. For assistance, contact BMC Customer Support.

12

1200

Data set not found in MVS catalog. Verify the data set name.

12

1204

Data set is VSAM and SHARE options are 3,3.

12

1208

The version of DB2 that is being used is not supported by XBM.

12

1300

Connect for preimage reading failed. This reason code signifies an access method error. The access method issues codes that provide information to help you troubleshoot the error. XBM publishes these codes in the job log.

12

1304

Disconnect for preimage reading failed. This reason code signifies an access method error. The access method issues codes that provide information to help you troubleshoot the error. XBM publishes these codes in the job log.

12

1400

Incorrect IMS data set type. XBM supports only VSAM, OSAM, and FastPath IMS data sets.

12

1404

IMS utility lacks data sharing support. XBM declined the request from the IMS utility because that version of the utility does not support data sharing. Contact BMC to obtain a version of the IMS utility that supports data sharing.

12

1408

IMS utility lacks caching API support. XBM declined the request from the IMS utility because that version of the utility does not support the caching API. Contact BMC to obtain a version of the IMS utility that supports the caching API.

12

2016

Unable to read preimage due to internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2024

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2036

I/O error while reading preimage. First, check LOGREC for I/O errors. For assistance, contact BMC Customer Support.

12

2040

Unrecognized I/O request. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2044

Unable to obtain storage. XBM could not obtain storage for cache allocation because an insufficient amount of storage was available. For assistance, contact BMC Customer Support.

12

2048

Snapshot cache read error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2052

Snapshot is not caching due to managed object definition. The cache type attribute is set to NONE on the snapshot template. Change this value to enable caching.

12

2056

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2060

Unsupported media manager option. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2064

Abend occurred during snapshot processing. Check LOGREC and MVS console messages for possible information regarding the abend. Try restarting XBM and the snapshot job. For assistance, contact BMC Customer Support.

12

2068

Read beyond high used relative byte address (RBA). Check your snapshot utility for possible errors. For assistance, contact BMC Customer Support.

12

2072

Preimage stolen from snapshot cache. If a hiperspace cache is in use, the page was stolen by the system. If a data space cache is in use, the cache might have filled. Try specifying a larger data space cache.

12

2076

Preimage stolen from snapshot cache. If a hiperspace cache is in use, the page was stolen by the system. If a data space cache is in use, the cache might have filled. Try specifying a larger data space cache.

12

2080

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2084

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2088

Data set's cache limit for snapshot was exceeded.

Try specifying a larger cache size in one of the following:

• In a snapshot template for snapshot.
• In a management set for I/O caching.

12

2092

Data set's cache limit for snapshot was exceeded.

Try specifying a larger cache size in one of the following:

• In a snapshot template for snapshot.
• In a management set for I/O caching.

12

2096

Cache is full. The snapshot job might not be successful. Define a larger cache to try to prevent this error.

12

2100

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2104

Required cache type not defined or ESO hiperspace error. The configuration does not support the cache type specified in the management set-, or an internal error occurred. For assistance, contact BMC Customer Support.

12

2108

Snapshot internal error. For assistance, contact BMC Customer Support.

12

2112

Snapshot internal error. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

2116

This reason code is issued in response to an error code issued by the sysplex. For information about the cause of the sysplex error code, see the IBM MVS Sysplex Service Reference documentation.

12

2120

An abend occurred during PSS snapshot processing or the PSS hook is disabled. Check LOGREC and MVS console messages for possible information regarding the abend. For assistance, contact BMC Customer Support.

12

2124

The snapshot component of XBM detected an unsupported CISIZE or block size while processing a snapshot request. This problem most likely occurred due to a error in the snapshot request that the utility initiated and sent to XBM.

For assistance, determine the actual CISIZE or block size of the data set and contact BMC Customer Support.

12

2128

The XBM coupling facility (CF) cache is full. To prevent the problem from occurring, do one of the following actions:

• Increase the size of CF cache storage.
• Run the job at a time when less update activity is occurring.
• Run the job when fewer snapshot-enabled utilities are processing jobs.

You can review XBM shutdown information or use the XBM ISPF Monitor for the PSS component to determine the current size and usage information for the XBM CF cache structure.

12

3000

Snapshot detected an XCF error communicating with another XBM. This reason code is issued in response to an error code issued by the sysplex. For information about the cause of the sysplex error code, see the IBM MVS Sysplex Service Reference documentation. For assistance, contact BMC Customer Support.

12

3004

Snapshot detected an error has occurred in another XBM. Review the other XBM subsystem's SYSPRINT and DTRACE output for possible errors and then retry the snapshot job.

12

3008

Snapshot detected a group member without an XBM subsystem, or the XCF group could not be determined.

12

3012

Snapshot detected an error accessing the coupling facility. For information about the cause of the sysplex error code, see the IBM MVS Sysplex Service Reference documentation.

12

3016

Data sharing environment changed, leaving a group member without an XBM. Another member was added to the data sharing group without an active XBM subsystem, or a member's XBM subsystem was stopped.

12

3020

Snapshot detected a timeout while waiting for a response from one or more XBM subsystems. To prevent this error, try increasing the timeout interval located on the PSS Options subpanel.

12

3024

Snapshot detected an unacceptable change in the data sharing group. XBM detected a data sharing I/O to an Image Copy snapshot job that differs from the information contained in the IMAGE COPY PLUS control cards. Make sure data sharing is correctly defined in the job control cards and retry the job.

12

3028

An XBM subsystem controlling a snapshot job has detected an error or timeout condition when communicating with a remote XBM subsystem. The XBM subsystem that detected the error terminates the snapshot processing on that remote XBM system for the data set; however, the controlling XBM subsystem continues to attempt processing the data set with other available XBM subsystems.

This error message is displayed on the remote XBM subsystem for which the snapshot processing of the data set was terminated.

When this error occurs, you can determine the results of the copy by reviewing the utility job output or the SYSPRINT output of the XBM subsystem that controlled the snapshot job.

12

3032

This XBM subsystem terminated the snapshot job because it encountered an error while synchronizing snapshots with another XBM subsystem. The originating XBM subsystem will determine whether to fail the snapshot job because of this error.

This error message is displayed on the remote XBM subsystem upon which the error occurred. When this error occurs, you can determine the results of the copy by reviewing the utility job output or the SYSPRINT output of the XBM subsystem that controlled the snapshot job.

12

4004

Error detected during hardware snapshot process. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

4008

Error detected during hardware snapshot process. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

4012

Error detected during hardware snapshot process. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

4016

Error detected during hardware snapshot process. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

4020

Error detected during hardware snapshot process. Preserve any SVC dumps that result from this error and contact BMC Customer Support.

12

4024

Hardware devices or components not available for snapshot. A hardware snapshot could not be attempted because the registered data set did not reside on a device required for hardware snapshot or the snapshot job was set up incorrectly. If you cannot determine the cause of the error and correct it, contact BMC Customer Support.

12

4028

Hardware devices status has changed or component no longer available. Before snapshot initialization, XBM determined a hardware snapshot was valid. However, by the time the snapshot initialization began, the hardware environment was no longer valid. Check and correct the status of the hardware environment. For assistance, contact BMC Customer Support.

12

4036

Hardware- assisted snapshot not permitted per user option. On the SSI Options subpanel, the option allowing SSI-assisted snapshots is set to NO. To enable SSI-assisted snapshots, change this option to YES.

12

4040

Hardware devices are in intervention-required state. Ensure that hardware devices are operating correctly. For assistance, contact BMC Customer Support.

12

4044

Required hardware operation failed to complete (timed out). The operation failed because the hardware device was busy. Check the status of the hardware device to ensure it is no longer busy, and retry the operation.

12

4052

Error in status of hardware mirror device. XBM attempted a split of the mirror device from the primary device. However, an unexpected status resulted for the mirror device. If you cannot determine the cause of the error and correct it, contact BMC Customer Support.

12

4056

The requested data set snap copy failed. Review accompanying messages to determine what action is required. If you cannot determine the cause of the error and correct it, contact BMC Customer Support.

12

4060

Snapshot internal error. For assistance, contact BMC Customer Support.

12

4064

Snapshot internal error. For assistance, contact BMC Customer Support.

12

4068

Snapshot internal error. For assistance, contact BMC Customer Support.

12

4072

Snapshot internal error. For assistance, contact BMC Customer Support.

12

4076

Snapshot internal error. For assistance, contact BMC Customer Support.

12

4080

Snapshot internal error. For assistance, contact BMC Customer Support.

16

Abend in snapshot utility interface. For assistance, contact BMC Customer Support.

20 (x14)

The installed version of XBM does not support requested function. The function requested by the snapshot utility is not supported by the installed version of XBM. To determine what version of XBM your utility requires, see the documentation for that utility. Upgrade to a newer version of XBM, if necessary. For assistance, contact BMC Customer Support.

103 (x67)

XBM not active. The XBM subsystem was partially initialized when the operation request occurred. Retry the operation.

115 (x73)

The XBM subsystem is not active or is not available in a data sharing environment. Ensure that the XBM subsystem is available before attempting the operation. In a data sharing environment, also ensure that the PSS component is started, that the XBM subsystem is associated with the correct data sharing group, and that the XBMID value has been specified correctly.

117 (x75)

A required component in the XBM subsystem is not active for processing. Start the required component and retry the operation.

142 (x8E)

The PSS component is stopped or the XBMGROUP has not been set.

Ensure that the XCF value in the PSS options identifies the XBMGROUP (and is nonblank) to use and start the PSS component. If the XBMGROUP is not identified, the PSS component will not start.

147 (x93)

Abend in XBM subsystem. For assistance, contact BMC Customer Support.

150 (x96)

User denied access to a secured resource. Obtain authorization to the resource before continuing.

160 (xA0)

An XBM component could not be found. For assistance, contact BMC Customer Support.

199 (xC7)

XBM does not support a function call that was issued by the BMC utility. Ensure that when you upgrade your utility that you also install the latest version of XBM.