The Software Product SHC-OSD is the BS2000

U41000-J-Z125-4-76 1

1 PrefaceThe software product SHC-OSD is the BS2000 host component for Symmetrix disk systems (abbreviated: Symmetrix systems; Symmetrix). It provides information services and commands for controlling the Symmetrix functions SRDF (Symmetrix Remote Data Facility) and TimeFinder:

● Symmetrix configuration– output global configuration data,

such as the microcode status and cache size– output information on the logical devices of a Symmetrix,

such as the device name, controller, RAID level, etc.

● Symmetrix SRDF function– output status information on local and remote Symmetrix systems– change the processing mode– test the recovery procedures– ensure control after a disaster

● Symmetrix TimeFinder (Symmetrix Multi Mirror Facility) function– creates Business Continuance Volumes (BCVs), which can be addressed

separately.– outputs status information on multi-mirror pairs and units – splits Multi Mirror Pairs into independent data processing – reconstructs Multi Mirror pairs

The service engineer must make the corresponding settings in the Symmetrix control function in order to make these functions available. The necessary software and licenses must be present.

SHC-OSD V4.0A wll run as of BS2000/OSD-BC V4.0 and supports Symmetrix systems with microcode statuses 5266, 5566, 5267, 5567 and 5568.

SHC-OSD V4.0A is based on the strategic interface of the EMC2 Corporation for controlling the Symmetrix subsystems, the SYMAPI (Symmetrix Application Programming Interface). This is used in the context of the partnership between Fujitsu Siemens Computers and EMC2 in the ’EMC Developers Program’.

2 U41000-J-Z125-4-76

Target group Preface

1.1 Target group

The manual is aimed at systems support staff and service engineers.

1.2 Summary of contents

The manual consists of 9 chapters and the indexes.

Chapter 1, “Preface”Contains a brief product description of SHC-OSD and describes the target group, the structure of the manual and changes with regard to the previous version.

Chapter 2, “Symmetrix in BS2000/OSD”Describes the basic functions of a Symmetrix system and explains the various compo-nents of a Symmetrix system using the example of the Symmetrix 8000. In the final section, hardware generation is explained using an example.

Chapter 3, “Software product SHC-OSD”Describes the SHC-OSD subsystem, how it is started and terminated, and the facilities available for monitoring the Symmetrix. It contains notes on the configuration and instal-lation of SHC-OSD.

Chapter 4, “SRDF (Symmetrix Remote Data Facility)”Describes the SRDF and explains the most important concepts involved. A unidirec-tional SRDF configuration is explained on the basis of a simplified representation. In addition, failure scenarios and action taken to maintain operation are described, and examples of commands are given. Finally, the chapter goes into the recovery proce-dures.

Chapter 5, “TimeFinder (Symmetrix Multi Mirror Facility)”Describes the TimeFinder function and explains the most important concepts involved. Examples of commands and short sequences are included to help describe how multi-mirror pairs are created, split and reconstructed.

Chapter 6, “Commands”Contains the SHC-OSD commands (i.e. syntax, function and operand descriptions and examples).

Chapter 7, “Program interface”Contains a description of the NDEINF macro, including the format of the macro call, and descriptions of the operands and return code table. A short example and the list of parameters for the Assembler programming language are included. You will also find the call syntax for the C interface ndeinf.h.

U41000-J-Z125-4-76 3

Preface Readme file

Chapter 8, “Messages”Contains a list of all SHC-OSD’s messages.

Chapter 9, “Appendix”Informs the user about the SDF syntax used, the components of the command return codes and the representation of S variables.

The manual contains the following indices:Lists of Abbreviations and Related publications, a Glossary and an index.

1.3 Readme file

The product-specific readme file contains details of functional changes and additions to the current product version. You will find the readme file on your BS2000/OSD system under the filename SYSRME.SHC-OSD.version.language. To find out the user ID under which the readme file is stored, please ask your system administrator. With IMON you can determine the filename with the following command:

/SHOW-INSTALLATION-PATH INSTALLATION-UNIT=SHC-OSD,LOGICAL-IDENTIFIER=SYSRME.E

You can view the readme file using /SHOW-FILE or an editor, or print it to a standard printer using the following command:

/PRINT-DOCUMENT filename, LINE-SPACING=*BY-EBCDIC-CONTROL

4 U41000-J-Z125-4-76

Changes made since the last edition of March 2002 (SHC-OSD V3.0A) Preface

1.4 Changes made since the last edition of March 2002 (SHC-OSD V3.0A)

This edition of the manual contains the following major changes since the last edition, SHC-OSD V3.0A (March 2002):

General changes

● SHC-OSD is no longer started automatically on SYSTEM READY. It must now be started explicitly as soon the required subsystems (SYMAPI-D and POSIX) have been started.

● SHC-OSD comprises a section which runs as a privileged task (SHC-OSD subsystem) and a program with the same name (SHC-OSD) running in a POSIX environment. To run the program, a batch task with the job name SHCUSERT is automatically started in the SHC-OSD subsystem under the TSOS ID.

● It is strongly recommended that gatekeeper devices are defined when connecting via S channels and essential that they are defined when connecting via Fibre Channel.

New functions in SHC-OSD V4.0A

● SHC-OSD supports the connection of Business Servers of the S line and Business Servers of the SX line to Symmetrix systems via Fibre Channel.

● Meta-volumes: Symmetrix offers two options for working with meta-volumes: Meta-volumes (on the Fibre Channel) and RAID10 (on the type-S channel). A number of Symmetrix volumes are used for both options. Only the first of these volumes (meta-header volume) is visible to the host. The other type (meta-member volumes) are only visible with SHC-OSD as ’non-generated’ devices. SRDF and TimeFinder actions are not yet supported for RAID10.

U41000-J-Z125-4-76 5

Preface Changes made since the last edition of March 2002 (SHC-OSD V3.0A)

Extensions and changes to commands

Command Operand Change / Function

HOLD-REMOTE-COPY FORCE New operand:Controls interruption of remote copy operation for remote copy pairs which are not (yet) synchronous.

SELECT New suboperand of operand value *ALL-SOURCE-UNITS: Selects subsets of volumes.

HOLD-MULTI-MIRRORING

RESUME-REMOTE-COPY

Operand is no longer supported:The value *BY-USER is permanently set. The control option offered in SHC-OSD V3.0 with the operand RESUME-REMOTE-COPY=*BY-SYSTEM has been withdrawn and not replaced, as this function is not available via the SYMAPI.

MODIFY-REMOTE-COPY-PARAMETERS


RESUME-REMOTE-COPY


SET-REMOTE-COPY-ACCESS

SELECT New suboperand of operand values *ALL-SOURCE-UNITS and *ALL-TARGET-UNITS: Selects subsets of volumes.

SHOW-SYMMETRIX--CONFIGURATION

INFORMATION New operand value:*LOCKS

SHOW-SYMMETRIX-DEVICE-CONFIG

CONFIGURATION New operand value:*META-MEMBERS

INFORMATION New operand value:*LOCKED-DEVICES

RAID-LEVEL New operand value:*RAID10

START-MULTI-MIRRORING

MULTI-ADD-MIRRORS

Operand is no longer supported:The value *YES is permanently set. The control option offered in SHC-OSD V3.0 with the operand MULTI-ADD-MIRRORS has been withdrawn and not replaced, as this function is not available with the SYMAPI

UNLOCK-SYMMETRIX New command to release Symmetrix locks

UNLOCK-SYMMETRIX-DEVICE

New command to release Symmetrix device locks

Table 1: Extensions and changes to commands

6 U41000-J-Z125-4-76

Notational conventions Preface

Extensions to macro NDEINF

1.5 Notational conventions

The following abbreviated names are used in this manual:

Business servers of the SX line (SPARC systems) are referred to as SX servers.

The BS2000/OSD operating system is referred to in compound terms, masks and lists as ’BS2000’, e.g. BS2000 account file.

The following notational conventions are used in this manual:

This symbol denotes important information which you should always observe.

This symbol and the word CAUTION! precede warning information. In the interests of system and operating security you should always observe this information.

fixed Commands or statements that you can enter via the keyboard as well as path and file names in the running text are displayed using a fixed font. This convention is also used for interface items (functions, menus, window names, field names, etc.) and path and file names in the running text.

bold provides emphasis in the running text

Short names and numbers are used for references to other publications. The complete title of each publication is provided next to its number in the list of related publications at the back of the manual.

Macro Operand Function

NDEINF UPD_TABLE New operand:Specifies whether internal data is updated before the macro is executed.Operand values:– *YES: internal data is updated before execution (default

value)– *NO: internal data is not updated before execution

Table 2: Extensions to macro NDEINF

i

!

U41000-J-Z125-4-76 7

2 Symmetrix in BS2000/OSDSymmetrix is the name of what is currently EMC2 Corporation’s top-of-the-range disk storage subsystem. Symmetrix supports mainframes and open systems and thus provides an enterprise-wide storage solution. Symmetrix emulates the 3860-42, -43 and -51 disk controllers and the D3435, D3480, D348E, D348F, D3475-8F and D3490-xx disks.

2.1 Functions and components

All Symmetrix systems are high-availability disk storage systems that meet the require-ments of all the availability levels defined by the RAID Advisory Board as well as the old RAID standards defined by Berkeley University. They differ only in their configurations (disk capacity, cache size and channel ports). For more information, see EMC2 Corporation’s product manuals, available on the internet at the address http://www.emc.com/products/.

Failure-tolerant disk storage systems (FTDS) can be created by the following means:

● data mirroring (RAID1)

● parity checking (RAIDS)

● a combination of RAID1 and RAIDS within one system in order to meet requirements in terms of performance, availability and cost.

Symmetrix uses a “proactive” maintenance strategy:

● The cache and disks are checked at intervals for errors (scrubbing).

● To enable rapid and well-targeted responses to failures, each subsystem has a direct connection to the service center of the EMC2 Corporation, which recognizes what needs to be done and then coordinates and initiates the necessary action.

http://www.emc.com/products/

8 U41000-J-Z125-4-76

Functions and components Symmetrix in BS2000/OSD

Meta-volumes: Symmetrix offers two options for working with meta-volumes: meta-volumes (on Fibre Channel) and RAID10 (on type-S channel). For both options, a number of Symmetrix volumes are used. Only the first of these volumes (meta header volume) is visible to the host. The remaining meta member volumes are only visible under SHC-OSD as “non-generated” devices.

● Meta-volumes on Fibre Channel can be used as striped volumes (parallel addressing) and as concatenated volumes (sequential addressing).

● RAID10 on type-S channels supports striped volumes for CKD formatting. SRDF actions and TimeFinder actions will only be supported for RAID10 in a later version of SYMAPI.

Symmetrix offers the following functions:

● SRDF (Symmetrix Remote Data Facility)SRDF can be used to mirror the production data in a second, spatially separate Symmetrix without causing the host any additional load. The second Symmetrix can (theoretically) be located anywhere. In the event of a catastrophe there is therefore a copy of the data on this remote system. This constitutes a failure recovery functionality.In this manual, the term “catastrophe” indicates the simultaneous failure of the main host and the local Symmetrix in a computer center (CC failure), e.g. in the event of destruction due to fire, flood, explosion, earthquake etc.

● TimeFinder (Symmetrix Multi Mirror Facility)This function enables additional copies of a unit to be created, which can then be addressed separately. This can be used for the separate processing of critical data (e.g. for backup or test purposes).

The software product SHC-OSD supports the SRDF and the TimeFinder functions, which are both described in the following chapters.

U41000-J-Z125-4-76 9

Symmetrix in BS2000/OSD Functions and components

A Symmetrix consists of the following components:

Figure 1: Components of a Symmetrix system

C

A

D C

B

D C

A

D C

B

D

A

A

B A

B

B A

A

B A

B

B

C

A

D C

B

D C

A

D C

B

D

A

A

B A

B

B A

A

B A

B

BCA

Memory buses

CA CACA

DA DA DA

Cache

Low

Cache

memoryLow

memory

Highmemory

Highmemory

Top high

DA

Top lowBottom highBottom low

DA: Disk adapter

CA: Channel adapter

10 U41000-J-Z125-4-76

Functions and components Symmetrix in BS2000/OSD

● Channel Adapter (CA, EA or FC)Four type-2 channels, two or four type-S channels or two or four Fibre Channels can be connected per channel adapter. Simultaneous data transfer via various channels per channel adapter can be enabled. This, however, depends on the number of micro processors used. The channel adapters process the input/output requests from the host end and control access to the cache of the Symmetrix system.

● CacheEach input/output request is subject to caching. Write requests are considered to be completed as soon as the data is written to the cache and verified. A high hit rate (> 90%) can also be achieved for read requests by using a larger cache, regardless of the protection mode (RAID1 or RAIDS) at the disk end, because the cache is not used for “mirror” or “parity” data. On detection of sequential processing, data is prefetched track by track in order to avoid a read miss, with step-by-step increases up to the maximum of tracks.

● Disk adapters (DA)Disk adapters control access to the physical drives (access systems). Two micropro-cessors per disk adapter (side A/side B) support a total of four SCSI paths. Simulta-neous data transmission on two SCSI paths (one path per side) is possible with each disk adapter. To ensure failsafe performance, the disk adapters are interconnected in pairs internally:

Figure 2: Disk adapters

This interconnection is generally implemented in such a way that, in the event of an emergency, disk adapter xA can access the access systems of disk adapter yA, and disk adapter xB can access the access systems of disk adapter yB.

C D

xA

C D

xB

DA x

C D

yA

C D

yB

DA y

X bus

Y bus

U41000-J-Z125-4-76 11

Symmetrix in BS2000/OSD Functions and components

● Access systemsThe gross capacity of each access system is at least 9 Gbyte. Devices with high capac-ities keep manufacturing costs down and, together with high cache efficiency, mean that loss of performance is negligible. Disadvantages generally arise when it comes to application-friendly allocation and administration.

Net capacity of an 18-Gbyte disk (1 Gbyte = 109 byte):

Net capacity of a 9-Gbyte disk:

The Hyper-Volume Extension (HVE) function allows many logical volumes to be set up on an access system in configurations such as the following:– 3 D3490-30 logical volumes or– 2 D3490-30 logical volumes and 3 D3490-10 logical volumes or – 8 D3490-10 logical volumes or– 1 to max. D3435 logical volumes (where max. = maximum value of the HVE

function).

Device type Formatting Capacity (in Gbyte)

2K 12.3

D3490-x (CKD) NK2 13.7

NK4 15.5

2K 14.6

D3435 (FBA) NK2 18.2

NK4 currently not supported by BS2000/OSD

Device type Formatting Capacity (in Gbyte)

2K 6.08

D3490-x (CKD) NK2 6.72

NK4 7.68

2K 7.24

D3435 (FBA) NK2 9.05

NK4 currently not supported by BS2000/OSD

12 U41000-J-Z125-4-76

Symmetrix generation Symmetrix in BS2000/OSD

2.2 Symmetrix generation

A Symmetrix can emulate different controllers and devices. For example, it is possible to specify that the controller shoul behave like a 3860-51. In this case, this controller type must be assigned to the relevant channel as well when the hardware is generated in BS2000/OSD-BC. The volumes fitting the types of device will also be emulated in the Symmetrix and can be generated in BS2000/OSD with the standard volume type STDDISK.

If the CUADD function is used then up to 16 times 256 devices can be addressed via one S-type channel at S series business servers (with /390 architecture).

2.2.1 Terminology used and explanations

The terms “unit” and “device” signify a logical volume (logical disk) in the Symmetrix.

In SHC-OSD commands, Symmetrix volumes are defined using the UNIT operand. In the majority of commands, UNIT can be used to specify one of the following:

● controller (emulated controller)

● MN (mnemonic device name of the logical volume)

● VSN (Volume Serial Number)

● Pubset ID or volume set ID (ID of a SF/SM pubset or ID of a volume set)

● Symmetrix serial number and Symmetrix internal number of the logical volume

UNIT can therefore be used to specify one or more logical volumes.

All abbreviations used are listed and explained from page 309 onwards, all technical terms from page 311 onwards.

U41000-J-Z125-4-76 13

Symmetrix in BS2000/OSD Symmetrix generation

2.2.2 Mapping the BS2000/OSD generation to the Symmetrix configuration

The relationships between the names of the units using BS2000/OSD language conven-tions and Symmetrix language conventions are illustrated in figure 3 and figure 4.

Figure 3: Assignment of units (BS2000/OSD and Symmetrix language conventions)

The files (:A:$<user>.<file1..6>) are located on pubset A (figure 3). Pubset A consists of the units 5000..5003 together with the associated volumes PUBA00..PUBA03. These are assigned to the logical volumes #0000..#0003 in the Symmetrix. The logical volumes #0000 and #0001 are located on physical volume 2A:C0 and are mirrored on 15A:C0 (Raid1). The same applies to the logical volumes #0002 and #0003 (figure 3).

# Log. volume

Phys.volume

#0000

#0001

#0002

#0003

2A:C0

15A:C0

2A:C1

15A:C1

BS2000/OSD Symmetrix

5001

5000

5002

5003

VolumeUnit (MN)

(VSN)

:A:$<user>.<file1>

:A:$<user>.<file2>

:A:$<user>.<file3>

:A:$<user>.<file4>

:A:$<user>.<file5>

:A:$<user>.<file6>

Files Pubset ID

PUBA00

PUBA01

PUBA02

PUBA03

PUBSET

A

14 U41000-J-Z125-4-76

Symmetrix generation Symmetrix in BS2000/OSD

Figure 4: Physical and logical assignment of units for connection to type-S channel (schematic)

The C500 and C501 controllers use channel numbers 20, 21, 40 and 41 (figure 4). They are connected to the Symmetrix I/O adapter via SCD ports 90, 91, 92 and 93. Unit 5000 with volume PUBA00 is assigned to logical volume #0000 in the Symmetrix. Logical volume #0000 is located on physical volume 2A:C0 and is mirrored on 15A:C0 (Raid1).

BS2000/OSD Symmetrix

20214041 3b:A

C0physicalrelocation

logicalrelocation

5000#0000

3a:A1b:A1a:A

SCD93

909192

PUBA00

BS2000/OSD generation:/CTL C500,BLM,(20,1,90) (21,1,91)/CTL C501,BLM,(40,1,92),(41,1,93) /DVC 5000,AA,D,00,(C500),(C501), -/ *,MULT=256,AT=CTL

Symmetrix configuration:Logical volume #0000addresses:

01 00 at 1a:A, 01 00 at 1b:A, 01 00 at 3a:A, 01 00 at 3b:A

RAID type: RAID1Mirror on 2A:C0, 15A:C0

20,21,40,41 Channel numbers at the BS2000/OSD host

90, 91, 92, 93 Port numbers at the SCD (S Connection Director)

1a:A, 1b:A, 3a:A, 3b:A Channel adapter (CA or EA) and port in Symmetrix

5000/PUBA00 Unit (MN)/Volume (VSN)

#0000 Logical volume

2A:C0, 15A:C0 Disk adapter (DA) and physical disks in Symmetrix

CUADD: Control Unit Image Number (0..3)

Address: Current address at the channel (00..FF)

C500/C501: MN of the controller

15A2A

C1 D1

D0 C0

C1 D1

D0

U41000-J-Z125-4-76 15

Symmetrix in BS2000/OSD Symmetrix generation

2.2.3 Generation in BS2000/OSD

In order to use and address the logical volumes of a Symmetrix subsystem in BS2000/OSD, they must be generated statically when the hardware is generated or defined in S systems by changing the dynamic I/O configuration, see manual “Introductory Guide to Systems Support” [5]. Business servers of the SX range (SPARC systems) are referred to below as SX servers. Generation in BS2000/OSD is not necessary for SX servers connected over the Fibre Channel.

The specific characteristics of static generation are described below (see also the manual “System Installation” [6]).

Example of generation statements for hardware generation, type-S channel and SCD (type S connection director) similar to figure 4:

Each device can be reached via four channels. The Symmetrix is configured in such a way that devices 5000 to 507F are available via all Channel adapters (CAs) assigned to ports 90, 91, 92 and 93 of the SCD and are thus available on every host connected to the SCD. In this case, the four channels 20, 21, 40 and 41 are assigned to the SCD.

Example of generation statements for hardware generation for 2 times 256 devices, type-S channel and using the CUADD function for a Business Server of the S line:

* CTL C500,BLM,(20,1,90),(21,1,91) CTL C501,BLM,(40,1,92),(41,1,93)* DVC 5000,AA,D,00,(C500),(C501),MULT=28,AT=CTL * 5000-501B DVC 501C,89,D,1C,(C500),(C501),MULT=33,AT=CTL * 501C-503C DVC 503D,A7,D,3D,(C500),(C501),MULT=3,AT=CTL * 503D-503F* DVC 5040,A7,D,40,(C500),(C501),MULT=8,AT=CTL * 5040-5047 DVC 5048,89,D,48,(C500),(C501),MULT=56,AT=CTL * 5048-507F

* CTL 5200,BLM,(20,0,C2),(21,0,46),(61,0,C6),(60,0,4A) CTL 5201,BLM,(22,0,CA),(25,0,4E),(63,0,CE),(62,0,52) * DVC 5200,AA,D,00,(5200),(5201),MULT=256,AT=CTL * 5200-52FF* CTL 5210,BLM,(20,0,C2),(21,0,46),(61,0,C6),(60,0,4A),CUADD=1 CTL 5211,BLM,(22,0,CA),(25,0,4E),(63,0,CE),(62,0,52),CUADD=1* DVC 5300,AA,D,00,(5210),(5211),MULT=256,AT=CTL * 5300-53FF

16 U41000-J-Z125-4-76

Special features for devices on the fibre channel Symmetrix in BS2000/OSD

● The device addresses on the S channel must not contain gaps and must be generated in ascending order: Device 0, 1, 2 and so on.

● For every generated controller (defined with CTL statement) assigned to a Symmetrix, at least one device should be attached to permit SHC-OSD to recognize the entire configuration of the Symmetrix and assign it to the generated devices.

● When using TimeFinder in BS2000/OSD, the additional mirror units (BCVs) also have to be configured.

● When using SRDF in BS2000/OSD, at least the source units have to be generated for SHC-OSD control to be available. The target units have to be generated at the host that uses them in the event of a catastrophe.

● Gatekeeper devices must also be generated and formatted for BS2000/OSD.

CAUTION!When using Microcode versions 5266 and 5566, the logical volumes of a Symmetrix cannot be assigned correctly and uniquely to unattached BS2000 device mnemonic names (mapping) when using the CUADD function.

2.3 Special issues under SHC-OSD for devices on the Fibre Channel

This section provides information on the configuration and operation when BS2000 disks are connected to Business Servers of the SX range via Fibre Channel (see below and page 20) or to S systems (see page 20).

2.3.1 Configuration on Business Servers of the SX line

BS2000 disks which are connected via Fibre Channel to SX servers are mapped to parti-tions of the configured Solaris disks. These are operated using one or more Fibre Channel HBAs (Host Bus Adapters). The Solaris disks are connected directly or via a Fibre Channel switch to the Symmetrix. BS2000 disks connected via Fibre Channel on SX servers must therefore be configured on Symmetrix(1), Switch(2), Solaris(3) and X2000(4) levels (the numbers of the levels as they are used in the following figure are given in brackets). This is described below for the individual levels.

i

!

U41000-J-Z125-4-76 17

Symmetrix in BS2000/OSD Special features for devices on the fibre channel

Figure 5: Configuration of units on the Business Servers of the SX range (example: SX130)

BS2000 Mnemonic name 2000

SX130

Lpfc0 Lpfc1

Switch Switch

Symmetrix

FC 4A FC 5A50:00:..01 50:00:..02

DA 1A DA 4A

X2000 4 Assignment of BS2000 de-vice to Solaris device

MN 2000 : /emc/power20a

Powerpath 3 Path management, mapping to physical device

/emc/power20a →/dev/dsk/020 + /dev/dsk/040

SCSI driver

3 Assignment of target/LUN to device name

/dev/dsk/020 : target 0, Lpfc0, Lun 0/dev/dsk/040 : target 0, Lpfc1, Lun 0

FC driver 3 Assignment of WWN to targets

Lpfc0 : wwn 50:00:..:01 → target 0Lpfc1: wwn 50:00:..:02 → target 0

Instance Level Task / Representation Configuration example

SymmetrixDA adapter

1 Assignment of logical device # to physical disks

logical volume 010 → DA 1A Disk 0logical volume 010 → DA 4A Disk 0

Switch 2 Zoningvisibility of ports

Symmetrix FC adapter

1 Assignment of LUN to Symmetrix logical device #

4A : t/lun 000 → logical volume 0105A : t/lun 000 → logical volume 010

18 U41000-J-Z125-4-76


Symmetrix

The settings in the Symmetrix must be carried out by a qualified engineer.

The Symmetrix devices are type-FBA (server). The Fibre Channel port of the Symmetrix must be set as for Solaris.

In order to operate via Fibre Channel, SHC-OSD requires gatekeeper devices. Gatekeeper devices are devices specially configured in the Symmetrix to handle the inputs and outputs of the host components (in this case SHC-OSD). These devices should be defined as RAID1 disks with 3 to 10 cylinders.

Switch

The zone must be set correctly in the Fibre Channel switch.

Solaris

The settings in Solaris must be carried out by a qualified engineer.

The visiblity of the Symmetrix disks is controlled by the configuration of the HBAs and the SCSI devices connected to these HBAs. The HBAs should be operated in “Persistent Binding” mode, i.e. the mapping of the WWNs (World Wide [port] Name) of the Symmetrix Fibre Channels should be permanently assigned to targets on the HBA with appropriate entries in the configuration file /kernel/drv/lpfc.conf. The program /usr/sbin/lpfc/lputil can be used to manage the configuration.

The visible LUNs (Logical Unit Number) of the targets of the HBA are defined in the file /kernel/drv/sd.conf. Further rules on displays in /etc/system and /kernel/drv/lpfc.conf for Solaris must be taken into account.

If the Symmetrix disks are made visible via several HBAs, the Power Path software from EMC should be used to select the paths and, in the event of the non-availability of a path, automatically select an alternative path.

i

i

U41000-J-Z125-4-76 19


X2000

CAUTION! In BS2000/OSD V5.0, it is not possible to operate one and the same Symmetrix disk with different system or channel architectures if it was formatted on an SX130 machine using Fibre Channel (since the emulation and thus the formatting and the label depends on the channel type). The Solaris label would corrupt a BS2000 label written using a type-S channel without this becoming immediately visible, since the VSN remains readable.

The Symmetrix disks must be provided with a Solaris label and partitioned using WSA (user interface WebSysAdmin for domain management, see the manual “WebSysAdmin/DomainAdmin” [18]).

CAUTION! If SHC-OSD is to be able to display the disks correctly or if SRDF and/or TimeFinder are to be operated with SHC-OSD for these disks, they must be partitioned in such a way that they contain exactly one BS2000 partition. X2000 and SHC-OSD do not check this rule. If this rule is not observed, SRDF or TimeFinder commands can produce unwanted side effects, as SHC-OSD can only ever handle complete Symmetrix devices.

Only devices of a single Symmetrix controller should be generated for host connectors (host adapters of the servers, visible to BS2000 as a bus channel).

In order to configure the disks with X2000, they must be writable and readable, i.e. they must not be in NOT-READY or READ-ONLY status. This is especially important for BCVs and SRDF target units. SRDF target units can be configured in READ-ONLY status if the corre-sponding SRDF source unit is already configured and thus if the partition data is readable. The gatekeeper devices must be configured for BS2000/OSD.

BS2000/OSD

The gatekeeper devices must be attached and formatted in BS2000/OSD.

Devices which are connected via Fibre Channel do not have a controller and thus have the following special features:

● No control mnemonic names are output with the SHOW commands.

● Controllers are not accepted as selection criteria for SHOW commands and SRDF commands. Such entries are rejected with the message NDE1002.

● The mapping of BS2000/OSD mnemonic device names to the Symmetrix configuration is thus only possible for devices in ATTACHED status.

!

!

20 U41000-J-Z125-4-76


2.3.2 Operation on Business Servers of the SX line

Notes on devices in NOT-READY status:

SRDF target units and additional mirror units (BCVs) can be deactivated for access by the host (status NOT-READY). This has several consequences:

● If the devices are in NOT-READY status when Solaris is started, the start of Solaris and X2000 is delayed by several seconds per NOT-READY device. The corresponding BS2000 devices can be attached, i.e. they are recognized in BS2000 but not accessible.

● If the devices are returned to READY status by actions of the EMC service engineer or by SHC-OSD commands, they can be brought back into operation. SHC-OSD cannot rename the BCVs in a command run, however, in this status, if they have not already been configured and attached in BS2000, as it will not recognize which configured device is the BCV. When the target units have been attached with /ATTACH-DEVICE (see the manual “Commands” [1]), SHC-OSD can recognize the assignment again.

● If a device which was generated when Solaris and BS2000 were started is switched to NOT-READY status, all access to the device, e.g. by SHC-OSD or by the disk monitor, is rejected with IO errors (INOP). Messages displaying the devices as “offline” are output on the Solaris console. SHC-OSD can still operate this device, however.

2.3.3 Configuration on S systems

The configuration of the Fibre Channel on S systems is similar to that of a type-S channel. BS2000 disks which are connected to S systems via Fibre Channels are operated on configured disks with FBA track format. Disks with CKD track format are not supported. BS2000 disks on the Fibre Channel are operated via one or more Fibre Channel HBAs (Host Bus Adapter). The disks are always connected to the Symmetrix via a Fibre Channel switch. BS2000 disks connected to S systems via Fibre Channel must be configured on Symmetrix(1), Switch(2) and BS2000(3) levels (the numbers of the levels as they are used in the following figure are given in brackets). This is described for the individual levels in the following sections. The WWN of the fibre channel port of the Symmetrix must be set for the channel on generation.

U41000-J-Z125-4-76 21


Figure 6: Configuration of units on the Business Servers of the S line

Symmetrix

The settings in the Symmetrix should be carried out by a qualified engineer.

The Symmetrix devices are type-FBA (server). The Fibre Channel port of the Symmetrix must be set as for Solaris (see page 18).

In order to be used via Fibre Channel, SHC-OSD requires gatekeeper devices. Gatekeeper devices are devices specially configured in the Symmetrix to handle the inputs and outputs of the SYMAPI functions of host components (here SHC-OSD). The advantage of gatekeeper devices is that by concentrating the inputs and outpus on them, the load on other devices is relieved.

BS2000 3 MN 2000

S 1xx

Kanal 80 Kanal 81

Switch Switch

Symmetrix

FC 4A FC 5A50:00:..01 50:00:..02

DA 1A DA 4A

Dynamic Channel Subsystem

3 Path management (as per configuration)

MN 2000 to channel 80, 81

FC Host Bus Adapter

3 Assignment of WWN to targets

Lpfc 0 : wwn 50:00:..:01 → target 0Lpfc 1: wwn 50:00:..:02 → target 0

Instance Level Task / Display Configuration example

SymmetrixDA adapter

1 Assignment of logical de-vice # to physical disks

logical volume 010 → DA 1A Disk 0logical volume 010 → DA 4A Disk 0

Switch 2 Zoningvisibility of ports

Symmetrix FC adapter

1 Assignment of LUN to Symmetrix logical device #

4A : t/lun 000 → logical volume 0105A : t/lun 000 → logical volume 010

i

22 U41000-J-Z125-4-76


The configuration of these devices is described in the section “Configuring gatekeeper devices” on page 26.

Switch

The number of visible devices (zones) must be set correctly in the Fibre Channel switch. These settings are carried out by the service engineer.

BS2000/OSD

Devices which operate on the type-F channel must be generated with the program IOGEN (see the manual “System Installation” [6]). They thus have the following special features/differences from the type-S channel:

CTL statement: The controller is defined via its WWN

CHN statement: The IBF-type channel with FCP mode must also be specified and the WWN entered for each path. For further information on FCP mode, see the readme file of BS2000/OSD V5.0.

DEV statement: Instead of the device address, the LUN must be specified

U41000-J-Z125-4-76 23

3 Software product SHC-OSD SHC-OSD provides information services on the global Symmetrix configuration, the Symmetrix device configuration and the SRDF and TimeFinder functions via BS2000/OSD command interfaces and a program interface.

SHC-OSD also permits the SRDF function to be controlled and the TimeFinder function to be used and controlled via BS2000/OSD command interfaces (see chapter “SRDF (Symmetrix Remote Data Facility)” on page 47 and chapter “TimeFinder (Symmetrix Multi Mirror Facility)” on page 73). The control of these functions can be integrated in operational procedures. This results in a high degree of automation and in reliable processing in critical operating situations.

SHC-OSD V4.0A is an optional DSSM subsystem which will run as of BS2000/OSD-BC V4.0.

Commands for SRDF

Command Function Page

DISABLE-REMOTE-LINK-DIRECTOR Disables remote link directors 101

ENABLE-REMOTE-LINK-DIRECTOR Enables remote link directors 104

HOLD-REMOTE-COPY Interrupts remote copy operation 113

MODIFY-REMOTE-COPY-PARAMETER Changes the processing mode and remote copy parameters

118

RESUME-REMOTE-COPY Resumes remote copy operation 141

SET-REMOTE-COPY-ACCESS Sets the access path for the data of a remote copy pair

146

SHOW-REMOTE-COPY-STATUS Displays the status of remote copy pairs 163

SHOW-SYMMETRIX-CONFIGURATION Displays the Symmetrix configuration 184

SHOW-SYMMETRIX-DEVICE-CONFIG Displays the Symmetrix device configu-ration

192

UNLOCK-SYMMETRIX Releases Symmetrix locks 217

UNLOCK-SYMMETRIX-DEVICE Releases Symmetrix device locks 218

24 U41000-J-Z125-4-76

Software product SHC-OSD

SHC-OSD allows the SRDF processing mode to be set. The Symmetrix draws distinctions between a synchronous, a semi-synchronous and an asynchronous processing mode. It is also possible to define how the Symmetrix should respond when part of the remote copy pair is no longer available (see section “Testing the recovery procedures” on page 67). The commands for controlling the SRDF function allow you to enable and disable the remote link directors (remote adapter) and to set access paths for the remote copy pairs. The SHOW commands allow you to obtain the status of the remote copy pairs and the SRDF settings.

Commands for TimeFinder (incl. Multi-BCV)

The commands for controlling the TimeFinder functions allow you to establish and split multi-mirror pairs and to reconstruct them once they have been split. The SHOW commands display the current processing status and the status of the multi-mirror pair.

Commands for the control of the internal settings

The internal setting for maintenance and diagnostics of the SHC-OSD subsystem can be displayed and modified with the aid of the two above mentioned commands.


HOLD-MULTI-MIRRORING Splits a multi-mirror pair 107

RESUME-IO Resume input/output activity 134

RESUME-MULTI-MIRRORING Reconstructs a multi-mirror pair 135

SHOW-MULTI-MIRRORING-STATUS Displays the status of multi-mirror pairs 152

SHOW-SYMMETRIX-DEVICE-CONFIG Shows Symmetrix configuration 192

START-MULTI-MIRRORING Establishes a multi-mirror pair 207

STOP-MULTI-MIRRORING Cancels a multi-mirror pair 213



MODIFY-SHC-PROCESSING Changes the internal settings of SHC-OSD 125

SHOW-SHC-PROCESSING Displays the internal settings of SHC-OSD 179

U41000-J-Z125-4-76 25

Software product SHC-OSD Symmetrix configuration

Commands of the information services

The information service commands enable the outputs above and support the structured output in S variables.

3.1 Symmetrix configuration

The Symmetrix must be configured by a service technician, to enable the following functions:

● In order to use SRDF, a number of logical volumes must be made available for the use of SRDF on two Symmetrix systems and two or more ports (type-S channel adapters or Fibre Channels) must be made available for remote links.

● In order to use TimeFinder, at least one logical volume must be reserved. The reserved volumes should then only be used for TimeFinder. The types and sizes of these units (logical volumes) must correspond to those of the normal unit.

SHC-OSD requires BS2000 devices to display and control Symmetrix systems via which it can handle inputs and outputs on the Symmetrix. For a Fibre Channel connection, these must be gatekeeper devices (devices specially configured in the Symmetrix). Gatekeeper devices are not absolutely necessary for an S channel connection, but strongly recom-mended to ensure smooth operation.






SHOW-SYMMETRIX-DEVICE-CONFIG Displays the Symmetrix device configuration 192

26 U41000-J-Z125-4-76

Configuring gatekeeper devices Software product SHC-OSD

3.2 Configuring gatekeeper devices

Configuring dedicated gatekeeper devices

Dedicated gatekeeper devices must be set up in the Symmetrix and in the BS2000 gener-ation.

These devices must not be set up as SRDF source units, SRDF target units, additional mirror units or meta-volumes and should have the following additional properties:

● Capacity of 3 to 10 Mbytes (3 to 10 cylinders)

● Formatted with the utility program VOLIN (see the manual “Utility Routines” [8]) as shared volumes and thus independent of global settings made, for instance, with /SET-DISK-PARAMETER

● RAID1 protection (so that these devices can always be accessed)

● Definition with low unit address (e.g. MN 5400 on controller 5400)

● Optional inclusion in the SYMAPI Gkselect file (see section “Configuring SYMAPI to operate SHC-OSD” on page 31)

● When using VM2000, gatekeeper devices can be assigned to all guest systems in “shared” mode by the monitor system and shared by the guest systems.

Type-S channel

If disruption to BS2000 operation due to occupancy by SYMAPI is to eliminated, dedicated gatekeeper devices should definitely be configured in the Symmetrix and the BS2000 generation (see above).

When using type-S channels, any device can be used as a gatekeeper device if necessary, if it can be accessed and occupied locally and, depending on the disk properties, meets certain requirements:

● The disks must not be occupied by their own system or by foreign systems. SYMAPI occupies these disks for short periods for SHC-OSD actions. This can be determined using /SHOW-DISK-STATUS. Such occupancy is indicated as task-exclusive SPECIAL occupancy.

● Imported pubsets: Here, SYMAPI occupies the pubset in the same way as when opening a file on this pubset. The tasks which occupy the pubset can be identified with /SHOW-PUBSET-PARAMETERS ...,INFORMATION=*PUBSET-OCCUPATION.

SYMAPI tries to avoid queries during the occupancy. Queries which may arise (SYMAPI messages NKVD013 and MOUNT DISK) can be identified by the text FOR SYMAPI BS2000 DRIVER and are rejected.

U41000-J-Z125-4-76 27

Software product SHC-OSD Installing SHC-OSD

In the case of SRDF or TimeFinder actions, SHC-OSD (SYMAPI) may not be able to find any suitable gatekeeper devices. The command will then be rejected with the error message NDE1150, since the current devices to be processed cannot be used as gatekeeper devices.

Channel type Fibre Channel

When using a channel of the type Fibre Channel, dedicated gatekeeper devices must be defined.

3.3 Installing SHC-OSD

SHC-OSD is installed with IMON. The precise installation procedure (change of version or initial installation) is described in the Release Notices SYSFGM.SHC-OSD.040.D and SYSFGM.SHC-OSD.040.E.

3.3.1 Requirements for installation

● SHC-OSD V4.0 can be run on the Business Servers of the S line and the SX line.

● SHC-OSD V4.0 requires at least BS2000/OSD V4.0.

● The current correction statuses needed for operation can be found in the Release Notice.

● The products SYMAPI and POSIX-BC must be installed.

● CRTE-BASYS must be available in at least version 1.3C and be started.

● POSIX and SYMAPI-D must be started, so that SHC-OSD can be started. Conversely, SHC-OSD must be stopped when POSIX or SYMAPI-D have to be stopped.

28 U41000-J-Z125-4-76

Installing SHC-OSD Software product SHC-OSD

3.3.2 Delivery components

SHC-OSD V4.0A includes the selectable units SHC-OSD and SYMAPI.

The selectable unit SHC-OSD comprises a section which runs as a privileged task (SHC-OSD subsystem) and a program with the same name (SHC-OSD) running in a POSIX environment. To run the program, a type-TP batch task with the job name SHCUSERT is automatically started in the SHC-OSD subsystem under the TSOS ID.

SHC-OSD is no longer started automatically on SYSTEM READY. As soon as the required subsystems (SYMAPI-D and POSIX) are started, it must be started explicitly.

The selectable unit SYMAPI comprises a section which runs as a privileged task (SYMAPI-D subsystem) and EMC Corporation’s SYMAPI product ported into the POSIX environment of BS2000.

SYMAPI is a C interface with which the configuration, the status, performance data and important control functions of Symmetrix can be accessed. This interface is largely independent of the microcode.

The SHC-OSD selectable unit contains the following components:

Component Meaning

SIPLIB.SHC-OSD.040 Library with privileged macros

SYSDMP.SHC-OSD.040 PRODAMP procedures which are incorporated in SYSDMP.DAMP and started via NDMDAMP.

SYSENT.SHC-OSD.040 ENTER job for SHC-OSD User Task. This job is only used internally by SHC-OSD.

SYSFGM.SHC-OSD.040.D or SYSFGM.SHC-OSD.040.E

Release Notice in German and English

SYSLIB.SHC-OSD.040 Library with LLM objects and user macros

SPMLNK.SHC-OSD.040 Subsystem for SX line

SYSLNK.SHC-OSD.040 Subsystem for S line

SYSMES.SHC-OSD.040 Message file; it must be incorporated in the system message files or activated with /MODIFY-MIP-PARAMETERS (see manual “Commands” [1])

SYSPRG.SHC-OSD.040 This program is only used internally by SHC-OSD.

SYSRME.SHC-OSD.040.D bzw.SYSRME.SHC-OSD.040.E

Readme file in German and English

SYSRMS.SHC-OSD.040 REP depot for the subsystem

SYSSDF.SHC-OSD.040 SDF syntax file; it must be incorporated into the system syntax file with SDF-I or SDF-U or activated with /MODIFY-SDF-OPTIONS (see manual “Commands” [1]).

Table 3: Components of the SHC-OSD selectable unit (part1 of 2)

U41000-J-Z125-4-76 29


The SYMAPI selectable unit contains the following components:

● See the relevant Release Notice for information on installing diagnostic aids.

● In order to create diagnostic information, the component NDMDAMP V13.0A03 for BS2000/OSD V4.0 or higher should be used. The section “Diagnostic aids” on page 44 describes how to use the diagnostic aids for SHC-OSD.

● SHC-OSD is loaded dynamically as a DSSM subsystem.

SYSSMB.SHC-OSD.040 DAMP symbol files which are incorporated in SYSSMB.DAMP.

SYSSPR.SHC-OSD.040 Compiled SDF-P procedure to start the SHC-OSD-TU program. The procedure is only used internally by SHC-OSD.

SYSSSC.SHC-OSD.040 Subsystem catalog for DSSM subsystem SHC-OSD. The file must be incorporated in the system subsystem catalog.

Component Meaning

SINLIB.SYMAPI.051 Configuration files and SHELL scripts of SYMAPI

SYSFGM.SYMAPI.051.D bzw. SYSFGM.SYMAPI.051.E

Release Notice in German and English

SPMLNK.SYMAPI.051.DRIVER Subsystem driver for SX line

SYSLNK.SYMAPI.051.DRIVER Subsystem driver for S line

SYSLNK.SYMAPI.051.TU LLM objects for BS2000/OSD

SYSRMS.SYMAPI.051.DRIVER REP depot for driver subsystem

SYSSSC.SYMAPI.051.DRIVER Subsystem catalog for driver: SYMAPI-D

Table 4: Components of the SYMAPI selectable unit

Component Meaning

Table 3: Components of the SHC-OSD selectable unit (part2 of 2)

i

30 U41000-J-Z125-4-76


3.3.3 Installing SYMAPI

Installation is carried out using IMON and the POSIX installation program.

Driver components (subsystem SYMAPI-D) and TU components (above all SINLIB) are installed with IMON.

The subsystem SYMAPI-D is automatically started after SYSTEM READY.

The POSIX programs from SINLIB.SYMAPI.<version> and the configuration files of SYMAPI are installed in the POSIX file system with the POSIX installation program.

3.3.4 Symmetrix microcode and licenses

Symmetrix microcode and licenses for SHC-OSD

● SHC-OSD V4.0A supports all Symmetrix systems of the series

– 5000 with microcode status 5266 and 5267 – 8000 with microcode status 5566, 5567 and 5568

You can ask your service engineer to upgrade the Symmetrix microcode status.

● In order to use SRDF, you must have an SDRF license for all the Symmetrix systems that are to contain the source or target units.

● In order to use TimeFinder, you must have a TimeFinder license for all the Symmetrix systems that are to contain the additional mirror units.

● Multi BCV is available for use for all supported Symmetrix systems.

Licenses for SYMAPI

A license is required to operate SHC-OSD with SYMAPI. This license is included free of charge in the scope of supply of the SYMAPI selectable unit when you purchase the SHC-OSD product. The file with the license key is automatically installed when SYMAPI is installed with the POSIX installation program.

All SHC-OSD functions are thus available after a complete installation.

U41000-J-Z125-4-76 31


3.3.5 Configuring SYMAPI to operate SHC-OSD

SHC-OSD is directly affected by the settings of the SYMAPI configuration options:

● SYMAPI options file:

Settings under /var/symapi/config/options impact on the SRDF commands.

● SYMAPI avoidance files (symavoid and gkavoid) :

If serial numbers of Symmetrix systems are stored in /var/symapi/config/symavoid, SHC-OSD can neither display nor control these systems.

If mnemonic names of BS2000 devices are entered in /var/symapi/config/gkavoid, SHC-OSD actions can fail because no gatekeeper device can be opened.

● SYMAPI gatekeeper file:

If mnemonic names of BS2000 devices are entered in /var/symapi/config/gkselect, only these devices are used as gatekeeper devices. When using this function, ensure that gatekeeper devices are entered for all connected Symmetrix subsystems and that these are also attached in BS2000/OSD. Otherwise, SHC-OSD actions can fail because no gatekeeper device can be opened.

The advantage of this function is that SYMAPI does not have to search for a gatekeeper device but always selects one from the specified list.

Note that BS2000 devices entered in the SYMAPI avoidance file /var/symapi/config/gkavoid are given precedence.

A blank file in /var/symapi/config/gkselect means “no access to the connected Symmetrix systems!” i

32 U41000-J-Z125-4-76


Example

Extract from a gkselect file

3.3.6 Resources needed for operation

In order to operate, SHC-OSD needs a fixed batch task which is automatically started by SHC-OSD V4.0 when the subsystem is started. It is started with the standard job class (for batch under TSOS) and without any time limit.

In order to execute commands, SHC-OSD dynamically generates further tasks.

To operate SHC-OSD, at least 100 Mbytes of additional storage capacity must be defined in the paging area. If a number of SHC-OSD commands are run in parallel, the memory requirements can increase by this size again.

The POSIX file system must be configured to use SYMAPI. In the /var file system, 20-100 Mbytes of free disk space is required for SYMAPI configuration files and logging files. The space requirement is largely dependent on the number of logging files which are stored. The system administrator should delete or archive the logging files regularly. A limit can be set on the number of files in the SYMAPI options. This is described in the options file which is delivered and installed as a standard. For further information, see the manuals of the EMC2 Corporation and the relevant notes in the section “Functions and components” on page 7.

SHC-OSD uses POSIX semaphores (variables which control access to a shared resource). At least 20 free semaphore records should be available for operation (see manuals “POSIX” [2] and [3]).

SHC-OSD uses up to 2 POSIX shared memory segments.

############################################################################# ## SYMAPI GATEKEEPER LIST FILE TEMPLATE ## ## This gatekeeper list file /var/symapi/config/gkselect contains the ## list of the MNs of of all gatekeeper devices used to access all ## SYMMETRIX subsystems to be managed by SHC-OSD using SYMAPI. ## These should be your dedicated gatekeeper devices. ## ## Format: ## <device MN1> ## <device MN2> ## ... ## For example: ## 5700 ## 5431 #############################################################################5420 5421 571C 571D

U41000-J-Z125-4-76 33

Software product SHC-OSD Starting SHC-OSD

3.4 Starting SHC-OSD

After installation, the SHC-OSD subsystem can be called by means of

/START-SUBSYSTEM SUBSYSTEM-NAME=SHC-OSD,VERSION=040

Only the default values are allowed for the other operands of this command.

A successful start is only possible after meeting the following requirements:

● All necessary files are installed

● The version of the subsystem is suitable for the BS2000/OSD version

● The product SYMAPI is installed

● POSIX is available

● The batch job started by SHC-OSD is active and the message NDE1201 indicates that the SHC-OSD program has been initialized successfully

● The SYMAPI library must be located in the POSIX file system under /usr/lib (the POSIX path variable LD_LIBRARY_PATH is ignored)

Due to its dependency on POSIX and SYMAPI-D, SHC-OSD is not started automatically after SYSTEM READY, but has to be started by the system administrator or in the CMDFILE.

3.5 Terminating SHC-OSD

The subsystem can be terminated at any time by means of

/STOP-SUBSYSTEM SUBSYSTEM-NAME=SHC-OSD

DSSM automatically waits for the completion of the last call, either by means of a command or the SVC interface.

Only the default values are allowed for the other operands of this command.

34 U41000-J-Z125-4-76

Working with SHC-OSD Software product SHC-OSD

3.6 Working with SHC-OSD

SHC-OSD operation differs depending on whether or not the units were generated in BS2000/OSD. Usually, you will work with generated units. The Symmetrix functions are available without restriction for generated units.

Unlike the predecessor versions, SHC-OSD as of V3.0 now allows you to display and administer a logical volume directly via the Symmetrix serial number and the internal unit number (internal number of the logical volume). This combination makes it possible to identify each unit uniquely and independently of any host-specific names, such as different MNs at different hosts for the same unit in the Symmetrix.

This functionality is available for generated as well as for non-generated units at the local host and for Symmetrix controllers that can only be accessed indirectly via SRDF connec-tions. This means that it is also possible to display non-generated units and use the Symmetrix SRDF and TimeFinder functions for non-generated units.

Partitioning

BS2000/OSD does not support partitioning.

In the case of other operating systems, it is possible to partition a logical Symmetrix volume and distribute it across multiple, independent file systems.

Problems may occur if Symmetrix volumes are operated via the serial number and the unit number since it is only ever possible to process one logical volume at a time. If partitioning is performed, the specification of the logical volume is more than is required. However, SHC-OSD is unable to recognize this discrepancy. Conse-quently, it is solely the SHC-OSD user’s responsibility to ensure correct addressing.

Meta-volumes

Meta-volumes are supported by BS2000/OSD.

If Symmetrix volumes are operated via the serial number and the unit number, only one logical volume is ever processed at a time. When using meta-volumes, actions are only accepted for the meta-header volume and also implicitly executed for all meta-member volumes of the meta-volume. Actions on meta-member volumes are rejected with the message NDE1154.

At present, all actions on RAID10 volumes are rejected with the message NDE1155.

i

i

U41000-J-Z125-4-76 35

Software product SHC-OSD Working with SHC-OSD

3.6.1 Operating units that have not been generated in BS2000/OSD

Conditions

For SHC-OSD to be able to identify the Symmetrix via the serial number and internal unit number, at least one unit for each local Symmetrix must be known (i.e. generated and attached) in BS2000/OSD.

To declare remote Symmetrix controllers to SHC-OSD, at least one unit must be attached to the local Symmetrix and at least one SRDF controller must be activated, i.e. the Remote Adapter (RA) must have the status ENABLE and the port must be connected (PORT-STATE has the status CONNECTED).

Addressing Symmetrix units via the serial and unit number

In commands, the following syntax should be used to identify the units:

UNIT=*BY-SYMMETRIX(SERIAL-NUMBER=<serialnumber>,LOGICAL-VOLUME=<number>)

The Symmetrix serial number is a twelve-digit number starting with three zeros (000xxyyzzzzz); x identifies the manufacturing site, y the model and z the sequential number of the Symmetrix.

The internal unit number is a hexadecimal number between 0000 and FFFF.

SHC-OSD makes it possible to shorten the serial number. In dialog boxes, you simply need to specify the last three digits since these are usually unique. The serial number is then checked for uniqueness by means of a comparison with the currently known configuration. If it is not unique then the corresponding command is rejected.

In the case of procedures, the twelve-digit number from the the S variables should be used.

If two Symmetrix systems that share the same final three numbers are used and one of these is not attached, then SHC-OSD is unable to recognize the ambiguity. You should therefore first check whether there is only one unit with the corre-sponding number.

Even though the Symmetrix unit number is displayed in the UNIT field on SHOW command outputs to SYSOUT, this field remains empty when the output is sent to S variables.

In messages, the UNIT insert, which previously contained the MN is also empty. However, there are now new inserts that output the serial number and the unit number (see chapter “Messages” on page 255). The ’#’ character is used as a separator between the serial number and the device number. Since the UNIT insert is empty the message may contain spaces.

i

36 U41000-J-Z125-4-76


Example

NDE1015 DEVICE 000183600026#0000 NOT DEFINED.

Where 18 = manufacturing site, 36 = model and 00026 = number of the Symmetrix.

3.6.2 Utilization concept for non-generated units

Central monitoring and control

You can set central monitoring for a Symmetrix with:

/MODIFY-SHC-PROCESSING STATE-CHANGE-POLLING=*PARAMETERS(SELECT-DEVICES=*ALL)

This causes all status changes to non-generated and detached units to be logged additionally at the console by means of NDE0xxx messages.

Central control also enables you to modify SRDF or TimeFinder statuses at detached units.

Security functions are present to prevent any incorrect operation of the units. These are described in detail in the section “SHC-OSD security functions” on page 38.

Controlling remote Symmetrix systems exclusively via SRDF

The main host can also control remote Symmetrix systems exclusively via SRDF (Long Distance SRDF/TimeFinder). This means that the host can control the target units of the associated remote Symmetrix, even if there is no channel connection between the host and the remote Symmetrix (see figure 7). Any necessary actions can be performed centrally.

If, in the event of a catastrophe it is necessary to continue working with the target units in the same BS2000 generation, then only the source units should be generated. If a catastrophe occurs then only the channel connections have to be switched over to the recovery Symmetrix controller. This demands a symmetric configuration of the two Symmetrix systems.

The capabilities for controlling remote Symmetrix systems via SRDF also permit “vaulting scenarios”. In a “vaulting scenario” the remote Symmetrix has no channel connection to the host. The second Symmetrix is located in a fire-resistant area in order to ensure that, at the very least, the data on this Symmetrix is secured even if the first Symmetrix fails as a result of a catastrophe (see figure 8).

The TimeFinder disks at the target units are controlled via the pubset ID. This is achieved by means of the operand SELECT=*TARGET-UNIT in /HOLD-MULTI-MIRRORING and /RESUME-MULTI-MIRRORING (see also the section “Working with TimeFinder” on page 78). The function is available for all target units and their BCV mirrors. They do not have to be generated or attached.

i

U41000-J-Z125-4-76 37


Figure 7: Main host controlling a remote Symmetrix exclusively via SRDF

Figure 8: Remote Symmetrix spatially separate from the local Symmetrix (“data vaulting”)

TS B T S B

B BCVS Source unitT Target unit

200 km

Standbyhost

Mainhost

Local Symmetrix Remote Symmetrix

Local computer center Remote computer center

SRDF(bidirectional)

S B T B

B BCVS Source unitT Target unit

Local Symmetrix Remote Symmetrix

Mainhost

Computer center

Fire-resistant area

SRDF(unidirectional)

38 U41000-J-Z125-4-76


3.6.3 SHC-OSD security functions

Before executing an action command, SHC-OSD checks the configuration of the Symmetrix volumes in order to avoid incorrect operation. There are corresponding security functions for detached and non-generated units. These are described in this section.

Action commands on which a security check is performed

Actions for detached units

Default setting

Only actions for attached units are permitted (as in SHC-OSD V2.0).

The default settings for the security function can be modified using the command /MODIFY-SHC-PROCESSING (see page 125). There is a global operand that applies to all tasks (SYSTEM-ADMIN-SCOPE) and a task-specific operand (TASK-ADMIN-SCOPE). Changes to the security settings are logged at the console. The task-specific settings remain valid until the next /EXIT-JOB or /LOGOFF.

If no setting is made for the current task then the global default setting applies:

TASK-ADMIN-SCOPE=*PARAMETERS(DETACHED-DEVICES=*SYSTEM-ADMIN-SCOPE)

The global default setting can be overridden by a task-specific setting:

TASK-ADMIN-SCOPE=*PARAMETERS(DETACHED-DEVICES=*ACCEPT or *REJECT)


HOLD-MULTI-MIRRORING Splits mult-mirror pair 107


MODIFY-REMOTE-COPY-PARAMETER Changes processing mode and remote copy parameter

118

RESUME-MULTI-MIRRORING Reconstructs multi-mirror pair 135



146

START-MULTI-MIRRORING Generates multi-mirror pair 207

STOP-MULTI-MIRRORING Cancels multi-mirror pair 213

U41000-J-Z125-4-76 39


Only if units are attached is it possible (as before) to check whether a disk formatted for BS2000/OSD is simultaneously being used by another system.

The setting governing logging of status changes at the console remains unchanged and can be modified using the operand STATE-CHANGE-POLLING=*PAR(SELECT-DEVICES=*ALL/*ATTACHED) in /MODIFY-SHC-PROCESSING.

Actions for non-generated units

Default setting

Actions are only permitted for generated units.

The default settings for the security function can be modified using the command /MODIFY-SHC-PROCESSING (see page 125). There is a global operand that applies to all tasks (SYSTEM-ADMIN-SCOPE) and a task-specific operand (TASK-ADMIN-SCOPE). Changes to the security settings are logged at the console. The task-specific settings remain valid until the next /EXIT-JOB or /LOGOFF.

If no setting is made for the current task then the global default setting applies:

TASK-ADMIN-SCOPE=*PARAMETERS(NOT-DEFINED-DEVICES=*SYSTEM-ADMIN-SCOPE)

The global default setting can be overridden by a task-specific setting:

TASK-ADMIN-SCOPE=*PARAMETERS(NOT-DEFINED-DEVICES=*ACCEPT or *REJECT)

If the security functions are not used then the possible consequences of actions for other systems that also use a given disk should also be considered. This is the responsibility of the SHC-OSD user.

The setting governing logging of status changes at the console remains unchanged and can be modified using the operand STATE-CHANGE-POLLING=*PAR(SELECT-DEVICES=*ALL/*ATTACHED) in /MODIFY-SHC-PROCESSING.

If a controller is specified in the command then only the generated units are affected (with the exception of ENABLE-REMOTE-LINK-DIRECTOR and DISABLE-REMOTE-LINK-DIRECTOR). If the Symmetrix serial number and the unit number are defined in the command then the following specification affects generated and non-generated units:

LOGICAL-VOLUME=*ALL-SOURCE-UNITS/*ALL-TARGET-UNITS

i

i

40 U41000-J-Z125-4-76


SHC-OSD reactions

The rules governing how SHC-OSD reacts to certain security settings are described below together with the configuration of the units for commands that trigger TimeFinder or SRDF actions.

The following general rules apply:

● If the unit is affected by the action then it must be attached.

● If it is not attached or not generated then the corresponding security level must be set.

Note:

● When using TimeFinder, the normal units or additional mirror units do not have to be attached if they are not modified.

● If the additional mirror units are to be renamed then they must be generated and attached.

If the additional mirror units are not attached when /HOLD-MULTI-MIRRORING is executed then no internal implicit /UNLOCK-DISK is possible.

In addition to the possible security function settings, the semantics used for actions have also changed.

Displaying units

Default setting

● In the SHOW commands, the followingUNIT=*BY-CONTROLLER / *BY-VOLUME / *BY-PUBSET / <alphanum-name 2..2> /

<x-text 4..4> display only generated units.

● In the SHOW commands, UNIT=*BY-SYMMETRIX displays all the selected units of the Symmetrix.

● Only status changes to attached units are displayed at the console (NDE0xxx messages).

Global modifications to the default display settings for the SHOW commands are possible using /MODIFY-SHC-PROCESSING DEVICE-PRESELECTION=*AN or by specifying the operand SELECT=*BY-ATTRIBUTES(DEVICE=*ANY) in any SHOW command.

The default setting for the display at the console can also be modified using /MODIFY-SHC-PROCESSING.

U41000-J-Z125-4-76 41

Software product SHC-OSD Logging status changes

The following setting also displays status changes to non-generated and detached disks:

/MODIFY-SHC-PROCESSING STATE-CHANGE-POLLING=*PARAMETERS( SELECT-DEVICES=*ALL)

3.7 Logging status changes

SHC-OSD provides monitoring functions that display status changes in the configuration of the Symmetrix controllers, the status of the units, the remote copy operation status and the multi-mirror functionality.

When status changes are detected, a message is output on the console via routing code ’D’. The message describes the detected status changes. Status changes that relate to changes in a host’s access to the Symmetrix subsystem or the availability of the SRDF connection between two Symmetrix subsystems are output as asynchronous queries at the console, using routing code ’D’

The monitoring function is called at intervals by the holder task associated with the SHC-OSD subsystem and implicitly at each command or SVC call of the SHC-OSD subsystem.

The logging of the device-specific changes is dependent on the global subsystem operand SELECT-DEVICES at /MODIFY-SHC-PROCESSING. You can display the settings by means /SHOW-SHC-PROCESSING):

*ALL status changes are displayed for all generated and not generated devices.

*ATTACHED status changes are only displayed for the currently attached devices.

The logging of the status changes is dependent on the global subsystem operand LOG-CHANGES at /MODIFY-SHC-PROCESSING. You can display the settings by means of /SHOW-SHC-PROCESSING).

*ALL-EVENTS All status changes are logged.

*MAJOR-EVENTS-ONLY Only the global status changes are logged for the Symmetrix subsystem, as are the status changes for the TimeFinder and SRDF functions offered by Symmetrix.

42 U41000-J-Z125-4-76

Logging status changes Software product SHC-OSD

The following changes will be recorded:

Global changes to the Symmetrix

NDE0006 SYMMETRIX SUBSYSTEM ’(&07)’ ACCESSIBLE VIA CONTROLLER ’(&01)’

NDE0007 SYMMETRIX SUBSYSTEM ’(&07)’ NO LONGER ACCESSIBLE

NDE0008 HOST ACCESS FOR SYMMETRIX SUBSYSTEM ’(&10)’ CHANGED TO: ’(&08)’

NDE0010 SYMMETRIX SUBSYSTEM ’(&10)’ STATE OF REMOTE LINK DIRECTOR ’(&05)’ CHANGED TO ’(&07)’

NDE0011 GROUP ’(&09)’ OF REMOTE LINK DIRECTORS ’(&08)’ OF SYMMETRIX SUBSYSTEM ’(&07)’ AVAILABLE

NDE0012 GROUP ’(&09)’ OF REMOTE LINK DIRECTORS ’(&08)’ OF SYMMETRIX SUBSYSTEM ’(&07)’ NOT AVAILABLE

Changes to the Symmetrix controllers

NDE0002 SYMMETRIX CONTROLLER ’(&01)’ ACCESSIBLE

NDE0003 SYMMETRIX CONTROLLER ’(&01)’ NO LONGER ACCESSIBLE

Message no. Output for *MAJOR-EVENTS-ONLY

Output for *ALL-EVENTS

Output as a question

NDE0001 - x -

NDE0002-7 x x -

NDE0008 x x x

NDE0010 x x -

NDE0011-12 x x x

NDE0020 x x -

NDE0021-23 - x -

NDE0024 x x -

NDE0025-26 x x -

NDE0030 x x -

NDE0040 - x -

NDE0041-42 - x -

Table 5: Logging status changes depending on the setting of the subsystem-global satting LOG-CHANGES

U41000-J-Z125-4-76 43

Software product SHC-OSD Logging status changes

Changes to the Symmetrix device status

NDE0001 SYMMETRIX DEVICE (&00)(&10)(&09)(&11) STATE CHANGED TO: ’(&07)’

NDE0004 SYMMETRIX DEVICE ’(&00)’ ATTACHED TO CONTROLLER’(&01)’

NDE0005 SYMMETRIX DEVICE ’(&00)’ DETACHED FROM CONTROLLER ’(&01)’

NDE0020 STATE OF ’REMOTE COPY’ CHANGED TO ’(&07)’ FOR DEVICE (&00)(&10)(&09)(&11)

NDE0021 STATE OF REMOTE COPY SOURCE UNIT (&00)(&10)(&09)(&11) CHANGED TO ’(&07)’

NDE0022 STATE OF REMOTE COPY TARGET UNIT (&00)(&10)(&09)(&11) CHANGED TO ’(&07)’

NDE0023 LINK STATE OF REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) CHANGED TO: ’(&07)’

NDE0024 ’TARGET-ACCESS’ FOR REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) CHANGED TO: ’(&07)’

NDE0025 REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) SYNCHRONIZED AGAIN

NDE0026 REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) OUT OF SYNCHRONIZATION

NDE0030 ’MULTI MIRROR’ STATE CHANGED TO ’(&07)’ FOR MULTI MIRROR PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13)

NDE0040 STATE OF INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) CHANGED TO: ’(&08)’

NDE0041 INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) OUT OF SYNCHRONIZATION

NDE0042 INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) SYNCHRONIZED AGAIN

44 U41000-J-Z125-4-76

Diagnostic aids Software product SHC-OSD

3.8 Diagnostic aids

SHC-OSD

SHC-OSD offers the product NDMDAMP, which enables SHC-OSD data to be extracted from a SLED or the running system (see “Diagnostics Handbook” [7]). This information cannot be determined from system dumps, since they contain neither the SHC-OSD admin-istration data in the system part nor that in the SHC task segment).

The tasks generated by SHC-OSD have the job name SHCUSERT.

The POSIX shared memory segment generated by SHC-OSD cannot be identified uniquely on the basis of the ipcs-key: it uses the key 0 (PRIVATE).

SYMAPI

In order to diagnose errors, it is necessary to back up the POSIX semaphore statuses, the configuration files and if necessary the SYMAPI logging files to a file.

A SHELL script /opt/emc/bin/savelogs.sh is supplied for this purpose. This generates a file in the BS2000 file system with all relevant data. The script can also be called from a BS2000 dialog with /CALL-PROCEDURE (SINLIB.SYMAPI.051,SAVELOGS.PROC).

The SYMAPI logging files can grow so large that the file system containing /var/symapi becomes full (POSIX will report this to the operator terminal). The standard supplied options file in /var/symapi/config limits the number of log files retained to 7. In order to change this number, the variable SYMAPI_LOGFILE_RETENTION must be changed in /var/symapi/config.

If additional information is needed from SYMAPI for diagnosis, SHC-OSD offers the

/MODIFY-SHC-PROCESSING command with an option for switching the SYMAPI debugging function on and off and for writing the SYMAPI data structures to a file (see also page 125):

/MODIFY-SHC-PROCESSING SYMAPI-DEBUG=*ON/*OFF

This generates large volumes of data in the POSIX file system (approximately 2 to 10 Mbytes). Before switching debugging on, you should check whether this amount of space is available. The DEBUG option must definitely be deactivated after a problem has been reproduced. The statement

/MODIFY-SHC-PROCESSING SAVE-SYMAPI-DB=*YES

writes the SYMAPI data structures to the file /var/symapi/db/shc_osd040_db.bin. This can then also be used for diagnosis (as a binary file). It only contains information about the Symmetrix configuration.

U41000-J-Z125-4-76 45

Software product SHC-OSD Diagnostic aids

Symmetrix locks

As of SHC-OSD V4.0A, SRDF and TimeFinder actions are locked against simultaneous actions by other tasks or systems by using Symmetrix locks (like other SYMAPI users on other systems).

It may arise from this that either the global Symmetrix lock for SRDF actions (corresponding to lock number 0) or the individual device locks are occupied. This will be indicated by the messages NDE1152 and NDE1153. The name of the system which set the lock cannot be output.

The global Symmetrix locks for SRDF actions are displayed with /SHOW-SYMMETRIX-CONFIGURATION ...,INFORMATION=*LOCKS and reset with /UNLOCK-SYMMETRIX. The global Symmetrix locks are not used for TimeFinder actions.

The device locks are displayed with /SHOW-SYMMETRIX-DEVICE-CONFIGURATION ...,INFORMATION=*LOCKED-DEVICES and reset with /UNLOCK-SYMMETRIX-DEVICE.

46 U41000-J-Z125-4-76

Diagnostic aids Software product SHC-OSD

U41000-J-Z125-4-76 47

4 SRDF (Symmetrix Remote Data Facility)SRDF (Symmetrix Remote Data Facility) supports the data mirroring of a local Symmetrix system (local Symmetrix) to a remote Symmetrix system (remote Symmetrix). This data mirroring feature is also known as remote copying.

The local and remote Symmetrix systems are linked to each other by at least two remote link directors (remote adapter, RA; see figure 9 on page 50) . Each Symmetrix can be linked to up to four others by means of remote links. The connection to the RA can be made using a S type channel or a fibre channel.

In the case of a type-S channel, two Symmetrix systems can be up to 60 km apart and in case of a fibre channel up to 10 km. Greater distances between two Symmetrix systems are possible if telephone lines are attached to additional channel adapters. Regardless of the distance involved, SRDF can be used in unidirectional or bidirectional configurations.

If a Symmetrix fails then the current data (if synchronous SRDF processing mode is used) is still present in the remote Symmetrix. The consequences for the data after a failure are as follows:

● the current data does not have to be read back in,

● no check is necessary to determine whether the backups are usable or consistent,

● there is no need to roll back to an earlier state.

Since SRDF is run by the Symmetrix itself, regardless of the operating system version, any application can use it.

The RAB (Raid Advisory Board) classifies and certifies the RAID variants of different vendors. In the new RAB system of classification, Symmetrix reaches the highest security level DTDS+ (Disaster Tolerant Disk System; “+” stands for greater distances) with SRDF.

SRDF thus allows critical business data to be made available rapidly when either the local Symmetrix or the whole local computer center fails as a result of an outage or a “disaster”.

48 U41000-J-Z125-4-76

SRDF (Symmetrix Remote Data Facility)

Remote copy pair

The remote copy pair consists of the source unit (original) and the target unit (copy of the data) connected by a remote link. The source unit is on the Symmetrix that receives the write jobs in normal remote copy operation. This sends the updated data to the remote Symmetrix, which stores the data on the target unit. The remote copy pair is set up by the service engineer.

Remote link director (remote adapter, RA)

The remote link director can be used as a channel adaptor for S type channels or for fibre channels. It is used to connect the local and remote Symmetrix systems for remote copying.

Each RA has one to four ports, each of which can be used for remote links. The RA has a logical status (ENABLE or DISABLE). The director is only active when the logical status is ENABLE and the status of the port (control panel on the Symmetrix) is CONNECTED.

A remote copy pair has at least two RAs that function as remote links between the source unit and the target unit. The remote link for the pair is AVAILABLE when at least one of the two RAs on each side has the status ENABLE and the ports have the status CONNECTED. If the remote link is not in AVAILABLE status, the source and target unit will not be synchronized.

RA groups

RA groups determine the SRDF link between 2 Symmetrix systems and are configured using Symmetrix microcode. The letters A through H are assigned to them. An RA group contains two or more remote adapters. A remote adapter and each volume used for SRDF can be assigned to only one RA group. You can display the assignment using /SHOW-REMOTE-COPY-STATUS (see page 163) or /SHOW-SYMMETRIX-CONFIGURATION (see page 184).

U41000-J-Z125-4-76 49

SRDF (Symmetrix Remote Data Facility) Interface overview

4.1 Interface overview

4.2 SRDF configurations

SRDF configurations can be unidirectional or bidirectional.

Unidirectional means that when there are two Symmetrix systems, all the source units are located on one of them, and all the target units are on the other. In bidirectional configura-tions, each Symmetrix has both source and target units.

A unit cannot simultaneously be used as a target unit for one link and as a source unit for another.

Each host that is to use SRDF units in the normal remote copy operation must generate the source units in the usual way. The target units must be generated for each host that is to access them. If the same host is to have access to source and target units, both must be generated on the host. It will then be possible to access the target units if the Symmetrix with the source units fails.






118



146






Program Function Page

NDEINF (assembly language macro) Equivalent to the SHOW functions 221

ndeinf.h (C header file) Equivalent to the SHOW functions 253

50 U41000-J-Z125-4-76

SRDF configurations SRDF (Symmetrix Remote Data Facility)

The figure below shows a unidirectional SRDF configuration (simplified diagram). The local Symmetrix contains all the source units. It is connected to the remote Symmetrix via two remote links. The remote Symmetrix contains all the target units.

In this example, only one source unit, one target unit and two remote links are shown: RA 5B and 12B of the local Symmetrix are linked to RA 3B and 14B of the remote Symmetrix. Remote copying is indicated by the black arrows. The main host in the local computer center accesses the source unit. The target unit is accessed via the remote links. If the local computer center fails in the event of a disaster occurring, processing can be continued with the standby host (gray arrows). The standby host in the remote computer center accesses the target unit.

Figure 9: Unidirectional SRDF configuration

Source unit Target unit

Local computer center Remote computer center

Main Standby

Source path(normal

Target path

EA14A

RA14B

RA3B

EA3A

RA12B

EA12A

RA5B

EA5A

Cache Cache

LocalSymmetrix

RemoteSymmetrix

hosthost

EA: Channel adapter for type-S channels; links the host with the cache of the Symmetrix.RA: Remote Adapter (corresponding with remote link director). Channel adapter links the local with the remote Symmetrix.

U41000-J-Z125-4-76 51

SRDF (Symmetrix Remote Data Facility) Remote copy operation

4.3 Remote copy operation

The settings for remote copy operation are specified by means of the remote copy parameters. The remote copy parameters are COPY-MODE, ON-ERROR and PENDING-UPDATES. You can set the COPY-MODE and ON-ERROR remote copy parameters by means of the /MODIFY-REMOTE-COPY-PARAMETER command. The PENDING-UPDATES parameter is always set on the Symmetrix containing the target unit. In the event of a problem, the ON-ERROR and PENDING-UPDATES remote copy parameters have considerable effects on the availability of the source and target unit (see section “ON-ERROR” on page 53 and section “PENDING-UPDATES” on page 53).

/SHOW-REMOTE-COPY-STATUS displays the values of the ON-ERROR parameter in a separate column. The internal Symmetrix parameter PENDING-UPDATES is displayed in the split column PEND-UPD-ON-TARGET. The ALLOW column indicates whether or not PENDING-UPDATES are permitted. The CURR-SIZE column indicates the current size of outstanding write jobs intended for the target unit.

/SHOW-REMOTE-COPY-STATUS UNIT=(587C,587D),INF=*PARAMETERS

4.3.1 COPY-MODE (processing mode)

Remote copying can take place in a synchronous, semi-synchronous or asynchronous processing mode. The initial settings are made by the service engineer. The remote copy processing mode can be changed by means of the COPY-MODE operand in /MODIFY-REMOTE-COPY-PARAMETER.

● SYNCHronous processing modeProcessing mode = synchronous processing. All write jobs are written via the host channel to the cache of the local Symmetrix and are forwarded from there to the cache of the remote Symmetrix. When this has been successfully completed, the main host is notified. Not until then is the next write job executed.

In this processing mode, the data is written on the source unit and the target unit after every successful write job. The synchronous processing mode is the most secure mode.

% -------------------------------------------------------------------------- % SOURCE TARGET VOLUME!COPY-MODE: !ON- !PEND-UPD-ON-TARG: % UNIT UNIT !MODE WR-BUFF P-UPD-LIM!ERROR !ALLOW CURR-SIZE % ========================================================================== % 587C #007C 8BN4.0!SYNCH - - !CONTI !NO 0 MB % 587D #007D 8BN4.1!SYNCH - - !CONTI !NO 0 MB

52 U41000-J-Z125-4-76

Remote copy operation SRDF (Symmetrix Remote Data Facility)

When the synchronous processing mode is set with /MODIFY-REMOTE-COPY-PARAMETER WAIT=*UNTIL-SYNCHRONIZATION, the system waits until the remote copy pair is synchro-nized again. This is only possible when the remote copy status is ACTIVE. Waiting can be canceled again in dialog mode by hitting [K2].

● SEMI-SYNCHronous processing modeProcessing mode = semi-synchronous processing. All write jobs are written via the host channel to the cache of the local Symmetrix. When this has been successfully completed, the main host is notified. After a specific interval and before the next write job is executed, the “old” data is forwarded to the cache of the remote Symmetrix.

The data on the source and target units cannot differ by more than one processing step. This processing mode is good when large distances are involved. Performance is better than in the synchronous processing mode provided the write jobs do not come one after the other in rapid succession.

● ADAPTIVE-COPY processing modeProcessing mode = asynchronous processing. In this processing mode there can be more than one pending write job. You can explicitly set the maximum number of pending write jobs by using the PENDING-UPDATE-LIMIT operand of /MODIFY-REMOTE-COPY-PARAMETER. If the number of pending write jobs exceeds the limit that has been set, the semi-synchronous processing mode is set automatically until the number of pending jobs is under the limit.

This processing mode is available in two submodes, which use different strategies for recording the pending write jobs. You can use /MODIFY-REMOTE-COPY-PARAMETER and Operand WRITE-BUFFER=*DISK or WRITE-BUFFER=*CACHE to set whether the pending write jobs are recorded on the source unit or in the cache of the local Symmetrix.

In the ADAPTIVE-COPY processing mode, performance improves when there is a write load, but remote copy reliability is reduced because there may be a discrepancy of several write jobs between the source and target units.

If the ADAPTIVE-COPY processing mode is terminated, all pending write jobs are trans-ferred before a new write job is forwarded from the host. In the event of the failure of the unprotected source unit (i.e. not protected by RAID) when WRITE-BUFFER=*DISK is set, all the data that has not yet been transferred is lost. The setting WRITE-BUFFER=*DISK should be used for data migration, and the setting WRITE-BUFFER=*CACHE should be used when there is a high write load with reproducible jobs. Since the data that is still to be transferred is buffered in the cache, the cache space available for other actions is reduced. That may have a negative effect on throughput.

U41000-J-Z125-4-76 53


4.3.2 ON-ERROR

The ON-ERROR remote copy parameter allows you to control how the Symmetrix is to respond when part of the remote copy pair is no longer available (in the event of the failure of the remote link or the source or target unit). If the Symmetrix with the source unit fails, this parameter is without effect. The application encounters an error, since neither the remote link nor the source or the target unit is available.

ON-ERROR=*CONTINUE

In the event of a failure, work continues with the remaining unit; the applications are not put on hold. If the target unit fails, a subsequent switchover to the target unit is not possible.

ON-ERROR=*HOLD

In the event of a failure (failure of the remote connection or the target unit), the Symmetrix with the source units rejects all further jobs; the applications are put on hold and have to wait for a response. A decision can then be made (automatically or by the user) as to whether to continue with the source unit alone or to suspend operation in order to preserve data consistency. To continue operation, /MODIFY-REMOTE-COPY-PARAMETER ON-ERROR= *CONTINUE and /SETREMOTE-COPY-ACCESS TARGET-ACCESS=*BY-SOURCE must be recorded.

ON-ERROR=*HOLD must not be specified for paging units. If it is, it may be that no further SHC-OSD commands can be executed.

4.3.3 PENDING-UPDATES

In the event of the failure of the source unit or of the entire local computer center, it is possible to access the data copy directly by means of the target path in the remote computer center. What happens subsequently depends on whether or not the internal setting is ignored.

The internal setting of the PENDING-UPDATES parameter is always made on the Symmetrix with the target unit. This can only be done by the service engineer.

/SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*DIRECT(ALLOW-PEND-UPDATES=*NO) The PENDING-UPDATES parameter setting is not ignored. The target unit rejects the transition to READY and assumes the status DISABLED if there are still pending write jobs on it.

i

54 U41000-J-Z125-4-76


/SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*DIRECT(ALLOW-PEND-UPDATES=*YES) The PENDING-UPDATES parameter setting is ignored. The target unit assumes the status READY, even if there are still pending write jobs on it.

CAUTION! The PENDING-UPDATES parameter setting can result in data inconsistency.

4.3.4 Remote copy status

The /SHOW-REMOTE-COPY-STATUS command indicates the remote copy status.

The remote copy status can be: ACTIVE, ERROR or IN-HOLD.

The status depends on the availability of the physical source units, target units and (at least one) remote link. The physical volumes containing the source or target unit must therefore be ready for operation. It is not enough that the source or target units can be addressed from the host.

ACTIVE

If the source unit and target unit are ready for operation and there is a link between the local and remote Symmetrix systems, the remote copy status is ACTIVE (normal status).

The remote copy status ACTIVE is characterized by the following output: :

Output Output field Command

ACTIVE REM-COPY-STATE SHOW-REMOTE-COPY-STATUS

BY-SOURCE TARGET-ACCESS SHOW-REMOTE-COPY-STATUS

IN-USE1

1 The status IN-USE for the target unit means that the physical drives of the target unit are ready for the remote copy operation. IN-USE does not mean that the target unit is available to the host (see the status display for the /SHOW-SYMMETRIX-DEVICE-CONFIG command on page 192).

SOURCE DEVICE(S) SHOW-REMOTE-COPY-STATUS

IN-USE1 TARGET DEVICE(S) SHOW-REMOTE-COPY-STATUS

AVAILABLE LINK SHOW-REMOTE-COPY-STATUS

YES or NO SYNCH SHOW-REMOTE-COPY-STATUS

READY STATE (for source unit) SHOW-SYMMETRIX-DEVICE-CONFIG

NOT-READY or READ-ONLY STATE (for target unit) SHOW-SYMMETRIX-DEVICE-CONFIG

!

U41000-J-Z125-4-76 55


Examples

/SHOW-REMOTE-COPY-STATUS UNIT=587C

/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=527C,CONF=*REM-COPY-PAIR,INF=*ALL

ERROR

In the event of a failure of one of the units or of the last remote link, the remote copy status is ERROR. You can use /SHOW-REMOTE-COPY-STATUS to display the failed component: one or more components of the remote copy pair will have the status ERROR or NOT-AVAIL. If the remote links are disabled with /DISABLE-REMOTE-LINK-DIRECTOR, the remote copy status is also ERROR. The SYNCH status indicates NO, if the source and the target unit are no longer synchronized.

Example


% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C #007C 8BN4.0!ACTIVE BY-SOURCE!IN-USE IN-USE AVAILABLE! YES

% ---------------------------------------------------------------------------- % UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MULTI- SIZE: % /SERIAL-NO COPY MIRROR CURR./MAXIMUM % ============================================================================ % 527C D3490-30 5200 NOT-READY - T - - / 2348 MB % 587C 8BN4.0 D3490-30 5800 READY - S N 2348/ 2348 MB % ---------------------------------------------------------------------------- % UNIT VOL !INTERNAL-DISK: PHYSICAL-INFORMATION % !TYPE PENDING DA-NO DISK STA !TYPE PENDING DA-NO DISK STA % ============================================================================ % 527C !REMOTE: 0 MB READY!LOCAL : 0 MB 2B D0 READY % 587C 8BN4.0!LOCAL : 0 MB 14A D1 READY!REMOTE: 0 MB READY % !ADD-M : 0 MB 2A C3 READY

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C #007C 8BN4.0!ERROR NONE !IN-USE ERROR NOT-AVAIL! YES

56 U41000-J-Z125-4-76


IN-HOLD

The remote copy status is only IN-HOLD if /HOLD-REMOTE-COPY has been executed. In this case, the status of the target unit is always ERROR (output via /SHOW-REMOTE-COPY-STATUS).

Example


4.3.5 Operating statuses

The following table shows how the operating statuses during remote copy operation can be identified by means of the outputs of /SHOW-REMOTE-COPY-STATUS.

The operating status is indicated by the values for REM-COPY-STATE and TARGET-ACCESS (see the table below). The other fields indicate the device status.

Example

/SHOW-REMOTE-COPY-STATUS UNIT=(587C,587D)

Operating status Output of the /SHOW-REMOTE-COPY-STATUS command

REM-COPY-STATE field TARGET ACCESS field

OK ACTIVE BY-SOURCE

Failure of part of the remote copy pair

ERROR BY-SOURCE or NONE (ON-ERROR=HOLD)

Disaster ERROR NONE

Failure recovery ERROR DIRECT

Failure recovery test IN-HOLD DIRECT

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C #007C 8BN4.0!IN-HOLD BY-SOURCE!IN-USE ERROR AVAILABLE! YES

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C #007C 8BN4.0!IN-HOLD DIRECT !FREE ERROR AVAILABLE! NO % 587D #007D 8BN4.1!ACTIVE BY-SOURCE!IN-USE IN-USE AVAILABLE! YES

U41000-J-Z125-4-76 57

SRDF (Symmetrix Remote Data Facility) Failure scenarios and action taken

4.4 Failure scenarios and action taken to maintain operation

Only the most important failure scenarios are dealt with below:

1. failure of a protected source or target unit (see below)

2. failure of an unprotected source or target unit (see page 58)

3. failure of the remote link (see page 59)

4. failure of the remote Symmetrix (see page 59)

5. failure of the local Symmetrix (see page 59)

6. failure of the main host (see page 60)

7. failure of the local Symmetrix and the main host (computer center failure) (see page 61)

8. failure as a result of switching back to the local Symmetrix (see page 62)

Failover and failback can be automated using the HIPLEX AF product (see manual “HIPLEX AF (BS2000/OSD” [10]), depending on the failure scenarios.

The disaster protection for BS2000/OSD systems is dealt with for all systems in the White Paper “Disaster Recovery Concepts in BS2000/OSD” [14].

If a unit fails, a distinction has to be drawn as to whether or not data protection was provided by RAID1, RAIDS or a spare unit. In the event of the failure of the remote link, there is a difference depending on whether it was just one of several remote links or the last remote link.

After the failure of a Symmetrix or another failure in the local computer center, a check should be carried out to establish whether local troubleshooting will get the application up and running again more quickly than remote recovery. In most cases, local troubleshooting is quicker and remote recovery not to be recommended.

If remote recovery is carried out, you have to take account of the downtime of the application that is necessary in order to switch it over to the remote computer center, start it and switch it back to the local computer center after the problem has been dealt with.

58 U41000-J-Z125-4-76

Failure scenarios and action taken SRDF (Symmetrix Remote Data Facility)

4.4.1 Failure of a protected source or target unit

If the source or target unit is protected locally by RAID1 or RAIDS, it is still possible to access the data after a failure. The applications are not suspended. Data consistency is maintained.

If the failed unit is replaced or a spare unit used, all readable data is copied from the failed unit. The data that cannot be read is copied from the other unit (source or target unit) via the remote link.

4.4.2 Failure of an unprotected source or target unit

The ON-ERROR operand of /MODIFY-REMOTE-COPY-PARAMETER controls how the Symmetrix responds. The initial settings of the operands are made by the service engineer.

The following applies to an unprotected source unit: data can only get lost in the ADAPTIVE-COPY processing mode when WRITE-BUFFER=*DISK is set.

In the event of both the source unit and the target unit failing, operation cannot be maintained. The output of /SHOW-REMOTE-COPY-STATUS shows the value NONE for TARGET-ACCESS.

The setting for the ON-ERROR operand determines what happens in this case.

/MODIFY-REMOTE-COPY-PARAMETER ON-ERROR=*CONTINUE

In the event of a failure, operation continues with the remaining unit only; the applications are not put on hold. If the target unit fails, it is not possible to switch over to the target unit subsequently.

/MODIFY-REMOTE-COPY-PARAMETER ON-ERROR=*HOLD

The Symmetrix with the source units rejects all the subsequent jobs; the applications are put on hold and have to wait for a response. The source unit assumes the status REMOUNT.

A decision can then be made (automatically or by the user) as to whether to continue with the source unit alone or to suspend operation in order to preserve data consistency. ON-ERROR=*HOLD must not be specified for paging units. If it is, it may be that no further SHC-OSD commands can be executed.

To continue operation, the following commands must be entered:/MODIFY-REMOTE-COPY-PARAMETER ON-ERROR=*CONTINUE /SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*BY-SOURCE

U41000-J-Z125-4-76 59


4.4.3 Failure of the remote link

The failure of an individual remote link has the same effect as the failure of a protected unit (see section “Failure of a protected source or target unit” on page 58).

The failure of the last remote link has the same effect as the failure of an unprotected unit (see section “Failure of an unprotected source or target unit” on page 58).

4.4.4 Failure of the remote Symmetrix

The failure of the remote Symmetrix has the same effect as the failure of an unprotected unit (see section “Failure of an unprotected source or target unit” on page 58).

4.4.5 Failure of the local Symmetrix

In the event of the failure of the local Symmetrix, processing can be resumed quickly with the target units of the remote Symmetrix. There may be data inconsistency is the semi-synchronous or asynchronous processing mode was set before the local failure, or if the local failure was preceded by the failure of the remote link or the target unit. If paging is affected, the main host also fails (see section “Failure of the local Symmetrix and the main host (computer center failure)” on page 61).

Actions on the main host

1. Use /ATTACH-DEVICE to attach the target units (see manual “Commands” [1])

2. Set the target units to READY.If the remote Symmetrix contains only target units that are affected by the failure, the entire remote Symmetrix can be specified. All affected devices will be switched simul-taneously

/SET-REMOTE-COPY-ACCESSUNIT=*BY-SYMMETRIX(SERIAL-NUMBER=<serial# of the remote Symmetrix>,LOGICAL-VOLUMES=*ALL-TARGETS),TARGET-ACCESS=*DIRECT

The values DETACHED-DEVICES=*ACCEPT and NOT-DEFINED-DEVICES=*ACCEPT must be set for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE when this function is used.

60 U41000-J-Z125-4-76


If not all the target units of the remote Symmetrix are affected by the failure, the units must be specified separately. The selection of devices depends on the settings for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE with:

/SET-REMOTE-COPY-ACCESS UNIT=*BY-CONTROLLER(CONTROLLER=<MN of controller with target unit>) /

*BY-VOLUME(VOLUME=<vsn>) / *BY-PUBSET(PUBSET=<cat-id>) /<MN of the target unit>

,TARGET-ACCESS=*DIRECT

If the target unit was not synchronized with the source unit, the transition to READY is rejected when PENDING-UPDATES are not allowed for this unit. This setting can be overridden by means of the following command:

/SET-REMOTE-COPY-ACCESSUNIT=*BY-CONTROLLER(CONTROLLER=<MN of controller with target unit>) /


,TARGET-ACCESS=*DIRECT(ALLOW-PEND-UPDATES=*YES)

The *BY-VOLUME and *BY-PUBSET operands can only be used if the target unit was READ-ONLY and is unique or the source unit was accessible (i.e. that the VSN or pubset ID was readable there).

3. Check data integrity (see section “Data integrity after a failure” on page 64)

4. Start importing of the pubsets and applications

4.4.6 Failure of the main host

In the event of the failure of the main host, no data inconsistency occurs, since operation is interrupted. The main host must be restarted.

If it is not possible to restart the main host and it is necessary to switch over to the standby host then remote copy operation must first be interrupted with /HOLD-REMOTE-COPY. The actions at the standby host are then performed as described in section section “Failure of the local Symmetrix and the main host (computer center failure)” on page 61.

U41000-J-Z125-4-76 61


4.4.7 Failure of the local Symmetrix and the main host (computer center failure)

In the event of the failure of the local computer center, processing can be continued on the standby host.If the home pubset of the main host has been duplicated with SRDF, and if the standby host is to be started up with the same home pubset, another, “small” system is required in order to activate the target path before startup (/SET-REMOTE-COPY-ACCESS with operand TARGET-ACCESS= *DIRECT).Data inconsistency can occur if the semi-synchronous or asynchronous processing mode was set before the local failure, or if the local failure was preceded by the failure of the remote link or the target unit.

Actions on the standby host

1. Use /ATTACH-DEVICE to attach the target units (see manual “Commands” [1])

2. Activate the target path (set target units to READY).If the remote Symmetrix contains only target units that are affected by the failure, the entire remote Symmetrix can be specified. The switchover is performed for all units in question at the same time.

/SET-REMOTE-COPY-ACCESSUNIT=*BY-SYMMETRIX(SERIAL-NUMBER=<serial# of the remote Symmetrix>,LOGICAL-VOLUMES=*ALL-TARGETS),TARGET-ACCESS=*DIRECT

The values DETACHED-DEVICES=*ACCEPT and NOT-DEFINED-DEVICES=*ACCEPT must be set for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE in /MODIFY-SHC-PROCESSING when this function is used.

If not all the target units of the remote Symmetrix are affected by the failure, the units must be specified separately. The selection of the devices depends on settings for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE with:



,TARGET-ACCESS=*DIRECT

The *BY-VOLUME operand can only be used if the target unit was READ-ONLY and it is unique or if the source unit was accessible, i.e. the VSN on the source unit was readable.

The *BY-PUBSET operand can only be used if the source unit was accessible and the pubset is imported on that host.

62 U41000-J-Z125-4-76


If the target unit was not synchronized with the source unit, the transition to READY is rejected when PENDING-UPDATES are not allowed for this unit.

This setting can be overridden by means of the following command:



,TARGET-ACCESS=*DIRECT(ALLOW-PEND-UPDATES=*YES)

3. Check data integrity (see page 64)

4. Start importing of the pubsets and applications

4.4.8 Failure as a result of switching back to the local Symmetrix

If the local Symmetrix or local computer center is ready for operation again, processing can be switched to the local Symmetrix and the local computer center again. The applications must be terminated on the standby host and restarted on the main host. If the home pubset is also affected, the standby host must be shut down.

Actions in the remote computer center

1. Terminate the applications, and export the pubsets

2. Switch over to the source path (i.e. set the target unit to NOT-READY or READ-ONLY).If the remote Symmetrix contains only target units that are affected by the failure, the entire remote Symmetrix can be specified. The selection of the devices depends on the settings for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE with:

/SET-REMOTE-COPY-ACCESSUNIT=*BY-SYMMETRIX(SERIAL-NUMBER=<serial# of the remote Symmetrix>,LOGICAL-VOLUMES=*ALL-TARGETS),TARGET-ACCESS=*BY-SOURCE

The values DETACHED-DEVICES=*ACCEPT and NOT-DEFINED-DEVICES=*ACCEPT must be set for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE when this function is used.

If the default setting is used then all the units that are generated in BS2000/OSD are set to the status NOT-READY and all others to the status READ-ONLY. Target units in BS2000/OSD must have the status NOT-READY, as otherwise duplicate (i.e. non-unique) VSNs would occur in the system. The status READ-ONLY is required for other target units as these would not otherwise be recognized by the system in question. Target units that are not correctly covered by the default setting must be processed separately.

U41000-J-Z125-4-76 63


If not all the units of the remote Symmetrix are target units affected by the failure, the units must be specified separately. The units are selected according to the settings for SYSTEM-ADMIN-SCOPE or TASK-ADMIN-SCOPE with


*BY-VOLUME(VOLUME=<vsn>) / *BY-PUBSET(PUBSET=<cat-id>) <MN of the target unit>

,TARGET-ACCESS=*BY-SOURCE

3. Enable the remote links on the remote Symmetrix.If the remote Symmetrix contains only target units affected by the failure, all the remote links can be enabled.

/ENABLE-REMOTE-LINK-DIRECTORDIRECTOR=*ALL,SERIAL-NUMBER=<serial# of the remote Symmetrix>

or/ENABLE-REMOTE-LINK-DIRECTORDIRECTOR=*ALL,CONTROLLER-UNIT=<MN of the remote Symmetrix>

If not all the units of the remote Symmetrix are target units affected by the failure, the units must be specified separately.

4. Use /DETACH-DEVICE to detach the target units (see manual “Commands” [1])

Actions in the local computer center

1. Prepare the local Symmetrix:

– Disable all the channels and remote links (in order to prevent accesses).– Reconnect all the channel or remote link cables. – Start up the local Symmetrix.– The service engineer should check the local Symmetrix for damage, including

whether all the tracks on the source unit are readable and whether the local symmetrix is ready for the comparison.

2. Enable the remote links of the local SymmetrixThe local and remote Symmetrix systems begin syncronization. When the remote links are enabled, the data is copied from the target units to the source units.

3. Enable the host channels of the local SymmetrixOnce the synchronization process has begun, the host channels can be set to online.

4. Start up the main host

64 U41000-J-Z125-4-76


5. Attach the source units on the main host and resume processing: /ATTACH-DEVICE (see manual “Commands” [1]).The reconstruction process can be checked by means of the following command

/SHOW-SYMMETRIX-DEVICE-CONFIGUNIT=<MN of the source unit(s) / MN of the target unit(s)>,CONFIGURATION=*REMOTE-COPY-PAIR,INFORMATION=*PHYSICAL

6. Import the pubsets, and start the applications

4.4.9 Data integrity after a failure

Data integrity after a failure is dependent on the processing mode (SYNCH, SEMI-SYNC, ADAPTIVE-COPY) and the number of pending write jobs.

If a link or device error occurs before or during a failure, the source and target units will no longer be synchronized. In other words, if the internal synchronization process is inter-rupted by a failure in the SEMI-SYNCH or ADAPTIVE-COPY processing mode, the source and target units do not contain the same data. This is also the case when the synchronization process started by /RESUME-REMOTE-COPY is interrupted.

The situation is even more complicated if not all the logically interdependent data is located on the same remote copy pair. In the following case, a device or link error occurs while a DB record is being written. The host does not respond to the error and writes the associated LOG record to another remote copy pair that is not affected by the error. The data on the target units is then inconsistent with the DB and LOG records.

There are two ways of avoiding this:

● By using the SYNCH processing mode and protecting the target units with RAID1 or RAIDS. It makes sense to configure the target units containing the logically interlinked data on the same Symmetrix. In this case, only a remote link failure can interrupt operation, and it affects all devices at the same time.

● By using the SYNCH processing mode and entering /MODIFY-REMOTE-COPY-PARAMETER ON-ERROR=*HOLD for all the source units. If a device or link error occurs, host access is interrupted. A decision can then be made as to whether to continue with the source unit only (failure of an individual device, not a disaster) or to suspend operation in order to maintain data consistency.

U41000-J-Z125-4-76 65


4.4.10 Summary of failure scenarios

The following table contains the most important failure scenarios and features. The table on page 66 describes the specified action.

Failure Condition Reported by

Operation inter-rupted?

Effects Response(measure)

Data inconsistency on subsequently switching to targets?

Source or target unit

Protected NJD0012 No - Service engineer(action 1)

No

Unprotected, ON-ERR=*CONT

NJD0012,NDE0020

No Perfor-mance, if source unit is affected

Service engineerNote inconsis-tency (action 2)

Yes, if target unit is affected

Unprotected, ON-ERR=*HOLD

NJD0012,NDE0020

REMOUNT NKVD014

Applications wait

Action 1 or continue with remaining unit

NoYes

Individual remote link

NJD0012,NDE0008,NDE0010

No Writeperformance

Service engineer No

Lastremotelink

ON-ERR=*CONT

NJD0012,NDE0008,NDE0010,NDE0012

No - Service engineerNote inconsis-tency

Yes

ON-ERR=*HOLD

NJD0012,NDE0010,NDE0020,NDE0012

REMOUNT NKVD014

Applications wait for response

Action 1 or continue with remaining unit

NoYes

Symmetrix with source units

NDE0008,PGER message

Yes Action 1 Possible1

1 Data inconsistencies on a subsequent switchover to the targets are possible if synchronous mode is not set or if errors have previously occurred at remote connections or target units.

Local host - .. Yes - Restart No

computer center failure2

2 CC failure: failure of the Symmetrix with source units and failure of the host

.. Yes Action 1 Possible1

Switchover back to local Symmetrix

- Yes Action 2

66 U41000-J-Z125-4-76


Actions to recover from the failure

Action Description Condition What to do Command

1 Switchover to target unit, main host affected

Start up standby host, attach target units

ATTACH-DEVICE

Source and target units were synchronized

Make target units available

SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*DIRECT

Source and target units were not synchronized, inconsistencies acceptable (or reset to last synchroni-zation point)

SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*DIRECT(PEND-UPD-ALLOWED=*YES)

2 Switchover back to the local Symmetrix, operation on standby host

Terminate use of target units

EXPORT-PUBSET

Make target unitsunavailable

SET-REMOTE-COPY-ACCESS TARGET-ACCESS=*BY-SOURCE

Disable all channels and remote links on local Symmetrix

(Service engineer)

Start up local Symmetrix

(Service engineer)

Local Symmetrix OK(checked by service engineer)

Attach and enable remote links

(Service engineer)

Comparison OK / automatic synchronization begun?

Attach channels (Service engineer)

Power up main host (Service engineer)

U41000-J-Z125-4-76 67

SRDF (Symmetrix Remote Data Facility) Testing the recovery procedures

4.5 Testing the recovery procedures

The test scenario differs from a genuine failure in that the local Symmetrix is active during the test. Processing takes place on the source units in the local computer center; the recovery procedures are tested using the target units in the remote computer center.

CAUTION! If the source units are not protected locally by RAID1 or RAIDS, data loss can occur while the source and target units are separated. If a system is started up from a target unit, the SYSID of the pubset must first be changed by means of the /SET-PUBSET-ATTRIBUTES command (see manual “Commands” [1]). Otherwise, problems can occur in the case of units that can be used more than once.

Overview

A recovery procedure consists of the following steps:

● failure detection

● a check to establish whether processing can be continued on the main host (with the source unit)

● interruption of remote copy operation and enabling of the target path

● shutdown of the main host, if necessary

● startup of the standby host and continuation of processing (IPL, attachment, importing, network node change, restart of applications)

The actions you must take to interrupt a remote copy operation and enable the target path are described in section “Interrupting remote copy operation and enabling the target path” on page 68, while the actions pertaining to a recovery of the source and target unit are described in the section “Reconstructing the source unit and target unit after testing” on page 71.

!

68 U41000-J-Z125-4-76

Testing the recovery procedures SRDF (Symmetrix Remote Data Facility)

4.5.1 Interrupting remote copy operation and enabling the target path

Since the local Symmetrix must remain ready for operation during the tests, remote copy operation has to be interrupted.


1. Before remote copy operation is interrupted, the /MODIFY-REMOTE-COPY-PARAMETER command must be specified with the setting ON-ERROR=*CONTINUE, since otherwise the source unit will reject all jobs.

/MODIFY-REMOTE-COPY-PARAMETERUNIT=<MN of the source unit> /

*BY-VOLUME(VOLUME=<vsn>) / *BY-PUBSET(PUBSET=<cat-id>) / *BY-CONTROLLER(CONTROLLER-UNIT=

<MN of controller with source unit>) / *BY-SYMMETRIX(SERIAL-NUMBER=

<serial# of controller with source unit>,LOGICAL-VOLUME=*ALL-SOURCES / <internal device no>)

,ON-ERROR=*CONTINUE

It is important to specify the operand ON-ERROR=*CONTINUE!

2. The source unit and target unit must be synchronized. This requires the processing mode to be set to SYNCH, because pending write jobs could be recorded in the SEMI-SYNCH or ADAPTIVE-COPY processing mode.

/MODIFY-REMOTE-COPY-PARAMETERUNIT=<MN of the source unit> /

*BY-VOLUME(VOLUME=<vsn>) / *BY-PUBSET(PUBSET=<cat-id>) / *BY-CONTROLLER(CONTROLLER-UNIT=

<MN of controller with source unit>) / *BY-SYMMETRIX(SERIAL-NUMBER=

<serial# of controller with source unit>,LOGICAL-VOLUME=*ALL-SOURCES / <internal device no>)

,COPY-MODE=*SYNCH

It is important to specify the operand COPY-MODE=*SYNCH!

3. Terminate applications, if necessary, in order to maintain the data consistency of the source and target unit.

i

i

U41000-J-Z125-4-76 69


4. Check whether the source and target unit are synchronized.

Global check: the field SYNCH indicates YES

/SHOW-REMOTE-COPY-STATUS UNIT=587C,INFORMATION=*SUMMARY

/SHOW-SYMMETRIX-DEVICE-CONFIGUNIT=<MN of the source unit> / <MN of the target unit> ,CONFIGURATION=*REMOTE-COPY-PAIR,INFORMATION=*PHYSICAL

Detailed check: The number of pending write jobs for the target unit must be 0 (see the grayed field in the example below).

Example

[Targets detached!]/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=(587C),CONF=*REM-COPY-PAIR,INF=*ALL

5. Interrupt remote copy operation.

/HOLD-REMOTE-COPYUNIT=<MN of the source unit> / *BY-VOLUME(VOLUME=<vsn>) /

*BY-PUBSET(PUBSET=<cat-id>)

The main host continues processing using only the source units.

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C 527C 8BN4.0!ACTIVE BY-SOURCE!IN-USE IN-USE AVAILABLE! YES /

% ---------------------------------------------------------------------------- % UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MULTI- SIZE: % /SERIAL-NO COPY MIRROR CURR./MAXIMUM % ============================================================================ % 527C D3490-30 5200 NOT-READY - T - - / 2348 MB % 587C 8BN4.0 D3490-30 5800 READY - S N 2348/ 2348 MB % ---------------------------------------------------------------------------- % UNIT VOL !INTERNAL-DISK: PHYSICAL-INFORMATION % !TYPE PENDING DA-NO DISK STA !TYPE PENDING DA-NO DISK STA % ============================================================================ % 527C !REMOTE: 0 MB READY!LOCAL : 0 MB 2B D0 READY % 587C 8BN4.0!LOCAL : 0 MB 14A D1 READY!REMOTE: 0 MB READY % !ADD-M : 0 MB 2A C3 READY

70 U41000-J-Z125-4-76


Example


The information issued corresponds to the view on the remote copy pair and not to that on an individual unit. The /SHOW-SYMMETRIX-DEVICE-CONFIG command (see page 192) supplies detailed information on a unit. For instance, the status TARGET-DEVICE=ERROR means that the remote copy operation has been halted using the /HOLD-REMOTE-COPY command and not that there is an error on the target unit itself.


1. As long as remote copy operation is interrupted, the remote links do not have to be deactivated, but it may be done by the recovery procedures. You should therefore ensure before the test that no other unit is using these remote links.

Enable the target path, which means setting the target units to READY.

/SET-REMOTE-COPY-ACCESSUNIT=<MN of the target unit> / *BY-VOLUME(VOLUME=<vsn>) /

*BY-PUBSET(PUBSET=<cat-id>),TARGET-ACCESS=*DIRECT

Once this command has been executed, the standby host can access the target units. The recovery procedures can now be tested. The main host continues to access the source units, since the /SET-REMOTE-COPY-ACCESS command does not affect the source units if the /HOLD-REMOTE-COPY command has been entered beforehand.

The operand *BY-VOLUME may only be used if the target unit had the status READ-ONLY and is unique or if the source unit was accessible, i.e. the VSN could be read there.

The operand *BY-PUBSET is only usable if the source unit was accessible and the pubset has been imported at this host.

2. If the source unit and target unit were not fully synchronous before /HOLD-REMOTE-COPY was issued, and if PENDING-UPDATES are not allowed, the transition of the target unit to READY is rejected, thus preventing the use of invalid data. This can be overridden by means of the following command.

/SET-REMOTE-COPY-ACCESSUNIT=<MN of the target unit> / *BY-VOLUME(VOLUME=<vsn>) /

*BY-PUBSET(PUBSET=<cat-id>),TARGET-ACCESS=*DIRECT(ALLOW-PEND-UPDATES=*YES)

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C 527C 8BN4.0!IN-HOLD BY-SOURCE!IN-USE ERROR AVAILABLE! YES /

i

U41000-J-Z125-4-76 71


Example


The information issued corresponds to the view on the remote copy pair and not to that on an individual unit. The /SHOW-SYMMETRIX-DEVICE-CONFIG command (see page 192) supplies detailed information on a unit. For instance, the status TARGET-DEVICE=ERROR means that the remote copy operation has been halted using /HOLD-REMOTE-COPY and not that there is an error on the target unit itself.

4.5.2 Reconstructing the source unit and target unit after testing

Before the resumption of remote copy operation, the remote copy pair must be checked for data discrepancies, and a decision has to be made as to whether to accept the differences on the source or on the target unit.


The access of the standby host to the target units must be interrupted. Processing takes place via the source path again. If necessary, enable the remote link (/ENABLE-REMOTE-LINK-DIRECTOR).

/SET-REMOTE-COPY-ACCESSUNIT=<MN of the target unit> / *BY-PUBSET(PUBSET=<cat-id>) /

*BY-VOLUME(VOLUME=<vsn>) ,TARGET-ACCESS=*BY-SOURCE


Check whether there is a data discrepancy between the source unit and target unit.

/SHOW-SYMMETRIX-DEVICE-CONFIGUNIT=<MN of the source unit> / <MN of the target unit>,CONFIGURATION=*REMOTE-COPY-PAIR,INFORMATION=*PHYSICAL

% -------------------------------------------------------------------- % SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH % UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ==================================================================== % 587C 527C 8BN4.0!IN-HOLD DIRECT !FREE ERROR AVAILABLE! YES

i

72 U41000-J-Z125-4-76


Depending on the result of the SHOW output, a decision has to be made as to which action is appropriate.

● Keep the changes on the source units (i.e. all the changes made on the target unit during the recovery tests are rejected).

/RESUME-REMOTE-COPYUNIT=<MN of the source unit> / *BY-VOLUME(VOLUME=<vsn>) /

*BY-PUBSET(PUBSET=<cat-id>),RESTORE=*FROM-SOURCE,WAIT=*UNTIL-SYNCHRONIZATION

● Keep the changes on the target units (i.e. all the changes made on the source unit during the recovery tests are rejected).

– Terminate the applications on the source units (but the source unit should remain attached).

– Start the reconstruction process.

/RESUME-REMOTE-COPYUNIT=<MN of the source unit> / *BY-VOLUME(VOLUME=<vsn>) /

*BY-PUBSET(PUBSET=<cat-id>),RESTORE=*TO-SOURCE,WAIT=*UNTIL-SYNCHRONIZATION

The WAIT operand specifies whether the command is to wait until synchronization is termi-nated (WAIT=*UNTIL-SYNCHRONIZATION) or not (WAIT=*NO). This simplifies the programming of test procedures for recovery procedures, because comprehensive queries regarding the progress of synchronization for the remote copy pair become unnecessary.

U41000-J-Z125-4-76 73

5 TimeFinder (Symmetrix Multi Mirror Facility)TimeFinder allows (additional) copies of the units on a Symmetrix to be created, which can then be processed separately after splitting. TimeFinder always copies a logical unit in its entirety. The unit containing the production data is known as the normal unit and the unit containing the copy of this data as the additional mirror unit or Business Continuance Volume (BCV). Together the normal unit and the additional mirror unit form a multi-mirror pair.

Data evaluation

The additional copy means that important applications can be productive for longer. While the original data is available to the main application, parallel backup and batch evaluations (which usually require the application to be terminated/interrupted) can be carried out on the copy. In other words, it is possible to create a copy of the “live data” of the application in order to test program modifications without reducing the availability of the main application (see figure 10 on page 74).

After completion of separate processing, either the original data or the copy can be updated in order to make the data identical again. If the copy is no longer needed then this additional mirror unit can be used to mirror a different unit.

TimeFinder can also be used in conjunction with SRDF. The unit with the copy can be connected to the SRDF source unit or SRDF target unit.

When using SHC-OSD it is possible to split the multi-mirror pairs of a pubset without inter-rupting normal operation. Halting all input/output operations on all affected units for the duration of the splitting process ensures that data consistency is maintained. This feature can be used in order to generate a consistent standby pubset on the basis of the home pubset.

Data backups and creation of database replicates

The software product HSMS in connection with the CCOPY function, the Symmetrix function TimeFinder can also be used for data backup. Data backup is performed from the split additional mirror units. When the backup process is completed, the multi-mirror pairs are reconstructed automatically. In the case of a fault, the backup can revert to the additional mirror unit status and, in contrast to the backup process with the CCOPY function used until now, this does not create an extra load on the CPU.

74 U41000-J-Z125-4-76

TimeFinder (Symmetrix Multi Mirror Facility)

The operand CONCURRENT-COPY=*YES(WORK-FILE-NAME=*BY-ADD-MIRROR-UNIT) has to be set for the HSMS statement //BACKUP-FILES. This embedding allows TimeFinder to be used transparently to back up SF and SM pubsets.The Symmetrix function, TimeFinder is also supported when saving the data bank systems (e.g.SESAM/SQL Server V3.1. See also the manual “SESAM/SQL Server” [17]).

Figure 10: Effect of the command /HOLD-MULTI-MIRRORING PUBSET=A,NEW-PUBSET=B

Migration

The TimeFinder function can also be used for data migration from one unit to another. In this case, an additional mirror unit is assigned to the unit with the data that is to be migrated. Following the synchronization, the additional mirror unit can be split off again using /HOLD-MULTI-MIRRORING and then assigned to another normal unit with /START-MULTI-MIRRORING. RESTORE=*TO-ORIGINAL copies the data from the additional mirror unit to the new normal unit, which then also contains the migrated data.When copying is completed the additional mirror unit can be split off again using /HOLD-MULTI-MIRRORING and it is then available again for other tasks.

Multi BCV (multi additional mirror units

TimeFinder offers the multi BCV function as a standard. In the Symmetrix, all the normal unit assignments and modification information are administered for a maximum of 16 additional mirror units.

LocalSymmetrix

Host

Add. mirror unitNormal unit

LocalSymmetrix

Host

Add. mirror unitNormal unit

Pubset ID A Pubset ID A Pubset ID B

Channels to local SymmetrixChannels to local Symmetrix

Status after execution of/HOLD-MULTI-MIRRORING

Initial status

U41000-J-Z125-4-76 75

TimeFinder (Symmetrix Multi Mirror Facility) Prerequisites

5.1 Prerequisites

One or more additional mirror units must be configured on the Symmetrix (an interruption-free installation is possible).

A multi-mirror pair cannot be established only when there are already 4 physical disks in use for a logical disk, e.g. SRDF, RAID1 or RAIDS, spare and Symmetrix optimizer.

Figure 11: TimeFinder

Normal unit

Mirror disk

Unused

+

Established

Splitting

Split

Establishing

Separate processing

/START-MULTI-MIRRORING

/HOLD-MULTI-MIRRORING

/RESUME-MULTI-MIRRORING

Unused

/STOP-MULTI-MIRRORING

76 U41000-J-Z125-4-76

Interface overview TimeFinder (Symmetrix Multi Mirror Facility)

5.2 Interface overview

5.3 Device status

A distinction is drawn between a normal unit and an additional mirror unit.

The normal unit contains the original data and may be protected by RAID or SRDF.

The additional mirror unit is used to provide a copy of the data of the normal units that can be held separately. On demand, the copy can be protected by RAID or SRDF. The additional mirror unit can assume one of the following statuses:

● UNUSEDThe additional mirror unit is not connected to a normal unit. SHC-OSD also displays a unit as UNUSED if

– its status is SPLIT and the associated normal unit is used in another multi-mirror pair or

– the assignment is terminated with /STOP-MULTI-MIRRORING

CAUTION! The additional mirror unit can be used by the host, but all data from the additional mirror unit is lost if its status switches to ESTABLISHED.






SHOW-SYMMETRIX-DEVICE-CONFIG Shows Symmetrix configuration 192



UNLOCK-SYMMETRIX-DEVICE Releases device locks 218

Program Function Page

NDEINF (assembly language macro) Equivalent to the SHOW functions 221

ndeinf.h (C header file) Equivalent to the SHOW functions 253

!

U41000-J-Z125-4-76 77

TimeFinder (Symmetrix Multi Mirror Facility) Device status

– UNUSED-LOCKEDCorresponds to the status UNUSED.Additionally, /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING without the operand UNLOCK-ADD-MIRROR=*YES is rejected. This protects the additional mirror unit against “inadvertent” activation of the TimeFinder operation.

● ESTABLISHINGThe additional mirror unit is connected to another normal unit, but the copy operation is not yet completed. It is not available to the host. When the copy operation is completed, the status switches to ESTABLISHED.

● ESTABLISHEDThe additional mirror unit is synchronous with the normal unit. All write jobs on the normal unit are also executed on the additional mirror unit. The additional mirror unit is not directly available to the host. In this status the additional mirror unit can be separated at any time.

● SPLITTINGThe separation or splitting process is not yet completed. Write jobs are executed on the normal unit only and are recorded on the normal unit as pending write jobs for the additional mirror unit. The additional mirror unit is not available to the host. When the splitting process is completed, the status switches to SPLIT.

● SPLITThe additional mirror unit is available to the host. It can be read and updated. All the write jobs on the additional mirror unit and the normal unit are recorded on the other as pending write jobs. In this status the normal unit and the additional mirror unit are processed separately.

– SPLIT-BACKGThe splitting process has been started but has not yet been completed. All write jobs destined for the additional mirror unit and the normal unit are noted as outstanding write jobs for the other unit. In this transitional status, the additional mirror unit can be used when the optimized split function “Instant Split” is used as of microcode 5266 or 5566. However, it is not possible to start TimeFinder operation with a new normal unit.

– SPLIT-LOCKEDCorresponds to the status SPLIT.Additionally, /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING without the operand UNLOCK-ADD-MIRROR=*YES is rejected. This protects the additional mirror unit from being overwritten unintentionally and ensures that the additional mirror unit is available for split processing in the long term.

– SPLIT-LOCKED-BCorresponds to the status SPLIT-BACKG as a transitional status after SPLIT-LOCKED.The split process has been initiated but not yet completed. The additional mirror unit is protected against accidental overwriting and cannot be accessed by the host.

78 U41000-J-Z125-4-76

Working with TimeFinder TimeFinder (Symmetrix Multi Mirror Facility)

● RECONSTRUCTINGThe additional mirror unit is not available to the host. The normal unit is reconstructed by the additional mirror unit. When the reconstruction process is completed, the status reverts to ESTABLISHED.

5.4 Working with TimeFinder

The service engineer must set up a number of additional mirror units (BCV: Business Continuance Volumes) on physical drives for the Symmetrix. The additional mirror units must have the same disk type and capacity as the normal units to which they are assigned. Like any other disk, the additional mirror units must be defined during hardware generation in the files with the I/O configuration data (IOCONF and IOCF).

The SHC-OSD subsystem provides information services and commands for controlling the TimeFinder function. The devices controlled using these commands must be attached to the host.

Detached devices, or those not connected directly to the host can be controlled using /MODIFY-SHC-PROCESSING

5.4.1 Establishing a multi-mirror pair

The current VSN and the formatting of the additional mirror units are not significant.

A distinction is drawn between setting up additional mirror units for the entire pubset or only for one normal unit or more specific normal units.

Entire pubset

There must be an additional mirror unit for each of the pubset’s normal units.

Establishing a multi-mirror pair or pairs

/START-MULTI-MIRRORING PUBSET=<cat-id>,ADDITIONAL-MIRROR-UNIT=<list of MNs of the additional mirror units>

The order of the additional mirror units is determined by the archive number (VSN) of the disks of the pubset. Thus, if the pubset ID or volume set ID is MMF, the first additional mirror unit will be assigned a VSN of MMF.00, the second a VSN of MMF.01, and so on.

U41000-J-Z125-4-76 79

TimeFinder (Symmetrix Multi Mirror Facility) Working with TimeFinder

Individual units

Alternatively, every normal unit can be assigned an additional mirror unit.

Establishing a multi-mirror pair

/START-MULTI-MIRRORING NORMAL-UNIT=<MN of the normal unit>,ADDITIONAL-MIRROR-UNIT=<MN of the additional mirror unit>

The /START-MULTI-MIRRORING command must be issued for all the pubset’s normal units that are to be mirrored.

The multi-mirror pairs can be established during normal processing. The copy process may cause a slight loss of performance.

It is also possible to specify /START-MULTI-MIRRORING when the additional mirror unit is linked to another normal unit, but it must be in SPLIT or SPLIT-LOCKED status for this.

Subsequent operational sequence

When the /START-MULTI-MIRRORING command is executed, the data of the normal unit is copied to the additional mirror unit in the Symmetrix. In other words, the multi-mirror pair is established.

The console message NDE0030 indicates that the copy operation is completed and that the status is ESTABLISHED. On completion of the copy operation, the /SHOW-MULTI-MIRRORING-STATUS command displays the status ESTABLISHED.

Asynchronous command processing

/START-MULTI-MIRRORING with the operand WAIT=*NO specifies that the command will not await the completion of the synchronization process.

The process can be monitored by means of the following command:

/SHOW-MULTI-MIRRORING-STATUS PUBSET=<cat-id>or/SHOW-MULTI-MIRRORING-STATUS UNIT=<list of MNs of the normal units>

80 U41000-J-Z125-4-76


Synchronous command processing

/START-MULTI-MIRRORING with the operand WAIT=*UNTIL-SYNCHRONIZATION specifies that the command awaits the termination of the synchronization process, i.e. it waits for the multi-mirror pair to be ESTABLISHED. In dialog mode, the status can be interrupted with the [K2] key.

Multi BCV

When you call /START-MULTI-MIRRORING then changes to the normal unit compared to all the assigned additional mirror units with the status SPLIT or SPLIT-LOCKED are stored in the Symmetrix. This means that in the event of a new assignment of an additional mirror unit to the normal unit, only those changes that have occurred during the intervening period have to be copied.

Note the following points:

● The relocated additional mirror unit must be in SPLIT status, otherwise the command will be rejected with the message NDE1040.

● MULTI-BCVs are always generated automatically (this can no longer be deactivated).

● If the maximum number of additional mirror units set per normal unit is exceeded with /START-MULTI-MIRRORING, for instance, because different additional mirror units have been assigned, the message NDE1051 is output. The additional mirror units which are no longer required must be released with /STOP-MULTI-MIRRORING

● Only one additional mirror unit is generally ever in ESTABLISHED status at any time; the rest are all split from the normal unit and in SPLIT status (see figure 12). When using the concurrent BCV function, a maximum of two additional mirror units can be in ESTAB-LISHED status. This function is tolerated by SHC-OSD V4.0, but is not actively supported. For further information on concurrent BCV, see the manuals of the EMC2 Corporation and the relevant notes in the section “Functions and components” on page 7.

U41000-J-Z125-4-76 81


Figure 12: Example of multiple BCV usage

Note on performance: If possible, the normal unit and the additional mirror unit should not be located on the same physical disks. If optimal synchronization times are to be achieved, then it is better for them to be connected to different disk adapters (DA). The disk adapters should have either an even or odd adapter number.

5.4.2 Splitting a multi-mirror pair

Pubset

1. Begin by checking whether all the pubset’s multi-mirror pairs are synchronized. /SHOW-MULTI-MIRRORING-STATUS must display the status ESTABLISHED, and not ESTABLISHING or RECONSTRUCTING.

2. Then a synchronization point for the data must be created:

– suspend or terminate the applications or

– close all files or

– export the pubset. Only if the pubset is exported is it certain that all the cache data buffered with DAB has been written back (database etc.).

The /HOLD-MULTI-MIRRORING command does not require the pubset to be exported, but you are strongly recommended to do so.

Normal unit Additional mirror units

*PREVIOUS

*OLDEST

*CURRENT

SPLIT

SPLIT

ESTABLISHED

2 p.m.

6 a.m.

11 p.m. (current)

Selection with keyword

Status of the units

Status of copy

i

i

82 U41000-J-Z125-4-76


If the pubset is not exported, note the following:

– Write caching using DAB on Server side must be terminated. In the case of PFA caching, /STOP-PUBSET-CACHING has to be issued, and in the case of ADM caching /STOP-DAB-CACHING (see manual “Commands” [1]).

– If the pubset consists of more than one unit, input and output processes should be held for the duration of the separation. This can be done using /HOLD-MULTI-MIRRORING UNIT=*BY-PUBSET and operand HOLD-IO=*UNTIL-SPLIT.

– The separated pubset on the additional mirror units reacts as though the last import process had not been carried out. Either enter Y in response to message DMS038C or specify the operand SESSION-CHECK-MSG=*NO for /IMPORT-PUBSET (see manual “Commands” [1]). The F5 labels on the disks are reconstructed from the catalog.

– Files on the separated pubset are in the same state as they were on the original pubset at the time the separation took place, i.e. they have possibly not been closed. If the application does not carry the operation out itself, you will need to use /REPAIR-DISK-FILES (same effect as restart after system failure) (see manual “Commands” [1]).

3. If the multi-mirror pairs are synchronized and the data is consistent, the multi-mirror pairs can be split.

If the split pubsets are to be processed in the same session as the originals, the pubset must be renamed. Note the following points:

● The additional mirror units must be generated and attached.

● SF pubsets (single-feature pubsets) can be renamed directly by means of /HOLD-MULTI-MIRRORING . The new pubset ID must be the same length as the old pubset ID.

● The PVSREN program must be used for any other renaming.

● IMON uses the file SYS.IMON.SCI which contains pubset IDs. If the SCI file is located on the pubset that is being split off and renamed then the SCI file must be modified manually with /MODIFY-IMON-SCI (see the “IMON” manual [13]). The PVSREN program does this automatically.

● Regardless of whether you use the PVSREN program or /HOLD-MULTI-MIRRORING for renaming, a number of points must be noted:

– Only the S0 level of the pubset (normal processing level - for more detailed infor-mation see the “HSMS” manual [12]) is duplicated with TimeFinder; the migrated files thus exist only once on the tape and in the HSMS directory.

CAUTION! No files may be migrated or restored on the additional mirror pubset! Otherwise, data may be lost.

!

U41000-J-Z125-4-76 83


– Paging files are renamed automatically. If pubset IDs or VSNs have been programmed into the applications, they must be changed manually.

The PVSREN program can complete renaming operations performed by SHC-OSD for IMON, SYSID and the default pubset for user IDs.

– If a system is to be started from the additional mirror unit, the SYSID must be changed beforehand by means of /SET-PUBSET-ATTRIBUTES (see manual “Commands” [1]).

A unique SYSID is necessary in MSCF environments!

– If no renaming of the pubset is carried out, the additional mirror units cannot be used in the same system, since they have the same VSN. They can be used by another host or a virtual machine.

– If the additional mirror units are to be backed up with the software product FDDRL or if the multi-mirror pairs are to be implicitly split using HSMS then it is possible to rename the additional mirror units (with the NEW-PUBSET=*SPECIAL-VSN operand). This prevents ambiguous VSNs in the system. You will find further information on FDDRL (Fast Disk Dump and ReLoad) in the manual “FDDRL” [11].

Private disks

● Private disks cannot be renamed.

● Applications have to be closed.

● The HOLD-IO operand is not supported.

● Private disks have to be released with /SET-DISK-PARAMETER and operand ASSIGN-TIME=*USER.


The Symmetrix writes all the data from the cache to the normal unit and the additional mirror unit before the split (synchronization point).

The command /UNLOCK-DISK is issued internally for all additional mirror units (see manual “Commands” [1]), provided that they are attached and the identification TSOS comes with the OPERATING privilege.

The new pubset can be imported as soon as the splitting process is completed and the status is SPLIT. The corresponding MRSCAT entry is created automatically or updated.

i

i

84 U41000-J-Z125-4-76


When the status is SPLIT, every change made on the original pubset or the new pubset is recorded as a pending write job on the Symmetrix. No additional space is required in the cache for this.

The console message NDE0030 indicates that the splitting process is completed and that the status is SPLIT. On completion of the splitting process, the status can be displayed by means of /SHOW-MULTI-MIRRORING-STATUS.

Locking additional mirror units

You can use the operand LOCK-ADD-MIRROR=*YES in the /HOLD-MULTI-MIRRORING command to lock a split-off additional mirror unit against an accidental resumption of TimeFinder operation (status SPLIT-LOCKED). You can use the option to make the additional mirror disk available for split processing (in the long term). In order to unlock the unit, the operand UNLOCK-ADD-MIRROR=*YES has to be specified in /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING.

Splitting a pubset while retaining data consistency

Prerequisites

● No DAB write caching may be active

● All sharers are using BS2000/OSD-BC V5.0

● All sharers have started SHC-OSD V4.0

● The command must be executed at the master

● There must be MSCF connections between the master and all sharers

● The pubset must not have the status QUIET

It is possible to split a multi-mirror pair with /HOLD-MULTI-MIRRORING and Operand UNIT=*BY-PUBSET(HOLD-IO=*UNTIL-SPLIT) at a synchronization point without having to interrupt normal operation and without having to export the pubset. The consistent splitting of shared pubsets with multiple sharers in a CCS network is also possible. The function stops all output on the pubset for the duration of the separation. Thus it is possible, for example, to create a consistent copy of the home pubset during operation and then use this in parallel as a standby pubset or back it up.

CAUTION! /RESUME-IO can be used to resume the temporarily halted input/output activity for pubsets. This command is intended for emergency situations only and if used unnecessarily may jeopardize data consistency on the separated additional mirror units.

!

U41000-J-Z125-4-76 85


Optimized copying of additional mirror units

The amount of data copied from the additional mirror unit to the internal mirror disk can be restricted. /HOLD-MULTI-MIRRORING and operand RESTORE-DATA=*MODIFIED-ONLY copies only the data that has been modified. This is only of relevance for additional mirror units that have a second, internal RAID1 or SRDF mirror disk. In the case of /HOLD-MULTI-MIRRORING with RESTORE-DATA=*MODIFIED-ONLY, the changes between the additional mirror unit and the internal mirror disk are recorded in the Symmetrix. The data will be evaluated the next time /HOLD-MULTI-MIRRORING RESTORE-DATA= *MODIFIED-ONLY is executed, i.e. only the data that has been modified will be copied to the second, internal RAID1 or SRDF mirror disk.In the case of /HOLD-MULTI-MIRRORING with the operand RESTORE-DATA=*ALL-DATA, the modifications recorded will be discarded again in the Symmetrix.

Furthermore, for additional mirror units that are at the same time SRDF source units, in /HOLD-MULTI-MIRRORING with RESUME-REMOTE-COPY=*BY-SYSTEM/*BY-USER, it is possible to specify whether data is to be synchronized from the additional mirror unit to the remote Symmetrix automatically or whether the process has to be activated explicitly by the user.

Multi BCV

Since only one multi-mirror pair can be established when using multi BCV, no further operand is necessary. This active pair is split using /HOLD-MULTI-MIRRORING

5.4.3 Reconstructing a multi-mirror pair

If split processing is completed, the multi-mirror pair can be restored. The reconstruction can be started for all the multi-mirror pairs of a pubset or for individual multi-mirror pairs.

The following alternatives are available:

● Copying the data from the normal unit to the additional mirror unit

If all the changes on the additional mirror units are rejected, either all or only the changed data can be copied from the normal units to the additional mirror units.

– Terminate processing on the additional mirror units. Export the pubset. – Copy the changed data or all the data to the additional mirror unit.

/RESUME-MULTI-MIRRORINGUNIT=*BY-PUBSET(PUBSET=<normal cat-id>) / *BY-VOLUME(<vsn>) /

<MN of the normal unit> / *BY-SYMMETRIX(SERIAL-NUMBER=<serial# of the Symmetrix>,

LOGICAL-VOLUME=<# of the logical volume>),RESTORE=*FROM-ORIGINAL,RESTORE-MODE=*MODIFIED-ONLY / *ALL-DATA

86 U41000-J-Z125-4-76


● Copying the data from the additional mirror unit to the normal unit

If all the changes on the normal units are rejected, either all or only the changed data can be copied from the additional mirror units to the normal units.

– Terminate processing on the normal units and the additional mirror units of the pubset. Export both pubsets.

– Copy the changed data or all the data to the normal units. /RESUME-MULTI-MIRRORINGUNIT=*BY-PUBSET(PUBSET=<normal cat-id>) / *BY-VOLUME(<vsn>) /

<MN of the normal unit> / *BY-SYMMETRIX(SERIAL-NUMBER=<serial# of the Symmetrix>,

LOGICAL-VOLUME=<# of the logical volume>),RESTORE=*TO-ORIGINAL,RESTORE-MODE=*MODIFIED-ONLY / *ALL-DATA


During the reconstruction process, the multi-mirror pairs have the status ESTABLISHING or RECONSTRUCTING, depending on the direction of copying. The additional mirror units can no longer be accessed.

The console message NDE0030 indicates that the reconstruction process has been completed and that the status is ESTABLISHED. On completion of the reconstruction process, the status can be displayed by means of /SHOW-MULTI-MIRRORING-STATUS.

Asynchronous command processing

/RESUME-MULTI-MIRRORING with the operand WAIT=*NO specifies that the command will not await the completion of the recovery process.

Synchronous command processing

/RESUME-MULTI-MIRRORING with the operand WAIT=*UNTIL-SYNCHRONIZATION specifies that the command awaits the termination of the recovery process, i.e. it waits for the multi-mirror pair to be ESTABLISHED. In dialog mode, the status can be interrupted with the [K2] key.

Multi BCV

Using the new operand SELECT-ADD-MIRROR in the /RESUME-MULTI-MIRRORING command, it is possible to choose which additional mirror unit is to be used to restore the multi-mirror pair when multi BCV operation is used.

The following operand values are possible: *CURRENT, *PREVIOUS and *OLDEST. For details, see “RESUME-MULTI-MIRRORING” on page 135.

U41000-J-Z125-4-76 87


5.4.4 Unassigning a multi-mirror pair

If the assignment of one or more multi-mirror pairs is no longer required then it can be termi-nated using /STOP-MULTI-MIRRORING. If Multi BCV is active then this command makes it possible to deactivate the current, preceding, oldest or all additional mirror unit assign-ments. In figure 13, the oldest assignment is deactivated using/STOP-MULTI-MIRRORING together with the operand SELECT-ADD-MIRROR=*OLDEST. For details on this command see “STOP-MULTI-MIRRORING” on page 213.

Figure 13: Deactivating the last multi-mirror pair (oldest assignment)

5.4.5 Displaying information on multi-mirror pairs

/SHOW-MULTI-MIRRORING-STATUS indicates the status of multi-mirror pairs.

Example

/SHOW-MULTI-MIRRORING-STATUS *BY-CONTROLLER(CONTROLLER-UNIT=5000)

SYSOUT output

Normal unit Additional mirror units

*CURRENT

UNUSED

ESTABLISHED11 p.m. (current)

Selection with keyword

Status of the units

Status of copy

*PREVIOUSSPLIT2 p.m.

% ------------------------------------------------------------------------% NORMAL- !ADD-MIRROR- !SERIAL-NO !STATE !PENDING-SYNCH % UNIT VOLUME!UNIT VOLUME! ! !NORM-UNIT ADD-MIRR% ========================================================================% ! 50A8 !000282500505!UNUSED ! 0 MB 0 MB% 50BC ! 50C5 !000282500505!ESTABLISHED! 0 MB 0 MB% 50BD ! 50C6 !000282500505!ESTABLISHED! 0 MB 0 MB% 50BE ! 50C7 !000282500505!SPLIT ! 1 MB 148 MB% 50BF ! 50C8 !000282500505!SPLIT ! 1 MB 66 MB

88 U41000-J-Z125-4-76


The fields of the SYSOUT output are explained in the command description on page 157.

When Multi BCV is used, all additional mirror units can be output that were until then stored in a normal unit. This is done using the operand INFORMATION=*ALL-ADD-MIRRORS

Example

/SHOW-MULTI-MIRRORING-STATUS UNIT=5244,INFORMATION=*ALL-ADD-MIRRORS

SYSOUT output

5.4.6 Utilization concepts for the Multi BCV function

The UNIT type pubset is used for the utilization concepts for the Multi BCV function.

It is always necessary to rename the separated additional mirror units.

The position of a separated (split off) additional mirror unit with regard to the normal unit is always relative to the time at which it was split off:

● The most recently separated additional mirror unit with the status SPLIT can be selected using /RESUME-MULTI-MIRRORING or /STOP-MULTI-MIRRORING together with the operand SELECT-ADD-MIRROR=*PREVIOUS. This unit is listed first in the SYSOUT output.

● The first separated additional mirror unit is the one that has had the status SPLIT for the longest and can be selected using /RESUME-MULTI-MIRRORING or /STOP-MULTI-MIRRORING together with the operand SELECT-ADD-MIRROR=*OLDEST. This unit is listed last in the SYSOUT output.

CAUTION! To avoid modifying the relative position and thus guarantee data consistency, the command /RESUME-MULTI-MIRRORING should be run with the operand UNIT=*BY-PUBSET.

% ===========================================================================% NORMAL-UNIT: 5244 NORMAL-VOLUME: OLB.00 SERIAL-NO: 000183500813 % ---------------------------------------------------------------------------% ADD-MIRROR- !STATE !SPLIT-SINCE !PENDING-SYNCH % UNIT VOLUME! !DDDD.HH:MM:SS!CURR: NORM: ADD-M: BACKG: % ---------------------------------------------------------------------------% 52C7 OL1.00!ESTABLISHED ! - ! 0 MB 0 MB 0 MB 0 MB % 52C4 PL1.00!SPLIT ! 0.00:39:19! 0 MB 1 MB 0 MB 0 MB % 52C7 RL1.00!SPLIT ! 0.00:11:59! 0 MB 1 MB 0 MB 0 MB % 52C4 LL1.00!SPLIT ! 1.00:39:19! 0 MB 1 MB 0 MB 0 MB

!

U41000-J-Z125-4-76 89


5.4.6.1 Alternating additional mirror units

If an additional mirror unit (BCV) is used to map precisely one normal unit then it is not possible to access the mirrored data. To ensure that at least one copy of the current data resources is always available online it is possible to use two or more BCV groups in alter-nation (see figure 14). A BCV group comprises the same number of units that are in use for the pubset that is to be backed up.

This alternating use of BCV groups is suitable, for example, for

● the rapid reconstruction of the home pubset or a database

● separate data analysis

● data backup to magtape

Example

The last backup version of the production data should always be available. In addition, the data should always be backed up to tape following synchronization.

Pubset A, which contains the production data, is assigned two BCV groups (B and C, see figure 14). The two groups are then synchronized in alternation with pubset A. During synchronization, a separated, current BCV group is always available.

To achieve this, START-MULTI-MIRROR only needs to be run once for each BCV group. Subsequently, it is possible to control switching between the BCV groups using /HOLD-MULTI-MIRROR and /RESUME-MULTI-MIRROR. If you specify the operand SELECT-ADD-MIRROR=*OLDEST then the process runs independently of the number of employed BCV groups and of the BCV MNs.

If an error occurs at the normal unit, then the data is reconstructed on pubset A from the last BCV group using /RESUME-MULTI-MIRRORING with the operand RESTORE=*TO-ORIGINAL (step 3; not illustrated in figure 14).

1. Installing the BCV groups

/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(2000,2001)/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=C/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(1000,1001)

2. Changing between BCV groups

/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=<B or C>/RESUME-MULTI-MIRRORING PUBSET=A, SELECT-ADD-MIRROR=*OLDEST

3. Reconstructing the last BCV group

/RESUME-MULTI-MIRRORING PUBSET=A, SELECT-ADD-MIRROR=*PREVIOUS, RESTORE=*TO-ORIGINAL

90 U41000-J-Z125-4-76


The multi BCV function causes the changes in pubset A compared to the two BCV groups to be stored in the Symmetrix. Since the default setting for /RESUME-MULTI-MIRRORING is RESTORE-DATA=*MODIFIED-ONLY then only the data that differs between the normal unit and the oldest additional mirror unit is harmonized.

If, for example, seven BCV groups are used then a different one can be updated on each day of the week. The pubset name of the NEW-PUBSET operand can be ascertained, for example, from the day of the week.

Figure 14: Multi BCV with alternating additional mirror units (2 BCV groups)

B

A

C

B

A

C

B

A

C

B

A

C

B

A

C

Aligning A with C Pubset A is synchronized with BCV group C.

BCV group C is not available at the momentBCV group B is currently available and contains the stored data from the earlier process “Aligning A with B”.

Backing up C to tapePubset A is split from BCV group C.BCV group C can now be backed up to tape.

BCV group B remains available.The recency of the stored data is the same as in the earlier process “Aligning A with B”.

Aligning A with BPubset A is synchronized with BCV group B.BCV group B is not currently available. BCV group C is currently available and contains stored data from the earlier process “Aligning A with C”.

Backing up B to tapePubset A is split from BCV group B.BCV group B can now be backed up to tape.

BCV group C remains available.The recency of the stored data is the same as in the earlier process “Aligning A with C”.

U41000-J-Z125-4-76 91


5.4.6.2 Sequential utilization of additional mirror units

The additional mirror units are available for a variety of procedures. Since the individual BCV groups cannot be synchronized and split at the same time, the BCV group with the status SPLIT must always wait for the BCV group with the status SPLITTING. The processing of the BCV groups may be performed in parallel if both BCV groups have the status SPLIT.

Independent procedures

This variant is most easily implemented if the multi-mirror pairs are split in normal operation and the applications do not attach the BCV group until required. It is then necessary to await synchronization and the separation of the units (see figure 15 on page 92).

Example

1. Set up the BCV group

/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(1000,1001)/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=B/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(2000,2001) /HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=C

2. Attach the BCV group for procedure 1

/RESUME-MULTI-MIRRORING PUBSET=A, SELECT-ADD-MIRROR=*OLDEST/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=B

3. Attach the BCV group for procedure 2

/RESUME-MULTI-MIRRORING PUBSET=A, SELECT-ADD-MIRROR=*OLDEST/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=C

92 U41000-J-Z125-4-76


Figure 15: Sequential use of the BCV groups for several processes

B

A

C

B

A

C

B

A

C

B

A

C

B

A

C

Split BCV groupsBCV groups B and C are synchronized The BCV groups have the status SPLIT. At this point, they are available for both procedures.

Aligning A with B: Process 1Pubset A is synchronized with BCV group B.BCV group B is not currently available.BCV group C is currently available for process 2 and contains stored data from the earlier process “Aligning A with C”.

Split BCV groupsBCV groups B and C are synchronized

The BCV groups are now in SPLIT status and are available for both processes.

Aligning A with C for process 2Pubset A is synchronized with BCV group CBCV group C is not currently availableBCV group is currently available for process 1 and contains the stored data from the earlier process “Aligning A with B”.

U41000-J-Z125-4-76 93


Main and subsidiary procedures

In this variant it may be necessary for data backup to be prioritized and, wherever possible, this should be performed using current data. Consequently, the BCV group for the main procedure is usually set up. A subsidiary procedure only runs if it does not disturb the main procedure (see figure 16).

Figure 16: Sequential utilization of the BCV groups for the main and subsidiary procedures

B

A

C

B

A

C

B

A

C

B

A

C

B

A

C

B

A

C

Aligning A with B for the main procedurePubset A is synchronized with BCV group B.BCV group B is not currently available.

BCV group C is currently available and contains the stored data from the earlier “ process “Aligning A with C ... “.

Backing up B to tape for the main procedurePubset A is split from BCV group B.BCV group B can now be backed up to tape.BCV group C currently available and contains the stored data from the earlier process “Aligning A with C ... “.

Aligning A with B for the main procedurePubset A is synchronized with BCV group B.

BCV group B is not currently available. BCV group C is currently available and contains the stored data from the earlier process “Aligning A with C ... “.

Aligning A with C for the subsidiary procedurePubset A is synchronized with BCV group Ct.BCV group C is not currently available.

BCV group B can now be backed up to to tape.

Utilization of C for the subsidiary procedurePubset A is split from BCV group C.

BCV group C can now be used by the subsidiary procedure.BCV group B is currently available and contains the stored data from the earlier process “Aligning A with B ... “.

94 U41000-J-Z125-4-76


If the subsidiary procedure needs to run, it first splits off the main procedure’s BCV group. It then establishes and synchronizes its own BCV group. It then immediately disconnects and re-establishes the main procedure’s disks.

This ensures that when the main procedure’s BCV group is synchronized, the smallest possible number of changes need to be aligned and that the group can be backed up rapidly.

Example

1. Installing the BCV groups

/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(1000,1001)/HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=B/START-MULTI-MIRRORING PUBSET=A, ADD-MIRROR-UNIT=(2000,2001) /HOLD-MULTI-MIRRORING PUBSET=A, NEW-PUBSET=C

2. Setting up the main procedure (e.g. implicitly via HSMS)

/HOLD-MULTI-MIRRORING PUBSET=A,NEW-PUBSET=B/RESUME-MULTI-MIRRORING PUBSET=A

3. Setting up the subsidiary procedureWait until the main procedure’s BCV groups have been synchronized

/HOLD-MULTI-MIRRORING PUBSET=A,NEW-PUBSET=B (as in the main procedure)/RESUME-MULTI-MIRRORING PUBSET=A,

SELECT-ADD-MIRROR=*OLDEST, WAIT=*UNTIL-SYNCH

/HOLD-MULTI-MIRRORING PUBSET=A,NEW-PUBSET=C/RESUME-MULTI-MIRRORING PUBSET=A,SELECT-ADD-MIRROR=*PREVIOUS

The main procedure is independent of the number and names of the employed BCV groups. It always ensures itself the alignment of its own BCV group and thus makes sure that the backed up data is up-to-date. The subsidiary procedure has to know the pubset ID used by the main procedure. The final /RESUME-MULTI-MIRRORING is uncritical since the preceding procedure (main procedure) has to be restarted.

5.4.7 Additional mirror units protected with RAID1 or SRDF

Additional mirror disks that are protected with RAID1 or SRDF are only synchronized with their internal mirror disks (RAID1 or SRDF) when /HOLD-MULTI-MIRRORING is executed. In general all data is copied in this procedure. The /HOLD-MULTI-MIRRORING command with operand RESTORE-DATA=*MODIFIED-DATA can be used to specify that only the data that has been modified is to be copied. From the second separation with /HOLD-MULTI-MIRRORING on, only the modified data is copied to the second mirror disk of the additional mirror unit (see “Optimized copying of additional mirror units” on page 85).

U41000-J-Z125-4-76 95


The remote copy process is interrupted if SRDF is used for the additional mirror units and /START-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING is issued. /SHOW-REMOTE-COPY-STATUS displays the remote copy status IN-HOLD.

CAUTION! After /HOLD-MULTI-MIRRORING, remote copy operation can be resumed. Up to SHC-OSD V3.0 inclusive, this could be initiated implicitly by means of the operand RESUME-REMOTE-COPY=*BY-SYSTEM. This interface is no longer available in SYMAPI. Remote copy operation must therefore be resumed explicitly for the additional mirror units with /RESUME-REMOTE-COPY.

5.4.8 Multi-mirror pairs with SRDF target unit

Additional mirror units can be assigned to the source and the target unit of a remote copy pair. The additional mirror unit and the source unit or the target unit then each form a multi-mirror pair. The source unit or the target unit are also the normal units of the multi-mirror pair.

If a multi-mirror pair consists of a target unit and an additional mirror unit, then the multi-mirror pair cannot be accessed via the VSN or the pubset ID, since the target unit is generally not readable. However, if the source unit is attached, the pubset ID of the source unit can also be specified in the /HOLD-MULTI-MIRRORING and /RESUME-MULTI-MIRRORING commands using the operand SELECT=*TARGET-UNIT (see figure 17 on page 96).

SF pubsets can be renamed implicitly with /HOLD-MULTI-MIRRORING and NEW-PUBSET=<new catid>. Input/output can be stopped on the source unit with /HOLD-MULTI-MIRRORING HOLD-IO=*UNTIL-SPLIT in order to split the units and maintain data consistency.

Prerequisites for addressing a multi-mirror pair with a target unit via the pubset ID or the VSN:

● The source unit is attached.

● If the pubset on the additional mirror units must renamed, they must generated and attached.

● If the pubset on the additional mirror units doesn’t have to be renamed, a channel between the host and the remote Symmetrix is not needed.

● The remote copy operation has to be interrupted for /HOLD-MULTI-MIRRORING (/SHOW-REMOTE-COPY-STATUS indicates the remote copy status IN-HOLD or ERROR) or, if the remote copy operation is active, the synchronous processing mode has to be set and the remote copy pair has to be synchronized.

!

96 U41000-J-Z125-4-76


TimeFinder with SRDF

Without renaming the additional mirror units

The source unit and the target unit form a remote copy pair (figure 17). This can be a “Long-Distance-SRDF” connecting 200 km away, e.g.

Simultaneously, both form a multi-mirror pair:

● the source unit with the additional mirror unit of the local Symmetrix and

● the target unit with the additional mirror unit of the remote Symmetrix.

The host possesses no channels to the remote Symmetrix and cannot therefore access it directly. The target unit cannot be accessed via the VSN or the pubset ID. The source unit has pubset ID A. The multi-mirror pair in the remote Symmetrix is split by means of /HOLD-MULTI-MIRRORING and the operands PUBSET=A,SELECT=*TARGET-UNIT.

Remote copy operation is briefly interrupted internally so that /HOLD-MULTI-MIRRORING can be processed and is then resumed again automatically. Consequently, the source unit and the target unit may not be synchronous for a short while. This procedure means that the status of the target units is always up-to-date although the status may be inconsistent in the event of a catastrophe. The additional mirror units on the remote Symmetrix are consistent and have the status as at the time of the last split.

Figure 17: TimeFinder with SRDF without renaming the additional mirror units

LocalSymmetrix

Host

Channels to local Symmetrix

SRDF connections

RemoteSymmetrix

Target unit /Normal unit

Add. mirror unit

Multi-mirror pair

Source unit /Normal unit

Pubset-ID A

Add. mirror unit

Multi-mirror pair

U41000-J-Z125-4-76 97


With renaming the additional mirror units

The source unit and the target unit form a remote copy pair (figure 18).

Simultaneously, both form a multi-mirror pair:

● the source unit and the additional mirror unit of the local Symmetrix and

● the target unit and the additional mirror unit of the remote Symmetrix.

The host has channels to the remote Symmetrix, thus making this directly accessible from the host.

The target unit cannot be accessed via the VSN or the pubset ID.

The source unit has pubset ID A. The multi-mirror pair in the remote Symmetrix is split by means of /HOLD-MULTI-MIRRORING and the operands PUBSET=A,NEW-PUBSET=C, SELECT=*TARGET-UNIT and the pubset ID of the additional mirror unit is changed to C.

The remote copy operation is briefly interrupted internally so that /HOLD-MULTI-MIRRORING can be processed and is then resumed again automatically. Consequently, the source unit and the target unit may not be synchronous for a short while.

Figure 18: TimeFinder with SRDF, renaming the additional mirror units

The multi-mirror pair in the local Symmetrix is separated by issuing a further /HOLD-MULTI-MIRRORING PUBSET=A,NEW-PUBSET=B and the pubset ID of the additional mirror unit is changed to B.

LocalSymmetrix

Host

Channels to local Symmetrix

SRDF connections

Channels to remote Symmetrix (necessary because of renaming)

RemoteSymmetrix

Target unit /Normal unit

Pubset-ID C

Add. mirror unit

Multi mirror pair

Source unit /Normal unit

Pubset-ID BPubset-ID A

Add. mirror unit

Multi mirror pair

98 U41000-J-Z125-4-76


As a consequence, the units can be utilized, for instance, as follows:

● the source unit (with pubset ID A) for the main application

● the additional mirror unit of the local Symmetrix (with pubset ID B) for backup

● the target unit as a copy in the case of a disaster

● the additional mirror unit of the remote Symmetrix (with pubset ID C) for evaluations

/RESUME-MULTI-MIRRORING with the operand RESTORE=*TO-ORIGINAL can only be used for an SRDF target unit if the target unit has the status READY, i.e. if the remote copy status is *IN-HOLD or *ERROR and the value of TARGET-ACCESS is *DIRECT. Thus, for example, if a catastrophe occurs, the last consistent state of the additional mirror unit can be copied to the target unit. This makes it possible to copy the data from the additional mirror unit at the target unit to the source unit in a number of separate steps.

U41000-J-Z125-4-76 99

6 CommandsThis chapter contains the description of the syntax and semantics of all SHC-OSD commands. You will find an overview of the commands on page 100.

The commands are described in alphabetical order, and the descriptions have the following structure:

● the command’s name and function

● a description of the command function

● an illustration of the command’s format

● a description of the command’s operands

● information to the Command processing, should it be needed

● some example(s), should they be required

● for SHOW commands: output formats

● for SHOW commands: output in S variables

● a description of the command return codes

In chapter “Appendix” on page 285 you will find general explanations to the metasyntax, the command returncodes and to the representation of S variables.

100 U41000-J-Z125-4-76

Commands

Command overview







118

MODIFY-SHC-PROCESSING Changes the internal settings of SHC-OSD 125





146










U41000-J-Z125-4-76 101

Commands DISABLE-REMOTE-LINK-DIRECTOR

DISABLE-REMOTE-LINK-DIRECTORDisable remote link directors

/DISABLE-REMOTE-LINK-DIRECTOR disables one or all of the remote link directors (remote adapter, RA) of a Symmetrix controller. After execution of the command, the directors are offline. Remote copy operation is then no longer possible via these remote link directors. If the last remote link director is disabled, the source unit and target unit are no longer synchronized, and the remote copy pair switches to the remote copy status ERROR.

This command is used for failure recovery or in order to change the remote link status after a failure.

In the case of a Symmetrix system that can only be accessed via SRDF, the last remote link director is not disabled, since then it would no longer be possible to access the remote Symmetrix. If the last remote link director were to be disabled, then this status could not be reversed by the same host.

At startup of a failed Symmetrix, the disabling of its remote link directors prevents the two Symmetrix systems from being connected automatically.

Domain: DEVICE

Privileges: TSOS

DISABLE-REMOTE-LINK-DIRECTOR

DIRECTOR = *ALL / < alphanum-name 1..3>

,UNIT = *BY-CONTROLLER(...) / *BY-SYMMETRIX(...)

*BY-CONTROLLER(...)

CONTROLLER-UNIT = <alphanum-name 2..2> / <x-text 4..4>

*BY-SYMMETRIX(...)

SERIAL-NUMBER = <alphanum-name 3..12>

102 U41000-J-Z125-4-76

DISABLE-REMOTE-LINK-DIRECTOR Commands

DIRECTOR =Specifies which remote link directors are to be disabled. Each remote link director is processed individually. A value range of 1A...16A, 1B...16B, ..., to 1H...16H can be specified for the Symmetrix systems of the series 8000. A value range of 1A...16A and 1B...16B for the Symmetrix systems of the series 5000.

DIRECTOR = *ALLDisables all the remote link directors of a Symmetrix controller.

DIRECTOR = <alphanum-name 1..3>The name of the remote link director to be deactivated.

UNIT =Selects the Symmetrix system by means of the mnemonic name of the emulated controller (*BY-CONTROLLER) or the Symmetrix serial number (*BY-SYMMETRIX).

UNIT = *BY-CONTROLLER(...)Selects the Symmetrix system by means of the mnemonic name of the emulated controller. This is not possible when connecting the Symmetrix via Fibre Channel to the servers of the SX line. See also the section “Configuration on Business Servers of the SX line” on page 16.

CONTROLLER-UNIT = <alphanum-name 2..2> / <x-text 4..4>The mnemonic name of the Symmetrix controller on which the remote link director is to be disabled.

UNIT = *BY-SYMMETRIX(...)Selects the Symmetrix system by means of its serial number.

SERIAL-NUMBER = <alphanum-name 3..12>The Symmetrix serial number (make sure it is unique!).

Command processing

The following messages are output to SYSOUT for each director and distributed via routing code ’0’, i.e. they were only logged in the CONSLOG file. You will find detailed information concerning the CONSLOG file (logging file) in the manual “Introductory Guide to Systems Support” [5].

● For successful processing:

NDE1074 (&04) PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’

● For unsuccessful processing:

NDE2008 COMMAND ’(&04)’ NOT PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’

U41000-J-Z125-4-76 103

Commands DISABLE-REMOTE-LINK-DIRECTOR

Examples

/DISABLE-REMOTE-LINK-DIRECTOR DIRECTOR=*ALL,UNIT=*BY-CONTROLLER( CONTROLLER-UNIT=S4)

/DISABLE-REMOTE-LINK-DIRECTOR DIRECTOR=15A,CONTROLLER-UNIT=S4

/DISABLE-REMOTE-LINK-DIRECTOR DIRECTOR=12D,SERIAL-NUMBER=525

Command return codes

(SC2) SC1 Maincode Meaning0 CMD0001 Command successfully executed

1 0 NDE2003 Command successfully executed, no processing necessary2 0 NDE2004 Command successfully executed but not yet completed

1 CMD0202 Syntax error32 NDE2002 Internal error64 CMD0087 Function not permitted in the current input mode or with the current

task privileges 64 CMD0216 Required privilege not available 64 NDE1002 Controller not found 64 NDE1010 Microcode status not supported (too low or too high)64 NDE1023 Director is not a remote link director of the device controller 64 NDE1080 No remote link director for the specified device controller64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1130 Last remote link director is not disabled64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful 64 NDE2001 Command not executed 64 NDE2011 No Symmetrix license entered

104 U41000-J-Z125-4-76

ENABLE-REMOTE-LINK-DIRECTOR Commands

ENABLE-REMOTE-LINK-DIRECTOREnable remote link directors

/ENABLE-REMOTE-LINK-DIRECTOR enables one or all of the remote link directors of a Symmetrix controller. After execution of the command, the directors are online.

The prerequisite for successful processing is that the remote links of the remote link director (remote adapter, RA) must be physically connected.

This command is used for failure recovery or in order to change the remote link status after a failure.

DIRECTOR =Specifies which remote link directors are to be enabled. Each remote link director is processed individually. A value range of 1A...16A, 1B...16B, ..., to 1H...16H can be specified for the Symmetrix systems of the series 8000. A value range of 1A...16A and 1B...16B for the Symmetrix systems of the series 5000.

DIRECTOR = *ALLEnables all the remote link directors of a Symmetrix controller.

DIRECTOR = <alphanum-name 1..3>The name of the remote link director to be enabled.

Domain: DEVICE

Privileges: TSOS

ENABLE-REMOTE-LINK-DIRECTOR

DIRECTOR = *ALL / < alphanum-name 1..3>

,UNIT = *BY-CONTROLLER(...) / *BY-SYMMETRIX(...)

*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


U41000-J-Z125-4-76 105

Commands ENABLE-REMOTE-LINK-DIRECTOR

UNIT =Selects the Symmetrix system by means of the mnemonic name of the emulated controller (*BY-CONTROLLER) or the Symmetrix serial number (*BY-SYMMETRIX).

UNIT = *BY-CONTROLLER(...)Selects the Symmetrix system by means of the mnemonic name of the emulated controller. This is not possible when connecting the Symmetrix via Fibre Channel to the servers of the SX line. See also the section “Configuration on Business Servers of the SX line” on page 16.

CONTROLLER-UNIT = <alphanum-name 2..2> / <x-text 4..4>The mnemonic name of the Symmetrix controller on which the remote link director is to be enabled.

UNIT = *BY-SYMMETRIX(...)Selects the Symmetrix system by means of its serial number.


Command processing

The following messages are output to SYSOUT for each director and distributed via routing code ’0’, i.e. they were only logged in the CONSLOG file.


NDE1074 (&04) PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’


NDE2008 COMMAND ’(&04)’ NOT PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’

Examples

/ENABLE-REMOTE-LINK-DIRECTOR DIRECTOR=*ALL,CONTROLLER-UNIT=S5

/ENABLE-REMOTE-LINK-DIRECTOR DIRECTOR=15A,CONTROLLER-UNIT=S4

/ENABLE-REMOTE-LINK-DIRECTOR DIRECTOR=12D,SERIAL-NUMBER=525

106 U41000-J-Z125-4-76

ENABLE-REMOTE-LINK-DIRECTOR Commands





task privileges64 CMD0216 Required privilege not available64 NDE1002 Controller not found64 NDE1010 Microcode status not supported (too low or too high)64 NDE1023 Director is not a remote link director of the device controller64 NDE1080 No remote link director for the specified device controller64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2011 No Symmetrix license entered

U41000-J-Z125-4-76 107

Commands HOLD-MULTI-MIRRORING

HOLD-MULTI-MIRRORINGSplit multi-mirror pair

/HOLD-MULTI-MIRRORING splits one or more multi-mirror pairs consisting of a normal unit and an additional mirror unit. After a successful split, the additional mirror unit is available to the host and contains all the data of the normal unit at the time at which the command was processed.

The normal units of the multi-mirror pairs must always be specified for the UNIT operand. If the SRDF function is used, then the specified normal unit may also be the source unit of a remote copy pair (see also “Multi-mirror pairs with SRDF target unit” on page 95). The operand SELECT=*TARGET-UNIT can be used to select the multi-mirror pair at the target unit. The additional mirror units are assigned automatically.

The command is only executed when the multi-mirror pair has the status ESTABLISHED. A synchronization point should be created for the data before the command is called. In order to achieve this, the applications must be terminated, all files must be closed, and the pubset must be exported. Only in the exported status can you be sure that all the data that has been buffered with DAB has been written back from the cache (database etc.).

Only pubsets that have been completely mirrored are processed. The additional mirror pubset on the additional mirror unit can be renamed directly by means of the NEW-PUBSET operand. Only SF pubsets can be implicitly renamed.

While the multi-mirror pair is split, the changed data on the normal unit and the additional mirror unit is recorded for the other unit in each case as pending write jobs. This information is used to accelerate the reconstruction process with /RESUME-MULTI-MIRRORING.

In the case of additional mirror units which are also SRDF source units, remote copy operation can be resumed when the multi-mirror pairs have been split. This can no longer be performed implicitly by the system (as in SHC-OSD V3.0) but must be initiated explicitly with /RESUME-REMOTE-COPY.

SHC-OSD checks the global and task-specific security settings before the /HOLD-MULTI-MIRRORING command is executed. The current settings can be displayed with /SHOW-SHC-PROCESSING (see also page 179). The security settings are defined by means of the operands TASK-ADMIN-SCOPE and/or SYSTEM-ADMIN-SCOPE in /MODIFY-SHC-PROCESSING (see also page 125ff).

Domain: DEVICE

Privileges: TSOS

108 U41000-J-Z125-4-76

HOLD-MULTI-MIRRORING Commands

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume.

UNIT = *BY-VOLUME(...)Selects the units by means of a specific archive number.

VOLUME = <vsn 1..6>The archive number of the volume.

UNIT = *BY-PUBSET(...)Selects the units by means of a pubset ID or volume set ID. The SF/SM pubset is locked against reconfiguration while a command is being executed.

PUBSET = <cat-id 1..4>The pubset ID or the volume set ID.

NEW-PUBSET =The catalog ID of the additional mirror pubset of the additional mirror unit(s).

NEW-PUBSET = *SAMEThe additional mirror pubset of the additional mirror unit(s) is not renamed; it retains the same name.

HOLD-MULTI-MIRRORING

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-SYMMETRIX(...) / <alphanum-name 2..2> / <x-text 4..4>

*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)

PUBSET = <cat-id 1..4>

,NEW-PUBSET = *SAME / *SPECIAL-VSN / <cat-id 1..4>

,HOLD-IO = *NO / *UNTIL-SPLIT

*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = <x-text 1..4>

,LOCK-ADD-MIRROR = *NO / *YES

,RESTORE-DATA = *ALL-DATA / *MODIFIED-ONLY

,SELECT = *STD / *TARGET-UNIT

U41000-J-Z125-4-76 109


NEW-PUBSET = *SPECIAL-VSN*SPECIAL-VSN renames all the volumes of the additional mirror unit in order to avoid confusion with the original. The period in a VSN is changed into a colon and, in the case of single-digit catalog IDs, the string “PUB” is changed into “P:B”.

NEW-PUBSET = <cat-id 1..4>The additional mirror pubset of the additional mirror unit(s) is renamed. In other words, the new catalog ID must be specified explicitly. The catalog ID must have the same length as specified for the PUBSET operand. Only SF pubsets can be specified, and the new additional mirror pubset will be also a SF pubset. An existing MRSCAT entry is used if it is of the right type. If it is not, it is deleted and created again.

HOLD-IO =Processing of input/output operations on the multi-mirror pair while the pair is being split (see “Splitting a pubset while retaining data consistency” on page 84).

HOLD-IO = *NOInput/output on the multi-mirror pair continues as before. This may lead to data incon-sistencies on the additional mirror units in applications that were not stopped before the pair was split.

HOLD-IO = *UNTIL-SPLITInput/output on the multi-mirror pair is halted until the multi-mirror pair of the pubset is SPLIT. Subsequently, input/output on the normal units continues. If an error occurs when the inputs/outputs are halted or resumed, the command is aborted with an error. It may be necessary to restart input/output activity with/RESUME-IO.

UNIT = *BY-SYMMETRIX(...)Specifies the unit by means of the Symmetrix serial number and the Symmetrix internal number of the logical volume.


LOGICAL-VOLUME = <x-text 1..4>The Symmetrix internal number of the logical volume.

UNIT = <alphanum-name 2..2> / <x-text 4..4>Selects the unit by means of the mnemonic device name of the logical volume.

110 U41000-J-Z125-4-76


LOCK-ADD-MIRROR =Specifies whether the additional mirror unit is protected against unintentional overwriting by /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING.

LOCK-ADD-MIRROR = *NOThe additional mirror unit is not locked.

LOCK-ADD-MIRROR = *YESThe additional mirror unit is locked.

RESTORE-DATA =Specifies whether only the modified data or all data is to be copied to the internal RAID1 or SRDF mirror disks of the additional mirror unit.

RESTORE-DATA = *ALL-DATAAll of the data is copied.

RESTORE-DATA = *MODIFIED-ONLYOnly modified data is copied.

SELECT =Selection of the multi-mirror pairs.

SELECT = *STDSelection of the multi-mirror pairs defined using the UNIT operand.

SELECT = *TARGET-UNITSelection of the multi-mirror pairs assigned to the target unit of a remote copy pair. See also “Multi-mirror pairs with SRDF target unit” on page 95.

U41000-J-Z125-4-76 111


Command processing

The following message is output to SYSOUT for each device and distributed via routing code ’0’, i.e. they are only logged in the CONSLOG file.

NDE1073 (&04) PROCESSED FOR DEVICE (&00)(&10)(&09)(&11)

Examples

/HOLD-MULTI-MIRRORING UNIT=*BY-PUBSET(PUBSET=A,NEW-PUBSET=*SAME), LOCK-ADD-MIRROR=*YES

/HOLD-MULTI-MIRRORING UNIT=*BY-PUBSET(PUBSET=ALT,NEW-PUBSET=NEU, HOLD-IO=*UNTIL-SPLIT)


(part 1 of 2)



1 CMD0202 Syntax error1 NDE1036 PUBSET and NEW-PUBSET have different lengths

32 NDE2002 Internal error64 CMD0087 Function not permitted in the current input mode or with the current

task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1005 Pubset not homogeneous64 NDE1008 Volume cannot be allocated64 NDE1010 Microcode status not supported (too low or too high)64 NDE1015 Device not defined in BS2000/OSD64 NDE1030 No multi-mirror function for the unit64 NDE1032 Multi-mirror pair is not yet synchronous 64 NDE1035 Device is not a normal unit64 NDE1040 Incorrect status of the normal unit 64 NDE1041 Incorrect status of the additional mirror unit64 NDE1043 Pubset type not supported 64 NDE1044 NEW-PUBSET already exists64 NDE1045 HOLD-MULTI-MIRRORING not yet completed, renaming of the

pubset not possible 64 NDE1085 HOLD-IO=*UNTIL-SPLIT not supported 64 NDE1087 HOLD-IO=*UNTIL-SPLIT only permitted for imported pubsets

112 U41000-J-Z125-4-76


64 NDE1092 Already split and additional mirror unit already renamed64 NDE1100 Invalid pubset status 64 NDE1101 HOLD-IO=*UNTIL-SPLIT: more than one sharer for pubset 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1104 HOLD-IO=*UNTIL-SPLIT: DAB caching active64 NDE1105 Inconsistent pubset64 NDE1108 SELECT=*TARGET-UNIT: UNIT is not a source unit64 NDE1109 SELECT=*TARGET-UNIT: TARGET-UNIT not found64 NDE1110 SELECT=*TARGET-UNIT: SRDF not synchronous or IN-HOLD64 NDE1111 Volume allocated by DRV, HOLD-IO not possible64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1120 Error suspending or resuming input/output access to pubset64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices are not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2009 Command aborted by [K2] key64 NDE2011 Symmetrix license not entered

130 NDE2005 Command cannot be executed at the moment

(part 2 of 2)

(SC2) SC1 Maincode Meaning

U41000-J-Z125-4-76 113

Commands HOLD-REMOTE-COPY

HOLD-REMOTE-COPYInterrupt remote copy operation

/HOLD-REMOTE-COPY interrupts remote copy operation. The remote copy pair gets the remote copy status IN-HOLD. On successful execution of this command, no more data is transferred to the target unit (no synchronization). Both the source unit and the target unit record the data discrepancy as pending write jobs for the other. The command is used for recovery tests.

CAUTION! The target unit and source unit can contain inconsistent data when the semi-synchronous or asynchronous processing mode is set. To ensure data consistency on the source unit and the target unit, before interrupting the remote copy operation, you should use /MODIFY-REMOTE-COPY-PARAMETER to set the synchronous processing mode and wait for the end of the synchronization process.

As of SHC-OSD V4.0, the splitting of SRDF devices on which target unit and source unit are not synchronized is only permitted with the operand FORCE=*YES. FORCE=*YES is rejected if the parameter SYMAPI_ALLOW_RDF_SYMFORCE=TRUE is not set in the SYMAPI option file.

This command is only executed when the remote copy pair has the remote copy status ACTIVE and access takes place via the source path. If the source unit is not available, or if /MODIFY-REMOTE-COPY-PARAMETER ON-ERROR=*HOLD is specified, the command is rejected.

The command is only executed for attached source units.

SHC-OSD checks the global and task-specific security settings before the command is executed. The current settings can be displayed with /SHOW-SHC-PROCESSING (see also page 179). The security settings are defined by means of the operands TASK-ADMIN-SCOPE and/or SYSTEM-ADMIN-SCOPE in /MODIFY-SHC-PROCESSING (see also page 125ff).

Domain: DEVICE

Privileges: TSOS

!

114 U41000-J-Z125-4-76

HOLD-REMOTE-COPY Commands

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), an emulated controller (*BY-CONTROLLER), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume. If VOLUME, PUBSET or CONTROLLER-UNIT is specified, the action is automatically carried out for the correct unit (i.e. the source unit). A mnemonic name or the Symmetrix internal name can only be specified for source units.





HOLD-REMOTE-COPY

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-CONTROLLER(...) / *BY-SYMMETRIX(...) /

<alphanum-name 2..2> / <x-text 4..4>

*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)


*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = <x-text 1..4> / *ALL-SOURCE-UNITS(...)

*ALL-SOURCE-UNITS(...) SELECT = *ANY / *ALL-DEFINED / *ATTACHED

FORCE = *NO / *YES

U41000-J-Z125-4-76 115


UNIT = *BY-CONTROLLER(...)Selects the units by means of the mnemonic name of the emulated controller. This is not possible when connecting the Symmetrix via Fibre Channel to the servers of the SX line. See also the section “Configuration on Business Servers of the SX line” on page 16.

CONTROLLER-UNIT = <alphanum-name 2..2> / <x-text 4..4>The mnemonic name of the emulated controller.





LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...)Selects the source units of the specified Symmetrix.

SELECT = *ANY Selects all source units of the specified Symmetrix.

SELECT = *ALL-DEFINEDSelects all source units of the specified Symmetrix generated in BS2000/OSD.

SELECT = *ATTACHEDSelects all source units of the specified Symmetrix attached in BS2000/OSD.

FORCE =FORCE controls the interruption of remote copy operation for remote copy pairs which are not (yet) synchronous. This is an incompatibility in comparison to SHC-OSD V3.0 which results from the usage of SYMAPI. Up to SHC-OSD V3.0 inclusive, remote copy pairs were inter-rupted after the message NDE1067 was output.

FORCE = *NORemote copy operation is not interrupted for non-synchronous pairs; the command is rejected with the message NDE1067.

FORCE = *YESRemote copy operation is always interrupted. This requires the option SYMAPI_ALLOW_RDF_SYMFORCE=TRUE in the SYMAPI option file under var/symapi/config/options. If the option is not set, the command is rejected with the message NDE1067.

116 U41000-J-Z125-4-76

HOLD-REMOTE-COPY Commands

Command processing

The following messages are output to SYSOUT for each device and distributed via routing code ’0’, i.e. they are only logged in the CONSLOG file.




NDE2007 COMMAND ’(&04)’ NOT PROCESSED FOR DEVICE (&00)(&10)(&09)(&11)

Examples

/HOLD-REMOTE-COPY UNIT=*BY-VOLUME(VOLUME=RDF000)

/HOLD-REMOTE-COPY UNIT=*BY-PUBSET(PUBSET=RDF)


(part 1 of 2)


1 0 NDE2003 Command successfully executed, no processing necessary2 0 NDE2004 Command successfully executed but not yet completed3 0 NDE1067 Remote copy pair not yet synchronous 3 0 NDE1069 Successful execution; data of some units not yet updated


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1005 Pubset not homogeneous64 NDE1010 Microcode status not supported (too low or too high)64 NDE1015 Device not defined in BS2000/OSD64 NDE1020 No remote copy function for the specified unit 64 NDE1021 Device is not a source unit 64 NDE1028 Data medium not unique in the unit 64 NDE1041 Target unit is ADD-MIRROR-UNIT in ESTABLISHED status64 NDE1060 Remote copy status is not ACTIVE64 NDE1062 Access to target unit of the remote copy pair is DIRECT64 NDE1063 Source unit does not have the status READY64 NDE1066 No remote link director available

U41000-J-Z125-4-76 117


64 NDE1067 Remote copy pair is not synchronous64 NDE1079 None of the selected units are attached 64 NDE1100 Invalid pubset status 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1107 No allocation possible for pubset 64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1152 FORCE flag not permitted64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2011 No Symmetrix license entered

130 NDE1082 Shortage of memory130 NDE2005 Command cannot be executed at the moment

(part 2 of 2)


118 U41000-J-Z125-4-76

MODIFY-REMOTE-COPY-PARAMETER Commands

MODIFY-REMOTE-COPY-PARAMETERModify processing mode and remote copy parameters

/MODIFY-REMOTE-COPY-PARAMETER allows you to set the processing mode (COPY-MODE) to synchronous, semi-synchronous or asynchronous processing (see section “COPY-MODE (processing mode)” on page 51). You change the remote copy parameters by means of the ON-ERROR operand. This controls whether applications are put on hold when there is a device failure or whether operation continues with the remaining unit (see section “ON-ERROR” on page 53).When changing into synchronous processing mode, WAIT=*UNTIL-SYNCHRONIZATION can be used in order to specify that the command has to wait for synchronization to be termi-nated.

The command is only executed for source units.


Domain: DEVICE

Privileges: TSOS

U41000-J-Z125-4-76 119

Commands MODIFY-REMOTE-COPY-PARAMETER




MODIFY-REMOTE-COPY-PARAMETER



*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)


*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


LOGICAL-VOLUME = <x-text 1..4> / *ALL-SOURCE-UNITS(...)


,COPY-MODE = *UNCHANGED / *SYNCHRONOUS(...) / *SEMI-SYNCHRONOUS / *ADAPTIVE-COPY(...)

*SYNCHRONOUS(...)

WAIT = *NO / *UNTIL-SYNCHRONIZATION

*ADAPTIVE-COPY(...)

WRITE-BUFFER = *CACHE / *DISK

,PENDING-UPDATE-LIMIT = *UNCHANGED / <integer 1...65535>

,ON-ERROR = *UNCHANGED / *HOLD / *CONTINUE

120 U41000-J-Z125-4-76




UNIT = *BY-CONTROLLER(...)Selects the source units by means of the mnemonic name of the emulated controller. This is not possible when connecting the Symmetrix via Fibre Channel to the servers of the SX line. See also the section “Configuration on Business Servers of the SX line” on page 16.






LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...)Selects the source units of the specified Symmetrix.




U41000-J-Z125-4-76 121


COPY-MODE =Changes the processing mode for remote copy operation (see section “COPY-MODE (processing mode)” on page 51).

COPY-MODE = *UNCHANGEDThe processing mode remains unchanged. The initial setting is made by the service engineer.

COPY-MODE = *SYNCHRONOUS(...)Sets the processing mode to synchronous processing. This mode ensures that the data is written to both the source unit and the target unit after every successful write job.

WAIT =Specifies whether or not the command is to wait until synchronization is terminated.

WAIT = *NOThe command does not wait until synchronization is terminated.

WAIT = *UNTIL-SYNCHRONIZATIONThe command waits until synchronization is terminated.WAIT=*UNTIL-SYNCHRONIZATION simplifies the programming of test procedures for recovery processes, since extensive queries of the progress of the synchronization for the remote copy pair can be omitted.Waiting can be aborted in dialog mode by means of the [K2] key.

COPY-MODE = *SEMI-SYNCHRONOUSSets the processing mode to semi-synchronous processing. The data on the source unit and the target unit can differ by no more than one processing step.

122 U41000-J-Z125-4-76


COPY-MODE = *ADAPTIVE-COPY(...)Sets the processing mode to asynchronous processing. In this mode, performance improves in the case of a write load, but remote copy reliability is reduced because the source and target units can differ from each other by several write jobs. This must not be specified together with ON-ERROR=*HOLD.

WRITE-BUFFER =Specifies whether the pending write jobs are to be recorded on the source unit or in the cache of the local Symmetrix.

WRITE-BUFFER = *CACHEThe pending write jobs are recorded in the cache of the local Symmetrix. This reduces the cache storage space that is available for the read buffer. Performance can be impaired if a higher value has been specified for the PENDING-UPDATE-LIMIT operand.

WRITE-BUFFER = *DISKThe pending write jobs are recorded on the source unit. If the unprotected source unit fails, all data that has not yet been transferred is lost.

PENDING-UPDATE-LIMIT =Specifies how many pending write jobs can be recorded. If the maximum number of pending write jobs exceeds the limit set, the processing mode switches to semi-synchronous until the number falls under the limit again.

PENDING-UPDATE-LIMIT = *UNCHANGEDThe previous entry is not changed. The initial setting is made by the service engineer.

PENDING-UPDATE-LIMIT = <integer 1..65535>The maximum number of pending write jobs permitted.

ON-ERROR =Specifies how the Symmetrix is to respond if part of the remote copy pair is no longer available (in the event of the failure of the remote link, the source unit or the target unit).

ON-ERROR = *UNCHANGEDThe previous entry is not changed. The initial setting is made by the service engineer.

U41000-J-Z125-4-76 123


ON-ERROR = *HOLDThe Symmetrix with the source units rejects all further jobs; the applications are put on hold and wait for a reply. The source unit assumes the status REMOUNT. A decision can then be made (automatically or by the user) as to whether to continue with the source unit only or whether to suspend operation in order to preserve data consistency.This must not be specified for paging units because, if it is, it is possible that no more SHC-OSD commands can be executed. This must not be specified together with COPY-MODE=*ADAPTIVE-COPY.

ON-ERROR = *CONTINUEIn the event of a failure, operation continues with the remaining unit; the applications are not put on hold. If the target unit fails, data loss occurs when subsequently switching over to the target unit.

Command processing

The following messages are output to SYSOUT for each device and distributed to CONSOLE via routing code ’0’, i.e. they are only logged in the CONSLOG file.


NDE1070 REMOTE COPY MODE CHANGED TO ’(&07)’ FOR DEVICE (&00)(&10)(&09)(&11)

NDE1071 REMOTE-COPY PARAMETER ’ON-ERROR’ CHANGED TO ’(&07)’ FOR DEVICE



Examples

/MODIFY-REMOTE-COPY-PARAMETER UNIT=*BY-PUBSET(PUBSET=RDF), COPY-MODE=*SYNCH,ON-ERROR=*HOLD

/MODIFY-REMOTE-COPY-PARAMETER UNIT=5000, COPY-MODE=*ADAPTIVE-COPY( WRITE-BUFFER=*CACHE,PENDING-UPDATE-LIMIT=44)

124 U41000-J-Z125-4-76




1 0 NDE2003 Command successfully executed, no processing necessary2 0 NDE2004 Command successfully executed but not yet completed3 0 NDE1067 Remote copy pair not yet synchronous 3 0 NDE1069 Successful execution; data of some units not yet updated


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1010 Microcode status not supported (too low or too high)64 NDE1020 No remote copy function for the specified unit64 NDE1021 Device is not a source unit64 NDE1028 Data medium not unique in the unit64 NDE1077 Combination of COPY-MODE=*AD-COPY(WR-BUFFER=*DISK) and

ON-ERROR=*HOLD64 NDE1079 None of the selected units are attached 64 NDE1081 Synchronous command processing not possible64 NDE1100 Invalid pubset status 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2009 Command aborted by [K2]

64 NDE2011 No Symmetrix license entered130 NDE1082 Shortage of memory130 NDE2005 Command cannot be executed at the moment

U41000-J-Z125-4-76 125

Commands MODIFY-SHC-PROCESSING

MODIFY-SHC-PROCESSINGModify internal settings

/MODIFY-SHC-PROCESSING allows you to change the internal settings of SHC-OSD for maintenance and diagnosis. The initial settings are described in the example of /SHOW-SHC-PROCESSING on page 179. The current internal settings can be output by means of /SHOW-SHC-PROCESSING . The changes to save settings via the operands SYSTEM-ADMIN-SCOPE and TASK-ADMIN-SCOPE are shown on console.

Domain: DEVICE

Privileges: TSOS

(part 1 of 2)

MODIFY-SHC-PROCESSING

TRACE = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)

EXTENDED-TRACE = *UNCHANGED / *OFF / *ON

,NEW-TRACE-SIZE = *UNCHANGED / <integer 64..4096 Kbyte>

,NEW-ERROR-TRACE-SIZE = *UNCHANGED / <integer 64..4096 Kbyte>

,RELEASE-TRACE-AT-UNLOAD = *UNCHANGED / *YES / *NO

,LOCK-RETRY = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)

WAIT-TIME = *UNCHANGED / <integer 1..10 seconds>

,RETRY-COUNT = *UNCHANGED / <integer 1..100>

,IO-RETRY = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)



,SYNCH-WAIT-RETRY = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)



continued ➠

126 U41000-J-Z125-4-76

MODIFY-SHC-PROCESSING Commands

TRACE = *UNCHANGED / *PARAMETERS(...)Changes the trace options.

EXTENDED-TRACE = *UNCHANGED / *OFF / *ONControls the size of the entries in SHC-OSD’s normal trace. If EXTENDED-TRACE=*ON is specified, additional information is recorded in order to facilitate diagnosis. The default setting is *OFF.

NEW-TRACE-SIZE =Specifies whether the size of the trace area in class 4 memory is to be changed. If it is, the existing area is released and the new area requested.

NEW-TRACE-SIZE = *UNCHANGEDThe previous setting remains unchanged.

,COMM-WAIT-RETRY = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)



,STATE-CHANGE-POLLING = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)

SHORT-INTERVAL = *UNCHANGED / <integer 30..3600 seconds>

,NORMAL-INTERVAL = *UNCHANGED / <integer 60..7200 seconds>

,LONG-INTERVAL = *UNCHANGED / <integer 360..86400 seconds>

,SELECT-DEVICES = *UNCHANGED / *ALL / *ATTACHED

,LOG-CHANGES = *UNCHANGED / *ALL-EVENTS / *MAJOR-EVENTS-ONLY

,DEVICE-PRESELECTION = *UNCHANGED / *ALL-DEFINED / *ANY

,SYSTEM-ADMIN-SCOPE = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)

DETACHED-DEVICES = *UNCHANGED / *ACCEPT / *REJECT

,NOT-DEFINED-DEVICES = *UNCHANGED / *ACCEPT / *REJECT

,TASK-ADMIN-SCOPE = *UNCHANGED / *PARAMETERS(...)

*PARAMETERS(...)

DETACHED-DEVICES = *UNCHANGED / *ACCEPT / *REJECT / *SYSTEM-ADMIN-SCOPE

,NOT-DEFINED-DEVICES = *UNCHANGED / *ACCEPT / *REJECT / *SYSTEM-ADMIN-SCOPE

,MAX-MULTI-BCV = *UNCHANGED / <integer 1 .. 16>

,SYMAPI-DEBUG = *UNCHANGED / *ON / *OFF

,SAVE-SYMAPI-DB = *NO / *YES

(part 2 of 2)

U41000-J-Z125-4-76 127


NEW-TRACE-SIZE = <integer 64..4096 Kbyte>New size of the trace area.

NEW-ERROR-TRACE-SIZE =Specifies whether the size of the error trace area in class 4 memory is to be changed. If it is, the existing area is released and the new area requested.

NEW-ERROR-TRACE-SIZE = *UNCHANGEDThe previous setting remains unchanged.

NEW-ERROR-TRACE-SIZE = <integer 64..4096 Kbyte>New size of the error trace area.

RELEASE-TRACE-AT-UNLOAD =Specifies whether the trace area is released when the /HOLD-SUBSYSTEM or /STOP-SUBSYSTEM SHC-OSD command has been specified (see manual “Commands” [1]).

RELEASE-TRACE-AT-UNLOAD = *UNCHANGEDThe previous setting remains unchanged. The initial setting is *YES.

RELEASE-TRACE-AT-UNLOAD = *YESTrace areas are released when SHC-OSD is unloaded.

RELEASE-TRACE-AT-UNLOAD = *NO/HOLD-SUBSYSTEM (see manual “Commands” [1]) allows diagnostic information to be created for problems at termination of subsystems, in that NDMDAMP is executed after /HOLD-SUBSYSTEM. The memory area in class 4 memory cannot be released.

LOCK-RETRY = *UNCHANGED / *PARAMETERS(...)Changes the retry count and the wait time between retries when an internal SHC-OSD lock conflict occurs.

WAIT-TIME = *UNCHANGED / <integer 1..10 seconds>The wait time between the retries.

RETRY-COUNT = *UNCHANGED / <integer 1..100>The maximum number of retries (retry count).

IO-RETRY = *UNCHANGED / *PARAMETERS(...)Changes the retry count and wait time between the retries when an expected status change does not occur on the Symmetrix.

WAIT-TIME = *UNCHANGED / <integer 1..10 seconds>Indicates the waiting time between the retries.


128 U41000-J-Z125-4-76


SYNCH-WAIT-RETRY = *UNCHANGED / *PARAMETERS(...)Changes the retry count and wait time between the retries when WAIT=*UNTIL-SYNCHRONIZATION is issued with a command.



COMM-WAIT-RETRY = *UNCHANGED / *PARAMETERS(...)Changes the retry count and wait time between the retries for internal FITC communication



STATE-CHANGE-POLLING = *UNCHANGED / *PARAMETERS(...)Changes the polling interval for the checking of all Symmetrix units after status changes. Specifies whether status changes are to be recorded for all devices or only for attached devices.

SHORT-INTERVAL = *UNCHANGED / <integer 30..3600 seconds>Polling interval for checking at short intervals (i.e. a Symmetrix unit was not accessible at the last polling).

NORMAL-INTERVAL = *UNCHANGED / <integer 60..7200 seconds>Polling interval for checking at normal intervals (i.e. there were no problems during the last polling cycle).

LONG-INTERVAL = *UNCHANGED / <integer 360..86400 seconds>Polling interval for checking at long intervals (i.e. no supported Symmetrix units were found at the last polling).

SELECT-DEVICES = *UNCHANGED / *ALL / *ATTACHEDSpecifies whether status changes found during polling or SHC-OSD commands are to be displayed for all devices or only for the currently attached devices.

LOG-CHANGES = Specifies whether all status changes or only the global status changes are to be logged at the console.

LOG-CHANGES = *UNCHANGED The existing setting is not changed.

U41000-J-Z125-4-76 129


LOG-CHANGES = *ALL-EVENTS All status changes are logged at the console, i.e. all status changes detected in the Symmetrix, including the status changes of individual logical units and their internal mirror disks are logged in the console.

LOG-CHANGES = *MAJOR-EVENTS-ONLYAll global status changes detected in the Symmetrix as well as the status changes for functions offered in the Symmetrix, e.g. TimeFinder and SRDF, are logged in the console. Status changes of individual logical units and their internal mirror disks are not logged.

DEVICE-PRESELECTION = Preselection of the units for which information is output by default by the SHOW commands.If the basic setting is used then only the generated units are displayed for UNIT=*BY-CONTROLLER/*BY-VOLUME/*BY-PUBSET/ <alphanum-name 2..2> and <x-text 4..4> while all the selected units for the Symmetrix are output for UNIT=*BY-SYMMETRIX.

DEVICE-PRESELECTION = *UNCHANGED The previous setting remains unchanged.

DEVICE-PRESELECTION = *ALL-DEFINEDBy default, the SHOW commands output information on all the units generated in BS2000/OSD in accordance with the basic setting.

DEVICE-PRESELECTION = *ANY The SHOW commands normally send information about all of the units contained in the selected Symmetrix.

SYSTEM-ADMIN-SCOPE = Modifies the global security settings for the execution of remote copy and multi-mirror actions. Depending on the setting, such actions may be performed only for units that are attached or defined (generated) in BS2000/OSD or for any Symmetrix units. All action commands take account of the security settings:

HOLD-MULTI-MIRRORING on page 107HOLD-REMOTE-COPY on page 113MODIFY-REMOTE-COPY-PARAMETER on page 118RESUME-MULTI-MIRRORING on page 135RESUME-REMOTE-COPY on page 141SET-REMOTE-COPY-ACCESS on page 146START-MULTI-MIRRORING on page 207STOP-MULTI-MIRRORING on page 213

The basic setting corresponds to the values DETACHED-DEVICES=*REJECT and NOT-DEFINED-DEVICES=*REJECT.

130 U41000-J-Z125-4-76


SYSTEM-ADMIN-SCOPE = *UNCHANGED The previous setting remains unchanged.

SYSTEM-ADMIN-SCOPE = *PARAMETERS(....) The setting is made via parameters.

DETACHED-DEVICES = Actions for detached devices executed.

DETACHED-DEVICES = *UNCHANGEDThe previous setting remains unchanged.

DETACHED-DEVICES = *REJECTActions for detached devices rejected.

DETACHED-DEVICES = *ACCEPT Actions for detached devices executed.

NOT-DEFINED-DEVICES = Actions executed for devices not generated in BS2000/OSD.

NOT-DEFINED-DEVICES = *UNCHANGEDThe previous setting remains unchanged.

NOT-DEFINED-DEVICES = *REJECTActions for devices not generated rejected.

NOT-DEFINED-DEVICES = *ACCEPT Actions for devices not generated, executed.

TASK-ADMIN-SCOPE = Modifies the local (task-specific) settings for the execution of remote copy and multi-mirror actions. Depending on the setting, such actions may be performed only for units that are attached or defined (generated) in BS2000/OSD or for any Symmetrix units. All action commands take account of the security settings:

HOLD-MULTI-MIRRORING on page 107HOLD-REMOTE-COPY on page 113MODIFY-REMOTE-COPY-PARAMETER on page 118RESUME-MULTI-MIRRORING on page 135RESUME-REMOTE-COPY on page 141SET-REMOTE-COPY-ACCESS on page 146START-MULTI-MIRRORING on page 207STOP-MULTI-MIRRORING on page 213

The basic setting corresponds to the values DETACHED-DEVICES=*SYSTEM-ADMIN-SCOPE and NOT-DEFINED-DEVICES=*SYSTEM-ADMIN-SCOPE.

U41000-J-Z125-4-76 131


TASK-ADMIN-SCOPE = *UNCHANGED The previous setting remains unchanged.

TASK-ADMIN-SCOPE =*PARAMETERS(....) The setting is performed via parameters.

DETACHED-DEVICES = Actions for detached devices executed.

DETACHED-DEVICES = *UNCHANGEDThe previous setting remains unchanged.

DETACHED-DEVICES = *REJECTActions for detached devices rejected.

DETACHED-DEVICES = *ACCEPT Actions for detached devices executed.

DETACHED-DEVICES = *SYSTEM-ADMIN-SCOPE The global system setting applies.

NOT-DEFINED-DEVICES = Actions for devices not generated in BS2000/OSD executed.

NOT-DEFINED-DEVICES = *UNCHANGEDThe previous setting remains unchanged.

NOT-DEFINED-DEVICES = *REJECTActions for devices not generated are rejected.

NOT-DEFINED-DEVICES = *ACCEPT Actions for devices not generated executed.

NOT-DEFINED-DEVICES = *SYSTEM-ADMIN-SCOPE The global system setting applies.

MAX-MULTI-BCV = Changes the number of additional mirror units allowed per normal unit.

MAX-MULTI-BCV = *UNCHANGEDThe previous setting remains unchanged.

MAX-MULTI-BCV = <integer 1 .. 16>A new maximum value is set (default: 8).

132 U41000-J-Z125-4-76


SYMAPI-DEBUG = Changes the setting of the debug mode for SYMAPI with regard to the current log file in the POSIX file system (path: /var/symapi/log).

The operand must only be used with care and only to create diagnostic documents. Sufficient memory space must be made available in the POSIX file system before activating debug mode. When the diagnostic documents have been created, debug mode should be deactivated again immediately, otherwise a memory bottleneck may be produced in the POSIX file system. SYMAPI-DEBUG is not offered in a prompted dialog.

SYMAPI-DEBUG = *UNCHANGEDThe previous setting remains unchanged.

SYMAPI-DEBUG = *ONDebug mode is activated.

SYMAPI-DEBUG = *OFFDebug mode is deactivated.

SAVE-SYMAPI-DB = Starts a (one-off) backup of the SYMAPI configuration database to a file /var/symapi/db/shc-osd040db.bin in the POSIX file system. The operand is only used to create diagnostic information and is not offered in a prompted dialog.

SAVE-SYMAPI-DB = *NOThe backup of the database is not started.

SAVE-SYMAPI-DB = *YESThe backup of the database is started.

i

U41000-J-Z125-4-76 133


Examples

/MODIFY-SHC-PROCESSING TRACE=*PARAMETERS(EXTENDED-TRACE=*ON)

/MODIFY-SHC-PROCESSING LOCK-RETRY=*PARAMETERS(WAIT-TIME=2,RETRY-COUNT=40)

/MODIFY-SHC-PROCESSING STATE-CHANGE-POLLING=*PARAMETERS( SELECT-DEVICES=*ALL)


(SC2) SC1 Maincode Meaning0 CMD0001 Command successfully executed1 CMD0202 Syntax error


task privileges64 CMD0216 Required privilege not available

134 U41000-J-Z125-4-76

RESUME-IO Commands

RESUME-IO Resume input/output activity for pubsets

/RESUME-IO is used to resume input/output activity for pubsets after this has been halted by SHC-OSD.

In normal operation, SHC-OSD automatically halts and then resumes input//output activity for pubsets in order to ensure the consistent splitting of additional mirror units that have been set using TimeFinder.

CAUTION! This command is provided for emergencies only and should be used with great care in order to avoid jeopardizing data consistency when a split is performed.

PUBSET =Specifies the pubset with stopped input/output activity.

PUBSET = *ALLSelects all pubsets for which input/output activity is currently halted.

PUBSET = <cat-id 1..4>The pubset ID.

Example

/RESUME-IO PUBSET=MMF


Domain: DEVICE

Privileges: TSOS

RESUME-IO

PUBSET = *ALL / <cat-id 1..4>


32 NDE2002 Internal error64 CMD0216 Required privilege not available64 NDE1004 Pubset not found or incorrect pubset type

!

U41000-J-Z125-4-76 135

Commands RESUME-MULTI-MIRRORING

RESUME-MULTI-MIRRORINGReconstruct multi-mirror pairs

/RESUME-MULTI-MIRRORING allows you to reconstruct a multi-mirror pair that has been split by means of /HOLD-MULTI-MIRRORING.

The normal units of the multi-mirror pairs must always be specified for the UNIT operand. If the SRDF function is used, then the specified normal unit may also be the source unit of a remote copy pair (see also “Multi-mirror pairs with SRDF target unit” on page 95). The operand SELECT=*TARGET-UNIT can be used to select the multi-mirror pair at the target unit. The additional mirror units are assigned automatically.

During the reconstruction process, the information recorded on the pending write jobs while the pair was split can be evaluated (RESTORE-DATA=*MODIFIED-ONLY), or a full copy can be created (RESTORE-DATA=*ALL-DATA).

The data can be copied either from the normal unit to the additional mirror unit or vice versa. The additional mirror unit must not be occupied. If the normal unit is simultaneously the target unit of a remote copy pair then RESTORE=*TO-ORIGINAL is only possible if the remote copy status is *IN-HOLD or *ERROR and TARGET-ACCESS has the value *DIRECT.

To safeguard against data inconsistency, the command is rejected when pending write jobs are recorded on the source unit, which is determined on the basis of the copy direction.

If the additional mirror unit was locked with /HOLD-MULTI-MIRRORING and operand LOCK-ADD-MIRROR= *YES, then /RESUME-MULTI-MIRRORING with operand UNLOCK-ADD-MIRROR=*YES must be specified to release the lock again.

WAIT=*UNTIL-SYNCHRONIZATION / *NO specifies whether or not the command waits for synchronization to be terminated.


Domain: DEVICE

Privileges: TSOS

136 U41000-J-Z125-4-76

RESUME-MULTI-MIRRORING Commands

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume.



UNIT = *BY-PUBSET(...)Selects the units by means of a pubset ID or volume set ID. The SF/SM pubset is locked against reconfiguration while a command is being executed.The corresponding additional mirror pubset is found automatically.


RESUME-MULTI-MIRRORING

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-SYMMETRIX(...) / <alphanum-name 2..2> / <x-text 4..4>

*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)


*BY-SYMMETRIX(...)



,RESTORE = *FROM-ORIGINAL / *TO-ORIGINAL

,RESTORE-DATA = *MODIFIED-ONLY / *ALL-DATA

,UNLOCK-ADD-MIRROR = *NO / *YES

,WAIT = *NO / *UNTIL-SYNCHRONIZATION


,SELECT-ADD-MIRROR = *CURRENT / *PREVIOUS / *OLDEST

U41000-J-Z125-4-76 137


UNIT = *BY-SYMMETRIX(...)Specifies the normal unit by means of the Symmetrix serial number and the Symmetrix internal number of the logical volume.



UNIT = <alphanum-name 2..2> / <x-text 4..4>Selects the units by means of the mnemonic device name of the logical volume.

RESTORE =Specifies the copy direction when there is a data discrepancy between the normal unit and the additional mirror unit.

RESTORE = *FROM-ORIGINALCopies from the normal unit to the additional mirror unit.

RESTORE = *TO-ORIGINALCopies from the additional mirror unit to the normal unit.

RESTORE-DATA =Specifies whether all the data or only the changed data is to be copied.

RESTORE-DATA = *MODIFIED-ONLYCopies all the changed data from the “source” unit (normal unit or additional mirror unit, depending on RESTORE) to the “target” unit; replaces data modified on the “target” unit with data from the “source” unit.

RESTORE-DATA = *ALL-DATACopies all the data.

UNLOCK-ADD-MIRROR =Specifies whether the lock set previously with /HOLD-MULTI-MIRRORING and operand LOCK-ADD-MIRROR=*YES is to be released or not.

UNLOCK-ADD-MIRROR = *NOIf there is a lock, it is not released.However, if at least one additional mirror unit is locked, then the command is rejected with message NDE1083.

UNLOCK-ADD-MIRROR = *YESIf there is a lock, it is released.

138 U41000-J-Z125-4-76




WAIT = *UNTIL-SYNCHRONIZATIONThe command waits until synchronization is terminated.WAIT=*UNTIL-SYNCHRONIZATION simplifies the programming of test procedures for recovery processes, since extensive queries of the progress of the synchronization for the multi-mirror pair can be omitted.Waiting can be aborted in dialog mode by means of the [K2] key.

SELECT =Selects the multi-mirror pairs.

SELECT = *STDSelects the multi-mirror pairs of the units specified with the UNIT operand.

SELECT = *TARGET-UNITSelection of the multi-mirror pairs assigned to the target unit of a remote copy pair. See also section “Multi-mirror pairs with SRDF target unit” on page 95.

SELECT-ADD-MIRROR =Selection of the additional mirror units that are assigned to the specified multi-mirror pairs. If the Multi BCV function is used, it is also possible to select the last split-off or oldest additional mirror unit (see also section “Utilization concepts for the Multi BCV function” on page 88).

SELECT-ADD-MIRROR = *CURRENTSelects the additional mirror unit currently attached.

SELECT-ADD-MIRROR = *PREVIOUSSelects the additional mirror unit last to be split.

SELECT-ADD-MIRROR = *OLDESTSelects the oldest additional mirror unit.

U41000-J-Z125-4-76 139


Command processing






Examples

/RESUME-MULTI-MIRRORING UNIT=*BY-PUBSET(PUBSET=MMF), SELECT-ADD-MIRROR=*PREVIOUS

/RESUME-MULTI-MIRRORING UNIT=*BY-VOLUME(VOLUME=A)


(part 1 of 2)




task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1005 Pubset not homogeneous64 NDE1006 Pubset/volume is allocated64 NDE1008 Volume cannot be allocated64 NDE1010 Microcode status not supported (too low or too high)64 NDE1015 Device not defined in BS2000/OSD64 NDE1030 No multi-mirror function for the unit64 NDE1033 Multi-mirror pair is not split64 NDE1035 Device is not a normal unit64 NDE1040 Incorrect status of the normal unit64 NDE1041 Incorrect status of the additional mirror unit64 NDE1042 Normal unit is SRDF target unit and RESTORE=*TO-ORIGINAL,

normal unit is not in status *READY 64 NDE1043 Pubset type not supported

140 U41000-J-Z125-4-76


64 NDE1076 Additional mirror unit has pending write jobs, copy to normal unit rejected

64 NDE1083 Additional mirror unit locked64 NDE1100 Invalid pubset status 64 NDE1101 More than one sharer for pubset 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1108 SELECT=*TARGET-UNIT: UNIT not a source unit64 NDE1109 SELECT=*TARGET-UNIT: TARGET-UNIT not found64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices not supported64 NDE2009 Command aborted by [K2]

64 NDE2011 No Symmetrix license entered130 NDE2005 Command cannot be executed at the moment

(part 2 of 2)


U41000-J-Z125-4-76 141

Commands RESUME-REMOTE-COPY

RESUME-REMOTE-COPYResume remote copy operation

/RESUME-REMOTE-COPY reactivates remote copy operation after it has been interrupted by means of /HOLD-REMOTE-COPY.

The command can be used to resume remote copy operation after testing of the recovery procedure. If data was changed on the source unit or target unit when the remote copy status was IN-HOLD, the RESTORE operand can be used to specify the copy direction during the subsequent synchronization of the remote copy pair. WAIT=*UNTIL-SYNCHRONIZATION can be used to specify that the command is to wait until synchronization is concluded.

The command is executed only for source units when the remote copy pair has the remote copy status IN-HOLD and access is via the source path (TARGET-ACCESS=*BY-SOURCE).

To prevent data inconsistency, the command is rejected if it is established that there are pending write jobs recorded for the receiving unit or that there is a multi-mirror recon-struction in progress on the receiving unit.


Domain: DEVICE

Privileges: TSOS

142 U41000-J-Z125-4-76

RESUME-REMOTE-COPY Commands






RESUME-REMOTE-COPY



*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)


*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = <x-text 1..4> / *ALL-SOURCE-UNITS(...)


,RESTORE = *FROM-SOURCE / *TO-SOURCE


U41000-J-Z125-4-76 143


UNIT = *BY-CONTROLLER(...)Selects the units by means of the menmonic name of the emulated controller. This is not possible when connecting the Symmetrix via Fibre Channel to the servers of the SX line. See also the section “Configuration on Business Servers of the SX line” on page 16.





LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...)Selects the source units of the Symmetrix.





RESTORE =Specifies the copy direction when there is a data discrepancy between the source unit and the target unit.

RESTORE = *FROM-SOURCECopies from the source unit to the target unit.

RESTORE = *TO-SOURCECopies from the target unit to the source unit.

To ensure data consistency, the copy direction *TO-SOURCE is only accepted when there are no pending write jobs locally recorded on the target unit. The source units must not be occupied (export pubset).

i

144 U41000-J-Z125-4-76

RESUME-REMOTE-COPY Commands



WAIT = *UNTIL-SYNCHRONIZATIONThe command waits until synchronization is terminated.WAIT=*UNTIL-SYNCHRONIZATION simplifies the programming of test procedures for recovery processes, since extensive queries of the progress of the synchronization for the remote copy pair can be omitted.Waiting can be aborted in dialog mode by means of the [K2] key.

Command processing






Examples

/RESUME-REMOTE-COPY UNIT=*BY-VOLUME(VOLUME=RDF000),RESTORE=*TO-SOURCE

/RESUME-REMOTE-COPY UNIT=*BY-PUBSET(PUBSET=RDF),RESTORE=*FROM-SOURCE


(part 1 of 2)


1 0 NDE2003 Command successfully executed, no processing necessary2 0 NDE2004 Command successfully executed but not yet completed3 0 NDE1067 Remote copy pair not yet synchronous3 0 NDE1068 Pending write jobs are still recorded 3 0 NDE1069 Successful execution; data of some units not yet updated


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix

U41000-J-Z125-4-76 145


64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1005 Pubset not homogeneous64 NDE1006 Pubset/volume is allocated64 NDE1010 Microcode status not supported (too low or too high)64 NDE1020 No remote copy function for the specified unit64 NDE1021 Device is not a source unit64 NDE1028 Data medium not unique in the unit64 NDE1041 Target unit is ADD-MIRROR-UNIT in status ESTABLISHED64 NDE1061 Remote copy status is not IN-HOLD64 NDE1062 Access to target unit of the remote copy pair is DIRECT64 NDE1063 Source unit does not have the status READY64 NDE1064 Target unit does not have the status READY64 NDE1065 ON-ERROR=*HOLD64 NDE1066 No remote link director available64 NDE1076 Pending write jobs locally are recorded on the target unit with

RESTORE=*TO-SOURCE specified 64 NDE1079 None of the selected units are attached 64 NDE1081 Synchronous command processing not possible64 NDE1093 Remote copy status no longer ACTIVE64 NDE1100 Invalid pubset status 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1107 No allocation possible for pubset64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta disk64 NDE1155 RAID10 devices not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2009 Command aborted by [K2]

64 NDE2011 No Symmetrix license entered130 NDE1082 Shortage of memory130 NDE2005 Command cannot be executed at the moment

(part 2 of 2)


146 U41000-J-Z125-4-76

SET-REMOTE-COPY-ACCESS Commands

SET-REMOTE-COPY-ACCESSSet access path for data of remote copy pair

/SET-REMOTE-COPY-ACCESS changes the access path for the data of a remote copy pair (via the source path or target path).

The data of the remote copy pair is normally accessed via the source path (i.e. the target unit can only be accessed internally via the remote link).

If either the Symmetrix with the source units or the entire local computer center fails, it is possible to access the data directly via the target path. This is done by entering the command with the setting TARGET-ACCESS=*DIRECT.

The command is rejected when the remote copy pair has the remote copy status ACTIVE.


Domain: DEVICE

Privileges: TSOS

U41000-J-Z125-4-76 147

Commands SET-REMOTE-COPY-ACCESS

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), an emulated controller (*BY-CONTROLLER), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume.




SET-REMOTE-COPY-ACCESS



*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-PUBSET(...)


*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = <x-text 1..4> / *ALL-SOURCE-UNITS(...) / *ALL-TARGET-UNITS(...)


*ALL-TARGET-UNITS (...) SELECT = *ANY / *ALL-DEFINED / *ATTACHED

,TARGET-ACCESS = *BY-SOURCE(....) / *DIRECT(...)

*BY-SOURCE(...)

TARGET-STATE = *STD / *NOT-READY / *READ-ONLY

*DIRECT(...)

ALLOW-PEND-UPDATES = *NO / *YES

148 U41000-J-Z125-4-76








LOGICAL-VOLUME = *ALL-SOURCE-UNITS(...)Selects the source units of the Symmetrix.




LOGICAL-VOLUME = *ALL-TARGET-UNITS(...)Selects the target units of the Symmetrix.

SELECT = *ANY Selects all target units of the specified Symmetrix.

SELECT = *ALL-DEFINEDSelects all target units of the specified Symmetrix generated in BS2000/OSD.

SELECT = *ATTACHEDSelects all target units of the specified Symmetrix attached in BS2000/OSD.

UNIT = <alphanum-name 2..2> / <x-text 4..4>Selects the units by means of the mnemonic device name of the logical volume.

U41000-J-Z125-4-76 149


TARGET-ACCESS =Specifies the access path for the data of a remote copy pair.

TARGET-ACCESS = *BY-SOURCE(...)The data of the remote copy pair is accessed via the source path (i.e. the source unit is addressed). This is the normal access path for the remote copy pair or when remote copy operation is to be resumed after a failure.The target units are not addressed in this status. To avoid ambiguous archive numbers during BS2000/OSD operation, the status NOT-READY is set by default for generated target units. For all other target units, i.e. non-BS2000 systems, the status READ-ONLY is set.

TARGET-STATE =Specifies the status setting for the target units.

TARGET-STATE = *STDThe target unit setting depends on the generation in BS2000/OSD as described in TARGET-ACCESS=*BY-SOURCE(...).

TARGET-STATE = *NOT-READYAll target units will be set in NOT-READY status.

TARGET-STATE = *READ-ONLYAll target units will be set in READ-ONLY status.

TARGET-ACCESS = *DIRECT(...)The data of the remote copy pair is accessed directly (i.e. the target unit is addressed). This access path is set when either the Symmetrix with the source units or the entire computer center fails and operation is to continue with the target unit until the problem is dealt with. What happens then depends on whether or not the (Symmetrix internal) setting PEND-UPD=NOT-ALLOWED or ALLOWED is overridden.

ALLOW-PEND-UPDATES =Specifies how the setting PEND-UPD=NOT-ALLOWED is to be handled. This setting prevents the inadvertent use of invalid data when the target unit is no longer synchronized.

ALLOW-PEND-UPDATES = *NOThe PEND-UPD=NOT-ALLOWED setting is not overridden. The target unit rejects the transition to READY and receives the status DISABLED if there are still pending write jobs recorded on the target unit.

ALLOW-PEND-UPDATES = *YESThe PEND-UPD=NOT-ALLOWED setting is overridden. The target unit receives the status READY, even if there are still pending write jobs recorded. This can result in data incon-sistencies.

150 U41000-J-Z125-4-76


Command processing



NDE1072 PARAMETER ’TARGET-ACCESS’ CHANGED TO ’(&07)’ FOR REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13)



Examples

/SET-REMOTE-COPY-ACCESS UNIT=*BY-PUBSET(PUBSET=RDF),TARGET-ACCESS=*DIRECT

/SET-REMOTE-COPY-ACCESS UNIT=*BY-VOLUME(VOLUME=RDF.00), TARGET-ACCESS=*BY-SOURCE


(part 1 of 2)


1 0 NDE2003 Command successfully executed, no processing necessary2 0 NDE2004 Command successfully executed but not yet completed3 0 NDE1025 Direct access to the source unit not possible 3 0 NDE1069 Successful execution; data of some units not yet updated


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1005 Pubset not homogeneous64 NDE1010 Microcode status not supported (too low or too high)64 NDE1020 No remote copy function for the specified unit64 NDE1021 Device is not a source unit64 NDE1026 Direct access to the target unit not possible 64 NDE1027 Remote copy status is ACTIVE64 NDE1028 Data medium not unique in the unit64 NDE1029 Target unit has the status DISABLED64 NDE1041 Target unit is ADD-MIRROR-UNIT with status ESTABLISHED

U41000-J-Z125-4-76 151


64 NDE1065 ON-ERROR=*HOLD64 NDE1078 TARGET-ACCESS=*BY-SOURCE not permitted when paging is active

on the target unit 64 NDE1079 None of the selected units are attached 64 NDE1094 TARGET-ACCESS=*BY-SOURCE not allowed, if source unit is in

status DISABLED and ON-ERROR=*HOLD 64 NDE1100 Invalid pubset status 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset64 NDE1105 Inconsistent pubset64 NDE1107 No allocation possible for pubset64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2011 No Symmetrix license entered

130 NDE1082 Shortage of memory130 NDE2005 Command cannot be executed at the moment

(part 2 of 2)


152 U41000-J-Z125-4-76

SHOW-MULTI-MIRRORING-STATUS Commands

SHOW-MULTI-MIRRORING-STATUSDisplay status of multi-mirror pairs

/SHOW-MULTI-MIRRORING-STATUS displays the status of multi-mirror pairs (see also section “Device status” on page 76).

The command supports structured output to S variables (for information on how this works, see section “Representation of S variables” on page 307; for further details see manual “Commands, Volume 6” [4]).

Domain: DEVICE

Privileges: TSOS, OPERATING, HW-MAINTENANCE, SW-MONITOR-ADMINISTRATION

Routing code: @

SHOW-MULTI-MIRRORING-STATUS

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-CONTROLLER / *BY-SYMMETRIX(...) /

list-poss(24): <alphanum-name 2..2> / <x-text 4..4

*BY-VOLUME(...)

VOLUME = list-poss(24): <vsn 1..6>

*BY-PUBSET(...)

PUBSET = list-poss(24): <cat-id 1..4>

*BY-CONTROLLER(...)

CONTROLLER-UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>

*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = *ALL / <x-text 1..4>

,SELECT = *ALL-PRESELECTED / *BY-ATTRIBUTES(...)

*BY-ATTRIBUTES(...)

MULTI-MIRROR-STATUS = *ANY / *ESTABLISHED / *ESTABLISHING / *SPLIT / *SPLITTING /

*RECONSTRUCTING / *UNUSED

,SYNCHRONIZED = *ANY / *YES / *NO

,REMOTE-COPY-USE = *STD / *TARGET-UNIT

,DEVICE = *ALL-PRESELECTED /*ALL-DEFINED / *ATTACHED / *DETACHED / *ANY

,INFORMATION = *CURRENT / *ALL-ADD-MIRRORS

U41000-J-Z125-4-76 153

Commands SHOW-MULTI-MIRRORING-STATUS

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), the mnemonic name of emulated controllers (*BY-CONTROLLER), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume. At least one unit of each emulated controller of the Symmetrix must be attached.

UNIT = *BY-VOLUME(...)Selects the units via a specific archive number.

VOLUME = list-poss(24): <vsn 1..6>The archive number of the volume. Up to 24 volumes can be specified in a list.

UNIT = *BY-PUBSET(...)Selects the units by means of a pubset ID or volume set ID. Information is output for all volumes of the specified pubset. Catalog IDs of SF pubsets, volume sets or imported SM pubsets can be specified. No information is output for exported SM pubsets.

PUBSET = list-poss(24): <cat-id 1..4>The pubset ID or the volume set ID. Up to 24 pubsets or volume sets can be specified in a list.

UNIT = *BY-CONTROLLER(...)Selects the units by means of the mnemonic name of the emulated controller.

CONTROLLER-UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>The mnemonic name of the emulated controller. Up to 24 emulated controllers can be specified in a list.



LOGICAL-VOLUME = *ALLSelects all logical volumes of the Symmetrix.


UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>Selects the units by means of the mnemonic device name of the logical volume. Up to 24 logical volumes can be specified in a list.

154 U41000-J-Z125-4-76


SELECT =The information volume can be selected according to the multi-mirror status, synchroni-zation and remote copy use.

SELECT = *ALL-PRESELECTEDThe information volume is not restricted.

SELECT = *BY-ATTRIBUTES(...)The information volume is restricted by means of the selection criteria.

MULTI-MIRROR-STATUS =The information is only issued for multi-mirror pairs in the specified status.

MULTI-MIRROR-STATUS = *ANYThe information is issued for all multi-mirror pairs, regardless of their status.

MULTI-MIRROR-STATUS = *ESTABLISHEDThe information is only issued for ESTABLISHED multi-mirror pairs.

MULTI-MIRROR-STATUS = *ESTABLISHINGThe information is only issued for ESTABLISHING multi-mirror pairs.

MULTI-MIRROR-STATUS = *SPLITThe information is only issued for SPLIT, SPLIT-BACKG and SPLIT-LOCKED multi-mirror pairs.

MULTI-MIRROR-STATUS = *SPLITTINGThe information is only issued for SPLITTING multi-mirror pairs.

MULTI-MIRROR-STATUS = *RECONSTRUCTINGThe information is only issued for RECONSTRUCTING multi-mirror pairs.

MULTI-MIRROR-STATUS = *UNUSEDThe information is only issued for UNUSED and UNUSED-LOCKED multi-mirror pairs.

SYNCHRONIZED =The information is only issued for multi-mirror pairs with regard to their synchronization.

SYNCHRONIZED = *ANYThe information is issued for all multi-mirror pairs, regardless of their synchronization.

SYNCHRONIZED = *YESThe information is only issued for synchronized multi-mirror pairs.

SYNCHRONIZED = *NOThe information is only issued for non-synchronized multi-mirror pairs.

U41000-J-Z125-4-76 155


REMOTE-COPY-USE =The information is only issued for units with the remote copy use specified.

REMOTE-COPY-USE = *STDThe information is issued for all units, regardless of their remote copy use.

REMOTE-COPY-USE = *TARGET-UNITOf the devices selected with the UNIT operand, only the SRDF source units are considered. The multi-mirror pairs for the target units allocated to the source units are output. This corresponds to the Multi-mirror pair selection via the operand SELECT=*TARGET-UNIT of the commands /HOLD-MULTI-MIRRORING and /RESUME-MULTI-MIRRORING (see also section “Multi-mirror pairs with SRDF target unit” on page 95). Specification of an emulated controller (*BY-CONTROLLER) in the UNIT operand is not supported.

DEVICE = Outputs information about units with the selected status as viewed by BS2000/OSD.

DEVICE = *ALL-PRESELECTEDOutputs information about all units corresponding to the global subsystem setting (value of DEVICE-PRESELECT in the output from/SHOW-SHC-PROCESSING).

DEVICE = *ALL-DEFINEDSelects all units generated in BS2000/OSD.

DEVICE = *DETACHEDSelects units generated in BS2000/OSD but detached.

DEVICE = *ATTACHEDSelects all units attached in BS2000/OSD.

DEVICE = *ANYSelects all the units belonging to the Symmetrix specified in UNIT independently of the generation in BS2000/OSD.

INFORMATION =Selects information about the additional mirror units assigned to the normal unit.

INFORMATION = *CURRENTThe additional mirror unit currently attached is shown.

INFORMATION = *ALL-ADD-MIRRORSAll additional mirror units attached until now are shown.

156 U41000-J-Z125-4-76


Examples

/SHOW-MULTI-MIRRORING-STATUS UNIT=*BY-CONTR(CONTR-UNIT=5400)

SYSOUT output

/SHOW-MULTI-MIRRORING-STATUS UNIT=*BY-SYMM(SERIAL-NO=227,LOGICAL-VOLUME=100)

SYSOUT output

/SHOW-MULTI-MIRRORING-STATUS UNIT=*BY-SYMM(SERIAL-NO=227,LOGICAL-VOLUME=100),REMOTE-COPY-USE=*TARGET-UNIT

SYSOUT output

/SHOW-MULTI-MIRRORING-STATUS UNIT=5244,INF=*ALL-ADD-MIRRORS

SYSOUT output

% ---------------------------------------------------------------------- % NORMAL- !ADD-MIRROR-!SERIAL-NO !STATE !PENDING-SYNCH % UNIT VOLUME!UNIT VOLUME! ! !NORM-UNIT ADD-MIRR % ====================================================================== % 5400 41K.00!5410 !000282600920!ESTABLISHED ! 0 MB 0 MB % 5407 !5417 !000282600920!SPLIT ! 1 MB 28 MB % 5423 !#102 !000282600920!ESTABLISHING ! 0 MB 122 MB % !5432 !000282600920!UNUSED ! 0 MB 0 MB

% ------------------------------------------------------------------------ % NORMAL- !ADD-MIRROR- !SERIAL-NO !STATE !PENDING-SYNCH % UNIT VOLUME!UNIT VOLUME! ! !NORM-UNIT ADD-MIRR % ======================================================================== % #0100 !#011A !000184500227!ESTABLISHED ! 0 MB 0 MB

% ------------------------------------------------------------------------% NORMAL- !ADD-MIRROR- !SERIAL-NO !STATE !PENDING-SYNCH % UNIT VOLUME!UNIT VOLUME! ! !NORM-UNIT ADD-MIRR% ========================================================================% 5200 ! 522C !000183500813!ESTABLISHED ! 0 MB 0 MB

% ===========================================================================% NORMAL-UNIT: 5244 NORMAL-VOLUME: OLB.00 SERIAL-NO: 000183500813 % ---------------------------------------------------------------------------% ADD-MIRROR- !STATE !SPLIT-SINCE !PENDING-SYNCH % UNIT VOLUME! !DDDD.HH:MM:SS!CURR: NORM: ADD-M: BACKG: % ---------------------------------------------------------------------------% 52C4 !ESTABLISHED ! - ! 0 MB 0 MB 0 MB 0 MB % 52C7 !SPLIT ! 0.23:05:21! 0 MB 1 MB 0 MB 0 MB % 52C8 !SPLIT ! 123.06:33:20! 0 MB 1 MB 234 MB 0 MB % 52C9 !SPLIT !1234.01:05:21! 0 MB 1 MB 333 MB 0 MB

U41000-J-Z125-4-76 157


Meanings of the output columns

(part 1 of 2)

Keyword Meaning with INF =

ADD-MIRROR-UNIT

MN of an additional mirror unit (business continuance volume) or internal device number in the Symmetrix with prefix #

*CURRENT

ADD-MIRRORS-UNIT

MN of an additional mirror unit (business continuance volume) or internal device number in the Symmetrix with prefix #

*ALL-ADD-MIRRORS

ADD-MIRROR-VOLUME

VSN of an additional mirror unit *CURRENT

ADD-MIRRORS-VOLUME

VSN of an additional mirror unit *ALL-ADD-MIRRORS

NORMAL-UNIT MN of a normal unit or internal device number in the Symmetrix with prefix # *CURRENT /*ALL-ADD-MIRRORS

NORMAL-VOLUME VSN of a normal unit *CURRENT /*ALL-ADD-MIRRORS

PENDING-SYNCH Pending write jobs for the unit/status in question (in MB or GB) *ALL-ADD-MIRRORS

ADD-M Pending write jobs for the additional mirror unit while the status *ESTABLISHING is active

BACKG Pending background write jobs during a background SPLIT for an additional mirror unit

CURR Pending write jobs while the statuses *ESTABLISHING or *RECONSTRUCTING are active

NORM Pending write jobs for the normal unit

PENDING-SYNCH Pending write jobs for the unit/status in question (in MB or GB) *CURRENT

ADD-MIRR Pending write jobs for the additional mirror unit while the status *ESTABLISHING is active

NORM Pending write jobs for the normal unit

SERIAL-NO Serial number of the Symmetrix subsystem *CURRENT /*ALL-ADD-MIRRORS

SPLIT-SINCE Time since last split (SPLIT), Format: dddd.hh:mm:ss *ALL-ADD-MIRRORS

158 U41000-J-Z125-4-76


STATE Device status.Possible values:

*CURRENT /*ALL-ADD-MIRRORS

UNUSED: Unit is not connected to a normal unit

UNUSED-LOCKED: Unit is not connected to a normal unit and it is protected against unintentional overwriting.

ESTABLISHING: Copying from the normal unit to the additional mirror unit (synchronization) after /START-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING

ESTABLISHED: Normal unit and additional mirror unit are synchronized

SPLITTING: Additional mirror unit is separated from the normal unit after /HOLD-MULTI-MIRRORING

SPLIT: Split processing, data discrepancy is recorded

SPLIT-BACKG: Split processing, data discrepancy is recorded. The splitting process has been started but not yet completed

SPLIT-LOCKED: Split processing, data discrepancy is recordedAdditional mirror unit is protected against unintentional overwriting.

SPLIT-LOCKED-B: Split processing, data discrepancy is recordedAdditional mirror unit is protected against unintentional overwriting. The splitting process has been started but not yet completed

RECONSTRUCTING: Copying from the additional mirror unit to the normal unit after splitting and /RESUME-MULTI-MIRRORING

(part 2 of 2)


U41000-J-Z125-4-76 159


S variables (part 1 of 3)

Output information Name of the S variable T Contents Condition Inf=

Pending write jobs for an additional mirror unit while the status *ESTABLISHING is active (in MB)

var(*LIST).ADD-MIRROR(*LIST).ADD-PEND

I <integer 0..65535> *ALL-ADD-M

Pending background write jobs during a back-ground SPLIT for an additional mirror unit (in MB)

var(*LIST).ADD-MIRROR(*LIST).BACKG-PEND


SPLIT process running in background or completed

’’: Status is not *SPLIT or *UNUSEDY: SPLIT process in backgroundN: no SPLIT process in background

vsn(*LIST).ADD-MIRROR(*LIST).BACKG-SPLIT

S ’’YN

*ALL-ADD-M

Pending write jobs while the statuses *ESTABLISHING or *RECONSTRUCTING are active (in MB)

var(*LIST).ADD-MIRROR(*LIST).CURR-PEND


Lock against overwriting the additional mirror unit with status *SPLIT or *UNUSED

’’: status is not *SPLIT or *UNUSEDY: additional mirror unit lockedN: additional mirror unit not locked

var(*LIST).ADD-MIRROR(*LIST).LOCKED

S ’’YN

*ALL-ADD-M

Internal device number of an additional mirror unit (B C V)

var(*LIST).ADD-MIRROR(*LIST).LOGIC-VOL

S ’’<cstring 1..4>

*ALL-ADD-M

Pending write jobs on the normal unit (in Mbyte) var(*LIST).ADD-MIRROR(*LIST).NORM-PEND


Time in seconds since the last split of an addi-tional mirror unit (BCV)

var(*LIST).ADD-MIRROR(*LIST).SPLIT-SINCE


*ALL-ADD-M

160 U41000-J-Z125-4-76


Device status of an additional mirror unit (BCV).*UNUSED: Unit is not connected to a

normal unit*ESTABLISHING: Copying from the

normal unit to the additional mirror unit (syn-chronization) after /START-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING

*ESTABLISHED: Additional mirror unit and nor-mal unit are synchronized

*SPLITTING: Additional mirror unit is separated from the normal unit after /HOLD-MULTI-MIRRORING

*SPLIT: Split processing, data discrepancy is recorded

*RECONSTRUCTING: Copying of the additional mirror unit to the normal unit (after splitting and /RESUME-MULTI-MIRRORING)

var(*LIST).ADD-MIRROR(*LIST).STA

S *UNUSED*ESTABLISHING*ESTABLISHED*SPLITTING*SPLIT*RECONSTRUCT-

ING

*ALL-ADD-M

MN of an additional mirror unit (BCV) var(*LIST).ADD-MIRROR(*LIST).UNIT

S ’’<mnemo-name>

*ALL-ADD-M

VSN of a additional mirror unit var(*LIST).ADD-MIRROR(*LIST).VOL

S ’’<vsn>

*ALL-ADD-M

Internal device number of an additional mirror unit (B C V)

var(*LIST).ADD-MIRROR-LOGIC-VOL


*CURR

Pending write jobs for an additional mirror unit while the status *ESTABLISHING is active (in MB)

var(*LIST).ADD-MIRROR-PEND I <integer 0..65535> *CURR

MN of an additional mirror unit (BCV) var(*LIST).ADD-MIRROR-UNIT S ’’<mnemo-name>

*CURR

VSN of the additional mirror unit var(*LIST).ADD-MIRROR-VOL S ’’<vsn>

*CURR

SPLIT process running in background or completed

’’: Status is not *SPLIT or *UNUSEDY: SPLIT process in backgroundN: no SPLIT process in background

vsn(*LIST).BACKG-SPLIT S ’’YN

*CURR

Internal device number of a normal unit var(*LIST).NORMAL-LOGIC-VOL S ’’<cstring 1..4>

*CURR /*ALL-ADD-M

Pending write jobs for the normal unit (in MB) var(*LIST).NORMAL-PEND I <integer 0..65535> *CURR

MN of a normal unit var(*LIST).NORMAL-UNIT S ’’<mnemo-name>

*CURR /*ALL-ADD-M

(part 2 of 3)


U41000-J-Z125-4-76 161


VSN of a normal unit var(*LIST).NORMAL-VOL S ’’<vsn>

*CURR /*ALL-ADD-M

Number of assigned additional mirror units var(*LIST).NUM-OF-ADD-MIRROR I <integer 0..65535> *ALL-ADD-M

Lock against overwriting the additional mirror unit with status *SPLIT or *UNUSED

’’: status is not *SPLIT or *UNUSEDY: additional mirror unit lockedN: additional mirror unit not locked

var(*LIST).LOCKED S ’’YN

*CURR

Device status*UNUSED: Unit is not connected to a

normal unit*ESTABLISHING: Copying from the

normal unit to the additional mirror unit (synchronization) after /START-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING

*ESTABLISHED: Additional mirror unit and normal unit are synchronized

*SPLITTING: Additional mirror unit is separated from the normal unit after /HOLD-MULTI-MIRRORING

*SPLIT: Split processing, data discrepancy is recorded

*RECONSTRUCTING: Copying of the additional mirror unit to the normal unit (after splitting and /RESUME-MULTI-MIRRORING)

var(*LIST).STA S *UNUSED*ESTABLISHING*ESTABLISHED*SPLITTING*SPLIT*RECONSTRUCT-

ING

*CURR

Serial number of the Symmetrix disk storage subsystem

var(*LIST).SERIAL-NO S ’’<cstring 3..12>

*CURR /*ALL-ADD-M

(part 3 of 3)


162 U41000-J-Z125-4-76





task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1010 Microcode status not supported (too low or too high)64 NDE1030 No multi-mirror function for the unit64 NDE1043 Pubset type not supported 64 NDE1100 Invalid pubset status 64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2006 There is no output information64 NDE2011 No Symmetrix license entered

U41000-J-Z125-4-76 163

Commands SHOW-REMOTE-COPY-STATUS

SHOW-REMOTE-COPY-STATUSDisplay status of remote copy pairs

/SHOW-REMOTE-COPY-STATUS displays the status of remote copy pairs and remote links.

The remote copy status can be: ACTIVE, ERROR or IN-HOLD. The remote copy status is dependent on the availability of the physical source units, target units and (at least) one remote link - in other words, that the physical volumes that contain the source or target units are ready for operation; it does not mean that the source or target units can be addressed from the host. For more details see also section “Remote copy status” on page 54.


Domain: DEVICE


Routing code: @

164 U41000-J-Z125-4-76

SHOW-REMOTE-COPY-STATUS Commands

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), the mnemonic name of emulated controllers (*BY-CONTROLLER), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume. At least one unit for each emulated controller of the Symmetrix must be attached.

UNIT = *BY-VOLUME(...)Selects the units by means of a specific archive number. The information is output on private or public volumes.

VOLUME = list-poss(24): <vsn 1..6>The archive number of the volume. Up to 24 volumes can be specified in a list.

SHOW-REMOTE-COPY-STATUS

UNIT = *BY-VOLUME(...) / *BY-PUBSET(...) / *BY-CONTROLLER / *BY-SYMMETRIX(...) /

list-poss(24): <alphanum-name 2..2> / <x-text 4..4>

*BY-VOLUME(...)


*BY-PUBSET(...)


*BY-CONTROLLER(...)


,REMOTE-CONTROLLER = *ANY / <alphanum-name 2..2> / <x-text 4..4>

*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = *ALL / *ALL-SOURCE-UNITS / *ALL-TARGET-UNITS /

<x-text 1..4>


*BY-ATTRIBUTES(...)

REMOTE-COPY-STATUS = *ANY / *ACTIVE / *ERROR / *IN-HOLD

,TARGET-ACCESS = *ANY / *BY-SOURCE / *DIRECT / *NONE

,SYNCHRONIZED = *ANY / *YES / *NO

,LINK-STATUS = *ANY / *AVAILABLE / *NOT-AVAILABLE

,COPY-MODE = *ANY / *SYNCHRONOUS / *SEMI-SYNCHRONOUS / *ADAPTIVE-COPY

,ON-ERROR = *ANY / *HOLD / *CONTINUE

,DEVICE = *ALL-PRESELECTED /*ALL-DEFINED / *ATTACHED / *DETACHED / *ANY

,INFORMATION = *SUMMARY / *PARAMETERS / *LINK-STATUS / *ALL

U41000-J-Z125-4-76 165






REMOTE-CONTROLLER = Selects the remote copy pairs using the related remote Symmetrix as well.

REMOTE-CONTROLLER = *ANYThe information is output on all the remote copy pairs of the controllers selected by means of CONTROLLER-UNIT.

REMOTE-CONTROLLER = <alphanum-name 2..2> / <x-text 4..4>The information is only for remote copy pairs with the controller selected with CONTROLLER-UNIT. The remote copy pairs have to be linked to the remote Symmetrix selected by means of the explicitly specified mnemonic name of the remote controller.



LOGICAL-VOLUME = Selects the logical volumes of the Symmetrix.


LOGICAL-VOLUME = *ALL-SOURCE-UNITSSelects all source units of the Symmetrix.

LOGICAL-VOLUME = *ALL-TARGET-UNITSSelects all target units of the Symmetrix.

166 U41000-J-Z125-4-76



UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>Selects the units by means of the mnemonic device name of the logical volume. Up to 24 logical volumes can be specified in a list.

SELECT =The information volume can be selected according to the remote copy status, access path, synchronization, link status, copy mode and the remote copy parameter ON-ERROR.

SELECT = *ALL-PRESELECTEDThe information volume is not restricted.

SELECT = *BY-ATTRIBUTES(...)The information volume is restricted by means of the selection criteria.

REMOTE-COPY-STATUS =This information is only issued for remote copy pairs with the specified remote copy status.

REMOTE-COPY-STATUS = *ANYThis information is issued for all remote copy pairs, regardless of their remote copy status.

REMOTE-COPY-STATUS = *ACTIVEThis information is only issued for ACTIVE remote copy pairs.

REMOTE-COPY-STATUS = *IN-HOLDThis information is only issued for IN-HOLD remote copy pairs.

REMOTE-COPY-STATUS = *ERRORThis information is only issued for remote copy pairs with the remote copy status ERROR.

TARGET-ACCESS =This information is only issued for remote copy pairs with the specified access path.

TARGET-ACCESS = *ANYThis information is issued for all remote copy pairs, regardless of the access path set.

TARGET-ACCESS = *BY-SOURCEThis information is issued for all remote copy pairs with the BY-SOURCE access path.

TARGET-ACCESS = *DIRECTThis information is issued for all remote copy pairs with the DIRECT access path.

TARGET-ACCESS = *NONEThis information is issued for all remote copy pairs with no access path to the target unit.

U41000-J-Z125-4-76 167


SYNCHRONIZED =This information on the remote copy pairs is issued depending on their synchronization.

SYNCHRONIZED = *ANYThis information is issued for all remote copy pairs, regardless of their synchronization.

SYNCHRONIZED = *YESThis information is only issued for synchronized remote copy pairs.

SYNCHRONIZED = *NOThis information is only issued for non-synchronized remote copy pairs.

LINK-STATUS =This information is only issued for remote copy pairs with the specified availability of the remote link.

LINK-STATUS = *ANYThis information is issued for all remote copy pairs, regardless of the availability of their remote link.

LINK-STATUS = *AVAILABLEThis information is only issued for remote copy pairs whose remote link is available.

LINK-STATUS = *NOT-AVAILABLEThis information is only issued for remote copy pairs whose remote link is not available.

COPY-MODE =This information is only issued for remote copy pairs with the specified copy mode.

COPY-MODE = *ANYThis information is issued for all remote copy pairs, regardless of their copy mode.

COPY-MODE = *SYNCHRONOUSThis information is only issued for remote copy pairs with the copy mode SYNCHRONOUS.

COPY-MODE = *SEMI-SYNCHRONOUSThis information is only issued for remote copy pairs with the copy mode SEMI-SYNCHRONOUS.

COPY-MODE = *ADAPTIVE-COPYThis information is only issued for remote copy pairs with the copy mode ADAPTIVE-COPY.

168 U41000-J-Z125-4-76


ON-ERROR =This information is issued for remote copy pairs depending on the set remote copy parameter ON-ERROR.

ON-ERROR = *ANYThis information is issued for all remote copy pairs, regardless of the set remote copy parameter ON-ERROR.

ON-ERROR = *HOLDThis information is only issued for remote copy pairs with the remote copy parameter ON-ERROR=HOLD .

ON-ERROR = *CONTINUEThis information is only issued for remote copy pairs with the remote copy parameter ON-ERROR=CONTINUE .

DEVICE = Information is output about units with the selected status as seen by BS2000/OSD.

DEVICE = *ALL-PRESELECTEDThe information about all units corresponding to the global setting for the subsystem will be output. (Value of DEVICE-PRESELECTION in the output from/SHOW-SHC-PROCESSING).

DEVICE = *ALL-DEFINEDAll units generated in BS2000/OSD are selected.

DEVICE = *DETACHEDAll units generated in BS2000/OSD but which are detached units are selected.

DEVICE = *ATTACHEDAll units attached in BS2000/OSD are selected.


U41000-J-Z125-4-76 169


INFORMATION =A header line is output, and a line for each unit containing the appropriate values.The information issued always relates to the remote copy pairs selected with SELECT=....

INFORMATION = *SUMMARYOverview information is output on the mnemonic names of the source and target units, the remote copy status, the access path, the status of the source and target units, the remote link and the synchronization status of the source and the target units.

The information issued corresponds to the view on the remote copy pair and not on the individual units. /SHOW-SYMMETRIX-DEVICE-CONFIG (see page 192) supplies detailed information on individual units. The status TARGET-DEVICE=*ERROR, for instance, will show an error or an interruption in the remote copy operation, but not the status of the target unit as such.

Output format SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCHUNIT UNIT !STATE ACCESS !DEVICE DEVICE !

INFORMATION = *PARAMETERSInformation is output on the processing mode (COPY-MODE, WR-BUFF, PEND-UPD-LIM) and the remote copy parameters (ON-ERR, PEND-UPD).

Output format SOURCE TARGET VOLUME!COPY-MODE: !ON- !PEND-UPD-ON-TARG: UNIT UNIT !MODE WR-BUFF P-UPD-LIM!ERROR !ALLOW CURR-SIZE

INFORMATION = *LINK-STATUSInformation is output on the status of the remote links and of the remote copy pairs. The assignment of the units to the RA groups is indicated under GRP (letters A through H), see also “RA groups” on page 48.

Output format SOURCE TARGET!SOURCE CONTR1 DIRECTOR : !TARGET CONTR1 DIRECTOR: UNIT UNIT !/SERIAL-NO GRP NO STA P-C !/SERIAL-NO GRP NO STA P-C

INFORMATION = *ALLAll the information specified for *SUMMARY, *PARAMETERS and *LINK-STATUS is output.

i

170 U41000-J-Z125-4-76


Examples

/SHOW-REMOTE-COPY-STATUS UNIT=*BY-PUBSET(PUBSET=RDF),INFORMATION=*SUMMARY

/SHOW-REMOTE-COPY-STATUS UNIT=*BY-PUBSET(PUBSET=RDF),INFORMATION=*PARAMETERS

/SHOW-REMOTE-COPY-STATUS UNIT=*BY-PUBSET(PUBSET=RDF), INFORMATION=*LINK-STATUS

SYSOUT outputs

INFORMATION=*SUMMARY

INFORMATION=*PARAMETERS

INFORMATION=*LINK-STATUS

% --------------------------------------------------------------------% SOURCE TARGET VOLUME!REM-COPY TARGET !SOURCE TARGET LINK !SYNCH% UNIT UNIT !STATE ACCESS !DEVICE DEVICE ! % ====================================================================% 5244 5844 RDF.00!ACTIVE BY-SOURCE!IN-USE IN-USE AVAILABLE! YES % 5245 5845 RDF.01!IN-HOLD BY-SOURCE!IN-USE ERROR AVAILABLE! NO % 5246 5846 RDF.02!ACTIVE BY-SOURCE!IN-USE IN-USE AVAILABLE! YES

% --------------------------------------------------------------------------% SOURCE TARGET VOLUME!COPY-MODE: !ON- !PEND-UPD-ON-TARG: % UNIT UNIT !MODE WR-BUFF P-UPD-LIM!ERROR !ALLOW CURR-SIZE% ==========================================================================% 5244 5844 RDF.00!SYNCH - - !CONTI !NO 0 MB % 5245 5845 RDF.01!SEMI-SYNCH - - !CONTI !NO 0 MB % 5246 5846 RDF.02!AD-COPY CACHE 999!CONTI !NO 0 MB

% ------------------------------------------------------------------------ % SOURCE TARGET!SOURCE CONTR1 DIRECTOR : !TARGET CONTR1 DIRECTOR: % UNIT UNIT !/SERIAL-NO GRP NO STA P-C !/SERIAL-NO GRP NO STA P-C % ======================================================================== % 5244 5844 ! 5200 B 5B ENA Y ! 5800 B 12B ENA Y % !000183500813 B 12B ENA Y !000183500026 B 5B ENA Y % ------------------------------------------------------------------------ % 5245 5845 ! 5200 B 5B ENA Y ! 5800 B 12B ENA Y % !000183500813 B 12B ENA Y !000183500026 B 5B ENA Y % ------------------------------------------------------------------------ % 5246 5846 ! 5200 B 5B ENA Y ! 5800 B 12B ENA Y % !000183500813 B 12B ENA Y !000183500026 B 5B ENA Y % ------------------------------------------------------------------------

U41000-J-Z125-4-76 171


Meanings of the output columns

(part 1 of 3)


COPY-MODE:MODE

Processing mode (see section “COPY-MODE (processing mode)” on page 51).Possible values:

*PAR / *ALL

SYNCH: Target unit is updated before the next time the source unit is write accessed

SEMI-SYNC: Target unit is no more than one processing step behind the source unit

AD-COPY: The write jobs are processed asynchronously

COPY-MODE:P-UPD-LIM

Max. number of pending write jobs (0...65535)-: Irrelevant for the set processing mode

*PAR / *ALL

COPY-MODE:WR-BUFF

Recording of the pending write jobs. Possible values:

*PAR / *ALL

CACHE: Recorded in the cache

DISK: Recorded on the volume

-: Irrelevant for the set processing mode

DIRECTOR: GRP

RA group of the remote link director for the source and the target unit (A, B, ..., H or ’’)

*ALL / *LINK-STA

DIRECTOR: NO

Name of the remote link director for the source and the target unit (1A...16A, 1B...16B, ...,1H...16H or ’’)

*ALL / *LINK-STA

DIRECTOR:STA

Status of the remote link director for the source and target unit.Possible values:

*ALL / *LINK-STA

ENABLE: Remote link director activated and connected

DISABLE: Remote link director deactivated or not connected

UNDEFINED: No information available on the remote link director

DIRECTOR: P-C

Port connected.Possible values:

*ALL / *LINK-STA

Y: At least one port is connected

N: No ports are connected

LINK Status of the remote links.Possible values:

*SUM / *ALL

AVAILABLE: Remote link activated and connected

NOT-AVAIL: Remote link deactivated or not connected

UNDEFINED: No information available on the remote link

172 U41000-J-Z125-4-76


ON-ERR Specifies what is to happen in the event of the failure of part of the remote copy pair (see section “ON-ERROR” on page 53).Possible values:

*PAR / *ALL

HOLD: In the event of part of the failure of part of the remote copy pair, the applications are put on hold and wait for a reply.

CONTI: In the event of part of the failure of part of the remote copy pair, processing continues with the remaining unit.

PEND-UPD-ON-TARG: ALLOW

Transition to READY with write jobs pending on the target unit.Possible values:

*PAR / *ALL

YES: Transition permitted

NO: Transition not permitted

UNDEF: No information, since the remote Symmetrix with the target units is not available

PEND-UPD-ON-TARG:CURR-SIZE

Current value of the pending write jobs from the source unit and intended for the target unit in MB or GB (only at the Symmetrix with the target unit)

*PAR / *ALL

REM-COPY-STATE Remote copy status. Possible values:

*SUM / *ALL

ACTIVE: Remote copy operation active

IN-HOLD: Remote copy operation interrupted by means of /HOLD-REMOTE-COPY

ERROR: Remote copy operation interrupted on account of an error

SOURCE CONTR1 MN of the first emulated controller (of the Symmetrix that contains the source unit)

*ALL / *LINK-STA

SOURCEDEVICE(S)

Status of the source units.Possible values:

*SUM / *ALL

IN-USE: Used for SRDF

ERROR: Error situation

FREE: Not used for SRDF

SOURCE SERIAL-NO

Serial number of the Symmetrix with the source unit (R1) *ALL / *LINK-STA

SOURCE UNIT MN or internal device numbers in the Symmetrix with prefix # of the source units (R1)

*SUM / *PAR / *ALL / *LINK-STA

(part 2 of 3)


U41000-J-Z125-4-76 173


SYNCH Synchronization status of a remote copy pairPossible values:

*SUM / *ALL

YES: Remote copy pair is synchronous

NO: Remote copy pair is not synchronous

TARGET-ACCESS Access path for the data of a remote copy pair. Possible values:

*SUM / *ALL

BY-SOURCE: Access via the source path

DIRECT: Access via the target path

NONE: Access not possible

TARGET CONTR1 MN of the first emulated controller (of the Symmetrix that contains the target unit)

*ALL / *LINK-STA

TARGETDEVICE

Status of the target units.Possible values:

*SUM / *ALL

IN-USE: Used for SRDF

ERROR: Error situation

FREE: Not used for SRDF

TARGET SERIAL-NO

Serial number of the Symmetrix with the target unit (R2) *ALL / *LINK-STA

TARGET UNIT MN or internal device number in the Symmetrix with prefix # of the target unit (R2)

*SUM / *PAR / *ALL / *LINK-STA

VOLUME VSN of the (logical) volume *SUM / *PAR / *ALL / *LINK-STA

(part 3 of 3)


174 U41000-J-Z125-4-76



Output in (part 1 of 4)formation Name of the S variable T Contents Condition INF =

MN of the first emulated controller (of the Symmetrix that contains the source unit)

var(*LIST).LINK.SOURCE-CONTR-UNIT1

S ’’<mnemonic name>

*ALL /*LINK-STA

Name of the remote link director var(*LIST).LINK.SOURCE-DIR(*LIST).DIR-NO

S ’’<1A....16A><1B....16B>...<1H....16H>

*ALL /*LINK-STA

Remote link director group of the source unit var(*LIST).LINK.SOURCE-DIR(*LIST).GROUP-NO

S ’’<c-string 0..1>

*ALL / *LINK-STA

Port connected.Y: At least one port is connected N: No ports are connected

var(*LIST).LINK.SOURCE-DIR(*LIST).PORT-CONNECTION

S ’’YN

*ALL /*LINK-STA

Status of the remote link directors of the source unit.

*ENABLE: Remote link directors activated and connected

*DISABLE: Remote link directors deactivated or not connected

var(*LIST).LINK.SOURCE-DIR(*LIST).STA

S ’’*ENABLE*DISABLE

*ALL /*LINK-STA

MN of the first emulated controller (of the Symmetrix unit that contains the target unit)

var(*LIST).LINK.TARGET-CONTR-UNIT1

S ’’<mnemonic name>

*ALL /*LINK-STA

Name of the remote link director var(*LIST).LINK.TARGET-DIR(*LIST).DIR-NO

S ’’<1A....16A><1B....16B>...<1H....16H>

*ALL /*LINK-STA

Remote link director group of the target unit var(*LIST).LINK.TARGET-DIR(*LIST).GROUP-NO

S ’’<c-string 0..1>

*ALL / *LINK-STA

Port connected.Y: At least one port is connected N: No ports are connected

var(*LIST).LINK.TARGET-DIR(*LIST).PORT-CONNECTION

S ’’YN

*ALL /*LINK-STA

Status of the remote link directors of the target unit .

*ENABLE: Remote link directors activated and connected

*DISABLE: Remote link directors deactivated or not connected

var(*LIST).LINK.TARGET-DIR(*LIST).STA

S ’’*ENABLE*DISABLE

*ALL /*LINK-STA

U41000-J-Z125-4-76 175


Processing mode (see page 51).*SYNCH: Target unit is updated before the

next time the source unit is write-accessed*SEMI-SYNCH: Target unit is no more than

one processing step behind the source unit*ADAPTIVE-COPY: The write jobs are

processed asynchronously

var(*LIST).PAR.COPY-MODE S *SYNCH*SEMI-SYNCH*ADAPTIVE-COPY

*PAR / *ALL

Specifies what is to happen in the event of the failure of part of the remote copy pair (see page 53)

*HOLD: In the event of the failure of part of the remote copy pair, the applications are put on hold and wait for a reply

*CONTI: In the event of the failure of part of the remote copy pair, processing continues with the remaining unit

var(*LIST).PAR.ON-ERROR S *HOLD*CONTI

*PAR / *ALL

Transition to READY with pending write jobs.

*YES: Transition permitted *NO: Transition not permitted ’’: No information, since there is no access to

the target unit“

var(*LIST).PAR.PEND-UPD-ALLOWED

S ’’*YES*NO

*PAR / *ALL

Max. number of pending write jobs at COPY-MODE=*ADAPTIVE-COPY

’’: at COPY-MODE=*SYNCH and *SEMI-SYNCH

var(*LIST).PAR.PEND-UPD-LIMIT I ’’<integer 0..65535>

*PAR / *ALL

Current value of the pending write jobs from the source unit and intended for the target unit in MB

var(*LIST).PAR.PEND-UPD-SIZE I ’’<integer 0..65535>

*PAR / *ALL

Recording of the pending write jobs. *CACHE: Recorded in the cache*DISK: Recorded on the volume’’: At COPY-MODE=*SYNCH and

*SEMI-SYNCH

var(*LIST).PAR.WRITE-BUF S ’’*CACHE*DISK

*PAR / *ALL

Internal device number of the source unit (R1)

var(*LIST).SOURCE-LOGIC-VOL S ’’<c-string 0..4>

*LINK-STA / *PAR / *SUM / *ALL

(part 2 of 4)


176 U41000-J-Z125-4-76


Serial number of the Symmetrix with the source unit (R1).

var(*LIST).SOURCE-SERIAL-NO S ’’<c-string 0..12>


MN of the source unit (R1) var(*LIST).SOURCE-UNIT S ’’<mnemonic name>

*LINK-STA /*PAR / *SUM / *ALL

Status of the remote links.*AVAIL: Remote links activated and

connected *NOT-AVAIL: Remote links deactivated or

not connected

var(*LIST).SUMM.LINK-STA S *AVAIL*NOT-AVAIL

*SUM / *ALL

Remote copy status.*ACTIVE: Remote copy operation active*IN-HOLD: Remote copy operation

interrupted by means of /HOLD-REMOTE-COPY

*ERROR: Remote copy operation interrupted due to an error

var(*LIST).SUMM.REM-COPY-STA S *ACTIVE*IN-HOLD *ERROR

*SUM / *ALL

Status of the synchronization.*YES: Remote copy pair is synchronous*NO: Remote copy pair is not synchronous

var(*LIST).SUMM.REM-COPY-SYNCH

S *YES*NO

*SUM / *ALL

Status of the source units. *IN-USE: Used for SRDF*ERROR: Error situation*FREE: Not used for SRDF

var(*LIST).SUMM.SOURCE-DEV-STA S *IN-USE*ERROR*FREE

*SUM / *ALL

Access path for the data of a remote copy pair.

*BY-SOURCE: Access via source path *DIRECT: Access via target path *NONE: Access not possible

var(*LIST).SUMM.TARGET-ACCESS S *BY-SOURCE*DIRECT*NONE

*SUM / *ALL

Status of the target units.*IN-USE: Used for SRDF*ERROR: Error situation*FREE: Not used for SRDF

var(*LIST).SUMM.TARGET-DEV-STA S *IN-USE*ERROR*FREE

*SUM / *ALL

Internal device number of the target unit (R2) var(*LIST).TARGET-LOGIC-VOL S ’’<c-string 0..4>


(part 3 of 4)


U41000-J-Z125-4-76 177


Serial number of the Symmetrix with the target unit (R2).

var(*LIST).TARGET-SERIAL-NO S ’’<c-string 0..12>


MN of the target unit (R2) var(*LIST).TARGET-UNIT S ’’<mnemonic name>


VSN of the volume var(*LIST).VOL S ’’<vsn>


(part 4 of 4)


178 U41000-J-Z125-4-76



(SC2) SC1 Maincode Meaning0 CMD0001 Command successfully executed 1 CMD0202 Syntax error


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1010 Microcode status not supported (too low or too high)64 NDE1020 No remote copy function for the specified unit64 NDE1024 Remote controller not found64 NDE1100 Invalid pubset status 64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2006 No output information available 64 NDE2011 No Symmetrix license entered

U41000-J-Z125-4-76 179

Commands SHOW-SHC-PROCESSING

SHOW-SHC-PROCESSINGDisplay Internal settings

/SHOW-SHC-PROCESSING displays information on the current internal maintenance and diagnostic settings of SHC-OSD for maintenance and diagnosis. You can use /MODIFY-SHC-PROCESSING to change these settings (see page 125).


Example

Output of the presettings for the subsystem.

/SHOW-SHC-PROCESSING

SYSOUT output

Domain: DEVICE

Privileges: TSOS

SHOW-SHC-PROCESSING

% SHOW-SHC-PROCESSING (SHC-OSD VERSION 03.0A00)% TRACE: % EXTENDED-TRACE=*OFF,RELEASE-TRACE-AT-UNLOAD=*YES % TRACE-SIZE= 256 kB,ERROR-TRACE-SIZE= 64 kB % LOCK-RETRY: % WAIT-TIME= 1 s,RETRY-COUNT= 30 % IO-RETRY: % WAIT-TIME= 2 s,RETRY-COUNT= 30 % SYNCH-WAIT-RETRY: % WAIT-TIME= 30 s,RETRY-COUNT= 20 % STATE-CHANGE-POLLING: % SHORT-INTERVAL= 60 s,NORMAL-INTERVAL= 600 s % LONG-INTERVAL= 3600 s,SELECT-DEVICES=*ATTACHED % LOG-CHANGES= *ALL-EVENTS % DEVICE-PRESELECT = *ALL-DEFINED % SYSTEM-ADMIN-SCOPE % DETACHED-DEVICES = *REJECT % NOT-DEFINED-DEVICES = *REJECT % TASK-ADMIN-SCOPE % DETACHED-DEVICES = *SYSTEM-ADMIN-SCOPE % NOT-DEFINED-DEVICES = *SYSTEM-ADMIN-SCOPE % MAX-MULTI-BCV-PER-DEVICE = 8

180 U41000-J-Z125-4-76

SHOW-SHC-PROCESSING Commands

Meaning of the output columns (part 1 of 2)

Keyword Meaning Operand value

DEVICE- PRESELECT

Preset number of units for SHOW output *ALL-DEFINED*ANY

COMM-RETRY: RETRY-COUNT

Retry count for internal FITC communication <integer 1..100>

COMM-RETRY: WAIT-TIME

Wait time between retries for internal FITC communication <integer 10..100>

IO-RETRY:RETRY-COUNT

Retry count when an expected status change has not occurred in the Symmetrix.

<integer 1..100>

IO-RETRY:WAIT-TIME

Wait time between retries when an unexpected status change has not occured in the Symmetrix.

<integer 1..10>

LOCK-RETRY:RETRY-COUNT

Retry count when a lock conflict occurs. <integer 1..100>

LOCK-RETRY:WAIT-TIME

Wait time between retries when a lock conflict occurs. <integer 1..10>

STATE-CHANGE-POLLING:LOG-CHANGES

All status changes that were detected are issued.Only global status changes are issued.

*ALL-EVENTS*MAJOR-EVENTS

STATE-CHANGE-POLLING:LONG-INTERVAL

Polling interval for checks at long intervals (i.e. a supported Symmetrix unit was not found at the last polling).

<integer 120..86400>

STATE-CHANGE-POLLING:NORMAL-INTERVAL

Polling interval for checks at normal intervals (i.e. no problem occurred at the last polling).

<integer 20..7200>

STATE-CHANGE-POLLING:SELECT-DEVICES

Status changes are output for all generated devices. Status changes are only output for attached devices.

*ALL*ATTACHED

STATE-CHANGE-POLLING:SHORT-INTERVAL

Polling interval for checks at short intervals (i.e. a Symmetrix unit was not accessible at the last polling).

<integer 10..3600>

SYMAPI-DEBUG Shows whether SYMAPI is running in debug mode, i.e. whether extended DEBUG entries for SYMAPI are written in the current log file under/var/symapi/log in the POSIX file system

*ON*OFF

SYMAPI VERSION Version of the SYMAPI program interface <char 0..8>

SYNCH-WAIT-RETRY:RETRY-COUNT

Retry count for queries on synchronous command conclusion when a lock conflict occurs.

<integer 1..100>

SYNCH-WAIT-RETRY:WAIT-TIME

Wait time between two queries on synchronous command conclusion.

<integer 1..120>

SYSTEM-ADMIN-SCOPE:DETACHED-DEVICES

System-wide save setting for detached devices. *REJECT*ACCEPT

SYSTEM-ADMIN-SCOPE:NOT-DEFINED-DEVICES

System-wide save settings for devices, which are not recognized by BS2000/OSD (devices not generated).

*REJECT*ACCEPT

U41000-J-Z125-4-76 181


TASK-ADMIN-SCOPE:DETACHED-DEVICES

Local (task-specific) security setting for detached units. *REJECT*ACCEPT*SYSTEM-ADMIN-SCOPE

TASK-ADMIN-SCOPE:NOT-DEFINED-DEVICES

Local (task-specific) security setting for units that are not known to BS2000/OSD (non-generated units).

*REJECT*ACCEPT*SYSTEM-ADMIN-SCOPE

TRACE: RELEASE-TRACE-AT-UNLOAD

Trace areas are released when SHC-OSD is unloaded. Trace areas are not released when SHC-OSD is unloaded in order to facilitate diagnostics.

*YES*NO

TRACE:ERROR-TRACE-SIZE

Size of the error trace area in Kbyte. <integer 64..4096>

TRACE:EXTENDED-TRACE

Controls the size of the entries in the normal trace of SHC-OSD. When EXT=*ON is specified, additional information is recorded in order to facilitate diagnostics. The initial setting is *OFF.

*OFF*ON

TRACE:TRACE-SIZE

Size of the trace area in Kbyte. <integer 64..4096>

(part 2 of 2)

Keyword Meaning Operand value

182 U41000-J-Z125-4-76

SHOW-SHC-PROCESSING Commands


Output information Name of the S variable T Contents Condition

Predefined number of units for SHOW informa-tion output

*ALL-DEFINED: only units known in BS2000/OSD

*ANY: all units

var(*LIST).DEV-PRESELECT *ALL-DEFINED*ANY

Maximum number of retries for communication var(*LIST).COMM-RETRY.LIM I <integer 0..100>

Maximum number of retries for inputs/outputs var(*LIST).IO-RETRY.LIM I <integer 0..30>

Wait time (in seconds) on communication retry var(*LIST).COMM-RETRY.TIME I <integer 10..100>

Wait time (in seconds) on input/output retries var(*LIST).IO-RETRY.TIME I <integer 0..120>

Maximum number of retries if lock conflicts occur

var(*LIST).LOCK-RETRY.LIM I <integer 0..30>

Wait time (in seconds) on retries caused by lock conflicts

var(*LIST).LOCK-RETRY.TIME I <integer 0..120>

Logging of status changes:Events.

*ALL-EVENTS: All events*MAJOR-EVENTS: Only global events

var(*LIST).STA-CHA-POLLING.LOG-CHA

S *ALL-EVENTS*MAJOR-EVENTS

Polling of status changes:long interval

var(*LIST).STA-CHA-POLLING.LONG-INTERVAL

I <integer 0..7200>

Polling of status changes:short interval

var(*LIST).STA-CHA-POLLING.NORMAL-INTERVAL

I <integer 0..3600>

Logging of status changes: Units.

*ATTACH: Only for attached units*ALL: For all units

var(*LIST).STA-CHA-POLLING.SEL-DEV

S *ATTACH*ALL

Polling of status changes:short interval

var(*LIST).STA-CHA-POLLING.SHORT-INTERVAL

I <integer 0..120>

Version number of the SYMAPI program var(*LIST).SYMAPI-VERSION S '<c-string 0..8>

Maximum number of retries to check synchro-nization

var(*LIST).SYNCH-RETRY.LIM I <integer 0..30>

Wait time (in seconds) on retries to check synchronization

var(*LIST).SYNCH-RETRY.TIME I <integer 0..120>

Global security setting for detached units*REJECT: Process rejected*ACCEPT: Process accepted

var(*LIST).SYS-ADM-SCOPE.PROCESS-DET-DEV

S *REJECT*ACCEPT

Global security setting for units not known in BS2000/OSD.

*REJECT: Process rejected*ACCEPT: Process accepted

var(*LIST).SYS-ADM-SCOPE.PROCESS-NOT-DEF-DEV

S *REJECT*ACCEPT

U41000-J-Z125-4-76 183



Local (task-specific) security setting for detached units

*SYS-ADM-SCOPE: Global setting is valid locally


var(*LIST).TASK-ADM-SCOPE.PROCESS-DET-DEV

S *SYS-ADM-SCOPE*REJECT*ACCEPT

Local (task-specific) security setting for unitsnot known in BS2000/OSD.

*SYS-ADM-SCOPE: Global setting is valid locally


var(*LIST).TASK-ADM-SCOPE.PROCESS-NOT-DEF-DEV

S *SYS-ADM-SCOPE*REJECT*ACCEPT

Size of error trace var(*LIST).TRACE.ERROR-SIZE I <integer 0..4096>

Extended trace*ON: Switched on*OFF: Switched off

var(*LIST).TRACE.EXT S *ON*OFF

Release of trace on unloading subsystem*YES or *NO

var(*LIST).TRACE.REL-AT-UNLOAD S *YES*NO

Size of trace var(*LIST).TRACE.SIZE I <integer 0..4096>

Version number of the SHC-OSD subsystem var(*LIST).VERSION S ’’<cstring 0..7>



task privileges64 CMD0216 Required privilege not available

(part 2 of 2)

Output information Name of the S variable T Contents Condition

184 U41000-J-Z125-4-76

SHOW-SYMMETRIX-CONFIGURATION Commands

SHOW-SYMMETRIX-CONFIGURATIONDisplay Symmetrix configuration

/SHOW-SYMMETRIX-CONFIGURATION displays information on the Symmetrix configuration, such as the microcode status, cache size and configuration of the directors (adapters).


UNIT =Selects the units by means of the mnemonic name of the emulated controllers (*BY-CONTROLLER) or the Symmetrix serial number (*BY-SYMMETRIX) or selection of all Symmetrix systems (*ALL). At least one unit per emulated Symmetrix controller must be attached.


CONTROLLER-UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>The mnemonic name of the emulated controller.Up to 24 emulated controllers can be specified in a list.

Domain: DEVICE


Routing code: @

SHOW-SYMMETRIX-CONFIGURATION

UNIT = *BY-CONTROLLER(...) / *BY-SYMMETRIX(...) / *ALL

*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


,INFORMATION = *STD / *DIRECTORS /*LOCKS / *ALL

,REMOTE-CONFIGURATION = *NO / *YES

U41000-J-Z125-4-76 185

Commands SHOW-SYMMETRIX-CONFIGURATION

UNIT = *BY-SYMMETRIX(...)Specifies the unit by means of the Symmetrix serial number.


UNIT = *ALL Output for all Symmetrix systems known to the host.

INFORMATION =Specifies the scope of the information to be output.

INFORMATION = *STDGlobal Symmetrix information is output.

Output format CONTR-UNIT TYPE SERIAL-NO CACHE-SIZE EMUL-TYPE MICROCODE HOST-ACCESS

INFORMATION = *DIRECTORSInformation is output on the directors of the Symmetrix. The output field GR-NO indicates the assignment of the remote link directors to the RA groups (letters A through H), see also “RA groups” on page 48.

Output format SERIAL-NO / !DIRECTOR: !REM-LINK: !REMOTE CONTR-UNIT !NO TYPE STATE PORT-CONNECTION!TYPE GR-NO! SERIAL-NO

INFORMATION = *LOCKSThe global Symmetrix locks and the associated RA groups are output. The operand INFORMATION=*LOCKS is only supported in combination with UNIT=*BY-SYMMETRIX(SERIAL-NUMBER=<alphanum-name 3..12>).

Output format SERIAL-NO !GR-NO!LOCKED-SINCE:

INFORMATION = *ALLThe information described for both *STD and *DIRECTORS is output.

REMOTE-CONFIGURATION =Determines whether information is output only for local or also for remote Symmetrix system controllers.

REMOTE-CONFIGURATION = *NOInformation is output only for the directly accessible, generated Symmetrix system controllers.

186 U41000-J-Z125-4-76


REMOTE-CONFIGURATION =*YESInformation is output for the directly accessible, generated Symmetrix system controllers and, if necessary, for Symmetrix systems that are available via remote connections.

Examples

/SHOW-SYMMETRIX-CONFIGURATION CONTROLLER-UNIT=5A00,REMOTE-CONFIG=*YES,INFORMATION=*STD

/SHOW-SYMMETRIX-CONFIGURATION CONTROLLER-UNIT=5A00,INFORMATION=*DIRECTORS

SYSOUT outputs

INFORMATION=*STD

INFORMATION=*DIRECTORS

% ------------------------------------------------------------------------% CONTR-UNIT TYPE SERIAL-NO CACHE-SIZE EMUL-TYPE MICROCODE HOST-ACCESS% ========================================================================% 5A00, 5A01 8430 000184500219 8192 MB 3860-51 5567/ 32 DIRECT % ------------------------------------------------------------------------% 8430 000184500227 8192 MB 3860-51 5567/ 32 REMOTE % ------------------------------------------------------------------------

% --------------------------------------------------------------------% SERIAL-NO / !DIRECTOR: !REM-LINK: !REMOTE % CONTR-UNIT !NO TYPE STATE PORT-CONNECTION!TYPE GR-NO! SERIAL-NO % ====================================================================% 000184500219! 1A DA ENABLE - - - - ! - - ! % 5A00, 5A01 ! 2A DA ENABLE - - - - ! - - ! % ! 3A FC DISABLE N - - - ! - - ! % ! 4A EA ENABLE N Y - - ! - - ! % !13A EA ENABLE Y N - - ! - - ! % !14A RA ENABLE Y - - - ! F B !000184500227% !15A DA ENABLE - - - - ! - - ! % !16A DA ENABLE - - - - ! - - ! % ! 1B DA ENABLE - - - - ! - - ! % ! 2B DA ENABLE - - - - ! - - ! % ! 3B FC DISABLE N - - - ! - - ! % ! 4B EA ENABLE Y Y - - ! - - ! % !13B EA ENABLE Y Y - - ! - - ! % !14B RA ENABLE Y - - - ! F B !000184500227% !15B DA ENABLE - - - - ! - - ! % !16B DA ENABLE - - - - ! - - ! % --------------------------------------------------------------------% --------------------------------------------------------------------

U41000-J-Z125-4-76 187


Meaning of the output columns (part 1 of 2)


CACHE-SIZE Cache size in Mbytes *STD / *ALL

CONTR-UNIT MN of the (first) emulated controller or the channel (SPARC) *STD / *DIR / *ALL

DIRECTOR NO

Name of the director (1A...16A, 1B...16B, ..., 1H...16H) *DIR / *ALL

DIRECTOR PORT-CONNECTION

Port connected (4 per director) (Y / N / -) *DIR / *ALL

DIRECTORSTATE

Status of the director.Possible values:

*DIR / *ALL

ENABLE: Director activated and connected

DISABLE: Director deactivated or not connected

DIRECTORTYPE

Director type. Possible values:

*DIR / *ALL

EA: Adapter for channel type S

EF: Adapter for channel type F

CA: Channel adapter for channel type 2

SA: SCSI adapter

RA: Remote adapter

DA: Disk adapter

FC: Fibre channel adapter

EMUL-TYPE Type of the emulated controller (3860-42, 3860-43, 3860-51) *STD / *ALL

GR-NO RA group of the remote link director (A, B, ..., H or ’) *LOCKS

HOST-ACCESS Host access to Symmetrix disk storage subsystemsPossible values:

DIRECT: Directly via a connected unit

REMOTE: Via the SRDF partner’s remote connection

NO: Access not currently possible

*STD / *ALL

LOCKED-SINCE Time for which lock has been held, format: dddd.hh:mm:ss *LOCKS

MICROCODE Microcode status (family/patch level) *STD / *ALL

188 U41000-J-Z125-4-76


REM-LINK GR-NO

RA group of the remote link directors (A, B, ..., H or ’’) *DIR / *ALL

REM-LINK TYPE

Type of the remote link director.Possible values:

*DIR / *ALL

M: Master for channel type S

S: Slave for channel type S

F: Fiber channel adapter

I: SRDF over IP adapter

REMOTESERIAL-NO

Serial number of the Symmetrix disk storage subsystem which is connected via SRDF

*STD / *ALL

SERIAL-NO Serial number of the Symmetrix disk storage subsystem *STD / *ALL /*LOCKS

TYPE Type of the Symmetrix disk storage subsystem *STD / *ALL

(part 2 of 2)


U41000-J-Z125-4-76 189



Output information Name of the S variable T Contents INF =

Cache size in Mbytes var(*LIST).CACHE-SIZE I <integer 0..4> *STD / *ALL

MN of the first emulated controller or the channel

var(*LIST).CONTR-UNIT1 S ’’<mnemo-name>

*DIR / *ALL

MN of the emulated controller var(*LIST).CONTR-UNIT(*LIST) S ’’<mnemo-name>

*STD / *ALL

Name of the director var(*LIST).DIR(*LIST).DIR-NO S <1A...16A><1B...16B>...<1H...16H>

*DIR / *LOCKS/*ALL

Port 1 connected var(*LIST).DIR(*LIST).PORT-CONNECTION1

S ’’YN

*DIR / *LOCKS/*ALL


S ’’YN

*DIR / *LOCKS/*ALL


S ’’YN

*DIR / *LOCKS/*ALL


S ’’YN

*DIR / *LOCKS/*ALL

Status of the director*ENABLE: Director activated and connected*DISABLE: Director deactivated or not

connected.

var(*LIST).DIR(*LIST).STA S *ENABLE*DISABLE

*DIR / *LOCKS/*ALL

Remote serial number var(*LIST).DIR(*LIST)REM-SERIAL-NO

S <c-string 0..12> *DIR / *ALL

Time for which lock has been held var(*LIST).DIR(*LIST).LOCKED-SINCE

S ’<c-string 13..13>

*LOCKS

Remote link director group var(*LIST).DIR(*LIST).GROUP-NO S ’’<c-string 0..1>

*DIR / *LOCKS/*ALL

Remote link director type: *F: Fibre channel*I: SRDF over IP*M: Master for channel type S*S: Slave for channel type S

var(*LIST).DIR(*LIST).REM-LINK-TYPE

S ’’*F*I*M*S

*DIR / *ALL

190 U41000-J-Z125-4-76


Director type: *EA: Adapter for channel type S*EF: Adapter for channel type F*CA: Channel adapter for channel type 2*SA: SCSI adapter*RA: Remote adapter*DA: Disk adapter*FC: Fibre channel adapter

var(*LIST).DIR(*LIST).TYPE S*EA*EF*CA*SA*RA*DA*FC

*DIR / *LOCKS/*ALL

Typ of the emulated controller var(*LIST).EMULATED-TYPE S 3860-423860-433860-512105

*STD / *ALL

Access from the host*DIRECT: Direct access*REMOTE: Remote access*NO: No access

var(*LIST).HOST-ACCESS S*DIRECT*REMOTE*NO

*STD / *ALL

Microcode status (family) var(*LIST).MICROCODE-LEVEL S <c string 0..4> *STD / *ALL

Microcode status (patch level) var(*LIST).PATCH-LEVEL S <c string 0..4> *STD / *ALL

Serial number var(*LIST).SERIAL-NO S <c string 0..12> *STD / *ALL

Symmetrix type var(*LIST).TYPE S <c string 0..4> *STD / *ALL

(part 2 of 2)

Output information Name of the S variable T Contents INF =

U41000-J-Z125-4-76 191





task privileges64 CMD0216 Required privilege not available64 NDE1002 Controller not found64 NDE1007 No Symmetrix controller found64 NDE1010 Microcode status not supported (too low or too high)64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2006 No output information available64 NDE2011 No Symmetrix license entered

192 U41000-J-Z125-4-76

SHOW-SYMMETRIX-DEVICE-CONFIG Commands

SHOW-SYMMETRIX-DEVICE-CONFIGDisplay Symmetrix device configuration

/SHOW-SYMMETRIX-DEVICE-CONFIG displays information on the logical devices of the Symmetrix systems, such as the device name, device type, status, RAID mode, volume size etc.

At least one unit of the Symmetrix must be attached.


Domain: DEVICE


Routing code: @

(part 1 of 2)

SHOW-SYMMETRIX-DEVICE-CONFIG


list-poss(24): <alphanum-name 2..2> / <x-text 4..4>

*BY-VOLUME(...)


*BY-PUBSET(...)


*BY-CONTROLLER(...)


*BY-SYMMETRIX(...)


,LOGICAL-VOLUME = *ALL / <x-text 1..4>

continued ➠

U41000-J-Z125-4-76 193

Commands SHOW-SYMMETRIX-DEVICE-CONFIG

UNIT =Selects the units by means of a specific archive number (*BY-VOLUME), a specific catalog ID (*BY-PUBSET), the mnemonic name of the emulated controller (*BY-CONTROLLER), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or the mnemonic device name of the logical volume. At least one unit per emulated controller of the Symmetrix must be attached.

UNIT = *BY-VOLUME(...)Selects the units by means of the archive number. The information is issued for private and public volumes.

VOLUME = list-poss(24): <vsn 1..6>The volume serial number of the volume. Up to 24 volumes can be specified in a list.




*BY-ATTRIBUTES(...)

CONFIGURATION = *STD / *CONTROLLER / *SUBSYSTEM / *REMOTE-COPY-PAIR /

*MULTI-MIRROR-PAIR / *ALL-MIRRORS / *PHYSICAL-DISK /

*META-MEMBERS

,DEVICE = *ALL-PRESELECTED / *ALL-DEFINED / *ATTACHED / *DETACHED / *ANY

,TYPE = *ANY / <device>

,RAID-LEVEL = *ANY / *YES / *RAID1 / *RAIDS / *RAID10 / *NO

,STATE = *ANY / *READY / *NOT-READY / *DISABLE / *READ-ONLY / *NO-ACCESS

,REMOTE-COPY-USE = *ANY / *YES / *SOURCE-UNIT / *TARGET-UNIT / *NO

,MULTI-MIRROR-USE = *ANY / *YES / *NORMAL-UNIT / *ADD-MIRROR-UNIT / *NO

,INFORMATION = *STD / *PHYSICAL / *ALL / *LOGICAL-VOLUME-NUMBER / *LOCKED-DEVICES

(part 2 of 2)

194 U41000-J-Z125-4-76








UNIT = list-poss(24): <alphanum-name 2..2> / <x-text 4..4>Selects the units by means of the mnemonic names of the logical volume. Up to 24 logical volumes can be specified in a list.

SELECT =The information volume can be selected on the basis of the configuration, device, device type, status, RAID protection, remote copy use and multi-mirror use.

SELECT = *ALL-PRESELECTEDThe information volume is not restricted. The global setting for the subsystem applies (value of DEVICE-PRESELECTION in the output from /SHOW-SHC-PROCESSING).

SELECT = *BY-ATTRIBUTES(...)The information volume is restricted by means of selection criteria.

CONFIGURATION =Selects the configuration to be output. The selection may be further restricted by speci-fying additional selection criteria.

CONFIGURATION = *STDIf a mnemonic device name, an archive number or a catalog ID was specified for the operand UNIT, information is issued only for the units specified.If an emulated controller was specified for the operand UNIT, information is issued for all units belonging to that controller.

U41000-J-Z125-4-76 195


CONFIGURATION = *CONTROLLERThis information is issued for all units belonging to the controllers selected with UNIT. This value may not be specified together with DEVICE=*ANY.

CONFIGURATION = *SUBSYSTEMThis information is issued for all units belonging to the Symmetrix systems selected with UNIT.

CONFIGURATION = *REMOTE-COPY-PAIRThis information is only issued for the units selected with UNIT and for any remote copy pairs that might be allocated to them.This must not be used in conjunction with UNIT=*BY-CONTROLLER or LOGICAL-VOLUME=*ANY.

CONFIGURATION = MULTI-MIRROR-PAIRThis information is only issued for the units selected with UNIT and for any multi-mirror pairs that might be allocated to them.This must not be used in conjunction with UNIT=*BY-CONTROLLER or LOGICAL-VOLUME=*ANY.

CONFIGURATION = *ALL-MIRRORSThis information is only issued for the units selected with UNIT and for any remote copy pairs that might be allocated to them. This must not be used in conjunction with UNIT=*BY-CONTROLLER or LOGICAL-VOLUME=*ANY.

CONFIGURATION = *PHYSICAL-DISKThis information is issued for all physical volumes selected with UNIT and for all other logical volumes located on the same physical volume of a Symmetrix controller. This output does not consider any additional internal mirrored disks that might be located on that physical device.This must not be used in conjunction with UNIT=*BY-CONTROLLER or LOGICAL-VOLUME=*ANY.

CONFIGURATION = *META-MEMBERSThis information is output on all units selected with UNIT and all other units belonging to the same meta-volume. The value may not specified together with UNIT=*BY-CONTROL-LER or LOGICAL-VOLUME=*ANY.

DEVICE = This information is issued for units having the specified status in BS2000/OSD.

DEVICE = *ALL-PRESELECTEDThe information about all units corresponding to the global setting for the subsystem is shown (value of DEVICE-PRESELECTION in the output from /SHOW-SHC-PROCESSING).

DEVICE = *ALL-DEFINEDAll units generated in BS2000/OSD are selected.

196 U41000-J-Z125-4-76


DEVICE = *DETACHEDSelects all units generated in BS2000/OSD but which are detached.

DEVICE = *ATTACHEDSelects all units attached in BS2000/OSD.


TYPE = This information is only issued for units with the specified emulated device type.

TYPE = *ANYThis information is issued for all units, regardless of their emulated device type.

TYPE = <device>This information is only issued for specific device types.Only device types known to the system are accepted. In dialog mode, the valid device types can be displayed with TYPE=?. Information can only be issued for device types emulated in the Symmetrix.

STATE = This information is only issued for units which are in the specified state from the viewpoint of the Symmetrix.

STATE= *ANYThis information is issued for all devices, regardless of their status from the viewpoint of the Symmetrix.

STATE = *READYThis information is only issued for units which have the status *READY.

STATE = *NOT-READYThis information is only issued for units which have the status *NOT-READY.

STATE = *DISABLEThis information is only issued for units which have the status *DISABLE.

STATE = *READ-ONLYThis information is only issued for units which have the status *READ-ONLY.

STATE = *NO-ACCESSThis information is only issued for units which have the status *NO-ACCESS. These could also be PAV alias units. For more information on parallel access volumes, see page 313 and the manual “Introductory Guide to Systems Support” [5].

U41000-J-Z125-4-76 197


RAID-LEVEL = This information is only issued for units with the specified RAID protection.

RAID-LEVEL= *ANYThis information is issued for all units, regardless of their RAID protection.

RAID-LEVEL = *YESThis information is only issued for units with RAID protection.

RAID-LEVEL = *RAID1This information is only issued for units with RAID protection according to RAID1.

RAID-LEVEL = *RAIDSThis information is only issued for units with RAID protection according to RAIDS.

RAID-LEVEL = *RAID10This information is only issued for type RAID10 units, i.e. striped CKD meta-volumes.

RAID-LEVEL = *NOThis information is only issued for units without RAID protection.

REMOTE-COPY-USE = This information is only issued for units with the specified remote copy use.

REMOTE-COPY-USE = *ANYThis information is issued for all units, regardless of their remote copy use.

REMOTE-COPY-USE = *YESThis information is only issued for remote copy units (source and target units).

REMOTE-COPY-USE = *SOURCE-UNITThis information is only issued for source units.

REMOTE-COPY-USE = *TARGET-UNITThis information is only issued for target units.

REMOTE-COPY-USE = *NOThis information is only issued for units that are not used for remote copy.

MULTI-MIRROR-USE = This information is only issued for units with the specified multi-mirror use.

MULTI-MIRROR-USE = *ANYThis information is issued for all units, regardless of their multi-mirror use.

198 U41000-J-Z125-4-76


MULTI-MIRROR-USE = *YESThis information is only issued for multi-mirror units (normal units and additional mirror units).

MULTI-MIRROR-USE = *NORMAL-UNITThis information is only issued for normal units.

MULTI-MIRROR-USE = *ADD-MIRROR-UNITThis information is only issued for additional mirror units.

MULTI-MIRROR-USE = *NOThis information is only issued for units that are not used for multi-mirroring.

INFORMATION =A header line is output, and a line for each unit containing the appropriate values.The information issued always relates to the units selected with SELECT=....

INFORMATION = *STDGlobal device information is issued, e.g. the mnemonic name of the logical volumes, VSN, BS2000 type, mnemonic controller name, status, RAID level, remote copy use (SRDF), multi-mirror use, usable or maximum volume size.

Output format UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MULTI- SIZE: /SERIAL-NO COPY MIRROR CURR./MAXIMUM

INFORMATION = *PHYSICALThe mnemonic name of the logical volume and its VSN is issued. The mirroring type (RAID1, RAIDS, TimeFinder, SRDF), synchronization status, the location and the status are output for the relevant physical volumes (up to 4 mirrored disks).The status refers to the internal mirroring method, i.e. the status READY means that the device is available for internal mirroring, and not that the device can be accessed by the host.

Output format UNIT VOL !INTERNAL-DISK: PHYSICAL-INFORMATION !TYPE PENDING DA-NO DISK STA !TYPE PENDING DA-NO DISK STA

INFORMATION = *ALLAll the information described for *STD and *PHYSICAL is output.

U41000-J-Z125-4-76 199


INFORMATION = *LOGICAL-VOLUME-NUMBERThe same information is issued as with INFORMATION=*STD, except that the internal Symmetrix number of the logical volume is issued instead of the VSN. This information is of particular interest to the service engineers. No S variables are supported with this operand value.

Output format UNIT SYMM- TYPE CONTR-UNIT1 STATE RAID REM- MULTI- SIZE: LOG-VOL /SERIAL-NO COPY MIRROR CURR./MAXIMUM

INFORMATION = *LOCKED-DEVICESInformation is issued for all units for which a lock is held. The operand SELECT is not evalu-ated for this. The operand INFORMATION=*LOCKED-DEVICES is only supported in combination with UNIT=*BY-SYMMETRIX(..).

Output format UNIT !SERIAL-NO LOG-VOL!LOCKED-SINCE:

Examples

/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=5700,CONFIGURATION=*REMOTE-COPY-PAIR, DEVICE=*ANY,INFORMATION=*STD

/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=5700,CONFIGURATION=*REMOTE-COPY-PAIR, DEVICE=*ANY,INFORMATION=*PHYSICAL

/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=*BY-PUBSET(PUBSET=OLB), INFORMATION=*ALL

/SHOW-SYMMETRIX-DEVICE-CONFIG UNIT=5700,CONFIGURATION=*REMOTE-COPY-PAIR, DEVICE=*ANY,INFORMATION=*LOGICAL-VOLUME-NUMBER

SYSOUT outputs

INFORMATION=*STD

% -----------------------------------------------------------------------------% UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MUL- SIZE: % /SERIAL-NO /META COPY MIRR CURR./MAXIMUM % =============================================================================% 5700 D3435 5700 NOT-READY -/- T N - / 449 MB% #0000 D3435 000184600024 READY -/- S N - / 449 MB

200 U41000-J-Z125-4-76


INFORMATION=*PHYSICAL

INFORMATION=*ALL

INFORMATION=*LOGICAL-VOLUME-NUMBER

% ----------------------------------------------------------------------------% UNIT VOL !INTERNAL-DISK: PHYSICAL-INFORMATION % !TYPE PENDING DA-NO DISK STA !TYPE PENDING DA-NO DISK STA % ============================================================================% 5700 !REMOTE: 0 MB READY!LOCAL : 0 MB 1A C2 READY% !ADD-M : 0 MB 1A D1 N-RDY % #0000 !LOCAL : 0 MB 1A C2 READY!REMOTE: 0 MB READY% !ADD-M : 1 MB 2B C0 READY

% ----------------------------------------------------------------------------% UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MULTI- SIZE: % /SERIAL-NO COPY MIRROR CURR./MAXIMUM % ============================================================================% 5244 OLB.00 D3490-30 5200 READY - S N 2054/ 2348 MB% 5245 OLB.01 D3490-30 5200 READY - S N 2054/ 2348 MB% 5246 OLB.02 D3490-30 5200 READY - S N 2054/ 2348 MB% ----------------------------------------------------------------------------% UNIT VOL !INTERNAL-DISK: PHYSICAL-INFORMATION % !TYPE PENDING DA-NO DISK STA !TYPE PENDING DA-NO DISK STA % ============================================================================% 5244 OLB.00!LOCAL : 0 MB 2A C1 READY!REMOTE: 0 MB READY% !ADD-M : 51 MB 2A C2 N-RDY % 5245 OLB.01!LOCAL : 0 MB 15B C3 READY!REMOTE: 0 MB READY% !ADD-M : 1 MB 15B C2 N-RDY % 5246 OLB.02!LOCAL : 0 MB 3A C1 READY!REMOTE: 0 MB READY

% -----------------------------------------------------------------------------% UNIT VOL TYPE CONTR-UNIT1 STATE RAID REM- MUL- SIZE: % /SERIAL-NO /META COPY MIRR CURR./MAXIMUM % =============================================================================% 5700 0 D3435 5700 NOT-READY -/- T N - / 449 MB% #0000 0 D3435 000184600024 READY -/- S N - / 449 MB

U41000-J-Z125-4-76 201


Meaning of the output columns

(part 1 of 3)


CONTR-UNIT1 MN of the (first) emulated controller *STD / *ALL

DA-NO Director name (DA) of physical devices *PHYS / *ALL

DISK Physical device on director (DA) *PHYS / *ALL

META Meta-volumePossible values:

H/S: Header of a striped meta-volume

M/S: Member of a striped meta-volume

H/C: Header of a concatenated meta-volume

M/C: Member of a concatenated meta-volume

-: Not a meta-volume

*STD / *ALL

MULTI-MIRROR Multi-mirror functionality.Possible values:

*STD / *ALL

N: Normal unit

A: Additional mirror unit

-: No multi-mirror functionality

PENDING Pending write jobs on the relevant physical device in Mbytes *PHYS / *ALL

RAID RAID level Possible values:

*STD / *ALL

1: RAID1 (mirroring)

S: RAIDS (3 data volumes : 1 parity volume or 7:1)

10: RAID10 (striped CKD volume)

-: No RAID protection

REM-COPY Remote copy operation (SRDF).Possible values:

*STD / *ALL

S: Source unit

T: Target unit

-: No remote copy operation

CURR-SIZE Usable size of the volume in Mbytes *STD / *ALL

202 U41000-J-Z125-4-76


LOCKED-SINCE Time for which the lock has been held, format: dddd.hh:mm:ss *LOCKED

LOG-VOL Symmetrix internal device number *LOCKED

MAXIMUM-SIZE Maximum size of the volume in Mbytes *STD / *ALL

SERIAL-NO Serial number of the Symmetrix disk storage subsystem *STD / *ALL /*LOCKED

STA Status of the relevant physical device (mirrored disks).Possible values:

*PHYS / *ALL

READY: Device ready for operation

N-RDY: Device not ready for operation

WR-D: Write to device not possible

STATE Device status of logical unit.Possible values:

*STD / *ALL

READY: Device ready for operation

NOT-READY: Device not ready for operation

READ-ONLY: Read access only (not usable in BS2000/OSD)

DISABLE: Neither read nor write access possible to device

NO-ACCESS: Access not possible; previous status is displayed

NO-ACC-PAV: No access possible because alias unit for PAV (Parallel Access Volume)

SYMM-LOG-VOL Symmetrix internal device number *LOG-VOL

TYPE BS2000 volume type *STD / *ALL

TYPE Device usage.Possible values:

*PHYS / *ALL

LOCAL: Local (primary) unit

MIRROR: Local mirroring (RAID1)

PARITY: Local parity (RAIDS)

REMOTE: Remote mirroring (SRDF)

SPARE: Spare device

ADD-M: Multi-mirror device (TimeFinder)

UNUSED: unused

(part 2 of 3)


U41000-J-Z125-4-76 203


UNIT MN of the logical device or internal device number in the Symmetrix with prefix #

*STD / *PHYS /*LOCKED /*ALL

VOL VSN of the (logical) volume *STD / *PHYS / *ALL

(part 3 of 3)


204 U41000-J-Z125-4-76


S variables

(part 1 of 2)

Output information Name of the S variable T Contents with INF =

MN of the first emulated controller var(*LIST).CONTR-UNIT1 S <mnemonic name> *STD / *ALL

Usable size of the volume in Mbytes var(*LIST).CURR-SIZE I <integer 0..4> *STD / *ALL

Time since the lock has been held var(*LIST).DIR(*LIST).LOCKED-SINCE

S ’’<c-string 13..13>

*LOCKED

Internal device number (logical volume) var(*LIST).LOGIC-VOL S <c-string 0..4> *STD / *ALL / *LOCKED /*LOG-VOL

Maximum size of the volume in Mbytes var(*LIST).MAX-SIZE I <integer 0..4> *STD / *ALL

Meta-volume functionalityHEADER-STRIPED: Striped meta-volume

headerHEADER-CONCAT: Concatenated meta-

volume headerMEMBER-STRIPED: Striped meta-volume

memberMEMBER-CONCAT: Concatenated meta-

volume member

var(*LIST).META-TYPE S HEADER-STRIPEDHEADER-CONCATMEMBER-STRIPEDMEMBER-CONCAT

*STD / *ALL

Multi-mirror functionality. *NORMAL-UNIT: Normal unit*ADD-MIRROR-UNIT: Additional mirror unit

var(*LIST).MULTI-MIRROR S ’’NORMAL-UNITADD-MIRROR-UNIT

*STD / *ALL

PAV alias unit var(*LIST).PAV-ALIAS B *TRUE / *FALSE *STD

Base MN of the PAV alias unit var(*LIST).PAV-BASE-MN S ’’<mnemo-name>

*STD

Director name (DA) of physical devices var(*LIST).PEND-SYNCH(*LIST).DA-NO

S ’’<1A...16A><1B...16B>

*PHYS /*ALL

Physical device on disk adapter (DA) var(*LIST).PEND-SYNCH(*LIST).DISK

S ’’<c string 0..2>

*PHYS /*ALL

Device usage.*LOC: Local (primary) unit *MIRROR: Local mirroring (RAID1)*PARITY: Local parity (RAIDS)*REM: Remote mirroring (SRDF)*SPARE: Spare device*ADD-MIRROR: Multi-mirror unit

(TimeFinder)UNUSED: not used

var(*LIST).PEND-SYNCH(*LIST).INTERNAL-DISK

S *LOC*MIRROR*PARITY*REM*SPARE*ADD-MIRROR*UNUSED

*PHYS /*ALL

U41000-J-Z125-4-76 205


Pending write jobs on physical device (in Mbytes)

var(*LIST).PEND-SYNCH(*LIST).SIZE

I <integer 0..4> *PHYS /*ALL

Status of physical device (mirrored disk).*READY: Device ready for operation*NOT-READY: Device not ready for

operation *WR-DISABLE: Write to device disabled

var(*LIST).PEND-SYNCH (*LIST) STA S *READY*NOT-READY*WR-DISABLE

*PHYS / *ALL

RAID level 1: RAID1 (mirroring)S: RAIDS (3 data volumes : 1 parity volume

or 7:1)10: RAID10 (striped CKD volume)’’: no RAID protection

var(*LIST).RAID S ’’RAID1RAIDSRAID10

*STD / *ALL

Remote copy operation (SRDF)SOURCE-UNIT: Source unitTARGET-UNIT: Target unit’’: No remote copy operation

var(*LIST).REM-COPY S ’’SOURCE-UNITTARGET-UNIT

*STD / *ALL

Serial number var(*LIST).SERIAL-NO S <c-string 0..12> *STD / *LOCKED /*ALL

Device status.*READY: Device ready for operation*NOT-READY: Device not ready for

operation *READ-ONLY: Read access only

(not usable in BS2000/OSD)*DISABLE: Read and write access to device

not possible *NO-ACCESS: Access not possible;

previous status is displayed

var(*LIST).STA S *READY*NOT-READY*READ-ONLY*DISABLE*NO-ACCESS

*STD / *ALL

Emulated device type var(*LIST).TYPE S D3480D348ED348FD3490-xx

*STD / *ALL

MN of the logical volume var(*LIST).UNIT S <mnemonic name> *STD /*PHYS /*ALL

VSN of the logical volume var(*LIST).VOL S ’’<vsn>

*PHYS /*STD / *ALL

(part 2 of 2)

Output information Name of the S variable T Contents with INF =

206 U41000-J-Z125-4-76



(SC2) SC1 Maincode Meaning0 CMD0001 Command successfully executed 1 CMD0202 Syntax error


task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1002 Controller not found64 NDE1003 Volume not online64 NDE1004 Pubset not online64 NDE1010 Microcode status not supported (too low or too high)64 NDE1100 Invalid pubset status64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2006 No output information available64 NDE2011 No Symmetrix license entered

U41000-J-Z125-4-76 207

Commands START-MULTI-MIRRORING

START-MULTI-MIRRORINGCreate multi-mirror pairs

/START-MULTI-MIRRORING creates one or more multi-mirror pairs by assigning an additional mirror unit to a normal unit. All the data is copied either from the normal unit to the additional mirror unit or from the additional mirror unit to the normal unit depending on the setting of the RESTORE operand.

Write jobs from the host to the normal unit are mapped to the additional mirror unit. The additional mirror unit is not available to the host.

The normal unit and additional mirror unit must be on the same Symmetrix and be of the same size and same type. The additional mirror unit can be assigned to any other normal unit as long as it has the status SPLIT. Similarly, the normal unit can be assigned to any other additional mirror unit as long as it has the status SPLIT. If the meta-volumes function is used for the normal unit, the additional mirror unit must also be identical in respect of these properties, i.e. the meta-header volume pairs and all meta-member pairs must be the same size, have the same number and the same “stripe size” as the relevant meta-member volumes.

On execution of the command, the multi-mirror pair assumes the status ESTABLISHING or RECONSTRUCTING. When all the data has been copied from the normal unit to the additional mirror unit, it assumes the status ESTABLISHED. The multi-mirror pair can be split by means of /HOLD-MULTI-MIRRORING.

You can specify a pubset to be mirrored and a list of additional mirror units that are all UNUSED or SPLIT and whose number must correspond to the number of units of the pubset.

If the command is issued only for individual units of a pubset, it must be ensured that multi-mirror pairs are created for all the units of the pubset.

If the additional mirror unit was locked with /HOLD-MULTI-MIRRORING LOCK-ADD-MIRROR= *YES, then /START-MULTI-MIRRORING UNLOCK-ADD-MIRROR=*YES has to be specified to release the lock again.

If TimeFinder pairs which have already been assigned have the status SPLIT, the multi BCV function is used explicitly and changes to additional mirror units which have already been used earlier are recorded in the Symmetrix.

The control option offered in SHC-OSD V3.0 via the operand MULTI-ADD-MIRRORS has been withdrawn as of SHC-OSD V4.0 and not replaced, as this function is not offered by the SYMAPI.

Domain: DEVICE

Privileges: TSOS

208 U41000-J-Z125-4-76

START-MULTI-MIRRORING Commands


If you try to generate more multi BCVs than are permitted with /START-MULTI-MIRRORING, e.g. because different additional mirror units have been assigned, the message NDE1051 is issued. (The maximum number of permitted multi-BCVs is specified with /MODIFY-SHC-PROCESSING via the operand MAX-MULTI-BCV.) The multi BCVs which are no longer required must be released with /STOP-MULTI-MIRRORING.

NORMAL-UNIT =Specifies the normal unit by means of a specific catalog ID (*BY-PUBSET), by the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume.

NORMAL-UNIT = *BY-PUBSET(...)Specifies the normal unit by means of a pubset ID or volume set ID. The SF/SM pubset is locked against reconfiguration while a command is being executed.


START-MULTI-MIRRORING

NORMAL-UNIT = *BY-PUBSET(...) / *BY-SYMMETRIX(...) / <alphanum-name 2..2> / <x-text 4..4>

*BY-PUBSET(...)


*BY-SYMMETRIX(...)



,ADD-MIRROR-UNIT = *BY-SYMMETRIX(...) / list-poss(256): <alphanum-name 2..2> / <x-text 4..4>

*BY-SYMMETRIX(...)

LOGICAL-VOLUME = <x-text 1..4>

,RESTORE = *FROM-ORIGINAL / *TO-ORIGINAL



U41000-J-Z125-4-76 209


NORMAL-UNIT = *BY-SYMMETRIX(...)Specifies the normal unit by means of the Symmetrix serial number and the Symmetrix internal number of the logical volume.



NORMAL-UNIT = <alphanum-name 2..2> / <x-text 4..4>Specifies the normal unit by means of the mnemonic device name of the logical volume of the normal unit.

ADD-MIRROR-UNIT =Specifies the additional mirror unit by means of the mnemonic device name of the logical volume.

ADD-MIRROR-UNIT = list-poss(256): <alphanum-name 2..2> / <x-text 4..4>Specifies the additional mirror unit by means of the mnemonic device name of the logical volume. A unit list is only accepted when a pubset has been specified for the NORMAL-UNIT operand. Up to 256 additional mirror units can be specified in a list.

ADD-MIRROR-UNIT = *BY-SYMMETRIX(...)Specifies the unit by means of the Symmetrix serial number of the logical volume.


RESTORE =Specifies the copy direction.

RESTORE = *FROM-ORIGINALCopies from the normal unit to the additional mirror unit. This is normally the case; an additional mirror unit is attached to a normal unit, in order to be able to use it in parallel.

RESTORE = *TO-ORIGINALCopies from the additional mirror unit to the normal unit. This option is required if the data on the additional mirror unit is to be copied to the normal unit in the course of a data migration (see also page 74).

210 U41000-J-Z125-4-76


UNLOCK-ADD-MIRROR =Specifies whether or not a lock previously set with /HOLD-MULTI-MIRRORING LOCK-ADD-MIRROR=*YES is released.

UNLOCK-ADD-MIRROR = *NONo attempt is made to release an existing lock.If at least one additional mirror unit is still locked, the command is rejected and message NDE1083 is issued.

UNLOCK-ADD-MIRROR = *YESAn existing lock is released.



WAIT = *UNTIL-SYNCHRONIZATIONThe command waits until synchronization is terminated.WAIT=*UNTIL-SYNCHRONIZATION simplifies the programming of test procedures for recovery processes, since extensive queries of the progress of the synchronization for the multi-mirror pairs can be omitted.Waiting can be aborted in dialog mode by means of the [K2] key.

Command processing

The following messages are output to SYSOUT for each device and distributed to CONSOLE via routing code ’0’, i.e. they were only logged in the CONSLOG file.


Examples

/START-MULTI-MIRRORING NORMAL-UNIT=5000,ADD-MIRROR-UNIT=5040

/START-MULTI-MIRRORING NORMAL-UNIT=5001,ADD-MIRROR-UNIT=5041, MULTI-ADD-MIRRORS=*YES(An already existing multi mirror pair with normal unit 5001 must have the status SPLIT)

/START-MULTI-MIRRORING NORMAL-UNIT=*BY-PUBSET(PUBSET=MMF), ADD-MIRROR-UNIT=(5100,5101,5102)

(Pubset MMF consists of 3 units)

U41000-J-Z125-4-76 211



(part 1 of 2)




task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1008 Volume cannot be allocated64 NDE1010 Microcode status not supported (too low or too high)64 NDE1015 Device not defined in BS2000/OSD64 NDE1030 No multi-mirror function for the unit64 NDE1031 Different number of devices for normal units and additional mirror

units 64 NDE1034 Additional mirror unit is already being used in another pair 64 NDE1035 Device is not a normal unit64 NDE1037 MNs of the normal unit and additional mirror unit are identical 64 NDE1038 Normal unit and additional mirror unit differ in type or size 64 NDE1039 Normal unit and additional mirror unit are on different Symmetrix

systems64 NDE1040 Incorrect status of the normal unit64 NDE1041 Incorrect status of the additional mirror unit64 NDE1043 Pubset type not supported 64 NDE1051 Too many additional mirror units64 NDE1100 Invalid pubset status 64 NDE1076 Additional mirror unit has pending write jobs, copy to normal unit

rejected64 NDE1083 Additional mirror unit locked64 NDE1101 More than one sharer for pubset 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk is member of a meta-volume 64 NDE1155 RAID10 devices not supported

212 U41000-J-Z125-4-76


64 NDE1158 Normal unit and additional mirror unit are meta-volumes with different ’stripe size’

64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2009 Command aborted by [K2]


(part 2 of 2)


U41000-J-Z125-4-76 213

Commands STOP-MULTI-MIRRORING

STOP-MULTI-MIRRORING Cancel a multi mirror pair

/STOP-MULTI-MIRRORING terminates the assignment of one or more multi-mirror pairs which have the status SPLIT.

When this command is executed, the additional mirror unit is assigned the status UNUSED and the normal unit indicates no further multi-mirror utilization once the connection to the last additional mirror unit has been interrupted.

If the additional mirror unit has been locked by means of the operand LOCK-ADD-MIRROR=*YES in /HOLD-MULTI-MIRRORING then you must specify the operand UNLOCK-ADD-MIRROR=*YES in /STOP-MULTI-MIRRORING in order to unlock it.


Domain: DEVICE

Privileges: TSOS

STOP-MULTI-MIRRORING

UNIT = *BY-PUBSET(...) / *BY-VOLUME(...) / *BY-SYMMETRIX(...) / <alphanum-name 2..2> / <x-text 4..4>

*BY-PUBSET(...)


*BY-VOLUME(...)

VOLUME = <vsn 1..6>

*BY-SYMMETRIX(...)





,SELECT-ADD-MIRROR = *CURRENT / *PREVIOUS / *OLDEST / *ALL

214 U41000-J-Z125-4-76

STOP-MULTI-MIRRORING Commands

UNIT =Selects the normal unit by means of a specific catalog ID (*BY-PUBSET), a specific archive number (*BY-VOLUME), the Symmetrix serial number and the Symmetrix internal number of the logical volume (*BY-SYMMETRIX) or directly by means of the mnemonic device name of the logical volume.








UNIT = <alphanum-name 2..2> / <x-text 4..4>Specifies the normal unit by means of the mnemonic device name of the logical volume.

UNLOCK-ADD-MIRROR =Specifies whether the lock set previously with /HOLD-MULTI-MIRRORING and Operand LOCK-ADD-MIRROR=*YES is to be released or not.

UNLOCK-ADD-MIRROR = *NOIf there is a lock, it is not released.However, if at least one additional mirror unit is locked, then the command is rejected with message NDE1083.

UNLOCK-ADD-MIRROR = *YESIf there is a lock, it is released.

U41000-J-Z125-4-76 215

Commands STOP-MULTI-MIRRORING

SELECT =Selects the multi-mirror pairs.

SELECT = *STDSelects the multi-mirror pairs of the units specified with the UNIT operand.

SELECT = *TARGET-UNITSelects the multi-mirror pairs that are assigned to the target unit of a remote copy pair. See also section “Multi-mirror pairs with SRDF target unit” on page 95.

SELECT-ADD-MIRROR = Selects the assigned additional mirror units for the multi-mirror pairs selected by means of the SELECT operand. Further details of the Multi BCV function are described in the section “Working with TimeFinder” on page 78.

SELECT-ADD-MIRROR = *CURRENTSelects currently attached additional mirror unit.

SELECT-ADD-MIRROR = *PREVIOUSSelects the additional mirror unit last to be separated.

SELECT-ADD-MIRROR = *OLDESTSelects the oldest additional mirror unit.

SELECT-ADD-MIRROR = *ALLSelects all additional mirror units.

Command processing



Examples

/STOP-MULTI-MIRRORING UNIT=5000, SELECT-ADD-MIRROR=*ALL

/STOP-MULTI-MIRRORING UNIT=*BY-PUBSET(PUBSET=MMF)

216 U41000-J-Z125-4-76

UNLOCK-SYMMETRIX Commands





task privileges64 CMD0216 Required privilege not available64 NDE1000 Device not found or not on Symmetrix64 NDE1001 Device not attached64 NDE1003 Data medium not online or not unique64 NDE1004 Pubset not found or incorrect pubset type64 NDE1008 Volume cannot be allocated64 NDE1010 Microcode status not supported (too low or too high)64 NDE1015 Device not defined in BS2000/OSD64 NDE1030 No multi-mirror function for the unit64 NDE1035 Device is not a normal unit64 NDE1040 Incorrect status of the normal unit64 NDE1041 Incorrect status of the additional mirror unit64 NDE1043 Pubset type not supported 64 NDE1083 Additional mirror unit locked64 NDE1100 Invalid pubset status 64 NDE1101 More than one sharer for pubset 64 NDE1102 Not all volumes of pubset allocated64 NDE1103 No reconfiguration lock for pubset 64 NDE1105 Inconsistent pubset64 NDE1114 Symmetrix serial number not found64 NDE1115 Symmetrix serial number not unique 64 NDE1116 Logical volume of the Symmetrix not found64 NDE1150 Gatekeeper device not found64 NDE1153 Symmetrix device lock set64 NDE1154 Disk belongs to a meta-disk64 NDE1155 RAID10 devices not supported64 NDE2000 Execution partially successful64 NDE2001 Command not executed64 NDE2009 Command aborted by [K2]


U41000-J-Z125-4-76 217

Commands UNLOCK-SYMMETRIX

UNLOCK-SYMMETRIX Release Symmetrix locks

/UNLOCK-SYMMETRIX releases the global internal Symmetrix locks for remote copy operation. They are valid for all RA groups of the entire Symmetrix subsystem. Actions which modify remote copy operation are serialized with this lock in the Symmetrix subsystem.

The currently assigned global Symmetrix locks can be shown with /SHOW-SYMMETRIX-CONFIGURATION ...,INFORMATION=*LOCKS

CAUTION!The command is only provided in case of emergency and must be used with great care. The lock should only be released if it can be ruled out that any other host is carrying out actions at this time to control the remote copy operation.

SERIAL-NUMBER = Selects the Symmetrix subsystem by means of the Symmetrix serial number.

SERIAL-NUMBER = <alphanum-name 12..12>Specifies the Symmetrix serial number (for reasons of security, this cannot be shortened).

Example

/UNLOCK-SYMMETRIX SERIAL-NUM=000184601234


Domain: DEVICE

Privileges: TSOS

UNLOCK-SYMMETRIX



32 NDE2002 Internal error64 CMD0216 Necessary privilege not available64 NDE1114 Symmetrix serial number not found

!

218 U41000-J-Z125-4-76

UNLOCK-SYMMETRIX-DEVICE Commands

UNLOCK-SYMMETRIX-DEVICE Release Symmetrix device locks

/UNLOCK-SYMMETRIX-DEVICE releases the unit-specific device locks of the Symmetrix. They are used by SHC-OSD for all action commands in order to serialize actions on the units of the Symmetrix subsystem.

The currently assigned unit-specific device locks can be shown with /SHOW-SYMMETRIX-DEVICE-CONFIGURATION ...,INFORMATION=*LOCKED-DEVICES.

CAUTION! This command is only provided in case of emergency and must be used with great care. The lock should only be released if it can be ruled out that any other host is carrying out actions for the relevant devices at this time.

SERIAL-NUMBER = Selects the Symmetrix subsystem by means of the Symmetrix serial number.

SERIAL-NUMBER = <alphanum-name 12..12>Specifies the Symmetrix serial number (for reasons of security, this cannot be shortened).

LOGICAL-VOLUME = <x-text 1..4>Specifies the internal Symmetrix number of the logical volume.

LOGICAL-VOLUME = *ALLSelects all units of the Symmetrix.

Example

/UNLOCK-SYMMETRIX SERIAL-NUM=000184601234,LOGICAL-VOLUME=15

Domain: DEVICE

Privileges: TSOS

UNLOCK-SYMMETRIX-DEVICE


,LOGICAL-VOLUME = <x-text 1..4> / *ALL

!

U41000-J-Z125-4-76 219

Commands UNLOCK-SYMMETRIX-DEVICE



32 NDE2002 Internal error64 CMD0216 Necessary privilege not available64 NDE1114 Symmetrix serial number not found64 NDE1154 Disk belongs to a meta-disk

220 U41000-J-Z125-4-76

UNLOCK-SYMMETRIX-DEVICE Commands

U41000-J-Z125-4-76 221

7 Program interfaceSHC-OSD provides a program interface that supports all the information functions of the SHOW commands. The interface is designed as the NDEINF assembly language macro and the ndeinf.h C header file.

7.1 The NDEINF assembly language macro

The NDEINF macro provides information on the Symmetrix status and configuration. The type and extent of the information depends on the value of the INF operand.

The output area is created in class 6 memory. The release of the output memory is the responsibility of the caller. The fields for the output have a gray background in the parameter list (see page 246). The address of the output area is given to the caller in the NDEIOPTR field and points to the first output record. The number of output records, the length of an output record and the total length of the output area in bytes are specified in other fields.

The NDEINF macro can only be called by programs running under a user ID with the privilege TSOS, OPERATING, HW-MAINTENANCE or SW-MONITOR-ADMINISTRATION.

Information on Operands

Symmetrix configuration INF=*SYMM_CONF, UNITTYPE=*CONTR_UNIT or *ALL

Symmetrix device status INF=*DEV_CONF, every UNITTYPE except *ALL

Remote copy status (SRDF) INF=*REMOTE_COPY, every UNITTYPE except *ALL

Multi-mirroring status (TimeFinder) INF=*MULTI_MIRROR, every UNITTYPE except *ALL

222 U41000-J-Z125-4-76

The NDEINF assembly language macro Program interface

Format

(part 1 of 2)

Macro Operands

NDEINF MF=D / L / C / M / E

,PREFIX=N / p

,MACID=DEI / mac

,PARAM=adr / (r)

,VERSION=002 / <c-string_without_quotes 1..3>

,XPAND=PARAM / MULTI_MIRROR / X_MULTI_MIRROR / REMOTE_COPY / DEV_CONF /

SYMM_CONF

,INF=*SYMM_CONF / *DEV_CONF / *REMOTE_COPY / *MULTI_MIRROR /

<var: enum-of _inf_s:1>

,SELECT=*STD / *CONTROLLER / *SUBSYSTEM / *RC_PAIR / *MM_PAIR / *RC_MM_PAIR /

*PHYS_DISK / <var: enum-of _select_s:1>

,UNITTYPE=*CONTR_UNIT / *UNIT / *VOLUME / *PUBSET / *INT_SYMM_NO / *ALL /

<var: enum-of _unittype_s:1>

,REM_CTL=*ANY / <var: char:4>

,ATTR_DEV=*STD / *ALL / *ANY / *ATTACHED / *DETACHED /

<var: enum-of _attr_device_s:1>

,REM_CONFIG=*NO / *YES / <var: enum-of: _rem_config_s:1>

,ATTR_TYPE=*ANY / <var: char:8>

,ATTR_STATE=*ANY / *NO_ACCESS / *READY / *NOT_READY / *DISABLE / *READ_ONLY /

<var: enum-of _attr_state_s:1>

,ATTR_RAID=*ANY / *YES / *RAID1 / *RAIDS / *NO_RAID / <var: enum-of _attr_raid_s:1>

,ATTR_RC_USE=*ANY / *YES / *SOURCE / *TARGET / *NO / <var: enum-of _attr_rc_use_s:1>

,ATTR_MM_USE=*ANY / *YES / *NORMAL / *ADD_MIRROR / *NO /

<var: enum-of _attr_mm_use_s:1>

,ATTR_SYNCH=*ANY / *YES / *NO / <var: enum-of _attr_synchronized_s:1>

,ATTR_RC_STA=*ANY / *ACTIVE / *ERROR / *IN_HOLD /

<var: enum-of _attr_rdf_state_s:1>

,ATTR_TARG_ACC=*ANY / *NONE / *BY_SOURCE / *DIRECT /

<var: enum-of _attr_target_acc_s:1>

U41000-J-Z125-4-76 223

Program interface The NDEINF assembly language macro

The metasyntax is described in detail in chapter “Use of macros” in the manual “Executive Macros” [9]. The types of data are described as follows:

Data types of the operand values

Data types of the variables

NDEINF

(Cont.),ATTR_LINK_STA=*ANY / *AVAIL / *NOT_AVAIL / <var: enum-of _attr_link_state_s:1>

,ATTR_COPY_MODE=*ANY / *SYNCH / *S_SYNCH / *AD_COPY /

<var: enum-of _attr_rdf_mode_s:1>

,ATTR_ON_ERR=*ANY / *HOLD / *CONT / <var: enum-of _attr_on_error_s:1>

,ATTR_MM_STA=*ANY / *ESTAED / *ESTANG / *SPLIT / *SPLING / *RECONG / *UNUSED /

<var: enum-of _attr_mmf_state_s:1>

,MM_SEL=*STD / *TARGET / <var: enum-of _mmf_select_s:1>

,MM_INF=*CURRENT / *ALL / <var: enum-of _mmf_inf_s:1>

,UPD_TABLE=*YES/*NO

Data type Character set Remarks

var: Precedes specification of a variable. The colon is followed by the type of the variable (see table below).

<var: var-type>

c-string_without_quotes EBCDIC character Must not be quoted

Data type Description Definition in program

char: n The variable is a string of n characters. If the length is not specified, n=1 applies.

CLn

enum-of E: n The variable is the enumeration E, which takes up n bytes. If the length is not specified, n=1 applies (n ≤ 4).

XLn

(part 2 of 2)

Macro Operands

224 U41000-J-Z125-4-76


Operands

MF =For a general description of the MF operand, the associated operand values and the subsequent operands (PREFIX, MACID and PARAM), see the manual entitled “Executive Macros” [9]. The valid MF values are specified there at the beginning of the macro description and can be seen in the format of the call.

In the C form, D form and M form of the macro call, a prefix (PREFIX) can be specified, and in the C form or M form it is possible to specify a macid (MACID) as well. Only the operands PREFIX, MACID, VERSION, XPAND and EQUATES are allowed in the D form.

XPAND =Specifies whether a DSECT is to be created for the NDEINF parameter list or for the description of the output layouts of multi-mirror pairs, remote copy pairs, the device configuration or the Symmetrix configuration. This can only be specified in association with MF=D or MF=C.

PARAMA DSECT is created for the NDEINF parameter list. The address of the output area is provided to the caller in the NDEIOPTR field.

MULTI_MIRRORA DSECT is created with the output layout for multi-mirror pairs, which are indicated by the operands MMF_INF=*CURRENT.

X_MULTI_MIRRORA DSECT with an output layout for the Multi-mirror pairs is produced. This is indicated by the operand MMF_INF=*ALL.

REMOTE_COPYA DSECT is created with the output layout for remote copy pairs.

DEV_CONFA DSECT is created with the output layout for the Symmetrix device configuration.

SYMM_CONFA DSECT is created with the output layout for the Symmetrix configuration.

U41000-J-Z125-4-76 225


INF =Specifies the type of the information to be output.

*SYMM_CONFInformation on the Symmetrix configuration is output. The UNITTYPE operand must also be specified. Only UNITTYPE=*CONTR_UNIT or UNITTYPE=*ALL is permissible.

*DEV_CONFInformation on the Symmetrix device configuration is output. The SELECT operand is mandatory. The UNITTYPE operand must also be specified. All operand values except UNITTYPE=*ALL are permissible.

*REMOTE_COPYInformation on the status of remote copy pairs is output. The UNITTYPE operand must also be specified. All operand values except UNITTYPE=*ALL are permissible.

*MULTI_MIRRORInformation on the status of multi-mirror pairs is output. The UNITTYPE operand must also be specified. All operand values except UNITTYPE=*ALL are permissible.

<var: enum-of _inf_s:1>Name of the field with the equate for the operand values of INF=.... Can only be specified in conjunction with MF=M.

SELECT =The information volume can be selected according to the device name. Can only be specified in conjunction with INF=*DEV_CONF.

*STDData records are only output for the specified device names.

*CONTROLLERData records are output for all the devices of the controllers, selected by means of the device names.

*SUBSYSTEMData records are output for all the devices of the Symmetrix systems, selected by means of the device names.

*RC_PAIRData records are output for all the devices and any remote copy pairs that might be allocated to them, selected by means of the device names. UNITTYPE=*ALL and UNITTYPE=*CONTR_UNIT must not be specified.

226 U41000-J-Z125-4-76


*MM_PAIRData records are output for all the devices and any multi-mirror pairs that might be allocated to them, selected by means of the device names. UNITTYPE=*ALL and UNITTYPE=*CONTR_UNIT must not be specified.

*RC_MM_PAIRData records are output for all the devices and any remote copy and multi-mirror pairs that might be allocated to them, selected by means of the device names. UNITTYPE=*ALL and UNITTYPE=*CONTR_UNIT must not be specified.

*PHYS_DISKData records are output for all devices and for all other logical devices located on the same physical device of a Symmetrix controller. Output does not consider any additional internal mirrored disks that might be located on the same physical device.UNITTYPE=*CONTR_UNIT must not be specified.

<var: enum-of _select_s:1>Name of the field with the equate for the operand values of SELECT=.... This may only be specified in conjunction with MF=M.

UNITTYPE =Specifies the type of the specified device names. The parameter list permits the input of a list of up to 24 device names. These values must be entered directly in the parameter list. The length of a device name depends on the UNITTYPE operand and is 6 bytes each for VSNs and 4 bytes each for all others. It is essential that at least one device name is entered except for UNITTYPE=*ALL.

*CONTR_UNITThe specified device names are the mnemonic names of the controllers.

*UNITThe specified device names are the mnemonic names of the logical units.

*VOLUMEThe specified device names are the archive numbers (VSNs) of the logical units.

*PUBSETThe specified device names are the catalog IDs of the pubsets.

U41000-J-Z125-4-76 227


*INT_SYMM_NOThe specified device number is the unique Symmetrix serial number. Unless specified in connection with INF=*SYMM_CONF it must be specified in combination with the logical volume number of the Symmetrix.

*ALLThe information is output for all known Symmetrix systems. This can only be specified in conjunction with INF=*SYMM_CONF.

<var: enum-of _unittype_s:1>Name of the field with the equate of the operand values of UNITTYPE=.... This may only be specified in conjunction with MF=M.

REM_CTL =The mnemonic name of the remote controller. This can only be specified in conjunction with INF=*REMOTE_COPY and UNITTYPE=*CONTR-UNIT.

*ANYAll mnemonic names of the remote controller for remote copying

<var: char:4>Name of the field with the mnemonic name of the remote controller for remote copying. This can only be specified in conjunction with MF=M.

ATTR_DEV =The units are selected on the basis of their BS2000/OSD status.This can only be specified in conjunction with INF=*DEV_CONF.

*STDAll units are output in accordance with the global setting for the subsystem.

*ALLAll units that are defined in BS2000/OSD are output.

*ANYAll units are output, regardless of whether or not they are defined in BS2000/OSD.

*ATTACHEDOnly units that are attached to BS2000/OSD are output.

*DETACHEDOnly detached units are output.

228 U41000-J-Z125-4-76


<var: enum-of _attr_device_s:1>Name of the field with the equate of the operand values of ATTR_DEV=.... This can only be specified in conjunction with MF=M.

REM_CONFIG =Selects the Symmetrix configurations. This specification is only permitted in combination with INF=*SYMM_CONF.

*NOOnly those Symmetrix subsystems, which can be accessed by the host and via the SRDF link are shown.

*YESSymmetrix subsystems, which can be accessed by the host and via the SRDF link are shown.

<var: enum-of: _rem_config_s:1>Name of the field with the equate for the operand values of REM_CONFIG=.... This specification is only permitted in combination with MF=M.

ATTR_TYPE =Selects the units on the basis of their emulated device type. This can only be specified in conjunction with INF=*DEV_CONF.

*ANYAll devices are output, regardless of their emulated device type.

<var: char: 8>Name of the field with the operand value of ATTR_TYPE=.... This can only be specified in conjunction with MF=M.

ATTR_STATE =Selects the units on the basis of their status from the Symmetrix viewpoint.This can only be specified in conjunction with INF=*DEV_CONF.

*ANYAll devices are output, regardless of their from the Symmetrix viewpoint.

*NO-ACCESSOnly units with the status *NO-ACCESS are output.

*READYOnly units with the status *READY are output.

*NOT-READYOnly units with the status *NOT-READY are output.

U41000-J-Z125-4-76 229


*DISABLEOnly units with the status *DISABLE are output.

*READ-ONLYOnly units with the status *READ-ONLY are output.

<var: enum-of _attr_state_s:1>Name of the field with the equate of the operand values of ATTR_STATE=.... This can only be specified in conjunction with MF=M.

ATTR_RAID =Selects the units on the basis of their RAID protection. This can only be specified in conjunction with INF=*DEV_CONF.

*ANYAll devices are output, regardless of their RAID protection.

*YESAll devices with RAID protection are output.

*RAID1All devices with RAID protection according to RAID1 are output.

*RAIDSAll devices with RAID protection according to RAIDS are output.

*NO_RAIDAll devices with no RAID protection are output.

<var: enum-of _attr_raid_s:1>Name of the field with the equate of the operand values of ATTR_RAID=.... This can only be specified in conjunction with MF=M.

ATTR_RC_USE =Selects the units on the basis of their remote copy use. This can only be specified in conjunction with INF=*DEV_CONF.

*ANYAll devices are output, regardless of their remote copy use.

*YESAll remote copy devices (source units and target units) are output.

*SOURCEAll source units are output.

*TARGETAll target units are output.

230 U41000-J-Z125-4-76


*NOAll devices without remote copy use are output.

<var: enum-of _attr_rc_use_s:1>Name of the field with the equate of the operand values of ATTR_RC_USE=.... This can only be specified in conjunction with MF=M.

ATTR_MM_USE =Selects the units on the basis of their multi-mirror use. This can only be specified in conjunction with INF=*DEV_CONF.

*ANYAll devices are output, regardless of their multi-mirror use.

*YESAll multi-mirror devices (normal units and additional mirror units) are output.

*NORMALAll normal units are output.

*ADD-MIRRORAll additional mirror units are output.

*NOAll devices without multi-mirror use are output.

<var: enum-of _attr_mm_use_s:1>Name of the field with the equate of the operand values of ATTR_MM_USE=.... This can only be specified in conjunction with MF=M.

ATTR_SYNCH =Selects the units on the basis of their synchronization. This can only be specified in conjunction with INF=*REMOTE_COPY or INF=*MULTI_MIRROR.

*ANYAll devices are output, regardless of their synchronization.

*YESOnly synchronized remote copy pairs or multi-mirror pairs are output.

*NOOnly non-synchronized remote copy pairs or multi-mirror pairs are output.

<var: enum-of _attr_synchronized_s:1>Name of the field with the equate of the operand values of ATTR_SYNCH=.... This can only be specified in conjunction with MF=M.

U41000-J-Z125-4-76 231


ATTR_RC_STA =Selects the units on the basis of their remote copy status. This can only be specified in conjunction with INF=*REMOTE_COPY.

*ANYAll devices are output, regardless of their remote copy status.

*ACTIVEOnly remote copy pairs with the status *ACTIVE are output.

*ERROROnly remote copy pairs with the status *ERROR are output.

*IN_HOLDOnly remote copy pairs with the status *IN_HOLD are output.

<var: enum-of _attr_rdf_state_s:1>Name of the field with the equate of the operand values of ATTR_RC_STA=.... This can only be specified in conjunction with MF=M.

ATTR_TARG_ACC =Selects the units on the basis of their set access path. This can only be specified in conjunction with INF=*REMOTE_COPY.

*ANYAll devices are output, regardless of their set access path.

*NONEOnly remote copy pairs with no access path are output.

*BY_SOURCEOnly remote copy pairs with an access path set to *BY_SOURCE are output.

*DIRECTOnly remote copy pairs with an access path set to *DIRECT are output.

<var: enum-of _attr_target_acc_s:1>Name of the field with the equate of the operand values of ATTR_TARG_ACC=.... This can only be specified in conjunction with MF=M.

232 U41000-J-Z125-4-76


ATTR_LINK_STA =Selects the units on the basis of the availability of their remote link. This can only be specified in conjunction with INF=*REMOTE_COPY.

*ANYAll devices are output, regardless of the availability of their remote link.

*AVAILOnly remote copy pairs with an available remote link are output.

*NOT_AVAILOnly remote copy pairs with no available remote link are output.

<var: enum-of _attr_link_state_s:1>Name of the field with the equate of the operand values of ATTR_LINK_STA=.... This can only be specified in conjunction with MF=M.

ATTR_COPY_MODE =Selects the units on the basis of the set copy mode. This can only be specified in conjunction with INF=*REMOTE_COPY.

*ANYAll devices are output, regardless of the copy mode set.

*SYNCHOnly remote copy pairs with the copy mode *SYNCHRONOUS are output.

*S_SYNCHOnly remote copy pairs with the copy mode *SEMI-SYNCHRONOUS are output.

*AD_COPYOnly remote copy pairs with the copy mode *ADAPTIVE-COPY are output.

<var: enum-of _attr_rdf_mode_s:1>Name of the field with the equate of the operand values of ATTR_COPY_MODE=.... This can only be specified in conjunction with MF=M.

U41000-J-Z125-4-76 233


ATTR_ON_ERR =Selects the units on the basis of remote copy parameter ON-ERROR. This can only be specified in conjunction with INF=*REMOTE_COPY.

*ANYAll devices are output, regardless of the setting of the remote copy parameter ON-ERROR.

*HOLDOnly remote copy pairs with the remote copy parameter ON-ERROR=*HOLD are output.

*CONTOnly remote copy pairs with the remote copy parameter ON-ERROR=*CONTINUE are output.

<var: enum-of _attr_on_error_s:1>Name of the field with the equate of the operand values of ATTR_ON_ERR=.... This can only be specified in conjunction with MF=M.

ATTR_MM_STA =Selects the units on the basis of their multi-mirror status. This can only be specified in conjunction with INF=*MULTI_MIRROR.

*ANYAll devices are output, regardless of their multi-mirror status.

*ESTAEDOnly multi-mirror pairs with the status *ESTABLISHED are output.

*ESTANGOnly multi-mirror pairs with the status *ESTABLISHING are output.

*SPLITOnly multi-mirror pairs with the status *SPLIT are output.

*SPLINGOnly multi-mirror pairs with the status *SPLITTING are output.

*RECONGOnly multi-mirror pairs with the status *RECONSTRUCTING are output.

*UNUSEDOnly multi-mirror pairs with the status *UNUSED are output.

<var: enum-of _attr_mmf_state_s:1>Name of the field with the equate of the operand values of ATTR_MM_STA=.... This can only be specified in conjunction with MF=M.

234 U41000-J-Z125-4-76


MM_SEL =Selects the units on the basis of their remote copy use.This can only be specified in conjunction with INF=*MULTI_MIRROR.

*STDAll devices are output, regardless of their remote copy use.

*TARGETOnly SRDF source units are considered.The multi-mirror pairs for the target units allocated to the source units are output.

<var: enum-of _mmf_select_s:1>Name of the field with the equate of the operand values of MM_SEL=.... This can only be specified in conjunction with MF=M.

MM_INF =Selects the information about the additional mirror units that are allocated to the normal unit.

*CURRENTShows the additional mirror units currently attached.

*ALLShows the additional mirror units attached until now.

<var: enum-of _mmf_inf_s:1>Name of the field with the equate for the operand values of MM_INF=.... This specification is only permitted in combination with MF=M.

UPD_TABLE =Specifies whether the internal data is to be updated before the macro is executed.

*YESThe internal data is updated before the macro is executed.

*NOThe internal data is not updated before the macro is executed. This increases the performance when the function is executed.

U41000-J-Z125-4-76 235


Macro return codes

(SC2) SC1 Maincode MeaningX’00’ X’00’ X’0000’ Function successfully executedX’02’ X’00’ X’0001’ Function partially executed X’00’ X’01’ X’0002’ Invalid value for INFX’00’ X’01’ X’0003’ Invalid value for UNITTYPEX’00’ X’01’ X’0004’ Invalid combination of INF and UNITTYPEX’00’ X’40’ X’0005’ No information availableX’00’ X’82’ X’0006’ No memory availableX’00’ X’40’ X’0007’ Specified unit is not of the type SymmetrixX’00’ X’40’ X’0008’ Microcode status is not supported X’00’ X’40’ X’0009’ Remote copying is not supported for the specified units X’00’ X’40’ X’000A’ Multi-mirroring is not supported for the specified units X’00’ X’40’ X’000B’ Device not foundX’00’ X’40’ X’000C’ Device not assignedX’00’ X’40’ X’000D’ Controller not foundX’00’ X’40’ X’000E’ Volume not onlineX’00’ X’40’ X’000F’ Pubset not onlineX’00’ X’40’ X’0010’ Input/output errorX’00’ X’40’ X’0011’ No device assigned for input/output X’00’ X’40’ X’0012’ Remote controller not found X’00’ X’40’ X’0013’ Lock for accessing the internal administration data not received X’00’ X’40’ X’0014’ User does not have the privilege for receiving information X’00’ X’40’ X’0015’ SM pubsets not supported in versions < BS2000/OSD-BC V4.0 X’00’ X’40’ X’0016’ No information for exported SM pubsetsX’02’ X’00’ X’0017’ Remote control is identical with local controlX’00’ X’40’ X’0018’ No remote copy functionX’00’ X’40’ X’0019’ Remote copy target unit not foundX’00’ X’40’ X’001A’ Target unit has no multi-mirror functionalityX’00’ X’40’ X’0021’ Logical volume not foundX’00’ X’40’ X’0022’ Symmetrix serial number not foundX’00’ X’40’ X’0023’ Symmetrix serial number not unique X’00’ X’40’ X’0024’ Remote input/output is not possibleX’02’ X’00’ X’0025’ Symmetrix configuration with more than 32 directorsX’02’ X’00’ X’0026’ Function not supported by the microcode status X’02’ X’00’ X’0027’ Symmetrix configuration with more than 64 directorsX’00’ X’20’ X’00FF’ Internal error

236 U41000-J-Z125-4-76


Example 1

Query of the serial numbers of the SYMMETRIX disk subsystems with the emulated ZM and S6 device controllers.

SYMMINF START SYMMINF AMODE ANYSYMMINF RMODE ANY BASR 10,0 USING *,10* REQM 1 Request memory for parameter list LR 4,1 USING NDEIMDL,4 DSECT for parameter list MVC NDEIMDL(NDEI#),PARAM Transfer parameter list ** Modify parameter list * NDEINF MF=M,INF=*SYMM_CONF,UNITTYPE=*CONTR_UNIT** Enter individual controller units in the parameter list * MVC NDEIVCTL(4),=C‘S6 ’ MVC NDEIVCTL+4(4),=C‘ZM ’** Call function * NDEINF MF=E,PARAM=NDEIMDL ** Evaluate return code* CLI NDEISR1,X‘00‘ BNE FEHLER** Evaluate output area * L 5,NDEIOPTR Load address of the output area LTR 5,5 BZ FEHLER Not an output area* (analyze return code) USING NDEISMDL,5 DSECT for the output area* L 6,NDEIOUT# Load number of outputs L 7,NDEI1LEN Load length of an output*NEXT EQU ** MVC SERIAL_NO(12),NDEISSER

U41000-J-Z125-4-76 237


* Evaluate data:* e.g. create output, etc.* AR 5,7 Position on next output BCT 6,NEXT Process next output*END EQU *** Release memory for output area ** Division of register 8 / 4096 specifies the number of 4K pages L 8,NDEIOLEN Total length of memory SRA 8,12 Shift 12 places to the right * (multiple of 4K)* Division of register 5 / 4096 specifies the page number L 5,NDEIOPTR Load address of the output area SRA 5,12 Shift 12 places to the right* RELM (8),(5)* TERM Terminate program * ERROREQU *** Error recovery (e.g. output return code)* TERM MODE=ABNORMAL,UNIT=STEP** Memory areas*SERIAL_NO DS CL12** Parameter list* PARAM NDEINF MF=L** DSECT for parameter list* NDEINF MF=D,XPAND=PARAM** DSECT for SYMMETRIX configuration* NDEINF MF=D,XPAND=SYMM_CONF* END

238 U41000-J-Z125-4-76


Execution log

(IN) DEL-SYS-FILE *OMF(IN) START-ASSEMBH(OUT) % BLS0500 PROGRAM ’ASSEMBH‘, VERSION ’1.2B00‘ OF ’1998-04-24‘ LOADED(OUT) % BLS0552 COPYRIGHT (C) FUJITSU SIEMENS COMPUTERS GMBH 1990. ALL

RIGHTS RESERVED(OUT) % ASS6010 V 1.2B01 OF BS2000 ASSTRAN READY(IN) //COMPILE SOURCE=NDEINF.BSP,MACRO-LIBRARY=(SYSLIB.SHC-OSD.020,-( ) // SYSLIB.BS2CP.130),LISTING=PAR(OUTPUT=LST.ASSEMBH),-( ) // TEST-SUPPORT=YES(OUT) % ASS6011 ASSEMBLY TIME: 1982 MSEC(OUT) % ASS6018 0 FLAGS, 0 PRIVILEGED FLAGS, 0 MNOTES(OUT) % ASS6019 HIGHEST ERROR-WEIGHT: NO ERRORS(OUT) % ASS6006 LISTING GENERATOR TIME: 834 MSEC(IN) END(OUT) % ASS6012 END OF ASSTRAN

(IN) LOAD-PROG *MOD(*OMF),TEST=AID(OUT) % BLS0517 MODULE ‚SYMMINF‘ LOADED(IN) %IN NEXT;%R(OUT) STOPPED AT LABEL: NEXT, SRC_REF: 65, SOURCE: SYMMINF, ( ) PROC: SYMMINF ——————————————————————————————————————————————————— (1) (IN) %D %5(OUT) CURRENT PC: 00000052 CSECT: SYMMINF ***************************************(NL) %5 = 00002000 ——————————————————————————————————————————————————— (2) (IN) %D %6(OUT) %6 = 00000002 ——————————————————————————————————————————————————— (3) (IN) %D %7(OUT) %7 = 000001F0 ——————————————————————————————————————————————————— (4) (IN) %D %5->NDEISSER(OUT) SRC_REF: 65 SOURCE: SYMMINF PROC: SYMMINF ********************************(NL) NDEISMDL.NDEISSER = |000282500505| —————————————————————————————— (5) (IN) %R(OUT) STOPPED AT LABEL: NEXT, SRC_REF: 65, SOURCE: SYMMINF, ( ) PROC: SYMMINF ——————————————————————————————————————————————————— (6) (IN) %d %5(OUT) CURRENT PC: 00000052 CSECT: SYMMINF ***************************************(NL) %5 = 000021F0 ——————————————————————————————————————————————————— (7) (IN) %d %6(OUT) %6 = 00000001 ——————————————————————————————————————————————————— (8) (IN) %d %7(OUT) %7 = 000001F0 ——————————————————————————————————————————————————— (9)

U41000-J-Z125-4-76 239


(IN) %d %5->NDEISSER(OUT) SRC_REF: 65 SOURCE: SYMMINF PROC: SYMMINF ********************************(NL) NDEISMDL.NDEISSER = |000282600434| —————————————————————————————— (10) (IN) %IN ENDE;%R

(OUT) STOPPED AT LABEL: ENDE, SRC_REF: 75, SOURCE: SYMMINF, ( ) PROC: SYMMINF ——————————————————————————————————————————————————— (11) (IN) %T 9 %INSTR(OUT) SYMMINF+5E L R8,AC(R0,R4) 2 R8=00001000 A2=000010AC O2=00001000(OUT) SYMMINF+62 SRA R8,C(R0) 2 R8=00000001 SR=12 —————————————— (12) (OUT) SYMMINF+66 L R5,A4(R0,R4) 2 R5=00002000 A2=000010A4 O2=00002000(OUT) SYMMINF+6A SRA R5,C(R0) 2 R5=00000002 SR=12 —————————————— (13) (OUT) SYMMINF+6E BCR B‘0000‘,R0 2 NOP R0=00000000 (OUT) SYMMINF+70 BAS R1,7A(R0,R10) 2 R1=00000074(NL) A2=0000007C=SYMMINF+7C (OUT) SYMMINF+7C SVC 74 2 FCT=RELM IR1=00000074 (NL) R1=00000074 R15=0000000C (NL) PAR=01000008 01000005 ——————————————————————————————————————————— (14) (OUT) SYMMINF+7E LA R1,86(R0,R10) 2 R1=00000088(NL) A2=00000088=SYMMINF+88 (OUT) SYMMINF+82 BC B‘1111‘,96(R0,R10) 2 * M=0+1+2+3 (NL) A1=00000098=SYMMINF+98 (IN) %R

(1) NEXT label after successful execution of the NDEINF macro.Beginning of loop for interpreting the output area (first pass).

(2) Register 5 contains the pointer to the beginning of the output area, i.e. the contents of the NDEIOPTR field of the parameter list.

(3) Register 6 contains the number of output records, i.e. the contents of the NDEIOUT# field of the parameter list.

(4) Register 7 contains the length of the output record, i.e. the contents of the NDEI1LEN field of the parameter list.

(5) The NDEISMDL.NDEISSER field of the 1st output record contains the first serial number.

(6) NEXT label at the beginning of the 2nd loop pass.

(7) Register 5 contains the pointer to the 2nd output record.

(8) Register 6 contains the number of output records still to be processed.

(9) Register 7 contains the length of an output record, i.e. the contents of the NDEI1LEN field of the parameter list.

240 U41000-J-Z125-4-76


(10) The NDEISMDL.NDEISSER field of the 2nd output record contains the next serial number.

(11) ENDE label: Processing of the output records is completed, the memory must be released.

(12) The number of 4K pages is calculated in register 8.

(13) The page number of the 4K page is calculated in register 5.

(14) Memory release with the RELM macro.

Example 2

Query of the device MNs for all devices and their allocated remote copy pairs for the pubset SYMM.The pubset SYMM consists of the source units 5095, 5096, 5097. The target units allocated for the remote copy are 512F, 5130, 5131.

SYDVINF START SYDVINF AMODE ANYSYDVINF RMODE ANY BASR 10,0 USING *,10* REQM 1 Request memory for parameter list LR 4,1 USING NDEIMDL,4 DSECT for parameter list* MVC NDEIMDL(NDEI#),PARAM Transfer parameter list** Modify parameter list * NDEINF MF=M,INF=*DEV_CONF,UNITTYPE=*PUBSET,SELECT=*RC_PAIR** Enter catalog ID for pubset in parameter list* MVC NDEIVPVS(4),=C‘SYMM‘** Call function* NDEINF MF=E,PARAM=NDEIMDL ** Evaluate return code * CLI NDEISR1,X‘00‘ BNE FEHLER

U41000-J-Z125-4-76 241


** Evaluate output area* L 5,NDEIOPTR Load address of output area LTR 5,5 BZ FEHLER Not an output area* (analyze return code) USING NDEIDMDL,5 DSECT for the output area* L 6,NDEIOUT# Load number of outputs L 7,NDEI1LEN Load length of an output area*NEXT EQU ** MVC DEV_MN(4),NDEIDUNT MN of the device* * Evaluate data:* e.g. create output, etc.* AR 5,7 Position on next output BCT 6,NEXT Process next output *END EQU *** Release memory for output area** Division of register 8 / 4096 specifies the number of 4K pages L 8,NDEIOLEN Total length of memory SRA 8,12 Shift 12 places to the right* (multiple of 4K)* Division of register 5 / 4096 specifies the page number L 5,NDEIOPTR Load address of the output area SRA 5,12 Shift 12 places to the right* RELM (8),(5)* TERM Terminate program* ERROR EQU *** Error recovery (e.g. output return code)* TERM MODE=ABNORMAL,UNIT=STEP** Memory areas*DEV_MN DS CL4*

242 U41000-J-Z125-4-76


* Parameter list* PARAM NDEINF MF=L** DSECT for parameter list* NDEINF MF=D,XPAND=PARAM** DSECT for device configuration* NDEINF MF=D,XPAND=DEV_CONF* END

Execution log

(IN) DEL-SYS-FILE *OMF(IN) START-ASSEMBH(OUT) % BLS0500 PROGRAM ’ASSEMBH‘, VERSION ’1.2B00‘ OF ’1998-04-24‘ LOADED(OUT) % BLS0552 COPYRIGHT (C) FUJITSU SIEMENS COMPUTERS GMBH 1990. ALL

RIGHTS RESERVED(OUT) % ASS6010 V 1.2B01 OF BS2000 ASSTRAN READY(IN) //COMPILE SOURCE=NDEINF.BSP2.SRC,-( ) // MACRO-LIBRARY=(SYSLIB.SHC-OSD.020,SYSLIB.BS2CP.130),-( ) // LISTING=PAR(OUTPUT=LST.ASSEMBH),TEST-SUPPORT=YES(OUT) % ASS6011 ASSEMBLY TIME: 656 MSEC(OUT) % ASS6018 0 FLAGS, 0 PRIVILEGED FLAGS, 0 MNOTES(OUT) % ASS6019 HIGHEST ERROR-WEIGHT: NO ERRORS(OUT) % ASS6006 LISTING GENERATOR TIME: 248 MSEC(IN) END(OUT) % ASS6012 END OF ASSTRAN

(IN) LOAD-PROG *MOD(*OMF),TEST=AID(OUT) % BLS0517 MODULE ’SYDVINF‘ LOADED(IN) %IN NEXT;%R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (1) (IN) %D %5(OUT) CURRENT PC: 00000052 CSECT: SYDVINF (NL) %5 = 00003000 ——————————————————————————————————————————————————— (2) (IN) %D %6(OUT) %6 = 00000006 ——————————————————————————————————————————————————— (3) (IN) %D %7(OUT) %7 = 00000058 ——————————————————————————————————————————————————— (4) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |5095| —————————————————————————————————————— (5)

U41000-J-Z125-4-76 243


(IN) %R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (6) (IN) %D %5(OUT) %5 = 00003058 ——————————————————————————————————————————————————— (7) (IN) %D %6(OUT) %6 = 00000005 ——————————————————————————————————————————————————— (8) (IN) %D %7(OUT) %7 = 00000058 ——————————————————————————————————————————————————— (9) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |512F| —————————————————————————————————————— (10) (IN) %R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (11) (IN) %D %6(OUT) CURRENT PC: 00000052 CSECT: SYDVINF ******************************(NL) %6 = 00000004 ——————————————————————————————————————————————————— (12) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |5096| —————————————————————————————————————— (13) (IN) %R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (14) (IN) %D %6(OUT) CURRENT PC: 00000052 CSECT: SYDVINF ******************************(NL) %6 = 00000003 ——————————————————————————————————————————————————— (15) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |5130| —————————————————————————————————————— (16) (IN) %R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (17) (IN) %D %6(OUT) CURRENT PC: 00000052 CSECT: SYDVINF ******************************(NL) %6 = 00000002 ——————————————————————————————————————————————————— (18) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |5097| —————————————————————————————————————— (19) (IN) %R(OUT) STOPPED AT LABEL: NEXT , SRC_REF: 65 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (20) (IN) %D %6(OUT) CURRENT PC: 00000052 CSECT: SYDVINF ******************************(NL) %6 = 00000001 ——————————————————————————————————————————————————— (21) (IN) %D %5->NDEIDUNT(OUT) SRC_REF: 65 SOURCE: SYDVINF PROC: SYDVINF ************************(NL) NDEIDMDL.NDEIDUNT = |5131| —————————————————————————————————————— (22)

244 U41000-J-Z125-4-76


(IN) %IN ENDE;%R(OUT) STOPPED AT LABEL: ENDE , SRC_REF: 75 SOURCE: SYDVINF ,(OUT) PROC: SYDVINF —————————————————————————————————————————————————— (23) (IN) %T 9 %INSTR(OUT) SYDVINF+5E L R8,AC(R0,R4) 2 R8=00001000 A2=000010AC (NL) O2=00001000(OUT) SYDVINF+62 SRA R8,C(R0) 2 R8=00000001 SR=12 ——————— (24) (OUT) SYDVINF+66 L R5,A4(R0,R4) 2 R5=00003000 A2=000010A4 (NL) O2=00003000(OUT) SYDVINF+6A SRA R5,C(R0) 2 R5=00000003 SR=12 ——————— (25) (OUT) SYDVINF+6E BCR B‘0000‘,R0 2 NOP R0=00000000 (OUT) SYDVINF+70 BAS R1,7A(R0,R10) 2 R1=00000074 (NL) A2=0000007C=SYDVINF+7C (OUT) SYDVINF+7C SVC 74 2 FCT=RELM IR1=00000074 (NL) R1=00000074 R15=00000000 (NL) PAR=01000008 01000005 ——————— (26) (OUT) SYDVINF+7E LA R1,86(R0,R10) 2 R1=00000088 (NL) A2=00000088=SYDVINF+88(OUT) SYDVINF+82 BC B‘1111‘,96(R0,R10) 2 * M=0+1+2+3 (NL) A1=00000098=SYDVINF+98 (IN) %R

(1) NEXT label after successful execution of the NDEINF macro.Beginning of loop for interpreting the output area (first pass).

(2) Register 5 contains the pointer to the beginning of the output area, i.e. the contents of the NDEIOPTR field of the parameter list.

(3) Register 6 contains the number of output records, i.e. the contents of the NDEIOUT# field of the parameter list.

(4) Register 7 contains the length of the output record, i.e. the contents of the NDEI1LEN field of the parameter list.

(5) The NDEISMDL.NDEISSER field of the 1st output record contains the first device MN.

(6) NEXT label at the beginning of the 2nd loop pass.

(7) Register 5 contains the pointer to the 2nd output record.


(9) Register 7 contains the length of an output record, i.e. the contents of the NDEI1LEN field of the parameter list.

(10) The NDEISMDL.NDEIDUNT field of the 2nd output record contains the second device MN.

(11) NEXT label at the beginning of the 3rd loop pass.

U41000-J-Z125-4-76 245



(13) The NDEISMDL.NDEIDUNT field of the 3rd output record contains the 3rd device mnemonic.

(14) NEXT label at the beginning of the 4th loop pass.


(16) The NDEISMDL.NDEIDUNT field of the 4th output record contains the 4th device MN.







(23) ENDE label: processing of the output records is completed, the memory must be released.

(24) The number of 4K pages is calculated in register 8.

(25) The page number of the 4K page is calculated in register 5.

(26) Memory release with the RELM macro.

246 U41000-J-Z125-4-76


Parameter list

NDEINF MF=D,XPAND=PARAM 1 MFTST MF=D,PREFIX=N,MACID=DEI,ALIGN=F, C 1 DMACID=DEI,SUPPORT=(E,D,C,M,L),DNAME=DEIMDL 2 NDEIMDL DSECT , 2 *,##### PREFIX=N, MACID=DEI ##### 1 * partial success 1 NDEIPSUC EQU 2 partial success getting 1 * information 1 * 1 * NDEINF parameter list 1 NDEIFHDR FHDR MF=(C,NDEI),EQUATES=NO FHDR 2 NDEIFHDR DS 0A 2 NDEIFHE DS 0XL8 0 GENERAL PARAMETER AREA HEADER 2 * 2 NDEIIFID DS 0A 0 INTERFACE IDENTIFIER 2 NDEIFCTU DS AL2 0 FUNCTION UNIT NUMBER 2 * BIT 15 HEADER FLAG BIT, 2 * MUST BE RESET UNTIL FURTHER NOTICE 2 * BIT 14-12 UNUSED, MUST BE RESET 2 * BIT 11-0 REAL FUNCTION UNIT NUMBER 2 NDEIFCT DS AL1 2 FUNCTION NUMBER 2 NDEIFCTV DS AL1 3 FUNCTION INTERFACE VERSION NUMBER 2 * 2 NDEIRET DS 0A 4 GENERAL RETURN CODE 2 NDEISRET DS 0AL2 4 SUB RETURN CODE 2 NDEISR2 DS AL1 4 SUB RETURN CODE 2 2 NDEISR1 DS AL1 5 SUB RETURN CODE 1 2 NDEIMRET DS 0AL2 6 MAIN RETURN CODE 2 NDEIMR2 DS AL1 6 MAIN RETURN CODE 2 2 NDEIMR1 DS AL1 7 MAIN RETURN CODE 1 2 NDEIFHL EQU 8 8 GENERAL OPERAND LIST HEADER LENGTH 2 * 1 * main return codes 1 NDEICOMPLETE_SUCCESS EQU 0 complete success 1 NDEIPARTIAL_SUCCESS EQU 1 partial success 1 NDEIINVALID_INF EQU 2 invalid inf value 1 NDEIINVALID_UNITTYPE EQU 3 invalid unittype value 1 NDEIINVALID_COMBINATION EQU 4 invalid combination of 1 * unittype and inf 1 NDEINO_INFORMATION EQU 5 no information exists 1 NDEINO_MEMORY EQU 6 no memory available 1 NDEINO_SYMMETRIX_UNIT EQU 7 specified unit is not of type 1 * Symmetrix 1 NDEIINVALID_MICROCODE EQU 8 microcode level not supported 1 NDEINO_REMOTE_COPY EQU 9 no remote copy facilities 1 * supported for specified

U41000-J-Z125-4-76 247


1 * units 1 NDEINO_MULTI_MIRROR EQU 10 no multi mirroring facilities 1 * supported for specified 1 * units 1 NDEIDEVICE_NOT_FOUND EQU 11 device not found 1 NDEIDEVICE_NOT_ATT EQU 12 device not attached 1 NDEICONTR_NOT_FOUND EQU 13 controller not found 1 NDEIVOLUME_NOT_ONLINE EQU 14 volume not online 1 NDEIPUBSET_NOT_ONLINE EQU 15 volume not online 1 NDEIIO_ERROR EQU 16 IO error 1 NDEINO_DEVICE_ATTACHED EQU 17 no device attached for IO 1 NDEIREMOTE_CONTR_NOT_FOUND EQU 18 remote controller not found 1 NDEINO_LOCK_OBTAINED EQU 19 no lock obtained during 1 * administration access 1 NDEICALLER_NOT_PRIVILEGED EQU 20 caller not privileged to get 1 * information 1 NDEIPUBSET_TYPE_NOT_SUPP EQU 21 SM pubsets not supported for 1 * < OSD V4.0 1 NDEIEXPORTED_SM_PUBSET EQU 22 no info for exported SM 1 * pubsets 1 NDEIREM_CONTR_IS_SAME EQU 23 remote contr is same as local 1 NDEINO_REM_COPY EQU 24 no remote copy 1 NDEISEL_TARGET_NOT_FOUND EQU 25 selected remote copy target 1 * not found 1 NDEINO_MMF_ON_TARGET EQU 26 remote copy target has no 1 * multi mirror function 1 NDEIINT_NO_NOT_FOUND EQU 27 internal device number not 1 * found 1 NDEIAMB_SERIAL_NO EQU 28 specified serial number is 1 * not unique 1 NDEINO_REMOTE_IOS_POSS EQU 29 no remote ios possible for 1 * remote update 1 NDEIMORE_THAN_32_DIRS EQU 30 configuration with more than 1 * 32 dirs 1 NDEINO_SUPPORT_BY_MICROCODE EQU 31 function is not supported by 1 * current microcode level 1 NDEINO_X_MMF_INFO EQU 32 no historical multi mirror 1 * info available 1 NDEIINTERNAL_ERROR EQU 255 internal error 1 * 1 NDEIIINF DS FL1 information 1 * Information 1 NDEIISYM EQU 1 SHOW-SYMM-CONF 1 NDEIIDEV EQU 2 SHOW-SYMM-DEV-CONF 1 NDEIIRDF EQU 3 SHOW-REMOTE-COPY 1 NDEIIMMF EQU 4 SHOW-MULTI-MIRRORING 1 * 1 NDEIIUTY DS FL1 input Unit type

248 U41000-J-Z125-4-76


1 * Input Unit 1 NDEIKCTL EQU 1 Controller MNs 1 NDEIKDVC EQU 2 Device MNs 1 NDEIKVSN EQU 3 Volume Serial # 1 NDEIKPVS EQU 4 Catalog ID 1 NDEIKIS# EQU 6 SYMMETRIX Serial # + Internal 1 * Device # 1 NDEIKALL EQU 255 All available 1 * 1 NDEIISEL DS FL1 select for INF=*DEV_CONF 1 * SELECT for INF=*DEV_CONF 1 NDEISSTD EQU 1 only records for input keys 1 NDEISCTL EQU 2 records for all devices on 1 * control units selected by 1 * input keys 1 NDEISSUB EQU 3 records for all devices on 1 * Symmetrix subsystems 1 * selected by input keys 1 NDEISRCP EQU 4 records for all remote copy 1 * devices by input keys 1 NDEISMMP EQU 5 records for all multi mirror 1 * devices by input keys 1 NDEISRMP EQU 6 records for all remote copy 1 * and multi mirror devices by 1 * input keys 1 NDEISPHD EQU 7 records for all logical 1 * devices on same physical 1 * disk 1 * 1 NDEIIORC DS 0XL1 IO Recovery Duration 1 NDEIRECD DS FL1 IO recovery duration class 1 * Recovery Duration 1 NDEISTDD EQU 0 standard 1 NDEINOLW EQU 1 few repetitions for logical 1 * errors, $DOER with NOOPA and 1 * PRIMITIV, and short 1 * io-timeout 1 NDEISNLW EQU 2 no repetitions for logical 1 * errors, $DOER with ONLY 1 * LOGGING and short io-timeout 1 * 1 ORG NDEIIORC 1 NDEIRECW DS X IO recovery duration integer 1 ORG NDEIIORC+1 1 NDEIIVAL DS 0XL144 Input Unit Values 1 NDEIVALL DS CL144 all units 1 ORG NDEIIVAL 1 NDEIVVSN DS 24CL6 Volume Serial #s

U41000-J-Z125-4-76 249


1 NDEIVVSN# EQU 24 1 ORG NDEIIVAL 1 NDEIVCTL DS 24CL4 Controller MNs 1 NDEIVCTL# EQU 24 1 ORG NDEIIVAL 1 NDEIVDVC DS 24CL4 Device MNs 1 NDEIVDVC# EQU 24 1 ORG NDEIIVAL 1 NDEIVPVS DS 24CL4 Catalog IDs 1 NDEIVPVS# EQU 24 1 ORG NDEIIVAL 1 NDEIVSYM DS 0XL16 Internal Symmetrix # 1 NDEISYS# DS CL12 symmetrix serial number 1 NDEISYD# DS H Symmetrix internal device 1 * number 1 NDEISRCD DS FL1 selected devices for remote 1 * copy 1 NDEIUNUY DS XL1 1 DS 0XL16 1 NDEIVSYM# EQU 1 1 ORG NDEIIVAL+144 1 NDEIRCTL DS CL4 MN of Remote Controller for 1 * remote_copy only, *ALL=' ' 1 NDEITCBP DS A NDETCB Pointer

1 NDEIOCLS DS X memory class of output area 1 NDEIUNU3 DS XL1 1 NDEISMSG DS CL7 summary command return code 1 * message 1 NDEIOINF DS XL3 element of unit list found 1 NDEIORCI DS XL3 element of unit list have RC 1 NDEIOMMI DS XL3 element of unit list have MM 1 NDEISVCF DS AL1 flags 1 NDEIAM24 EQU X'80' tu program in amode 24 1 NDEIAUN1 EQU X'7F' 1 NDEIUNU4 DS XL1 1 NDEISDV DS FL1 DEVICE operand of 1 * SHOW-SYMM-DEV-CONF, 1 * SHOW-REM-COPY-STA or 1 * SHOW-MULTI-MIRR cmd 1 * DEVICES operand of SHOW-SYMM-DEV-CONF command 1 NDEIDALL EQU 0 all found defined devices 1 NDEIDATC EQU 1 consider attached devices 1 * only

1 NDEIOPTR DS A pointer to output 1 NDEIOUT# DS F number of output records 1 NDEIOLEN DS F total length of output 1 NDEI1LEN DS F length of one output record

250 U41000-J-Z125-4-76


1 NDEIDDTC EQU 2 consider detached devices 1 * only 1 NDEIDANY EQU 3 consider all (defined + not 1 * defined) devices 1 NDEIDSTD EQU 4 consider devices regarding to 1 * global setting (all or any) 1 * 1 NDEISTY DS CL8 TYPE operand of 1 * SHOW-SYMM-DEV-CONF cmd 1 NDEISST DS FL1 STATE operand of 1 * SHOW-SYMM-DEV-CONF cmd 1 * STATE operand of SHOW-SYMM-DEV-CONF command 1 NDEISNOA EQU 0 consider devices with no 1 * access only 1 NDEISRDY EQU 1 consider ready devices only 1 NDEISNRY EQU 2 consider not ready devices 1 * only 1 NDEISROY EQU 3 consider read only devices 1 * only 1 NDEISDIS EQU 4 consider disabled devices 1 * only 1 NDEISTAN EQU 255 all found records 1 * 1 NDEISRA DS FL1 RAID operand of 1 * SHOW-SYMM-DEV-CONF cmd 1 * RAID-LEVEL operand of SHOW-SYMM-DEV-CONF command 1 NDEIRAIA EQU 0 all found records 1 NDEIRAIY EQU 1 all found RAID devices 1 NDEIRAI1 EQU 2 consider RAID1 devices only 1 NDEIRAIS EQU 3 consider RAIDS devices only 1 NDEIRAIN EQU 4 consider no RAID devices only 1 * 1 NDEISRC DS FL1 REMOTE-COPY-USE operand of 1 * SHOW-SYMM-DEV-CONF cmd 1 * REMOTE-COPY-USE operand of SHOW-SYMM-DEV-CONF command 1 NDEIRANY EQU 0 all found records 1 NDEIRALL EQU 1 consider all remote copy 1 * units 1 NDEIRSRC EQU 2 consider source units only 1 NDEIRTRG EQU 3 consider target units only 1 NDEIRCNO EQU 4 consider not remote copy 1 * units only 1 * 1 NDEISMM DS FL1 MULTI-MIRROR-USE operand of 1 * SHOW-SYMM-DEV-CONF cmd 1 * MULTI-MIRROR-USE operand of SHOW-SYMM-DEV-CONF command 1 NDEIMANY EQU 0 all found records 1 NDEIMALL EQU 1 consider all multi mirror

U41000-J-Z125-4-76 251


1 * units 1 NDEIMNUN EQU 2 consider normal units only 1 NDEIMADM EQU 3 consider add mirror units 1 * only 1 NDEIMMNO EQU 4 consider not multi mirror 1 * units only 1 * 1 NDEISSY DS FL1 SYNCHRONIZED operand of 1 * SHOW-REM-COPY-STA or 1 * SHOW-MULTI-MIRR cmd 1 * attribute remote copy or multi mirror pair synchronized 1 NDEIASYA EQU 0 pair synchronized any 1 NDEIASYY EQU 1 pair synchronized yes 1 NDEIASYN EQU 2 pair synchronized no 1 * 1 NDEISRD DS FL1 REM-COPY-STA operand of 1 * SHOW-REM-COPY-STA cmd 1 * attribute remote copy state 1 NDEIARCY EQU 0 remote copy state any 1 NDEIARCA EQU 1 remote copy state active 1 NDEIARCE EQU 2 remote copy state error 1 NDEIARCH EQU 3 remote copy state in hold 1 * 1 NDEISTA DS FL1 TARGET-ACC operand of 1 * SHOW-REM-COPY-STA cmd 1 * attribute remote target access 1 NDEIATAY EQU 0 target access any 1 NDEIATAN EQU 1 target access none 1 NDEIATAS EQU 2 target access through source, 1 * normal path 1 NDEIATAD EQU 3 target access through target, 1 * recovery path 1 * 1 NDEISLS DS FL1 LINK-STATE operand of 1 * SHOW-REM-COPY-STA cmd 1 * attribute link state 1 NDEIALSY EQU 0 link state any 1 NDEIALSA EQU 1 one or more links available 1 NDEIALSN EQU 2 no link available 1 * 1 NDEISRM DS FL1 COPY-MODE operand of 1 * SHOW-REM-COPY-STA cmd 1 * attribute copy mode 1 NDEIACMY EQU 0 copy mode any 1 NDEIACMS EQU 1 synchronous 1 NDEIACME EQU 2 semi-synchronous 1 NDEIACMA EQU 3 adaptive copy 1 *

252 U41000-J-Z125-4-76


1 NDEISOE DS FL1 ON-ERROR operand of 1 * SHOW-REM-COPY-STA cmd 1 * attribute ON-ERROR 1 NDEIAOEY EQU 0 on error any 1 NDEIAOEC EQU 1 on error continue 1 NDEIAOEH EQU 2 on error hold 1 * 1 NDEISMF DS FL1 MULTI-MIRR-STA operand of 1 * SHOW-MULTI-MIRR cmd 1 * attribute multi mirror state 1 NDEIAMMY EQU 0 multi mirror state any 1 NDEIAMMU EQU 1 multi mirror state unused 1 NDEIAMME EQU 2 multi mirror state 1 * established 1 NDEIAMMF EQU 3 multi mirror state 1 * establishing 1 NDEIAMMT EQU 4 multi mirror state splitting 1 NDEIAMMS EQU 5 multi mirror state split 1 NDEIAMMR EQU 6 multi mirror state 1 * reconstructing 1 * 1 NDEISEMF DS FL1 REMOTE COPY USE operand of 1 * SHOW-MULTI-MIRR cmd 1 * select multi mirror unit 1 NDEISMMS EQU 0 multi mirror select std 1 NDEISMMT EQU 1 multi mirror select target 1 * 1 NDEISIMF DS FL1 ADD-MIRROR_INF operand of 1 * SHOW-MULTI-MIRR cmd 1 * info about multi mirror assignments 1 NDEIIMMC EQU 0 info about current assignment 1 NDEIIMMA EQU 1 info about all assignments 1 * 1 NDEISRCF DS FL1 REMOTE-CONFIG operand of 1 * SHOW-SYMM-CONF cmd 1 * select remote config or not 1 NDEIRCFN EQU 0 remote config not selected 1 NDEIRCFY EQU 1 remote config selected 1 * 1 NDEIZZUN DS XL1 filler 1 NDEI# EQU *-NDEIFHDR *

U41000-J-Z125-4-76 253

Program interface The C header file (ndeinf.h)

7.2 The C header file (ndeinf.h)

The C header file (ndeinf.h) is present in the library SYSLIB.SHC-OSD.030 as part of the SHC-OSD selectable unit. The function call is as follows:

#include "FHDR.H"#include "NDEINF.H"

NDESVC (struct NDEINF_pl_mdl param)

254 U41000-J-Z125-4-76

The C header file (ndeinf.h) Program interface

U41000-J-Z125-4-76 255

8 MessagesThe inserts and their contents are listed in the following table:

No Content of the inserts Length in characters

00 MN of the device 4

01 MN of the controller 4

02 Archive number of the volume (VSN) 6

03 Pubset ID 4

04 Command name 32

05 Remote link director # 3

06 second MN 4

07 Free text 32

08 Second free text 32

09 A separator 1

10 Symmetrix serial number 12

11 Symmetrix internal number of the logical volume 4

12 second Symmetrix serial number 12

13 second Symmetrix internal number of the logical volume 4

14 A separator 1

Table 6: Contents of the Inserts

256 U41000-J-Z125-4-76

NDE0001

NDE0001 SYMMETRIX DEVICE (&00)(&10)(&09)(&11) STATE CHANGED TO: ’(&07)’ (B) Routing code: D Weight: 66

NDE0002 SYMMETRIX CONTROLLER ’(&01)’ ACCESSIBLE (B) Routing code: D Weight: 66

NDE0003 SYMMETRIX CONTROLLER ’(&01)’ NO LONGER ACCESSIBLE (B) Routing code: D Weight: 66

NDE0004 SYMMETRIX DEVICE ’(&00)’ ATTACHED TO CONTROLLER ’(&01)’ (B) Routing code: D Weight: 66

NDE0005 SYMMETRIX DEVICE ’(&00)’ DETACHED FROM CONTROLLER ’(&01)’ (B) Routing code: D Weight: 66

NDE0006 SYMMETRIX SUBSYSTEM ’(&07)’ ACCESSIBLE VIA CONTROLLER ’(&01)’ (B) Routing code: D Weight: 66

MeaningSYMMETRIX SUBSYSTEM: specifies the SYMMETRIX subsystem of emulated controllers and devices by its serial number.

NDE0007 SYMMETRIX SUBSYSTEM ’(&07)’ NO LONGER ACCESSIBLE (B) Routing code: D Weight: 66


NDE0008 HOST ACCESS FOR SYMMETRIX SUBSYSTEM ’(&10)’ CHANGED TO: ’(&08)’ (B) Routing code: D Weight: 66


NDE0010 SYMMETRIX SUBSYSTEM ’(&10)’ STATE OF REMOTE LINK DIRECTOR ’(&05)’ CHANGED TO ’(&07)’ (B) Routing code: D Weight: 66

MeaningDirector: Channel adapter card of Symmetrix subsystem. REMOTE-LINK-DIRECTOR (RA): Channel adapter used to connect two Symmetrix subsystems for remote copy (SRDF).

U41000-J-Z125-4-76 257

NDE0011

NDE0011 GROUP ’(&09)’ OF REMOTE LINK DIRECTORS ’(&08)’ OF SYMMETRIX SUBSYSTEM ’(&07)’ AVAILABLE (B) Routing code: D Weight: 66

MeaningThe connection is available via at least one REMOTE-LINK-DIRECTOR of the group. Director: Channel adapter card of Symmetrix subsystem. REMOTE-LINK-DIRECTOR (RA): Channel adapter used to connect two Symmetrix subsystems for remote copy (SRDF). Two Symmetrix subsystems are connected by one or more groups of REMOTE- LINK-DIRECTORS.

NDE0012 GROUP ’(&09)’ OF REMOTE LINK DIRECTORS ’(&08)’ OF SYMMETRIX SUBSYSTEM ’(&07)’ NOT AVAILABLE (B) Routing code: D Weight: 66

MeaningNo more REMOTE-LINK-DIRECTOR of the group is available, i.e. the connection is not available. Director: Channel adapter card of Symmetrix subsystem. REMOTE-LINK-DIRECTOR (RA): Channel adapter used to connect two Symmetrix subsystems for remote copy (SRDF). Two Symmetrix subsystems are connected by one or more groups of REMOTE- LINK-DIRECTORS.

NDE0020 STATE OF ’REMOTE COPY’ CHANGED TO ’(&07)’ FOR DEVICE (&00)(&10)(&09)(&11) (B) Routing code: D Weight: 66

Meaning’REMOTE COPY’ State: State of the remote copy operations for a remote copy pair. Possible values: *ACTIVE, *IN-HOLD or *ERROR.

NDE0021 STATE OF REMOTE COPY SOURCE UNIT (&00)(&10)(&09)(&11) CHANGED TO ’(&07)’ (B) Routing code: D Weight: 66

MeaningSOURCE-UNIT: first device of a remote copy pair which is accessed by the local host.

NDE0022 STATE OF REMOTE COPY TARGET UNIT (&00)(&10)(&09)(&11) CHANGED TO ’(&07)’ (B) Routing code: D Weight: 66

MeaningTARGET-UNIT: second device of a remote copy pair.

258 U41000-J-Z125-4-76

NDE0023

NDE0023 LINK STATE OF REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) CHANGED TO: ’(&07)’ (B) Routing code: D Weight: 66

MeaningLINK-STATE: State of the connection between source unit and target unit of a remote copy pair.Possible values: *AVAILABLE, *NOT-AVAILABLE or *UNDEFINED.

NDE0024 ’TARGET-ACCESS’ FOR REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) CHANGED TO: ’(&07)’ (B) Routing code: D Weight: 66

MeaningTARGET-ACCESS: Access to the target unit of the remote copy pair. Possible values: *BY-SOURCE, *DIRECT or *NONE.

NDE0025 REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) SYNCHRONIZED AGAIN (B) Routing code: D Weight: 66

MeaningThe internal synchronisation process is completed for the remote copy pair in state *ACTIVE.

NDE0026 REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) OUT OF SYNCHRONIZATION (B) Routing code: D Weight: 66

MeaningThe remote copy pair is out of synchronization. The pending updates are kept internal by the SYMMETRIX.

ResponseGet more information using the command

/SHOW-SYMMETRIX-DEVICE-CONFIG ... INFORMATION=*PHYSICAL.

NDE0027 SOURCE-UNIT AND TARGET-UNIT OF REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) SWAPPED (B) Routing code: D Weight: 66

MeaningThe SOURCE- and TARGET-UNIT of the remote copy pair were swapped due to a config-uration change on the SYMMETRIX.


/SHOW-REMOTE-COPY-STATUS ...INFORMATION=*ALL.

U41000-J-Z125-4-76 259

NDE0030

NDE0030 ’MULTI MIRROR’ STATE CHANGED TO ’(&07)’ FOR MULTI MIRROR PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) (B) Routing code: D Weight: 66

MeaningMULTI MIRROR State: Processing state of Multi Mirroring for a multi mirror pair. Possible values: *UNUSED, *UNUSED-LOCKED, *ESTABLISHING, *ESTABLISHED, *SPLITTING, *SPLIT, *SPLIT-LOCKED, *SPLIT-BACKG, *SPLIT-LOCKED-B or *RECONSTRUCTING.

NDE0040 STATE OF INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) CHANGED TO: ’(&08)’ (B) Routing code: D Weight: 66

MeaningInternal Mirror: One logical volume on a Symmetrix subsystem has up to 4 internal physical mirrors. Possible values for insert 7: *LOCAL, *REMOTE, *MIRROR, *PARITY or *ADD-MIRROR.

NDE0041 INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) OUT OF SYNCHRONIZATION (B) Routing code: D Weight: 66

MeaningAn internal mirror ist out of synchronization. The pending updates are kept internal on the Symmetrix.Internal Mirror: One logical volume on a Symmetrix subsystem has up to 4 internal physical mirrors.Possible values for insert 7: *MIRROR or *PARITY.


/SHOW-SYMMETRIX-DEVICE-CONFIG ... INFORMATION=*PHYSICAL.

NDE0042 INTERNAL MIRROR TYPE ’(&07)’ OF SYMMETRIX DEVICE (&00)(&10)(&09)(&11) SYNCHRONIZED AGAIN (B) Routing code: D Weight: 66

MeaningThe synchronisation process is completed for an internal mirror. Internal Mirror: One logical volume on a Symmetrix subsystem has up to 4 internal physical mirrors. Possible values for insert 7: *MIRROR or *PARITY.

NDE0100 (&07)-ADMIN-SCOPE FOR SHC-OSD CHANGED TO ’(&08)’ (C) Routing code: D Weight: 66

260 U41000-J-Z125-4-76

NDE1000

NDE1000 DEVICE ’(&00)’ NOT FOUND OR NOT IN A SYMMETRIX SUBSYSTEM Warranty: Y

MeaningThe device is not generated as an emulated device of a Symmetrix subsystem or not generated at all.

NDE1001 DEVICE (&00)(&10)(&09)(&11) NOT ATTACHED Warranty: Y

NDE1002 CONTROLLER UNIT ’(&01)’ NOT FOUND OR NOT A SYMMETRIX SUBSYSTEM Warranty: Y

MeaningThe controller unit is not generated as an emulated controller of a Symmetrix subsystem or not generated at all.

NDE1003 VOLUME ’(&02)’ NOT ONLINE, NOT UNIQUE OR NOT ON A SYMMETRIX SUBSYSTEM Warranty: Y

NDE1004 PUBSET ’(&03)’ NOT FOUND OR NOT ON A SYMMETRIX SUBSYSTEM Warranty: Y

NDE1005 PUBSET ’(&03)’ NOT HOMOGENEOUS Warranty: Y

MeaningNot all volumes of the pubsets were found, are Remote Copy, or are Multi Mirror volumes respective.

NDE1006 (&07) ’(&02)(&03)’ NOT FREE Warranty: Y

MeaningThe specified volume/pubset is allocated.

NDE1007 NO CONTROLLER OF A SYMMETRIX SUBSYSTEM FOUND Warranty: Y

MeaningNo controller unit could be identified as an emulated controller unit of a SYMMETRIX subsystem. Possible reasons: - No SYMMETRIX subsystem is existing or generated on this host. - The type of the emulated controller is not supported.

The following types are supported: 3860-42, 3860-43 and 3860-51. - The installation prerequisits for the subsystem SHC-OSD are not completely fullfilled.

U41000-J-Z125-4-76 261

NDE1008

NDE1008 VOLUME ’(&02)’ COULD NOT BE ALLOCATED ON DEVICE ’(&00)’ Warranty: Y

MeaningEither the volume itself could not be allocated (e.g. if it already is allocated by a different system or if a NKVD013 message has been rejected) or the corresponding pubset could not be occupied.

NDE1009 LOCK-CONFLICT DURING PROCESSING OF COMMAND ’(&04)’ Warranty: Y

MeaningA lock conflict occurred due to concurrent access to internal data of the SHC-OSD.

ResponsePlease retry your command input.

NDE1010 MICROCODE LEVEL NOT SUPPORTED FOR SELECTED SYMMETRIX SUBSYSTEM(S) Warranty: Y

MeaningThe current version of SHC-OSD supports the microcode levels 5266, 5267, 5566, 5567 and 5568.

NDE1011 NO ACCESS TO SELECTED SYMMETRIX SUBSYSTEM, BECAUSE NO OR NO SUITABLE DEVICE ATTACHED Warranty: Y

MeaningTo access a Symmetrix subsystem at least one device must be attached. For /HOLD-MULTI-MIRROR or /RESUME-MULTI-MIRROR a second device besides the NORMAL-UNIT to be processed has to be attached, because the NORMAL-UNIT cannot be used for TimeFinder actions.

NDE1012 I/O ERROR DURING PROCESSING Warranty: Y

NDE1013 MICROCODE LEVEL NOT SUPPORTED FOR SOME SELECTED SYMMETRIX SUBSYSTEMS Warranty: Y

MeaningThe current version of SHC-OSD supports the microcode levels 5266, 5267, 5566, 5567 and 5568.

NDE1014 NO ACCESS TO SOME SELECTED SYMMETRIX SUBSYSTEMS, BECAUSE NO DEVICE ATTACHED Warranty: Y

MeaningTo access a Symmetrix subsystem at least one device must be attached.

262 U41000-J-Z125-4-76

NDE1015

NDE1015 DEVICE (&10)(&09)(&11) NOT DEFINED Warranty: Y

MeaningThe device to be processed is not defined, SHC-OSD knows only its internal device number. However, the chosen function requests the device to be defined.

NDE1016 NO ACCESS TO SOME SELECTED SYMMETRIX SUBSYSTEMS, BECAUSE NO REMOTE IO’S POSSIBLE Warranty: Y

NDE1017 COMMAND (&04) REJECTED FOR CURRENT TASK/SYSTEM-ADMIN-SCOPE Warranty: Y

MeaningThe current settings of SYSTEM-ADMIN-SCOPE and TASK-ADMIN-SCOPE do not allow the processing of the command with the given operands.

ResponseDisplay the current settings:

/SHOW-SHC-PROCESSING Modify the settings:

/MODIFY-SHC-PROCESSING SYSTEM-ADMIN-SCOPE=*PARAMETERS(...), TASK-ADMIN-SCOPE=*PARAMETERS(...)

NDE1020 NO REMOTE COPY FUNCTION FOR (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) Warranty: Y

MeaningThe unit specifies the selected MN of the device, VSN of the volume, catid of the pubset or MN of the controller selected by the command input. Values for insert 7:

UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified. LOGICAL-VOLUME, if Insert 10 and 11 are specified.

U41000-J-Z125-4-76 263

NDE1021

NDE1021 (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) IS (HAS) NO SOURCE-UNIT Warranty: Y

MeaningThe unit specifies the selected MN of the device, VSN of the volume, catid of the pubset or MN of the controller selected by the command input. Values for insert 7:

UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

SOURCE-UNIT: first device of a remote copy pair which is addressed by the local host.

NDE1022 (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) IS OR HAS NO TARGET UNIT Warranty: Y

MeaningValues for insert 7:

UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

TARGET-UNIT: second device of a remote copy pair.

NDE1023 DIRECTOR ’(&05)’ NO REMOTE-LINK-DIRECTOR OF CONTROLLER UNIT/SYMMETRIX (&01)(&10) Warranty: Y

MeaningDirector: Channel adapter card of Symmetrix Subsystem. REMOTE-LINK-DIRECTOR: Channel adapter of channel type S used to connect two Symmetrix subsystems for remote copy.

NDE1024 REMOTE CONTROLLER UNIT ’(&01)’ NOT FOUND Warranty: Y

MeaningPossible reasons: - No SYMMETRIX controller unit with this MN found. - The controller unit was found but is emulated in the local SYMMETRIX.

NDE1025 NO DIRECT ACCESS FROM LOCAL HOST TO SOURCE-UNIT (&00)(&10)(&09)(&11) Warranty: Y


264 U41000-J-Z125-4-76

NDE1026

NDE1026 NO DIRECT ACCESS FROM HOST TO TARGET UNIT: (&06)(&12)(&14)(&13) Warranty: Y

MeaningTARGET-UNIT: second device of a remote copy pair.

NDE1027 REMOTE-COPY PAIR (&00)(&10)(&09)(&11),(&06)(&12)(&14)(&13) STATE IS *ACTIVE. COMMAND ’(&04)’ NOT PROCESSED. Warranty: Y

NDE1028 VOLUMES IN (&07) ’(&01)(&02)(&03)’ NOT UNIQUE Warranty: Y

MeaningWerte fuer Insert 7: CONTROLLER, wenn Insert 1 versorgt ist. VOLUME, wenn Insert 2 versorgt ist. PUBSET, wenn Insert 3 versorgt ist.

NDE1029 TARGET UNIT (&00)(&10)(&09)(&11) IN STATE ’*DISABLED’ DUE TO PENDING UPDATES Warranty: Y

NDE1030 NO MULTI MIRROR FUNCTION FOR (&07) (&00)(&02)(&10)(&09)(&11) Warranty: Y

MeaningValues for insert 7: UNIT, if insert 0 is valid VOLUME, if insert 2 is valid

NDE1031 DIFFERENT NUMBER OF DEVICES FOR NORMAL-UNIT AND ADD-MIRROR-UNIT Warranty: Y

MeaningThe number of devices for the specified pubset is different from the number of specified devices for the ADD-MIRROR-UNIT.

NDE1032 MULTI-MIRROR PAIR (&00)(&10)(&09)(&11) NOT YET SYNCHRONIZED Warranty: Y

NDE1033 MULTI-MIRROR PAIR ON DEVICE (&00)(&10)(&09)(&11) NOT YET SPLIT Warranty: Y

NDE1034 ADDITIONAL-MIRROR UNIT (&06)(&12)(&14)(&13) USED IN OTHER MULTI-MIRROR PAIR Warranty: Y

NDE1035 DEVICE (&00)(&10)(&09)(&11) NO NORMAL-UNIT Warranty: Y

NDE1036 DIFFERENT LENGTHS OF CATALOG IDENTIFIERS OF ’PUBSET’ AND ’NEW-PUBSET’ Warranty: Y

U41000-J-Z125-4-76 265

NDE1037

NDE1037 MN’S OR DEVICE NUMBERS OF THE NORMAL-UNIT AND OF THE ADDITIONAL-MIRROR-UNIT IDENTICAL: (&00)(&10)(&09)(&11) Warranty: Y

NDE1038 NORMAL-UNIT (&00)(&10)(&09)(&11) AND ADDITIONAL-MIRROR-UNIT (&06)(&12)(&14)(&13) OF DIFFERENT (META) TYPE OR DIFFERENT SIZE Warranty: Y

ResponsePlease check the concerned units with /SHOW-SYMMETRIX-DEVICE-CONFIG.

NDE1039 NORMAL-UNIT (&00)(&10)(&09)(&11) AND ADDITIONAL-MIRROR-UNIT (&06)(&12)(&14)(&13) ON DIFFERENT SYMMETRIX SUBSYSTEMS Warranty: Y

NDE1040 STATE OF NORMAL-UNIT (&00)(&02)(&10)(&09)(&11) WRONG: ’(&07)’ Warranty: Y

MeaningPossible reason for this message: If you specified /HOLD-MULTI-MIRROR with the option HOLD-IO=*UNTIL-SPLIT, the command is rejected if one or more MULTI-MIRROR pairs are already split.

ResponseCheck the MULTI-MIRROR state(s) using /SHOW-MULTI-MIRROR.

NDE1041 STATE OF ADDITIONAL-MIRROR-UNIT (&06)(&12)(&14)(&13) WRONG: ’(&07)’ Warranty: Y

NDE1042 NORMAL-UNIT (&00)(&10)(&09)(&11) IS A TARGET-UNIT AND RESTORE=*TO-ORIGINAL Warranty: Y

MeaningRESUME-MULTI-MIRRORING RESTORE=*TO-ORIGINAL is not supported if the original device is also used as TARGET-UNIT of a remote copy pair. TARGET-UNIT: second device of a remote copy pair.

NDE1043 PUBSET TYPE OF PUBSET ’(&03)’ NOT SUPPORTED Warranty: Y

Meaning1. System managed pubsets (SM-pubsets) are supported by SHC-OSD only in

BS2000/OSD-BC V4.0 and higher. 2. /HOLD-MULTI-MIRRORING does not support integrated renaming of

SM-pubsets or volume sets (operand NEW-PUBSET). 3. /HOLD-MULTI-MIRRORING with operand HOLD-IO=*UNTIL-SPLIT is not

supported for volume sets.

266 U41000-J-Z125-4-76

NDE1044

NDE1044 ’NEW-PUBSET’ ’(&03)’ ALREADY EXISTS Warranty: Y

MeaningDisk(s) were found ONLINE or allocated that may belong to the pubset to be created by /HOLD-MULTI-MIRRORING.

NDE1045 COMMAND ’(&04)’ NOT YET COMPLETED, PUBSET RENAMING NOT POSSIBLE Warranty: Y

MeaningSplitting of all multi mirror pairs of the pubset is not yet completed. The renaming of the ADDITIONAL-MIRROR-UNITs requested by the command can’t be processed. Command rejected.

NDE1046 ’OPERATING’ PRIVILEGE NOT SET FOR USER ID, COMMAND ’(&04)’ CANNOT BE EXECUTED Warranty: Y

MeaningWhile processing the command /START-MULTI-MIRRORING, /HOLD-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING, the command ’(&04)’ should be executed. However, this is only possible if the privilege ’OPERATING’ is set for the current user ID. Values for command (Insert 04:) /UNLOCK-DISK: /HOLD-MULTI-MIRRORING tries to reset the allocating systems

in the SVL of the ADD-MIRROR-UNITs. This may affect operation of disks shared between two hosts or virtual machines (SPD or shared pubsets).

/DETACH-DEVICE: /START-MULTI-MIRRORING or /RESUME-MULTI-MIRRORING try toremove the ADD-MIRROR-UNITS to prevent erroneous accesses to the unavailabledisks. This will only occur on hosts that attach a Symmetrix via SCSI or fibre channel.

/ATTACH-DEVICE: /HOLD-MULTI-MIRRORING tries to attach removed ADD-MIRROR-UNITs again. This will only occur on hosts that attach a Symmetrix via SCSI of fibre channel.

Responsea) If SECOS is used, allow privilege OPERATING for the user ID. This

enables ALL operating commands for tasks of this user ID, which might have unwanted consequences.

b) Execute the command for all concerned disks on the console.

NDE1047 SHC-OSD SUSPENDS IO ACCESS TO PUBSET ’(&03)’ Warranty: Y

MeaningWhile executing the command /HOLD-MULTI-MIRROR with option HOLD-IO=*UNTIL-SPLIT, IOs to the pubset (&03) are suspended. They will be resumed when all current IOs are terminated and all necessary actions to split the multi mirror pairs are executed.

NDE1048 SHC-OSD RESUMES IO ACCESS TO PUBSET ’(&03)’ Warranty: Y

U41000-J-Z125-4-76 267

NDE1049

NDE1049 NO ’ADDITIONAL-MIRROR-UNIT’ ASSIGNED TO (&00)(&10)(&09)(&11) AND ’SELECT-ADD-MIRROR=(&07)’ Warranty: Y

NDE1050 ’MULTI-ADD-MIRRORS=*NO’ SPECIFIED FOR NORMAL-UNIT (&00)(&10)(&09)(&11), BUT OLD ASSIGNMENTS EXIST Warranty: Y

ResponseDelete old assignments using /STOP-MULTI-MIRRORING or specify MULTI-ADD-MIRRORS=*YES.

NDE1051 TOO MANY ADDITIONAL-MIRROR-UNITS ASSOCIATED TO NORMAL-UNIT (&00)(&10)(&09)(&11) Warranty: Y

MeaningTo one NORMAL-UNIT, only a certain number of ADDITIONAL-MIRROR-UNITS can be associated. The maximum number can be displayed with the /SHOW-SHC-PROCESSING command. If this number is exceeded, further commands /START-MULTI-MIRRORING are rejected.

ResponseDelete old assignments using /STOP-MULTI-MIRRORING.

NDE1055 FUNCTION ’MULTI-BCV’ NOT SUPPORTED BY MICROCODE Warranty: Y

MeaningThe function Multi-BCV is not supported by the current microcode level. Information about current ADDITIONAL-MIRROR assignments is provided.

ResponseThe function Multi-BCV is supported starting with microcode level 5x66.

NDE1056 NO INFORMATION ABOUT MULTI-ADDITIONAL-MIRROR-UNITS Warranty: Y

MeaningNo information is available about ADDITIONAL-MIRROR-UNITS previously assigned by function Multi-BCV. Information about current ADDITIONAL-MIRROR assignments is provided.

268 U41000-J-Z125-4-76

NDE1060

NDE1060 REMOTE COPY PAIR SELECTED BY (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) NOT IN STATE ’*ACTIVE’ Warranty: Y

MeaningHOLD-REMOTE-COPY is not supported, if the state of the remote copy pair is not ’*ACTIVE’. The unit specifies the selection by command input. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

NDE1061 REMOTE COPY PAIR SELECTED BY (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) NOT IN STATE ’*IN-HOLD’ Warranty: Y

MeaningRESUME-REMOTE-COPY is not supported, if the state of the remote copy pair is not ’*IN-HOLD’. The unit specifies the selection by command input. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

NDE1062 ’TARGET-ACCESS’ FOR THE REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) NOT ’*BY-SOURCE’ Warranty: Y

MeaningTARGET-ACCESS: Access to the target unit of a remote copy pair. Possible values: *BY-SOURCE, *DIRECT or *NONE.

NDE1063 SOURCE-UNIT OF THE REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) NOT IN STATE ’*READY’ Warranty: Y


NDE1064 TARGET-UNIT OF THE REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) IN STATE ’*READY’, ’*READ-ONLY’ OR ’*DISABLE’ Warranty: Y

MeaningResuming remote copy was unsuccessful due to the current state *READY or *READ-ONLY or *DISABLE of the target unit. TARGET-UNIT:second device of a remote copy pair.

U41000-J-Z125-4-76 269

NDE1065

ResponsePlease enter the command /SET-REMOTE-COPY-ACCESS with the operand TARGET-ACCESS = *BY-SOURCE for the concerned Symmetrix units.

NDE1065 VALUE ’*HOLD’ FOR PARAMETER ’ON-ERROR’ OF THE REMOTE COPY PAIR (&00)(&10)(&09)(&11),(&06)(&12)(&14)(&13) Warranty: Y

MeaningThe parameter ON-ERROR defines the reaction on errors during remote copy processes. Possible values: *HOLD or *CONTI.

NDE1066 NO REMOTE-LINK AVAILABLE BETWEEN SOURCE-UNIT (&00)(&10)(&09)(&11) AND TARGET-UNIT (&06)(&12)(&14)(&13) Warranty: Y

MeaningSOURCE-UNIT: first device of a remote copy pair which is accessed by the local host. TARGET-UNIT: second device of a remote copy pair.

NDE1067 REMOTE COPY PAIR WITH SOURCE-UNIT (&00)(&10)(&09)(&11) NOT YET SYNCHRONIZED Warranty: Y

MeaningThe synchronization of the remote copy pair is not yet completed due to pending updates - after setting the COPY-MODE to SYNCHRONOUS or SEMI-SYNCHRONOUS, - after resuming the remote copy function with /RESUME-REMOTE-COPY, - before suspending the remote copy function with /HOLD-REMOTE-COPY. SOURCE-UNIT: first device of a remote copy pair which is accessed by the local host.

ResponseTo suspend the remote copy function, use /HOLD-REMOTE-COPY with option FORCE=*YES.

NDE1068 REFRESHING THE REMOTE COPY PAIR WITH SOURCE-UNIT (&00)(&10)(&09)(&11) NOT SUCCESSFUL Warranty: Y

MeaningRESUME-REMOTE-COPY could not be processed because of failing ’REFRESH’-function. The ’REFRESH’-function ist strictly necessary before starting any copy or restauration processing between source-unit and target-unit. SOURCE-UNIT: first device of a remote copy pair. TARGET-UNIT: second device of a remote copy pair.

270 U41000-J-Z125-4-76

NDE1069

NDE1069 NO CURRENT INFORMATION AVAILABLE ABOUT SOME REMOTE COPY PAIRS Warranty: Y

MeaningThere is no access to some Source-Units or Target-Units of Remote Copy pairs for the moment. As result some internal administration data tables of SHC-OSD are not updated.

NDE1070 REMOTE COPY MODE CHANGED TO ’(&07)’ FOR DEVICE (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

NDE1071 REMOTE-COPY PARAMETER ’ON-ERROR’ CHANGED TO ’(&07)’ FOR DEVICE (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

NDE1072 PARAMETER ’TARGET-ACCESS’ CHANGED TO ’(&07)’ FOR REMOTE COPY PAIR (&00)(&10)(&09)(&11), (&06)(&12)(&14)(&13) Warranty: Y (B) Routing code: 0 Weight: 70

NDE1073 (&04)(&07) PROCESSED FOR PAIR (&00)(&10)(&09)(&11),(&06)(&12)(&14)(&13) Warranty: Y (B) Routing code: 0 Weight: 70

NDE1074 (&04) PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’ Warranty: Y (B) Routing code: 0 Weight: 70

NDE1075 REMOTE CONTROLLER UNIT ’(&06)’ AND CONTROLLER UNIT ’(&01)’ IN SAME SYMMETRIX SUBSYSTEM Warranty: Y

MeaningThe specified remote controller unit is contained in the SYMMETRIX subsystem specified by the local controller unit. Remote Copy Pairs have to be located in different SYMMETRIX subsystems.

NDE1076 LOCAL SYNCHRONIZATION STILL PENDING ON (&07) (&00)(&10)(&09)(&11) Warranty: Y

MeaningRESUME-REMOTE-COPY RESTORE=*FROM-SOURCE is not supported, if there are local pending updates on the SOURCE-UNIT. RESUME-REMOTE-COPY RESTORE=*TO-SOURCE is not supported, if there are local pending updates on the TARGET-UNIT, or the state of ’MULTI-MIRROR’ of the SOURCE-UNIT is ’*RECONSTRUCTING’. This behaviour ensures the consistency of data on the remote-copy pair. RESUME-MULTI-MIRRORING RESTORE=*FROM-ORIGINAL is not supported, if there are local pending updates on the NORMAL-UNIT. RESUME-MULTI-MIRRORING RESTORE=*TO-ORIGINAL is not supported, if there are local pending updates on the ADD-MIRROR-UNIT. This behaviour ensures the consistency of data on the multi-mirror pair.

U41000-J-Z125-4-76 271

NDE1077

NDE1077 COEXISTENCE OF REMOTE COPY MODE ’*ADAPTIVE-COPY’ WITH WRITE BUFFER ’*DISK’ AND PARAMETER ’ON-ERROR = *HOLD’ NOT POSSIBLE FOR SOURCE-UNIT (&00)(&10)(&09)(&11) Warranty: Y

MeaningMODIFY-REMOTE-COPY-PARAMETERS ... ON-ERROR=*HOLD is not supported, if the remote copy mode is set to *ADAPTIVE-COPY with WR-BUFFER=*DISK. MODIFY-REMOTE-COPY-PARAMETERS ... COPY-MODE=*ADAPTIVE-COPY(WRITE-BUFFER=*DISK) is not supported, if the parameter ON-ERROR is set to *HOLD. This behaviour ensures the consistency of data on the remote-copy pair.

NDE1078 REMOTE-COPY-UNIT ’(&00)’ USED FOR PAGING ALLOCATION Warranty: Y

MeaningThe Source-Unit/Target-Unit of the remote copy pair is used for paging. Modifying the TARGET-ACCESS or the ON-ERROR parameter would lead to system crash.

NDE1079 NO DEVICE OF SELECTED (&07) (&00)(&01)(&02)(&03)(&10) ATTACHED Warranty: Y

MeaningNo device selected by the operand UNIT is attached. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

NDE1080 NO REMOTE-LINK-DIRECTOR FOUND FOR CONTROLLER-UNIT/SYMMETRIX (&01)(&10) Warranty: Y

MeaningDirector: Channel adapter card of Symmetrix Subsystem. REMOTE-LINK-DIRECTOR: Channel adapter of channel type S used to connect two Symmetrix subsystems for remote copy.

NDE1081 SYNCHRONOUS PROCESSING OF COMMAND ’(&04)’ NOT POSSIBLE FOR DEVICE (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

MeaningThe REMOTE-COPY-STATUS is not *ACTIVE, i.e. the copy process to synchronize the remote copy pair can’t be started or completed.

NDE1082 SHORTAGE OF MEMORY DURING PROCESSING OF COMMAND ’(&04)’ Warranty: Y (B) Routing code: 0 Weight: 70

272 U41000-J-Z125-4-76

NDE1083

NDE1083 VOLUME ’(&02)’ ON DEVICE (&00)(&10)(&09)(&11) LOCKED Warranty: Y

MeaningThe additional mirror unit has been locked at the last /HOLD-MULTI-MIRRORING command with operand LOCK-ADD-MIRROR=*YES. The normal units can be locked also (by other EMC programs).

ResponseRetry command specifying UNLOCK-ADD-MIRROR=*YES.

NDE1084 MULTI-MIRROR PAIR (&00)(&10)(&09)(&11) ALREADY SPLIT. COMMAND NOT PROCESSED Warranty: Y

NDE1085 COMMAND ’(&04)’ WITH OPERAND ’HOLD-IO=*UNTIL-SPLIT’ NOT SUPPORTED Warranty: Y

MeaningOperand HOLD-IO=*UNTIL-SPLIT is only supported in BS2000/OSD-BC V3.0 and higher.

NDE1086 OPTION ’(&07)’ OF VOLUME ’(&02)’ ON DEVICE (&00)(&10)(&09)(&11) NOT SUPPORTED, PROCESSING CONTINUES Warranty: Y

MeaningThe option is not supported by the microcode of the Symmetrix. Possible values for OPTION: LOCK-ADD-MIRROR=*YES: For /HOLD-MULTI-MIRRORING this option has been

specified to prevent an (accidental) /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING. This option has been supported since Symmetrix Microcode Version 5265.

UNLOCK-ADD-MIRROR=*YES: For /RESUME-MULTI-MIRRORING or /START-MULTI- MIRRORING this option has been specified. This option has been supported since Symmetrix Microcode Version 5265.

RESUME-REMOTE-COPY=*BY-USER: For /HOLD-MULTI-MIRRORING this option was specified to prevent an automatic resume of remote copy. This option has been supported since Symmetrix Microcode Version 5265.

RESTORE-DATA=*MODIFIED-ONLY: For /HOLD-MULTI-MIRRORING this option was specified to copy only the modified data to the second mirror of the additional mirror unit. This option has been supported since Symmetrix Microcode Version 5265.

MULTI-ADD-MIRRORS=*YES: For /START-MULTI-MIRRORING this option was specified to instruct the Symmetrix to track changes between the currently assigned ADDITIONAL-MIRROR-UNITs and the ORIGINAL-UNITs. This option has been supported since Symmetrix Microcode Version 5x66.

U41000-J-Z125-4-76 273

NDE1087

ResponseNone. The command is executed for this device as if the option has not been specified.

NDE1087 (&07) ’(&02)(&03)’ NOT ALLOCATED, HOLD-IO=*UNTIL-SPLIT NOT PERMITTED Warranty: Y

MeaningThe specified volume/pubset is not allocated although HOLD-IO=*UNTIL-SPLIT was specified. Values for insert 7: VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

ResponseRetry command with HOLD-IO=*NO.

NDE1088 (&07) MB PENDING UPDATES STILL TO BE COPIED FROM (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

MeaningPending updates of the specified size are copied from the SOURCE resp. NORMAL unit (&00) to the corresponding TARGET resp. ADD-MIRROR unit to synchronize the REMOTE-COPY or MULTI-MIRROR pair.

NDE1089 (&07) MB PENDING UPDATES STILL TO BE COPIED TO UNIT (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

MeaningPending updates of the specified size are copied from the TARGET resp. ADD-MIRROR unit to the SOURCE resp. NORMAL unit (&00) to synchronize the REMOTE-COPY or MULTI-MIRROR pair.

NDE1090 RESTORE-DATA=*MODIFED-ONLY NOT POSSIBLE FOR ADDITIONAL MIRROR UNIT (&00)(&10)(&09)(&11) Warranty: Y (B) Routing code: 0 Weight: 70

MeaningAt command /HOLD-MULTI-MIRRORING the operand RESTORE-DATA=*MODIFIED-DATA has been specified. This optimized update between the first and the second internal mirror of the Additional-Mirror-Unit is only possible if SDDF is enabled in the Symmetrix. SDDF: Symmetrix Differential Data Facility.

ResponseNone, processing continues.

274 U41000-J-Z125-4-76

NDE1091

NDE1091 OPTION ’(&07)’ NOT SUPPORTED, BECAUSE ADDITIONAL-MIRROR UNIT (&00)(&10)(&09)(&11) HAS NO SECOND MIRROR. PROCESSING CONTINUES Warranty: Y (B) Routing code: 0 Weight: 70

MeaningPossible values for OPTION: LOCK-ADD-MIRROR=*YES: For /HOLD-MULTI-MIRRORING this option has been

specified to prevent an (accidential) /RESUME-MULTI-MIRRORING or /START-MULTI-MIRRORING.

UNLOCK-ADD-MIRROR=*YES: For /RESUME-MULTI-MIRRORING or /START-MULTI- MIRRORING this option has been specified.

RESUME-REMOTE-COPY=*BY-USER: For /HOLD-MULTI-MIRRORING this option was specified to prevent an automatic resume of remote copy.

RESTORE-DATA=*MODIFIED-ONLY: For /HOLD-MULTI-MIRRORING this option was specified to copy only the modified data to the second mirror of the additional mirror unit.

ResponseNone. These options have been supported since Symmetrix Microcode Version 5265. The command is executed for this device as if the option has not been specified.

NDE1092 MULTI-MIRROR PAIR (&00)(&10)(&09)(&11) ALREADY ’SPLIT’, ADDITIONAL-MIRROR-UNIT ALREADY RENAMED TO ’(&02)’ Warranty: Y (B) Routing code: 0 Weight: 70

MeaningAt /HOLD-MULTI-MIRRORING a new catid for the Additional-Mirror-Units was requested. However (at least) for this unit, the command has been issued before with a different catid.

NDE1093 REMOTE COPY PAIR WITH SOURCE UNIT (&00)(&10)(&09)(&11) NOT IN STATE ’*ACTIVE’ ANY MORE Warranty: Y

MeaningThe command is aborted, because the state of the remote copy pair has changed during processing.

NDE1094 SOURCE-UNIT ’(&00)(&10)(&09)(&11)’ STATE=*DISABLE AND ON-ERROR=*HOLD Warranty: Y

MeaningThe Source Unit of the Remote Copy Pair is in state *DISABLE due to the Remote Copy Parameter ON-ERROR=*HOLD to assure data consistency on Source-Unit and Target-Unit. Setting the TARGET-ACCESS to *BY-SOURCE is not possible in this state.

U41000-J-Z125-4-76 275

NDE1100

ResponseActions to be performed: 1. /MODIFY-REMOTE-COPY-PARAMETERS <unit>,ON-ERROR=*CONTINUE 2. /SET-REMOTE-COPY-ACCESS <unit>,TARGET-ACCESS=*DIRECT

NDE1100 PUBSET ’(&03)’ IS IN STATE ’(&07)’ Warranty: Y

Meaning1. All commands support pubsets only if they are locally imported or completely exported. 2. SHOW-commands support SM-pubsets only if they are locally imported.

NDE1101 MORE THAN ONE SHARER FOR PUBSET ’(&03)’ AND REQUIREMENTS FOR HOLD-IO FOR SHARED PUBSETS NOT MET Warranty: Y

MeaningRequirements: 1. BS2000/OSD V5 on master and all slave computers 2. SHC-OSD >= V3.0 on master and all slave computers 3. command execution on master 4. MSCF connections between master and all slave computers are active 5. Pubset is neither on master or on all slave computers in state QUIET

NDE1102 NOT ALL VOLUMES OF PUBSET ’(&03)’ ALLOCATED Warranty: Y

MeaningPossible Reasons: 1. The Pubset could not be allocated. 2. The list of volumes for the SM-Pubset in state EXPORTED can’t be

provided due to not unique VSNs mounted on the devices.

ResponsePlease input command /DETACH-DEVICE for not used devices to avoid not unique VSNs.

NDE1103 NO RECONFIGURATION LOCK FOR PUBSET ’(&03)’ Warranty: Y

MeaningThe imported Pubset could not be locked against reconfiguration.

276 U41000-J-Z125-4-76

NDE1104

NDE1104 DAB CACHING ACTIVE FOR PUBSET ’(&03)’ ON HOST ’(&07)’ Warranty: Y

MeaningThe imported Pubset uses DAB for caching. The specified action may lead to data inconsistency. Values for Insert 07: *LOCAL-HOST: own (local) host <hostname> : BCAM name of partner computer in MSCF cluster.

NDE1105 PUBSET ’(&03)’ VOLUME CATALOG NOT READABLE OR INCONSISTENT Warranty: Y

MeaningThe Pubset Online Catalog could on the PUBRES volume could not be read or is incon-sistent. This may occur if the PUBRES was only initializied but no pubset has yet been built. PUBRES: First volume of a pubset, e.g. PUBA00.

NDE1106 ’(&04)’ WAITS FOR DEVICES TO COMPLETE SYNCHRONIZATION Warranty: Y

Meaning’(&04)’ is a command of SHC-OSD where the user specified to wait for the completion of a synchronization process it initialized. The command can be terminated in dialog mode by pressing the K2 key.

NDE1107 NO ALLOCATION POSSIBLE FOR PUBSET ’(&03)’ Warranty: Y

MeaningPossible Reasons: 1. The Pubset could not be allocated. 2. The list of volumes for the SM-Pubset in state EXPORTED can’t be provided due to

not unique VSNs mounted on the devices.

ResponsePlease input command /DETACH-DEVICE for not used devices to avoid not unique VSNs.

NDE1108 DEVICE (&00)(&10)(&09)(&11) NO REMOTE COPY SOURCE-UNIT, ’(&04)’ WITH SELECT=*TARGET-UNIT NOT POSSIBLE Warranty: Y

Meaning(&04) was called with SELECT=*TARGET-UNIT. The device (&00) specified by the UNIT operand is no remote copy source unit; there is no corresponding target unit existing. The command is rejected.

U41000-J-Z125-4-76 277

NDE1109

NDE1109 REMOTE-COPY TARGET-UNIT CORRESPONDING TO DEVICE (&00)(&10)(&09)(&11) UNKNOWN, ’(&04)’ WITH SELECT=*TARGET-UNIT NOT POSSIBLE Warranty: Y

Meaning(&04) was called with SELECT=*TARGET-UNIT. For the device (&00) specified by the operand UNIT no remote copy Target-Unit can be found due to unavailable direct or remote access to the Symmetrix subsystem. The command is rejected.

Response- Provide direct access attaching (/ATTACH-DEVICE) a device or the

corresponding remote copy Target-Unit or - Provide remote access enabling the remote link directors

(/ENABLE-REMOTE-LINK-DIRECTOR) and retry the command.

NDE1110 TARGET-UNIT OF DEVICE (&00)(&10)(&09)(&11) IS NOT SYNCHRONIZED, ’(&04)’ WITH SELECT=*TARGET-UNIT REJECTED Warranty: Y

Meaning(&04) was called with SELECT=*TARGET-UNIT. The device (&00) specified by the UNIT operand and its remote copy Target-Unit are not synchronized, not in synchronous remote copy mode or not in remote copy state ’*IN-HOLD’. The command is rejected.

Responsea) set the remote copy mode to SYNCHRONOUS or b) resume the remote copy function and wait for the synchronization to complete or c) suspend the remote copy function.

NDE1111 VOLUME ’(&02)’ ALLOCATED BY DRV, ’HOLD-IO=*UNTIL-SPLIT’ NOT POSSIBLE Warranty: Y

MeaningDRV = Dual Recording by Volume. Even in Mode DRV-MONO HOLD-MULTI-MIRRORING with option HOLD-IO= *UNTIL-SPLIT is not possible.

Response1. export pubset 2. Stop DRV mode with /SET-DRV-PARAMETER ..,RECORDING-MODE=SRV 3. import pubset

NDE1114 SYMMETRIX SUBSYSTEM ’(&10)’ NOT FOUND Warranty: Y

MeaningThere is currently no SYMMETRIX subsystem with the specified serial number.

278 U41000-J-Z125-4-76

NDE1115

NDE1115 SERIAL NUMBER ’(&10)’ OF SYMMETRIX SUBSYSTEM NOT UNIQUE Warranty: Y

MeaningThe specified serial number is not unique.

NDE1116 LOGICAL VOLUME ’(&11)’ NOT FOUND IN SYMMETRIX SUBSYSTEM ’(&10)’ Warranty: Y

MeaningThe specified logical volume is not contained in the SYMMETRIX subsystem.

NDE1118 NO MULTI-MIRROR FUNCTION FOR TARGET-UNIT(S) CORRESPONDING TO (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) Warranty: Y

MeaningThe TARGET-UNIT(s) for the device(s) specified by the operand UNIT have no multi-mirror function. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

NDE1119 NO TARGET-UNIT(S) CORRESPONDING TO (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) FOUND Warranty: Y

MeaningNo remote copy TARGET-UNIT could be determined for the device(s) specified by the operand UNIT. Possible reasons: - the specified device(s) is (are) no remote copy SOURCE-UNIT(s). - the remote copy TARGET-UNIT(s) is (are) unknown in the local host. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

U41000-J-Z125-4-76 279

NDE1120

NDE1120 ERROR SUSPENDING OR RESUMING IO ACCESS TO PUBSET (&03), COMMAND (&04) ABORTED Warranty: Y

MeaningError during the execution of command (&04) with option HOLD-IO=*UNTIL-SPLIT: Suspending or resuming IO access might have failed on the local host or on the slave hosts using the pubset The command is aborted because the data on the ADDITIONAL-MIRROR-UNITs might not be as consistent as required. If communication to slave hosts was interrupted, issue a /RESUME-IO PUBSET=(&03) command on each slave to make sure IO access will be resumed. In any case, you have to reestablish the MULTI-MIRROR pairs using /RESUME-MULTI-MIRROR PUBSET=(&03).

ResponseIf communication to slave hosts was interrupted, issue a /RESUME-IO PUBSET=(&03) command on each slave to make sure IO access will be resumed. In any case, you have to reestablish the MULTI-MIRROR pairs using /RESUME-MULTI-MIRROR PUBSET=(&03).

NDE1130 COMMAND ’(&04)’ REJECTED FOR SYMMETRIX SUBSYSTEM ’(&10)’ DUE TO HOST ACCESS=*REMOTE Warranty: Y

MeaningDisabling the last REMOTE-LINK-DIRECTOR of a Symmetrix subsystem accessible from host via remote link only is rejected. This action would cut off any access from host to the Symmetrix and therefore it would be a point of no return.

NDE1131 RA-GROUP ’(&09)’ NOT FOUND ON SYMMETRIX SUBSYSTEM (&10) Warranty: Y

MeaningRA group: Group of REMOTE-LINK DIRECTORS used to connect two Symmetrix subsystens for remote copy.

NDE1150 NO GATEKEEPER DEVICE FOR SYMMETRIX SUBSYSTEM (&10)

MeaningThere is currently no eligible gatekeeper device to process IOs on the specified Symmetrix subsystem.

Response/ATTACH-DEVICE for a device in state READY on the specified Symmetrix Subsystem and retry.

NDE1151 SYMMETRIX SUBSYSTEM (&10) LOCKED FOR COMMANDS

MeaningThe Symmetrix subsystem might be locked temporarily during concurrent actions.

280 U41000-J-Z125-4-76

NDE1152

ResponseRetry command.

NDE1152 SYMMETRIX FORCE OPTION NOT ALLOWED FOR SRDF

MeaningThe command will only be processed if the option SYMAPI_ALLOW_RDF_SYMFORCE in the SYMAPI file /var/symapi/config/options is set to TRUE.

ResponsePlease consult the official EMC documentation for SYMAPI.

NDE1153 SYMMETRIX DEVICE (&00)(&10)(&09)(&11) LOCKED FOR COMMANDS. ADDITIONAL INFORMATION: (&07)

MeaningThe Symmetrix device might be locked temporarily during concurrent actions.

ResponseRetry command.

NDE1154 (&07) (&00)(&01)(&02)(&03)(&10)(&09)(&11) IS (HAS) ’META MEMBER’

MeaningSymmetrix meta devices consist of one meta head and meta member devices. SRDF and TimeFinder commands are allowed only for meta head devices. The unit specifies the selected MN of the device, VSN of the volume, catid of the pubset or MN of the controller selected by the command input. Values for insert 7: UNIT, if Insert 0 is specified. CONTROLLER, if Insert 1 is specified. VOLUME, if Insert 2 is specified. PUBSET, if Insert 3 is specified.

NDE1155 (&04) NOT SUPPORTED FOR RAID-10 SYMMETRIX DEVICE (&00)(&10)(&09)(&11)

MeaningThe current version of SYMAPI does not support RAID-10 .

NDE1156 RA-GROUP(S) ’(&07)’ OF SYMMETRIX SUBSYSTEM (&10) UNLOCKED FOR COMMANDS (B) Routing code: D Weight: 99

NDE1157 SYMMETRIX DEVICE(S) (&00)(&10)(&09)(&11) UNLOCKED FOR COMMANDS (B) Routing code: D Weight: 99

U41000-J-Z125-4-76 281

NDE1158

NDE1158 NORMAL-UNIT (&00)(&10)(&09)(&11) AND ADDITIONAL-MIRROR-UNIT (&06)(&12)(&14)(&13) META VOLUMES OF DIFFERENT STRIPE SIZE Warranty: Y

MeaningStriped Meta-Volumes die als TimeFinder-Paar verwendet werden sollen, sind in der Symmetrix mit gleicher stripe size zu konfigurieren.

NDE1200 SHC-OSD TASK INITIALISATION ERROR. REASON: ’(&07)’ (C) Routing code: D Weight: 66

NDE1201 SHC-OSD TASK READY. SYMAPI VERSION ’(&07)’/’(&08)’ (C) Routing code: D Weight: 66

NDE1202 SHC-OSD TASK ABNORMAL TERMINATION (C) Routing code: D Weight: 66

MeaningA SHC-OSD task hit a program error and will terminated abnormally. A user dump may be created that is important for diagnostic purposes.

NDE2000 COMMAND ’(&04)’ PROCESSED WITH PARTIAL SUCCESS Warranty: Y

MeaningFinal message of a SHC-OSD command for which not all parts have been successfully processed.

NDE2001 COMMAND ’(&04)’ COMPLETED UNSUCCESSFULLY Warranty: Y

MeaningFinal message of a SHC-OSD command which has not been successfully processed.

NDE2002 INTERNAL ERROR IN COMMAND ’(&04)’ Warranty: Y

MeaningFinal message of a SHC-OSD command which could not be processed successfully due to an internal error.

NDE2003 COMMAND ’(&04)’ SUCCESSFUL, NO ACTION NECESSARY Warranty: Y

MeaningFinal message of a SHC-OSD command for which no processing was necessary.

282 U41000-J-Z125-4-76

NDE2004

NDE2004 COMMAND ’(&04)’ SUCCESSFUL, PROCESSING NOT YET COMPLETED Warranty: Y

MeaningFinal message of a SHC-OSD command that has been started successfully, but the processing is not finished yet.

NDE2005 COMMAND ’(&04)’ CANNOT BE PROCESSED AT THE MOMENT Warranty: Y

MeaningFinal message of a SHC-OSD command that can not be started at the moment for internal reasons: - SHC-OSD cannot lock internal tables (LOCK-CONFLICT) - HOLD-MULTI-MIRROR with option HOLD-IO=*UNTIL-SPLIT:

Timeout while locking IOs - Resource limitations in Symmetrix (load may be too high)

NDE2006 NO OUTPUT INFORMATION FOR COMMAND ’(&04)’ Warranty: Y

MeaningFinal message of a SHC-OSD SHOW-command with no output information for the specified input operands.

NDE2007 COMMAND ’(&04)’ NOT PROCESSED FOR DEVICE (&00)(&10)(&09)(&11) (&07) (&06)(&12)(&14)(&13) Warranty: Y (B) Routing code: 0 Weight: 70

NDE2008 COMMAND ’(&04)’ NOT PROCESSED FOR DIRECTOR ’(&05)’ OF SYMMETRIX ’(&10)’ WITH CONTROLLER ’(&01)’ Warranty: Y (B) Routing code: 0 Weight: 70

NDE2009 SYNCHRONOUS PROCESSING OF COMMAND ’(&04)’ ABORTED BY K2 KEY OR CANCEL-JOB Warranty: Y

MeaningFinal message of a SHC-OSD command which synchronous processing was interrupted by input of key K2.

NDE2010 COMMAND ’(&04)’ COMPLETED WITH WARNINGS Warranty: Y

MeaningFinal message of a SHC-OSD command which has been processed successfully after output of warning message(s).

U41000-J-Z125-4-76 283

NDE2011

NDE2011 NO LICENSE, COMMAND ’(&04)’ REJECTED Warranty: Y

MeaningSHC-OSD requires license key registration for SYMAPI. The following keys are required for the individual commands: SHOW commands:BASE license REMOTE-COPY commands:BASEand SRDF license MULTI-MIRROR commands: BASEand BCVlicense

ResponseAdd the required registration keys with the POSIX program symlmf. It is usually installed in /opt/emc/bin.

284 U41000-J-Z125-4-76

NDE2011

U41000-J-Z125-4-76 285

9 AppendixThis chapter contains a description of the metasyntax for SDF commands and statements and the representation of command return codes, S variables and macros.

9.1 Metasyntax for SDF commands

Notes on the SDF user interface

The statements and commands of the functional units described here are processed by the SDF (System Dialog Facility) command processor. The functional units thus offer various forms of guided and unguided dialog and permit help menus for the statements and commands to be requested. A correction dialog can be executed in the case of invalid entries. See also the manual “Introductory Guide to the SDF Dialog Interface” [15].

Abbreviation of names

SDF permits entries to be abbreviated in both dialog (interactive) and batch mode. However, these abbreviations must be unambiguous within the existing syntax environment.

However, an abbreviation which is unambiguous at the moment may become ambiguous at a later date, particularly if additional functions are implemented. It is therefore advisable to avoid the use of abbreviations, particularly in cataloged command sequences.

Command and statement names, operands and symbolic operand values can be abbre-viated in two stages:

● entire parts of the name can be omitted from right to left;

● individual characters can be omitted from right to left within each part of the name.

Exception: an asterisk (*) before a constant operand value is not a valid abbreviation for this operand value.

286 U41000-J-Z125-4-76

Metasyntax for SDF commands Appendix

Input example

Full form of the command:

/MODIFY-SDF-OPTIONS SYNTAX-FILE= USER(NAME= *DEACTIVATE), GUIDANCE= MINIMUM

Abbreviated form of the command:

/MOD-SDF SYN-F=US(NA=*D),GUID=MIN

As an aid to the user, the format diagrams of the commands and statements show a possible abbreviation for each name in boldface font. Note that these abbreviations are simply suggestions for abbreviated input; they are not necessarily the shortest possible abbreviations in their syntax environment.

Positional operands

SDF permits operands to be specified either as keyword operands or as positional operands. However, it cannot be guaranteed that all operands will retain their current positions in the next version of the program. For this reason, the use of positional operands should be avoided, particularly in command sequences.

Syntax description

This syntax description is valid for SDF V4.5A.The syntax of the SDF command/statement language is explained in the following three tables.

Table 7: Notational conventions

The meanings of the special characters and the notation used to describe command and statement formats are explained in table 7.

Table 8: Data types

Variable operand values are represented in SDF by data types. Each data type represents a specific set of values. The number of data types is limited to those described in table 8 on page 290.

The description of the data types is valid for the entire set of commands/statements. Therefore only deviations (if any) from table 8 on page 290 are explained in the relevant operand descriptions.

U41000-J-Z125-4-76 287

Appendix Metasyntax for SDF commands

Table 9: Suffixes for data types

Data type suffixes define additional rules for data type input. They contain a length or interval specification and can be used to limit the set of values (suffix begins with without), extend it (suffix begins with with), or declare a particular task mandatory (suffix begins with mandatory). The following short forms are used in this manual for data type suffixes:

cat-id catcompletion complcorrection-state corrgeneration genlower-case lowmanual-release manodd-possible oddpath-completion path-complseparators septemporary-file temp-file underscore underuser-id userversion verswildcard-constr wild-constrwildcards wild

The description of the ‘integer’ data type in table 9 on page 296 contains a number of items in italics; the italics are not part of the syntax and are only used to make the table easier to read. For special data types that are checked by the implementation, table 9 on page 296 contains suffixes printed in italics (see the special suffix) which are not part of the syntax.

The description of the data type suffixes is valid for the entire set of commands/statements. Therefore only deviations (if any) from table 9 on page 296 are explained in the relevant operand descriptions.

288 U41000-J-Z125-4-76


Metasyntax

Representation Meaning Examples

UPPERCASE

LETTERS Uppercase letters denote keywords (command, statement or operand names, keyword values) and constant operand values. Keyword values begin with *.

HELP-SDF

SCREEN-STEPS = *NO

UPPERCASE

LETTERS

in boldface

Uppercase letters printed in boldface denote guaranteed or suggested abbreviations of keywords.

GUIDANCE-MODE = *YES

= The equals sign connects an operand name with the associated operand values.

GUIDANCE-MODE = *NO

< > Angle brackets denote variables whose range of values is described by data types and suffixes (see Tables 8 and 9).

SYNTAX-FILE = <filename 1..54>

Underscoring Underscoring denotes the default value of an operand.

GUIDANCE-MODE = *NO

/ A slash serves to separate alternative operand values.

NEXT-FIELD = *NO / *YES

(…) Parentheses denote operand values that initiate a structure.

,UNGUIDED-DIALOG = *YES (...) / *NO

[ ] Square brackets denote operand values which introduce a structure and are optional. The subsequent structure can be specified without the initiating operand value.

SELECT = [*BY-ATTRIBUTES](...)

Indentation Indentation indicates that the operand is dependent on a higher-ranking operand.

,GUIDED-DIALOG = *YES (...)

*YES(...)

SCREEN-STEPS = *NO /

*YES

Table 7: Metasyntax (part 1 of 2)

U41000-J-Z125-4-76 289


A vertical bar identifies related operands within a structure. Its length marks the beginning and end of a structure. A structure may contain further structures. The number of vertical bars preceding an operand corresponds to the depth of the structure.

SUPPORT = *TAPE(...)

*TAPE(...)

VOLUME = *ANY(...) *ANY(...) ...

, A comma precedes further operands at the same structure level.

GUIDANCE-MODE = *NO / *YES

,SDF-COMMANDS = *NO / *YES

list-poss(n): The entry “list-poss” signifies that a list of operand values can be given at this point. If (n) is present, it means that the list must not have more than n elements. A list of more than one element must be enclosed in parentheses.

list-poss: *SAM / *ISAM

list-poss(40): <structured-name 1..30>

list-poss(256): *OMF / *SYSLST(...) /

<filename 1..54>

Alias: The name that follows represents a guaranteed alias (abbreviation) for the command or statement name.

HELP-SDF Alias: HPSDF

Representation Meaning Examples

Table 7: Metasyntax (part 2 of 2)

290 U41000-J-Z125-4-76


Data types

Data type Character set Special rules

alphanum-name A…Z0…9$, #, @

cat-id A…Z0…9

Not more than 4 characters; must not begin with the string PUB

command-rest freely selectable

composed-name A…Z0…9$, #, @hyphenperiod catalog ID

Alphanumeric string that can be split into multiple substrings by means of a period or hyphen. If a file name can also be specified, the string may begin with a catalog ID in the form :cat: (see data type filename).

c-string EBCDIC character Must be enclosed within single quotes; the letter C may be prefixed; any single quotes occurring within the string must be entered twice.

date 0…9Structure identifier: hyphen

Input format: yyyy-mm-dd jjjj: year; optionally 2 or 4 digitsmm: monthtt: day

device A…Z0…9hyphen

Character string, max. 8 characters in length, corresponding to a device available in the system. In guided dialog, SDF displays the valid operand values. For notes on possible devices, see the relevant operand description.

fixed +, - 0…9period

Input format: [sign][digits].[digits]

[sign]: + or -[digits]: 0...9

must contain at least one digit, but may contain up to 10 characters (0...9, period) apart from the sign.

Table 8: Data types (part 1 of 6)

U41000-J-Z125-4-76 291


filename A…Z0…9$, #, @hyphenperiod

Input format:

[:cat:][$user.]

:cat: optional entry of the catalog identifier; character set limited to A...Z and 0...9; maximum of 4 characters; must be enclosed in colons; default value is the catalog identifier assigned to the user ID, as specified in the user catalog.

$user. optional entry of the user ID; character set is A…Z, 0…9, $, #, @; maximum of 8 characters; first character cannot be a digit; $ and period are mandatory; default value is the user's own ID.

$. (special case)system default ID

file file or job variable name; may be split into a number of partial names using a period as a delimiter: name1[.name2[...]] namei does not contain a period and must not begin or end with a hyphen; file can have a maximum length of 41 characters; it must not begin with a $ and must include at least one character from the range A...Z.



filefile(no)group

group(*abs)(+rel)(-rel)

292 U41000-J-Z125-4-76


filename (contd.)

#file (special case) @file (special case)

# or @ used as the first character indicates temporary files or job variables, depending on system generation.

file(no) tape file name no: version number; character set is A...Z, 0...9, $, #, @. Parentheses must be specified.

group name of a file generation group (character set: as for “file”)

group

(*abs) absolute generation number (1-9999); * and parentheses must be specified.

(+rel) (-rel)

relative generation number (0-99); sign and parentheses must be specified.

integer 0…9, +, - + or -, if specified, must be the first character.

name A…Z 0…9$, #, @

Must not begin with 0...9.



(*abs)(+rel)(-rel)

U41000-J-Z125-4-76 293


partial-filename A…Z0…9$, #, @hyphenperiod

Input format: [:cat:][$user.][partname.]

:cat: see filename$user. see filename

partname optional entry of the initial part of a name common to a number of files or file generation groups in the form: name1.[name2.[...]] namei (see filename).The final character of “partname” must be a period. At least one of the parts :cat:, $user. or partname must be specified.

posix-filename A...Z0...9special characters

String with a length of up to 255 characters; consists of either one or two periods or of alpha-numeric characters and special characters. The special characters must be escaped with a preceding \ (backslash); the / is not allowed. Must be enclosed within single quotes if alter-native data types are permitted, separators are used, or the first character is a ?, ! or ^. A distinction is made between uppercase and lowercase.

posix-pathname A...Z0...9special charactersstructure identifier: slash

Input format: [/]part1/.../partnwhere parti is a posix-filename; max. 1023 characters; must be enclosed within single quotes if alter-native data types are permitted, separators are used, or the first character is a ?, ! or ^.



294 U41000-J-Z125-4-76


product-version A…Z0…9periodsingle quote

Input format:

where m, n, s and o are all digits and a is a letter. Whether the release and/or correction status may/must be specified depends on the suffixes to the data type (see suffixes without-corr, without-man, mandatory-man and mandatory-corr in table 9). product-version may be enclosed within single quotes (possibly with a preceding C). The specification of the version may begin with the letter V.

structured-name A…Z0…9$, #, @hyphen

Alphanumeric string which may comprise a number of substrings separated by a hyphen. First character: A...Z or $, #, @

text freely selectable For the input format, see the relevant operand descriptions.

time 0…9structure identifier: colon

Time-of-day entry:

Input format:

hh: hoursmm: minutesss: seconds

vsn a) A…Z 0…9

a) Input format: pvsid.sequence-no max. 6 characters pvsid: 2-4 characters; PUB must

not be enteredsequence-no: 1-3 characters

b) A…Z 0…9 $, #, @

b) Max. 6 characters;PUB may be prefixed, but must not be followed by $, #, @.



[[C]’][V][m]m.naso[’]

correction status

release status

hh:mm:sshh:mmhh

Leading zeros may be omitted

U41000-J-Z125-4-76 295


x-string Hexadecimal: 00…FF

Must be enclosed in single quotes; must be prefixed by the letter X. There may be an odd number of characters.

x-text Hexadecimal: 00…FF

Must not be enclosed in single quotes; the letter X must not be prefixed. There may be an odd number of characters.



296 U41000-J-Z125-4-76


Suffixes for data types

Suffix Meaning

x..y unit With data type “integer”: interval specification

x minimum value permitted for “integer”. x is an (optionally signed) integer.

y maximum value permitted for “integer”. y is an (optionally signed) integer.

unit with “integer” only: additional units. The following units may be specified: days byte hours 2Kbyte minutes 4Kbyte seconds Mbyte milliseconds

x..y special With the other data types: length specification For data types catid, date, device, product-version, time and vsn the length specification is not displayed.

x minimum length for the operand value; x is an integer.

y maximum length for the operand value; y is an integer.

x=y the length of the operand value must be precisely x.

special Specification of a suffix for describing a special data type that is checked by the implementation. “special” can be preceded by other suffixes. The following specifications are used: arithm-expr arithmetic expression (SDF-P) bool-expr logical expression (SDF-P) string-expr string expression (SDF-P) expr freely selectable expression (SDF-P) cond-expr conditional expression (JV) symbol CSECT or entry name (BLS)

with Extends the specification options for a data type.

-compl When specifying the data type “date”, SDF expands two-digit year specific-tions in the form yy-mm-dd to:

20jj-mm-tt if jj < 6019jj-mm-tt if jj Ï 60

-low Uppercase and lowercase letters are differentiated.

-path-compl

For specifications for the data type “filename”, SDF adds the catalog and/or user ID if these have not been specified.

Table 9: Data type suffixes (part 1 of 7)

U41000-J-Z125-4-76 297


with (contd.)

-under Permits underscores (_) for the data type “name”.

-wild(n) Parts of names may be replaced by the following wildcards.n denotes the maximum input length when using wildcards. Due to the introduction of the data types posix-filename and posix-pathname, SDF now accepts wildcards from the UNIX world (referred to below as POSIX wildcards) in addition to the usual BS2000 wildcards. However, as not all commands support POSIX wildcards, their use for data types other than posix-filename and posix-pathname can lead to semantic errors.Only POSIX wildcards or only BS2000 wildcards should be used within a search pattern. Only POSIX wildcards are allowed for the data types posix-filename and posix-pathname. If a pattern can be matched more than once in a string, the first match is used.

BS2000 wildcards

Meaning

* Replaces an arbitrary (even empty) character string. If the string concerned starts with *, then the * must be entered twice in succession if it is followed by other characters and if the character string entered does not contain at least one other wildcard.

Termina-ting period

Partially-qualified entry of a name.Corresponds implicitly to the string “./*”, i.e. at least one other character follows the period.

/ Replaces any single character.

<sx:sy> Replaces a string that meets the following conditions: – It is at least as long as the shortest string (sx or sy) – It is not longer than the longest string (sx or sy) – It lies between sx and sy in the alphabetic collating

sequence; numbers are sorted after letters (A...Z, 0...9) – sx can also be an empty string (which is in the first position

in the alphabetic collating sequence)– sy can also be an empty string, which in this position stands

for the string with the highest possible code (contains only the characters X’FF’ )

<s1,…> Replaces all strings that match any of the character combina-tions specified by s. s may also be an empty string. Any such string may also be a range specification “sx:sy” (see above).

Suffix Meaning


298 U41000-J-Z125-4-76


with-wild(n) (contd.)

-s Replaces all strings that do not match the specified string s. The minus sign may only appear at the beginning of string s. Within the data types filename or partial-filename the negated string -s can be used exactly once, i.e. -s can replace one of the three name components: cat, user or file.

Wildcards are not permitted in generation and version specifications for file names. Only system administration may use wildcards in user IDs. Wildcards cannot be used to replace the delimiters in name components cat (colon) and user ($ and period).

POSIX wildcards

Meaning

* Replaces any single string (including an empty string). An * appearing at the first position must be duplicated if it is followed by other characters and if the entered string does not include at least one further wildcard.

? Replaces any single character; not permitted as the first character outside single quotes.

[cx-cy] Replaces any single character from the range defined by cx and cy, including the limits of the range. cx and cy must be normal characters.

[s] Replaces exactly one character from string s. The expressions [cx-cy] and [s] can be combined into [s1cx-cys2].

[!cx-cy] Replaces exactly one character not in the range defined by cx and cy, including the limits of the range. cx and cy must be normal characters. The expressions [!cx-cy] and [!s] can be combined into [!s1cx-cys2].

[!s] Replaces exactly one character not contained in string s. The expressions [!s] and [!cx-cy] can be combined into [!s1cx-cys2].

Suffix Meaning


U41000-J-Z125-4-76 299


with (contd.)

wild-constr(n)

Specification of a constructor (string) that defines how new names are to be constructed from a previously specified selector (i.e. a selection string with wildcards). See also with-wild. n denotes the maximum input length when using wildcards.The constructor may consist of constant strings and patterns. A pattern (character) is replaced by the string that was selected by the corresponding pattern in the selector.The following wildcards may be used in constructors:

Wildcard Meaning

* Corresponds to the string selected by the wildcard * in the selector.

Termina-ting period

Corresponds to the partially-qualified specification of a name in the selector;corresponds to the string selected by the terminating period in the selector.

/ or ? Corresponds to the character selected by the / or ? wildcard in the selector.

<n> Corresponds to the string selected by the n-th wildcard in the selector, where n is an integer.

Allocation of wildcards to corresponding wildcards in the selector: All wildcards in the selector are numbered from left to right in ascending order (global index). Identical wildcards in the selector are additionally numbered from left to right in ascending order (wildcard-specific index). Wildcards can be specified in the constructor by one of two mutually exclusive methods:

1. Wildcards can be specified via the global index: <n>

2. The same wildcard may be specified as in the selector; substitution occurs on the basis of the wildcard-specific index. For example:the second “/” corresponds to the string selected by the second “/” in the selector

Suffix Meaning


300 U41000-J-Z125-4-76


with-wild-constr(n)

(contd.)

The following rules must be observed when specifying a constructor:

– The constructor can only contain wildcards of the selector.

– If the string selected by the wildcard <...> or [...] is to be used in the constructor, the index notation must be selected.

– The index notation must be selected if the string identified by a wildcard in the selector is to be used more than once in the constructor. For example: if the selector “A/” is specified, the constructor “A<n><n>” must be specified instead of “A//”.

– The wildcard * can also be an empty string. Note that if multiple asterisks appear in sequence (even with further wildcards), only the last asterisk can be a non-empty string, e.g. for “****” or “*//*”.

– Valid names must be produced by the constructor. This must be taken into account when specifying both the constructor and the selector.

– Depending on the constructor, identical names may be constructed from different names selected by the selector. For example: “A/*” selects the names “A1” and “A2”; the constructor “B*” generates the same new name “B” in both cases. To prevent this from occurring, all wildcards of the selector should be used at least once in the constructor.

– If the constructor ends with a period, the selector must also end with a period. The string selected by the period at the end of the selector cannot be specified by the global index in the constructor specification.

Suffix Meaning


U41000-J-Z125-4-76 301


with-wild-constr(n)(contd.)

Examples:

without Restricts the specification options for a data type.

-cat Specification of a catalog ID is not permitted.

-corr Input format: [[C]’][V][m]m.na[’]Specifications for the data type product-version must not include the correction status.

-gen Specification of a file generation or file generation group is not permitted.

-man Input format: [[C]’][V][m]m.n[’]Specifications for the data type product-version must not include either release or correction status.

-odd The data type x-text permits only an even number of characters.

-sep With the data type “text”, specification of the following separators is not permitted: ; = ( ) < > Ë (i.e. semicolon, equals sign, left and right paren-theses, greater than, less than, and blank).

-temp-file

Specification of a temporary file is not permitted (see #file or @file under filename).

Suffix Meaning


Selector Selection Constructor New name

A//* AB1AB2A.B.C

D<3><2> D1D2D.CB

C.<A:C>/<D,F> C.AADC.ABDC.BAFC.BBF

G.<1>.<3>.XY<2> G.A.D.XYAG.A.D.XYBG.B.F.XYAG.B.F.XYB

C.<A:C>/<D,F> C.AADC.ABDC.BAFC.BBF

G.<1>.<2>.XY<2> G.A.A.XYAG.A.B.XYBG.B.A.XYAG.B.B.XYB

A//B ACDBACEBAC.BA.CB

G/XY/ GCXYDGCXYEGCXY. 1

G.XYC1 The period at the end of the name may violate naming conventions (e.g. for fully-qualified

file names).

302 U41000-J-Z125-4-76


without (contd.)

-user Specification of a user ID is not permitted.

-vers Specification of the version (see “file(no)”) is not permitted for tape files.

-wild The file types posix-filename and posix-pathname must not contain a pattern (character).

mandatory Certain specifications are necessary for a data type.

-corr Input format: [[C]’][V][m]m.naso[’]Specifications for the data type product-version must include the correction status and therefore also the release status.

-man Input format: [[C]’][V][m]m.na[so][’]Specifications for the data type product-version must include the release status. Specification of the correction status is optional if this is not prohibited by the use of the suffix without-corr.

-quotes Specifications for the data types posix-filename and posix-pathname must be enclosed in single quotes.

Suffix Meaning


U41000-J-Z125-4-76 303

Appendix Command return codes

9.2 Command return codes

SDF uses a command return code to provide the user with information about the analysis of the command input and about execution of the command. This command return code is similar to the return code used at the programming level and permits the user to react specifically to certain error situations.

The command return code consists of three parts:

● the maincode, which corresponds to a message key with which more detailed infor-mation can be requested by means of /HELP-MSG-INFORMATION.

● subcode1, which assigns the error situation to an error class from which the severity of the error can be determined. The value of subcode1 is output in decimal. The following five error classes are defined in BS2000/OSD:

– Class A: no errorThe value is zero. Processing can be continued normally.

– Class B: syntax error. The value is a number between 1 and 31. There is a syntax error in the command input. This syntax error should be corrected before the command is retried.

– Class C: internal error (system error). The value is 32. The command should be retried only after the internal error has been rectified.

– Class D: errors which cannot be assigned to any other error class. The value is a number between 64 and 127. The maincode should be evaluated in order to determine what to do next.

– Class E: the command cannot be executed at the present time. The value is a number between 128 and 130. The command can be retried without correction after waiting for a specific period. The length of this waiting period is specified as short, long or undefined.

“Short” is shown by the value 128 and means that waiting within a dialog is regarded as acceptable.

“Long” is shown by the value 129 and means that waiting in batch mode is regarded as acceptable.

“Undefined” is shown by the value 130 and means that it is not certain that the error can be rectified at all.

304 U41000-J-Z125-4-76

Command return codes Appendix

● subcode2, which may contain additional information (value other than zero). The value of subcode2 is output in decimal. In the case of an error (i.e. subcode1 not zero), there are no set rules for the use of subcode2. In addition to zero, subcode2 may have the value 1 or 2 if no error has occurred. Subcode2 with the value 1 indicates that the requested state already existed before the command was issued. Subcode2 with the value 2 indicates a special situation and should be regarded as a warning.

The command return code can only be evaluated with the facilities of SDF-P in S proce-dures and dialog blocks (see the manual “SDF-P” [16]). For details of this evaluation, see also the descriptions of /IF-BLOCK-ERROR and of the builtin functions MAINCODE, SUBCODE1 and SUBCODE2 in the manual “Commands” [1].

Note on the representation of the command return codes:

All command return codes which may be returned for a given command are listed in a table. These command return codes are listed in the order of subcode2, subcode1, maincode and explanatory text. If the value of subcode2 is zero, i.e. there is no additional information, then this is not shown in the table.

The command return codes which can be returned for execution of a BS2000 command are part of the related command description.The following command return codes are automatically returned by SDF if

● SDF detects an error before execution of the command (e.g. syntax error);

● the command cannot be executed;

● the command, i.e. the actual execution module, does not return a command return code. In this case, no command-specific return codes are listed in the command description.

U41000-J-Z125-4-76 305

Appendix Command return codes

1. The command return codes CMD0093, CMD0201 and CMD0205 are not possible if the command was issued via the CMD macro.

2. The command return code CMD0205 is returned if the spin-off mechanism was triggered. Example: program termination by means of the TERM macro with UNIT=STEP and the user program has not set its own command return code by means of the CMDRC macro.

3. The command return code CMD0214 cannot be returned to the calling program by the CMD macro, since the program was terminated by execution of the CMD macro.

4. The command return code CMD0002 is returned by SDF if a program triggers the spin-off mechanism although no error has occurred. This ensures compatible support for the existing spin-off behavior of commands and thus for error handling in procedures. Error handling is not initiated in S procedures which use ERROR-MECHANISM=BY-RETURNCODE (see the /SET-PROCEDURE-OPTIONS or /MODIFY-PROCEDURE-OPTIONS command), since the related subcode1 has the value zero.

(SC2) SC1 Maincode Meaning 0 CMD0001 No error0 CMD0002 Command executed with warning 4)

1 0 CMD0026 Command no longer supported 2 0 CMD0093 Procedure ended in test mode 1)

2 0 CMD0201 End of file reached 1)

2 0 CMD0214 End of program 3)

2 1 CMD0211 SDF transfer area too small 1 CMD0202 Syntax error 5) 6)

1 CMD0205 Spin-off 1) 2)

1 CMD2201 Parameter error 2 CMD0200 Command presently not available 2 CMD2202 Subsystem not defined 3 CMD2203 Installation error 32 CMD0221 Internal SDF error 32 CMD2009 Error during output to variables 64 CMD0216 Requisite privilege missing 65 CMD2241 Subsystem not loaded 66 CMD2242 Subsystem not connected 128 CMD2280 Subsystem not available for a short period 129 CMD2281 Subsystem not available for a long period 130 CMD2282 Subsystem not available for an indefinite period

130 NBR0748 After /SHUTDOWN, the only command that can be entered at the operator terminal is /SHOW-PENDING-MSG

306 U41000-J-Z125-4-76

Command return codes Appendix

5. The command return code CMD0202 is returned by SDF if a command does not trigger the spin-off mechanism although an error has occurred. CMD0202 indicates syntax and semantic errors which were detected during command execution. This ensures compatible support for the existing spin-off behavior of commands and thus for error handling in procedures. Error handling is initiated in S procedures which use ERROR-MECHANISM=BY-RETURNCODE (see /SET-PROCEDURE-OPTIONS or /MODIFY-PROCEDURE-OPTIONS), since the related subcode1 has a value other than zero.

6. The command return code CMD0202 is returned by SDF in the case of syntax errors or semantic errors in the execution module.

Note

A command return code can be set in user programs by means of the CMDRC macro. This return code remains set until CMDRC is called again. When the program is terminated, the current command return code from the program is returned to the caller. In proce-dures in which ERROR-MECHANISM=BY-RETURNCODE is specified (see /SET-PROCEDURE-OPTIONS or /MODIFY-PROCEDURE-OPTIONS), error handling is initiated if the value of subcode1 is not zero.

U41000-J-Z125-4-76 307

Appendix Representation of S variables

9.3 Representation of S variables

If the chargeable product SDF-P V2.0A or higher is in use, the output of certain SHOW commands can be directed to structured S variables.

This option of directing output to S variables with SDF-P V2.0A or higher is an alternative to directing output to the system files SYSOUT or SYSLST. SYSOUT and SYSLST outputs consists of constant labels and case-specific variable infor-mation. The output must be directed to a file if the current parts of the total information are to be made available to procedures for further processing. The individual items of infor-mation can subsequently be selected by means of string processing. This requires precise knowledge of the output layout. There is a possibility of SYSOUT and SYSLST layouts changing in future versions, so private procedures must be updated accordingly. In the case of structured output in S variables, each current item of information is stored as the content of an S variable. Users employ the names of the S variables to access the desired items of information in SHOW commands and can ignore the layout. The names of the S variables are predefined for each SHOW command and guaranteed for the future versions, i.e. they will not change.

Name components of the S variables

The names of the list elements (e.g. F-NAME, F-SIZE) are predefined for each SHOW command. They follow the S variable names declared by the user. Whenever possible, the names correspond to the associated operand names. If the information is hierarchically structured on this level, other names follow. The separator is a period.

Contents of the S variables

Whenever possible, the contents of the S variables correspond to the associated operand values. The data type of the S variable is the factor which determines the character set from which the contents of the S variable are drawn.

Data types of the S variables

The tables reproduced under “Output in S variables” are arranged by the names of the S variables. Each S variable has a defined data type : string, integer or boolean. The entry in column T (Type) indicates the data type of the contents: S (string), I (integer), B (boolean).

See “Commands, Volume 6“ [4] for more details.

308 U41000-J-Z125-4-76

Representation of S variables Appendix

U41000-J-Z125-4-76 309

Abbreviations BCV Business Continuance Volume

CA Channel Adapter (Channel Director)

CKD Count Key Data

DA Disk Adapter (Disk Director)

DAB Disk Access Buffer

Dir Director

DSSM Dynamic Subsystem Management

DTDS Disaster-Tolerant Disk System

EA Adapter for channel type S

FBA Fixed Block Architecture

FC Fiber Channel adapter

FTDS Failure Tolerant Disk Systems

HBA Host Bus Adapter

HVE Hyper-Volume Extension

LUN Logical Unit Number

MRSCAT MASTER catalogue

PAV Parallel Access Volume

RA Remote Adapter (Remote Link Director)

RAB Raid Advisory Board

RAID Redundant Array of Independent Disks

RMS Reliant Monitor Software

SA SCSI Adapter

SCD Director for channel type S

SF pubset Single-Feature pubset

SM pubset System-Managed pubset

310 U41000-J-Z125-4-76

Abbreviations

SRDF Symmetrix Remote Data Facility

SMMF Symmetrix Multi Mirror Facility (also known as TimeFinder)

SVL Standard Volume Label

SYMAPI Symmetrix Application Programming Interface

VSN Volume Serial Number (archive number)

WWN World Wide [port] Name

U41000-J-Z125-4-76 311

Glossaryadditional mirror unit

Additional mirror disk in (normal) RAID1 or SRDF that can be separated and used for other purposes (testing, backup, parallel processing, etc.) without impairing current I/O operation. “Additional mirror unit” is synonymous with “Business Continuance Volume”.

business continuance volume (BCV)See definition of additional mirror unit.

catalog ID (catid)Catalog ID used in fully qualified file names. The catalog ID is syntactically identical to the pubset ID.

channel adapter (CA)The channel adapters process the input/output requests from the host end and control access to the cache of the Symmetrix system. Four type 2 channels or two or four type S channels can be connected per channel adapter. The use of two microprocessors permits simultaneous data transfer on two channels per channel adapter.

concurrent BCVThe concurrent BCV function allows two additional mirror units to be assigned to a normal unit concurrently. Both pairs are then in the ESTABLISHED status simultaneously.

CUADD functionIt is possible to generate multiple Control Unit Images for controllers if the controllers provide this function.

data stripingDistribution of the individual data blocks of a file across the access systems.

312 U41000-J-Z125-4-76

Glossary

disaster tolerant disk system (DTDS)The highest level of security in the new system of classification of the RAB (Raid Advisory Board). This level is attained by storage systems that are protected against data loss and failure over a wide area by means of redundant, geographically separate data recording.

disk adapter (DA)Disk adapters control access to the physical drives (access systems). Two microprocessors per disk adapter support a total of four SCSI paths. Simulta-neous data transfer is possible on two SCSI paths per disk director (one path for each side). To ensure reliability, the disk adapters are interconnected in pairs internally.

file catalogThe file catalog TSOSCAT of an SF or SM pubset acts as a container for the catalog entries (e.g. files and job variables) of that pubset. The files and job variables are identified by means of unique names in the format :catid:$userid.name, where catid stands for the catalog ID and userid for the user ID.The file catalog of an SM pubset consists of several catalog files depending on the number of volume sets.

gatekeeper devicesGatekeeper devices are specially configured devices (of a size of 3 MB through 10 MB) in the Symmetrix for handling the I/Os of the host components (in this case SHC-OSD).

local Symmetrix The local Symmetrix is in the local computer center and generally contains the source units. All I/Os are written to the source unit first.

main host The main host is in the local computer center. The original processing takes place on the main host. In normal operation it sends the I/Os to the local Symmetrix.

meta volumeA meta volume is a correctly sequenced, linked set of logical volumes. As far as the host is concerned, these comprise a single logical unit. In fact, there is a meta header volume and all other volumes are then meta member volumes. In the case of TimeFinder and SRDF actions, it is always the meta header volume that is specified. The action is then carried out automatically for the meta header volume and all the associated meta member volumes.

U41000-J-Z125-4-76 313

Glossary

MASTER catalogueThe MASTER catalogue MRSCAT contains an index of all pubsets known to a particular business server, as well as the static and dynamic operating param-eters of the various pubsets. Previously known as an “MRS catalog”.

Multi BCVWith the Multi BCV function it is possible to administer all the assignment and modification information caused by a normal unit to up to 16 additional mirror units in the Symmetrix.

multi-mirror pair A multi-mirror pair consists of a normal unit and an additional mirror unit.

normal unit The unit of a multi-mirror pair that contains the original data

Parallel Access VolumeFunction implemented in Symmetrix controllers. Multiple I/O jobs can be run simultaneously on a logical volume. A logical PAV volume is represented by a basic unit and up to three 3 alias units.

persistent bindingOperating mode for host bus adapters (HBAs) in which the mapping of the WWNs (World Wide [port] Names) of the Symmetrix Fibre Channels to targets on the HBA is fixed by means of entries in the configuration file /kernel/drv/lpfc.conf.

POSIX semaphoreVariables which control access to a shared resource.

pubset (public volume set, PVS)A set of public disks that belong together with the same pubset ID. Pubset is the general name for a set of disks irrespective of the pubset type (SF or SM pubset). A pubset is addressed by the user for the purposes of file access using its catalog ID.

pubset IDName of a SF or SM pubset.

Redundant Array of Independent Disks (RAID)RAID refers to a technological concept for improving the availability of data. The following RAID levels exist: RAID0 to RAID6 and RAIDS (for Symmetrix systems only).

314 U41000-J-Z125-4-76

Glossary

RAID0RAID0 implements the distribution of the individual data blocks of a file (“data striping”) without backing up the data.

RAID1 RAID1 works with fully duplicated data and on a duplicated number of disks.

RAID10RAID10 implements the distribution of the individual data blocks of a file (“data striping”) and at the same time fully duplicates the data on twice the number of disks in the case of CKD disks (RAID1 and RAID0).

RAIDSRAIDS stands for redundant array of independent disks - Symmetrix. Similarly to the conventional RAID4 and RAID5 architecture, RAIDS implements common parity checking for multiple access systems, but there is no distribution of the individual data blocks of a file across the access systems (i.e. no → “data striping”).

RA groupsRA groups define the SRDF connection between two symmetrix systems and are configured using Symmetrix microcode. They are assigned the letters A through H. An RA group consists of two or more remote adapters. A remote adapter and each volume used for SRDF can be assigned to only one RA group.

remote copy pair The remote copy pair consists of the source unit (original) and the target unit (copy of the data), which are connected to each other by means of a remote link.

remote adapter (RA)→ remote link director

remote link directorThe remote link director (remote adapter, RA) is a channel adapter for type S or Fibre channels. It is used to connect the local and remote Symmetrix for remote copying.

remote Symmetrix The remote Symmetrix is in the remote computer center and generally contains the target units. If the entire local computer center fails then the target units are released to be used by the standby host.

U41000-J-Z125-4-76 315

Glossary

SF pubset (single-feature pubset)Pubset with a structure and mode of operation that correspond to the “pubset” up to and including BS2000/OSD-BC V2.0. An SF pubset consists of up to 255 disks. The format of all the disks must be identical for the allocation unit, formatting, PAM key use etc. Certain attributes are assigned to the SF pubset, e.g. high availability, which apply to all the files in the pubset.The SF pubset is addressed by the user only via the catalog ID. The pubset ID of an SF pubset is a syntactic component of the VSN of all disks belonging to the pubset (PUB or point notation).

SM pubset (system-managed pubset)Pubset consisting of several volume sets (see volume sets). The formats and attributes of the various volume sets that belong to an SM pubset can be different. Files with different requirements in terms of availability and perfor-mance can be stored in the SM pubset. Like an SF pubset, the SM pubset is addressed by the user only via one catalog ID.

source path Input/output path from the main host to the source unit

source unit The source unit is generally located on the local Symmetrix. All I/Os are written to the source unit first.

Standard Volume Label SVLStandard volume label containing information required by the system for volume management.

standby host The standby host is located in the remote computer center. It takes over processing tasks if the main host fails and generally uses the target path to the remote Symmetrix.

SX systemsDesignation for Business Servers from Fujitsu Siemens Computers which use a SPARC architecture.

SYMAPI (Symmetrix Application Programming Interface)Strategic interface from EMC for administration and control of the Symmetrix subsystems and which is used within the framework of the “EMC Developers Program”. It allows access to the configuration, status, performance data and important control functions of Symmetrix.

316 U41000-J-Z125-4-76

Glossary

SYMAPI Gkavoid fileOptional file gkavoid in the POSIX directory var/symapi/config in which a list of devices can be specified in the form of BS2000 mnemonic device names and which should not be used as gatekeepers.

SYMAPI Gkselect fileOptional file gkselect in the POSIX directory var/symapi/config in which a list of devices can be specified in the form of BS2000 mnemonic device names and which are to be used as gatekeepers.

SYMAPI options fileoptions file in the POSIX directory var/symapi/config in which the options for operating SYMAPI are defined and modified.

SYMAPI Symavoid fileOptional file symavoid in the POSIX directory var/symapi/config in which a list of Symmetrix subsystems can be specified which are not to be managed by SHC-OSD.

Symmetrix Remote Data Facility (SRDF)A Symmetrix system function, SRDF allows disk mirroring to another Symmetrix, regardless of where it is located, by means of remote copying, and thus offers failure recovery functionality.

Symmetrix / Symmetrix systemSymmetrix systems are high-availability disk storage systems (see the figure on page 10).

systems with a SPARC architectureRefers to business servers from Fujitsu Siemens arranged in a SPARC archi-tecture.

target path Input/output path from the standby host to the target unit

target unitThe target unit is generally located on the remote Symmetrix. The target unit is a copy of the source unit and is synchronized with it. In the event of a failure, the target unit receives the I/Os via the target path.

TimeFinder (Symmetrix Multi Mirror Facility)A Symmetrix system function, TimeFinder establishes, splits and reconstructs multi-mirror pairs.

U41000-J-Z125-4-76 317

Glossary

type S connection director (SCD)Hardware unit that is used to connect multiple controllers to a type S channel, to connect multiple servers to a controller or to extend the connections between type S channels and controllers.

type S channel (S-CON, IBS), type F channel (F-CON, IBF)Channel types based on fibre optics technology. BS2000/OSD-BC supports the S-CON (IBS channel) and F-CON (Fibre Channel, IBF channel) types.The data bits are transmitted serially (type 2 channels transmit data bits in parallel byte by byte).

volume set IDName of a volume set. The volume set ID is a syntactic components of the VSN of all disks belonging to the volume set (PUB or point notation).

Volume serial number VSN6-character alphanumeric identification stored in the → Standard Volume Label of a disk.

WebSysAdmin (WSA)User interface for using the DomainAdmin product the administration of computers in an administration domain.

318 U41000-J-Z125-4-76

Glossary

U41000-J-Z125-4-76 319

Related publicationsPlease contact your local branch office for information on how to order manuals.

The product descriptions of Symmetrix can be found on the internet at the addresshttp://www.emc.com/products/.

[1] BS2000/OSD-BC Commands (volumes 1-5)User Guides

Target groupThe manual addresses both nonprivileged BS2000/OSD users and systems support. ContentsThis manual contains BS2000/OSD commands (basic configuration and selected products) with the functionality for all privileges. The introduction provides information on cmd input.

[2] POSIX (BS2000/OSD)Commands User Guide

Target group This manual addresses all users of the POSIX shell. ContentsThis manual is designed as a work of reference. It describes working with the POSIX shell and the commands of the POSIX shell in alphabetical order.

http://www.emc.com/products/

320 U41000-J-Z125-4-76

Related publications

[3] POSIX (BS2000/OSD)POSIX Basics for Users and System AdministratorsUser Guide

Target group BS2000 system administrators, POSIX administrators, BS2000 users, users of UNIX workstations Contents– Introduction to and working with POSIX– BS2000 software products in a POSIX environment– Installing POSIX – Controlling POSIX and administering file systems– Administering POSIX users– BS2000 commands for POSIX

[4] BS2000/OSD-BC Commands, Volume 6, Output in S Variables and SDF-P-BASYS User Guide

Target groupThis manual is addressed to programmers and users who write procedures. ContentsVolume 6 contains tables of all S variables that are supplied with values by the SHOW commands in conjunction with structured output. Further chapters deal with: – introduction to working with S variables– SDF-P-BASYS

[5] BS2000/OSD-BCIntroductory Guide to Systems SupportUser Guide

Target groupThis manual is addressed to BS2000/OSD systems support staff and operators. ContentsThe manual covers the following topics relating to the management and monitoring of the BS2000/OSD basic configuration: system initialization, parameter service, job and task control, memory/device/system time/user/file/pubset management, assignment of privi-leges, accounting and operator functions.

U41000-J-Z125-4-76 321


[6] BS2000/OSD-BC System InstallationUser Guide

Target groupThis manual is intended for BS2000/OSD system administration.ContentsThe manual describes the generation of the hardware configuration with UGEN and the following installation services: disk organization with MPVS, the installation of volumes using the SIR utility routine, and the IOCFCOPY subsystem.

[7] BS2000/OSD-BCDiagnostics HandbookUser Guide

Target group The manual addresses system programmers, systems support and software maintenance. ContentsThe manual describes tools for identifying, logging and analyzing program execution data. It deals with dump generators (CDUMP, SNAP, SLED), dump analyzers (DAMP,NDMDAMP), logging tools (SERSLOG, AUDIT), the TRACE-MANAGER, and the log evaluator ELFE.

[8] BS2000/OSD-BCUtility RoutinesUser Guide

Target group The manual addresses both nonprivileged users and systems support. ContentsThe manual describes the utilities delivered with the BS2000 basicconfiguration BS2000/OSD-BC.

322 U41000-J-Z125-4-76


[9] BS2000/OSD-BCExecutive Macros User Guide

Target group The manual addresses all BS2000/OSD assembly language programmers. ContentsThe manual contains a summary of all Executive macros, detailed descriptions of each macro with notes and examples, including job variable macros, and a comprehensive general training section.

[10] HIPLEX AF (BS2000/OSD)High-Availability of Applications in BS2000/OSDProduct Manual

Target groupThis manual addresses system administrators and operators of BS2000/OSD.ContentsThe manual provides information on the requirements for switching applications and on operating HIPLEX AF. As it provides concrete know-how on how applications can be made switchable (organisation, generation, adapting procedures), it can also be used in preparing applications for manual switching with maximum reliability.

[11] FDDRL (BS2000/OSD)User Guide

Target group BS2000/OSD system administrators and operatorsContentsFDDRL physically saves and restores the contents of entire disks und pubsets. The manual describes the functions and statements of the program FDDRL for physical data saving in the computer center.

U41000-J-Z125-4-76 323


[12] HSMS / HSMS-SV (BS2000/OSD)Hierarchical Storage Management System2 VolumesUser Guide

Target group – BS2000/OSD users – BS2000/OSD system administrators – HSMS administrators ContentsVolume 1 contains the description of the functions, management and the installation.– Description of the data saving, archival, migration and data transfer functions – HSMS management, invocation, execution and installation – HSMS messages Volume 2 contains the description of the HSMS statements in alphabetical order.

[13] IMON (BS2000/OSD)Installation MonitorUser Guide

Target groupThis manual is intended for systems support staff of the BS2000/OSD operating system. ContentsThe manual describes the installation and administration of BS2000 software using the IMON installation monitor and its three components IMON-BAS, IMON-GPN and IMON-SIC. Installation (standard and customer-specific) using the component IMON-BAS for systems with BS2000-OSD V2.0 and as of BS2000-OSD V3.0 is described in detail with the aid of examples in two separate chapters.

[14] Disaster Recovery Concepts in BS2000/OSD White Paper

Internet address http://www.fujitsu-siemens.com/servers/broschue/brosc_us.htm#WHITEPA

[15] SDF (BS2000/OSD)Introductory Guide to the SDF Dialog Interface User Guide

Target group BS2000/OSD users ContentsThis manual describes the interactive input of commands and statements in SDF format. A Getting Started chapter with easy-to-understand examples and further comprehensive examples facilitates use of SDF. SDF syntax files are discussed.

http://www.fujitsu-siemens.com/servers/broschue/brosc_us.htm#WHITEPA

324 U41000-J-Z125-4-76


[16] SDF-P (BS2000/OSD)Programming in the Command LanguageUser Guide

Target group The manual addresses BS2000/OSD users and systems support. ContentsSDF-P is a structured procedure language in BS2000. The introduction is followed by a detailed description of commands, functions and macros.

[17] SESAM/SQL-Server (BS2000/OSD)PerformanceUser Guide

Target group Experienced users of SESAM/SQL. ContentsThe manual covers how to recognize bottlenecks in the behavior of SESAM/SQL and how to remedy this behavior.

[18] WebSysAdmin/DomainAdmin System Administration within a DomainUser Guide

Target groupThe manual addresses system administrators and field engineering staff. Contents This manual describes how several nodes can be bundled in an administration domain and thus managed jointly. This is possible using the domain administration system “Domain-Admin” via the WSA (WebSysAdmin) user interface.

U41000-J-Z125-4-76 325

Index

Aaccess path for the data of a remote copy pair

setting 146access system, Symmetrix system 11additional mirror unit 311additional mirror unit (TimeFinder) 75, 76

alternating 89lock 84optimized copying 85protected by RAID-1 or SRDF 94sequential 91status 76

addressing Symmetrix units 35alias 289alphanum-name (data type) 290alternating additional mirror units 89

Bbidrectional configuration (SRDF) 49boolean (S variable data type) 307business continuance volume (BCV) 311

CC header file 253cache 10cache size 184cat (suffix for data type) 301catalog ID 311catastrophe 8, 36cat-id (data type) 290changes

since SHC-OSD V3.0A 4to the commands 5

channel adapter (CA) 15, 311channel director 10

channel type S 15command overview (SHC-OSD) 99command-rest (data type) 290commands

DISABLE-REMOTE-LINK-DIRECTOR 101ENABLE-REMOTE-LINK-DIRECTOR 104for TimeFinder 24HOLD-MULTI-MIRRORING 107HOLD-REMOTE-COPY 113MODIFY-REMOTE-COPY-

PARAMETER 118MODIFY-SHC-PROCESSING 125RESUME-IO 134RESUME-MULTI-MIRRORING 135RESUME-REMOTE-COPY 141SET-REMOTE-COPY-ACCESS 146SHOW-MULTI-MIRRORING-STATUS 152SHOW-PUBSET-PARAMETERS 26SHOW-REMOTE-COPY-STATUS 163SHOW-SHC-PROCESSING 179SHOW-SYMMETRIX-

CONFIGURATION 184SHOW-SYMMETRIX-DEVICE-CONFIG 192START-MULTI-MIRRORING 207

commands of the information services 25compl (suffix for data type) 296components, Symmetrix system 9composed-name (data type) 290computer center failure (SRDF) 61concurrent BCV 311configuration

of the Directors 184of the Symmetrix 184

configuration (SHC-OSD) 25constructor (string) 299

326 U41000-J-Z125-4-76

Index

contentsof inserts 255of S variables 307

COPY-MODE 51corr (suffix for data type) 301, 302c-string (data type) 290CUADD function 15, 311

Ddata backup (TimeFinder) 73data integrity after a failure (SRDF) 64data migration (TimeFinder) 74data striping 311data type

alphanum-name 290cat-id 290command-rest 290composed-name 290c-string 290date 290device 290filename 291fixed 290integer 292name 292partial-name 293posix-filename 293posix-pathname 293product-version 294structured-name 294text 294time 294vsn 294x-string 295x-text 295

data types in SDF 286, 290suffixes 287

data types, S variables 307data vaulting 37date (data type) 290device (data type) 290device status (TimeFinder) 76devices in NOT-READY status 20

DISABLE-REMOTE-LINK-DIRECTOR (command) 101

disaster tolerant disk system (DTDS) 312disk adapter (DA) 312disk controllers, emulated 7disk director (DA) 10

configuration 184disks, emulated 7DTDS 312dynamic I/O configuration modification 15

Eemulated disk controllers 7emulated disks 7ENABLE-REMOTE-LINK-DIRECTOR

(command) 104example

alternating additional mirror units 89DISABLE-REMOTE-LINK-DIRECTOR 103ENABLE-REMOTE-LINK-DIRECTOR 105gkselect file 32HOLD-MULTI-MIRRORING 111HOLD-REMOTE-COPY 116MODIFY-REMOTE-COPY-

PARAMETER 123MODIFY-SHC-PROCESSING 133RESUME-IO 134RESUME-MULTI-MIRRORING 139RESUME-REMOTE-COPY 144sequential additional mirror units 91SET-REMOTE-COPY-ACCESS 150SHOW-MULTI-MIRRORING-STATUS 87,

88, 156SHOW-REMOTE-COPY-STATUS 55, 56, 71,

170SHOW-SHC-PROCESSING 179SHOW-SYMMETRIX-

CONFIGURATION 186SHOW-SYMMETRIX-DEVICE-CONFIG 69,

199STOP-MULTI-MIRRORING 215UGEN statement 15

exclusive control via SRDF 36extensions to the commands 5

U41000-J-Z125-4-76 327

Index

Ffailure (SRDF)

as a result of switching back to the local Symmetrix 62

of a protected source or target unit 58of the local Symmetrix 59of the local Symmetrix and the main host (com-

puter center failure) 61of the main host 60of the remote link 59of the remote Symmetrix 59

failure scenarios (SRDF) 57summary 65

Fibre Channel, connecting devices 16file

SYMAPI Gkavoid 316SYMAPI Gkselect 316SYMAPI options 316SYMAPI Symmavoid 316

file catalog 312filename (data type) 291fixed (data type) 290

Ggatekeeper devices 18, 21, 312

configuring 26gen (suffix for data type) 301generation in BS2000/OSD 15gkselect file, example 32global index 299

HHOLD-MULTI-MIRRORING (command) 107HOLD-REMOTE-COPY (command) 113HVE (Hyper-Volume Extension) 11Hyper-Volume Extension (HVE) 11

II/O configuration modification, dynamic 15IMON 27index 299inserts, contents 255

installationof diagnostic aids 29of SHC-OSD 27

installing diagnostic aids 29Instant Split 77integer (data type) 292integer (S variable data type) 307internal settings

change 125display 179maintenance and diagnostics 24

Llocal Symmetrix 312local Symmetrix (SRDF) 47, 50

failure 59logging status changes (SHC-OSD) 41low (suffix for data type) 296

Mmacro, NDEINF 221main host (SRDF) 50, 312

failure 60maintenance and diagnostics

internal settings 24man (suffix for data type) 301, 302mandatory (suffix for data type) 302MASTER catalog 313messages 255meta volume 312Meta Volumes 8metasyntax of SDF 286meta-volume, units output 195meta-volumes 4microcode

Instant Split 77RA groups 48supported statuses 1, 30

migration (TimeFinder) 74MODIFY-REMOTE-COPY-PARAMETER

(command) 118MODIFY-SHC-PROCESSING (command) 125monitoring function (SHC-OSD) 41

328 U41000-J-Z125-4-76

Index

Multi BCV (multi additional mirror units) 74, 313creating a multi-mirror pair 80multi-mirror pair, output information 87reconstructing a multi-mirror pair 86splitting a multi-mirror pair 85unassigning a multi-mirror pair 87

multi-mirror pair (TimeFinder) 313cancelling 213creating 207displaying status 152establishing 78reconstructing 85, 135splitting 81, 107terminating assignment 213with SRDF target unit 95

Nname (data type) 292name components of S variables 307NDEINF (macro) 221new functions in SHC-OSD V3.0A 4normal unit (TimeFinder) 76, 313notational conventions 6

for SDF 286NOT-READY (device status) 20

Oodd (suffix for data type) 301ON-ERROR (SRDF)

remote copy parameter 53operating statuses (SRDF) 56output to S variables 307

Ppartial-filename (data type) 293path-compl (suffix for data type) 296PENDING-UPDATES (SRDF)

remote copy parameter 53Persistent Binding 18persistent binding 313POSIX semaphore 313POSIX semaphores 32posix-filename (data type) 293posix-pathname (data type) 293

processing mode (SRDF) 51asynchronous (ADAPTIVE-COPY) 52changing 118semi-synchronous 52synchronous 51

product-version (data type) 294program interface 221pubset 313pubset (TimeFinder)

consistent splitting 84rename 82

pubset ID (pubset identifier) 313PVS 313

Qquotes (suffix for data type) 302

RRA groups 48, 314RAID0 314RAID10 314RAIDS 314recovery procedures, testing (SRDF) 67

interrupting remote copy operation and enab-ling the target path 68

overview 67reconstructing the source and target units after

testing 71Redundant Array of Independent Disks

(RAID) 313references 6Release Notice 27release Symmetrix device locks 218release Symmetrix locks 217remote adapter (RA) 48, 314remote copy (SRDF) 47remote copy operation (SRDF) 50, 51

COPY-MODE (processing mode) 51interrupting 113ON-ERROR 53operating statuses 56PENDING-UPDATES 53remote copy status 54resuming 141

U41000-J-Z125-4-76 329

Index

remote copy pair (SRDF) 48, 314displaying status of 163

remote copy parameters, changing (SRDF) 118remote copy status (SRDF) 54remote link (SRDF) 48, 50

failure 59remote link director (SRDF) 48, 314

disabling 101enabling 104

remote Symmetrix (SRDF) 47, 50, 314failure 59

requirements for installation 27resources, needed for operation 32resume input/output activity for a pubset 134RESUME-IO (command) 134RESUME-MULTI-MIRRORING (command) 135RESUME-REMOTE-COPY (command) 141

SS system, generation with UGEN 15S systems

fibre channel configuration 20S variable

contents 307data type 307name components 307

SCD (type S connection director) 317sep (suffix for data type) 301sequential utilization of additional mirror units 91SET-REMOTE-COPY-ACCESS (command) 146SF pubset 315SHC-OSD

command overview 99configuration 25delivery components 28installing 27licenses 30monitoring function 41starting 33status changes, logging 41supported Symmetrix systems 30Symmetrix microcode 30terminating 33working with SHC-OSD 34

SHOW-MULTI-MIRRORING-STATUS (command) 152

SHOW-PUBSET-PARAMETERS (command) 26SHOW-REMOTE-COPY-STATUS

(command) 163SHOW-SHC-PROCESSING (command) 179SHOW-SYMMETRIX-CONFIGURATION

(command) 184SHOW-SYMMETRIX-DEVICE-CONFIG

(command) 192SM pubset 315Solaris, Fibre Channel configuration 18source path 315source unit (SRDF) 48, 50, 315

failure 58SPLIT-BACKG, device status (TimeFinder) 77SPLIT-LOCKED, device status (TimeFinder) 77SRDF (Symmetrix Remote Data Facility) 8, 47,

316and TimeFinder 73configuration, bidirectional 49configuration, unidirectional 49configurations 49controlling remote Symmetrix systems 36failure scenarios 57interface overview 49local Symmetrix 47, 50main host 50ON-ERROR 53operating statuses 56PENDING-UPDATES 53remote copy 47remote copy operation 50, 51remote copy pair 48remote copy status 54remote link 48, 50remote link director 48remote Symmetrix 47, 50source unit 48, 50, 315standby host 50target unit 48, 50testing recovery procedures 67

SRDF target units 20Standard Volume Label (SVL) 315

330 U41000-J-Z125-4-76

Index

standby host (SRDF) 50START-MULTI-MIRRORING (command) 207status changes, logging (SHC-OSD) 41string (S variable data type) 307structured-name (data type) 294suffixes for data types 287, 296supported microcode statuses 1SVL 315switch, fibre channel configuration 18SX server

fibre channel configuration 16fibre channel operation 20

SYMAPI 28, 315configuring 31delivery components 29Gkavoid file 316Gkselect file 316installation 30licenses 30options file 316Symmavoid file 316

SYMAPI Gkavoid file 316SYMAPI Gkselect file 316SYMAPI options file 316SYMAPI Symmavoid file 316Symmetrix configuration 13, 184

displaying 184Symmetrix device configuration, displaying 192Symmetrix in BS2000/OSD 7

functions and components 7Symmetrix locks 45Symmetrix microcode status 1Symmetrix Multi Mirror Facility (TimeFinder) 316Symmetrix Remote Data Facility (SRDF) 316Symmetrix system 316Symmetrix system, components 9Symmetrix, fibre channel configuration 18syntax description 286system file

SYSLST 307SYSOUT 307

systems with a SPARC architecture 316systems with SPARC architecture 315

Ttarget path 316target unit (SRDF) 48, 50, 316

failure 58temp-file (suffix for data type) 301terms and their meanings 12testing the recovery procedures (SRDF) 67text (data type) 294time (data type) 294TimeFinder (Symmetrix Multi Mirror Facility) 8,

316additional mirror unit 75, 76additional mirror unit, lock 84additional mirror unit, optimized copying 85additional mirror unit, protected by RAID-1 or

SRDF 94and SRDF 73data backup 73data migration 74device status 76interface overview 76introduction 73migration 74Multi BCV 74, 80multi-mirror pair, establishing 78multi-mirror pair, reconstructing 85multi-mirror pair, splitting 81multi-mirror pairs with SRDF target unit 95normal unit 76prerequisites 75pubset, consistent splitting 84pubset, renaming 82

type F channel, F-CON 317type S channel, S-CON 317type S connection director (SCD) 317type-S channel 15type-S connection director (SCD) 15

Uunder (suffix for data type) 297unidirectional configuration (SRDF) 49Unit

physical and logical relocation for connection to type-S channel 14

U41000-J-Z125-4-76 331

Index

unitdesignation using different language

conventions 13term 12

UNUSED, device status (TimeFinder) 77UNUSED-LOCKED, device status

(TimeFinder) 77user (suffix for data type) 302utilization concept for non-generated units 36

Vvers (suffix for data type) 302volume set ID (volume set identifier) 317VSN 317vsn (data type) 294

WWebSysAdmin (WSA) 19, 317wild(n) (suffix for data type) 297wild-constr (suffix for data type) 299with (suffix for data type) 296with-constr (suffix for data type) 299with-low (suffix for data type) 296without (suffix for data type) 301without-cat (suffix for data type) 301without-corr (suffix for data type) 301without-gen (suffix for data type) 301without-man (suffix for data type) 301without-odd (suffix for data type) 301without-sep (suffix for data type) 301without-user (suffix for data type) 302without-vers (suffix for data type) 302with-under (suffix for data type) 297with-wild(n) (suffix for data type) 297working with SHC-OSD 34WSA 317

XX2000, Fibre Channel configuration 19x-string (data type) 295x-text (data type) 295

332 U41000-J-Z125-4-76

Index

U41000-J-Z125-4-76

Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Readme file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.4 Changes made since the last edition of March 2002 (SHC-OSD V3.0A) . . . . . . . . . . . . 41.5 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Symmetrix in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Functions and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Symmetrix generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.1 Terminology used and explanations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2.2 Mapping the BS2000/OSD generation to the Symmetrix configuration . . . . . . . . . . . . . 132.2.3 Generation in BS2000/OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3 Special issues under SHC-OSD for devices on the Fibre Channel . . . . . . . . . . . . . . . . 162.3.1 Configuration on Business Servers of the SX line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3.2 Operation on Business Servers of the SX line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.3 Configuration on S systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Software product SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Symmetrix configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2 Configuring gatekeeper devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3 Installing SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.1 Requirements for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.2 Delivery components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3.3 Installing SYMAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.4 Symmetrix microcode and licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.5 Configuring SYMAPI to operate SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.6 Resources needed for operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4 Starting SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.5 Terminating SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.6 Working with SHC-OSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6.1 Operating units that have not been generated in BS2000/OSD . . . . . . . . . . . . . . . . . . 353.6.2 Utilization concept for non-generated units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.3 SHC-OSD security functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7 Logging status changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.8 Diagnostic aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

U41000-J-Z125-4-76

Contents

4 SRDF (Symmetrix Remote Data Facility) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.1 Interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.2 SRDF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3 Remote copy operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.3.1 COPY-MODE (processing mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.3.2 ON-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.3.3 PENDING-UPDATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.3.4 Remote copy status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.3.5 Operating statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.4 Failure scenarios and action taken to maintain operation . . . . . . . . . . . . . . . . . . . . . . . 574.4.1 Failure of a protected source or target unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.4.2 Failure of an unprotected source or target unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.4.3 Failure of the remote link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.4.4 Failure of the remote Symmetrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.4.5 Failure of the local Symmetrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.4.6 Failure of the main host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.4.7 Failure of the local Symmetrix and the main host (computer center failure) . . . . . . . . . 614.4.8 Failure as a result of switching back to the local Symmetrix . . . . . . . . . . . . . . . . . . . . . 624.4.9 Data integrity after a failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.4.10 Summary of failure scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.5 Testing the recovery procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.5.1 Interrupting remote copy operation and enabling the target path . . . . . . . . . . . . . . . . . 684.5.2 Reconstructing the source unit and target unit after testing . . . . . . . . . . . . . . . . . . . . . 71

5 TimeFinder (Symmetrix Multi Mirror Facility) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.2 Interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.3 Device status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.4 Working with TimeFinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.4.1 Establishing a multi-mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.4.2 Splitting a multi-mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.4.3 Reconstructing a multi-mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.4.4 Unassigning a multi-mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.4.5 Displaying information on multi-mirror pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.4.6 Utilization concepts for the Multi BCV function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.4.6.1 Alternating additional mirror units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.4.6.2 Sequential utilization of additional mirror units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915.4.7 Additional mirror units protected with RAID1 or SRDF . . . . . . . . . . . . . . . . . . . . . . . . . 945.4.8 Multi-mirror pairs with SRDF target unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

U41000-J-Z125-4-76

Contents

6 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99DISABLE-REMOTE-LINK-DIRECTORDisable remote link directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ENABLE-REMOTE-LINK-DIRECTOREnable remote link directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104HOLD-MULTI-MIRRORINGSplit multi-mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107HOLD-REMOTE-COPYInterrupt remote copy operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113MODIFY-REMOTE-COPY-PARAMETERModify processing mode and remote copy parameters . . . . . . . . . . . . . . . . . . . . . . . 118MODIFY-SHC-PROCESSINGModify internal settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125RESUME-IO Resume input/output activity for pubsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134RESUME-MULTI-MIRRORINGReconstruct multi-mirror pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135RESUME-REMOTE-COPYResume remote copy operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141SET-REMOTE-COPY-ACCESSSet access path for data of remote copy pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146SHOW-MULTI-MIRRORING-STATUSDisplay status of multi-mirror pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152SHOW-REMOTE-COPY-STATUSDisplay status of remote copy pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163SHOW-SHC-PROCESSINGDisplay Internal settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179SHOW-SYMMETRIX-CONFIGURATIONDisplay Symmetrix configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184SHOW-SYMMETRIX-DEVICE-CONFIGDisplay Symmetrix device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192START-MULTI-MIRRORINGCreate multi-mirror pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207STOP-MULTI-MIRRORING Cancel a multi mirror pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213UNLOCK-SYMMETRIX Release Symmetrix locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217UNLOCK-SYMMETRIX-DEVICE Release Symmetrix device locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

U41000-J-Z125-4-76

Contents

7 Program interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2217.1 The NDEINF assembly language macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2217.2 The C header file (ndeinf.h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

8 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

9 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2859.1 Metasyntax for SDF commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2859.2 Command return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3039.3 Representation of S variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

U41000-J-Z125-4-76

SHC-OSD V4.0A (BS2000/OSD)

Symmetrix Host Component

Target group This manual is intended for systems support staff and service technicians.ContentsThe SHC-OSD software product is the BS2000 host component for Symmetrix systems. It provides information services and commands for controlling the Symmetrix functions SRDF (Symmetrix Remote Data Facility) and TimeFinder (Symmetrix Multi Mirror Facility).Brief overview of contents:– Symmetrix in BS2000/OSD– Software component SHC-OSD– SRDF: downtime scenarios and measures for ensuring continued operation– TimeFinder: working with multi-mirror pairs– commands (listed in alphabetical order)Assembler and C program interface

Edition: January 2003

File: shc_osd.pdf

Copyright © Fujitsu Siemens Computers GmbH, 2003.

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

This manual was produced bycognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

http://www.cognitas.de

Comments on SHC-OSD V4.0ASymmetrix Host Component

U41000-J-Z125-4-76

Fujitsu Siemens computers GmbHUser Documentation81730 MunichGermany

Fax: (++49) 0 700 / 372 00000

e-mail: [email protected]://manuals.fujitsu-siemens.com

CommentsSuggestionsCorrections

✁

Submitted by

mailto:[email protected]

http://manuals.fujitsu-siemens.com

The Software Product SHC-OSD is the BS2000

Documents

Transcript of The Software Product SHC-OSD is the BS2000