List of messages starting with YK

Storage Management Software for Mainframe Messages

Version
9.8.9
Audience
anonymous
Part Number
MK-92HC227-21

The following tables list and describe messages starting with YK.

Types of message starting with YK

Wait until all pending commands have finished execution before taking corrective action.

  • YK5: Hitachi Mainframe Cyber Resiliency function

    For details, see the Hitachi Mainframe Cyber Resiliency User Guide.

  • YK6: z/OSMF

  • YK7: YKBTSCAN or BCM Web API server

  • YK8: BCM Monitor

  • YK9: License

  • YKA: YKCONMSG or KTCONMSG

  • YKB: Messages output by the Copy Group Definition Generation function

  • YKC: YKSCAN

  • YKD: YKDELETE

  • YKE: YKEWAIT

  • YKF: YKFREEZE

  • YKG: YKHDAX (an internal program of YKLOAD)

  • YKH: YKH2B

  • YKJ: YKIMPORT or YKEXPORT

  • YKK: YKINSCHK, RSINSCHK, or KTINSCHK

  • YKL: YKLOAD

  • YKM: YKMAKE, messages displayed in the ISPF panel, or ISPF log

  • YKN: YKRUN

  • YKP: YKSTATS

  • YKQ: YKQUERY

  • YKR: YKRESYNC

  • YKS: YKSTORE

  • YKT: YKALCSVC, KTALCSVC, YKSETENV, or YKDSPENV

  • YKU: YKSUSPND

  • YKV: YKRECVER

  • YKW: YKWATCH

  • YKX: YKBLDCMD, YKDELCMD, or YKQRYDEV

  • YKY: Business Continuity Manager agent

  • YKZ: All commands or tools

Table. List of messages starting with YK (YK60x - YK90x)

Message ID

Message text

Explanation and recommended actions

YK6000E zOSMF RC=-3

TSO service is not available.

The TSO/E service is not available.

YK6001E zOSMF RC=16

No parameter-name parameter supplied.

The parameter-name parameter is not specified.

YK6002E zOSMF RC=16

parameter-name value is invalid.

value

The value specified for parameter-name is not correct.

value

The specified value

YK6003E zOSMF RC=12

An error occurred during the operation on the dataset. (dataset = dataset-name, status = dsstate)

An error occurred during an operation on the dataset dataset-name.

dataset-name

The name of the dataset where the error was detected

dsstate

The state of the dataset

CANNOT GET DSSTATE, reason code= nnnn

This indicates that information about the dataset could not be obtained.

nnnn (a decimal number) is the reason code (maintenance information).

YK6004E zOSMF RC=12

An error occurred during the execution of the command-name command.

An error occurred during the execution of the command-name command.

YK6005E zOSMF RC=12

Console cannot be activated.

The console could not be activated.

Check whether the user that executed the operation has console permissions.

YK6006E zOSMF RC=12

No messages were returned from the console.

No messages were returned from the console.

YK6007I zOSMF RC=0

Delete the recorde-name record that contains DSNAME(dataset-name).

Note: note

Delete the record recorde-name, which contains the dataset dataset-name.

note

Notes

YK6008I zOSMF RC=0

Delete the following line from the member-name parmlib member.

delete-name

Delete the following line from the member-name parmlib member.

delete-name

Name to be deleted

YK6009I zOSMF RC=0

Add the following line to the member-name parmlib member.

add-name

Add the following line to the member-name parmlib member.

add-name

Name to be added

YK6010I zOSMF RC=0

message

The method used to change parmlib members is output.

YK6011E zOSMF RC=12

Failed to create the license information dataset.

The license information dataset could not be created.

Check the information about free space on the volume and the free space in the VTOC.

YK6012E zOSMF RC=12

The member-name parmlib member cannot be accessed.

The member-name parmlib member could not be accessed.

YK6013E zOSMF RC=12

An attempt to perform an action on the dataset-name parmlib member failed. (action = action, return code = RC)

An attempt to perform an action (action) on the dataset-name parmlib member failed.

RC

Return code for the action

YK6014I zOSMF RC=0

The following records were backed up to dataset-name.

data

The following records were backed up to dataset-name.

data

Records that were backed up

YK6015I zOSMF RC=0

No Need change parameter because already register data.

The parameter does not need to be changed, because data is already registered.

YK6016I zOSMF RC=0

Update the member-name parmlib member by following records.

data

Update the member-name parmlib member according to the following records.

data

Records to be updated

YK6017I zOSMF RC=0

The following records were output to dataset-name.

data

The following records were output to dataset-name.

data

Records that were updated

YK6018E zOSMF RC=16

You cannot specify an active LNKLST for the TMPLNKL parameter.

An active LNKLST cannot be specified for the TMPLNKL parameter.

YK6019W zOSMF RC=4

The HWNAME, LPARNAME, or VMUSERID specified for IEASYMxx parmlib member cannot be updated.

The HWNAME, LPARNAME, or VMUSERID specified for the IEASYMxx parmlib member could not be updated.

YK6020E zOSMF RC=16

The name of the license information dataset could not be obtained.

The name of the license information dataset could not be obtained.

The Business Continuity Manager dataset might not be linked with LNKLST.

YK7000T PRT RC=16

Supplied parameters invalid: line

An invalid parameter was specified. Revise the value specified on the line line.

YK7001E PRT RC=16

No parameter-name parameter supplied.

The parameter-name parameter is not specified.

YK7003E PRT RC=16

The parameter parameter-name is invalid: line

The value specified for the parameter-name parameter is invalid.

Revise the value specified on the line line, and then verify the following:

  • The operand length is correct.

  • The format of the operand value is correct.

  • In the DEVN, VOLSER, or RANGE parameter, the value specified for the last value of the scan range is greater than the first value of the scan range.

YK7004E PRT RC=16

The parameter parameter-name is invalid.

The value assigned to the parameter-name parameter is invalid.

YK7005E PRT API RC=16

The parameters parameter-name1 and parameter-name2 cannot be concurrently specified.

You cannot specify the parameter-name1 parameter and the parameter-name2 parameter at the same time.

YK7006E PRT RC=16

Duplicate values exist. (parameter=parameter-name1, duplicate parameter=parameter-name2)

The same value is specified for the parameter-name1 parameter and the parameter-name2 parameter.

YK7014I PRT

RC: rc CMD: command-name

The command-name command was issued, and ended with the return code rc.

YK7015I PRT

RC: rc CMD: command-name

Severity: Severity

Text: Text

Value: Value

The command-name command was issued, and ended with the return code rc.

Severity

Severity code stored in Severity for the message structure

Text

Message ID and message text stored in Text for the message structure

Value

Detailed information stored in Value for the message structure

Severity: Severity, Text: Text, and Value: Value are displayed an amount of times equal to the number of messages included in the message structure.

YK7031I PRT RC=0

Scanned DASD Device Count: count

The number of devices scanned by executing YKBTSCAN.

count

Number of scanned devices

YK7032I PRT RC=0

Hitachi storage systems Devices Found: count

The number of Hitachi storage-system devices scanned by executing YKBTSCAN.

count

Number of scanned Hitachi storage-system devices

YK7033I PRT RC=4

The specified devices that do not have any available I/O paths were skipped: count

As a result of a scan, information acquisition was skipped for the devices on which no I/O paths were available.

count

Number of devices for which information acquisition was skipped

YK7034I PRT RC=0

Dummy device numbers in the disk configuration definition file were changed: count

The dummy device number in the disk configuration definition file was changed.

count

Number of devices in the disk configuration definition file whose dummy device number has been changed

YK7099I PRT

YKBTSCAN return code=nnnn

YKBTSCAN terminated with the return code nnnn. This message is always displayed to indicate the return code.

nnnn

Maximum value among the output return codes

YK7100E PRT RC=16

A duplicate serial number exists. (SN=SN, model=model1, other model=model2, pos=pos)

Processing was canceled because two or more storage systems have the same serial number. The model names for only two storage systems are displayed even if more than two storage systems have the same serial number.

SN

Duplicated serial number

model1

Model of one of the storage systems whose serial number is duplicated

model2

Model of another one of the storage systems whose serial number is duplicated

pos

Maintenance information

YK7101E PRT RC=16

You cannot perform a local scan because a remote DADID or Non Gen'ed DADID is specified as the local DADID.

A local scan cannot be performed as a batch job, because a remote device address domain ID or Non Gen'ed device address domain ID was specified as the local device address domain ID.

YK7102E PRT RC=16

The remote scan or NG scan could not be performed, because a DAD DADID is specified for parameter-name.

A remote scan or NG scan could not be performed as a batch job, because the device address domain ID of DAD is specified for the parameter-name parameter.

DAD
  • Local: Local device address domain

  • Rlocal: Local device address domain for a remote site (the first device address domain of a route starting from a remote site)

YK7103E PRT RC=16

The specified dummy device number already exists in the disk configuration definition file. (dummy device number=dummy, line=line, SN=SN, CU=CU, CCA=CCA)

When specifying the RENUM parameter or when specifying the DUMMY parameter with CCA, the dummy device number (dummy) duplicated the dummy device number that exists in the disk configuration definition file. The duplicate dummy device number is assigned to the volume whose storage system serial number is SN, control unit number is CU, and command control address is CCA.

Change the dummy device number specified in the line line to a number that is not a duplicate. Alternatively, change the scan range so that the volume with the duplicate dummy device number will be included.

YK7104E PRT RC=16

The same dummy device number was specified more than once. (dummy device number=dummy, line=line1, duplicate line=line2)

When specifying the RENUM parameter, the dummy device number (dummy) was duplicated in the scan range.

Revise the dummy device numbers specified in the line line1 and line2 so that the dummy device numbers are not duplicated.

YK7105E PRT RC=16

There are no dummy device numbers that can be specified for the volume. (line=line, SN=SN, CU=CU, CCA=CCA)

There are no dummy device numbers that can be assigned for the volume specified in the line line. An attempt to assign a dummy device number failed for the volume whose storage system serial number is SN, control unit number is CU, and command control address is CCA.

Delete the disk configuration definition file and then perform the scan again, or scan the entire range with the RENUM parameter specified.

YK7106E PRT RC=16

The same scan range was specified for multiple RANGE parameters. (line=line1, duplicate line=line2)

The same scan range was specified for multiple RANGE parameters.

Revise the line line1 and line2 so that the scan range for the RANGE parameters is not duplicated.

YK7107E PRT RC=16

You cannot perform an NG scan because no local scan has been performed for the specified storage system. (line=line)

You cannot perform an NG scan because no local scan has been performed for the storage system specified in the line line.

YK7108E PRT RC=16

The specified dummy device number already exists in the disk configuration definition file. (dummy device number=dummy, line=line, SN=SN, CU=CU, CCA=CCA)

When specifying the RENUM parameter or when specifying the DUMMY parameter with CCA, the dummy device number (dummy) duplicated the dummy device number that exists in the disk configuration definition file. The duplicate dummy device number is assigned to the volume whose storage system serial number is SN, control unit number is CU, and command control address is CCA.

Change the dummy device number specified in the line line to a number that is not a duplicate. Alternatively, change the scan range so that the volume with the duplicate dummy device number will be included.

YK7109E PRT RC=16

The same dummy device number was specified more than once. (dummy device number=dummy, line=line1, duplicate line=line2)

When specifying the RENUM parameter, the dummy device number (dummy) was duplicated in the scan range.

Revise the dummy device numbers specified in the line line1 and line2 so that the dummy device numbers are not duplicated.

YK7110E TSO RC=44

YKBTSCAN failed because of an ATTACH macro failure. RC=return-code

A subtask could not be generated. YKBTSCAN will end.

return-code (decimal number)

Return code of the ATTACH macro

YK7200E PRT API RC=48

No parameter-name parameter supplied.

The parameter-name parameter is not specified.

YK7201E PRT API RC=48

parameter-name value is invalid.

The value specified for parameter-name is not correct.

YK7202E PRT RC=48

The DUMMY operand cannot be specified on the first CDEV parameter under the ROUTE parameter.

The DUMMY operand cannot be specified in the first CDEV parameter following the ROUTE parameter. Use the DEVN operand.

YK7203E PRT RC=48

The DEVN operand can be specified only for the first CDEV parameter under the ROUTE parameter.

The DEVN operand can only be specified in the first CDEV parameter following the ROUTE parameter. Use the DUMMY operand.

YK7204E PRT RC=48

The DEVN(device-number) cannot be resolved.

The device address cannot be resolved from the specified device number.

device-number

Device number

YK7205E PRT API RC=40

The LISTCAT command failed.

The LISTCAT command could not execute successfully.

YK7206E PRT RC=40

The dataset could not be deleted. (dataset-name)

The dataset could not be deleted.

dataset-name

Dataset name

YK7207E PRT RC=40

The dataset was not found. (dataset-name)

The dataset was not found.

dataset-name

Dataset name

YK7208E PRT RC=48

A CDEV parameter is specified outside the scope of the ROUTE parameter.

There is a CDEV parameter that does not belong to a ROUTE parameter. Enter the CDEV parameter under the ROUTE parameter of the route to which the command device belongs.

YK7209E PRT RC=48

Too many CDEV parameters are specified.

Four or more CDEV parameters are entered under one ROUTE parameter.

YK7210E PRT RC=40

The copy type does not match the Copy Group cgid.

The specified copy type does not match the copy type of the copy group cgid.

cgid

Copy group ID

YK7211E PRT RC=48

The DEVN(device-number) dose not match the current host configuration.

The device number defined in the command device configuration file does not match the current configuration.

device-number

Device number

YK7212E PRT RC=48

Another program is already using the specified PREFIX.

Another program is using the specified prefix.

Revise the prefix value.

YK7213E PRT API RC=40

File Open error. EXECIO RC=rc: dd-name

The file indicated in dd-name could not be opened because the EXECIO TSO/E REXX command could not execute successfully. (return code = rc).

For details, see the IBM manual TSO/E REXX Reference.

dd-name

DD name of the file where the error occurred

rc

Return code of the EXECIO TSO/E REXX command

YK7214E PRT API RC=8

A BC Manager definition file that has the specified PREFIX and definition-file type was not found.

A BC Manager configuration file that has the specified prefix and configuration file type was not found.

YK7215E PRT RC=36

This command has no effect on the copytype copy group.

This command has no effect on a copy group that has the copy type indicated in copytype.

copytype

Copy type

YK7216I PRT RC=0

Output BC Manager configuration file. (dataset-name)

The BC Manager configuration file (dataset-name) was output.

dataset-name

Dataset name

YK7217I PRT RC=0

Deleted BC Manager configuration file. (dataset-name)

The BC Manager configuration file (dataset-name) was deleted.

dataset-name

Dataset name

YK7218I PRT RC=0

Backuped BC Manager configuration file. (dataset-name)

The BC Manager configuration file (dataset-name) was backed up.

dataset-name

Dataset name

YK7219E PRT API RC=48

A parameter syntax error exists. (dd name=dd-name, line=line)

The parameter syntax is incorrect.

line

Line number where the error was detected in the file indicated by dd-name.

dd-name

DD name of the file where the error occurred

YK7220I PRT RC=0

The Copy Group was loaded for an update. (Copy Group ID=cgid)

The copy group was loaded for an update.

cgid

Copy group ID

YK7221E PRT RC=48

The APID must be unique.

The APID is duplicated.

YK7222E PRT RC=48

The APID and LABEL must be unique for a volume.

Multiple APIDs or labels are specified for one volume.

YK7223W PRT RC=4

BC Manager ignored the fourth and subsequent storage systems on the route.

The fourth and subsequent storage systems on the route were ignored.

YK7224E PRT RC=48

CDEV parameters with the same DAD and SN are on the same route.

The same storage system cannot be defined on the same route.

YK7225E PRT API RC=48

The specified parameter (parameter-name) is unknown.

The specified parameter parameter-name is an unknown parameter.

parameter-name

Parameter name

YK7226E PRT API RC=48

An operand or operand value is not specified for the parameter parameter-name.

An operand or operand value of the parameter parameter-name is not specified.

parameter-name

Parameter name

YK7227I PRT RC=0

cli-name return code=return-code

The command cli-name ended with the return code return-code.

This message is always displayed to show the return code.

cli-name

Name of the CLI command that was executed

return-code

Maximum value in the output return codes

YK7228E PRT API RC=-3

TSO service is not available.

The TSO/E service is not available.

YK7229I PRT API RC=0

dd-name is not allocated.

The DD name indicated by dd-name is not allocated.

dd-name

DD name

YK7230E PRT RC=48

The operand of the parameter parameter-name contains an unnecessary character string (string).

The operand of the parameter parameter-name contains an extra string (string).

parameter-name

Parameter name

string

Extra string in the operand

(If there are multiple strings, this is the first string only.)

YK7231I PRT API RC=0

Value: message-value

This message outputs (in message-value) additional information about the command return configuration structure for the BC Manager message that was output immediately beforehand.

YK7232E PRT RC=48

DEVN or DUMMY (device-number1) was specified, but another DEVN or DUMMY (device-number2) is already specified for this CDEV.

Different device numbers were specified for one CDEV.

device-number1

Newly specified device number

device-number2

Previously specified device number

YK7233E PRT RC=44

No route starting from the specified DAD in the specified route list.

In the specified route list definition file, there is no route starting from the specified DAD.

Check the route list definition file or DADID.

YK7321E API RC=36 (cgid)

The copy group is not loaded.

To perform this processing, you need to load the copy group whose ID is cgid in advance.

cgid

ID of the copy group that needs to be loaded before performing the processing

YK7322E API RC=36 (psetid)

The path set is not loaded.

To perform this processing, you need to load the path set whose ID is psetid in advance.

psetid

ID of the path set that needs to be loaded before performing the processing

YK7323E API RC=36

No copy group is specified.

No copy group ID is specified.

YK7324E API RC=36

No path set is specified.

No path set ID is specified.

YK7325E API RC=36 (prefix)

Another prefix definition file is already loaded.

The configuration file cannot be loaded because a configuration file with a different prefix has been loaded.

prefix

Prefix of the loaded configuration file

YK7390I API TSO RC=0

The BCM Web API server has started.

The BCM Web API server started.

YK7399I API TSO RC=0

The BCM Web API server has ended. RC=rc

The BCM Web API server ended.

rc

Exit code of the BCM Web API server

YK7400E API TSO RC=-3

Failed to set the appropriate TSO/E profile.

In TSO/E environment setup, the PROFILE command could not set NOWTPMSG and NOINTERCOM.

YK7401E API TSO RC=-3

The SYSCALL environment cannot be established.

The SYSCALL environment could not be established.

YK7402E API TSO RC=-3

A JSON parser is unavailable.

HWTJSON in the host command environment is not available.

YK7403E API TSO RC=40

A msgrcv error occurred. RC=rc

The BCM Web API request could not be received because the syscall command of msgrcv returned a negative return value (rc). For details about rc, see the IBM manual z/OS Using REXX and z/OS UNIX System Services.

rc

Return value of address syscall msgrcv

YK7404E API TSO RC=40

A msgrcv error occurred. errno=errnos reason=errnojrs

The BCM Web API request could not be received because the msgrcv function returned a return value (rc) other than 0. For details about errnos and errnojrs, see the IBM manual z/OS UNIX System Services Messages and Codes.

errnos

z/OS UNIX return code returned by msgrcv

errnojrs

z/OS UNIX reason code returned by msgrcv

YK7405E API TSO RC=40

A msgsnd error occurred. RC=rc

The BCM Web API response could not be sent because the syscall command of msgsnd returned a negative return value (rc). For details about rc, see the IBM manual z/OS Using REXX and z/OS UNIX System Services.

rc

Return value of address syscall msgsnd

YK7406E API TSO RC=40

A msgsnd error occurred. errno=errnos reason=errnojrs

The BCM Web API request could not be received because the msgsnd function returned a return value (rc) other than 0. For details about errnos and errnojrs, see the IBM manual z/OS UNIX System Services Messages and Codes.

errnos

z/OS UNIX return code returned by msgsnd

errnojrs

z/OS UNIX reason code returned by msgsnd

YK7407E API TSO RC=8

The request message is too long.

The BCM Web API request could not be received because the body length of the BCM Web API request exceeded the value specified for the REQBUFSIZE default parameter.

YK7408E API TSO RC=40

The BC Manager cannot be executed. YKINSCHK RC=rc

The BCM Web API server cannot start because the YKINSCHK command returned a return value other than 0.

YK7409E API TSO RC=8

The response message is too long.

The BCM Web API response could not be sent because the body length of the BCM Web API response exceeded the value specified for the RESPBUFSIZE default parameter.

YK7410E API RC=40 (service-name)

service-name failed. RC=rc

The ADDRESS HWTJSON host command returned a host return code (rc) other than 0. For details about host return codes, see the chapter "The z/OS JSON parser" in the IBM manual z/OS MVS Programming: Callable Services for High-Level Languages.

service-name

Service name of the z/OS JSON parser callable service run by the HWTJSON host command

rc

Host return code returned by the HWTJSON host command

YK7411E API RC=48 (reason-Desc)

service-name failed. RC=return-Code reason=reason-Code

The service-name service of the z/OS JSON parser callable service returned a return code (return-Code) other than 0. For details about return-Code, see the chapter "The z/OS JSON parser" in the IBM manual z/OS MVS Programming: Callable Services for High-Level Languages.

service-name

Service name of the z/OS JSON parser

return-Code

Return code of the z/OS JSON parser service-name service

reason-Code

Error reason code of the z/OS JSON parser service-name service

reason-Desc

Error text of the z/OS JSON parser service-name service

YK7412E API RC=48

The value of the key-name key is invalid.

The value of the key-name key in the request body of the BCM Web API is invalid or the value type is invalid.

key-name

Key name specified in the BCM Web API request body

YK7413E API RC=48

The value of the key-name key is not specified.

The required key indicated by key-name is not specified in the request body of the BCM Web API.

key-name

Required key name

YK7414E API RC=48 (index)

The value of the key-name key is invalid.

The key-name key in the request body of the BCM Web API contains an error in the value type of the array value element.

index

If key-name is CLIPARMS, this is the element number of the key value array (first element = 0).

YK7415E API RC=48 (index)

The value of the key-name key is too long.

The string length specified in the array value element of the key-name key in the request body of the BCM Web API exceeds the limit value.

index

If key-name is CLIPARMS, this is the element number of the key value array (first element = 0).

YK7416I API TSO SC=0 RC=0

text

text

Message text output by the TSO/E console

YK7430E API RC=40

Allocation of the dd name failed. DD=dd-name

The DD with the name specified in dd-name could not be allocated.

dd-name

Name of the DD that could not be allocated

YK7431I API TSO RC=0

Allocation of the BCM Web API log data set failed. DSN=data-set-name

The BCM Web API log dataset indicated by data-set-name could not be allocated.

data-set-name

Name of the BCM Web API log dataset that could not be allocated

YK7432I API TSO RC=0

Execution of the LISTDSI command for the BCM Web API log data set failed. DSN=data-set-name reason=SYSREASON

The LISTDSI function could not be run successfully for the BCM Web API log dataset indicated by data-set-name.

SYSREASON

Reason code set in the SYSREASON variable by the LISTDSI function

YK7433I API TSO RC=0

Execution of the EXECIO command for the BCM Web API log data set failed. RC=rc: data-set-name

The BCM Web API log dataset indicated by data-set-name could not be opened or output.

rc

Return value of EXECIO, which was issued to output logs to the BCM Web API log dataset

data-set-name

BCM Web API log dataset name

YK7434I API TSO RC=0

The DSORG of the BCM Web API log data set is incorrect. DSN=data-set-name

The dataset organization of the BCM Web API log dataset indicated by data-set-name is incorrect.

data-set-name

BCM Web API log dataset name

YK7435I API TSO RC=0

The LRECL of the BCM Web API log data set is incorrect. DSN=data-set-name

The record length of the BCM Web API log dataset indicated by data-set-name is incorrect.

data-set-name

BCM Web API log dataset name

YK7436I API TSO RC=0

The BCM Web API log data set is not found or unavailable. DSN=data-set-name

The BCM Web API log dataset indicated by data-set-name was not found or is unusable.

data-set-name

BCM Web API log dataset name

YK7437I API TSO RC=0

The prefix of the BCM Web API log data set is not specified.

The log cannot be output because the prefix of the log dataset of the BCM Web API server cannot be identified due to one of the following factors.

  • The BCM Web API server started without the default parameters being allocated to the DD name CLIDFLTS.

  • The APILOGPREFIX parameter is not specified as a default parameter.

  • The value of the APILOGPREFIX default parameter is incorrect.

YK7440E API TSO RC=44

Initialization the response buffer failed. reason=reason

The BCM Web API response buffer could not be initialized due to one of the following factors.

reason

Reasons for the error

  • 00000024: BPX1QSN could not be loaded.

  • 0000002C: The GETMAIN request for the response buffer ended in an error.

  • 00000034: The value specified for the third parameter of YKAPISRV is invalid.

YK8001I CON

BCM Monitor started. (v.r.m-nn)

BCM Monitor has started.

v.r.m-nn

Version and revision number

YK8002I CON

BCM Monitor terminated.

BCM Monitor has stopped.

YK8003I PRT CON

time BCM Monitor stopped monitoring Copy Groups.

BCM Monitor set the monitoring status of all copy groups to INACTIVE.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8007I PRT CON

time Synchronization percentage decreased, Copy Group: cgid.

The copy progress percentage for the copy group (cgid) is decreasing.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

cgid

Copy group ID

YK8008E CON

BCM Monitor initialization failed: termination-code.

An attempt to start BCM Monitor failed because of the reason indicated in a preceding message that was output to either the console or dd SYSTSPRT.

Contact the center administrator. If you are the center administrator, take action that is appropriate to the previously output message, and then restart BCM Monitor.

termination-code (decimal number)
  • 04: An attempt was made to start BCM Monitor without using IKJEFT01.

  • 20: An attempt to analyze the YKMONOPT file failed.

  • 24: An attempt to analyze the YKMONCG file failed.

  • 32: An error occurred while loading the process module.

  • 36: No profile is defined in the FACILITY class of RACF.

  • 40: The prefix specified in the YKMONCG file is being used by the Business Continuity Manager agent.

  • 44: An attempt to initialize the subtask failed.

YK8009E CON

Task(task-ID) abended: completion-code.

The task terminated abnormally during startup of BCM Monitor. BCM Monitor will stop.

task-ID

Name for identifying the task

completion-code

System completion code

YK8010E CON

Module not found: load-module-name.

The load module identified by load-module-name cannot be found. BCM Monitor will stop.

Check whether the load module has been properly installed.

YK8011E CON

The profile is not defined in the facility class of RACF: xxxxxxxx.

The STGADMIN.YKA.BCM.YKQUERY profile or the STGADMIN.YKA.BCM.COMMANDS profile is not defined in the FACILITY class of RACF.

Review the RACF settings, and then restart BCM Monitor.

xxxxxxxx

Maintenance information

YK8012E CON

The specified prefix is being used by another program: prefix-name.

The specified prefix prefix-name is being used by another program.

Review the YKMONCG file.

YK8013E CON

BCM Monitor abended.

BCM Monitor terminated abnormally.

If you cannot determine the cause of this problem, obtain an ABEND dump in SYSABEND dump format, and then make a request to the Support Center to investigate the problem.

YK8014I CON

MODIFY command accepted: command-name.

BCM Monitor accepted the MODIFY command-name command.

YK8015I CON

STOP command accepted.

BCM Monitor accepted the STOP command.

YK8016E CON

Command syntax error.

There is an error in the command syntax.

Make sure that the entered command is valid.

YK8017E CON

Invalid command: command-name.

There is an error in the command-name command.

Make sure that the entered command is valid.

YK8018E CON

Operand is incorrect: command-name.

There is an error in an operand of the command-name command.

Correct the operand, and then re-enter the command.

YK8019E CON

The number of commands of execution waiting exceed the upper limit: command-name.

An attempt to execute the command identified by command-name failed because the number of commands waiting to be executed has reached the upper limit.

Wait until all the waiting commands are finished executing, and then re-execute the command.

YK8020I CON

nn: command-name[ parameter].

Information is displayed for the command waiting to be executed.

nn

Number assigned to the waiting command

command-name

Name of the waiting command

The full name of the command is displayed, even if the abbreviated name of the command was entered.

parameter

Parameter specified in the waiting command

The full name of the parameter is displayed, even if the abbreviated name of the parameter was specified. If an omittable parameter was omitted, the default value is displayed.

YK8021I CON

Execution waiting command none.

There is no command waiting to be executed.

YK8022I CON

The state of sleep was released.

BCM Monitor returned from the sleep state.

YK8023W CON

The WAKEUP command was not executed because it is not in a sleep status.

The WAKEUP command cannot be executed because BCM Monitor is not in the sleep state.

YK8024E CON

Insufficient space available: maintenance-information.

An attempt to allocate space to BCM Monitor failed. BCM Monitor will stop.

Increase the region size, and then restart BCM Monitor.

maintenance-information

Detailed information to assist in analyzing the error

YK8025E CON

IRXJCL module error: return-code.

The IRXJCL routine returned an error with the return code identified by return-code. BCM Monitor will stop.

Check the return code. If the code is 20, the SYSEXEC DD statement might be invalid in the cataloged procedure for startup for BCM Monitor.

Check the JCL, and then re-execute IRXJCL.

return-code
  • 20: EXEC processing failed.

  • 20021: There was an error in the parameter list that was passed to IRXJCL.

YK8026E CON

IRXINIT module error: code=​return-code,​R0=​abnormal-​termination-​code-​and-​reason-​code,​PARM7=​reason-code.

The IRXINIT routine returned an error with the return code identified by return-code. BCM Monitor will stop.

Check the return code.

return-code
  • 20: Processing failed due to an error. Check the reason code returned to PARM7 by IRXINIT.

  • 100: Processing failed because the system abnormally terminated while IRXINIT was checking the environment. The system might output multiple messages reporting abnormal termination. R0 includes the abnormal termination code and the reason code for abnormal termination.

abnormal-termination-code-and-reason-code

IRXINIT returns the abnormal termination code in the two trailing bytes of R0 and returns the reason code for abnormal termination in the two leading bytes of R0. If the reason code for abnormal termination is larger than two bytes, IRXINIT returns only the two trailing bytes for the reason code for abnormal termination. For details on the abnormal termination code and reason code, see the IBM manual MVS System Codes.

reason-code

For details about the reason code, see the IBM manual TSO/E REXX Reference.

YK8027E CON

IRXTERM module error: code=​return-code,​R0=​abnormal-​termination-​code-​and-​reason-​code.

The IRXTERM routine returned an error with the return code identified by return-code. BCM Monitor will stop.

Check the return code.

return-code

For details about the return code, see the IBM manual TSO/E REXX Reference.

abnormal-termination-code-and-reason-code

R0 includes the abnormal termination code and the reason code for abnormal termination. IRXTERM returns the abnormal termination code in the two trailing bytes of R0 and returns the reason code for abnormal termination in the two leading bytes of R0. If the reason code for abnormal termination is larger than two bytes, IRXTERM returns only the two trailing bytes of the reason code for abnormal termination. For details about the abnormal termination code and reason code, see the IBM manual MVS System Codes.

YK8028E CON

BCM Monitor function abend: code=Sxxx Uxxxx

abended-module=module-name C-Date=module-creation-date

base=bbbbbbbb disp=dddd

[calling-module=module-name C-Date=y'y'.m'm'.d'd' base=bbbbbbbb disp=dddd]

PSW=pppppppp pppppppp ILC=ll INTC=xx

Registers at time of failure

GR 00-03 contents-of-register-0 contents-of-register-1 contents-of-register-2 contents-of-register-3

GR 04-07 contents-of-register-4 contents-of-register-5 contents-of-register-6 contents-of-register-7

GR 08-11 contents-of-register-8 contents-of-register-9 contents-of-register-10 contents-of-register-11

GR 12-15 contents-of-register-12 contents-of-register-13 contents-of-register-14 contents-of-register-15

The main task or subtask terminated abnormally during BCM Monitor processing. If the task cannot be recovered, BCM Monitor will stop.

Contact the center administrator.

Sxxx (hexadecimal number)

System completion code when the task terminated abnormally

Uxxxx (decimal number)

User completion code when the task terminated abnormally

module-name

Section name of the BCM Monitor module or load module name.

If the module cannot be identified, UNKNOWN is displayed. In this case, the values of y'y'.m'm'.d'd' and bbbbbbbb are invalid.

module-creation-date

This is displayed in one of the following formats:

  • y'y'.m'm'.d'd': Creation date of the module identified by module-name

  • y'y'/m'm'/d'd': Creation date of the module identified by module-name

bbbbbbbb

Contents of the base register

dddd
  • ABENDED-MODULE: Location where ABENDED-MODULE was called, relative to the top of the module

  • CALLING-MODULE: Location where CALLING-MODULE was called, relative to the top of the module

pppppppp pppppppp

PSW during the abnormal termination

ll

Length of the command during the abnormal termination

xx

Interrupt code during the abnormal termination

YK8031W CON

The specified error-type is invalid: command-name.

The value identified by error-type, which was specified in the command-name command, is invalid.

error-type
  • label: The label name is invalid. Check the label name for ACTION=STOPPOINT specified in the YKMONCG file.

  • copy group: The copy group ID is invalid. Check the copy group ID for CGID specified in the YKMONCG file.

YK8032E CON

service-name service error occurred: return code=return-code, reason code=reason-code.

The TSO/E service routine (service-name) returned an error with the return code identified by return-code.

Check the return code.

For details about return-code and reason-code, see the IBM manual TSO/E Programming Services.

YK8040I PRT CON

time BCM Monitor will stop at STOPPOINT 'label'.

BCM Monitor will stop at the point label.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

label

Label at which BCM Monitor stops

YK8041I PRT CON

time BCM Monitor will stop at the end of monitor cycle.

BCM Monitor will stop at the end of a cycle.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8042I PRT CON

time BCM Monitor will sleep at STOPPOINT 'label' for max 'sleep-time' minutes.

BCM Monitor will go to sleep at the point label.

Entering the WAKEUP command resumes copy group monitoring before the duration identified by sleep-time has elapsed.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

label

Label at which BCM Monitor goes to sleep

sleep-time

Sleep duration

YK8043I PRT CON

time STOPPOINT 'label' reached.

BCM Monitor has reached the point label.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8044I PRT CON

time BCM Monitor will sleep now for max 'sleep-time' minutes.

BCM Monitor will sleep for the duration identified by sleep-time.

Entering the WAKEUP command resumes copy group monitoring before the duration identified by sleep-time has elapsed.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

sleep-time

Sleep duration

YK8045I PRT CON

time BCM Monitor reached the end of the monitoring cycle.

BCM Monitor has reached the end of a cycle.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8046I PRT CON

time Execute operator command 'opcmd'.

BCM Monitor will execute the operator command identified by opcmd.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8047I PRT CON

time Set MONITOR=status for Copy Group 'cgid'.

BCM Monitor set the monitoring status of the copy group cgid to the status status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

status
  • START: The monitoring status of the copy group was set to ACTIVE.

  • STOP: The monitoring status of the copy group was set to INACTIVE.

YK8048I PRT CON

time Set CYCLETIME to : cycletime.

BCM Monitor set CYCLETIME to the value identified by cycletime.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8049I PRT CON

time Set WAITTIMEOUT to : timeout.

BCM Monitor set WAITTIMEOUT to the value identified by timeout.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8050I PRT CON

time Set MSGLEVEL to : MSGLEVEL=lvllog,lvlcons.

BCM Monitor set MSGLEVEL to the values identified by lvllog and lvlcons.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

lvllog

Level of messages to be output to SYSTSPRT

lvlcons

Level of messages to be output to the console

YK8054I PRT CON

time BCM Monitor resume monitoring.

BCM Monitor resumed processing.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8055I PRT CON

time BCM Monitor will pause now for 'sleep-time' minutes.

BCM Monitor will go to sleep because the PAUSE action was executed.

Entering the WAKEUP command resumes copy group monitoring before the sleep time of sleep-time has elapsed.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

sleep-time

Sleep duration

YK8056E PRT CON

time Failed to execute operator command.

BCM Monitor failed to execute an operator command.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8070E PRT

time File Open error : dd-name.

The file dd-name could not be opened.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

dd-name

DD name of the file where the error occurred

YK8071E PRT

time File Close error : dd-name.

The file dd-name could not be closed.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

dd-name

DD name of the file where the error occurred

YK8073E PRT

time A GETMAIN error occurred. return code=nnn.

A GETMAIN error occurred. The program will stop running.

Contact customer support for assistance.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

nnn (decimal number)

Return code of the GETMAIN macro

YK8074E PRT

time A FREEMAIN error occurred. return code=nnn.

A FREEMAIN error occurred. The program will stop running.

Contact customer support for assistance.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

nnn (decimal number)

Return code of the FREEMAIN macro

YK8075E PRT

time Parameter syntax error : file : rec#.

There is a syntax error in a parameter.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

file

Name of the file where the error occurred

rec#

Number of the line in file where the error was detected

YK8076E PRT

time Invalid parameter was specified : file : rec#.

An invalid parameter was specified.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

file

Name of the file where the error occurred

rec#

Number of the line in file where the error was detected

YK8077E PRT

time Invalid value was specified for param parameter : file : rec#.

The parameter value param is invalid.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

file

Name of the file where the error occurred

rec#

Number of the line in file where the error was detected

YK8078E PRT

time A required parameter is missing : file : param-name.

The required parameter param-name is not specified.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

file

Name of the file where the error occurred

param-name

Name of the required parameter

YK8079E PRT

time CGID parameter must be specified first : rec#.

Specify the CGID parameter at the beginning of the copy group parameters in the YKMONCG file.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

rec#

Line number where the error was detected

YK8080E PRT

time Duplicate CGID parameters found : cgid.

The copy group cgid is specified more than once in the YKMONCG file.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

cgid

CGID parameter value that is specified more than once

YK8081E PRT

time Combination of STATUS and ACTION is invalid : rec#.

The combination of STATUS and ACTION specified in the YKMONCG file is invalid.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

rec#

Line number where the error was detected

YK8082E PRT

time Combination of Startup Status and NOCANCEL is invalid : rec#.

The combination of NOCANCEL and the startup status specified for the CGSTARTUPSTATUS parameter in the YKMONCG file is invalid.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

rec#

Line number where the error was detected

YK8083E PRT

time The corresponding CGID parameter is not defined : cgid.

The copy group cgid specified in the ACTION parameter of the YKMONCG file is not defined.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

cgid

Copy group ID specified in the ACTION parameter

YK8084E PRT

time The continuation symbol can not be specified in the final record : file.

The continuation symbol was specified for the final record.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

file

Name of the file where the error occurred

YK8085E PRT

time File record format is invalid : dd-name.

The record format of the file indicated by dd-name is invalid.

The valid record format is F, FB, V, or VB.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

dd-name

DD name of the file where the error occurred

YK8100I PRT CON

time sendmsg

The message (sendmsg) appears. The message is specified in SENDMSG with the CONS level designated.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8200I PRT CON

time sendmsg

The message (sendmsg) appears. The message is specified in SENDMSG with the ERROR level designated.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8220E PRT CON

time cmd error for Copy Group 'cgid'

time return code rc received from cmd

time COMMAND : 'cmd-parm'

time MSG:

time ['err-msg'].

An error occurred during execution of the cmd command for the copy group identified by cgid.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

cmd-parm

Executed CLI command

rc

Return code from the CLI command

err-msg

Message included in the message structure for the CLI command

The number of lines equal to the number of messages included in the message structure are displayed.

YK8221I PRT CON

time YKEWAIT (RC=4) : TIMEOUT value (timeout) reached.

The YKEWAIT command timed out before the transition to the expected group status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

timeout

Timeout value

YK8222E PRT CON

time YKEWAIT (RC=8) : Unexpected status reached.

An unexpected group status was reached during execution of the YKEWAIT command.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8223W PRT CON

time cmd (RC=4) : Some volumes with invalid status found.

Invalid volumes were detected in the copy group during the execution of the CLI command cmd. Processing of these volumes was skipped.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8230E PRT CON

time REPORT type is only valid for UR Copy Groups.

type, which was specified for the REPORT parameter, is only valid for Universal Replicator copy groups.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

type

Report type

YK8231E PRT CON

time BCM Monitor can not adjust Copy Group status.

BCM Monitor could not set the copy group to the specified startup status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8300I PRT CON

time sendmsg

The message (sendmsg) appears. The message is specified in SENDMSG with the STATUS level designated.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8301I PRT CON

time Not all volumes are in 'status'. action requested.

The action identified by action will be executed because there is a volume that is not in the status identified by status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8302I PRT CON

time Trying to cmd Copy Group 'cgid'.

The CLI command identified by cmd will be executed for the copy group identified by cgid.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8303I PRT CON

time Waiting for status 'status'.

BCM Monitor will wait until the copy group being monitored enters the status identified by status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8304I PRT CON

time Copy Group is in 'status' status. Wait until status has changed.

BCM Monitor will wait until the copy group status identified by status changes to another status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8305I PRT CON

time Status ok.

The copy group entered the expected status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8310I

See YK8310I PRT.

N/A

YK8311I CON

REPORT SUMMARY:

COPY GROUP : cgid TYPE : cgtype

DAD-ID : dad PREFIX : prefix

SIMPLEX : simplexct PENDING : pendingct DUPLEX : duplexct SUSPEND : suspendallct OTHER : otherct

GROUP STATUS : status MATCHING% : match REVERSED% : rev%

ATTIME(GMT) : attime -STATUS : attms

The report information for when SUMMARY is specified for REPORT is displayed.

cgid

Copy group ID

cgtype

Copy group type

dad

Copy group local device address domain ID

prefix

Prefix

simplexct

Number of copy pairs in SIMPLEX status

pendingct

Number of copy pairs in PENDING status

duplexct

Number of copy pairs in DUPLEX status

suspendallct

Number of copy pairs in SUSPEND status

otherct

Number of copy pairs in other statuses

status

Copy group status

match

Copy progress percentage

rev%

Percentage of copy pairs whose copy direction is secondary-to-primary

attime

ATTIME suspend time

attms

ATTIME suspend status

YK8312I

See YK8312I PRT.

N/A

YK8313I CON

REPORT DETAIL:

COPY GROUP : cgid TYPE : cgtype

DAD-ID : dad PREFIX : prefix

VOLSER PDEVN DIR SDEVN STATUS MATCH% C/T SUBC/T DELTA CTTIME

volser pdevn dir sdevn status match ctid sub-ctid ctdelta cttime

The report information for when DETAIL is specified for REPORT is displayed.

cgid

Copy group ID

cgtype

Copy group type

dad

Copy group local device address domain ID

prefix

Prefix

volser

Volume serial number

pdevn

Primary device number

dir

Copy direction

  • >: Primary-to-secondary

  • <: Secondary-to-primary

sdevn

Secondary device number

status

Copy pair status

match

Copy pair matching percentage

ctid

Consistency group ID or master journal group ID

sub-ctid

Restore journal group ID

ctdelta

Consistency delta value for each consistency group

cttime

Consistency time for each consistency group

YK8314I

See YK8314I PRT.

N/A

YK8315I CON

REPORT RPO:

COPY GROUP : cgid

C/T SUBC/T PSN SSN DELTA CTTIME

ctid sub-ctid psn ssn ctdelta cttime

The report information for when RPO is specified for REPORT is displayed.

cgid

Copy group ID

ctid

Consistency group ID or master journal group ID

sub-ctid

Restore journal group ID

psn

Serial number of the primary storage system

ssn

Serial number of the secondary storage system

ctdelta

Consistency delta value

cttime

Consistency time

YK8318I

See YK8318I PRT.

N/A

YK8319I CON

REPORT STATS:

COPY GROUP : cgid TYPE : cgtype

DAD-ID : dad PREFIX : prefix

C/T SUBC/T PSN SSN TRANS PJMET% PJDAT% SJMET% SJDAT% PJDATA SJDATA

ctid sub-ctid psn ssn mcu-to-rcu-kbps p-jnl-meta p-jnl-data s-jnl-meta s-jnl-data p-jnl-data-capacity s-jnl-data-capacity

The report information of the Universal Replicator copy group for when STATS is specified for REPORT is displayed.

cgid

Copy group ID

cgtype

Copy group type

dad

Copy group local device address domain ID

prefix

Prefix

ctid

Master journal group ID

sub-ctid

Restore journal group ID

psn

Serial number of the primary storage system

ssn

Serial number of the secondary storage system

mcu-to-rcu-kbps

Data transfer rate (Kbps) between the main control unit and the remote control unit

p-jnl-meta

Metadata % used rate in master journal volume

p-jnl-data

Data % used rate in master journal volume

s-jnl-meta

Metadata % used rate in restore journal volume

s-jnl-data

Data % used rate in restore journal volume

p-jnl-data-capacity

Master journal volume data capacity (GB)

s-jnl-data-capacity

Restore journal volume data capacity (GB)

YK8320I PRT CON

time Copy Group 'cgid' has reached target status 'status'.

The copy group (cgid) has switched to the target status identified by status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8321I PRT CON

time Some volumes are in a 'TRANSITION' status.

Some volumes are in the TRANSITION status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8322I PRT CON

time Some volumes are in a 'TRANSITION', 'SIMPLEX', 'HOLD' OR ERROR status.

Some volumes are in the TRANSITION, SIMPLEX, HOLD status, or an abnormal status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8323I PRT CON

time Some volumes are not in a 'HOLDER' status.

Some volumes are not in the HOLDER status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8324I PRT CON

time All volumes are in 'HOLDER' status.

All volumes are in the HOLDER status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8325I PRT CON

time Copy Group 'cgid' is 'status' now.

The copy group (cgid) entered the status identified by status.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8326I PRT CON

time Copy Group 'cgid' will be suspended at: atparm.

The copy group (cgid) set to suspend at the time indicated by atparm.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

atparm

ATTIME suspend time

YK8330I

See YK8330I PRT.

N/A

YK8331I CON

REPORT DETAIL:

COPY GROUP : cgid TYPE : cgtype

DAD-ID : dad PREFIX : prefix

VOLSER PDEVN DIR SDEVN STATUS MATCH% C/T SUBC/T DELTA CTTIME

volser pdevn dir sdevn status match ctid sub-ctid ctdelta cttime

The report information for when DETAIL is specified for REPORT is displayed.

cgid

Copy group ID

cgtype

Copy group type

dad

Copy group local device address domain ID

prefix

Prefix

volser

Volume serial number

pdevn

Primary device number

dir

Copy direction

  • >: Primary-to-secondary

  • <: Secondary-to-primary

sdevn

Secondary device number

status

Copy pair status

match

Copy pair matching percentage

ctid

Consistency group ID or master journal group ID

sub-ctid

Restore journal group ID

ctdelta

Consistency delta value for each consistency group

cttime

Consistency time for each consistency group

YK8400I PRT CON

time sendmsg

The message (sendmsg) appears. The message is specified in SENDMSG with the INFO level designated.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8401I PRT CON

time Check Startup Status of Copy Group 'cgid':

BCM Monitor will start checking the status of the copy group (cgid).

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8402I PRT CON

time Startup Status check of Copy Group 'cgid' finished.

The status check of the copy group (cgid) is complete.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8403I PRT CON

time Start monitoring Copy Group.

BCM Monitor will start monitoring the copy group.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

YK8404I PRT CON

time Execute action 'action err-action'

BCM Monitor will execute the action (action err-action) specified in the ACTION parameter for STATUS.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

action

Action to be executed

err-action

Error action to be executed

YK8405I PRT CON

time The return code of the action is RC=rc.

An error identified by rc occurred as the result of executing an action.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

rc
  • When the action is not an EXEC action:

    Return code of the Business Continuity Manager CLI command executed by the action

  • When the action is an EXEC action:

    Return code of the TSO/E EXEC command that executed the script

    If the return code is 12, the EXEC command of TSO/E might have failed to access the script file. Make sure that the script name specified for the EXEC action is correct.

YK8406I PRT CON

time Execute error action 'err-action'.

BCM Monitor will execute the error action identified by err-action.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

err-action

Error action to be executed

YK8410I PRT CON

time ---- date ----

The date is displayed when BCM Monitor is started or when the date changes while BCM Monitor is running.

time

Message output time

This is only displayed when the output destination is SYSTSPRT.

date

New date

For example, Thursday, 21 Jan 2010 is displayed.

YK8411I

See YK8411I PRT.

N/A

YK8412I CON

SYSTEM OPTIONS:

CYCLE TIME : cycletime WAITFOR TIMEOUT : timeout MSGLEVEL : lvllog,lvlcons ONACTIONERROR : err-action

STOP AT STOPPOINT : stoppt SLEEP AT STOPPOINT : sleeppt

This message indicates the values specified in the YKMONOPT file.

cycletime

Cycle time

timeout

Timeout value

lvllog

Level of messages to be output to SYSTSPRT

lvlcons

Level of messages to be output to the console

err-action

Error action to be executed

stoppt

Stop point

sleeppt

Sleep point

YK8413I

See YK8413I PRT.

N/A

YK8414I CON

COPY GROUP DEFINITIONS:

ID : cgid PREFIX : prefix

DAD-ID : dad ROUTE LIST : route[,route-label] VIACDEV : cgviacdev

MONITOR STATUS : cgmonstat STARTUP STATUS : cgsastat,cgsaact,cgsaopt

WHEN STATUS status DO ACTION 'action;err-action;'

This message indicates the values specified in the YKMONCG file. This message appears a number of times, equal to the number of copy groups specified.

cgid

Copy group ID

prefix

Prefix

dad

Copy group local device address domain ID

route

Route list ID

route-label

Route label

cgviacdev

The specified method for issuing commands

  • Y: Method for issuing commands via command devices

  • N: Method for issuing commands without passing through command devices

cgmonstat

Copy group monitoring status (ACTIVE or INACTIVE)

cgsastat

Copy group startup status to be checked when BCM Monitor starts

cgsaact

Startup action executed if the copy pair status for starting BCM Monitor is different from the specified startup status

cgsaopt

Option information of the CGSTARTUPSTATUS parameter

status action err-action

Status, action, and error action for the copy group specified in STATUS and ACTION

These parameters appear a specified number of times.

YK9001I ISPF zOSMF RC=0

The license key(s) has been installed

The license key was installed.

YK9051E ISPF zOSMF RC=40

An error occurred in the license information dataset

An error occurred with the license information dataset.

Check that the prefix of the license information dataset is registered correctly, and that the license information dataset is created correctly. If necessary, recreate the license information dataset and re-register the license keys in the order in which they were issued.

For details about registering a prefix name of the license information dataset, see the Hitachi Business Continuity Manager Reference Guide.

YK9052E ISPF zOSMF RC=44

An error occurred in the license key dataset

An error occurred with the license key dataset.

Check that the dataset name of the license key dataset is correct, and that the license key dataset is created correctly. If necessary, transfer the license key file again and recreate the license key dataset.

YK9071W ISPF zOSMF RC=48

A license key was not found

An attempt was made to install a license key, but no installable license key was found in the license key dataset.

Make sure that none of the following conditions exist:

  • The license key you attempted to install was already installed.

  • The license key you attempted to install was not for this product.

  • The dataset you specified was not a license key dataset.

YK9072W ISPF zOSMF RC=48

The license key could not be installed.

An attempt to install the license key has failed.

Check if one of the following conditions is applicable. If none is applicable, make sure the key code is correct:

  • The license key you attempted to install was already installed.

  • The license key you attempted to install was not for this product.

YK9080E CON

The expiration date for your license key (function).

The license (function) has expired.

To continue using this product after the expiry date, you need a permanent license.

If function is Basic:

A permanent license for Business Continuity Manager Basic is required.

If function is UR 4x4 Extended CTG:

A permanent license for Business Continuity Manager UR 4x4 Extended CTG is required.

YK9081W CON

Your function license will expire in n day(s).

The license (function) will expire in n days.

To continue using this product after the expiry date, you need a permanent license.

If function is Basic:

A permanent license for Business Continuity Manager Basic is required.

If function is UR 4x4 Extended CTG:

A permanent license for Business Continuity Manager UR 4x4 Extended CTG is required.

Table. List of messages starting with YK (YKA0x - YKB20x)

Message ID

Message text

Explanation and recommended actions

YKA000T TSO

Supplied parameters invalid

An error was detected during parameter analysis.

YKA001E TSO

HANDLE() value not valid

The handle value assigned to the HANDLE parameter is invalid.

YKA002E TSO

HANDLE() parameter required for this operation

The OP(GET) and OP(CLOSE) requests require the HANDLE parameter to be specified.

Use the handle value returned by the OP(OPEN) request in the YKA098I message.

YKA003E TSO

OP(OPEN|GET|CLOSE) option required

The OP parameter is missing.

Specify the OP parameter.

YKA004E TSO

Buffer full; messages discarded

An attempt to acquire the IEA494I console message, IOSHM0414I console message, or the message specified in the MSGID parameter of a message monitoring command failed. This problem sometimes occurs when there is too much traffic for console messages, or when the issuance interval of a message monitoring command is too long.

If you receive this message while using Business Continuity Manager, issue the YKQUERY command to check the copy pair status.

The message monitoring command is KTCONMSG or YKCONMSG.

YKA006E TSO

SYSTEM ERROR. error-type

A system error was detected.

Contact customer support for assistance.

error-type

Type of system error

YKA007E TSO

TIMEOUT() value not valid

The value specified in the TIMEOUT parameter is invalid.

YKA008E TSO

TIMEOUT() parameter cannot be specified for this operation

If GET or CLOSE is specified in the OP parameter, you cannot specify the TIMEOUT parameter.

Specify OPEN in the OP parameter, and then specify the TIMEOUT parameter.

YKA009E TSO

MSGID() value not valid

The value specified in the MSGID parameter is invalid.

YKA010E TSO

MSGID() parameter cannot be specified for this operation

If GET or CLOSE is specified in the OP parameter, you cannot specify the MSGID parameter.

Specify OPEN in the OP parameter, and then specify the MSGID parameter.

YKA011E TSO

AUTO() value is not valid

The value specified in the AUTO parameter is invalid.

YKA012E TSO

parameter-name parameter cannot be specified for this operation

The parameter parameter-name cannot be specified with the OP parameter for the operation that was executed.

If parameter-name is AUTO():

Specify OPEN in the OP parameter, and then specify the AUTO parameter.

If parameter-name is HANDLE():

Specify GET or CLOSE in the OP parameter, and then specify the HANDLE parameter.

YKA096I TSO

No message found

The processing of a message monitoring command with OP(GET) specified exceeded the time specified in the TIMEOUT parameter, but the IEA494I console message, IOSHM0414I console message, or the message specified in the MSGID parameter of the message monitoring command has not arrived.

Re-execute the command after the system becomes ready to receive messages.

The message monitoring command is KTCONMSG or YKCONMSG.

YKA097I TSO

message-text

A message monitoring command with OP(GET) specified returned the messages in the order they arrived.

message-text

The IEA494I console message, IOSHM0414I console message, or message specified in the MSGID parameter of the message monitoring command

The message monitoring command is KTCONMSG or YKCONMSG.

YKA098I TSO

HANDLE(x'handle')

A message monitoring command with the OP(OPEN) parameter specified was executed successfully.

From this point onward, when executing a message monitoring command with the OP(GET) or OP(CLOSE) parameter specified, use the handle value returned in handle.

The message monitoring command is KTCONMSG or YKCONMSG.

YKA099I TSO

Close operation complete

A message monitoring command with the OP(CLOSE) parameter specified ended normally.

The message monitoring command is KTCONMSG or YKCONMSG.

YKB001I TSO

YKP2B completed. RC=return-code

The YKP2B command terminated.

return-code

The return code of the YKP2B command:

0: The command ended successfully. The copy group definition file was output.

4: Indicates that one of the following occurred.

- The command ended successfully. No copy pair was detected within the range of the specified device numbers.

- A copy group definition file was created, but volume information not defined in the disk configuration definition file for the site specified in the DAD parameter was detected among copy pairs within the range specified in the DEVN parameter.

- A copy group definition file was created, but a change was detected in the I/O configuration when the YKP2B command was executed with CHECK specified in the HS parameter.

8: An I/O error occurred in a volume within the search range. The copy group definition file was created for the volume that was successfully detected.

44: The processing was canceled due to an error. The copy group definition file was not created.

48: The command ended due to an invalid parameter.

YKB002I TSO

No copy pair was discovered.

No copy pair was detected within the specified range.

Check the operating range and status of the copy pair that you want to acquire, and execute the YKP2B command again. If the copy pair status is SIMPLEX, the YKP2B command does not detect any copy pair.

YKB100E TSO

Missing or invalid parameter: parameter-name

The parameter is not specified, or an invalid value is specified for the parameter.

Check the following, and then re-execute the command:

  • Make sure that the required parameter (parameter-name) was specified.

  • Make sure that the value specified for the required parameter (parameter-name) is valid.

  • Make sure that different device address domain IDs for the primary and secondary sites are specified for the DAD parameter.

YKB101E TSO

The specified PREFIX is being used by another program.

The specified prefix is being used by another program.

Check the value specified for the prefix.

YKB102E TSO

Error occurred during execution. Cmd=info

msg=message-text: message-value: message-severity

An error occurred during execution of the YKP2B command.

See the explanation corresponding to the message ID of the error message indicated by message-text and take appropriate action. Also see the additional information indicated by message-value and message-severity and take appropriate action. If the problem is not resolved, contact customer support.

info

Maintenance information

message-text

Error message

message-value

Additional information about the error message

If no additional information is available, a space is displayed.

message-severity

Additional information about the error message

If no additional information is available, a space is displayed.

The error messages message-text, message-value, and message-severity are displayed on the TSO/E terminal. Long error messages may extend over several lines.

YKB103E TSO

The parameters parameter-name1 and parameter-name2 cannot be concurrently specified.

You cannot specify the parameter-name1 parameter and the parameter-name2 parameter at the same time.

YKB200W TSO

No information was acquired for DEVN=device-number

No copy pair information was acquired from the volume with the device number device-number.

There might not be a volume for the specified device number. If the volume exists for the specified device number, check the channel settings.

YKB201W TSO

No I/O paths are available for the specified devices. DEVN=device-number

No copy pair information was acquired from the volume with the device number device-number because no I/O paths are available, or because the active subchannel set ID is a value other than 0.

Verify the I/O path settings and the setting of the active subchannel set ID.

YKB202W TSO

Unable to resolve primary volume information. Pair=​CopyType,​DEVN=​Devn,​SN=​SerialNum,​CU=​CU#,​CCA=​CCA#

A P-VOL not defined in the disk configuration definition file was included among the PPRC copy pairs detected by the YKP2B command.

Check whether this P-VOL is defined in the disk configuration definition file.

CopyType

The copy type of the detected undefined volume

Devn

The device number of the detected undefined volume

SerialNum

The serial number of storage system of the detected undefined volume

CU#

The control unit number of the detected undefined volume

CCA#

The command control address number of the detected undefined volume

YKB203W TSO

Unable to resolve secondary volume information. Pair=​CopyType,​SN=​SerialNum,​CU=​CU#,​CCA=​CCA#

An S-VOL not defined in the disk configuration definition file was included among the PPRC copy pairs detected by the YKP2B command.

Check whether this S-VOL is defined in the disk configuration definition file.

CopyType

The copy type of the detected undefined volume

SerialNum

The storage system serial number of the detected undefined volume

CU#

The control unit number of the detected undefined volume

CCA#

The command control address number of the detected undefined volume

YKB204W TSO

A dynamic configuration change was detected. DEVN=device-number

A dynamic change was detected in an I/O configuration definition while the YKP2B command was executing with CHECK specified for the HS parameter.

Check the status of the device targeted by the YKP2B command, correct any errors in the configuration or execution conditions, and then re-execute the command.

device-number

Device number being processed when a dynamic change was detected in an I/O configuration definition

Table. List of messages starting with YK (YKC0x)

Message ID

Message text

Explanation and recommended actions

YKC000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the IKJPARS message (message ID starting with IKJ) that was output immediately before this message.

YKC001E MSG SC=48 RC=48

No controller ARRAYS() supplied

Nothing is assigned to the ARRAYS parameter.

YKC001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKC001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKC001E MSG SC=48 RC=48

No starting FROM() supplied

Nothing is assigned to the FROM parameter.

YKC002E MSG SC=48 RC=48

Controller ARRAYS(stem) does not include trailing "."

The last character of the ARRAYS parameter is not a period.

stem

Stem name assigned to the ARRAYS parameter

YKC002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKC002E MSG SC=48 RC=48

Results STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKC008E MSG SC=48 RC=48

Ending TO() not valid hex

The value specified in the TO parameter is not in hexadecimal format.

YKC008E MSG SC=48 RC=48

Starting FROM() not valid hex

The value specified in the FROM parameter is not in hexadecimal format.

YKC008E MSG SC=48

Starting FROMVSN() value invalid

The value specified in the FROMVSN parameter is invalid.

YKC008E MSG SC=48

Ending TOVSN() value invalid

The value specified in the TOVSN parameter is invalid.

YKC008E MSG SC=48

Subchannel set SCHSET() value invalid

The value specified in the SCHSET parameter is invalid.

YKC009E MSG SC=48 RC=48

Specify DEV# and VOLSER parm exclusively

You cannot specify a device number and a volume serial number at the same time.

YKC009E MSG SC=48 RC=48

Starting FROM() exceeds ending TO()

The value specified in the FROM parameter exceeds the value of the TO parameter.

YKC009E MSG SC=48 RC=48

Starting FROMVSN() exceeds ending TOVSN()

The value specified in the FROMVSN parameter exceeds the value of the TOVSN parameter.

YKC010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKC031I MSG SC=0 (count)

Scanned DASD Device Count

The number of DASD devices scanned by the YKSCAN command.

count

Number of scanned DASD devices

YKC032I MSG SC=0 (count)

Hitachi storage systems Devices Found

The number of Hitachi storage-system devices scanned by the YKSCAN command.

count

Number of Hitachi storage-system devices

YKC033I MSG SC=4 (count)

The specified devices that do not have any available I/O paths were skipped.

As a result of the device scan, information acquisition on devices for which no I/O path is available was skipped.

count

The number of devices skipped when the device information was acquired

YKC034E MSG SC=32 RC=32

A dynamic configuration change was detected during YKSCAN command processing.

A dynamic change to an I/O configuration definition was detected during processing of the YKSCAN command. This error may be due to the volume serial number in the acquired volume information differing from that in the actual configuration.

Check the disk configuration definition file after the scan is complete. If the volume serial number is different from the one in the actual configuration, re-execute the scan.

YKC099I TSO

YKSCAN command return code=nnnn, reason code=rrrr

The YKSCAN command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKD0x)

Message ID

Message text

Explanation and recommended actions

YKD000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKD099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKD001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKD001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKD002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKD002E MSG SC=48 RC=48

ORDER(stem) does not include trailing "."

The last character of the ORDER parameter is not a period.

stem

Stem name assigned to the ORDER parameter

YKD002E MSG SC=48 RC=48

ORDER() value invalid

The value assigned to the ORDER parameter is invalid.

YKD002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKD002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKD008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKD010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKD050E MSG SC=36 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKD099I TSO

YKDELETE command return code=nnnn, reason code=rrrr

The YKDELETE command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKE0x)

Message ID

Message text

Explanation and recommended actions

YKE000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKE099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKE001E MSG SC=48 RC=48

GOTO() not supplied

Nothing is assigned to the GOTO parameter.

YKE001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKE001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKE001E MSG SC=48 RC=48

TIMEOUT() not supplied

Nothing is assigned to the TIMEOUT parameter.

YKE001W MSG SC=4 RC=4

Timeout limit has expired, waiting for group copy-group to reach state state.

Processing is terminating because the timeout limit has expired.

Correct the timeout value or check that the status to be monitored is correctly specified. Use the YKQUERY command to check the status of the copy pairs. If there is a copy pair where a transition has not taken place, the S-VOL of that copy pair might be ONLINE. Make it OFFLINE and re-execute.

copy-group

Copy group ID

state

Status to be monitored

YKE002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKD002E MSG SC=48 RC=48

ORDER(stem) does not include trailing "."

The last character of the ORDER parameter is not a period.

stem

Stem name assigned to the ORDER parameter

YKD002E MSG SC=48 RC=48

ORDER() value invalid

The value assigned to the ORDER parameter is invalid.

YKE002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKE002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKE002E MSG SC=48 RC=48

TIMEOUT() value invalid

The value assigned to the TIMEOUT parameter is invalid.

YKE002E MSG SC=48 RC=48

UNTIL() value invalid

The value assigned to the UNTIL parameter is invalid.

YKE003E MSG SC=48 RC=48

GOTO value is invalid.

The value assigned to the GOTO parameter is invalid.

For the GOTO parameter, specify the DUPLEX, SUSPEND, SIMPLEX, SUSPVS, HOLD, SWAPPING, or SWAP2SUS option.

YKE003E MSG SC=8 RC=8

Unexpected transition of group copy-group pair index to state state. (pp,ss)

The copy pair in the copy group entered an unexpected status.

Check that the status to be monitored is correctly specified.

copy-group

Copy group ID

index

Pair index

Before version 2.0: Copy pair number

Version 2.0 or later: Copy group number and copy pair number

For details about identifying a volume with the copy group number and the copy pair number, see Identifying the volume to be processed

state

The status after the transition

pp,ss

P-VOL status code, S-VOL status code

If the status of the volume cannot be determined, ** will be displayed.

For details on the status codes, see the description of Using CLI commands to obtain status in the Hitachi Business Continuity Manager User Guide.

YKE008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKE010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKE099I TSO

YKEWAIT command return code=nnnn, reason code=rrrr

The YKEWAIT command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKF0x)

Message ID

Message text

Explanation and recommended actions

YKF000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKF099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKF001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKF001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKF002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKF002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKF002E MSG SC=48 RC=48

TIMEOUT() value invalid

The value assigned to the TIMEOUT parameter is invalid.

YKF010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKF050E MSG SC=48 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKF099I TSO

YKFREEZE command return code=nnnn, reason code=rrrr

The YKFREEZE command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKG0x)

Message ID

Message text

Explanation and recommended actions

YKG000T TSO SC=48

Supplied parameters invalid.

Invalid parameters have been specified.

YKG001E TSO RC=48

Unable to execute without valid MSG() parameter.

Specify a valid MSG parameter.

YKG002E TSO RC=48

MSG(stem) does not include trailing "." character.

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKG003E TSO RC=52

Unable to update MSG(stem) in Caller's environment. YKVSET result = result

An attempt to assign a value to a Message structure variable failed. The resulting value is displayed in result. This error can be caused by an invalid value being specified for the MSG parameter.

stem

Stem name assigned to the MSG parameter

YKG004E MSG SC=48 RC=48

Unable to execute without valid STEM() parameter.

Specify a valid STEM parameter.

YKG005E MSG SC=48 RC=48

STEM(stem) does not include trailing "." character.

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKG006E MSG SC=48 RC=48

Unable to execute without valid PREFIX() parameter.

Nothing or an invalid value is assigned to the PREFIX parameter.

To correct the error, see the CLI command descriptions in the Hitachi Business Continuity Manager Reference Guide, and then re-execute the command.

YKG008E MSG SC=48 RC=48

Unable to execute without valid SN() parameter.

An invalid value is assigned to the internal parameter SN that indicates the storage system serial number contained in the disk configuration definition file name.

Check the disk configuration definition file name.

YKG050W MSG SC=4 RC=4 (file:rec#)

Unrecognized element encountered: name

The system does not recognize the XML element name that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG051E MSG SC=36 RC=36 (file:rec#)

End of file encountered in comment.

XML input analysis detected a syntax error on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG053W MSG SC=4 RC=4 (file:rec#)

Unrecognized Version attribute value: value

The system does not recognize the version attribute value of the XML element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG054E MSG SC=36 RC=36 (file:rec#)

Unexpected termination of element: name

The XML element name that exists on the line with the line number identified by rec# in the file identified by file has not been correctly created.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG074E MSG SC=36 RC=36 (file:rec#)

Invalid "&" character discovered in quoted string. string

The & character string that exists on the line with the line number identified by rec# in the file identified by file has not been correctly escaped.

See the description of Extensible Markup Language (XML) 1.0 at http://www.w3.org.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG075W MSG SC=4 RC=4 (file:rec#)

Unrecognized Encoding attribute value: value

The system does not recognize the encoding attribute value of the XML element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG076W MSG SC=4 RC=4 (file:rec#)

Unrecognized attribute: name = value

The system does not recognize the XML attribute that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

name

XML attribute name

value

XML attribute value

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG077W MSG SC=4 RC=4 (file:rec#)

APIInfo Level=level invalid. Supported level is v.r.m.

The system does not recognize the Level attribute level of the APIInfo element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

v.r.m

API level

For details about this value, see the information about the XML document type definitions in the Hitachi Business Continuity Manager Reference Guide.

YKG079E MSG SC=44 RC=44 (result)

YKVSET program failure for: name = value

An attempt to assign the value value to the variable name failed with the result value identified by result. This error can be caused by an invalid value being specified for the STEM parameter.

YKG085E MSG SC=40 RC=40 (file:rec#)

Unable to read configuration file.

The configuration file could not be read, because the record length is too long.

file

Name of the configuration file where the error occurred

rec#

Number of the line in file where the error was detected

YKG088E MSG SC=40 RC=40 (file)

File Open error: dsstate.

An attempt to open the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKG089E MSG SC=40 RC=40 (file)

File Close error: dsstate.

An attempt to close the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKG090E MSG SC=40 RC=40 (file)

File Allocation Failed: dsstate.

An attempt to allocate the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKG091E MSG SC=40 RC=40 (file)

File Deallocation Failed: dsstate.

An attempt to deallocate the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKG092E MSG SC=40 RC=40 (file)

File Read error: dsstate.

An attempt to read the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKG099I MSG TSO

YKGETHDA command return code=max-value,reason code=reason-code.

The reading of the disk configuration definition file has finished.

This message is issued when an invalid disk configuration definition file is read in ISPF. If this message cannot be output to the REXX structure, it is output to the TSO/E terminal.

reason-code

Reason code for the returned max-value

max-value

Maximum value among the output return codes

Table. List of messages starting with YK (YKG2x - YKK10x)

Message ID

Message text

Explanation and recommended actions

YKG201E MSG SC=48 RC=48

Unable to execute without valid name parameter.

Nothing or an invalid value is assigned to the parameter identified by name.

YKG202E TSO RC=48

"SYSAUTH". cannot be specified in MSG() parameter.

SYSAUTH. cannot be specified in the MSG parameter. Specify a different name.

YKG203E MSG SC=48 RC=48

"SYSAUTH." cannot be specified in STEM() parameter.

SYSAUTH. cannot be specified for the STEM parameter. Specify a different name.

YKG204E TSO RC=48

name parameter is too long.

The parameter identified by name is too long.

YKG205E MSG SC=48 RC=48

name parameter is too long.

The parameter identified by name is too long.

YKG241W MSG SC=4 RC=4 (file:rec#)

The attribute attname is already defined.

The XML attribute identified by attname has already been defined.

Revise the specification of attname on line number rec# in file.

attname

XML attribute name

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG250E MSG SC=36 RC=36 (file:rec#)

The value value of the attribute name is an invalid format.

The value value of the XML attribute name is in an invalid format.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG251E MSG SC=36 RC=36 (file:rec#)

name attribute missing.

The required XML attribute name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG252E MSG SC=36 RC=36 (file:rec#)

The attribute statements are invalid.

The XML attribute description is invalid.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG253E MSG SC=36 RC=36 (file:rec#)

This kind of elements element can't be defined more than once.

The XML element element cannot be defined more than once.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG254E MSG SC=36 RC=36 (file:rec#)

The value value of attribute name is not match with filename.

The value value of the XML attribute name does not match the name in the file name.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG255E MSG SC=36 RC=36 (file:rec#)

The element name-1, for which the value value was specified for the attribute name-2, was not found.

The XML element name-1 with the value value specified for the XML attribute name-2 was not found.

Revise the specification on line number rec# in file.

file

Name of the configuration file in which the error was detected

rec#

Number of the line where the error was detected

YKG257E MSG SC=36 RC=36 (file:rec#)

The attribute name-1 is not a content of the element name-2.

The XML attribute name-1, which cannot be specified for the XML element name-2, was found.

Revise the specification on line number rec# in file.

file

Name of the configuration file in which the error was detected

rec#

Number of the line where the error was detected

YKG271E MSG SC=36 RC=36 (file:rec#)

The element name is required, but no element was found.

The required XML element name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG273E MSG SC=36 RC=36 (file:rec#)

The element statements are invalid.

The XML element description is invalid.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG274E MSG SC=36 RC=36 (file:rec#)

ETag name is mismatch. /correct-ETag-name is expected, but /incorrect-ETag-name is specified.

The specified ETag name /incorrect-ETag-name is not the expected ETag name /correct-ETag-name.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG275W MSG SC=4 RC=4 (file:rec#)

Extra ETag is specified: ETag-name

An extra ETag-name is specified.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG276E MSG SC=36 RC=36 (file:rec#)

The element name1 is not a content of the element name2.

The XML element identified by name2 contained the XML element name1 that cannot be specified.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG277E MSG SC=36 RC=36 (file:rec#)

name element missing.

The XML element name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG285E MSG SC=36 RC=36 (file:rec#)

Serial Number HDASN is required, but Serial Number DDSN is found.

The disk device element's SerialNum must be the same as the SerialNum value (HDASN) of the disk configuration element, but DDSN is defined for this value.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKG286E MSG SC=36 RC=36 (file:rec#)

Specify the local DADID of the primary site for the DAD() parameter.

A device address domain ID created by a remote scan or NG scan is specified.

Specify the local device address domain ID of the primary site in the DAD parameter.

file

Name of the configuration file where the error was detected

rec#

Number of the line in file where the error was detected

YKG290E MSG SC=44 RC=44 (result)

YKVGET program failure for: vn

An attempt to acquire the variable vn failed with the result value identified by result. This error can be caused by an invalid value being specified for the STEM parameter.

YKG295E MSG SC=44 RC=44 (file:rec#)

The element stack was overflowed.

The internal routine encountered a shortage of work space.

Contact customer support for assistance.

file

Name of the configuration file where the error was detected

rec#

Number of the line in file where the error was detected

YKG298E MSG TSO SC=44 RC=44 (detailed-info)

YKGETHDA encountered an unexpected error.

An unexpected error has occurred.

This error might have occurred with another error.

If another error message was output at the same time as this one, follow the instructions in that message to fix the corresponding problem.

If no other error message was output, collect the following materials and contact customer support:

  • The script from which this command was executed (not necessary if this command was executed from the ISPF panel).

  • The ISPF log (not necessary if this command was executed from a script).

  • The configuration files operated on from the script or ISPF panel (the copy group definition file, disk configuration definition file, command device definition file and route list definition file).

detailed-info

Information displayed to assist the customer support in resolving the problem.

YKH001I TSO

YKH2B completed. RC=return-code

The YKH2B command terminated.

return-code

Return code of the YKH2B command:

0: The command ended successfully. One or more copy group definition file was created.

4: One of the following occurred:

- The command ended successfully. No copy pairs were detected within the range of the specified device numbers.

- A copy group definition file was created, but volume information not defined in the disk configuration definition file for the site specified in the DAD parameter was detected among copy pairs within the range specified in the DEVN parameter.

- A copy group definition file was created, but a change was detected in the I/O configuration when the YKH2B command was executed without specifying the HS parameter or the YKH2B command was executed by specifying HS(CHECK).

- A copy group definition file was created, but a storage system that does not support 2DC configuration with HyperSwap and Universal Replicator was detected.

8: An I/O error occurred with a volume within the scan range. Copy group definition files were created for the volumes that were successfully detected.

44: The processing was canceled due to an error. The copy group definition file was not created.

48: The command ended due to an invalid parameter.

YKH002I TSO

No copy pair was discovered.

No copy pairs were detected within the specified range.

Check the operating range and status of the copy pair that you want to acquire, and execute the YKH2B command again. If the copy pair status is SIMPLEX, the YKH2B command will not detect the copy pair. In addition, if you execute the YKH2B command without specifying the HS parameter or execute the YKH2B by specifying HS(CHECK) while HyperSwap is disabled, copy pairs cannot be detected.

YKH100E TSO

Missing or invalid parameter: parameter-name

The parameter is not specified, or an invalid value is specified for the parameter.

Check the following, and then re-execute the command:

  • Make sure that the required parameter (parameter-name) was specified.

  • Make sure that the value specified for the required parameter (parameter-name) is valid.

YKH101E TSO

The specified PREFIX is being used by another program.

The specified prefix is being used by another program.

Check the value specified for the prefix.

YKH102E TSO

Error occurred during execution. Cmd=info

msg=message-text: message-value: message-severity

An error occurred during execution of the YKH2B command.

See the explanation corresponding to the message ID of the error message indicated by message-text and take appropriate action. Also see the additional information indicated by message-value and message-severity and take appropriate action. If the problem is not resolved, contact customer support.

info

Maintenance information

message-text

Error message

message-value

Additional information about the error message

If no additional information is available, a space is displayed.

message-severity

Additional information about the error message

If no additional information is available, a space is displayed.

The error messages message-text, message-value, and message-severity are displayed on the TSO/E terminal. Depending on the length of the error messages, they might extend over several lines.

YKH103E TSO

The parameters parameter-name1 and parameter-name2 cannot be concurrently specified.

You cannot specify the parameter-name1 parameter and the parameter-name2 parameter at the same time.

YKH200W TSO

No information was acquired for DEVN=device-number

No copy pair information was acquired from the volume with the device number device-number. There might not be a volume for the specified device number.

If a volume does exist for the specified device number, check the channel settings.

YKH201W TSO

No I/O paths are available for the specified devices. DEVN=device-number

No copy pair information was acquired from the volume with the device number device-number because no I/O paths are available, or because the active subchannel set ID is a value other than 0.

Verify the I/O path settings and the setting of the active subchannel set ID.

YKH202W TSO

Unable to resolve primary volume information. DEVN=​Devn,​SN=​SerialNum,​CU=​CU#,​CCA=​CCA#

A P-VOL not defined in the disk configuration definition file was included among the PPRC copy pairs detected by the YKH2B command.

Check whether this P-VOL is defined in the disk configuration definition file.

Devn

The device number of the detected undefined volume

SerialNum

The storage system serial number of the detected undefined volume

CU#

The control unit number of the detected undefined volume

CCA#

The command control address number of the detected undefined volume

YKH203W TSO

Unable to resolve secondary volume information. SN=SerialNum,CU=CU#,CCA=CCA#

An S-VOL not defined in the disk configuration definition file was included among the PPRC copy pairs detected by the YKH2B command.

Check whether the detected S-VOL is defined in the disk configuration definition file.

SerialNum

The storage system serial number of the detected undefined volume

CU#

The control unit number of the detected undefined volume

CCA#

The command control address number of the detected undefined volume

YKH204W TSO

A dynamic configuration change was detected. DEVN=device-number

A dynamic change was detected in an I/O configuration definition when the YKH2B command was executed either without the HS parameter or with HS(CHECK).

Check the status of the device targeted by the YKH2B command, correct any errors in the configuration or execution conditions (such as the parameter setting or the times at which the command has been executed), and then re-execute the command.

device-number

Device number being processed when a dynamic change was detected in an I/O configuration definition

YKJ000E TSO RC=48

Unable to execute without valid name parameter.

Nothing or an invalid value is assigned to the parameter identified by name.

name

Parameter name

YKJ001E TSO RC=48

name parameter is too long.

The parameter identified by name is too long.

name

Parameter name

YKJ002E TSO RC=48

The specified PREFIX is being used by another program.

The specified prefix is being used by another program.

Check the value specified for the prefix.

YKJ003E TSO RC=48

The parameters name1 and name2 cannot be concurrently specified.

You cannot specify the name1 parameter and the name2 parameter at the same time.

YKJ051E TSO RC=32

Error occurred during execution. Cmd= info

msg= message-text: message-value: message-severity

An error occurred during execution of the YKIMPORT command or YKEXPORT command.

See the error message message-text and resolve the problem. Also see the additional information indicated by message-value and message-severity and take appropriate action.

If the acquisition of information denoted by message-text, message-value, or message-severity fails, FATAL is displayed instead of the information that should be acquired. The reasons for FATAL to be displayed include an insufficient region size. Review the current region size, and then retry executing the command.

If the problem is not resolved, contact customer support for assistance.

info

Maintenance information

message-text

Error message

message-value

Additional information about the error message

If no additional information is available, a space is displayed.

message-severity

Additional information about the error message

If no additional information is available, a space is displayed.

The error messages message-text, message-value, and message-severity are displayed on the TSO/E terminal. Depending on the length of the error messages, they might extend over several lines.

YKJ099I TSO RC=0

cmd command completed. RC= return-code

The command identified by cmd has ended with a return code identified by return-code.

YKJ100E TSO RC=32

Error occurred during reading/writing configuration file: file

An error occurred while reading data from or writing data to the configuration file (file).

YKJ101I TSO RC=4

No copy pair is defined in specified Copy Group definition: file

No copy pair is defined for the specified copy group. No data was written in the CSV file.

file

Name of the specified copy group definition file

YKJ102E TSO RC=32

name is not specified in Copy Group definition specified by BASEGROUP.

The copy group definition file specified by the BASEGROUP parameter does not include the element identified by name.

Set the necessary elements in the copy group definition file that is to be used as the base, and then retry.

name

Name of an element in the copy group definition file

YKJ150E TSO RC=40

Error reported during file input/output. EXECIO RC= n: dd-name

Processing ended due to the EXECIO TSO/E REXX command failure (return code = n). For details, see the IBM manual TSO/E REXX User's Guide.

The probable causes are as follows:

  • No CSV file is assigned to the DD name required for the command.

  • The dataset format of the CSV file is not supported.

dd-name

DD name of the CSV file where the error was detected

YKJ151E TSO RC=40

File format is invalid: DSORG= XX. DSORG must be PS: dd-name

The dataset format of the CSV file identified by dd-name is invalid.

Delete the current CSV file and create a CSV file that is in the correct dataset format.

For details about the CSV file dataset format, see the Hitachi Business Continuity Manager Reference Guide.

XX

DSORG of the CSV file where the error was detected

dd-name

DD name of the CSV file where the error was detected

YKJ152E TSO RC=40

Failed to operate csv file: dd-name: dsstate

The CSV file operation will stop because an error occurred when using the CSV file.

Refer to the information output in the message to review the environment, and then update the CSV file again. For details about troubleshooting, see the accompanying message and the Hitachi Business Continuity Manager User Guide.

dd-name

DD name of the CSV file where the error was detected

dsstate

CSV file status

  • EXTENT= extent

    The number of extents of the dataset that is currently allocated

    extent indicates the number of extents that are allocated to the dataset indicated by dd-name.

  • CANNOT GET DSSTATE, reason code= nnnn

    The dataset information cannot be obtained, or the CSV file is not allocated.

    nnnn (decimal (base 10) number) indicates a reason code (maintenance information).

YKJ200E TSO RC=32

name is not specified in Pair information CSV file: dd-name: rec#

The item identified by name is not included in the pair information CSV file.

name

Name of the item in the pair information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ201E TSO RC=32

The value value of name in Pair information CSV file is invalid: dd-name: rec#

The value assigned to name in the pair information CSV file is in an invalid format.

value

Value assigned to the item identified by name

name

Name of the item in the pair information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ202I TSO RC=4

No copy pair is defined in specified Pair information CSV file.

No copy pair is defined in the pair information CSV file. No data was written in the copy group definition file.

YKJ203E TSO RC=32

The number of items specified for a line in Pair information CSV file is invalid: dd-name: rec#

The number of items specified on one line of the pair information CSV file is incorrect.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ204E TSO RC=32

Primary volume is not specified in Pair information CSV file: dd-name: rec#

No P-VOL is specified in the pair information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ205E TSO RC=32

Secondary volume is not specified in Pair information CSV file: dd-name: rec#

No S-VOL is specified in the pair information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ206E TSO RC=32

The specified volume does not exist in the disk configuration definition file: dd-name: rec#: device

The specified volume does not exist in the disk configuration definition file.

The subchannel set ID of the specified volume might not match the subchannel set ID in the base copy group definition file.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

device

One of the following is displayed. If both are specified, the device number is displayed.

  • Device number

  • Storage system serial number, control unit number, and command control address number

    The display format is storage-system-serial-number:CU-number:CCA-number.

YKJ207W TSO RC=8

Inconsistencies exist among the values used to specify the primary volume: dd-name: rec#

The P-VOL specified with the device number differs from the P-VOL specified with the storage system serial number, control unit number, and command control address number.

Although the copy group definition file was created, the settings therein might contain an error.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ208W TSO RC=8

Inconsistencies exist among the values used to specify the secondary volume: dd-name: rec#

The S-VOL specified with the device number differs from the S-VOL specified with the storage system serial number, control unit number, and command control address number.

Although the copy group definition file was created, the settings therein might contain an error.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ209E TSO RC=32

Sub C/T group ID cannot be specified for a copy-type Copy Group: dd-name: rec#

A sub consistency group ID is specified for a copy group of the copy type identified by copy-type. No sub consistency group ID can be specified if the copy type is ShadowImage, or TrueCopy.

copy-type

Copy type

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ210E TSO RC=32

The value specified for Number-of-Pairs exceeds the range in which volumes exist: Number-Of-Pairs: dd-name: rec#

No volume exists in the range of the Number-Of-Pairs repetitions.

Number-Of-Pairs

Number of pair repetitions

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ211E TSO RC=32

PVOL & SVOL of SI pair is in the different storage system: dd-name: rec#

A copy pair, which has a P-VOL storage system serial number and an S-VOL storage system serial number that do not match, was found in a copy group of copy type ShadowImage.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ212E TSO RC=32

A specific combination of a storage system serial number and a C/T group ID is used for multiple UR Copy Groups: dd-name: rec#

The combination of the copy groups is one of the following:

  • The serial numbers of the primary site storage systems are the same; the serial numbers of the secondary site storage systems are different; and copy pairs with the same consistency group ID exist.

  • The serial numbers of the primary site storage systems are different; the serial numbers of the secondary site storage systems are the same; and copy pairs with the same sub consistency group ID exist.

If the copy type is Universal Replicator, these combinations are not supported.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ213E TSO RC=32

Secondary volume is already specified in another copy pair as a secondary device: dd-name: rec#

The volume specified as the S-VOL is also specified as the S-VOL for other copy pairs. The same volume cannot be specified as the S-VOL for multiple copy pairs.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ214W TSO RC=8

A copy pair capacity check could not be performed because the capacity of a volume could not be acquired.

A copy pair capacity check could not be performed because the capacity of a volume could not be acquired. A capacity check cannot be performed in the following case:

  • When a volume capacity has not been acquired during a local scan, remote scan, or NG scan.

A copy group definition file was created, but the settings might contain incorrect information.

YKJ215E TSO RC=32

The capacities of the copy pair volumes are different: dd-name: rec#

The capacities of the copy pair volumes are different. A copy pair whose P-VOL and S-VOL capacities are different cannot be defined.

To create a copy pair whose P-VOL and S-VOL capacities are different for migration, specify NOCHECK for the CAPACITY parameter, and execute the YKIMPORT command. For details, see the Hitachi Business Continuity Manager Reference Guide.

dd-name

The DD name of the CSV file where the error was detected

rec#

Number of the line in the file indicated by dd-name where the error was detected

YKJ216E TSO RC=32

The device numbers for the copy pair do not match: dd-name: rec#

The copy pair cannot be defined because the S-VOL cannot be assigned the same device number as that of the P-VOL.

Check whether the disk configuration definition file for the secondary site includes the same device number as that of the P-VOL.

dd-name

The DD name of the CSV file where the error was detected

rec#

Number of the line in the file indicated by dd-name where the error was detected

YKJ217E TSO RC=32

The specified volume does not have a device number: dd-name: rec#

The specified volume does not have a device number.

For the P-VOL, specify a volume that has a device number.

dd-name

The DD name of the CSV file where the error was detected

rec#

Number of the line in the file indicated by dd-name where the error was detected

YKJ250E TSO RC=32

name is not specified in EXCTG information CSV file: dd-name: rec#

No value is assigned to the item identified by name in the EXCTG information CSV file.

name

Name of the item in the EXCTG information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ251E TSO RC=32

The value value of name in EXCTG information CSV file is invalid: dd-name: rec#

The format of the value assigned to name in the EXCTG information CSV file is invalid.

value

Value assigned to the item identified by name

name

Name of the item in the EXCTG information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ252E TSO RC=32

The number of items specified for a line in EXCTG information CSV file is invalid: dd-name: rec#

The number of items specified on one line of the EXCTG information CSV file is incorrect.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ253E TSO RC=32

Multiple EXCTG IDs are specified in EXCTG information CSV file: dd-name

Multiple EXCTG IDs are specified in the EXCTG information CSV file.

dd-name

DD name of the CSV file where the error was detected

YKJ254E TSO RC=32

The specified supervisor DKC or arbitration command device is invalid: dd-name: rec#

The supervisor disk controller or arbitration command device number specification is incorrect.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

If the EXCTG information CSV file does not include a line that specifies the supervisor disk controller, nothing is displayed for rec#.

YKJ255E TSO RC=32

A Copy Group that does not have any corresponding entry in EXCTG information CSV file is found: dd-name

The EXCTG information CSV file includes no entry (line) corresponding to the entry (line) specified in the pair information CSV file.

dd-name

DD name of the CSV file where the error was detected

YKJ256E TSO RC=32

This entry does not have any corresponding Copy Group in Pair information CSV file: dd-name: rec#

The pair information CSV file includes no entry (line) corresponding to the entry (line) specified in the EXCTG information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ257E TSO RC=32

Multiple entries that specify the same Copy Group are defined in EXCTG information CSV file: dd-name: rec#

The EXCTG information CSV file contains multiple entries (lines) that specify the same copy group.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ258E TSO RC=32

The EXCTG information is inconsistent: dd-name: rec#

The following entries specified as EXCTG information are contradictory:

  • EXCTG ID

  • Supervisor disk controller

  • Arbitration command device number

It is likely that different combinations of copy directions (forward direction only, reverse direction only, or forward and reverse directions) exist in the EXCTG information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Number of the line in the file identified by dd-name where the error was detected

YKJ270E TSO RC=32

name is not specified in CTG information CSV file: dd-name: rec#

No value is assigned to name in the CTG information CSV file.

name

Name of an item in the CTG information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Line number in the file dd-name where the error was detected

YKJ271E TSO RC=32

The value value of name in CTG information CSV file is invalid: dd-name: rec#

The value assigned to name in the CTG information CSV file is invalid.

value

Value assigned to name

name

Name of an item in the CTG information CSV file

dd-name

DD name of the CSV file where the error was detected

rec#

Line number in the file dd-name where the error was detected

YKJ272E TSO RC=32

The number of items specified for a line in CTG information CSV file is invalid: dd-name: rec#

An invalid number of items was specified on one line in the CTG information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Line number in the file dd-name where the error was detected

YKJ273E TSO RC=32

This entry does not have any corresponding Copy Group in Pair information CSV file: dd-name: rec#

The pair information CSV file includes no entries (lines) corresponding to the entries (lines) specified in the CTG information CSV file.

dd-name

DD name of the CSV file where the error was detected

rec#

Line number in the file dd-name where the error was detected

YKJ274E TSO RC=32

Multiple entries that specify the same Copy Group are defined in CTG information CSV file: dd-name: rec#

The CTG information CSV file contains multiple entries (lines) in which the same copy group is specified.

dd-name

DD name of the CSV file where the error was detected

rec#

Line number in the file dd-name where the error was detected

YKK001I PRT

command-name completed. RC=return-code, V/R=​version-number,​execution-date

The command-name command terminated.

command-name

KTINSCHK, RSINSCHK, or YKINSCHK

return-code

Return code of the command

version-number

Version number of the program that executed the command

execution-date

Time at which the command was executed

The time is indicated in the format YYYY/MM/DD HH:MM:SS

YKK101E TSO RC=32

Failed to get security setting information,​service=​service-name,​code=​code1,​code2.

Security setting information could not be acquired.

service-name

Name of the OS service that encountered an error

code1

Return code of the OS service that encountered an error

code2

Reason code of the OS service that encountered an error

If no reason code is returned for an OS service, code2 is 0.

YKK102E TSO RC=32

Failed to get user SVC routine information,​service=​service-name,​code=​code1,​code2.

User SVC information could not be acquired.

service-name

Name of the OS service that encountered an error

code1

Return code of the OS service that encountered an error

code2

Reason code of the OS service that encountered an error

If no reason code is returned for an OS service, code2 is 0.

YKK103E TSO RC=32

Acquisition of host ID settings failed,​service=​service-name,​code=​code1,​code2.

Host ID setting information could not be acquired.

service-name

Name of the OS service that encountered an error

code1

Return code of the OS service that encountered an error

code2

Reason code of the OS service that encountered an error

If no reason code is returned for an OS service, code2 is 0.

YKK104E TSO RC=48

Supplied parameters invalid.

Invalid parameters are specified.

YKK105E TSO RC=48

USERID() value invalid.

The value assigned to the USERID parameter is invalid.

YKK106E TSO RC=24

This command is not authorized to execute the request of USERID() parameter.

The user does not have permission to execute the RSINSCHK command with the USERID parameter specified.

Check that the user who executed the RSINSCHK command was given the READ permission for the STGADMIN.YKA.ERM.INSCHK profile.

YKK107E TSO RC=48

OPTION() value invalid.

The value assigned to the OPTION parameter is invalid.

YKK110E TSO RC=24

The command is not APF-authorized.

The program ended because the RSINSCHK command was started without being registered as APF-authorized.

Check the following:

  • The LINKLIB load library is registered as APF-authorized.

  • The RSINSCHK command has been added to the AUTHCMD section in the IKJTSOxx parmlib member.

Table. List of messages starting with YK (YKL0x)

Message ID

Message text

Explanation and recommended actions

YKL000T TSO SC=48

Supplied parameters invalid.

Invalid parameters have been specified.

YKL001E TSO RC=48

Unable to execute without valid MSG() parameter.

Specify a valid MSG parameter.

YKL002E TSO RC=48

MSG(stem) does not include trailing "." character.

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKL003E TSO RC=52

Unable to update MSG(stem) in Caller's environment. YKVSET result = result

An attempt to assign a value to a Message structure variable failed. The resulting value is displayed in result. This error can be caused by an invalid value being specified for the MSG parameter.

stem

Stem name assigned to the MSG parameter

YKL004E MSG SC=48 RC=48

Unable to execute without valid STEM() parameter.

Specify a valid STEM parameter.

YKL005E MSG SC=48 RC=48

STEM(stem) does not include trailing "." character.

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKL006E MSG SC=48 RC=48

Unable to execute without valid PREFIX parameter.

Specify a valid PREFIX parameter.

YKL007E MSG SC=48 RC=48

Unable to execute without valid GROUP parameter.

Specify a valid GROUP parameter.

YKL050W MSG SC=4 RC=4 (file:rec#)

Unrecognized element encountered: name

Revise the specification on line number rec# in file. If the error still exists, contact customer support for assistance.

name

XML element name

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL051E MSG SC=36 RC=36 (file:rec#)

End of file encountered in comment.

Check that the XML comments are balanced. Be careful to ensure that any XML comments will not be nested. If the error still exists, contact customer support for assistance.

file

Name of the configuration file where the error was detected

rec#

Number of the line in file where the error was detected

YKL053W MSG SC=4 RC=4 (file:rec#)

Unrecognized Version attribute value: value

The system does not recognize the version attribute value of the XML element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL054E MSG SC=36 RC=4 (file:rec#)

Unexpected termination of element: name

The XML element name that exists on the line with the line number identified by rec# in the file identified by file has not been correctly created.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL074E MSG SC=36 RC=36 (file:rec#)

Invalid "&" character discovered in quoted string. string

An invalid entity reference was found on the line with the line number identified by rec# in the file identified by file.

Use only defined entity references as specified in Extensible Markup Language (XML) 1.0 at http://www.w3.org.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL075W MSG SC=4 RC=4 (file:rec#)

Unrecognized Encoding attribute value: value

The system does not recognize the encoding attribute value of the XML element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL076W MSG SC=4 RC=4 (file:rec#)

Unrecognized attribute: name = value

The system does not recognize the XML attribute that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

name

XML attribute name

value

XML attribute value

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL077W MSG SC=4 RC=4 (file:rec#)

APIInfo Level=level invalid. Supported level is v.r.m.

The system does not recognize the Level attribute level of the APIInfo element that exists on the line with the line number identified by rec# in the file identified by file.

Check the indicated line, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

v.r.m

API level

For details about this value, see the information about the XML document type definitions in the Hitachi Business Continuity Manager Reference Guide.

YKL079E MSG SC=44 RC=44 (result)

YKVSET program failure for: name = value

An attempt to assign the value value to the variable name failed with the result value identified by result. This error can be caused by an invalid value being specified for the STEM parameter.

YKL080E MSG SC=36 RC=36 (file:rec#)

More than two DiskDevice Elements in CopyPair.

Only two copy pair elements are allowed: the first element for the P-VOL and the second element for the S-VOL.

Check the line with the line number identified by rec# in the file identified by file, and then identify the cause of the problem by referring to information contained in the XML document type definitions, in the Hitachi Business Continuity Manager Reference Guide.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL081W MSG SC=16 RC=16 (pair-index)

Unable to resolve primary device address.

The YKLOAD program failed to resolve the unit number (device address) of the P-VOL in the specified copy pair. For configuration definition, this process uses the Host Discovered Array object in the primary device address domain. For other purposes, the current local device address domain is used. The situation represented by this message is not always fatal. Some CLI commands, such as YKSUSPND, can be successfully executed by using only the S-VOL unit address.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKL082W MSG SC=8 RC=8 (pair-index)

Unable to resolve secondary device address.

The YKLOAD program failed to resolve the unit number (device address) of the S-VOL in the specified copy pair. For configuration definition, this process uses the Host Discovered Array object in the secondary device address domain. For other purposes, the current local device address domain is used. The situation represented by this message is not always fatal. Many CLI commands can be successfully executed by using only the P-VOL unit address.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKL083W MSG SC=12 RC=12 (pair-index)

Unable to resolve volume serial number.

The YKLOAD program failed to resolve the volume serial number of the P-VOL in the specified copy pair. For configuration definition, this process uses the Host Discovered Array object in the primary device address domain. For other purposes, the current local device address domain is used. The situation represented by this message is not always fatal. At present, the volume serial number is used only for display and warning.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKL084W MSG SC=16 RC=16

Unable to read disk configuration definition file. (SN=sn,DAD=dadid)

The disk configuration definition file of the storage system whose SerialNum and DADID attribute values match the disk controller elements in the route list definition file could not be read.

sn
The storage system serial number corresponding to the disk configuration definition file that could not be read
dadid
The device address domain ID corresponding to the disk configuration definition file that could not be read

YKL085E MSG SC=40 RC=40 (file:rec#)

Unable to read configuration file.

The configuration file could not be read, because the record length is too long.

file

Name of the configuration file where the error was detected

rec#

Number of the line in file where the error was detected

YKL087E MSG SC=40 RC=40 (file)

The license information dataset could not be read.

An attempt to read the license information dataset has failed.

Check that the dataset name of the license key dataset is correct, and that the license key dataset was created correctly. If necessary, transfer the license key file again and recreate the license key dataset.

YKL088E MSG SC=40 RC=40 (file)

File Open error: dsstate.

An attempt to open the configuration file identified by file failed.

dsstate

Status of the configuration file

  • No permission to read the data set: The user does not have READ permission for the file.
  • IRXINOUT rc=rc: The REXX I/O routine terminated with return code rc.
file

Name of the configuration file in which the error was detected

YKL089E MSG SC=40 RC=40 (file)

File Close error: dsstate.

An attempt to close the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKL090E MSG SC=40 RC=40 (file)

File Allocation Failed: dsstate.

An attempt to allocate the configuration file identified by file failed.

Verify that the configuration file identified by file is correctly created.

dsstate

Status of the configuration file

  • LOCATE rc=rc: The LOCATE macro terminated with return code rc. If rc is 8, the file might not exist or might not have been cataloged.
  • IKJDAIR rc=rc, ec=ec: The dynamic allocation routine IKJDAIR terminated with return code rc and error code ec.
file

Name of the configuration file in which the error was detected

YKL091E MSG SC=40 RC=40 (file)

File Deallocation Failed: dsstate.

An attempt to deallocate the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKL092E MSG SC=40 RC=40 (file)

File Read error: dsstate.

An attempt to read the configuration file identified by file failed.

dsstate

Status of the configuration file

file

Name of the configuration file in which the error was detected

YKL099I MSG TSO

process-name command return code=max-value, reason code=reason-code.

If process-name is YKLOAD:

The YKLOAD command has finished. This message is always displayed.

If process-name is YKGETRUT:

The route list definition file and the command device definition file have been read. This message is output when an invalid route list definition file or invalid command device definition file is read in ISPF.

reason-code

Reason code for the returned max-value

max-value

Maximum value among the output return codes

Table. List of messages starting with YK (YKL2x - YKL4x)

Message ID

Message text

Explanation and recommended actions

YKL201E MSG SC=48 RC=48

Unable to execute without valid name parameter.

Nothing or an invalid value is assigned to the parameter identified by name.

YKL202E TSO RC=48

"SYSAUTH". cannot be specified in MSG() parameter.

SYSAUTH. cannot be specified in the MSG parameter. Specify a different name.

YKL203E MSG SC=48 RC=48

"SYSAUTH." cannot be specified in STEM() parameter.

SYSAUTH. cannot be specified in the STEM parameter. Specify a different name.

YKL204E TSO RC=48

name parameter is too long.

The parameter identified by name is too long.

YKL205E MSG SC=48 RC=48

name parameter is too long.

The parameter identified by name is too long.

YKL206E MSG SC=48 RC=48

Route parameter is allowed only on 1st call of YKLOAD

The ROUTE parameter is allowed only on the first call of the YKLOAD command.

YKL241W MSG SC=4 RC=4 (file:rec#)

The attribute attname is already defined.

The XML attribute identified by attname has already been defined.

Revise the specification of attname on line number rec# in file.

attname

XML attribute name

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL250E MSG SC=36 RC=36 (file:rec#)

The value value of the attribute name is an invalid format.

The value value of the XML attribute name is in an invalid format.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL251E MSG SC=36 RC=36 (file:rec#)

name attribute missing.

The required XML attribute name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL252E MSG SC=36 RC=36 (file:rec#)

The attribute statements are invalid.

The XML attribute description is invalid.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL253E MSG SC=36 RC=36 (file:rec#)

This kind of elements element can't be defined more than once.

The XML element element is defined more than once.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL254E MSG SC=36 RC=36 (file:rec#)

The value value of attribute name is not match with filename.

The value value of the XML attribute name does not match the name in the file name.

Revise the specification on line number rec# in file, or correct the file name.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL255E MSG SC=36 RC=36 (file:rec#)

The element name-1, for which the value value was specified for the attribute name-2, was not found.

The XML element name-1 with the value value specified for the XML attribute name-2 was not found.

Revise the specification on line number rec# in file.

file

Name of the configuration file in which the error was detected

rec#

Number of the line in file where the error was detected

YKL257E MSG SC=36 RC=36 (file:rec#)

The attribute name-1 is not a content of the element name-2.

The XML attribute name-1, which cannot be specified for the XML element name-2, was found.

Revise the specification on line number rec# in file.

file

Name of the configuration file in which the error was detected

rec#

Number of the line where the error was detected

YKL262E MSG SC=36 RC=36

name is not specified or invalid.

The system symbol identified by name has not been defined or has been assigned an invalid value.

If name is YKCMDIF:

The host ID that identifies the host on which Business Continuity Manager is running is invalid or missing. Define YKCMDIF correctly.

For details about the host ID definition (YKCMDIF), see the Hitachi Business Continuity Manager Installation Guide.

YKL271E MSG SC=36 RC=36 (file:rec#)

The element name is required, but no element was found.

The required XML element name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL273E MSG SC=36 RC=36 (file:rec#)

The element statements are invalid.

The XML element description is invalid.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL274E MSG SC=36 RC=36 (file:rec#)

ETag name is mismatch. /correct-ETag-name is expected, but /incorrect-ETag-name is specified.

The specified ETag name /incorrect-ETag-name is not the expected ETag name /correct-ETag-name.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL275W MSG SC=4 RC=4 (file:rec#)

Extra ETag is specified: ETag-name

An extra ETag-name is specified.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL276E MSG SC=36 RC=36 (file:rec#)

The element name1 is not a content of the element name2.

The XML element identified by name2 contained the XML element name1 that cannot be specified.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL277E MSG SC=36 RC=36 (file:rec#)

name element missing.

The XML element name is missing.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL280E MSG SC=36 RC=36 (file)

No command devices were found.

No command devices were found.

Correct the route definition in the route list definition file (file).

YKL281E MSG SC=36 RC=36 (file:rec#)

No command devices are defined for routes that issue remote commands or for route labels.

No command device was found that is defined in the route for remote command issuance or with the specified route label.

Correct the route definition in the route list definition file (file).

rec#

Number of the line in file where the error was detected

YKL282E MSG SC=36 RC=36 (file)

The route label specified for the ROUTE parameter has not been defined.

The route label specified for the ROUTE parameter is not defined.

Correct the route definition in the route list definition file (file).

YKL283E MSG SC=36 RC=36 (file)

A route label is not specified for the ROUTE parameter, even though a route label is defined for all the command devices.

An attempt was made to load command device lines for which no route label is specified because no route label is specified for the ROUTE parameter. However, route labels are defined for all the command devices in the route list definition file (file).

Set an appropriate route label for the ROUTE parameter of the YKLOAD command, or use the Edit Attribute panel to delete the route labels of command devices in the route list definition file (file).

YKL284E MSG SC=36 RC=36 (file:rec#)

PVOL & SVOL of SI pair is in the different storage system.

In a file for a copy group of the ShadowImage copy type, a copy pair has been discovered for which the storage system serial numbers of the P-VOL and S-VOL do not match.

Revise the specification on line number rec# in file.

file

Name of the configuration file where the error was detected

rec#

Number of the line where the error was detected

YKL290E MSG SC=44 RC=44 (result)

YKVGET program failure for: vn

An attempt to acquire the variable vn failed with the result value identified by result. This error can be caused by an invalid value being specified for the STEM parameter.

YKL291E MSG SC=36 RC=36

function-name is not licensed for use on this system.

The license key for the function identified by function-name has not been installed, has expired, or is not correctly recognized.

Check whether the license key is available for this version.

If function-name is This product:

Business Continuity Manager commands cannot be used because the Business Continuity Manager license key has not been installed.

If function-name is UR 4x4 Extended CTG:

The function for preserving consistency on an EXCTG basis cannot be used because the license key required for a 4x4 configuration has not been installed.

YKL292E MSG CON SC=36 RC=36

The expiration date for your license key(function).

The license (function) has expired.

To continue using this product, you need a permanent license.

If function is Basic:

A permanent license for Business Continuity Manager Basic is required.

If function is UR 4x4 Extended CTG:

A permanent license for Business Continuity Manager UR 4x4 Extended CTG is required.

YKL293W MSG CON SC=0 RC=0

Your function license will expire in n day(s).

The license (function) will expire in n days.

To continue using this product after the expiry date, you need a permanent license.

If function is Basic:

A permanent license for Business Continuity Manager Basic is required.

If function is UR 4x4 Extended CTG:

A permanent license for Business Continuity Manager UR 4x4 Extended CTG is required.

YKL295E MSG SC=44 RC=44 (file:rec#)

The element stack was overflowed.

The internal routine encountered a shortage of work space.

Contact customer support for assistance.

file

Name of the configuration file where the error was detected

rec#

Number of the line in file where the error was detected

YKL298E MSG TSO SC=44 RC=44 (detailed-info)

CLI-name encountered an unexpected error.

An unexpected error has occurred. This error might have occurred with another error.

If another error message was output at the same time as this one, follow the instructions in that message to fix the corresponding problem.

If no other error message was output, collect the following materials and contact customer support:

  • The script from which this command was executed (not necessary if this command was executed from the ISPF panel).

  • The ISPF log (not necessary if this command was executed from a script).

  • The definition files operated on from the script or ISPF panel (the copy group definition file, disk configuration definition file, command device definition file and route list definition file).

CLI-name

The name of the executed CLI command

detailed-info

Detailed information displayed to assist the customer support in resolving the problem

YKL419E MSG SC=48 RC=48

The values of attribute1 and attribute2 conflict.

The values attribute1 and attribute2 conflict.

Make sure that both of these values are valid, and then retry the operation.

attribute1

Attribute name 1 included in the copy group definition

attribute2

Attribute name 2 included in the copy group definition

Table. List of messages starting with YK (YKM0x)

Message ID

Message text

Explanation and recommended actions

YKM000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKM099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKM001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKM001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKM002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKM002E MSG SC=48 RC=48

ORDER(stem) does not include trailing "."

The last character of the ORDER parameter is not a period.

stem

Stem name assigned to the ORDER parameter

YKM002E MSG SC=48 RC=48

ORDER() value invalid

The value assigned to the ORDER parameter is invalid.

YKM002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKM002E TSO

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKM008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKM010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKM011E ISPF

This device number msgdevn has not been discovered on msgdad.

The device number indicated by msgdevn has not been scanned in the device address domain indicated by msgdad.

msgdevn

Device number

msgdad

Device address domain

YKM012E ISPF

The End Devn value must not be lower than the Start Devn

The End device number is lower than the Start device number.

YKM014E ISPF

This Copy Group ID is already defined. Choose a different ID.

The copy group ID is already defined. Please use another ID.

YKM015I LOG

RC:nn CMD:command

The command terminated with the return code nnnn after issuing the command identified by command.

nn

Return code of this command

YKM016W LOG

SEV:nn TEXT:message-text VALUE:message-value

The command output the nn as Severity, message-text as message ID/message text, and message-value as additional information, and then terminated.

nn

Value set for Severity in the Message structure

message-text

Value set for Text in the Message structure

message-value

Value set for Value in the Message structure

YKM017I LOG

message-text

The console message message-text was output when issuing the command.

YKM020E ISPF

Please supply the required information.

Enter the required information.

YKM021E ISPF

Check either Device num or Volser

Select either Device Num or Volser.

YKM022E ISPF

The End Volser value must not be lower than the Start Volser

The End Volser value is lower than the Start Volser value.

YKM023E ISPF

Invalid value

The value is invalid.

YKM024E ISPF

Choose any one

Please choose one.

YKM025E ISPF

C/T ID cannot be added to a CopyGroup Container without C/T ID.

You cannot add a copy group to a copy group container if no consistency group ID is specified for the copy group.

YKM026E ISPF

The secondary device sdevn is already paired to primary device pdevn.

The secondary device indicated by sdevn is already defined as a copy pair in the primary device indicated by pdevn.

sdevn

Secondary device number

pdevn

Primary device number

YKM027E ISPF

The primary device pdevn and secondary device sdevn are on different storage system.

The primary device pdevn and the secondary device sdevn are on different storage system.

pdevn

Primary device number

sdevn

Secondary device number

YKM030E ISPF

File not found.

The file was not found.

YKM031E ISPF

Refresh SMS key is not available in case of Copy Group Creation.

The Refresh SMS key is not available while a new copy group is being created.

YKM032E ISPF

Invalid operation.

The operation is invalid.

YKM033E ISPF

Can not edit.

This cannot be edited.

YKM034E ISPF

Press F10 key and select C/T ID.

Press the F10 key, and then select a consistency group ID.

YKM035E ISPF

inputfld is not specified or invalid.

No value is specified in inputfld, or the specified value is invalid.

inputfld

The attribute name or the input field name

YKM036E ISPF

Specified APID is defined to another DADID.

The APID you specified is already defined in another device address domain ID.

YKM037E ISPF

Changing a local Device Address Domain ID is not allowed.

Changing a local device address domain ID is not allowed.

YKM038E ISPF

Specified DEVN is not found.

The device number you specified was not found.

YKM039E ISPF

Specified device is not command device because APID is not available.

The device you specified is not a command device because the APID cannot be used.

YKM040E ISPF

A Consistency Group ID (C/T ID,sub C/T ID) is required for Universal Replicator Copy Group definition.

For the Universal Replicator copy group definition, you need to specify a consistency group ID and a sub consistency group ID.

YKM041E ISPF

A sub Consistency Group ID cannot be specified for SI/TC Copy Group definition.

For the ShadowImage/TrueCopy copy group definition, you cannot specify a sub consistency group ID.

YKM042E ISPF

This Consistency Group ID (C/T ID,sub C/T ID) is already defined. Choose a different ID.

This consistency group ID is already defined. Please choose a different ID.

YKM043E ISPF

A Mirror ID is required for Universal Replicator Copy Group definition.

For the Universal Replicator copy group definition, you need to specify a mirror ID.

YKM044E ISPF

This Path Set ID is already defined.

This path set ID is already defined.

YKM045E ISPF

Physical path (priport secport) is already defined in this logical path.

The physical path is already defined in the logical path.

priport

The primary port you specified

secport

The secondary port you specified

YKM046E ISPF

The end CU/CCA value must not be lower than the start CU/CCA.

The end control unit/command control address value is lower than the start control unit/command control address value.

YKM047E ISPF

Processing to add, insert, or edit a storage system was denied because the storage system has already been discovered by the specified DADID.

A storage system cannot be added to, inserted into, or edited in a route because the storage system has already been scanned via the specified device address domain ID.

Correct the specified device address domain ID and serial number of the storage system.

YKM048E ISPF

You cannot perform a device scan because a remote DADID or Non Gen'ed DADID was specified as the local DADID in the Set Defaults panel.

Devices cannot be scanned because the remote device address domain ID or Non Gen'ed device address domain ID has been specified as the local device address domain ID in the Set Defaults panel.

YKM049E ISPF

A Path ID is required for Universal Replicator Copy Group definitions.

To define a Universal Replicator copy group, a path group ID is required.

YKM050E MSG SC=36 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKM056E MSG SC=36 RC=48

NOCOPY option invalid for ShadowImage Copy Group

The YKMAKE command with the NOCOPY parameter specified was executed on a ShadowImage copy group. This parameter is invalid on ShadowImage copy groups.

Re-execute the YKMAKE command without specifying the NOCOPY parameter.

YKM099I TSO

YKMAKE command return code=nnnn, reason code=rrrr

The YKMAKE command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKM1x - YKM5x)

Message ID

Message text

Explanation and recommended actions

YKM103E MSG SC=48

The parameter combination is invalid

The parameter combination is invalid.

YKM500E ISPF

You cannot perform a remote or an NG scan if the specified DADID matches a local DADID or if the Preset RouteListID, which is in the Set Defaults panel, is not enabled.

You cannot perform a remote scan or an NG scan for the following reasons:

  • The device address domain ID is the same as a local device address domain ID.

  • The device address domain ID is the same as the local device address domain ID for a remote site (the first device address domain ID of a route starting from a remote site). Make sure that no command device definition file exists that has the same device address domain ID.

  • Preset RouteListID in the Set Defaults panel is disabled.

YKM501E ISPF

You cannot edit the device number for a volume that was not found by remote scan or NG scan.

The device number cannot be edited because the volume was not found by a remote scan or an NG scan.

YKM502E ISPF

You cannot exit until all discovered devices are assigned dummy devn.

The exit operation cannot be performed until a device number is assigned to all discovered devices.

YKM504E ISPF

The number of connections of inter-DKC paths of the same PathID exceeds the maximum number of connections that is allowed within the same storage system.

The number of connections of inter-disk controller paths of the same PathID exceeded the maximum that is allowed within the same storage system.

YKM505E ISPF

This inter-DKC path is already defined in another logical path.

This inter-disk controller path is already defined in another logical path.

YKM506E ISPF

You cannot define inter-DKC path with this interface version.

In this interface version, the user cannot define inter-disk controller paths.

YKM508E ISPF

This inter-CU path is already defined in another logical path.

This inter-control unit path is already defined in another logical path.

YKM509E ISPF

The number of physical paths that are defined in the same logical path exceeds the limit.

The number of physical paths exceeded the maximum that is allowed within the same logical path.

YKM510E ISPF

This Model is not supported for this Path Type.

This model does not support this path type.

YKM511E ISPF

The value of CU exceeds the number of CUs that is allowed in this Model.

The number of control units exceeds the maximum number for this model.

YKM514E ISPF

CCA could not be assigned because either the path is already defined in another logical path, or the list of CCA could not be retrieved.

A command control address could not be assigned because the path is already defined in another logical path, or because a list of command control addresses could not be obtained.

YKM515E ISPF

You cannot specify the same serial number to the primary side and the secondary side of the same logical path.

The same serial number cannot be specified for both the primary and secondary sides of the same logical path.

YKM516E ISPF

Port errport is already defined as portdir port.

The port errport is already defined as portdir.

errport

The port that you specified

portdir

The port that is already defined

YKM517E ISPF

The value of PathID exceeds the value that is allowed in this Model.

The value of PathID exceeds the maximum for this model.

YKM518E ISPF

Port errport exceeds the limit that is allowed in this composition.

The number of ports exceeds the maximum number for this composition.

errport

The port that you specified

YKM519E ISPF

Different PathIDs cannot be specified for the primary side and secondary side of an inter-DKC path.

The path ID that is different for the primary site and for the secondary site cannot be specified to the inter-disk controller logical path.

YKM520E ISPF

These device number remdevn or storage system S/N remsn are not discovered on Device Address Domain remdad.

The device number or storage system serial number has not yet been scanned in the device address domain ID.

remdevn

The device number you specified

remsn

The storage system serial number you specified

remdad

The device address domain ID you specified

YKM521E ISPF

You cannot exit this panel until you define a command device.

The exit operation cannot be performed until you define a command device.

YKM522E ISPF

Please supply the required information.

Enter the necessary information.

YKM523E ISPF

You cannot enter values to both License Key Dataset Name field and Key Code field at the same time.

The License Key Dataset Name and Key Code fields cannot be specified simultaneously.

YKM524E ISPF

Please enter alphanumeric characters to Key Code field.

The value specified in the Key Code field contains characters that are not numbers or letters.

YKM525E ISPF

Invalid Key Code is entered. Please re-enter the Key Code.

The key code is incorrect. Please re-enter the key code.

YKM526E ISPF

Invalid dataset name is specified.

An incorrect dataset name is specified.

YKM527E ISPF zOSMF RC=16

You cannot specify the license information dataset.

The license information dataset cannot be specified.

YKM528E ISPF

Enter the value that you wish to find with the LOCATE command on a sorted field "field-name".

Enter the value that you want to find in the sorted field field-name by using the LOCATE command.

field-name

field name

YKM529E ISPF

You cannot specified except '00' as PathID with this interface version.

Only 00 can be specified for a path ID in this interface version.

YKM530E ISPF

The copy operation cannot be performed, because the model of the primary or secondary storage system is not supported.

The same number as the port number used for the physical path in the selected direction cannot be set for the physical path in the opposite direction, because the model of the primary or secondary storage system is not supported. The following are the storage system models for which you can set the same port number:

  • VSP 5000 series

YKM531E ISPF

Copying cannot be performed, because the number of physical paths that would be defined in the logical path exceeds the maximum value.

The maximum number of physical paths that can be defined in a logical path has been exceeded. The same number as the port number used for the physical path in the selected direction cannot be set for the physical path in the opposite direction.

YKM540E ISPF

You do not have permission to perform this operation. You must have the UPDATE permission for the STGADMIN.YKA.BCM.LICENSE profile.

You do not have permission to perform this operation. The program will stop. Make sure that you have been granted the UPDATE permission or a higher permission for the STGADMIN.YKA.BCM.LICENSE profile.

YKM541E ISPF

An error occurred during an alloc, open, read, or write operation for the license information data set.

The license information dataset could not be updated, because an error occurred in processing to allocate, open, read, or write to the license information dataset. Possible causes are as follows.

  • You do not have the UPDATE permission or a higher permission for the license information dataset.
  • Another job is allocating the license information dataset.
  • The DD name YKDDLCNS is used.

YKM542E ISPF

The non-temporary license key record for the specified storage system was not found in the license information data set.

No license key records for the storage system corresponding to the specified serial number and model name was not found in the license information dataset. Make sure that the specified serial number and model name are correct. Check whether a license key corresponding to the specified serial number and model name appears in the Manage Licenses panel.

If the storage system corresponding to the specified serial number and model name only has a temporary license key record (a license key record for which Temp. appears in the Type field), this message will still be output, because temporary license key records cannot be deleted.

YKM543E ISPF

The license key record to be deleted could not be identified. Specify a storage model name.

The license key record to be deleted could not be identified, because the license information dataset includes license key records that correspond to the storage system of the specified serial number but that have different model names. To identify the license key record to be deleted, specify a storage system model name.

YKM544E ISPF

Specify the correct storage system model name.

Enter the correct storage system model name.

Table. List of messages starting with YK (YKM7x)

Message ID

Message text

Explanation and recommended actions

YKM700E ISPF

Enter one of the listed values.

Please enter one of the listed values.

YKM701E ISPF

Enter required field at the cursor position.

Enter the required information at the cursor position.

YKM702E ISPF

The length of the data must be = crtlen.

The length of the input data must be crtlen.

crtlen

Necessary data length

YKM703E ISPF

Enter hexadecimal characters (0-9, A-F, a-f).

Enter hexadecimal characters (0-9, A-F, a-f).

YKM704E ISPF

Enter alphanumeric characters (0-9, A-Z, a-z).

Enter alphanumeric characters (0-9, A-Z, a-z).

YKM705E ISPF

Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z), the first alphabetic.

Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character.

YKM706E ISPF

The length of the "field-name" field data must be no more than loclen.

The length of the input entered into the field-name field must be no more than loclen.

YKM707E ISPF

Enter the number (hex. characters: 0-9, A-F, a-f) to search for.

Enter the hexadecimal characters (0-9, A-F, a-f) that you want to search for.

YKM708E ISPF

Enter the number (numerical characters: 0-9) to search for.

Enter the numeric values (0-9) that you want to search for.

YKM709E ISPF

Execute the sort command before executing the locate command.

Execute the SORT command before executing the LOCATE command.

YKM710E ISPF

Enter one of the following characters(P, S, N/A) to search for.

Enter the character you want to search for (P, S, or N/A).

YKM720E ISPF

Required parameter is not specified.

Enter the required parameters.

YKM721E ISPF

Invalid field name is specified.

Enter the name of the field that specifies the condition.

YKM722E ISPF

Invalid pattern is specified.

Specify correct values for the pattern parameter.

Make sure that none of the following conditions exist:

  • A value greater than value 1 was specified for value 2, as the range specification condition.

  • NULL was specified for value 1, as the range specification condition.

  • A value containing an asterisk (*) was specified for value 1 or value 2, as the range specification condition.

  • The specified value contained two or more asterisks.

  • An asterisk (*) was specified in a location other than before or after the value.

  • The storage system serial number specified for the DEVICE field was not a five-digit number.

YKM723E ISPF

Invalid action name is specified.

Enter the valid action name.

YKM724E ISPF

The length of the "field-name" field data must be no more than value-length.

The length of the input entered into the field-name field must be equal to or less than value-length.

YKM725E ISPF

Enter the number (hex. characters: 0-9, A-F, a-f).

Enter the hexadecimal characters (0-9, A-F, a-f).

YKM726E ISPF

Enter the number (numerical characters: 0-9).

Enter a numeric value (0-9).

YKM727E ISPF

Range specification is not supported for the field.

A range cannot be specified for the field.

YKM728E ISPF

The specified pattern produced no matching lines.

A line that matches the specified pattern was not found.

YKM731E ISPF

ISPF service error occurred. info

An error occurred in the ISPF service.

info

Maintenance information

YKM733E ISPF

Copy Group ID is not selected.

No copy group ID is selected.

YKM734E ISPF

No volume is selected.

No volume is selected.

YKM735E ISPF

The import destination is different from the original DADID or subchannel set.

The import destination is different from the original DADID or subchannel set.

YKM736E ISPF

Processing could not continue because the Copy Group definition file is invalid.

Processing could not continue because the copy group definition file is invalid.

YKM750E ISPF

Serial number must be a 5-digit combination of alphanumeric characters.

Serial numbers must be a five-digit combination of alphanumeric characters (0-9, A-Z, a-z).

YKM751E ISPF

DADID must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of DADID must be 1-28.

The device address domain ID must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character (A-Z, a-z). The length of the device address domain ID must be from 1 to 28 characters.

YKM752E ISPF

DEVN must be 4 hexadecimal characters (0-9, A-F, a-f).

The device number must be a four-digit hexadecimal number (0-9, A-F, a-f).

YKM753E ISPF

APID must be 4 hexadecimal characters (0-9, A-F, a-f).

The APID must be a four-digit hexadecimal number (0-9, A-F, a-f).

YKM754E ISPF

Route List ID must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Route List ID must be 1-8.

The route list ID must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character (A-Z, a-z). The length of the route list ID must be from 1 to 8 characters.

YKM755E ISPF

Configuration File Prefix must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Configuration File Prefix must be 1-16.

The configuration file prefix must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character (A-Z, a-z). The length of the configuration file prefix must be from 1 to 16 characters.

YKM756E ISPF

Copy Group ID must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Copy Group ID must be 1-40.

The copy group ID must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character (A-Z, a-z). The length of the copy group ID must be from 1 to 40 characters.

YKM757E ISPF

The 4-digit year (YYYY) or 2-digit month (MM) or 2-digit day (DD) was not numeric. Valid year values are 1970-2042, valid month values are 01-12, and valid day values are 01-31.

The value for the year (YYYY), month (MM), or day (DD) was not numeric. Specify a value for the year, month, and day in the range 1970 to 2042, 01 to 12, and 01 to 31, respectively.

YKM758E ISPF

The hour, minute, or second value is not numeric. Valid values are 00-23 for hour, 00-59 for minute, and 00-59 for second.

The value for the hour, minute, or second was not numeric. Specify a value for the hour, minute, and second in the range 00 to 23, 00 to 59, and 00 to 59, respectively.

YKM759E ISPF

Enter numeric characters (0-9).

Please enter a numeric value (0-9).

YKM760E ISPF

Preset Mode cannot be used when C/T ID is not specified.

You cannot set the Preset Mode without specifying a consistency group ID.

YKM761E ISPF

Check Device Num, Volser, or Non Gen'ed.

Check the value specified in Device Num, Volser, or Non Gen'ed.

YKM762E ISPF

You cannot perform a remote or an NG scan because the specified DADID matches a local DADID.

You cannot perform a remote scan or an NG scan, because the specified device address domain ID is the same as the local device address domain ID.

YKM763E ISPF

You cannot perform an NG scan because no local scan has been performed for the specified storage system.

You cannot perform an NG scan, because a local scan has not been performed for the specified storage system.

YKM764E ISPF

Select one of the displayed lines.

Select one of the displayed lines.

YKM765I ISPF

A description for the specified error code was not found.

A description for the specified error code was not found.

For details about error codes, see Details of error codes. If the error code is not listed in the manual, contact customer support.

YKM766E ISPF

Specified Prefix is being used by another program.

The specified prefix is being used by another program.

Check the value specified for the prefix.

YKM767E ISPF

This command is invalid for TrueCopy Copy Groups linkaged with HyperSwap.

The command cannot be executed for TrueCopy copy groups with the HyperSwap attribute.

Execute the PPRC copy pair operation from CSM.

YKM768E ISPF

HS cannot be used when C/T ID is specified.

If a consistency group ID is specified, you cannot specify HS for the linkage option.

YKM769E ISPF

Route Label must be an asterisk (*), or a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Route Label must be 1-8.

The route label must be an asterisk (*), or a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must begin with an alphabetic character (A-Z, a-z). The length of the route label must be from 1 to 8 characters.

YKM770E ISPF

Enter unique value in a storage system.

Enter a value that is unique within the storage system.

YKM771I ISPF

Panel could not scroll because it shows beginning of data.

The panel cannot be scrolled because the start of the data is already being displayed.

YKM772I ISPF

Panel could not scroll because it shows end of data.

The panel cannot be scrolled because the end of the data is already being displayed.

YKM773E ISPF

DADID must be shortened so that dataset name of disk configuration file is no more than 44 characters.

The dataset name of the disk configuration file exceeded the 44-character limit. Shorten the device address domain ID.

YKM774E ISPF

Specified storage system is defined in the same route.

The specified storage system is already defined in the route. Select a different storage system.

YKM775E ISPF

Panel could not proceed the insert action because number of the route entry has reached maximum.

The storage system cannot be added because the number of storage systems defined in the route is already at the maximum.

YKM776E ISPF

Route Label must be a combination of one or more qualifiers. Each qualifier must be 1-8 alphanumeric characters (0-9, A-Z, a-z) with the first character being an alphabetic character (A-Z, a-z). The length of Route Label must be 1-8.

The route label must be a combination of one or more qualifiers. Each qualifier must be from 1 to 8 alphanumeric characters (0-9, A-Z, a-z), and must start with an alphabetic character (A-Z, a-z). The length of the route label must be from 1 to 8 characters.

YKM779E ISPF LOG

A duplicate serial number exists. (SN=SN, model=model1, other model=model2, pos=pos)

Processing was canceled because two or more storage systems have the same serial number. The model names for only two storage systems are displayed even if more than two storage systems have the same serial number.

SN

Duplicated serial number

model1

Model of one of the storage systems whose serial number is duplicated

model2

Model of another one of the storage systems whose serial number is duplicated

pos

Maintenance information

YKM780E ISPF

The volume serial and device type fields cannot be concurrently specified.

You cannot specify the volume serial number field and the device type field at the same time.

YKM781E ISPF

A storage class can contain only alphanumeric characters (0-9, A-Z, a-z) and the following characters: $ # @

Use only alphanumeric characters (0-9, A-Z, a-z) and symbols ($, #, @) for storage classes.

YKM782E ISPF

A volume serial number can contain only alphanumeric characters (0-9, A-Z, a-z) and the following characters: $ # @ -

Use only alphanumeric characters (0-9, A-Z, a-z) and symbols ($, #, @, -) for volume serial numbers.

YKM783E ISPF

A device type can contain only alphanumeric characters (0-9, A-Z, a-z) and the following characters: $ # @ - /. However, you can use a forward slash (/) only as the first character.

Use only alphanumeric characters (0-9, A-Z, a-z) and symbols ($, #, @, -, /) for device types. Note that you can use a forward slash (/) only as the first character.

YKM784E ISPF

You cannot perform a local scan because the specified DADID dose not match the Local Device Address Domain ID which is in the Set Defaults panel.

You cannot perform a local scan, because the specified device address domain ID does not match the local device address domain ID specified in the Set Defaults panel.

YKM785E ISPF

You cannot specify a DADID that is specified in a route list starting from a remote site.

You cannot specify the first device address domain ID of a route starting from a remote site.

YKM786E ISPF

If the remote DKC control function is not used, no commands can be issued via command devices.

If the Remote DKC Control function is not used, you cannot issue commands via command devices.

YKM787E ISPF

Select a device.

Automatic pairing could not be performed, because no P-VOL was selected.

Select a P-VOL.

YKM788W ISPF

device-count devices were selected, but pair-count pairs were defined.

device-count volumes were selected, but only pair-count copy pairs were defined.

Some copy pairs could not be defined, because S-VOLs of the same device numbers as the P-VOLs could not be found.

device-count

Number of selected volumes

pair-count

Number of defined copy pairs

YKM789E ISPF

Multiple fields cannot be specified.

You cannot select multiple methods for specifying a volume.

Select one of the following: the device number, the volume serial number, or the device address.

YKM791E ISPF

DEVN(device-number) has already been assigned.

A volume whose device number is device-number is already defined.

YKM794I ISPF

The secondary SSID is valid.

The secondary SSID is valid.

YKM795W ISPF

The secondary SSID was corrected because the secondary CU did not match the secondary SSID.

The secondary SSID was corrected because the secondary control unit number and the secondary SSID are not consistent. Check the serial number, secondary control unit number, and secondary SSID of the secondary storage system.

YKM796E ISPF

Verification of the secondary SSID was skipped.

The processing was skipped because verification of the SSID could not be performed. Make sure the verification target is an inter-control unit logical path.

YKM797E ISPF

Verification of the secondary SSID failed because an error occurred during acquisition of information about the secondary volume.

An error occurred during verification of the SSID. Check the following:

  • Whether the implemented volume exists in the secondary control unit.

  • Whether the Remote DKC Control function can be used for the secondary storage system, or whether a local scan has already been performed for one or more volumes in the secondary storage system.

Table. List of messages starting with YK (YKM90x)

Message ID

Message text

Explanation and recommended actions

YKM900I ISPF

Start YKSTART command.

Start the YKSTART command.

YKM901E TSO

ISPF service is not available.

The ISPF service is not available.

Execute the YKSTART command in an ISPF environment.

After that, you can execute whichever Business Continuity Manager commands you need to.

YKM902E TSO

Load module is not found.

The Business Continuity Manager load module was not found. The Business Continuity Manager dataset might not be concatenated to the LNKLST.

Revise the settings for the LNKLST, and then execute the YKSTART command.

After that, you can execute whichever Business Continuity Manager commands you need to.

YKM903E TSO

SELECT service terminated abnormally. RC=nn

The SELECT service terminated abnormally with the return code nn.

If this message is displayed immediately after executing the YKSTART command, the Business Continuity Manager dataset might not be concatenated to the panel library (DD name: ISPPLIB), the table library (DD name: ISPTLIB), or the REXX exec library (DD name: SYSEXEC).

If DBCS (Double-Byte Character Set) is enabled for the environment, concatenate the Business Continuity Manager dataset to the alternate panel library (DD name: ISPPALT). For details, see the Hitachi Business Continuity Manager Installation Guide.

nn

Return code of the service

YKM904E TSO

Message library was not found.

The message library was not found.

The Business Continuity Manager dataset might not be concatenated to the message library (DD name: ISPMLIB).

If DBCS (Double-Byte Character Set) is enabled for the environment, concatenate the Business Continuity Manager dataset to the alternate message library (DD name: ISPMALT). For details, see the Hitachi Business Continuity Manager Installation Guide.

YKM905E TSO

A GETMAIN error occurred.

A GETMAIN error occurred. The program will stop running.

Contact customer support for assistance.

YKM906E TSO

A FREEMAIN error occurred.

A FREEMAIN error occurred. However, the program will continue to run.

Contact customer support for assistance.

Table. List of messages starting with YK (YKN0x)

Message ID

Message text

Explanation and recommended actions

YKN000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKN099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKN001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKN001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKN002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKN002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKN010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKN050E MSG SC=48 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKN099I TSO

YKRUN command return code=nnnn, reason code=rrrr

The YKRUN command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKP0x)

Message ID

Message text

Explanation and recommended actions

YKP000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKP099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKP001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKP001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKP002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKP002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKP002E MSG SC=48 RC=48

This command is only valid for UR Copy Groups

The YKSTATS command was executed on a copy group other than a Universal Replicator. This command works only on Universal Replicator copy groups.

Check that the command can be executed on this copy group, and then re-execute the command.

YKP010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable indicated by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code for REXX access

YKP065E MSG SC=36 RC=36

The storage system serial number pairs with more than 4 storage systems.

The storage system identified by serial-number is paired with more than four storage systems within the consistency group.

Correct the copy pair configuration within the consistency group.

serial-number

Storage system serial number (12 digits)

YKP099I TSO

YKSTATS command return code=nnnn, reason code=rrrr

The YKSTATS command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKQ0x)

Message ID

Message text

Explanation and recommended actions

YKQ000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKQ099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKQ001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKQ001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKQ002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKQ002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKQ002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKQ003E MSG SC=48

Parameters combination is invalid

The parameter combination is invalid.

YKQ008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKQ010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable indicated by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code for REXX access

YKQ018E MSG SC=16 RC=16 (pair-index)

SI PAIR deficiency. DEVN device#(SN,CU#,CCA#)

In a ShadowImage copy group, the volume in the target copy pair has already been paired with three volumes other than the pairing volume specified in the copy group definition.

Review the applicable copy pair definition in the copy group definition.

device#

Device number

If the device cannot be identified, **** is displayed.

SN

Storage system serial number

If the device cannot be identified, ************ is displayed.

CU#

Control unit number

If the device cannot be identified, ** is displayed.

CCA#

Command control address number

If the device cannot be identified, ** is displayed.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKQ019W MSG SC=12 RC=0 (pair-index)

Primary volume serial changed. DEVN device#(SN,CU#,CCA#)

Although the P-VOL is online, the current volume serial number does not match the volume serial number defined for the copy group. Processing will continue.

Check that the copy group indicates the correct volumes and is not being used for other purposes.

device#

Device number

If the device cannot be identified, **** is displayed.

SN

Storage system serial number

If the device cannot be identified, ************ is displayed.

CU#

Control unit number

If the device cannot be identified, ** is displayed.

CCA#

Command control address number

If the device cannot be identified, ** is displayed.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKQ021E MSG SC=12 RC=20 (pair-index)

SIB Primary is simplex, secondary not. DEVN device#(SN,CU#,CCA#)

Check that the S-VOL status is SIMPLEX.

device#

Device number

If the device cannot be identified, **** is displayed.

SN

Storage system serial number

If the device cannot be identified, ************ is displayed.

CU#

Control unit number

If the device cannot be identified, ** is displayed.

CCA#

Command control address number

If the device cannot be identified, ** is displayed.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKQ026W MSG SC=8 RC=8 (pair-index)

Primary volume is offline. DEVN device#(SN,CU#,CCA#)

The volume serial number of the P-VOL cannot be obtained because the P-VOL is offline.

Check that the copy group indicates the correct volumes and is not being used for other purposes, make the P-VOL online, and then re-execute the YKQUERY command.

device#

Device number

If the device cannot be identified, **** is displayed.

SN

Storage system serial number

If the device cannot be identified, ************ is displayed.

CU#

Control unit number

If the device cannot be identified, ** is displayed.

CCA#

Command control address number

If the device cannot be identified, ** is displayed.

pair-index

See the pair index description in the explanation of the YKE003E message.

YKQ099I TSO

YKQUERY command return code=nnnn, reason code=rrrr

The YKQUERY command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKR0x - YKR10x)

Message ID

Message text

Explanation and recommended actions

YKR000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKR099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKR001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKR001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKR002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKR002E MSG SC=48 RC=48

ORDER(stem) does not include trailing "."

The last character of the ORDER parameter is not a period.

stem

Stem name assigned to the ORDER parameter

YKR002E MSG SC=48 RC=48

ORDER() value invalid

The value assigned to the ORDER parameter is invalid.

YKR002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKR002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKR008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKR010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKR050E MSG SC=36 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKR099I TSO

YKRESYNC command return code=nnnn, reason code=rrrr

The YKRESYNC command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

YKR103E MSG SC=48

Parameters combination is invalid

The parameter combination is invalid.

Table. List of messages starting with YK (YKS0x)

Message ID

Message text

Explanation and recommended actions

YKS001E TSO RC=48

Unable to execute without valid MSG() parameter.

Specify a valid MSG parameter.

YKS002E TSO RC=48

MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKS003E TSO RC=52

Invoke YKSTORE REXX Script via YKSTORE Assembler subroutine.

The YKSTORE REXX program can only be invoked via the YKSTORE assembler REXX subroutine. This message indicates the most likely cause of the error indicated in the previous YKS003E message.

YKS003E TSO RC=52

Unable to update MSG(stem) in Caller's environment. YKVSET result = result

An attempt to assign a value to a variable of the Message structure failed with the result value indicated by result. This implies that the YKSTORE REXX subroutine has not properly been invoked or that Business Continuity Manager has not properly been installed.

stem

Stem name assigned to the MSG parameter

YKS004E MSG SC=48 RC=48

Unable to execute without valid STEM() parameter.

Specify a valid STEM parameter.

YKS005E MSG SC=48 RC=48

STEM(stem) does not include trailing "." character.

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKS006E MSG SC=48 RC=48

Unable to execute without valid PREFIX parameter.

Specify a valid PREFIX parameter.

YKS079E MSG SC=44 RC=44 (result)

YKVSET program failure for: variable =value.

An attempt to assign the value value to the variable variable failed with the result value identified by result. This error can be caused by the YKSTORE REXX subroutine's compiled REXX module being directly executed.

Use the YKSTORE REXX subroutine, instead of directly executing the compiled REXX module.

YKS085E MSG SC=44 RC=44

Error reported during file output. EXECIO RC =n

Because the EXECIO TSO/E REXX command failed (return code = n), the YKSTORE command is unavailable for creating or updating the configuration file. For details, see the IBM manual TSO/E REXX User's Guide.

YKS086E MSG SC=44 RC=44 (file)

File status is:dsstate

The input configuration file identified by file is unavailable.

dsstate

Status of the input configuration file

The following messages are output if the attribute of the input configuration file is abnormal:

  • DSORG = XX. DSORG must be YY

    The file is unavailable because the DSORG attribute value is abnormal. Therefore, delete the current configuration file, and then recreate a new configuration file that has correct file attributes.

  • RECFM = XX. RECFM must be YY

    The file is unavailable because the RECFM attribute value is abnormal. Therefore, delete the current configuration file, and then recreate a new configuration file that has correct file attributes.

  • LRECL = XX. LRECL must be YY

    The file is unavailable because the LRECL attribute value is abnormal. Therefore, delete the current configuration file, and then recreate a new configuration file that has correct file attributes.

  • BLKSIZE = XX. BLKSIZE must be YY

    The file is unavailable because the BLKSIZE attribute value is abnormal. Therefore, delete the current configuration file, and then recreate a new configuration file that has correct file attributes.

  • ALLOCATION FAILED

    Creation of a configuration file failed. For details about the cause of the failure and action to be taken, see the message that is output when the failure occurred and the Hitachi Business Continuity Manager User Guide. For details about the required disk capacity for a configuration file, see the Hitachi Business Continuity Manager Reference Guide.

  • UNAVAILABLE DATASET

    The configuration file is being used. Check the usage of the configuration file.

XX displays the file attribute value that caused the error and YY displays the correct file attribute value.

file

Name of the configuration file where the error was detected

YKS087E TSO SC=44

Start of TSO/E command error message

The start of the TSO/E command error message. The TSO/E command error message is displayed until the YKS088E message is output.

YKS088E TSO SC=44

End of TSO/E command error message

The end of the TSO/E command error message.

YKS089E TSO SC=44

No TSO/E command error message was found.

The TSO/E command error message could not be found.

YKS098E MSG SC=36 RC=36

Specified STEM() is not CopyGroup object.

The prefix of the REXX variable name specified in the STEM parameter does not comply with the copy group structure described in the Hitachi Business Continuity Manager Reference Guide.

YKS099I MSG TSO SC=max-severity RC=max-value

YKSTORE Processing Complete.

YKSTORE command processing has completed.

This message is always displayed.

max-severity

Maximum value among the output severity codes

max-value

Maximum value among the output return codes

Table. List of messages starting with YK (YKS2x)

Message ID

Message text

Explanation and recommended actions

YKS203E TSO RC=52

Invoke YKSTORE REXX Script via YKSTORE Assembler subroutine.

The YKSTORE REXX program can only be invoked via the YKSTORE assembler REXX subroutine. This message indicates the most likely cause of the error indicated in the previous YKS203E message.

YKS203E TSO RC=52

The MSG(stem) value cannot be acquired in the caller's environment. (YKVGET result = result)

An attempt to acquire the variable value of the Message structure failed with the result value identified by result. This implies that the YKSTORE REXX subroutine has not properly been invoked or that Business Continuity Manager has not properly been installed.

stem

Stem name assigned to the MSG parameter

YKS250E MSG SC=36 RC=36

The value value of the variable name is an invalid format.

The value value of the variable identified by name is invalid.

YKS260E MSG SC=44 RC=44

Too long record:record.

An attempt to output record to a dataset failed because record was too long.

Correct the variable setting so that the length of record becomes 256 characters or shorter.

YKS270E MSG SC=44 RC=44

Failed to operation configuration file. (name =dataset-name, dsstate)

Creation of the configuration file is stopped because an error occurred during the creation of the configuration file. Refer to the information output in the message to review the environment, and then create the configuration file again. For details about what action to take, see the message that was output and the Hitachi Business Continuity Manager User Guide.

operation

The operation performed for the configuration file

  • CREATE

    An error occurred during the creation of the configuration file.

  • UPDATE

    An error occurred during the update of the existing configuration file.

  • ALLOCATION

    Creation of a configuration file failed. For details about the cause of the failure and action to be taken, see the message that is output when the failure occurred and the Hitachi Business Continuity Manager User Guide. For details about the required disk capacity for a configuration file, see the Hitachi Business Continuity Manager Reference Guide.

  • CHECK

    An error occurred during the check of the existing configuration file. Check the status of the configuration file. The error might have occurred because the configuration file is in an unusable state, or the dataset format is invalid. If the dataset format is invalid, check the message that was output simultaneously.

  • EXECIO

    An error occurred while writing to the configuration file. For the cause of the error, check the message that was output simultaneously.

  • RENAME

    An error occurred when the name of the configuration file was changed to dataset-name.

    Check whether the dataset name displayed in dataset-name actually exists in the system, and then execute the command again.

    The name of a temporary file might be displayed for dataset-name.

dataset-name

Name of the configuration file to be created

dsstate

Status of the configuration file

If RENAME is displayed for operation, the status of the configuration file after its name has been changed is displayed.

  • EXTENT=extent

    The number of extents of the dataset that is currently allocated

    extent indicates the number of extents that are allocated to the dataset indicated by dataset-name.

  • DSORG=VSAM

    The dataset format is VSAM. A dataset with the format VSAM cannot be used as a configuration file. Change the dataset format of the configuration file into PS.

  • RECFM=XX

    RECFM value of the dataset

  • LRECL=XX

    LRECL value of the dataset

  • BLKSIZE=XX

    BLKSIZE value of the dataset

  • CANNOT GET DSSTATE, reason code=nnnn

    The dataset information cannot be obtained, or the configuration file is not assigned.

    nnnn (decimal (base 10) number) indicates a reason code (maintenance information).

This message indicates that, if dataset-name contains NEW or OLD, an error occurred while processing the temporary file used for creating or updating the configuration file.

YKS285E MSG SC=48 RC=48

file-name is too long for a filename.

The file name identified by file-name is too long. The file name must consist of 44 or fewer characters.

YKS290E MSG SC=44 RC=44 (result)

YKVGET program failure for:vn

An attempt to acquire the variable vn failed with the result value identified by result. This error can be caused by the YKSTORE REXX subroutine's compiled REXX module being directly executed.

Use the YKSTORE REXX subroutine, instead of directly executing the compiled REXX module.

YKS298E MSG SC=44 RC=44 (detailed-info)

YKSTORE encountered an unexpected error.

An unexpected error has occurred. This error might have occurred with another error.

If another error message was output at the same time as this one, follow the instructions in that message to fix the corresponding problem.

If no other error message was output, collect the following materials and contact customer support:

  • The script from which this command was executed (not necessary if this command was executed from the ISPF panel).

  • The ISPF log (not necessary if this command was executed from a script).

  • The configuration files operated on from the script or ISPF panel (the copy group definition file, disk configuration definition file, command device definition file and route list definition file).

detailed-info

Detailed information displayed to assist the customer support in resolving the problem

Table. List of messages starting with YK (YKT0x)

Message ID

Message text

Explanation and recommended actions

YKT001E CON

Can't find SVCTABLE

The "SVCTABLE" search in the NUCLKUP macro failed. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT002E CON

Can't find IGCERROR

The "IGCERROR" search in the NUCLKUP macro failed. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT003E CON

No SVC #'s available

No SVC number available. The program abnormally terminates with user completion code 996.

YKT004E CON

Couldn't add SVC entry

SVC number addition failed in the SVCUPDTE macro. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT005E CON

Couldn't create name/token

Name/Token registration failed. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT006W CON RC=16

Couldn't delete name/token

Name/Token deletion failed.

Contact customer support for assistance.

YKT007W CON RC=16

Couldn't delete SVC entry

SVC number deletion failed in the SVCUPDTE macro.

Contact customer support for assistance.

YKT008E CON RC=20

System task started from TSO.

A user SVC registration command was executed in the TSO/E environment.

Execute user SVC registration command by using the START command, or as a batch job.

The user SVC registration command is KTALCSVC, RSALCSVC, or YKALCSVC.

YKT009E CON

Couldn't delete name/token.

Name/Token deletion failed. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT012E CON RC=16

Name/token error

An error occurred in the Name/Token service.

Contact customer support for assistance.

YKT021E CON RC=20

Invalid parameter

A value specified in the PARM parameter is invalid.

Check the specification of the PARM parameter.

YKT022E CON RC=4

An SVC routine is already installed with a different SVC #

The user SVC is already registered with a different SVC number.

Delete the user SVC by using the user SVC registration command, and then re-execute the command. To update the user SVC by using the same SVC number, re-execute the user SVC registration command without specifying the PARM parameter.

The user SVC registration command is KTALCSVC, RSALCSVC, or YKALCSVC.

YKT023E CON RC=16

Couldn't delete SVC routine

The user SVC deletion failed.

Contact customer support for assistance.

YKT024E CON

Couldn't copy load module

Copying of the load module failed. The program abnormally terminates with user completion code 996.

Contact customer support for assistance.

YKT025E CON RC=4

SVC routine is already deleted

The user SVC is not registered or is deleted.

YKT026E CON

SVC # is already used

The specified SVC number is already used. The program abnormally terminates with user completion code 996.

Specify an unassigned number in the PARM parameter of the user SVC registration command, or re-execute the command without specifying the PARM parameter.

The user SVC registration command is KTALCSVC, RSALCSVC, or YKALCSVC.

YKT027I CON RC=0

An SVC routine of the same or a newer version is already installed

A user SVC of the same version or a newer version is already registered.

YKT032E CON RC=20

The task is not APF-authorized.

The dataset name of the Business Continuity Manager load library was not registered in SYS1.PARMLIB. Alternately, the execution of the command failed because authorized/unauthorized datasets co-existed while concatenating DD statements in the load library, and they were handled as unauthorized datasets.

YKT097I CON RC=0

SVC routine is updated

The user SVC was successfully updated.

YKT098I CON RC=0

SVC routine is deleted

The user SVC deletion succeeded.

YKT099I CON RC=0

SVC routine is inserted

The user SVC registration succeeded.

Table. List of messages starting with YK (YKT2x)

Message ID

Message text

Explanation and recommended actions

YKT210E CON RC=8

System task started without START from TSO.

The command was invoked from the TSO/E environment. The program stops processing.

Invoke the command using the START command, or as a batch job.

YKT211E CON RC=12

Failed to allocate space in CSA

A GETMAIN error occurred in CSA. The program stops processing.

Contact customer support for assistance.

YKT212E CON RC=12

Couldn't register Name/Token

An error occurred during Name/Token registration. The program stops processing.

Contact customer support for assistance.

YKT213E CON RC=4

Couldn't take Name/Token

An error occurred during acquisition of Name/Token. The program stops processing.

Contact customer support for assistance.

YKT219E CON RC=16

Processing ended abnormally

Processing terminated abnormally before completion. The program stops processing.

Contact customer support for assistance.

YKT220E CON RC=8

Unknown keyword is specified

The specified keyword is unknown. The program stops processing.

Specify a valid keyword and then re-execute the command.

YKT221E CON RC=4

Specified HOST ID is invalid

The value assigned to the YKCMDIF parameter is invalid. The program ignores the specification and continues processing.

In HOST ID, you can either omit specification (Delete) or specify a hexadecimal value (two characters) between 00 and 1F. Specify a correct value and retry the process.

YKT222E CON RC=4

Specified YKLCNSE is invalid

The value assigned to the YKLCNSE parameter is invalid. The program ignores the specification and continues processing.

You can specify a character string containing up to eight characters. Specify a correct value and retry the process.

YKT223E CON RC=4

Specified LOGPUT is invalid

The value assigned to the LOGPUT parameter is invalid. The program ignores the specification and continues processing.

Valid values are either LOGR or SAM. Specify a valid value and retry the process.

YKT226E CON RC=4

The specified SYSLOG value is invalid.

The value specified for the SYSLOG parameter is invalid. The program ignores the specification and continues processing.

Valid values are either YES or NO. Specify a valid value and retry the process.

YKT230E CON RC=4

The specified YKLCNS2 value is invalid.

The value specified for the YKLCNS2 parameter is invalid. The program will ignore the specification and continue processing.

A maximum of 8 characters can be specified. Specify a correct value, and then retry the operation.

YKT232E CON RC=12

The task is not APF-authorized.

The dataset name of the Business Continuity Manager load library is not registered in SYS1.PARMLIB. Alternately, the execution of the command has failed because authorized/unauthorized datasets co-existed while concatenating DD statements in the load library and they were handled as unauthorized datasets.

YKT299I CON SC=0

command command return code=nnnn.

The command identified by command terminated with the return code nnnn.

Table. List of messages starting with YK (YKT4x)

Message ID

Message text

Explanation and recommended actions

YKT400I CON

BC Manager environment variables (version)

This message displays the Business Continuity Manager environment variables.

version

Version of Business Continuity Manager

YKT401I CON

variable : value

This message displays the Business Continuity Manager environment variables.

variable

Environment variables for Business Continuity Manager

  • Host ID: The host ID

  • License info DSN prefix: Prefix of the license information dataset

  • BCM log output method: Output method of the BCM log

  • CLI log output settings: Output settings for the CLI command-execution logs

value

Value set for each of the Business Continuity Manager environment variables

YKT402I CON

varname = value1 (symbol = value2)

This message displays the details of the Business Continuity Manager environment variables.

varname

Name of the Business Continuity Manager environment variable that is set by using the YKSETENV command

value1

Value of the Business Continuity Manager environment variable that is set by using the YKSETENV command

If no value has been set for the Business Continuity Manager environment variable by using the YKSETENV command, N/A is displayed.

symbol

Name of the system symbol

value2

Value set for the symbol system symbol

If no value is set for the system symbol, N/A is displayed.

YKT403I CON

Hitachi Business Continuity Manager

This message displays the program product name.

Table. List of messages starting with YK (YKU0x)

Message ID

Message text

Explanation and recommended actions

YKU000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKU099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKU001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKU001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKU002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKU002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKU002E MSG SC=48

GENID() value invalid

The value assigned to the GENID parameter is invalid.

YKU002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKU002E MSG SC=48

TIMEOUT() value invalid

The value assigned to the TIMEOUT parameter is invalid.

YKU003E MSG SC=48 RC=48

ATTIME Specification attime is invalid.

The time value assigned to the ATTIME parameter is invalid.

For the correct format, see the description of the YKSUSPND command in the Hitachi Business Continuity Manager Reference Guide.

attime

Time value assigned to the ATTIME parameter

YKU003E MSG SC=48 RC=48

SVOL(PROTECT|PERMIT) option required

Either PROTECT or PERMIT must be specified for the SVOL parameter.

YKU004E MSG SC=48 RC=48

ATTIME Specification is before current time.

The time assigned to the ATTIME parameter is earlier than the present time.

YKU005E MSG SC=48 RC=48

ATTIME Specification is more than 45.5 days into the future.

The time assigned to the ATTIME parameter is more than 65,535 minutes (45.5 days) past the present time.

YKU008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKU008E MSG SC=48

GENID() not valid hex

The value specified in the GENID parameter is not in hexadecimal format.

YKU009E MSG SC=48

Specify ATTIME() and DEVN() parm exclusively

You cannot specify the ATTIME parameter and the DEVN parameter at the same time.

YKU009E MSG SC=48

Specify ATTIME() and VOLUNIT parm exclusively

You cannot specify the ATTIME parameter and the VOLUNIT parameter at the same time.

YKU010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKU050E MSG SC=36 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKU053E MSG SC=36 RC=48

CANCEL(UR) parameter is only valid for SI Copy Groups with C/T ID.

The YKSUSPND command with the CANCEL(UR) parameter specified was executed for a copy group other than a ShadowImage copy group with a consistency group ID specified. The CANCEL(UR) parameter is valid only for ShadowImage copy groups with a consistency group ID specified.

YKU054E MSG SC=36 RC=48

ATTIME parameter invalid for TrueCopy Copy Group

The YKSUSPND command with the ATTIME parameter specified was executed on a TrueCopy copy group. This parameter is invalid on TrueCopy copy groups.

Re-execute the YKSUSPND command without specifying the ATTIME parameter.

YKU055E MSG SC=48 RC=48

Specify PURGE and DEVN parameter exclusively for UR Copy Group

The PURGE and DEVN parameters cannot be specified simultaneously for a Universal Replicator copy group.

YKU055E MSG SC=48 RC=48

Specify PURGE and VOLUNIT parameter exclusively for UR Copy Group

The PURGE and VOLUNIT parameters cannot be specified simultaneously for a Universal Replicator copy group.

YKU056E MSG SC=48 RC=48

DRAIN parameter cannot be specified for UR Copy Group

The DRAIN parameter cannot be specified for a Universal Replicator copy group.

YKU057E MSG SC=36 RC=48

ATTIME and CANCEL parameters are invalid for UR Copy Group

The YKSUSPND command was executed on a Universal Replicator copy group with the ATTIME parameter or CANCEL parameter specified. These parameters are invalid on Universal Replicator copy groups.

Re-execute the YKSUSPND command without specifying the ATTIME or CANCEL parameter.

YKU099I TSO

YKSUSPND command return code=nnnn, reason code=rrrr

The YKSUSPND command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKV0x)

Message ID

Message text

Explanation and recommended actions

YKV000T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKV099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKV001E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKV001E MSG SC=48 RC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKV002E MSG SC=48 RC=48

Copy Group STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKV002E MSG SC=48

DEVN() value invalid

The value assigned to the DEVN parameter is invalid.

YKV002E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKV008E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKV010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKV050E MSG SC=36 RC=48 (attribute-value)

Invalid Copy Group attribute name

The specified copy group attribute value is invalid for this command.

Correct the value and then re-execute the command.

name

REXX variable name

attribute-value

REXX variable value

YKV099I TSO

YKRECVER command return code=nnnn, reason code=rrrr

The YKRECVER command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKW0x)

Message ID

Message text

Explanation and recommended actions

YKW001W TSO

Timeout limit has expired without group copy-group reaching state state.

The specified copy group copy-group did not reach the requested status state within the specified time limit.

YKW002E TSO

Primary Device(s) OFFLINE. Unable to receive IEA494I messages.

Because the specified copy group contains a copy pair with a P-VOL that is offline, the IEA494I message is not issued.

Make all P-VOLs within the specified copy group online, and then re-execute the command.

YKW003E TSO

Unexpected transition of group copy-group pair index device xxxx to state state.

One or more copy pairs identified by index within the specified copy group copy group entered a status identified by state that does not lead to the requested GOTO status. It is probable that this status transition was triggered manually.

Conduct an investigation using the ISPF panel interface's monitor function.

YKW006E TSO

YKLOAD error return code = nnnn

The YKWATCH command uses the YKLOAD command to obtain the copy group configuration. An error occurred during execution of the YKLOAD command.

Conduct an investigation using the ISPF panel interface's load function.

nnnn

Return code of YKLOAD command

For details, see the description for the YKLOAD command in the Hitachi Business Continuity Manager Reference Guide.

YKW007E TSO

YKQUERY error return code = nnnn.

The YKWATCH command uses the YKQUERY command to establish the copy group status start baseline. An error occurred during execution of the YKQUERY command.

Conduct an investigation using the ISPF panel interface's load function.

nnnn

Return code of the YKQUERY command

For details, see the description for the YKQUERY command in the Hitachi Business Continuity Manager Reference Guide.

YKW008E TSO

YKCONMSG error return code = nnnn

The YKWATCH command uses the YKCONMSG command to monitor the console message traffic of IEA494I copy status messages. An error occurred during execution of the YKCONMSG command.

nnnn

Return code of the YKCONMSG command

For details, see the description for the YKCONMSG command in the Hitachi Business Continuity Manager Reference Guide.

YKW009W TSO

Terminated due to Operator attention.

An interrupt occurred during execution of the YKWATCH command. The TSO/E command issued within the YKWATCH command cannot be completed.

Re-execute the command.

YKW010E TSO

Processing error encountered. Reason code = rrrr

An error occurred during execution of the YKWATCH command. The YKCONMSG command issued within the YKWATCH command cannot be executed correctly.

rrrr

Return code of the YKCONMSG command

For details, see the description for the YKCONMSG command in the Hitachi Business Continuity Manager Reference Guide.

YKW098E TSO

Invalid parameter-reason-message

The YKWATCH command detected an invalid startup parameter.

YKW099I TSO

Group copy-group has reached the desired state state.

This message is issued to notify the user that the copy group identified by copy-group entered the requested status identified by state.

Table. List of messages starting with YK (YKX0x)

Message ID

Message text

Explanation and recommended actions

YKX000T TSO

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKX099I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKX001E TSO

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKX001E MSG SC=48

No serial# SN() supplied

Nothing is assigned to the SN parameter.

YKX002E TSO

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKX010E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKX065W MSG SC=4 RC=0

Storage system serial-number Command Device Definition Failed. (APID=apid)

The command device definition for the storage system identified by serial-number failed.

If multiple command devices are defined for the storage system, processing continues.

Operate according to the I/O error messages issued simultaneously.

serial-number

Serial number of the corresponding storage system

apid

APID of the command device that failed to be defined

YKX066E MSG SC=48 RC=48

Necessary Route List is not found.

The route list to be processed was not found.

Check the ROUTE parameter, DAD parameter, route list definition file, and command device definition file specified in the YKLOAD command. Check that the information corresponding to the storage system serial number specified in the YKBLDCMD command is set.

YKX099I TSO

YKBLDCMD command return code=nnnn, reason code=rrrr

The YKBLDCMD command terminated with the return code nnnn and the reason code rrrr.

This message is always displayed to indicate the return code and the reason code.

nnnn

Maximum among the severity codes returned during command execution

Table. List of messages starting with YK (YKX1x)

Message ID

Message text

Explanation and recommended actions

YKX100T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKX199I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKX101E MSG SC=48

No application id APID() supplied

Nothing is assigned to the APID parameter.

YKX101E MSG SC=48

No command control address CCA() supplied

Nothing is assigned to the CCA parameter.

YKX101E MSG SC=48

No control unit# CU() supplied

Nothing is assigned to the CU parameter.

YKX101E MSG SC=48

No device# DEVN() supplied

Nothing is assigned to the DEVN parameter.

YKX101E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKX101E MSG SC=48

No serial# SN() supplied

Nothing is assigned to the SN parameter.

YKX102E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKX103E MSG SC=48

Parameter combination is invalid

The specified parameter combination is invalid.

For details about the combination of parameters, see the description of the YKBLDCMD command or the YKDELCMD command in the Hitachi Business Continuity Manager Reference Guide.

YKX104E MSG SC=48

Device# DEVN(devn) is not found

The device specified in the DEVN parameter does not exist, or a device other than DASD or a PAV ALIAS volume has been specified.

devn

Device number specified for the DEVN parameter

YKX105E MSG SC=48

Device# DEVN(devn) is not found

The device specified in the DEVN parameter does not exist, or a device other than DASD or a PAV ALIAS volume has been specified.

devn

Subchannel set ID and device number specified for the DEVN parameter

YKX108E MSG SC=48

APID() not valid hex

The value specified in the APID parameter is not in hexadecimal format.

YKX108E MSG SC=48

CCA() not valid hex

The value specified in the CCA parameter is not in hexadecimal format.

YKX108E MSG SC=48

CU() not valid hex

The value specified in the CU parameter is not in hexadecimal format.

YKX108E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKX110E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services.

nnnn

Error code returned upon REXX access

YKX166E MSG SC=48

Necessary Route List is not found.

The route list to be processed was not found.

Review the ROUTE and DAD parameters, route list definition file, and command device definition file you specified when executing the YKLOAD command.

YKX199I TSO

YKDELCMD command return code=nnnn, reason code=rrrr

The YKDELCMD command terminated with the return code nnnn and the reason code rrrr.

Table. List of messages starting with YK (YKX2x)

Message ID

Message text

Explanation and recommended actions

YKX200T TSO RC=48

Supplied parameters invalid

Invalid parameters are specified.

For details, see the reason code in the YKX299I message that will appear after this message. For reason codes, see IKJPARS in the IBM manual TSO/E Programming Services.

YKX201E MSG SC=48

No command control address CCA() supplied

Nothing is assigned to the CCA parameter.

YKX201E MSG SC=48

No control unit# CU() supplied

Nothing is assigned to the CU parameter.

YKX201E MSG SC=48

No device# DEVN() supplied

Nothing is assigned to the DEVN parameter.

YKX201E TSO RC=48

No message MSG() supplied

Nothing is assigned to the MSG parameter.

YKX201E MSG SC=48

No model SMODEL() supplied

Nothing is assigned to the SMODEL parameter.

YKX201E MSG SC=48

No results STEM() supplied

Nothing is assigned to the STEM parameter.

YKX201E MSG SC=48

No serial# SN() supplied

Nothing is assigned to the SN parameter.

YKX201E MSG SC=48

No serial# SSN() supplied

Nothing is assigned to the SSN parameter.

YKX202E TSO RC=48

Messages MSG(stem) does not include trailing "."

The last character of the MSG parameter is not a period.

stem

Stem name assigned to the MSG parameter

YKX202E MSG SC=48

Results STEM(stem) does not include trailing "."

The last character of the STEM parameter is not a period.

stem

Stem name assigned to the STEM parameter

YKX203E MSG SC=48

Parameter combination is invalid

The specified parameter combination is invalid.

For details about the combination of parameters, see the description of the YKQRYDEV command in the Hitachi Business Continuity Manager Reference Guide.

YKX204E MSG SC=48

Device# DEVN(devn) is not found

The device specified in the DEVN parameter does not exist, or a device other than DASD or a PAV ALIAS volume has been specified.

devn

Device number specified for the DEVN parameter

YKX205E MSG SC=48

Device# DEVN(devn) is not found

The device specified in the DEVN parameter does not exist, or a device other than DASD or a PAV ALIAS volume has been specified.

devn

Subchannel set ID and device number specified for the DEVN parameter

YKX208E MSG SC=48

CCA() not valid hex

The value specified in the CCA parameter is not in hexadecimal format.

YKX208E MSG SC=48

CU() not valid hex

The value specified in the CU parameter is not in hexadecimal format.

YKX208E MSG SC=48

DEVN() not valid hex

The value specified in the DEVN parameter is not in hexadecimal format.

YKX210E TSO RC=40

REXX failure return code=nnnn starting with variable name

Access to the REXX variable identified by name failed.

For details about the return code, see IKJCT441 in the IBM manual TSO/E Programming Services

nnnn

Error code returned upon REXX access

YKX266E MSG SC=48

Necessary Route List is not found.

The route list to be processed was not found.

Review the ROUTE and DAD parameters, route list definition file, and command device definition file you specified when executing the YKLOAD command.

YKX299I TSO

YKQRYDEV command return code=nnnn, reason code=rrrr

The YKQRYDEV command terminated with the return code nnnn and the reason code rrrr.

Table. List of messages starting with YK (YKY0x)

Message ID

Message text

Explanation and recommended actions

YKY001I CON

AGENT STARTED (Vv.r.r[-zz])

The Business Continuity Manager agent has started.

v

Version number

r

Revision number

zz

Exception

YKY002I CON

INVALID INITIALIZATION PARAMETER: parameter-name

The specified parameter has not been defined in the initialization parameters, or the initialization parameter shown as parameter-name is invalid. The Business Continuity Manager agent has been terminated.

Correct the initialization parameters and then restart the Business Continuity Manager agent.

YKY003I CON

INVALID CONTINUATION LINE FOUND. PARAMETER SCAN TERMINATED

The initialization parameters contain the specification for a continuation line, but no parameter is continued. The Business Continuity Manager agent will be terminated.

Correct the initialization parameters and then restart the Business Continuity Manager agent.

YKY005I CON

AGENT INITIALIZATION FAILED P=termination-code

The Business Continuity Manager agent cannot start for the reason indicated in the message that was displayed before this message.

Contact the center administrator. The center administrator must take appropriate action for the message that was displayed before this message and then restart the Business Continuity Manager agent.

termination-code (decimal number)
  • 04: An attempt was made to start without using IKJEFT01.

  • 08: Initialization parameter analysis processing failed.

  • 48: A process module loading error occurred.

  • 52: A NAME/TOKEN write error occurred.

  • 56: No profile is defined in the FACILITY class of the RACF.

  • 60: Subtask initialization processing failed.

  • 68: An error occurred in the PREFIX exclusion processing.

YKY008I CON

INSUFFICIENT SPACE AVAILABLE FOR INITIALIZATION

Initialization parameters analysis failed due to a shortage of work space. The Business Continuity Manager agent will be terminated.

Check, and, if necessary, revise the specification of the user region in the job step in the Business Continuity Manager agent startup cataloged procedure, correct the memory requirements, and then restart the Business Continuity Manager agent.

YKY016I CON

TASK(task-ID) ABENDED,CODE=completion-code

A task terminated abnormally during the Business Continuity Manager agent start up. The Business Continuity Manager agent will be terminated.

task-ID

Name of the task

completion-code

System completion code

YKY018I CON

MODULE(load-module-name) NOT FOUND

The load module shown as load-module-name was not found. The Business Continuity Manager agent will be terminated.

Make sure that the indicated load module was installed correctly.

YKY019I CON

dd-name DD STATEMENT NOT FOUND

The DD statement shown as dd-name is missing. The Business Continuity Manager agent will be terminated.

Specify the DD statement in the cataloged procedure used for starting the Business Continuity Manager agent and then restart the Business Continuity Manager agent.

YKY020I CON

THE PROFILE IS NOT DEFINED IN THE FACILITY CLASS OF RACF: xxxxxxxx

The STGADMIN.YKA.BCM.YKQUERY or STGADMIN.YKA.BCM.COMMANDS profile is not defined in the FACILITY class of the RACF.

Review the RACF settings and then restart the Business Continuity Manager agent.

xxxxxxxx

Maintenance information

YKY021I CON

A NAME/TOKEN WRITE ERROR OCCURRED,​RC=​return-code,​NAME=name

The command cannot be executed because a NAME/TOKEN write error occurred. The Business Continuity Manager agent will now stop.

return-code

Return code set by the NAME/TOKEN registration routine (IEANTCR)

name

Name registered in the NAME/TOKEN service

YKY022I CON

THE SPECIFIED PREFIX IS BEING USED BY ANOTHER PROGRAM

The specified prefix is being used by another program.

Check the initialization parameters.

YKY051I CON

AGENT ENDED

The Business Continuity Manager agent was terminated.

YKY052I CON

AGENT IN SCHEDULED SHUTDOWN

The Business Continuity Manager agent termination processing has begun.

YKY053I CON

AGENT ABENDED

The Business Continuity Manager agent terminated abnormally.

If the cause is unknown, collect the ABEND dump in the SYSABEND dump format and then contact customer support for investigation.

Table. List of messages starting with YK (YKY1x)

Message ID

Message text

Explanation and recommended actions

YKY100I CON

MODIFY COMMAND ACCEPTED

The MODIFY command was accepted.

YKY101I CON

STOP COMMAND ACCEPTED

The STOP command was accepted.

YKY102I CON

INVALID error-type: text

After an entry of the MODIFY command, an error was detected in the command or operand shown as text.

Check, and, if necessary, revise the command.

error-type
  • COMMAND: Indicates that an error was detected in the command.

  • OPERAND: Indicates that an error was detected in the operand.

YKY103I CON

COMMAND SYNTAX ERROR

The entered command has a syntax error.

Check, and, if necessary, revise the command.

YKY104I CON

OPERAND IS INCORRECT

The specified operand is invalid.

Correct the error and then re-enter the operand.

YKY111I CON

parameter-name WAS CHANGED

The value of the initialization parameter has been changed. The parameter name is given in parameter-name.

YKY114I CON

parameter-name=parameter-value

This message displays the current value of the initialization parameter.

parameter-name

Initialization parameter name

parameter-value

Initialization parameter value

YKY130I CON

SESSION NO.=session-number

This message displays the TCP/IP session number. This message is followed by the TCP/IP session information.

session-number

Session identification number

YKY131I CON

host-type PORT=port-number HOST=IP-address

This message displays the port number and IP address of the local or remote host. This message is followed by the TCP/IP session information.

host-type

The type of host with the TCP/IP session information displayed

  • LOCAL: Indicates that the host is a local host.

  • REMOTE: Indicates that the host is a remote host.

port-number
  • When LOCAL is displayed in host-type:

    The port number of the local host

  • When REMOTE is displayed in host-type:

    The port number of the remote host

IP-address
  • When LOCAL is displayed in host-type:

    The IP address of the local host

  • When REMOTE is displayed in host-type:

    The IP address of the remote host

YKY132I CON

CONNECTING START TIME=YYYY/MM/DD hh:mm:ss

This message displays the time the corresponding TCP/IP session was established. This message is followed by the TCP/IP session information.

YYYY/MM/DD hh:mm:ss

Time (local time)

YKY133I CON

LAST data-direction-type TIME=YYYY/MM/DD hh:mm:ss

This message displays the last transmission or reception time in the corresponding TCP/IP session.

data-direction-type

The direction of the data that was sent at the time displayed in YYYY/MM/DD hh:mm:ss

  • SEND: Indicates that the data was sent.

  • RECV: Indicates that the data was received.

YYYY/MM/DD hh:mm:ss

Time (local time)

Table. List of messages starting with YK (YKY3x - YKY5x)

Message ID

Message text

Explanation and recommended actions

YKY300I SYS

hh:mm:ss task-ID,TCP CONNECTION ACCEPTED

The TCP connection request was accepted. Information about the communication with the remote host is displayed in the YKY307I message.

hh:mm:ss

Message output time (local time)

task-ID

Number used to identify the processing task that output the message

YKY301I SYS

hh:mm:ss task-ID,TCP CONNECTION ENDED NORMALLY

The TCP connection was released successfully.

hh:mm:ss

Message output time (local time)

task-ID

Number used to identify the processing task that output the message

YKY304I SYS

hh:mm:ss task-ID,REQUEST DENIED,​REASON=​(reason-for-denial)

The request was received, but was denied.

hh:mm:ss

Message output time (local time)

task-ID

Number used to identify the processing task that output the message

reason-for-denial
  • INVALID FORMAT: The format is invalid.

  • VERSION MISMATCH: The version does not match.

YKY305I CON

task-ID,TCP CONNECTION LOST DURING EVENT PROCESSING,​TCP-STATUS=​(reason-​for-​disconnection)

The TCP connection was lost during TCP/IP processing for the reason shown as reason-for-disconnection.

Determine the cause of disconnection from the remote host.

task-ID

Number used to identify the processing task that output the message

reason-for-disconnection
  • FIN ACCEPT: A disconnection request (TCP-FIN) from the remote host was received.

  • RST ACCEPT: A disconnection request (TCP-RST) from the remote host was received.

YKY307I SYS

hh:mm:ss task-ID,TCP CONNECTION INFORMATION,​REMOTE-HOST=​IP-address,​REMOTE-PORT=​remote-​port-​number,​LOCAL-PORT=​local-​port-​number

The TCP connection request was accepted.

Take appropriate action according to the message that was displayed before this message.

hh:mm:ss

Message output time (local time)

task-ID

Number used to identify the processing task that output the message

IP-address

IP address of the remote host

remote-port-number

Port number of the remote host

local-port-number

Port number of the local host

YKY315I CON

task-ID,COMMUNICATION ERROR,​@API​[,request-name​[,RC=​response-code]]​[,EC=​event-code]​[,SRC=​local-​IP-​address​:​local-​port-​number]​[,DST=​connection-​target-​IP-​address​:​connection-​target-​port-​number]

A communication error was detected. The message displays the request name, the target IP address:target port number (decimal number), and the local IP address:local port number (decimal number).

The currently executing process is canceled. If necessary, check the YKY330I message that was displayed immediately before this message to determine the cause of the error.

task-ID

Number used to identify the processing task that output the message

request-name
  • @OPNSAP: Preprocessing

  • @OPEN: Processing for establishing a connection

  • @SEND: Send processing

  • @RECV: Receive processing

  • @CLOSE: Processing for releasing the connection

  • @QUERY: Remote address search processing

  • @ABORT: Forcibly releasing the connection

  • @QUIT: Postprocessing

response-code

Code generated during the request shown as request-name

event-code

Event that occurred during the TCP/IP session

local-IP-address

IP address of the local host

local-port-number

Port number of the local host

connection-target-IP-address

IP address of the connection target host

connection-target-port-number

Port number of the connection target host

YKY321I CON

task-ID,COMMUNICATION TIMED OUT

There is no response within the specified response wait time. The connection will be released.

Check the cause of the response timeout.

task-ID

Number used to identify the processing task that output the message

YKY330I CON

SOCKET API FAILURE (maintenance-​information,​request-​type,​return-​code,​error-​number)

The request shown as request-type resulted in an error on the socket interface for IBM® TCP/IP for MVS®. return-code and error-number indicate the error information.

Check the cause of the error and take appropriate action. If TCP/IP has stopped due to the error, stop the Business Continuity Manager agent. Once the error is corrected, start the TCP/IP program, and then start the Business Continuity Manager agent.

maintenance-information

Detailed information used for error analysis

request-type

One of the following request types is displayed:

  • "ACCEPT "

  • "BIND "

  • "CLOSE "

  • "INITAPI "

  • "IOCTL "

  • "LISTEN "

  • "RECV "

  • "SETSOCKOPT "

  • "SOCKET "

For details about the return code (RETCODE) for the request type and the error number (ERRNO), see the IBM manual Communications Server IP API Guide.

YKY362I CON

RECEIVED DATA SIZE INVALID,​DST=​connection-​target-​IP-​address​:​connection-​target-​port-​number

The Business Continuity Manager agent received an invalid size of data from connection-target-IP-address:connection-target-port-number. The corresponding receive processing will be stopped.

The size of data that can be received is 4,096 bytes. Check, and, if necessary, revise the received data size, and then re-execute the operation.

YKY500I SYS

RESULT OF UPDATING THE CONFIGURATION FILE: result

This message indicates whether the configuration file was successfully updated.

If the configuration file failed to be updated, see the other error message that was output with this one and take appropriate action.

result

Indicates the result.

  • SUCCESS: The update succeeded.

  • FAILURE: The update failed.

YKY501E XML

Disk configuration definition error-type error. file

An error occurred in the disk configuration definition file. See the error-type, and then remove the error. After that, retry the operation from Replication Manager.

error-type
  • ALLOCATE: An allocation error

    Make sure that the file indicated by file exists.

  • EXECIO: An input error

    Make sure that the file indicated by file has not been broken.

  • format: An XML format error

    Make sure that the XML description does not contain an error.

file

Name of the disk configuration definition file in which an error occurred

YKY502E XML

Configuration file DELETE error. file

During the update process for the configuration file, an error occurred during the attempt to delete the old configuration file. Remove the error, and then take the following action:

  1. If the configuration file in which the error occurred still exists, delete it.

  2. Change the name of the temporary file to the name indicated by file.

    For details on names of temporary files, see the chapter that explains linking with Replication Manager in the Hitachi Business Continuity Manager Installation Guide.

  3. Restart the Business Continuity Manager agent, and then refresh the configuration file from Replication Manager.

file

Name of the configuration file in which an error occurred

YKY503E XML

Temporary file error-type error. file

An error occurred in the temporary file. Check whether the temporary file indicated by file exists. If the error type is RENAME and the temporary file exists, change the name of the temporary file to the name of the configuration file that you want to update. After that, restart the Business Continuity Manager agent, and then refresh the configuration file from Replication Manager. If the error type is something other than RENAME and the temporary file exists, delete the temporary file.

error-type
  • ALLOCATE: An allocation error

  • READWRITE: An I/O error

  • DELETE: A deletion error

  • RENAME: A renaming error

file

Name of the temporary file in which an error occurred

YKY507E XML

Routelist configuration file error error-type. file

An error occurred in the route list definition file. See the error-type, and then remove the error. After that, retry the operation from Replication Manager.

error-type
  • ALLOCATE: An allocation error

    Make sure that the file indicated by file exists.

  • EXECIO: An input error

    Make sure that the file indicated by file has not been broken.

  • format: An XML format error

    Make sure that the XML description does not contain an error.

file

Name of the route list definition file in which an error occurred

Table. List of messages starting with YK (YKY6x)

Message ID

Message text

Explanation and recommended actions

YKY600I CON

INSUFFICIENT SPACE AVAILABLE. maintenance-information

The area allocation by the Business Continuity Manager agent failed. The Business Continuity Manager agent will be terminated.

Increase the region size and then restart the Business Continuity Manager agent.

maintenance-information

Detailed information used for error analysis

YKY604I CON

IRXJCL MODULE ERROR,CODE=return-code

The IRXJCL routine returned an error with the return code shown as return-code. The Business Continuity Manager agent will terminate the processing.

Check the return code. If the return code is 20, the SYSEXEC DD statement might be invalid in the cataloged procedure used for starting the Business Continuity Manager agent. Check, and, if necessary, revise JCL, and then re-execute.

return-code
  • 20: Processing failed. The EXEC processing was not performed.

  • 20021: The parameter list passed to IRXJCL was invalid.

YKY605I CON

IRXINIT MODULE ERROR,​CODE=​return-code,​R0=​abnormal-​termination-​code-​and-​reason-​code,​PARM7=​reason-code

The IRXINIT routine returned an error with the return code shown as return-code. The Business Continuity Manager agent will terminate the processing.

Check the return code.

return-code
  • 20: Processing failed due to an error. Check the reason code that was returned to PARM7 by IRXINIT.

  • 100: Processing failed because the system terminated abnormally while IRXINIT was checking the environment. The system might output multiple messages reporting abnormal termination. R0 includes the abnormal termination code and the reason code for abnormal termination.

abnormal-termination-code-and-reason-code

IRXINIT returns the abnormal termination code set in the two trailing bytes of R0. IRXINIT returns the reason code for abnormal termination set in the two leading bytes of R0. If the reason code for abnormal termination is larger than two bytes, IRXINIT returns only the two trailing bytes of the reason code for abnormal termination. For details about the abnormal termination code and reason code, see the IBM manual MVS System Codes.

reason-code

For details about the reason code, see the IBM manual TSO/E REXX Reference.

YKY606I CON

IRXTERM MODULE ERROR,​CODE=​return-code,​R0=​abnormal-​termination-​code-​and-​reason-​code

The IRXTERM routine returned an error with the indicated return code. The Business Continuity Manager agent terminates the processing.

Check the return code.

return-code

For details about the return code, see the IBM manual TSO/E REXX Reference.

abnormal-termination-code-and-reason-code

R0 includes the abnormal termination code and the reason code for abnormal termination. IRXTERM returns the abnormal termination code set in the two trailing bytes of R0. IRXTERM returns the reason code for abnormal termination set in the two leading bytes of R0. If the reason code for abnormal termination is larger than two bytes, IRXTERM returns only the two trailing bytes of the reason code for abnormal termination. For details about the abnormal termination code and reason code, see the IBM manual MVS System Codes.

YKY680I SYS

hh:mm:ss task-ID,​command,​RC=​return-code​[,text]

A command that was issued by the Business Continuity Manager agent ended with return-code. Messages for detected errors are output to text.

If the number of characters in the message output by the command exceeds 126, it will be displayed on multiple lines. The maximum number of message lines for a single command is 10.

hh:mm:ss

Message output time (local time)

task-ID

Identification number of the processing task to which the message was output

command

Name of the command that the Business Continuity Manager agent executed

return-code

Return code from the command that the Business Continuity Manager agent executed

text

Message (maintenance information) that was output by the command that the Business Continuity Manager agent executed

YKY699I CON

AGENT FUNCTION ABEND CODE=Sxxx Uxxxx DATE=yy-mm-dd TIME=hh:mm:nn

ABENDED-MODULE=module-name C-DATE=module-creation-date BASE=bbbbbbbb DISP=dddd

[CALLING-MODULE=module-name C-DATE=y'y'.m'm'.d'd' BASE=bbbbbbbb DISP=dddd]

PSW=pppppppp pppppppp ILC=ll INTC=xx

REGISTERS AT TIME OF FAILURE

GR 00-03 contents-of-register-0 contents-of-register-1 contents-of-register-2 contents-of-register-3

GR 04-07 contents-of-register-4 contents-of-register-5 contents-of-register-6 contents-of-register-7

GR 08-11 contents-of-register-8 contents-of-register-9 contents-of-register-10 contents-of-register-11

GR 12-15 contents-of-register-12 contents-of-register-13 contents-of-register-14 contents-of-register-15

The main task or subtask terminated abnormally during the Business Continuity Manager agent processing. If the task cannot be recovered, the Business Continuity Manager agent will be terminated.

Contact the center administrator.

Sxxx (hexadecimal)

System completion code when the task terminated abnormally

Uxxxx (decimal number)

User completion code when the task terminated abnormally

yy-mm-dd

Date the task terminated abnormally

hh:mm:nn

Time the task terminated abnormally

module-name

Section name of the Business Continuity Manager agent module or the load module name

If the module cannot be identified, UNKNOWN is displayed. When UNKNOWN is displayed, the values indicated by y'y'.m'm'.d'd' and bbbbbbbb are not correct.

module-creation-date

This is displayed in one of the following formats:

  • y'y'.m'm'.d'd': Creation date of the module indicated by module-name

  • y'y'/m'm'/d'd': Creation date of the module indicated by module-name

bbbbbbbb

Contents of the base register

dddd
  • ABENDED-MODULE: Location where ABENDED-MODULE was called, relative to the top of the module

  • CALLING-MODULE: Location where CALLING-MODULE was called, relative to the top of the module

pppppppp pppppppp

PSW during the abnormal termination

ll

Length of command during the abnormal termination

xx

Interrupt code during the abnormal termination

Table. List of messages starting with YK (YKY7x - YKY9x)

Message ID

Message text

Explanation and recommended actions

YKY703E XML

XML translation error: The sent entity is not XML.

The sent entity is not XML.

Revise the specified request.

YKY704E XML

End of request was detected in the comment.

The end of the XML request was detected in the comment.

Revise the comment.

YKY705E XML

End of request was detected in an element.

The end of the XML request was detected in an element.

Revise the last element in the XML request.

YKY706E XML

The number of elements exceeded the allowed limit.

The number of element hierarchies exceeded the permitted maximum value (16).

Revise the specified request.

YKY707E XML

The request version is a mismatch.

The API version of the XML request is not supported.

Make sure that the version is supported by the Business Continuity Manager agent.

YKY713E XML

An invalid element 'element-name' was specified in the XML request.

An invalid element-name was specified in the XML request.

Revise the specified request.

YKY714E XML

An invalid parameter 'parameter-name' was specified in the XML request element 'element-name'.

An invalid parameter-name was specified in the XML request element element-name.

Revise the specified request.

YKY715E XML

An invalid value was specified for the parameter 'parameter-name' in the XML request element 'element-name'.

An invalid value was specified for parameter-name in the XML request element element-name.

Revise the specified request.

YKY716E XML

An invalid child element 'child-element-name' was specified in the XML request element 'parent-element-name'.

An invalid child element