Mainframe component error messages

YK5000E

1st parameter value is invalid value

Explanation

The value specified for the first parameter is incorrect.

value: Specified value

Recommended actions

The specified value for the first parameter of the communication function of the backup REXX exec is incorrect. After fixing the specified value, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5001E

2nd parameter value is invalid value

Explanation

The value specified for the second parameter is incorrect.

value: Specified value

Recommended actions

The specified value for the second parameter of the communication function of the backup REXX exec is incorrect.

After fixing the specified value is complete, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5002E

Failed to operation console command process. (return code=nnnn)

Explanation

The CONSOLE command processing failed.

operation

CONSOLE command processing performed

INIT: Initializing CONSOLE command processing failed.
TERM: Ending CONSOLE command processing failed.

nnnn (decimal number)

Return code of the CONSOLE command processing module (maintenance information)

The following code is set for reason code.

0: Ended normally
400: The timeout time was passed without the MODIFY command or the STOP command being entered.
1000: The caller is not the REXX environment.
4000: An error occurred in REXX variable access. The possible cause is that the region size is not enough.
4400: An error occurred while OS micro is running.
6400: Running the function ended abnormally.

Recommended actions

When return code is 0, 400, or 1000:
Confirm that backup REXX exec is running in the TSO/E environment. After preparing for running backup REXX exec in the TSO/E environment, rerun the REXX exec.
When return code is 4000:
The region size might be insufficient. Review the region size.
When return code is 4400 or 6400:
Collect the trace information and contact customer support.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5003E

Failed to GET console command. (return code=nnnn)

Explanation

Getting the CONSOLE command failed.

nnnn (decimal number)

Return code of the CONSOLE command processing module (maintenance information)

The following reason codes are set for reason code.

0: Ended normally
400: The timeout time was passed without the MODIFY command or the STOP command being entered.
1000: The caller is not the REXX environment.
4000: An error occurred in REXX variable access. The possible cause is that the region size is not enough.
4400: An error occurred while OS micro is running.
6400: Running the function ended abnormally.

Recommended actions

When return code is 0, 400, or 1000:
Confirm that backup REXX exec is running in the TSO/E environment. After preparing for running backup REXX exec in the TSO/E environment, rerun the REXX exec.
When return code is 4000:
The region size might be insufficient. Review the region size.
When return code is 4400 or 6400:
Collect the trace information and contact customer support.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5004E

Failed to check configuration file. (name=ddname, dsstate)

Explanation

An error occurred when the attribute information of the external volume definition data set shown in ddname was checked.

Check the status of the external volume definition data set. The external volume definition data set might be unavailable, or the data set format might be incorrect.
If the data set format is incorrect, check the message that is output at the same time.

ddname

ddname of external volume definition data set in which an error occurs.

dsstate

Status of external volume definition data set in which an error occurs.

DSORG=xx: DSORG value of data set.
RECFM=xx: RECFM value of data set.
LRECL=xx: LRECL value of data set.
CANNOT GET DSSTATE, reason code=nnnn: Data set information cannot be obtained or external volume definition data set is not assigned.; nnnn is the reason code (maintenance information).

Recommended actions

When dsstate is CANNOT GET DSSTATE, reason code=nnnn: Data set might not be assigned to ddname (YKDDMTO, YKDDOTM).

Assign the data set to the ddname displayed in name= in the message, and then rerun the REXX exec.
Check the scheduled time of pair resync or split and determine whether to rerun the REXX exec in the current cycle or in the next cycle.
If the above is not the cause: An error occurred in the execution of the LISTDSI TSO/E external function for which the ddname displayed in name= in the message is specified. The reason code of LISTDSI is output in reason code=. For details, see the IBM^® document z/OS^® TSO/E REXX Reference.

When dsstate is other than the above: The format of the data set assigned to the ddname is not correct. The error data set format is displayed in the message.

Delete the configuration file in which the error occurred.
Check the data set format and the required device capacity and assign the configuration file again.
After fixing the data set name is complete, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5005E

File name is invalid: ddname

Explanation

The data set name indicated in ddname is invalid.

ddname: ddname of the data set in which an error occurs.; The data set name assigned to the ddname (YKDDMTO or YKDDOTM) is incorrect.

Recommended actions

Correct the data set name assigned to the ddname output in the message.
After correcting the data set name, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5006E

File Open error. EXECIO RC=n: ddname

Explanation

The data set indicated in ddname could not be opened because of the failure with the EXECIO TSO/E REXX command (return code=n).

ddname: ddname of the data set in which an error occurs.

Recommended actions

The read or write permissions of the data set might not be given.

Provide the read or write permissions to the user who runs the REXX exec.
After giving permissions is complete, rerun the REXX exec.
If permissions is not the cause of failure, re-running the EXECIO command for data set will fail again. The reason code of EXECIO is output in RC=. For details, see the IBM^® document z/OS^® TSO/E REXX Reference.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5007E

File record value is invalid: ddname

Explanation

The record value shown in ddname is invalid. Check if the record descriptions, such as timestamp and checksum, are correct.

ddname: ddname of the data set in which an error occurs.

Recommended actions

Read and write might have been performed redundantly for the data set. Rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5008E

The INIT process was not called in advance.

Explanation

In the communication function of the backup REXX exec, the INIT processing was not called in advance. To run the communication function with the first operand CHECK, SUBMIT, or GETREQ specified.

Recommended actions

Run the communication function of backup REXX exec by specifying INIT for the first operand in advance.
After completing the processing of the communication function with INIT specified in the REXX exec, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5009E

The process process was not called in advance.

Explanation

The processing of the communication function of the backup REXX exec shown in process was not called in advance.

process: processing name of the communication function of the backup REXX exec.

Recommended actions

To run the communication function of the backup REXX exec with CHECK specified for the first operand and PERMITREQ specified for the third operand.

Run the communication function by specifying SUBMIT for the first operand in advance.
After completing the processing of the communication function with SUBMIT specified in the REXX exec, rerun the REXX exec.

To run the communication function of the backup REXX exec with SUBMIT specified for the first operand and no second operand specified.

Run the communication function by specifying ACCEPT for the first operand in advance.
After completing the processing of the communication function with ACCEPT specified in the REXX exec, rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5010E

An invalid OTM attime request was detected.

Explanation

An invalid backup time is sent to the FXotm data set in the CHECK processing of the communication function of the backup REXX exec.

Recommended actions

If CONT is specified for the parameter TISPLIT:

As Open System Operator, verify that the backup is complete.
As Mainframe System Operator, execute the YKRESYNC command as needed.

If TERM is specified for the parameter TISPLIT:

As Open System Operator, verify that the backup is complete and initialize the FXotm data set.
As Mainframe System Operator, execute the YKRESYNC command as needed.
Rerun the YKCRSBUO REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)

YK5105E

Communication error. (TYPE=type, RC=return-code)

Explanation

An error occurred communicating with open side through FXmto and FXotm data sets. See the return code of the communication function of the backup REXX exec.

type

Function name of the communication function of the backup REXX exec

return-code

Return code of the communication function of the backup REXX exec

The following list of return codes is provided with their meaning.

4

The process was interrupted because a MODIFY command other than MODIFY STOP was entered in the console. Returns the command parameter string after the second word (if the first argument is CHECK, WAIT or GETREQ).

8

The process did not complete even if the timeout period specified for the second argument was reached (if the first argument is CHECK). There may be a problem with the open server. Check the status on the open server side.

12

External volume snapshot retrieval failed (if the first argument is CHECK). There may be a problem with the open server. Check the status on the open server side.

16

The process was interrupted because the MODIFY STOP, or STOP command was entered in the console. (If the first argument is CHECK, WAIT or GETREQ).

20

An invalid backup time is sent to the FXotm data set (if the first argument is CHECK).

24

Failed to register the task to retrieve the external volume snapshot (if the first argument is CHECK). There may be a problem with the open server. Check the status on the open server side.

36

The CONSOLE command could not be acquired, or the initialization process or termination process for acquiring the CONSOLE command failed.

40

Failed to open or I/O the FXmto or FXotm data set.

48

The input argument is incorrect, or the data set name or format specified for YKDDMTO or YKDDOTM is incorrect.

52

CHECK or SUBMIT was called without calling INIT in advance.
SUBMIT without the second operand was called without calling ACCEPT in advance.
CHECK of which the third operand is PERMITREQ is called without SUBMIT in advance.

Recommended actions

Check the description to resolve the problem.
If the REXX exec terminates, execute it again.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5106E

Processing will now end because a copy pair in the simplex state exists.

Explanation

Because there is a copy pair in the simplex state, the processing ends.

Recommended actions

Change the ShadowImage for Mainframe to the duplex or suspend status.
Rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5107E

A timeout occurred during the transition to the status state.

Explanation

Timeout occurred during transition to status state.

status: Target status of the copy pair.

Recommended actions

When status is DUPLEX:
Resync operation was not complete until two minutes before the scheduled split time. Review the time for performing split and rerun the REXX exec. If this error occurs when you start the backup REXX exec at a time that is earlier enough than the scheduled split time, the interval from the last backup time that was interrupted may be less than the maximum time that the backup specified for the TISPLIT parameter or CHECK parameter completes. To resolve this issue, reduce the maximum time specified in the TISPLIT parameter or CHECK parameter, or manually delete all the strings recorded in the FXmto data set on the mainframe side and delete the contents of open-system file for FXotm on the open side to ignore the interval from the last backup time.
When status is SUSPEND:
The maximum time of waiting for split to complete specified in the SUSPEND parameter was exceeded. Review the value specified in the SUSPEND parameter. To rerun the REXX exec, confirm that split is completed in advance.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5108E

A required argument is not specified.

Explanation

The required parameter is not specified.

Recommended actions

The PREFIX parameter, the GROUP parameter, or the DAD parameter is not specified. For parameters, see the Verification REXX execs or Restore script in the Hitachi Mainframe Cyber Resiliency User Guide. After specifying the parameters, rerun the REXX exec or script.

Source

YKCRSVDC, YKCRSVRC, YKCRSRES

Message output destinations

SYSTSPRT (job log)

YK5109E

command RC = return-code

Explanation

command ended with return-code. A CLI error message is output after this message.

command: Issued command names and their parameters
return-code: Return code of the issued command.

Recommended actions

When command name is YKQEXDEV, YKREXDEV, or YKDEXDEV: See Return codes of Universal Volume Manager operation commands.
When command name is other than YKQEXDEV, YKREXDEV and YKDEXDEV: See the Hitachi Business Continuity Manager Reference Guide.

Check the description to resolve the problem, and then execute it again.

Source

YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5110E

File Open error. EXECIO RC=n: ddname

Explanation

The data set shown ddname could not be opened by failure (return code = n) on the EXECIO TSO/E REXX command. For more information, see the IBM^® document z/OS^® TSO/E REXX Reference.

ddname: ddname of the data set where the error occurred.

Recommended actions

Check the description to resolve the problem, and then execute it again.

When disconnect or reconnect REXX exec, the data set name may not be specified in the ddname YKDDXDEV. After specifying the data set name in YKDDXDEV, rerun the REXX exec.

If this is not the cause, the EXECIO command for the data set assigned to the ddname YKDDXDEV will fail to execute. The reason code of EXECIO is output to RC. For more information, see the IBM^® document z/OS^® TSO/E REXX Reference.

Source

YKCRSBUO, YKCRSMON, YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)

YK5111E

Elements of the record are not defined. record number=line

Explanation

Elements of the record specified in the external volume definition data set assigned to YKDDXDEV are not defined. Review the description of the line number shown in line.

line: Line number in which an error was detected.

Recommended actions

The records in the external volume definition data set are incorrect. For records in the external volume definition data set, see the External volume definition data set (YKDDXDEV) description format in the Hitachi Mainframe Cyber Resiliency User Guide. Correct the records in the external volume definition data set and rerun the REXX exec.

Source

YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5112E

An error occurred during the execution of the command-name command. RC=return-code

Explanation

An error occurred in the command-name command.

return-code: Command return code

Recommended actions

An error occurred while running the CONSPROF command or YKCONMSG command. For the CONSPROF command, see the IBM^® document z/OS^® TSO/E System Programming Command Reference. For the YKCONMSG command, see the Hitachi Business Continuity Manager Reference Guide.

Source

YKCRSMON, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5113E

Console cannot be activated. RC=return-code

Explanation

The console could not be activated. Make sure that the user has console permissions.

return-code: Return code for the CONSOLE ACTIVATE command or GETMSG command.

Recommended actions

An error occurred while running the CONSOLE command. See the IBM^® document z/OS^® TSO/E System Programming Command Reference for the CONSOLE commands.

Source

YKCRSMON, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5114E

The volume is not offline, is not a simplex volume, or is not an external volume. (device number = device-number).

Explanation

The process was interrupted because there was a Verify‑Access volume that did not meet the prerequisites. Check the state of the volume shown in device-number.

device-number

Check whether the following conditions are met:

The volume was online from one of the mainframe servers.
The volume was not in the simplex state.
No external volumes were mapped.

Recommended actions

Ensure that the volume is an external volume.
Ensure that the volume is not paired or in an offline state.
Rerun the REXX exec.

Source

YKCRSVDC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5115I

Volume is OFFLINE. DEVN device-number

Explanation

There was a volume that could not be online.

device-number: Device number

Recommended actions

Check the status of the volume and path.

Source

YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6

YK5116E

One or more online volumes or non-simplex pairs exist.

Explanation

Processing was interrupted because there was a copy source volume or copy destination volume that did not meet the prerequisites of the script.

Recommended actions

Check if the following conditions are met:

The copy pair between the source volume and the destination volume was not in the simplex state.
The source volume was in the online state.
The destination volume was in the online state.

Make sure that all the pairs in the copy group are in simplex state and offline. Then, rerun the script.

Source

YKCRSRES

Message output destinations

SYSTSPRT (job log)

YK5118I

command-name RC = return-code

Explanation

command-name finished in return-code. The REXX exec continues processing. If there is a CLI error message, it will be printed after this message. This error occurred by running the YKQRYDEV command to the disconnected external volumes, but it will not affect the REXX exec operation.

Recommended actions

No action is required.

Source

YKCRSVDC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6

YK5119I

An error occurred during the execution of the command-name command. RC=return-code

Explanation

An error occurred in the command-name command. The REXX exec will continue processing.

return-code: Return code of command-name command.

Recommended actions

No action is required.

Source

YKCRSVDC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6

YK5120I

Console cannot be activated. RC=return-code

Explanation

Console could not be activated. The REXX exec will continue processing.

return-code: Return code for CONSOLE ACTIVATE or GETMSG command

Recommended actions

An error occurred while running the CONSOLE command. Please check if the executing user has console privileges. See the IBM^® document z/OS^® TSO/E System Programming Command Reference for the CONSOLE commands.

Source

YKCRSVDC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6

YK5121E

A required element in the record was not specified. (record number = line)

Explanation

The configuration information data set assigned to YKDDCONF contains records for which the required elements have not been specified.

Check the description of the line numbers shown in line.

line: The line number where the error was detected.

Recommended actions

Check the record where the error was detected and specify the required elements. For details, see the Monitoring of HyperSwap^® REXX exec in the Hitachi Mainframe Cyber Resiliency User Guide.

Source

YKCRSMON

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5122E

An element in the record is invalid. (record number = line)

Explanation

The configuration information data set assigned to YKDDCONF contains records for which the invalid elements have been specified. Check the description of the line numbers shown in line.

line: The line number where the error was detected.

Recommended actions

Check the record where the error was detected and specify the correct elements. For details, see the Monitoring of HyperSwap^® REXX exec in the Hitachi Mainframe Cyber Resiliency User Guide.

Source

YKCRSMON

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5123I

A CLI ERROR OCCURRED FOR cgid. MONITORING OF THIS COPY GROUP WILL NOW STOP.

Explanation

A CLI error has occurred in TrueCopy for Mainframe copy group cgid, and then stop monitoring this copy group.

cgid: The ID of copy group where the error occurred.

Recommended actions

To resume monitoring, resolve the problem and then run the monitoring REXX exec again.

Source

YKCRSMON

Message output destinations

Console
- Routing code: 11
- Descriptor code: 6

YK5124W

A HYPERSWAP OCCURRED IN cgid. message-text

Explanation

Perform the action indicated by the message-text. The message is output by using the routing code 6.

cgid

The ID of copy group where the HyperSwap^® occurred.

message-text

One of the following texts will be displayed.

Omit the backup job name: STOP ALL ASSOCIATED BACKUP JOBS.
Specify the backup job name: MAKE SURE THAT BACKUP JOB jobname HAS STOPPED.

Recommended actions

Perform operation of message-text.

Source

YKCRSMON

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5125W

HYPERSWAP FAILED. CHECK THE STATUS OF EACH TC COPY GROUP AND STOP THE BACKUP JOBS AS NEEDED.

Explanation

Detect the failure of HyperSwap^®. The message is output by using the routing code 6.

Recommended actions

Check the status of the TrueCopy for Mainframe/HyperSwap^® copy group and stop the backup job if necessary.

Source

YKCRSMON

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5126E

Processing will now end because there is a UR copy pair that is not in the status state.

Explanation

Because there is a Universal Replicator for Mainframe copy pair that is not in the status state, the processing ends.

status: The status of the Universal Replicator for Mainframe copy pair.

Recommended actions

Change the Universal Replicator for Mainframe to the status status.
Rerun the REXX exec.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

Recommended actions

If you want to run a backup REXX exec with the SUSPENDOPT(ATTIME) parameter specified, specify a C/T ID for the ShadowImage for Mainframe copy group and then run the REXX exec again.
In other cases, run the backup REXX exec with the SUSPENDOPT(NORMAL) parameter specified.

Source

YKCRSBUO

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5130A

REPLY Y TO RESUME MONITORING AFTER STOPPING BACKUP JOBS OR N. HYPERSWAP OCCURRED IN cgid.

Explanation

Stop the backup job that is associated with the copy group where the HyperSwap^® occurred. After the action is completed, reply Y to resume monitoring the other copy groups. To stop monitoring, reply N to the message.

cgid: The ID of copy group where the HyperSwap^® occurred.

Recommended actions

Reply Y to the message after stopping the backup job that is associated with the copy group where the HyperSwap^® occurred.

Source

YKCRSMON

Message output destinations

Console
- Routing code: 1
- Descriptor code: 7

YK5131A

REPLY Y TO RESUME MONITORING AFTER CONFIRMING THAT JOB jobname HAS STOPPED, OR REPLY N.

Explanation

Confirm that the backup job specified in the configuration information data set has stopped. After the action is completed, reply Y to resume monitoring the other copy groups. To stop monitoring, reply N to the message.

cgid: The ID of copy group where the HyperSwap^® occurred.

Recommended actions

Reply Y to the message after confirming that the backup job specified in the configuration information data set has stopped.

Source

YKCRSMON

Message output destinations

Console
- Routing code: 1
- Descriptor code: 7

YK5132A

REPLY Y TO RESUME MONITORING AFTER CHECKING THE STATUS OF EACH TC COPY GROUP AND BACKUP JOB, OR REPLY N.

Explanation

Detect the failure of HyperSwap^®.

Recommended actions

Check the status of the TrueCopy for Mainframe/HyperSwap^® copy group and stop the backup job if necessary.
When you have completed the action, reply Y to this message to resume HyperSwap^® monitoring. To stop monitoring, reply N to the message.

Source

YKCRSMON

Message output destinations

Console
- Routing code: 1
- Descriptor code: 7

YK5133I

The backup of cgid was successful. (ATTIME=attime)

Explanation

The processing of the current backup cycle was successful.

cgid: The ID of the copy group to be backed up.
attime: The time of ATTIME request in the current backup cycle. The time format is UTC ISO 8601 extended format. (yyyy-MM-ddTHH:mm:ssZ)

Recommended actions

No action is required.

Source

YKCRSBUO

Message output destinations

Console and SYSTSPRT (job log)
- Routing code: 11
- Descriptor code: 6

YK5134I

The backup of cgid failed. (ATTIME=attime)

Explanation

The processing of the current backup cycle failed. This message is also output when the MODIFY STOP or STOP command is entered in the console in the current backup cycle.

cgid: The ID of the copy group to be backed up.
attime: The time of ATTIME request in the current backup cycle. The time format is UTC ISO 8601 extended format. (yyyy-MM-ddTHH:mm:ssZ)

Recommended actions

If the user entered a MODIFY STOP or STOP command in the console, no action is required.
In other cases, check the previously output SYSTSPRT message.

Source

YKCRSBUO

Message output destinations

Console and SYSTSPRT (job log)
- Routing code: 11
- Descriptor code: 6

YK5135E

Value = detail

Explanation

A CLI error occurred before this message.

detail: Detailed information of the CLI error message that was output before this message.

Recommended actions

Check the explanation of the CLI error message that is output before this message, and then check this message to confirm specific issues such as the error location or volume identification information. For details about CLI error message, see Business Continuity Manager error messages.

Source

YKCRSBUO, YKCRSMON, YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5136W

Value = detail

Explanation

A CLI error occurred before this message.

detail: Detailed information of the CLI warning message that was output before this message.

Recommended actions

Check the explanation of the CLI warning message that is output before this message, and then check this message to confirm specific issues such as the error location or volume identification information. For details about CLI warning message, see Business Continuity Manager error messages.

Source

YKCRSBUO, YKCRSMON, YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 6
- Descriptor code: 6

YK5137I

Value = detail

Explanation

A CLI error occurred before this message.

detail: Detailed information of the CLI information message that was output before this message.

Recommended actions

Check the explanation of the CLI information message that is output before this message, and then check this message to confirm specific issues such as the error location or volume identification information. For details about CLI information message, see Business Continuity Manager error messages.

Source

YKCRSBUO, YKCRSMON, YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6

YK5200I

The UVM is detecting a fault condition (xx).

Explanation

An error of Universal Volume Manager is occurred.

xx

Failure code. The failure code lists in the following table.

Failure code	Failure status
02	Cannot detect port
03	Blocked
04	External device setting changed
05	LDEV size reduced
06	Not ready
07	Illegal request
08	Command aborted
09	Busy
0B	Response error
0C	Response error
0D	Initiator port
0F	Unknown port
10	Internal error
14	Device check error
15	Medium error
16	Medium error
17	Medium error
18	Medium error
19	Medium error
1A	Medium error
1B	Destage failed
C0	Cannot detect port

Recommended actions

Refer the failure codes and status in the Troubleshooting external path status section of Hitachi Universal Volume Manager User Guide.

Source

YKCRSVDC, YKCRSVRC

Message output destinations

SYSTSPRT (job log)
Console, if WTO(Y) or WTO(V) parameter is specified.
- Routing code: 11
- Descriptor code: 6