You can use the Command Control Interface (CCI) or Business Continuity Manager (BCM) operation logs to troubleshoot ShadowImage for Mainframe (SIz) operations. The following procedure describes CCI and BCM error codes and how to locate and interpret them.
- Open one of the following:
- The CCI or BCM window
- The CCI or BCM operation log file
- In the log that is displayed, locate the log entry or error code you are investigating. You can use the SSB1/SSB2 error code combination to determine the cause of the error. The error codes are shown to the right of the equal symbol (=) in the log. The SSB1 code is the last four alphanumeric characters to the left of the comma (,). The SSB2 code is the last four alphanumeric characters to the right of the comma (,).
- CCI or BCM window sample log entry:
It was rejected due to SKEY=0x05, ASC=0x20,SSB=0xB9E1,0xB901 on Serial#(64015)
SSB1 code: B9E1
SSB2 code: B901
- CCI or BCM operation log file sample error code:
11:06:03-37897-10413- SSB = 0xb9a0,2089
SSB1 code: B9A0
SSB2 code: 2089
- CCI or BCM window sample log entry:
- Locate the description of the SSB2 error code in the following table.
For details about errors that are not listed in this table, contact customer support.
For details about the CCI error codes, see the Command Control Interface User and Reference Guide.
For details about the BCM error codes, see the Business Continuity Manager User Guide.
SSB2 error codes for ShadowImage for Mainframe: SSB1 = 2E31, B9A0, B9A1, B9A2, B9A5, B9A6, B9AE, and B9AF
|
Error code (SSB2) |
Description |
|---|---|
|
- |
An error occurred during an SIz pair task. |
|
200D |
The pair task was rejected because the specified DP-VOL is not associated with a pool. |
|
201B |
The CTG pair-split was rejected because the URz pair is other than PAIR/PSUS/SSUS/PSUE. The URz S-VOL was the SIz P-VOL included in the CTG on which the pair-split is being performed. |
|
2026 |
The Quick Restore operation was rejected because the cache mode of the specified P-VOL is different from the cache mode of the external S-VOL. |
| 203B | The Quick Restore operation was rejected because volumes with and without Extent Space Efficient (ESE) attribute are mixed in the specified P-VOL and S-VOL. |
|
2043 |
The volume you specified as a P-VOL was a volume using two mirrors included in a 3-URz-DC multi-target or cascade configuration. The operation was rejected because the volume was used as a URz data volume. |
|
2044 |
The volume you specified as an S-VOL was a volume using two mirrors included in a 3-URz-DC multi-target or cascade configuration. The operation was rejected because the volume was used as a URz data volume. |
|
2047 |
The pair task was rejected because the current microcode version does not support the specified P-VOL capacity. |
|
2048 |
The pair task was rejected because the current microcode version does not support the specified S-VOL capacity. |
|
204F |
The pair task was rejected because the volume specified as the S-VOL was used as a Volume Migration source volume and the migration processing could not be suspended. Complete the migration processing of Volume Migration, and then retry the task. |
|
205B |
The pair was not created because the specified MU number is in use. |
|
2060 |
The volume you specified as an SIz P-VOL was a volume of a URz pair. The pair task was rejected because the status of the URz pair is not in the required status. |
|
2061 |
The volume you specified as an SIz S-VOL was a volume of a URz pair. The pair task was rejected because the status of the URz pair is not in the required status. |
|
2067 |
Volumes of the specified pair are shared by TCz and URz.
Cause of the error could be either of the following:
|
|
2071 |
The pair task was rejected because the volume specified as the P-VOL was used as a Volume Migration source volume and the migration processing could not be suspended. Complete the migration processing of Volume Migration, and then retry the task. |
|
2078 |
Because the specified P-VOL was also a URz P-VOL for delta resync, one of the following errors occurred:
|
|
2079 |
The pair task was rejected because the specified S-VOL was also a URz P-VOL for delta resync. |
|
2086 |
The pair task was rejected because the initialization process is being performed. |
|
2089 |
The Quick Restore operation was rejected because you are formatting the volume you specified as a P-VOL using Quick Format. For more information about formatting volumes using Quick Format, see the Provisioning Guide for your storage system. |
|
208A |
The Quick Restore operation was rejected because you are formatting the volume you specified as an S-VOL using Quick Format. For more information about formatting volumes using Quick Format, see the Provisioning Guide for your storage system. |
|
2097 |
The Quick Restore operation was rejected for one of the following reasons:
|
|
2098 |
The Quick Restore operation was rejected because all the following conditions were met when you performed the Quick Restore operation.
|
|
209A |
The Quick Restore operation was rejected because all the following conditions were met when you performed the Quick Restore operation.
|
|
209E |
The pair task was rejected because the volume you specified as the P-VOL is a FICON® Data Migration volume. |
|
20A2 |
The create pair task was rejected because the P-VOL is a DP-VOL for which the capacity is increasing. |
|
20A3 |
The pair was not created because the S-VOL is a DP-VOL for which capacity is increasing. |
|
20A9 |
The pair task was rejected because TIA is using the specified CTG ID. |
|
20AA |
The pair task was rejected because the volume specified as the P-VOL is a DP-VOL for which zero pages are being reclaimed. |
|
20AB |
The pair task was rejected because the volume specified as the S-VOL is a DP-VOL for which zero pages are being reclaimed. |
|
20B0 |
The pair task was rejected because the volume you specified as the P-VOL is a DP-VOL and its capacity is increasing. |
|
20B1 |
The pair task was rejected because the volume you specified as the S-VOL is a DP-VOL and its capacity is increasing. |
|
20B4 |
The pair task was rejected because the volume you specified as the P-VOL is a DP-VOL that is not associated with a pool. |
|
20B5 |
The pair task was rejected because the volume you specified as the S-VOL is a DP-VOL that is not associated with a pool. |
|
20BD |
The pair task was rejected because the emulation type of the volume you specified as the P-VOL is 3390-V. |
|
20BE |
The pair task was rejected because the emulation type of the volume you specified as the S-VOL is 3390-V. |
|
20C5 |
The command was rejected because you were in the process of turning off the storage system's power. |
|
20C9 |
The emulation type of the P-VOL was 3390-A, and the pair task is rejected because of one of the following reasons:
|
|
20CA |
The S-VOL's emulation type was 3390-A, and the pair task was rejected because of one of the following reasons:
|
|
20D0 |
The P-VOL rejected the paircreate CCI command because the DP pool is initializing in the DP-VOL. |
|
20D1 |
The S-VOL rejected the paircreate CCI command because the DP pool is initializing in the DP-VOL. |
|
20D6 |
The pair task was rejected because Compatible Software for IBM® FlashCopy® SE is using the P-VOL or the P-VOL is a TSE volume. |
|
20D7 |
The pair task was rejected because the S-VOL is a TSE volume. |
|
20DC |
You cannot use the specified P-VOL for SIz, because it is being used in SI. |
|
20E4 |
The command was rejected because the SIz CTG pair created by BCM or PPRC and the SIz CTG pair created by CCI cannot co-exist when the UR S-VOL and the SI P-VOL share a volume. |
|
20E6 |
CCI cannot execute CTG pair-split on a reserved CTG. |
|
20E9 |
The pair task was rejected because the volume you specified as the P-VOL is a S-VOL for an existing pair, and the volume you specified as the S-VOL is the P-VOL for another existing pair. |
|
20F0 |
The pair task was rejected because Soft Fence is set for the specified primary volume. |
|
20F1 |
The pair task was rejected because Soft Fence is set for the specified secondary volume. |
|
22F6 |
The pair task was rejected because the volume specified as the P-VOL is a target volume of Compatible FlashCopy® V2. |
|
22F7 |
The pair task was rejected because the volume specified as the S-VOL is a source or target volume of Compatible FlashCopy® V2. |
|
22F9 |
The Quick Restore or Reverse Copy operation was rejected because the volume specified as the S-VOL is a source or target volume of Compatible FlashCopy® V2. |
|
2301 |
The pair task was rejected because there is not a sufficient amount of installed shared memory or SIz is not installed. |
|
2306 |
The pair task was rejected because the LBA size of the specified P-VOL is not the same as the size of the specified S-VOL. |
|
2309 |
The pair was not created because the number of pairs exceeded the maximum number of pairs. |
|
230A |
The pair was not created because the volume you specified as the S-VOL is the P-VOL of the SIz pair that has an MU number of 0. |
|
230B |
The pair task was rejected because the pair is being suspended or deleted. |
|
2310 |
One of the following occurred:
|
|
2312 |
The pair task was rejected because the volume specified as the S-VOL is online from the host. |
|
2314 |
The pair was not created because the volume you specified as the S-VOL is the S-VOL of another SIz pair that has been split (PSUS or SSUS/SUSPOP status). |
|
231F |
The Quick Restore or Reverse Copy operation was rejected because the P-VOL of the specified pair is online from the host. |
|
2322 |
The pair task was rejected because there is not a sufficient amount of installed shared memory or initialization is not completed. |
|
2323 |
The Quick Restore operation was rejected because the combination of the pool ID and CU number associated with the specified P-VOL and S-VOL is a mixture of even and odd numbers. |
|
2324 |
The pair task was rejected because the number of slots of the volume you specified as the P-VOL exceeded the upper limit. |
|
2325 |
The pair task was rejected because the number of slots of the volume you specified as the S-VOL exceeded the upper limit. |
|
2326 |
The pair was not created because the volume you specified as the P-VOL had already had three S-VOLs. |
|
2327 |
The pair was not created because the node volume specified as the P-VOL had already had two S-VOLs. |
|
2328 |
The pair task was rejected because the pair configuration exceeded the number of the layers of the cascade configuration. |
|
2329 |
The pair task was rejected because the volume you specified as the S-VOL is the S-VOL of an existing pair. |
|
232A |
The pair was not created because pairs that would exceed the license capacity were going to be created. |
|
232F |
The pair task was rejected because the volume you specified as the P-VOL is allocated as the destination of the Volume Migration. |
|
2331 |
The pair task was rejected because the capacity of the specified P-VOL is not the same as the capacity of the S-VOL. |
|
2332 |
The pair was not created because the volume you specified as the P-VOL had already had three S-VOLs. |
|
2333 |
The pair task was rejected because the volume you specified as the P-VOL is not the P-VOL of the existing pair. |
|
2334 |
The pair task was rejected because of either of the following reasons:
|
|
2335 |
The pair task was rejected because the volume specified as the S-VOL had an emulation type that CCI does not support. |
|
2336 |
The pair task was rejected because the emulation types of the specified P-VOL and S-VOL were different. |
|
2337 |
The pair task was rejected because the volume specified as the P-VOL had already been the S-VOL. |
|
233A |
The pairresync CCI command was rejected because the volume you specified as the P-VOL is not an SIz P-VOL. |
|
233B |
The pair task was rejected because the volume you specified as the S-VOL is a root volume. |
|
233C |
The pair task was rejected because the volume you specified as the S-VOL is a node volume, and the volume you specified as the P-VOL is not the P-VOL for the specified S-VOL. |
|
233D |
The pairsplit CCI command was rejected because the specified P-VOL and S-VOLs were a L2 pair, and the L1 pair is not split (PSUS or SSUS/SUSPOP status). |
|
233E |
The pair task was rejected because the volume you specified as the P-VOL is being used as another SIz P-VOL, and also that pair's S-VOL is used as a TCz P-VOL. |
|
233F |
The pair task was rejected because the volume you specified as the S-VOL is the TCz P-VOL, and the pair is not in PSUS/SSUS/PSUE status. |
|
2342 |
The pair task was rejected because the volume you specified as the S-VOL is the destination of the Volume Migration. |
|
2343 |
The pair was not created because the volume you specified as the S-VOL had already been an S-VOL. |
|
2344 |
The pair task was rejected because the volume you specified as the S-VOL for SIz pair tasks is not an S-VOL. |
|
2346 |
The volume you specified as an SIz S-VOL is a TCz P-VOL. The pair task was rejected because the TCz pair is not in the required status. |
|
2347 |
The volume you specified as an SIz S-VOL was a TCz S-VOL. The pair task was rejected because the TCz pair is not in the required status. |
|
234A |
Creation of the cascaded pair was rejected because the volume specified as the S-VOL was an intermediate volume. |
|
234B |
The pair task was rejected because the volume you specified as the S-VOL is the volume of the Volume Migration. |
|
2350 |
The pair task was rejected because the specified P-VOL and the S-VOL for SIz pair tasks is not a pair. |
|
2351 |
The pair task was rejected because the volume you specified as the P-VOL and the volume you specified as the S-VOL are the same. |
|
2352 |
The pair was not restored because the specified P-VOL and S-VOLs is online to the host. |
|
2353 |
The pair was not deleted because the specified P-VOL and S-VOLs are in the process of being Quick Split. |
|
2354 |
The pairresync CCI command was rejected because the P-VOL and S-VOLs is in the process of being Steady Split. |
|
2357 |
The pair creation was rejected because the volume you specified as the S-VOL is the P-VOL of the pair you are splitting or the P-VOL of the pair you are reverse resynchronizing. |
|
2358 |
The pairresync CCI command was rejected because the volume you specified as the S-VOL is the P-VOL of the splitting pair. |
|
235B |
The volume you specified as a P-VOL is a TCz P-VOL. The Reverse Copy or Quick Restore operation was rejected because the TCz pair is not in PSUS/SSUS/PSUE status. |
|
235C |
The volume you specified as the P-VOL is a TCz S-VOL. The Reverse Copy or Quick Restore operation was rejected because the TCz pair is not in PSUS/SSUS/PSUE status. |
|
235D |
The volume you specified as an S-VOL was a TCz P-VOL. The Reverse Copy or Quick Restore operation was rejected because the TCz pair is not in PSUS/SSUS/PSUE status. |
|
236C |
The reverse resynchronization was rejected because the volume you specified as the P-VOL has the S-VOL Disable attribute assigned by the Data Retention Utility. |
|
236D |
The pair task was rejected because the volume you specified as the S-VOL has the S-VOL Disable attribute assigned by the Data Retention Utility. |
|
2370 |
The pair task was rejected because the volume you specified as the P-VOL is not mounted. |
|
2371 |
The pair task was rejected because the volume you specified as the P-VOL is blocked. |
|
2372 |
The pair task was rejected because the volume you specified as the P-VOL is being formatted or shredded. |
|
2373 |
The pair task was rejected because the volume you specified as the P-VOL is a command device. |
|
2374 |
An SIz pair cannot be created, because the differential data management specified at the pair creation differs from that for a different SIz pair that uses the specified P-VOL. |
|
2380 |
The pair task was rejected because of one of the following reasons:
|
|
2381 |
The pair task was rejected because the volume you specified as the S-VOL is blocked. |
|
2382 |
The pair task was rejected because the volume you specified as the S-VOL is being formatted or shredded. |
|
2383 |
The pair task was rejected because the volume you specified as the S-VOL is a command device. |
|
2387 |
The pair was not created because the volume you specified as the P-VOL is the volume for Volume Migration. |
|
2394 |
The pair was not registered in the CTG because the number of the pairs assigned to the CTG has exceeded the defined maximum number of pairs. |
|
2395 |
The pair task was rejected because you are reverse resynchronizing the pair sharing the specified volume as the P-VOL. |
|
2396 |
The pair task was rejected because you are reverse resynchronizing the L1 pair sharing the specified P-VOL as the root volume. |
|
2397 |
The pair task was rejected because you are reverse resynchronizing the L2 pair sharing the specified P-VOL or S-VOL as the node volume. |
|
2398 |
Quit Restore or Reverse Copy was rejected because the pair is not in PSUS(SSUS)/SUSPOP or PSUE/SUSPER status. |
|
2399 |
Quit Restore or Reverse Copy was rejected because some of the pairs sharing the specified volume as the P-VOL are not in PSUS or SSUS/SUSPOP/PSUE/SUSPER status. |
|
239D |
The pair was not created because you have set the Protect attribute for the volume you specified as the P-VOL using BCM. |
|
239E |
The pair was not created because you set the Protect attribute for the volume you specified as the S-VOL using BCM. |
|
23A9 |
The Quick Restore or Reverse Copy operation was rejected because the volume specified as the P-VOL had been specified as a Concurrent Copy (CC) primary volume. |
|
23AB |
The Quick Restore or Reverse Copy operation was rejected because the volume specified as the S-VOL had been specified as the Concurrent Copy (CC) primary volume. |
|
23AF |
Registration of a pair into the CTG from CCI was rejected because the specified CTG ID is reserved for BCM/PPRC. |
|
23B7 |
An SIz pair cannot be created, because the differential data management specified at the SIz pair creation differs from that for a TCz pair that uses the specified P-VOL. This problem might occur due to either of the following reasons:
|
|
23B8 |
An SIz pair cannot be created, because the differential data management specified at the SIz pair creation differs from that for a TCz pair that uses the specified S-VOL. This problem might occur due to either of the following reasons:
|
|
23BB |
The pair was not created because the volume you specified as the S-VOL could not be used as the S-VOL because of Volume Security settings. |
|
23BE |
An SIz pair cannot be created, because the differential data management specified at the SIz pair creation differs from that for a URz pair that uses the specified P-VOL. This problem might occur due to either of the following reasons:
|
|
23BF |
An SIz pair cannot be created, because the differential data management specified at the SIz pair creation differs from that for a URz pair that uses the specified S-VOL. This problem might occur due to either of the following reasons:
|
|
23EF |
The pair was not deleted because the P-VOL and S-VOL are in the process of being Quick Split. |
|
23F1 |
The pair was not created because the CTG identifier you specified is not supported. |
|
23F5 |
The pair task was rejected because you set a split time for the CTG. |
|
9100 |
You cannot run the command because the system did not authenticate your user information. |
|
B911 |
The pair task was rejected because the specified volume did not exist. |
|
B912 |
The pair was not created because the specified S-VOL does not exist. |
|
B913 |
The pair task was rejected because the mirror ID is invalid. |