raidcom add journal
Error message
Executing/
Async
Error code
Description
SSB1 SSB2
CMDRJE
Get Command
Status
Executing/
Async
2E30 0005 The specified volume cannot be used as a journal
volume because it is set by Cache Residency
Manager or Cache Residency Manager for
Mainframe.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0006 The specified volume cannot be used because it is
used in FICON(R) Data Migration.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0007 A path is defined in the specified volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 000C The operation failed because the specified volume
is a quorum disk.
CMDRJE
Get Command
Status
Executing/
Async
2E30 000D The specified volume cannot be used as a journal
volume because it is a system disk.
Get Command
Status
Async 2E30 000E The operation failed because the specified volume
is a pool volume of Dynamic Provisioning.
Get Command
Status
CMDRJE
Async/
Executing
2E30 000F The specified volume is already used as a journal
volume or a data volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0010 The specified volume is used as a command
device.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0013 The specified volume cannot be used as a journal
volume because it is a LUSE volume.
CMDRJE
Get Command
Status
Executing/
Async
2E30 0019 The specified volume cannot be used as a journal
volume because it is set by Data Retention Utility
or Volume Retention Manager.
CMDRJE
Get Command
Status
Executing/
Async
2E30 001A Using the specified volume is prohibited by Volume
Security.
CMDRJE Executing 2E30 0035 The internal volumes and external volumes exist in
the specified journal.
Get Command
Status
Async 2E30 0040 The emulation type of the specified volume is not
supported. Or, the combination of an emulation
type of the journal volume is incorrect.
Get Command
Status
Async 2E30 0041 The volume cannot be registered as a journal
volume because the CLPR ID of the specified
9-48
Troubleshooting
Command Control Interface User and Reference Guide