SVA - Concurrent Copy and Oracle Virtual Disk Storage Systems

Asset ID:	1-71-1007029.1
Update Date:	2011-05-25
Keywords:

Solution Type Technical Instruction Sure

Solution 1007029.1 : SVA - Concurrent Copy and Oracle Virtual Disk Storage Systems

Applies to:

Sun StorageTek V2X SVA Disk System - Version: Not Applicable to Not Applicable [Release: N/A to N/A]
All Platforms
Reviewed for currency 05/25/11

Goal

Concurrent Copy and Oracle StorageTek Virtual Disk Storage Systems. If concurrent copy is not being invoked, the following MVS message may be noted in the jobstream:

ADR735W (001)-T0MI (04), 1999.287 17:42:06 USE OF CONCURRENT COPY FAILED FOR DATA SET PROD01.PROCLIB ON VOLUME PRD005, 002. SERIALIZATION WILL BE HELD AND CONCURRENT COPY WILL NOT BE USED.

Solution

Solution: Review the prerequisites and requirements for concurrent copy. SNAPSHOT is required to use concurrent copy on the Oracle Virtual Disk Storage Systems.

Description: To perform concurrent copy, specify the CONCURRENT keyword on a DFSMSdss COPY or DUMP command. DFSMSdss calls the System Data Mover (SDM), which will call the SNAPSHOT LLAPI. Then the LLAPI will build the SNAPSHOT commands and send them to SVAA for execution. Maintenance for all these components must be applied to the host system software.

Prerequisites: To use virtual concurrent copy (VCC), the following prerequisites must be fulfilled.

1. Install the PSPAM diskette with SNAPSHOT enablement on the SVA/RVA (hardware support).  SVA/RVA microcode level R/T04.03.26 or higher (any K or E level) will support the concurrent copy feature.
2. Apply the PTFs which introduce the Low Level API to SVAA.
3. Install the SNAPSHOT host resident software.
4. Allocate the ANTMAIN working datasets per IBM's instructions.

   The dataset must be named SYS1.ANTMAIN.Ssmfid.SNAP0001 where smfid is the smf identifier for the system on which the job is running. If more than one working set is required, the datasets MUST be named SNAP002, SNAP003, etc and they MUST be named in sequential order.

Software Maintenance: The software components must be at the following levels for the concurrent copy process to function properly.

1. SVAA 3.1 FMID(ssib310) at minimum PTF level L2P001U
SNAPSHOT 1.2 FMID(SS0A120) at current maintenance level or
SNAPSHOT OS/390 FMID(ssoc210) at current maintenance level.
2. DFSMS 1.3 or higher with DSS license enabled:
OW29883 DFSMSdss Support of SNAPSHOT
OW30320 SDM Interface (API) to enable SNAPSHOT
OW29881 SDM Support of SNAPSHOT
OW26926 Volume preferencing to volumes provided by DFSMSdss
3. DFSMS Storage Class Support for SNAPSHOT:
OW28059 SMS Base support for BACKUP and VERSIONING
OW27857 SMS Storage Class support for BACKUP and VERSIONING
OW27860 ISMF user support for BACKUP and VERSIONING
OW28561 SMS Storage Class support for BACKUP and VERSIONING
OW31819 New Function support for ACCESSIBILITY BACKUP and VERSIONING

References:

IBM Redbook
Title: Implementing DFSMSdss SNAPSHOT
Document Number: SG24-5268-00

Title: DFSMS/MVS V1R5 DFSMSdss Storage Administration Reference
Document Number: SC26-4929-04

3.1.20.6 Explanation of COPY Command Keywords
3.1.23.5 Explanation of DUMP Command Keywords

   CONCURRENT
If the source volume is an RAMAC VIRTUAL ARRAY and CONCURRENT is specified, DFSMSdss uses the SNAPSHOT capability of the RVA to provide a function equivalent to concurrent copy. This function is called concurrent copy-compatible SNAPSHOT and is transparent to the user.

Note: IBM - RAMAC VIRTUAL ARRAY (RVA)
StorageTek - SHARED VIRTUAL ARRAY (SVA)

kw 03/23/00 created

Previously Published As
91085

Change History
Date: 2007-10-05

Attachments

This solution has no attachment