HP P9000 Command View Advanced Edition Suite software Mainframe Agent Installation and Configuration Guide Part number: TB581-96078 Sixth edition: November 2011
Legal and notice information © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. Confidential Computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Preface ................................................................................................ 9 1 About P9000 mainframe agent ......................................................... 11 Why use P9000 mainframe agent ? ............................................................................................ Installation requirements ............................................................................................................ Operating system requirements ...............
Setting the TCP/IP port number ................................................................................................... Setting the security .................................................................................................................... Setting the dataset security .................................................................................................. Setting up the Resource Access Control Facility (RACF) when linking with Replication Manager software .............
Software settings ......................................................................................................... Copy types and units that can generate configuration files ................................................ Supported PPRC commands .......................................................................................... YKP2A command ............................................................................................................... Format ................................
Subscription service .......................................................................................................... Documentation feedback ................................................................................................... New and changed information in this edition ............................................................................. Related information .................................................................................................................
Figures 1 P9000 mainframe agent configuration with P9000 Command View AE Suite products ................................................................................................................ 13 2 Configuration for using Replication Manager software to monitor PPRC copy pairs .......... 14 3 Configuration for using Device Manager to view storage information managed by the mainframe host and using Replication Manager software to monitor PPRC copy pairs ......
Tables 1 Programs required to use P9000 mainframe agent ...................................................... 12 2 Datasets stored on the installation CD-ROM ................................................................ 18 3 Storage attributes of library datasets .......................................................................... 19 4 YKALCSVC command return codes list .......................................................................
Preface This guide provides information about HP StorageWorks P9000 Command View Advanced Edition mainframe agent (called P9000 mainframe agent throughout), including the tasks like installing, setting up, starting, stopping, and troubleshooting and messages. This guide is intended for system administrators who install, set up, operate, or troubleshoot P9000 mainframe agent.
Preface
1 About P9000 mainframe agent This chapter explains the purpose of P9000 mainframe agent. The chapter also lists P9000 mainframe agent installation requirements, and provides an example system configuration. Why use P9000 mainframe agent ? P9000 mainframe agent is a product you can use to display information about mainframe system storage on a GUI of Device Manager or Replication Manager software.
Application software requirements The following table lists the P9000 mainframe agent.
System configuration example The following kinds of configurations exist: • Device Manager is used to view storage information managed by the mainframe host • Replication Manager software is used to monitor the statuses of PPRC copy pairs managed by the mainframe host • Device Manager is used to view storage information managed by the mainframe host, and Replication Manager software is used to monitor the statuses of PPRC copy pairs managed by the mainframe host Using Device Manager to view storage informa
Figure 2 Configuration for using Replication Manager software to monitor PPRC copy pairs The P9000 mainframe agent disk configuration definition file and copy group definition file are required for monitoring the statuses of PPRC copy pairs. For details, see “Using Replication Manager software to monitor PPRC copy pairs” on page 51.
Figure 3 Configuration for using Device Manager to view storage information managed by the mainframe host and using Replication Manager software to monitor PPRC copy pairs P9000 mainframe agent configuration files (disk configuration definition file and copy group definition file) are required for monitoring the statuses of PPRC copy pairs. For details, see “Using Replication Manager software to monitor PPRC copy pairs” on page 51.
About P9000 mainframe agent
2 Installing P9000 mainframe agent This chapter provides an overview of installing P9000 mainframe agent , describes pre-installation checks, and explains the installation and upgrade procedures. Installation overview The following figure provides an overview of installing P9000 mainframe agent. Figure 4 Overview of installing P9000 mainframe agent Pre-installation checks This section describes the items that you need to check before installing P9000 mainframe agent.
Provided datasets The following table lists the datasets that are on the installation CD-ROM. Table 2 Datasets stored on the installation CD-ROM Name of dataset on installation CD-ROM Library type Description MFAGENT.Vnnnn.SAMPLIB.XMIT SAMPLIB Sample file provided in the standard package (the initialization parameters and startup cataloged procedures for P9000 mainframe agent) MFAGENT.Vnnnn.LINKLIB.XMIT LINKLIB Load module for P9000 mainframe agent MFAGENT.Vnnnn.LPALIB.
Storage attributes of library datasets When you run an installation JCL, P9000 mainframe agent is registered in the library datasets with the storage attributes shown in the following table.
Installation procedure This section explains how to install P9000 mainframe agent. Installing P9000 mainframe agent The following figure shows the workflow of installing P9000 mainframe agent. Figure 5 Workflow of installing P9000 mainframe agent The following task outlines the installation of the P9000 mainframe agent. The numbers in the procedure correspond to the numbers in Figure 5. To install P9000 mainframe agent: 1. Insert the installation CD-ROM. 2.
4. Create space for the datasets to be transferred (execute the edited YKAGALLO job). The YKAGALLO job creates the sequential dataset space for transferring the P9000 mainframe agent object archive and the REXX alternate library archive to the host machine. 5. From the PC, transfer in binary mode the P9000 mainframe agent object archive and the REXX alternate library archive to the transfer dataset space allocated on the host machine.
Parameters SVC-number ~ ((200 to 255)) Specifies an SVC number to assign to a user SVC. DELETE Specified to delete a user SVC. If you omit the optional PARM= part of the command, an unused SVC number between 200 and 255 is assigned. Return codes Used to indicate task status, as shown in the following table. Table 4 YKALCSVC command return codes list Return code Meaning 0 The command ended normally. 4 The SVC number is already registered.
2. Insert the following SYMDEF statement (&YKSVCNO system symbol) into the IEASYMxx parmlib member: SYMDEF(&YKSVCNO='SVC-number') For the SVC-number, specify a decimal number between 200 and 255. 3. Use one of the following methods to link the LPALIB library of P9000 mainframe agent to LPALST: • Define the LPALIB library of P9000 mainframe agent in the LPALSTxx parmlib member. For details, see the MVS Initialization and Tuning Reference.
CAUTION: • If you delete a user SVC using the YKALCSVC command while P9000 mainframe agent is running, storage information may not be sent to Device Manager or Replication Manager software correctly. • If you register a user SVC using the YKALCSVC command while P9000 mainframe agent is running, any already-executing CLI command will continue to execute in the user SVC defined in the IEASVCxx parmlib member.
Checks before upgrading Checking whether to upgrade Device Manager Because P9000 mainframe agent is provided with Device Manager, make sure that you upgrade the server and mainframe hosts at the same time. Checking the user SVC number Check the user SVC number because you must assign the same number after upgrading. The method of checking the user SVC number varies depending on whether the user SVC was registered with the YKSETENV command or the IEASVCxx parmlib member.
3. Perform IPL with the CLPA parameter specified. Removing the concatenation of cataloged procedure libraries Remove the dataset concatenation of the library shown in the table below. If you copied the PROCLIB library members to a user PROCLIB, delete the copied members.
3 Setting up P9000 mainframe agent This chapter explains how to set up the environment to acquire storage information using the P9000 mainframe agent . Setting the TCP/IP port number Before performing this procedure, you need to reserve a port number for communicating with Device Manager or Replication Manager software. For a job that starts the P9000 mainframe agent, set the UNIX service's usage attributes (open a port for receiving).
Setting the dataset security When a P9000 mainframe agent is linked to Replication Manager software, the P9000 mainframe agent job references the P9000 mainframe agent's configuration files. Therefore, be sure to grant the P9000 mainframe agent job READ permission for the configuration files that are accessed by the P9000 mainframe agent job.
->SETROPTS CLASSACT(FACILITY) ->RDEFINE FACILITY STGADMIN.YKA.BCM.YKQUERY UACC(NONE) ->PERMIT STGADMIN.YKA.BCM.YKQUERY CLASS(FACILITY) ID(user-ID) ACCESS(READ) To improve the execution performance of the P9000 mainframe agent, activate the RACLIST function (in-storage profiles) for the FACILITY class using one of the following commands.
Figure 6 Example configuration when using IPv6 to establish connections To set up IBM HTTP Server to run as a reverse proxy server, specify the settings described in the following table for the httpd.conf file. Table 6 Settings to be specified in the httpd.conf file for IPv6 connections Directive to be specified Description of directive, and values to be specified CacheDisable Specify this directive so that the cache function for requests directed to the P9000 mainframe agent is disabled.
Directive to be specified Description of directive, and values to be specified Specify the following options to set up P9000 mainframe agent to act as the origin server for Device Manager or Replication Manager software: • The host name or IPv4 address of the host that is running P9000 mainframe agent ProxyPass and ProxyPassReverse • The port number that was specified for the PORT parameter when initially setting up P9000 mainframe agent The following example shows how to specify the options: ProxyPass /
You can specify more than one SETINIT command. You can specify different parameters for one SETINIT command, but cannot specify the same parameter more than once. If you specify the same parameters more than once for one SETINIT command, the last specified parameter is applied. To specify the same parameter more than once, use a separate SETINIT command. If a parameter that cannot be specified more than once in separate SETINIT commands is specified in that way, the last specified parameter is applied.
Continuing to the next line To continue a parameter onto the next line, enter a continuation symbol at the end of the line. The following table shows the continuation symbols. Table 7 Continuation symbols Continuation symbols Continuation method Hyphen (-) The hyphen is removed, and the parameter is continued in the leftmost column of the next line, retaining any contiguous spaces. Plus sign (+) The plus sign is removed, and the parameter is continued on the next line, removing any contiguous spaces.
/* COMMENT */ SETINIT PORT(24042) /* COMMENT */ Example of an invalid comment: If you specify a comment as follows, the text /* ERROR COMMENT */ will be interpreted as a part of the parameter instead of being interpreted as a comment: SETINIT DEVN(7300, + /* ERROR COMMENT */ 730F) Notes during creation of initialization parameters Do not specify an empty member as an initialization parameter when you start the P9000 mainframe agent.
HOSTNAME('host-identification-name') ~ <1 to 50 alphanumeric characters> <> Specify this parameter when Device Manager or Replication Manager software needs to identify the P9000 mainframe agent. When the P9000 mainframe agent is running on more than one host, and a HOSTNAME (host identification name) value is duplicated in these hosts, Device Manager or Replication Manager software cannot identify the host on which the target P9000 mainframe agent is running.
• In the PREFIX parameter, do not specify any value other than the prefix of the configuration file. If multiple datasets correspond to the specified prefix (such as the SYS1 prefix), P9000 mainframe agent processing might slow down. • Do not specify multiple PREFIX parameters for the same prefix. The monitoring processing of Device Manager or Replication Manager software might slow down.
Determining whether parameters can be specified more than once The following table explains what results when multiple SETINIT commands are used to specify each initialization parameter: Table 9 Whether the initialization parameter can be specified more than once Parameter name Results of multiple specification PORT RECVWAITTIME If specified more than once, the last specified parameter is applied.
Figure 7 Example configuration for connecting to Device Manager To connect P9000 mainframe agent to Device Manager in the configuration shown in Figure 7, specify the values shown in the following table.
When connecting to Replication Manager software This subsection explains how to specify initialization parameters when connecting P9000 mainframe agent to Replication Manager software. The following example configuration is used to explain the specification method. Figure 8 Example configuration for connecting to Replication Manager software To connect P9000 mainframe agent to Replication Manager software in the configuration shown in Figure 8, specify the values shown in the following table.
SETINIT LOGLEVEL(2) SETINIT PORT(24042) /* PREFIX */ SETINIT PREFIX('ACCOUNT','NY') SETINIT PREFIX('INFO','NY') /* DEVN */ SETINIT DEVN(7300,730F) SETINIT DEVN(7400,740F) Examples of initialization parameter analysis results When the P9000 mainframe agent starts, the results of the initialization analysis is output to the dataset specified in the YKLIST DD statement. The following examples show results. In the result list, the nn-nn portion varies depending on the P9000 mainframe agent version.
Standard cataloged procedure for startup in the expanded format • Member name: YKAGENTD In the sample JCL, the nnnn portion of Vnnnn varies depending on the version. //YKAGENTD PROC MEMBER=YKPRM00 //**************************************************************** //* //* ALL RIGHTS RESERVED. COPYRIGHT (C) 2006, 2011, HITACHI, LTD. //* //**************************************************************** //IEFPROC EXEC PGM=IKJEFT01,PARM=YKAGENTD, // TIME=1440,REGION=4096K //YKPARM DD DSN=MFAGENT.Vnnnn.
7. SYSABEND DD statement Specifies the location to which the dump is output when the P9000 mainframe agent terminates abnormally. SYSOUT=* is specified in the standard cataloged procedure for startup. If the DUMMY output class is assigned as the output destination class for system messages in a job that is started by the START command, we recommend that you specify SYSOUT=SYSOUT-class-enabled-for-output, since the dump is not output with SYSOUT=* specified. 8.
Registering the mainframe host in Device Manager To use the AddHost command to register the mainframe host in Device Manager: 1. Execute the AddHost command to register the mainframe host in Device Manager. When you execute the command, specify the following parameters: • hostname: In this parameter, specify the host name of the mainframe host (the value you specified for the parameter in “Parameters” on page 34). • hosttype: In this parameter, specify 2. 2.
1. Execute the AddURLLink command to register the P9000 mainframe agent running on the mainframe host in Device Manager. When you execute the command, specify the following parameters: • url: In this parameter, specify the IP address and port number. If the mainframe host is in an IPv4 environment, specify the IP address of the mainframe host on which P9000 mainframe agent is installed, and the port number used by P9000 mainframe agent.
When you execute the command, specify the following parameters: objectid: Specify the object ID of the mainframe host that was output when the mainframe host was registered using the AddHost command. Action to be taken if an error occurs during the execution of the AddHostRefresh command: 1. Check whether P9000 mainframe agent is operating normally. If it is not operating normally, check the P9000 mainframe agent settings, and restart P9000 mainframe agent. 2.
hdvmcli AddHostRefresh -o "D:\logs\AddHostRefresh.log" "objectid=HOST.1" Acquiring P9000 mainframe agent information registered in the Device Manager To acquire P9000 mainframe agent information registered in the Device Manager server, use the GetURLLink command. By executing this command, you can acquire the IP address and port number of the mainframe host from the url information in the execution results. Example of executing the command: hdvmcli GetURLLink -o "D:\logs\GetURLLink.log" "objectid=URLLINK.
1. Execute the GetHost command with no object ID specified to acquire a list of all hosts registered in Device Manager. 2. In the displayed host information, find the name of the mainframe host you are looking for. 3. Acquire the object ID based on the information related to the mainframe host you found in step 2. Example of executing the command: hdvmcli GetHost -o "D:\logs\GetHost.log" "objectid=HOST.
Registering an information source When you register P9000 mainframe agent as an information source, you need to specify the following information: • P9000 mainframe agent name (nickname) • IP address or host name of P9000 mainframe agent • Port number Setting the interval for collecting configuration information Set the interval for collecting copy pair configuration information and the start time of the collection.
4 Using P9000 mainframe agent This chapter explains how to link with Device Manager and Replication Manager software to acquire storage information that is from an open system and managed by a mainframe, and how to monitor PPRC copy pairs. Using Device Manager to collect mainframe system storage information This section describes how to use Device Manager to collect mainframe system storage information.
Figure 10 Operating procedure for installing P9000 mainframe agent To install P9000 mainframe agent: 1. See the following sections to set up the P9000 mainframe agent environment: 2. • Setting the TCP/IP port number, page 27 • Setting the security, page 27 • Creating initialization parameters, page 31 • Creating a cataloged procedure for startup, page 40 Start P9000 mainframe agent. see “Starting P9000 mainframe agent” on page 64. 3.
Figure 11 Operating procedure for changing the configuration of P9000 mainframe agent To change the configuration of P9000 mainframe agent: 1. Stop information collection by Device Manager. 2. Stop P9000 mainframe agent. see “Stopping P9000 mainframe agent” on page 65. 3. Correct the initialization parameter. see “Creating initialization parameters” on page 31. 4. Start P9000 mainframe agent. see “Starting P9000 mainframe agent” on page 64. 5. Restart information collection by Device Manager.
Figure 12 Overview of an operation in which Replication Manager software is used to monitor PPRC copy pairs CAUTION: The device number displayed as the device number of the PPRC copy pair secondary volume is not the same as the device number defined in the host because it is automatically assigned by the YKP2A command. Operation procedures To monitor PPRC copy pairs, configuration files for P9000 mainframe agent are required.
The following figure shows the steps to monitor PPRC copy pairs using Replication Manager software: Figure 13 Monitoring PPRC copy pairs using Replication Manager software 1. Use PPRC to put the copy pairs in operating status. 2. Set the security. For details, see “Setting up the Resource Access Control Facility (RACF) when linking with Replication Manager software” on page 28. 3.
Prerequisites for the copy group definition generation function The following shows the prerequisites for using the copy group definition generation function for PPRC copy pairs. Prerequisite hardware The following table describes the prerequisite hardware for using the copy group definition generation function for PPRC copy pairs.
Supported PPRC commands Table 15, Table 16, and Table 17 describe the PPRC commands supported by the copy group definition generation function for PPRC copy pairs. Configuration files can be generated for PPRC copy pairs that have been defined and operated by a PPRC command with the parameter values that have Yes indicated in the Supported column of each of these tables.
PPRC copy pair Parameter Value Supported NO(default) Yes Table 16 Supported parameter values for the pair suspend command (CSUSPEND) PPRC copy type Parameter Value Supported Specified No Omitted(default) Yes Specified No Omitted(default) Yes AGD00 Yes AGP00 No AVD00 No AVP00 No PRIMARY Inner-DKC asynchronous copy pair, Synchronous copy pair QUIESCE Asynchronous copy pair cmd_parm Table 17 Supported parameter values for the resynchronization command (CESTPAIR) PPRC copy type Par
YKP2A command The YKP2A command is a TSO/E command for generating configuration files for PPRC copy pairs. The following are explanations of the format and function of the YKP2A command. For details about elements and symbols used for command syntax descriptions, see Appendix A on page 109.
This specifies the device numbers for the range over which primary volumes for PPRC copy pairs are scanned. For device-number-1, specify the initial DEVN of the scan range, and for devicenumber-2, specify the last DEVN. For example, to scan primary volumes of PPRC copy pairs in the device number range from 7000 to 7300, specify DEVN(7000,7300). If device-number-1 is larger than device-number-2, device-number-2 is used as the initial DEVN in the scan range, and device-number-1 is used as the last DEVN.
if PREFIX(MFA.MIGRATE) and CGNAME1(MFATCS) are specified and three synchronous copy groups are generated, configuration files that have the following names are generated: MFA.MIGRATE.GRP.MFATCS00 MFA.MIGRATE.GRP.MFATCS01 MFA.MIGRATE.GRP.MFATCS02 If the CGNAME1 parameter is omitted, or no name is specified, MYTCS is used. CGNAME2(asynchronous-copy-group-name) ~ This specifies the asynchronous copy group name.
of information. In this case, collect the information for the next request (at the set interval for Replication Manager software). Return codes The following table lists the return codes for when the YKP2A command terminates. Table 18 Return codes for the YKP2A command Return code Description 0 Successful completion. The disk configuration definition file and copy group definition file are generated. 4 Successful completion. No PPRC copy pairs were detected in the specified device number range.
Example configuration for monitoring PPRC synchronous and asynchronous copy pairs The following figure shows an example of a configuration for combining PPRC synchronous and asynchronous copy pairs. Figure 14 Example configuration for monitoring PPRC synchronous and asynchronous copy pairs If the following YKP2A command is executed in the configuration shown in Figure 14, the configuration files for monitoring MFATCS and MFATCA are generated. YKP2A PREFIX(MFA.
Example configuration for monitoring only PPRC inner-DKC asynchronous copy pairs The following figure shows an example of a configuration for only PPRC inner-DKC asynchronous copy pairs. Figure 15 Example configuration for monitoring only PPRC inner-DKC asynchronous copy pairs If the following YKP2A command is executed in the configuration shown in Figure 15, the configuration files for monitoring MFASI are generated. YKP2A PREFIX(MFA.
Example configuration for monitoring PPRC synchronous and inner-DKC asynchronous copy pairs The following figure shows an example of a configuration for combining PPRC synchronous and inner-DKC asynchronous copy pairs. Figure 16 Example configuration for monitoring PPRC synchronous and inner-DKC asynchronous copy pairs If the following YKP2A command is executed in the configuration shown in Figure 16, the configuration files for monitoring MFATCS and MFASI are generated. YKP2A PREFIX(MFA.
Operation commands This section describes the commands used for P9000 mainframe agent operation. For details on the symbols used to explain the command syntax, see Table 25. For details on the command syntax elements, see Table 26. Starting P9000 mainframe agent To start P9000 mainframe agent, use the START command. P9000 mainframe agents reside on the system, and run in accordance with the definition of the YKPRMxx initialization parameter. You can start multiple P9000 mainframe agents.
START YKAGENTD.YK,MEMBER=YKPRM10,SYSOUT=X Stopping P9000 mainframe agent To stop P9000 mainframe agent, use the STOP command. If a request from another P9000 Command View AE Suite product is accepted before execution of the STOP command, the stop processing is suspended until the processing for that request completes. Format If both the name of the cataloged procedure for startup and the identification name were specified in the START command: STOP 1[cataloged-procedure-for-startup-name.
Return codes The following table lists and describes P9000 mainframe agent return codes when an agent is stopped.
Example To forcibly stop a P9000 mainframe agent that was started and whose identification name is YK, enter the following command: CANCEL YK Displaying the log output level To display the current P9000 mainframe agent log output level, use the MODIFY command with the DISPLAY LOGLEVEL parameter specified. Format If both the name of the cataloged procedure for startup and the identification name were specified in the START command: MODIFY 1[cataloged-procedure-for-startup-name.
MODIFY YK,DISPLAY LOGLEVEL YKY114I LOGLEVEL=2 Changing the log output level To change the P9000 mainframe agent log output level, use the MODIFY command with the SETINIT LOGLEVEL parameter. Format If both the name of the cataloged procedure for startup and the identification name were specified in the START command: MODIFY 1[cataloged-procedure-for-startup-name.
5 Messages This chapter describes the messages that are issued by P9000 mainframe agent. Message format This section describes the format of the messages that are issued by P9000 mainframe agent and the notations used in this manual. Message output format Each message issued by the P9000 mainframe agent consists of a message ID and the message text.
#2 A return code which is set when the message is output. The return code of a command contains the largest value of all return codes of messages output while the command was processing. #3 Details identifying specific items such as error locations, or copy pair numbers. #4 A character string enclosed in square brackets ([ ]) might be omitted.
Message ID Message text Explanation and actions 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 create a new configuration file that has correct file attributes. • RECFM = XX.
Message ID Message text Explanation and actions 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. 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.
Message ID YKT002E CON Message text Explanation and actions Can’t find IGCERROR The “IGCERROR” search in the NUCLKUP macro failed. The program abnormally terminates with user completion code 996. Contact Technical Support for assistance. YKT003E CON YKT004E CON No SVC #’s available Couldn’t add SVC entry No SVC number available. The program abnormally terminates with user completion code 996. SVC number addition failed in the SVCUPDTE macro.
Message ID Message text Explanation and actions YKT032E CON RC=20 The task is not APF-authorized. The dataset name of the P9000 mainframe agent 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. YKT098I CON RC=0 SVC routine is deleted The user SVC routine deletion succeeded.
Message ID YKY008I CON YKY016I CON Message text Explanation and actions INSUFFICIENT SPACE AVAILABLE FOR INITIALIZATION TASK(task-ID) ABENDED,CODE=completion-code Initialization parameters analysis failed due to a shortage of work space. The P9000 mainframe agent will be terminated. Check, and, if necessary, revise the specification of the user region in the job step in the P9000 mainframe agent startup cataloged procedure, correct the memory requirements, and then restart the P9000 mainframe agent.
Message ID Message text Explanation and actions The P9000 mainframe agent terminated abnormally. If the cause is unknown, collect the ABEND dump in the SYSABEND dump format and then contact customer support for investigation. YKY053I CON AGENT ABENDED YKY100I CON MODIFY COMMAND ACCEPTED The MODIFY command was accepted. YKY101I CON STOP COMMAND ACCEPTED The STOP command was accepted. After an entry of the MODIFY command, an error was detected in the command or operand shown as text.
Message ID Message text Explanation and actions 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 • LOCAL: Indicates that the TCP/IP session information for the local host is displayed. YKY131I CON host-type PORT=portnumber HOST=IP-address • REMOTE: Indicates that the TCP/IP session information for the remote host is displayed.
Message ID Message text Explanation and actions The request was received, but was denied. hh:mm:ss hh:mm:ss task-ID, YKY304I SYS REQUEST DENIED, REASON= (reason-for-denial) 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. The TCP connection was lost during TCP/IP processing for the reason shown as reason-for-disconnection.
Message ID Message text Explanation and actions 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 cancelled. If necessary, check the YKY330I message that was displayed immediately before this message to determine the cause of the error.
Message ID Message text Explanation and actions 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 P9000 mainframe agent. Once the error is corrected, start the TCP/IP program, and then start the P9000 mainframe agent.
Message ID Message text Explanation and actions The IRXJCL routine returned an error with the return code shown as return-code. The P9000 mainframe agent will terminate the processing. YKY604I CON IRXJCL MODULE ERROR,CODE=return-code 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 P9000 mainframe agent. Check, and, if necessary, revise JCL, and then re-execute. return-code • 20: Processing failed.
Message ID Message text Explanation and actions The IRXTERM routine returned an error with the indicated return code. The P9000 mainframe agent terminates the processing. Check the return code. return-code For details about the return code, see the TSO/E REXX Reference.
Message ID Message text Explanation and actions AGENT FUNCTION ABEND CODE=Sxxx Uxxxx DATE=yy-mm-dd TIME=hh:mm:nn The main task or subtask terminated abnormally during the P9000 mainframe agent processing. If the task cannot be recovered, the P9000 mainframe agent will be terminated.
Message ID Message text YKY705E XML End of request was detected in an element. YKY706E XML The number of elements exceeded the allowed limit. YKY707E XML The request version is a mismatch. YKY713E XML An invalid element ‘element-name’ was specified in the XML request. Explanation and actions The end of the XML request was detected in an element. Check, and, if necessary, revise the last element in the XML request. The number of element hierarchies exceeded the permitted maximum value (16).
Message ID Message text Explanation and actions A required parameter is missing in the element. YKY718E XML A required parameter is missing from the element ‘element-name’ of the request. ‘parametername’ Check, and, if necessary, revise the corresponding element specification in the request. element-name Element name parameter-name Name of the required parameter YKY719E XML There is a conflict with element ‘elementname’.
Message ID Message text Explanation and actions No copy pair was discovered in the specified range. YKY902I TSO No copy pair was discovered. Check the operating range and status of the copy pair that you want to acquire, and then execute the YKP2A command again. If the copy pair status is Simplex, the YKP2A command does not detect any copy pair. A parameter specification is invalid or missing. Check the following and then execute the command again.
Message ID YKY921W TSO Message text Explanation and actions No I/O paths are available for the specified devices. DEVN=Devn No copy pair information was acquired from the volume to which the device number Devn was assigned because no I/O paths are available. Verify the I/O path settings. Devn Device number of the volume whose information acquisition was skipped YKY999E TSO CON MFAgent cannot use this REXX exec library. A REXX script that cannot be used by P9000 mainframe agent was executed.
Message ID Message text Explanation and actions The command cannot be executed because a Core processing error occurred. message-text (string) Message text.
Message ID Message text Explanation and actions The internal program processing of YKP2A is starting. process (string) Processing name yyyy/mm/dd (string) GMT date YKZ208I TSO PRT The Core processing( process ) started. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy) hh:mm:ss.
Message ID Message text Explanation and actions The command cannot be executed because a NAME/TOKEN write error occurred. nnn (decimal number) Return code set by the NAME/TOKEN registration routine (IEANTCR) YKZ211E CON SC=40 A NAME/TOKEN write error occurred.
Message ID Message text Explanation and actions The command cannot be executed because a NAME/TOKEN delete error occurred. nnn (decimal number) Return code from the NAME/TOKEN registration routine (IEANTCR) YKZ250E TSO SC=40 A NAME/TOKEN delete error occurred.
Message ID Message text Explanation and actions P9000 mainframe agent failed to complete the requested processing. This device is skipped and processing continues. Check the status of the error device, and fix the problem in the configuration or execution condition if any. device-number-1 (string) The device that issued I/O device-number-2 (string) The device to be manipulated YKZ252E TSO SC=8 DASD device devicenumber-1(devicenumber-2) management error, messagetext.
Message ID Message text Explanation and actions An I/O error occurred. Processing will continue with this device skipped. If a sense byte is set, the sense byte is indicated in the YKZ255E message. When CC=3: The corresponding device might not be configured or connected. When CC=0 and CSW=xxxxxx0000xxxx (DSB=00, CSB=00): The corresponding device might not be configured or connected. When CC=0 and CSW=00000000060000: MIH might have occurred or a logical path might not be connected.
Message ID Message text Explanation and actions An I/O error occurred. P9000 mainframe agent might not support this device. Processing will continue with this device skipped. If a sense byte is set, the sense byte is indicated in the YKZ256E message. When CC=3: The corresponding device might not be configured or connected. When CC=0 and CSW=xxxxxx0000xxxx (DSB=00, CSB=00): The corresponding device might not be configured or connected.
Message ID Message text Explanation and actions Detailed information on the I/O error is displayed. device-number-1 (string) The device that issued I/O device-number-2 (string) The device to be manipulated YKZ255E TSO SC=32 (pair-index) DASD device devicenumber-1(devicenumber-2) sense: diagnostic-information (cmd=xxx, pos=yyy) If the device number of the device to be operated is not found, **** is displayed.
Message ID Message text Explanation and actions P9000 mainframe agent failed to complete the requested processing. Processing will continue with this device skipped. Check the status of the device involving the error, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and actions P9000 mainframe agent failed to complete the requested processing. P9000 mainframe agent might not support this device. Processing will continue with this device skipped. Check the status of the device involving the error, correct any errors related to the configuration or execution conditions, and then re-execute the command.
Message ID Message text Explanation and actions An error was detected in the REXX service. command Issued CLI command name rexx-service YKZ330E TSO RC=64 command detected the rexx-service service error. (return code=r[, reason code=n]) Name of the REXX service where an error was detected r (decimal number) Return code from the REXX service For details, see the TSO/E REXX User’s Guide. n (decimal number) Reason code from the REXX service For details, see the TSO/E REXX User’s Guide.
Message ID Message text Explanation and actions YKZ341E TSO RC=48 No DEVN() supplied. Nothing is assigned to the DEVN parameter. YKZ343E TSO RC=48 DEVN() value invalid. The value specified in the DEVN parameter is invalid. A dynamic change in an I/O configuration definition was detected during processing of the command. YKZ370E TSO SC=32 RC=32 A dynamic configuration change was detected during specified command processing.
Messages
6 Troubleshooting This chapter describes the troubleshooting of P9000 mainframe agent. Information output to logs P9000 mainframe agent connects and exchanges storage information with Device Manager via TCP/IP. If a communication line error or P9000 mainframe agent failure occurs while P9000 mainframe agent is running, error information is output to the Device Manager log.
Trigger of the log output Output information Output location Information output in the YKY315I message: Error detected during communication processing • Name of request during TCP/IP communication • Response code and event code • Local IP address: Local port number • Remote IP address: Remote port number No response after the response wait time was exceeded The YKY321I message is output.
When P9000 mainframe agent cannot be started The table below lists the events and actions to be taken when P9000 mainframe agent is unable to start. In the Event column, go down in the order listed and locate the first description that matches the event that is occurring, and then use the action in the Action column to solve the problem. Table 22 Events and what to do when P9000 mainframe agent cannot be started Event Action P9000 mainframe agent terminates with a system completion code (878).
Event Action A message other than those above is displayed. Take appropriate action according to the displayed message. P9000 mainframe agent terminates with a return code other than (00). Take appropriate action according to the return code. When information from P9000 mainframe agent is not updated The table below lists the events and actions to be taken when information is acquired by using P9000 Command View AE Suite product, but the information from P9000 mainframe agent is not updated.
7 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
• • • • • http://www.hp.com http://www.hp.com/go/storage http://www.hp.com/support/manuals http://www.hp.com/support/cvae/manuals http://www.hp.com/storage/spock Conventions This guide follows the conventions shown in Table 24 .
Product reference Full name or meaning VM Virtual Machine VTOC Volume Table Of Contents Replication Manager software HP StorageWorks P9000 Replication Manager software XML eXtensible Markup Language Mainframe Agent Installation and Configuration Guide 107
Support and other resources
A Command format Appendix A explains the symbols and syntax elements used in the syntax explanations of commands. Symbols used in command explanations The following table shows the symbols used in command explanations. Table 25 Symbols used in command explanations Font for symbol Convention Separator between multiple items, meaning "or". | (stroke) Example: "A|B|C" means "A, B, or C". Square brackets enclose an item whose specification is optional.
Syntax elements for parameters The following table lists the syntax elements for commands.
Glossary Glossary defines the terms used in this manual. AddHost command A Device Manager command used for registering mainframe hosts into Device Manager. AddHostRefresh command A Device Manager command used for refreshing mainframe storage information displayed on Device Manager GUI. AddURLLink command A Device Manager command used for registering P9000 mainframe agent in Device Manager. Asynchronous copy pair A function that creates and manages remote copies of volumes between storage systems.
GetURLLink command A Device Manager command used for acquiring P9000 mainframe agent registration information registered in Device Manager. host identification name A name specified to identify a mainframe when the volume information for multiple mainframe hosts is obtained. This name is specified by using the initialization parameter HOSTNAME of the P9000 mainframe agent.
secondary site A site with a recovery host and a storage system in a 2DC configuration. This is the destination for backup copies. To prevent both hosts from stopping simultaneously during a disaster, it should be some hundreds to some thousands of kilometers away from the primary host. serial number of storage system In XP1024/XP128 Seriess and XP12000/XP10000/SVS200, a serial number of storage system is a number assigned to each storage system (physical DKC serial number).
Glossary
Index A acquiring mainframe host information (Device Manager), 46 mainframe storage information (Device Manager), 44 P9000 mainframe agent information (Device Manager), 46 AddHost command, 111 notes on executing, 43 AddHostRefresh command, 111 AddURLLink command, 111 notes on executing, 44 Asynchronous copy pair, 111 C CANCEL command format, 66 glossary, 111 cataloged procedure for startup, 111 changing, 42 cataloged procedure library removing concatenation, 26 changing cataloged procedure for startup, 42
E EXEC statement, 41 F format YKALCSVC command, 21 G generating configuration files copy types and units, 54 GetURLLink command, 112 glossary, 111 H host identification name, 35 glossary, 112 HOSTNAME, 35 how to use SETINIT command, 31 HP StorageWorks P9000 for Business Continuity Manager software, 112 httpd.
overview using Device Manager to collect mainframe system storage information, 49 P P9000 Command View AE Suite products, 112 P9000 mainframe agent checking settings after upgrading, 26 installing, 17 operating procedure for changing the configuration, 51 operating procedure for installing, 50 overview, 11 purpose of installing, 11 registering, 43 setting up, 27 starting, 64 upgrading, 24, 26 using, 49 P9000 mainframe agent information (Device Manager) acquiring, 46 changing, 46 deleting, 46 parameters det
STOP command format, 65 glossary, 113 storage attributes library datasets, 19 supported PPRC commands, 55 suspend status, 113 SVC-number parameter YKALCSVC command, 22 symbols used in command explanations, 109 Synchronous copy pair, 113 SYSABEND DD statement, 42 SYSEXEC DD statement, 42 system configuration example, 13 SYSTSIN DD statement, 41 SYSTSPRT DD statement, 41 T troubleshooting, 101 when information from P9000 mainframe agent is not updated, 104 when P9000 mainframe agent cannot be started, 103 U
