Understanding scope violation codes
Reason codes are returned to IBM Z hosts when an issued command results in a scope violation.
| Reason code | Scope violation |
|---|---|
| 01 | Global Mirror Session Number violation (Destination
Device detected violation) or Global Mirror Master violation
(Connection LSS detected violation) Explanation: None. Action: None. |
| 02 | Global Mirror Session Subordinate Disallowed Explanation: None. Action: None. |
| 03 | Global Mirror Session Disallowed (Destination
Device detected violation) Explanation: None. Action: None. |
| 04 | Encryption Group Scope Mismatch (Primary/Source
detected violation) Explanation: None. Action: None. |
| 05 | Scope violation (Source detected violation, default case)
Explanation: An internal error occurred. Action: Contact IBM technical support. |
| 06 | Scope violation (Target detected violation, default case)
Explanation: An internal error occurred. Action: Contact IBM technical support. |
| 10 | CKD PPRC Secondary Scope violation (Primary
detected violation) Explanation: The copy services global scope attribute that is defined in the scope of the primary volume is not consistent with the scope specified in the secondary volume. Either the copy services request was specified incorrectly, or its scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the scope policies, or modify the scope policy of the primary volume to allow the requested operation. |
| 11 | CKD PPRC Primary Scope violation (Secondary
detected violation) Explanation: The copy services scope attribute that is defined in the scope of the secondary volume is not consistent with the scope specified in the primary volume. Either the copy services request was specified incorrectly, or its scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the scope policies, or modify the policy of the secondary volume to allow the requested operation. |
| 12 | CKD FlashCopy Full Volume Target Scope violation
(Source detected violation) Explanation: The copy services scope attribute that is defined in the scope of the source volume is not consistent with the label specified in the scope f the target volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the scope policies, or modify the policy of the source volume to allow the requested operation. |
| 13 | CKD FlashCopy Full Volume Source Scope violation
(Target detected violation) Explanation: The copy services global scope attribute that is defined in the target volume is not consistent with the label specified in the scope of the source volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation allowed by the policies, or modify the scope of the target volume to allow the requested operation. |
| 14 | CKD FlashCopy Dataset Target Scope violation
(Source detected violation) Explanation: The copy services global scope attribute that is defined in the scope of the source volume is not consistent with the label specified in the scope of the target volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the source volume to allow the requested operation. |
| 15 | CKD FlashCopy Dataset Source Scope violation (Target detected violation)
Explanation: The copy services scope attribute that is defined in the target volume is not consistent with the label specified in the scope of the source volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the target volume to allow the requested operation. |
| 20 | FB PPRC Secondary Scope violation (Primary detected
violation) Explanation: The copy services scope attribute that is defined in the primary volume is not consistent with the label specified in the scope of the secondary volume. Either the copy services request was specified incorrectly, or its scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the primary volume to allow the requested operation. |
| 21 | FB PPRC Primary Scope (Secondary detected
violation) Explanation: The copy services scope attribute that is defined in the secondary volume is not consistent with the label specified in the scope of the primary volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the secondary volume to allow the requested operation. |
| 22 | FB FlashCopy Full Volume Target Scope violation
(Source detected violation) Explanation: The copy services scope attribute that is defined in the source volume is not consistent with the label specified in the scope of the target volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the source volume to allow the requested operation. |
| 23 | FB FlashCopy Full Volume Source Scope violation
(Target detected violation) Explanation: The copy services scope attribute that is defined in the target volume is not consistent with the label specified in the source volume. Either the copy services request was specified incorrectly, or the scope attribute must be modified. Action: Either change the copy services request for an operation that is allowed by the policies, or modify the scope of the target volume to allow the requested operation. |
| 30 | Passthrough Scope violation (Connection device
detected violation on destination device) Explanation: The passthrough scope attribute specified in the CKD connection volume is not compatible with the label attribute specified in the scope of the destination volume that is specified in the command parameters. Either the connection volume that is used or the destination volume that is specified are incorrect or the operation is not allowed by the passthrough scope. Action: Take
one of the following actions so that the resource group policy of
the connection volume is consistent with the label of the destination
volume:
|
| 31 | Passthrough Scope violation (Connection device
detected violation on destination logical subsystem) Explanation: The passthrough scope attribute specified in the scope of the CKD connection volume is not compatible with the label attribute specified in the destination logical subsystem that is specified in the command parameters. Either the connection volume that is used or logical subsystem specified are incorrect or the passthrough scope attribute does not allow the requested operation. Action: Change the command to request a valid passthrough operation, or modify the scope of the connection volume to allow the requested operation, or change the scope of the specified volumes so that the scope of the connection volume is consistent with the resource group label of the destination LSS. |
| 32 | Passthrough Scope violation (Connection device
detected violation on local device) Explanation: The passthrough scope attribute specified in the scope of the CKD connection volume is not compatible with the label attribute specified in the scope of the local device (PPRC primary) associated with the remote destination logical volume (PPRC secondary and source volume in command) specified in the command parameters. Either one or both of the specified volumes are incorrect, or the passthrough scope attribute does not allow the operation. Action: Change the command to request a valid passthrough operation, or modify the scope of the connection logical volume to allow the requested operation, or change the scope of the specified volumes so that the scope of the connection volume is consistent with the label of the local volume. |
| 40 | User Scope violation (Destination Logical volume
detected violation) Explanation: The scope of the user session requesting this operation is not compatible with the label attribute in the volume to which the request is directed. Either the volume is specified incorrectly or the user account needs a different user scope to access the specified resource. Action: Either change the request to operate on a volume in which the user scope is compatible, or change the user account to have a user scope that is compatible with the specified volume. |
| 41 | User Scope violation (Destination LSS detected
violation) Explanation: You do not have the required access to the destination logical subsystem that you specified. Action: Obtain the required access and resubmit the command. |
| 42 | Scope violation (Local device of resource that
is accessed by user request) Explanation: The destination device that is specified in the user request is a remote device (PPRC Secondary) and the user scope does not match the label of the local device (PPRC Primary). Action: Either change the request to specify a scope that has a matching label, or specify a different destination device. |
| 43 | User Scope violation (Create Resource detected
violation) Explanation: The user scope of the user session requesting this create operation is not compatible with the label attribute in the scope that is specified for the resource being created. Either the scope is specified incorrectly, or the user account needs a different user scope to create the resource with the specified scope. Action: Either change the request to specify a scope with which the user scope is compatible, or change the user account to have a user scope that is compatible with the specified user scope. |
| 44 | User Scope violation (Modify Resource detected
violation) Explanation: The user scope of the user session requesting this change operation is not compatible with the label attribute in the user scope that is associated with the resource being modified. Either the user scope is specified incorrectly, the resource is associated with the wrong user scope, or the user account needs a different user scope to modify the resource. Action: To have a user
scope that is compatible with the label attribute in the resource
that is associated with the resource being modified, take
one of the following actions:
|
| 45 | User Scope violation (Delete Resource detected
violation) Explanation: The user scope of the user session requesting the delete operation is not compatible with the label attribute in the user scope that is associated with the resource being deleted. Either the resource is specified incorrectly, the resource is associated with the wrong user scope, or the user account needs a different user scope to modify the resource. Action: To have
a user scope that is compatible with the label attribute
in the user scope that is associated with the resource being
modified, take one of the following actions:
|