Tables

Table 1 Revisions..... 7 Table 2 Document conventions..... 7 Table 3 Conventions: Abbreviations..... 8 Table 1-1 Programs required to use mainframe agent.... 10 Table 2-1 Storage attributes.... 16 Table 2-2 Datasets stored on the installation CD.... 17 Table 2-3 YKALCSVC command return codes list.... 21 Table 2-4 Library for which the dataset concatenation must be removed before installation. 23 Table 3-1 Continuation symbols..... 27 Table 3-2 Whether the initialization parameter can be specified more than once... 28 Table 3-3 LOGLEVEL specification and the output messages... 31 Table 4-1 Pair Format command (CESTPAIR).... 47 Table 4-2 Pair Suspend Command (CSUSPEND).... 48 Table 4-3 Pair Resynchronization command (CESTPAIR).... 48 Table 4-4 Return codes when mainframe agent ends.... 54 Table 5-1 User completion codes.... 81 Table 6-1 Information output to logs.... 82 Table 6-2 Events and actions to be taken when mainframe agent cannot be started.. 84 Table 6-3 Events and actions to be taken when information from mainframe agent is not updated.. 85 Table A-1 Symbols used in command explanations.... 86 Table A-2 Command syntax elements..... 86
This guide provides information about HP StorageWorks XP Command View Advanced Edition mainframe agent (called mainframe agent throughout), including the following tasks:
Installing, setting up, starting, and stopping Troubleshooting and messages

Revision history

Table 1 Revisions Date

May, 2008

Edition

Revision

Initial release

Intended audience

This manual is intended for system administrators who install, set up, operate, or troubleshoot mainframe agent. This manual assumes that the reader has the following:
A basic knowledge of communications A basic knowledge of the operating system on which mainframe agent is installed (OS/390 or z/OS) A knowledge of HP StorageWorks XP Command View Advanced Edition software For linkage with HP StorageWorks XP Replication Manager software, knowledge of HP StorageWorks XP Replication Manager software
Document conventions and symbols
Table 2 Document conventions Convention Element Blue text
Blue, underlined text Bold text

Convention Element

Cross-reference links and e-mail addresses Web site addresses Key names Text typed into a GUI element, such as into a box GUI elements that are clicked or selected, such as menu and list
italics text Monospace text
Text emphasis File and directory names System output Code Text typed at the command-line Code variables Command-line variables

Monospace, italic text

Table 2 Document conventions Convention Element

Monospace, bold text

Ensure that DNS can resolve the host name you specify. If a host name that DNS can resolve is identical to a host name already managed by Device Manager, set the host identification name of the mainframe host for the HOSTNAME parameter, and then set the same host identification name in Device Manager. If neither of the above methods allows you to set a unique host name, change the host name of the host managed by Device Manager. If none of the above three methods allows you to set a unique host name, you can specify any host name.
PREFIX(prefix,local-site's-DADID) Specifies the prefix when information about mainframe agent is to be acquired from XP Replication Manager. Specify the prefix of the configuration file created by the YKP2A command. For details about the YKP2A command, see section 4-2-4. You can specify multiple PREFIX parameters. Specify multiple PREFIX parameters when the storage information to be acquired is information registered in multiple configuration files that have different prefixes, in an environment where XP Replication Manager and mainframe agent are oneto-one. prefix ~ <PREFIX character string consisting of 1 to 16 characters> Specifies the prefix of the configuration file name of mainframe agent that is provided to XP Replication Manager. The disk configuration definition file with the prefix specified here, the volume information defined in the copy group definition file, and the copy group are provided to XP Replication Manager. local-site's-DADID ~ <DAD character string consisting of 1 to 28 characters> Specify the DADID of the primary site specified for the DAD parameter of the YKP2A command. Notes about specifying the PREFIX parameter
Do not specify a nonexistent prefix or DADID in the PREFIX parameter. Even though
specifying a nonexistent prefix or DADID does not result in an error during mainframe agent startup, an error will occur during an XP Replication Manager request.
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), mainframe agent processing might slow down.
Do not define multiple PREFIX parameters in which the same prefix has been specified. If

Output messages

No output YKY300I, YKY301I, YKY304I, and YKY307I YKY300I, YKY301I, YKY304I, YKY307I, and YKY680I
3-3-3 Usage examples of initialization parameters
This subsection provides usage examples of initialization parameters for linking to Device Manager or XP Replication Manager. This example specifies the operating environment below. The following shows a configuration example for when the operating environment is set as follows:
Level of the log data to be output: 2 Connection port number: 24042 Prefix: ACCOUNT, INFO Local DADID of the prefix ACCOUNT: NY Local DADID of the prefix INFO: NY Device number on the DKC side whose prefix is ACCOUNT: X'7300' to X'730F' Device number on the DKC side whose prefix is INFO: X'7400' to X'740F'
Figure 3-1 Configuration example for connecting to Device Manager The following shows a specification example for connecting to Device Manager in the Figure 3-1 operating environment: SETINIT LOGLEVEL(2) SETINIT PORT(24042) /* DEVN */ SETINIT DEVN(7300,730F) SETINIT DEVN(7400,740F)
Figure 3-2 Configuration example for connecting to XP Replication Manager The following shows a specification example for connecting to XP Replication Manager in the Figure 3-2 operating environment: SETINIT LOGLEVEL(2) SETINIT PORT(24042) /* PREFIX */ SETINIT PREFIX('ACCOUNT','NY') SETINIT PREFIX('INFO','NY') /* DEVN */ SETINIT DEVN(7300,730F) SETINIT DEVN(7400,740F)
3-3-4 Examples of initialization parameter analysis results
When mainframe agent starts, the initialization parameter analysis result 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 mainframe agent version.
Result list with no error
*** AGENT nn-nn LISTING INFORMATION *** SETINIT PORT(24042) /* DEVN */ SETINIT DEVN(7300,730F) SETINIT DEVN(7400,740F) DATE=2006-02-03 TIME=13:34:35 PAGE=00040001
Result list with an error This example indicates an error due to the missing end device number that is required for the first DEVN parameter. The YKY002I message is displayed.
*** AGENT nn-nn LISTING INFORMATION *** SETINIT PORT(24042) /* DEVN */ SETINIT DEVN(7300) YKY002I INVALID INITIALIZATION PARAMETER: DEVN SETINIT DEVN(7400,740F) 00040001 DATE=2005-07-11 TIME=16:09:53 PAGE=00020001 00030003

3-5-1-3 Acquiring mainframe storage information
Use the AddHostRefresh command to acquire mainframe storage information. The acquired information is not included in the command execution results. Use Web Client to check this information. 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 mainframe agent is operating normally. If it is not operating normally, check the mainframe agent settings, and restart mainframe agent. 2. Check whether the mainframe host and mainframe agent are registered correctly. If they are registered correctly, use the AddHostRefresh command to acquire the mainframe storage information again. If they are not registered correctly, register them correctly using the procedures described in section 3-5-1-1 or section 3-5-1-2. Command format: hdvmcli AddHostRefresh "objectid=mainframe-host-object-ID" Example of executing the command: hdvmcli AddHostRefresh -o "D:\logs\AddHostRefresh.log" "objectid=HOST.1" Example of command output: RESPONSE: An instance of Host objectID=HOST.1 name=toro2 capacityInKB=0 hostType=2 sysplexID=RSDPLEX
3-5-2 Refreshing mainframe storage information
To refresh the mainframe storage information displayed in Web Client, use the AddHostRefresh command. This command is the only means of refreshing the mainframe storage information. When you execute the command, specify the following parameter: 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 mainframe agent is operating normally. If it is not operating normally, check the mainframe agent settings, and restart mainframe agent. 2. Check whether the mainframe host and mainframe agent are registered correctly. If they are registered correctly, use the AddHostRefresh command to acquire the mainframe storage information again. If they are not registered correctly, register them correctly using the procedures described in section 3-5-1-1 or section 3-5-1-2. Command format: hdvmcli AddHostRefresh "objectid=mainframe-host-object-ID" 38
Setting up mainframe agent Example of executing the command: hdvmcli AddHostRefresh -o "D:\logs\AddHostRefresh.log" "objectid=HOST.1" Example of command output: RESPONSE: An instance of Host objectID=HOST.1 name=toro2 capacityInKB=0 hostType=2 SysplexID=RSDPLEX
3-5-3 Acquiring mainframe agent information registered in the Device Manager
To acquire 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.HOST.1.1" Example of command output: RESPONSE: An instance of URLLink objectID=URLLINK.HOST.1.1 name=MainframeAgent url=http://192.168.99.114:24042 linkedID=HOST.1

3-5-4 Changing mainframe agent information registered in the Device Manager
To change 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. If the name parameter is specified incorrectly, it is not registered as mainframe agent information, and mainframe storage information cannot be acquired. If you specified the name parameter incorrectly, use the DeleteURLLink command to delete the mainframe agent information, and then use the AddURLLink command to correct the registered mainframe agent information. Example of executing the command: hdvmcli AddURLLink -o "D:\logs\AddURLLink.log" "url=http://192.168.99.100:24042" "name=MainframeAgent" "linkedid=HOST.1" Example of command output: RESPONSE: 39
Setting up mainframe agent An instance of URLLink objectID=URLLINK.HOST.1.1 name=MainframeAgent url=http://192.168.99.100:24042 linkedID=HOST.1
3-5-5 Deleting mainframe agent information registered in the Device Manager
To delete mainframe agent information registered in the Device Manager server, use the DeleteURLLink command. NOTE: Use this command when you want to delete only mainframe agent registration information. For example, you may want to execute the command if you specified the name parameter incorrectly. Example of executing the command: hdvmcli DeleteURLLink -o "D:\logs\DeleteURLLink.log" "objectid=URLLINK.HOST.1.1" Example of command output: RESPONSE: (Command completed; empty list returned)
3-5-6 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 all hosts registered in Device Manager. 1 In the displayed host information, find the name of the mainframe host you are looking for. 2 Acquire the object ID based on the information related to the mainframe host you found in step 2.

3-6-3 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.
This chapter explains how to use mainframe agent to acquire storage information.
Using Device Manager to collect mainframe system storage information (see section 4-1 ) Using XP Replication Manager to monitor PPRC copy pairs (see section 4-2 ) Operation commands (see section 4-3 )
4-1 Using Device Manager to collect mainframe system storage information
This section describes how to use Device Manager to collect mainframe system storage information.

4-1-1 Operation overview

When you execute information collection for Device Manager, mainframe agent collects storage information managed by mainframe hosts, and then provides this information to Device Manager. Figure 4-1 provides an overview of mainframe agent operation.
Figure 4-1 Overview of mainframe agent operation
4-1-2 Operating procedure during installation
Figure 4-2 shows the operating procedure when installing mainframe agent.
Figure 4-2 Operating procedure during installation
4-1-3 Operating procedure for changing a configuration
Figure 4-3 shows the operating procedure when changing the mainframe agent configuration.
Figure 4-3 Operating procedure when changing the configuration
4-2 Using XP Replication Manager to monitor PPRC copy pairs
This section describes how to use XP Replication Manager to monitor PPRC copy pairs.

4-2-1 Operation overview

When a request for information from XP Replication Manager is received, the following PPRC copy pair information is provided by XP Replication Manager, based on the mainframe agent:
Host volume information Copy group definition information Statuses of copy pairs defined in the copy group
The following figure gives an overview of operation in which XP Replication Manager is used to monitor PPRC copy pairs.
Figure 4-4 Overview of an operation in which XP Replication Manager is used to monitor PPRC copy pairs
Device information on the secondary volume of a PPRC copy pair cannot be displayed because the information cannot be acquired from the local DKC. n/a is displayed.
4-2-2 Operation procedures

To moniotr PPRC copy pairs, use the copy group definition generation function to create a configuration file. The YKP2A command is used to define copy groups. To monitor PPRC copy pairs using XP Replication Manager:
1. Make sure that copy pairs are running in PPRC. 2. Set the security. For details, see section 3-2-2. 3. Use the YKP2A command to scan for DKCs with PPRC copy pairs, and generate disk configuration definition files and copy group definition files. 4. Set up the mainframe agent environment. See Chapter 3. 5. Start mainframe agent. See section 4-3-1. 6. Set up the XP Replication Manager environment. See section 3-6. 7. Start monitoring PPRC copy pair statuses in XP Replication Manager.
4-2-3 Prerequisites for the copy group definition generation function
The following shows the prerequisites for using the copy group definition generation function.
4-2-3-1 Prerequisite hardware

1 machine is required.

DKC for XP12000/XP10000 or XP24000/XP20000 for which PPRC copy pairs are running.
4-2-3-2 Software settings

Copy pair

Use PPRC to put synchronous pairs and asynchronous pairs in operating status (DUPLEX or suspend (SUSPOP) status).
If the status of a PPRC copy pair is SIMPLEX, no copy group definition file is generated.
4-2-3-3 Copy types and units for a copy group definition
The following table shows the copy types and units for a copy group definition for which copy group definitions can be generated. Type of copy pair Unit for copy group definition generation
Synchronous pair One of all searched copy pairs1 Asynchronous pair By C/T groupTo define a copy group for each DKC in a synchronous pair, split the device number specification range for each DKC. 2 This is a group based on the function for preserving the consistency of volume update order, as provided by the DKC. C/T groups can be used to preserve the update order of volumes contained within.
4-2-3-4 Supported PPRC commands
The following explains the PPRC commands supported for the copy group definition generation function. The following shows the legend for the table. Legend: Yes: The PPRC copy pairs operated by a PPRC command with this parameter value are supported. No: The PPRC copy pairs operated by a PPRC command with this parameter value are not supported. _ (Underscore): Indicates the default value of the parameter. Table 4-1 Pair Format command (CESTPAIR) Type of copy pair

Synchronous pair

Parameter MODE PACE

Value COPY NOCOPY pace

Omitted

Status

Yes No No Yes No Yes

YES NO

Using mainframe agent Table 4-1 Pair Format command (CESTPAIR) Type of copy pair Parameter MSGREQ Value YES NO

Asynchronous pair

No Yes Yes No Yes No No Yes No Yes No Yes

cmd_parm

AGnnX AVnnX

LAST data-direction-type TIME=YYYY/MM/DD hh:mm:ss
This message displays the last transmission or reception time in the corresponding TCP/IP session. data-direction-type SEND: Indicates the last transmission time. RECV: Indicates the last reception time. YYYY/MM/DD hh:mm:ss Time (local time) The TCP connection request was accepted. Information about the communication with the remote host is displayed in the YKY307I message. hh:mm:ss Message output time (local time) task-ID Number used to identify the processing task that output the message The TCP connection was released successfully. hh:mm:ss Message output time (local time) task-ID Number used to identify the processing task that output the message The request was received, but was denied. hh:mm:ss Message output time (local time) task-ID Number used to identify the processing task that output the message reason-for-denial INVALID FORMAT: The format is invalid. VERSION MISMATCH: The version does not match. The TCP connection was lost during TCP/IP processing for the reason shown as reasonfor-disconnection. Determine the cause of disconnection from the remote host. task-ID Number used to identify the processing task that output the message reason-for-disconnection FIN ACCEPT: A disconnection request (TCP-FIN) from the remote host was received. RST ACCEPT: A disconnection request (TCP-RST) from the remote host was received. The TCP connection request was accepted. Take appropriate action according to the message that was displayed before this message. hh:mm:ss Message output time (local time)

YKY300I SYS

hh:mm:ss task-ID,TCP CONNECTION ACCEPTED

YKY301I SYS

hh:mm:ss task-ID,TCP CONNECTION ENDED NORMALLY

YKY304I SYS

hh:mm:ss task-ID,REQUEST DENIED,REASON=(reasonfor-denial)

YKY305I CON

task-ID,TCP CONNECTION LOST DURING EVENT PROCESSING,TCPSTATUS=(reason-fordisconnection)

YKY307I SYS

hh:mm:ss task-ID,TCP CONNECTION INFORMATION,REMOTEHOST=IP-address,REMOTEPORT=remote-portnumber,LOCAL-PORT=localport-number
task-ID Number used to identify the processing task that output the message IP-address IP address of the remote host remote-port-number Port number of the remote host local-port-number Port number of the local host 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. task-ID Number used to identify the processing task that output the message request-name @OPNSAP: Preprocessing @OPEN: Processing for establishing a connection @SEND: Send processing @RECV: Receive processing @CLOSE: Processing for releasing the connection @QUERY: Remote address search processing @ABORT: Forcibly releasing the connection

YKZ209I TSO PRT

The Core processing( process ) ended. (DATE=yyyy/mm/dd, TIME=hh:mm:ss.th, TOD=ttt, cmd=xxx, pos=yyy)

YKZ211E CON SC=40

A NAME/TOKEN write error occurred. (return code=nnn, name= name, cmd=xxx, pos=yyy)

YKZ212W CON#

A FREEMAIN error occurred. (return code=nnn, cmd=xxx, pos=yyy)
when the log and trace are obtained, the YKZ212W message is not output to the console, but is recorded in LOG and TRACE. Processing will then continue. A LOAD macro error occurred. nnn (decimal number) Return code from the LOAD macro mmm (decimal number) Reason code from the LOAD macro (maintenance information) name (string) Load module name xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information The command cannot be executed because a NAME/TOKEN delete error occurred. nnn (decimal number) Return code from the NAME/TOKEN registration routine (IEANTCR) name (string) Name to be registered in the NAME/TOKEN service xxx (decimal number) Command code of the command that was executing when the error occurred See the command code description in the explanation of the YKZ201E message. yyy (string) Maintenance information Mainframe agent failed to complete the requested processing. Processing will continue with this device skipped. Check the status of the error device, 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-text (string) Message text code1 (Hexadecimal number) Subcommand code code2 (Hexadecimal number) Error code (maintenance information)

YKZ219W CON

A LOAD error occurred. (return code=nnn, reason code=mmm, name=name, cmd=xxx, pos=yyy)

YKZ250E TSO SC=40

Information Output to Logs (see section 6-1 ) Troubleshooting (see section 6-2 )
6-1 Information output to logs
Mainframe agent connects via TCP/IP and exchanges storage information with Device Manager. If a communication line error or mainframe agent failure occurs while mainframe agent is running, error information is output to the Device Manager log. However, since the error is detected after Device Manager issues a request, the output of error information might be delayed for some time after the actual error occurrence. Also, if an error occurs when mainframe agent attempts to acquire storage information, that storage information and the error information will not be displayed in the Device Manager window. If this happens, check the contents of the collected log. Table 6-1 shows the information that mainframe agent outputs to logs. Table 6-1 Information output to logs Trigger of the log output
Reception of a request to establish a TCP connection

Output information

Information output in the YKY300I or YKY307I message: Message output time, when the connection request was received Remote host's IP address Remote host's port number Local host's port number Information output in the YKY301I message: Message output time, when the connection was released Information output in the YKY304I message: Message output time, when the request was denied Reason for denial

Output location

SYSLOG
Normal release of a TCP connection
Denial of a connection request
Error detected during information Information output in the YKY680I message: acquisition Time of message output when the command is executed Command name Command return code Forced release of a TCP connection Information output in the YKY305I message: Reason for release Console
Table 6-1 Information output to logs Trigger of the log output
Error detected during communication processing
Information output in the YKY315I message: Name of request during TCP/IP communication Response code and event code Local IP address: Local port number Remote IP address: Remote port number The YKY321I message is output. Information output in the YKY330I message: Request type Return code and error number for request identification See the Communications Server: IP API Guide. Information output in the YKY362I message: Remote IP address and remote port number Information output in the YKY699I message: System completion code when the task terminated abnormally User completion code when the task terminated abnormally# Date and time the task terminated abnormally Information on system status when the abnormal termination occurred (register contents, module information, PSW, instruction length, interrupt code)

--ABC, ABC.DEF

<DAD string>

ABC, ABC.DEF

<Copy group name string>

Glossary

Glossary term AddHost command AddHostRefresh command AddURLLink command C/T group CANCEL command configuration file Definition A Device Manager command used for registering mainframe hosts into Device Manager. A Device Manager command used for refreshing mainframe storage information displayed on Device Manager Web Client. A Device Manager command used for registering mainframe agent into Device Manager. Consistency group. A C/T group preserves consistency in the update sequence when updating volumes in the group. A command to forcibly stop the mainframe agent. A generic name that refers to copy group definition files, disk configuration definition files, command device definition files, route list definition files, and path set definition files. A group of several pair volumes used for the same operation. The status of a P-VOL and S-VOL copy pair. Example: SIMPLEX, DUPLEX, SUSPOP, PENDING DAD Device Address Domain. Indicates sites that adopt the same device numbering system. If several hosts on the same site have the same device numbering system, they have the same name. A Device Manager command used for deleting mainframe hosts registered in Device Manager. A Device Manager command used for deleting mainframe agent registration information registered in Device Manager. The base program for storage management. Device Manager can integrate storage operations and management functions. A device number used by a mainframe host to manage storage volumes. A number assigned to each disk subsystem. A Device Manager command used for acquiring mainframe agent registration information registered in Device Manager. A program used for building a highly reliable backup system in which multiple data centers are linked together. This program enables operations to continue, by using the copy functionality of the disk subsystems, even if a disaster occurs and also enables you to minimize the restoration time or data loss from a disaster. 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 mainframe agent. A parameter used for setting up the environment of the mainframe agent at the startup of the agent. The following settings are available by using this parameter: port number, reception wait time, host identification name, device number, and log output level. A cataloged procedure to start JES (Job Entry Subsystem).

primary site

ModifyHost command RACF REXX

REXX alternate library

secondary site

SETINIT command

START command startup cataloged procedure STOP command suspend status VOLSER XP Command View AE Suite products XP Continuous Access Asynchronous
XP Continuous Access Synchronous
Synchronous copy. A function that creates and manages volume remote copies between subsystems. This writes a copy pair to the S-VOL synchronously with the P-VOL. If you create a copy group definition by using the YKP2A command, a synchronous pair of PPRC is recognized as XP Continuous Access Synchronous.
Glossary term YKAGALLO job YKAGENTD YKAGINST job YKALCSVC command YKPRM00
Definition A job that assigns datasets required before installation of mainframe agent. An executable program of the mainframe agent. This is also the name of the standard startup cataloged procedure of the mainframe agent. A job that installs mainframe agent. A command used for registering the user SVC required for running mainframe agent. This command is started by the OS START command. A member to which an initialization parameter necessary to run the mainframe agent is registered.
acquiring: mainframe agent information (Device Manager), 39; mainframe host information (Device Manager), 40; mainframe storage information (Device Manager), 38 AddHost: notes on AddHost command, 36 AddHost command, 88 AddHostRefresh command, 88 AddURLLink command, 88; notes on executing, 37 audience, 7 DeleteHost command, 88 DeleteURLLink command, 88 deleting: mainframe host information (Device Manager), 41 deleting: mainframe agent information (Device Manager), 40 Device Manager, 88 Device Manager: using Device Manager to collect mainframe system information, 43 DEVN, 88 DEVN parameter, 31 DKC serial number, 88 document: conventions, 7; providing feedback, 9
mainframe agent: installing, 24; installing, 16; overview, 10; purpose of installing, 10; registering, in Device Manager, 37; starting, 53; upgrading, 22; using, 43 mainframe agent information (Device Manager): acquiring, 39; changing, 39; deleting, 40 mainframe host: registering, in Device Manager, 36 mainframe host information (Device Manager): deleting, 41 mainframe host information (Device Manager): acquiring, 40; changing, 40 mainframe storage information (Device Manager): acquiring, 38 mainframe storage information (Device Manager): refreshing, 38 message: list, 58; output destination, 58 message: output format, 57 messages: notations, 57 ModifyHost command, 89 monitoring PPRC copy pairs: XP Replication Manager, 44

backing up: startup cataloged procedure and initialization parameters, 23
Format of command explanations, 27
C/T group, 88 CANCEL command, 88 changing: mainframe host information (Device Manager), 40 changing: mainframe agent information (Device Manager), 39 checking: before upgrading, 22; user SVC number, 23; whether to upgrade Device Manager, 22 checking settings after upgrading, 24 commands: operation commands, 53 configuration example for connecting to Device Manager, 32 Configuration example for connecting to XP Replication Manager, 33 configuration file, 88 conventions: document, 7; text symbols, 8 Conventions: Abbreviations, 8 copy group, 88 copy pair status, 88 creating: initialization parameter, 26; startup cataloged procedure, 34

GetURLLink command, 88

help: obtaining, 9 host identification name, 88 HOSTNAME parameter, 29 HP: Subscriber's Choice for Business web site, 9; technical support, 9; web sites, 9 HP StorageWorks XP for Business Continuity Manager Software, 88
operating procedure: during installation, 43; for changing configuration, 44 operation commands, 53 output information: to logs, 82
initialization parameter, 88; creating, 26 initialization parameters: backing up, 23 installing: preparations, 16; procedure, 17
PORT parameter, 29 PREFIX: notes about specifying the PREFIX parameter, 30 PREFIX, 30 Prerequisites for the copy group definition generation function, 46 pre-upgrade procedure, 23 primary site, 89 program, backing up before migration, 23
JES startup procedure, 34, 88
log level, 89 log output level: changing, 56; displaying, 55 LOGLEVEL parameter, 31
RACF, 89 RECVWAITTIME parameter, 29

datasets, backing up, 23

refreshing: mainframe storage information (Device Manager), 38 registering: mainframe agent in Device Manager, 37; mainframe host in Device Manager, 36 requirements: application software, 10; hardware, 11; installation, 10; operating system, 10 REXX, 89 REXX alternate libraries, installing, 20 REXX alternate library, 89 REXX libraries, 16 linking with XP Replication Manager, 26 Specifying the DEVN Parameter: note, 31 standard startup cataloged procedure, 34 START command, 89 startup cataloged procedure, 89; backing up, 23; creating, 34 STOP command, 89 storage attributes, 16 Subscriber's Choice: HP, 9 suspend status, 89 symbols in text, 8 system configuration example, 12 user SVC: installing, 21; using IEASVCxx parmlib user to register, 21; using YKALCSVC command to install, 20

VOLSER, 89

web sites: HP, 9
XP Command View AE Suite products, 89 XP Continuous Access Asynchronous, 89 XP Continuous Access Synchronous Synchronous, 89

HP StorageWorks XP Command View Advanced Edition Software documentation map

Version 6.2 or later

Reference number: T1780-96325 Second edition: June 2009
Legal notices Copyright 2009 Hewlett-Packard Development Company, L.P. Printed in Puerto Rico The information in this document is subject to change without notice. Reference number: T1780-96325 Second edition: June 2009
XP Storage Management Task
Install XP Command View AE Suite server and host agent software in basic Windows configurations Install XP Command View AE management server software including: - Device Manager server - XP Provisioning Manager server - XP Tiered Storage Manager server - CLI SMI-S - Common Component (Includes Windows and Linux platforms) Install and manage XP Command View AE Software host agents Install XP Command View AE software mainframe agent
HP StorageWorks XP Product Guide
XP Command View Advanced Edition software quick installation guide XP Command View Advanced Edition software installation guide

See Also

XP Command View Advanced Edition software release notes
XP Command View Advanced Edition software Device Manager agent administrator guide XP Command View Advanced Edition software mainframe agent installation and configuration guide See Also XP Command View Advanced Edition software mainframe agent release notes
Install XP Replication Manager software
XP Replication Manager software installation and configuration guide See Also XP Replication Manager software release notes
Set up the Device Manager web client
XP CV AE Device Manager Online Help on the management server See Also XP Command View Advanced Edition software Device Manager user guide
Set up the XP Tiered Storage Manager software web client
Set up the XP Replication Manager software web client
XP Replication Manager software user guide
Set up and maintain the Device Manager server: - Modify server settings - Set up for copy pair management - Modify security - Back up and restore the database - Link with other products - Troubleshoot - Configure a cluster environment Set up and maintain the XP Tiered Storage Manager server: - Modify server settings - Manage security - Back up and restore databases - Troubleshoot - Configure a cluster environment Set up and maintain the XP Replication Manager server: - Modify server settings - Manage security - Troubleshoot - Configure a cluster environment Manage storage systems: - Add and delete users - Create logical groups - Manage hosts - Add storage systems (port and LDEV) - View storage resource reports - Troubleshoot CV AE Device Manager software
XP Command View Advanced Edition software server administrator guide for Device Manager and Provisioning Manager See Also XP Command View Advanced Edition software release notes
XP Tiered Storage Manager software administrator guide See Also XP Tiered Storage Manager software release notes
CV AE Device Manager Online Help See Also XP Command View Advanced Edition software Device Manager user guide XP Command View Advanced Edition software Device Manager CLI user guide See Also XP Command View Advanced Edition software release notes
- Manage storage pools - Manage file systems - Manage device files - Manage provision plans - Troubleshoot XP Provisioning Manager software
XP Provisioning Manager software user guide See Also XP Provisioning Manager software release notes
Replicate data: - Replicate volumes - Manage sites - Manage resource groups - Create storage pools - Create remote copy pairs - Create local copy pairs - Use wizards to set up replication Migrate data: - Manage volumes in tiers - Relocate volumes - Use mainframe volumes - Add and manage users - Manage storage domains - Manage storage tiers - Use the wizard to migrate volumes
XP Replication Manager software Online Help See Also XP Replication Manager software user guide See Also XP Replication Manager software release notes
XP Tiered Storage Manager software user guide XP Tiered Storage Manager software CLI user guide See Also XP Tiered Storage Manager software release notes