HP XP7 Command View Advanced Edition Mainframe Agent Installation and Configuration Guide Part number: TK981-96005 First edition: April 2014
Legal and notice information © Copyright 2014 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 XP7 mainframe agent .............................................................. 11 Why use XP7 mainframe agent ? ................................................................................................ Installation requirements ............................................................................................................ Operating system requirements ..........
Setting the security .................................................................................................................... Setting the dataset security .................................................................................................. Setting up the Resource Access Control Facility (RACF) when linking with Replication Manager .......................................................................................................................... Setting up IBM HTTP Server ...
Copy types and units that can generate configuration files ................................................ Supported PPRC commands .......................................................................................... YKP2A command ............................................................................................................... Format ....................................................................................................................... Function ...........................
Documentation feedback ................................................................................................... 111 Related information ................................................................................................................. 111 Conventions ........................................................................................................................... 112 A Command format ...........................................................................
Figures 1 XP7 mainframe agent configuration with HP XP7 Command View Advanced Edition products ................................................................................................................ 13 2 Configuration for using Replication Manager 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 to monitor PPRC copy pairs ...................
Tables 1 Programs required to use XP7 mainframe agent .......................................................... 11 2 Datasets stored on the installation CD-ROM ................................................................ 18 3 Storage attributes of library datasets .......................................................................... 18 4 YKALCSVC command return codes list .......................................................................
Preface This guide provides information about HP XP7 Command View Advanced Edition mainframe agent (called XP7 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 XP7 mainframe agent.
Preface
1 About XP7 mainframe agent This chapter explains the purpose of XP7 mainframe agent. The chapter also lists XP7 mainframe agent installation requirements, and provides an example system configuration. Why use XP7 mainframe agent ? XP7 mainframe agent is a product you can use to display information about mainframe system storage on a GUI of Device Manager or Replication Manager.
Program name Required TSO/E REXX Required TSO/E Required Overview Description Standard OS component. IBM Library for REXX on zSeries Release 4 (FMID HWJ9140) or IBM Library for REXX on zSeries Alternate Library (FMID HWJ9143) Device Manager Replication Manager IBM HTTP Server for z/OS Prerequisite program for executing XP7 mainframe agent Required IBM Library for REXX on zSeries Alternate Library (FMID HWJ9143) is a Standard OS component.
Using Device Manager to view storage information XP7 mainframe agent and Device Manager can be linked so that storage information managed by the mainframe host can be displayed on a GUI. The following figure shows a configuration example for using Device Manager to view storage information managed by the mainframe host.
Figure 2 Configuration for using Replication Manager to monitor PPRC copy pairs The XP7 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 to monitor PPRC copy pairs” on page 55.
Figure 3 Configuration for using Device Manager to view storage information managed by the mainframe host and using Replication Manager to monitor PPRC copy pairs XP7 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 to monitor PPRC copy pairs” on page 55.
About XP7 mainframe agent
2 Installing XP7 mainframe agent This chapter provides an overview of installing XP7 mainframe agent, describes pre-installation checks, and explains the installation and upgrade procedures. Installation overview The following figure provides an overview of installing XP7 mainframe agent. Figure 4 Overview of installing XP7 mainframe agent Pre-installation checks This section describes the items that you need to check before installing XP7 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 XP7 mainframe agent) MFAGENT.Vnnnn.LINKLIB.XMIT LINKLIB Load module for XP7 mainframe agent MFAGENT.Vnnnn.LPALIB.
U: Unfixed record Memory requirements The following shows the memory requirements for using the XP7 mainframe agent. The amount of required memory is expressed in KB. Note that sections within the formula enclosed in upward arrows indicate values whose decimal components are to be rounded up.
Figure 5 Workflow of installing XP7 mainframe agent The following task outlines the installation of the XP7 mainframe agent. The numbers in the procedure correspond to the numbers in Figure 5. To install XP7 mainframe agent: 1. Insert the installation CD-ROM. 2. From the PC and using ASCII, transfer the following installation JCLs to a host machine: • JCL (YKAGALLO) for allocating space for the datasets on the CD-ROM that are to be transferred.
6. Extract objects and libraries to the space allocated for the execution datasets (execute the edited YKAGINST job). The YKAGINST job allocates the execution dataset space, and extracts the objects and libraries from the transfer dataset archives to the execution dataset space. Settings for using the YKALCSVC command The YKALCSVC command registers the user SVC, and is started by the OS START command. To use the YKALCSVC command: 1.
Return code Meaning 20 Processing stopped due to an error (the specified value or execution environment is invalid). Registering a user SVC You must use one of the following methods to register the user SVC: • Registration using the IEASVCxx parmlib member • Registration using the YKALCSVC command If you use the IEASVCxx parmlib member to perform registration, you must reload the system (that is, perform an initial program load (IPL)).
Using the YKALCSVC command to register The following shows how to execute the YKALCSVC command. For details on the format of the YKALCSVC command, see “Settings for using the YKALCSVC command” on page 21. When the system starts or before you use XP7 mainframe agent, execute the YKALCSVC command to register a user SVC. Execute the command as follows with the SVC number specified: START YKALCSVC,PARM='SVC-number' An error is returned if another user SVC is already assigned to the SVC number specified here.
Settings for using the YKP2A command XP7 mainframe agent provides the YKP2A command, which is one of the TSO/E commands. To use the YKP2A command in a TSO/E environment: 1. Link EXECLIB (REXX Exec library) to the SYSEXEC dd name. 2. Link LINKLIB (load library) to the TSOLIB dd name. Upgrading XP7 mainframe agent This section explains how to upgrade XP7 mainframe agent. Notes for upgrading If you upgrade XP7 mainframe agent from version 5.7 or earlier to version 6.
Pre-upgrade procedure Deleting the user SVC When you upgrade the XP7 mainframe agent, you must delete the user SVC of an earlier XP7 mainframe agent version before installing the new version. If the user SVC was registered by using the YKALCSVC command, use the YKALCSVC command to delete the user SVC. If the user SVC was registered by using the IEASVCxx parmlib member, you cannot use the YKALCSVC command to delete the user SVC. Instead, you must complete the following procedure.
Installing XP7 mainframe agent
3 Setting up XP7 mainframe agent This chapter explains how to set up the environment to acquire storage information using the XP7 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. For a job that starts the XP7 mainframe agent, set the UNIX service's usage attributes (open a port for receiving). For details, refer to the Communications Server: IP Configuration Reference.
Setting the dataset security When an XP7 mainframe agent is linked to Replication Manager, the XP7 mainframe agent job references the XP7 mainframe agent's configuration files. Therefore, be sure to grant the XP7 mainframe agent job READ permission for the configuration files that are accessed by the XP7 mainframe agent job.
To improve the execution performance of the XP7 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 XP7 mainframe agent is disabled.
Directive to be specified Description of directive, and values to be specified Specify the following options to set up XP7 mainframe agent to act as the origin server for Device Manager or Replication Manager: • The host name or IPv4 address of the host that is running XP7 mainframe agent ProxyPass and ProxyPassReverse • The port number that was specified for the PORT parameter when initially setting up XP7 mainframe agent The following example shows how to specify the options: ProxyPass / http://host-na
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 XP7 mainframe agent.
HOSTNAME('host-identification-name') ~ <1 to 50 alphanumeric characters> <> Specify this parameter when Device Manager or Replication Manager needs to identify the XP7 mainframe agent. When the XP7 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 cannot identify the host on which the target XP7 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), XP7 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 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 XP7 mainframe agent to Device Manager in the configuration shown in Figure 7, specify the values shown in the following table. Table 10 Settings to be specified to connect to Device Manager Local site Remote site Level of the log data to be output Port number 2 24042 Device number 7300 to 730F No specification 7400 to 740F The following shows an example of specifying the settings shown in Table 10 for initialization parameters.
When connecting to Replication Manager This subsection explains how to specify initialization parameters when connecting XP7 mainframe agent to Replication Manager. The following example configuration is used to explain the specification method. Figure 8 Example configuration for connecting to Replication Manager To connect XP7 mainframe agent to Replication Manager 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 XP7 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 XP7 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, 2014, 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 XP7 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.
capacityInKB=0 hostType=2 managedBy=2 statusOfDBUpdating=-1 *****: The value is encoded by the CLI. Registering the XP7 mainframe agent running on the mainframe host in Device Manager To use the AddURLLink command to register the mainframe host in Device Manager: 1. Execute the AddURLLink command to register the XP7 mainframe agent running on the mainframe host in Device Manager.
hdvmcli AddURLLink "url=http://IBM-HTTP-Server-IP-address#:port-number" "name=MainframeAgent" "linkedid=mainframe-host-object-ID" # Enclose the IP address in square brackets ([ and ]). Example of executing the command (for an IPv4 environment): hdvmcli AddURLLink -o "D:\logs\AddURLLink.log" "url=http://192.168.99.114:24042" "name=MainframeAgent" "linkedid=*****" *****: The value is encoded by the CLI.
hdvmcli AddHostRefresh "objectid=mainframe-host-object-ID" Example of executing the command: hdvmcli AddHostRefresh -o "D:\logs\AddHostRefresh.log" "objectid=*****" *****: The value is encoded by the CLI. Example of output from executing the command: RESPONSE: An instance of Host objectID=***** name=toro2 hostID=1 capacityInKB=0 hostType=2 managedBy=2 sysplexID=RSDPLEX statusOfDBUpdating=-1 *****: The value is encoded by the CLI.
hdvmcli AddHostRefresh "objectid=mainframe-host-object-ID" Example of executing the command: hdvmcli AddHostRefresh -o "D:\logs\AddHostRefresh.log" "objectid=*****" *****: The value is encoded by the CLI. Example of output from executing the command: RESPONSE: An instance of Host objectID=***** name=toro2 hostID=1 capacityInKB=0 hostType=2 managedBy=2 sysplexID=RSDPLEX statusOfDBUpdating=-1 *****: The value is encoded by the CLI.
Changing XP7 mainframe agent information registered in Device Manager To change XP7 mainframe agent information registered in the Device Manager server, use the AddURLLink command. You can change the IP address or port number of the mainframe host by specifying a new IP address or port number in the url parameter in URL format. Note: In the name parameter, specify MainframeAgent.
Acquiring mainframe host information To acquire information about a mainframe host registered in the Device Manager server (such as the host name), use the GetHost command. Note: If you do not know the object ID of a mainframe host, use the following procedure to acquire the object ID. 1. Execute the GetHost command with no object ID specified to acquire a list of hosts registered in Device Manager. 2. In the displayed host information, find the name of the mainframe host you are looking for. 3.
hdvmcli ModifyHost -o "D:\logs\ModifyHost.log" "objectid=*****" "hostname=snow" *****: The value is encoded by the CLI. Example of output from executing the command: RESPONSE: An instance of Host objectID=***** name=snow hostID=1 capacityInKB=0 hostType=2 managedBy=2 sysplexID=RSDPLEX statusOfDBUpdating=-1 *****: The value is encoded by the CLI. Deleting a mainframe host To delete a mainframe host registered in the Device Manager server, use the DeleteHost command.
• IP address or host name of XP7 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. Setting the interval for collecting copy pair status information Specify the interval for collecting copy pair status information, in minutes. If you do not want copy pair status information to be collected automatically, disable the setting for periodic refresh.
Setting up XP7 mainframe agent
4 Using XP7 mainframe agent This chapter explains how to link with Device Manager and Replication Manager 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 XP7 mainframe agent To install XP7 mainframe agent: 1. See the following sections to set up the XP7 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 XP7 mainframe agent. see “Starting XP7 mainframe agent” on page 68. 3. When connecting to Device Manager by using IPv6, set up IBM HTTP Server.
Figure 11 Operating procedure for changing the configuration of XP7 mainframe agent To change the configuration of XP7 mainframe agent: 1. Stop information collection by Device Manager. 2. Stop XP7 mainframe agent. see “Stopping XP7 mainframe agent” on page 69. 3. Correct the initialization parameter. see “Creating initialization parameters” on page 31. 4. Start XP7 mainframe agent. see “Starting XP7 mainframe agent” on page 68. 5. Restart information collection by Device Manager.
Figure 12 Overview of operation in which Replication Manager 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 XP7 mainframe agent are required. The YKP2A command is used to create configuration files for XP7 mainframe agent.
Figure 13 Monitoring PPRC copy pairs using Replication Manager 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” on page 28. 3. Use the YKP2A command to scan for storage systems that contain primary volumes of PPRC copy pairs, and generate disk configuration files and copy group definition files. 4.
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 115.
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.
• When the YKP2A command is executed, and information is requested from Replication Manager, an error might occur in Replication Manager, which prevents the collection of information. In this case, collect the information for the next request (at the set interval for Replication Manager). 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.
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 XP7 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 XP7 mainframe agent To start XP7 mainframe agent, use the START command. XP7 mainframe agents reside on the system, and run in accordance with the definition of the YKPRMxx initialization parameter. You can start multiple XP7 mainframe agents.
START YKAGENTD.YK,MEMBER=YKPRM10,SYSOUT=X Stopping XP7 mainframe agent To stop XP7 mainframe agent, use the STOP command. If a request from another HP XP7 Command View Advanced Edition 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 XP7 mainframe agent return codes when an agent is stopped.
Example To forcibly stop an XP7 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 XP7 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 XP7 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 XP7 mainframe agent. Message format This section describes the format of the messages that are issued by XP7 mainframe agent and the notations used in this manual. Message output format Each message issued by the XP7 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 recreate 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 Message text Explanation and actions dsstate Status of the configuration file • 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 whose format is VSAM cannot be used as a configuration file. Change the dataset format of the configuration file into PS.
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 XP7 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 deletion succeeded.
Message ID YKY008I CON Message text INSUFFICIENT SPACE AVAILABLE FOR INITIALIZATION Explanation and actions Initialization parameters analysis failed due to a shortage of work space. The XP7 mainframe agent will be terminated. Check, and, if necessary, revise the specification of the user region in the job step in the XP7 mainframe agent startup cataloged procedure, correct the memory requirements, and then restart the XP7 mainframe agent.
Message ID Message text Explanation and actions The XP7 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 XP7 mainframe agent. Once the error is corrected, start the TCP/IP program, and then start the XP7 mainframe agent.
Message ID Message text Explanation and actions The IRXJCL routine returned an error with the return code shown as return-code. The XP7 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 XP7 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 XP7 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 XP7 mainframe agent processing. If the task cannot be recovered, the XP7 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 No I/O paths are available for the specified devices. DEVN=Devn Explanation and actions 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 XP7 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 XP7 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.
Message ID Message text Explanation and actions An I/O error occurred. XP7 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 XP7 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. device-number-1 (string) The device that issued I/O device-number-2 (string) The device to be manipulated If the device number of the device to be operated is not found, **** is displayed.
Message ID Message text Explanation and actions XP7 mainframe agent failed to complete the requested processing. XP7 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 YKZ301E CON RC=128 Message text The task is not authorized to execute the request. (reason code=reason) Explanation and actions The task is not authorized to execute XP7 mainframe agent or the YKP2A command. If this message is displayed, XP7 mainframe agent will not send storage information to the HP XP7 Command View Advanced Edition products.
Message ID Message text Explanation and actions An abnormal system termination was detected during the REXX service processing. command Issued CLI command name YKZ332E TSO RC=64 command detected the system abend during rexx-service processing. (code=sss, reason=rrrr) rexx-service Name of the REXX service where the abnormal system termination was detected sss (hexadecimal number) System completion code For details, see the MVS System Codes.
User completion codes The following table provides details about the user completion codes. Table 20 User completion codes Completion codes Explanation The user does not have the permission to execute XP7 mainframe agent.
Messages
6 Troubleshooting This chapter describes the troubleshooting of XP7 mainframe agent. Information output to logs XP7 mainframe agent connects and exchanges storage information with Device Manager via TCP/IP. If a communication line error or XP7 mainframe agent failure occurs while XP7 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 XP7 mainframe agent cannot be started The table below lists the events and actions to be taken when XP7 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 XP7 mainframe agent cannot be started Event Action XP7 mainframe agent terminates with a system completion code (878).
Event Action XP7 mainframe agent terminates with a return code other than (00). Take appropriate action according to the return code. When information from XP7 mainframe agent is not updated The table below lists the events and actions to be taken when information is acquired by using HP XP7 Command View Advanced Edition product, but the information from XP7 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.
Conventions This guide follows the conventions shown in Table 24.
Product reference Full name or meaning XML eXtensible Markup Language XP7 HP XP7 Storage Installation and Configuration Guide 113
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 XP7 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 XP7 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 XP7 mainframe agent.
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), 49 XP7 mainframe agent information (Device Manager), 47 AddHost command, 117 notes on executing, 43 AddHostRefresh command, 117 AddURLLink command, 117 notes on executing, 44 Asynchronous copy pair, 117 C CANCEL command format, 70 glossary, 117 cataloged procedure for startup, 117 changing, 42 cataloged procedure library removing concatenation, 25 changing cataloged procedure for startup, 42 log output level, 72 mainframe host information (Devi
F format YKALCSVC command, 21 G generating configuration files copy types and units, 58 GetURLLink command, 118 glossary, 117 H host identification name, 35 glossary, 118 HOSTNAME, 35 how to use SETINIT command, 31 HP XP7 Business Continuity Manager, 118 HP XP7 Command View Advanced Edition products, 118 httpd.
PPRC inner-DKC asynchronous copy pair configuration example for monitoring, 66 PPRC Synchronous and Asynchronous copy pairs configuration example for monitoring, 65 PPRC Synchronous and inner-DKC asynchronous copy pair configuration example for monitoring, 67 pre-installation checks, 17 pre-upgrade procedure, 25 PREFIX, 35 prerequisite equipment, 12 prerequisite hardware, 58 Prerequisites for the Copy Group Definition Generation Function, 58 primary site, 118 PROC statement, 41 PROFILE.
upgrading checking before upgrading, 24 deleting user SVC, 25 notes, 24 removing concatenation of cataloged procedure libraries, 25 removing concatenation of load libraries, 25 XP7 mainframe agent, 25 user SVC deleting, 25 registering, 22 user SVC number checking, 24 using Device Manager to collect mainframe system storage information, 53 V VOLSER, 119 W when connecting Device Manager, 37 Replication Manager, 39 X XP7 mainframe agent checking settings after upgrading, 25 installing, 17 operating procedur
