dlm v2.1 z/os implementation guide...including emc proven professional certification dlm v2.1 z/os...

Including EMC Proven™ Professional Certification

DLm V2.1 z/OS Implementation Guide

EMC Proven Professional Knowledge Sharing 2009

Mike Smialek, Sr. Solutions Architect [email protected] 412-809-5526

EMC SA & IS Personnel

Major Contributors:John CiraulaJohn MooreGary MorseNick PattisonJim Stout

mailto:Smialek_Mike%40emc.com?subject=

EMC Corporation, Technology Solutions DLm z/OS Implementation Guide

DLm z/OS Implementation Guide Page ii

Record of Revisions

The following is a list of revisions made to this document:

Rev Date Pages Affected Reason Summary of Technical Changes

1.0 2-16-09 All Initial document release.

1.1 2-22-09 All Expand upon examples

2.1 1-28-10 All V2.1 Update all sections with V2.1 information


DLm z/OS Implementation Guide Page iii

Table of Contents

Introduction.............................................................................................................................1

Purpose and Scope............................................................................................................................ 1

Audience and Prerequisites ............................................................................................................. 1

Reference Documentation and Resources ...................................................................................... 1

1 Background DLm Information ............................................................................................2

1. DLm Software .............................................................................................................................. 2

2. Terminology ................................................................................................................................. 2

3. DLm Facts Summary .................................................................................................................. 3

4. Hardware Summary.................................................................................................................... 3

5. z/OS Input Data for Configuring DLm ..................................................................................... 4

6 Example Solution Set.........................................................................................................5

6. Example Solution......................................................................................................................... 5

7. z/OS Options for Tape Allocation (Provided by Gary Morse) ................................................ 5

8. z/OS Tape Allocation Code ......................................................................................................... 6

9. z/OS Tape Operational Flow (Provided by John Moore) ....................................................... 8

10. Strategy for Configuring VTEs ................................................................................................ 9

11. Network Data for DLm Configuration.................................................................................. 11

12 Logon and Installation ...................................................................................................12

12. Using PuTTY and TightVNC (Contributed by Gary Morse) ............................................. 12

13. DLm Implementation Toolkit V2.1........................................................................................ 17

14 Operational Considerations............................................................................................21

14. Event Monitoring..................................................................................................................... 21

15. Changing Passwords and /dlm-keys Script ........................................................................... 23

16. Reading a Non-Cataloged Tape.............................................................................................. 24

17. VTE Displays............................................................................................................................ 24

18. DLm Logs ................................................................................................................................. 26

19 Modifying File Systems...................................................................................................26

19.1 Overview.................................................................................................................................. 26

19.2 Extending File Systems........................................................................................................... 26

19.3 Add File Systems to the Library............................................................................................ 26 19.4 Create a New File System...................................................................................................................................26

19.5 Export the NFS Exports......................................................................................................................................27

19.6 Mount New File Systems to VTEs.......................................................................................................................27


DLm z/OS Implementation Guide Page iv

19.7 Initialize Virtual Tapes .......................................................................................................................................28

19.8 Recycle VTE .......................................................................................................................................................28

19.9 Replication............................................................................................................................... 29

20 DLm Reports and Utilities...............................................................................................29

20.1 Overview.................................................................................................................................. 29

20.2 Script 501 Command Processing Facility............................................................................ 29 20.2.1 query config .....................................................................................................................................................29

20.2.2 query config .....................................................................................................................................................31

20.2.3 query paths assigned .......................................................................................................................................33

20.2.4 show channel paths..........................................................................................................................................34

20.3 Script 502 Log Copy Utility ................................................................................................... 35

20.4 Script 998 & 999 GENSTATS Reporting............................................................................. 36

20.5 AWSPRINT Utility (Contributed by John Moore) ............................................................. 37

21. DLm Utilities ............................................................................................................................ 39

22 Linux Commands ............................................................................................................41

22. Useful DLm Linux Commands (Provided by Nick Pattison) .............................................. 41


DLm z/OS Implementation Guide Page 1

Introduction

Implementation of a Data Library for mainframe, DLm V2.1 series, requires coordination between multiple system and people resources. These include mainframe tape library system, z/OS operating system software, NAS, and configuration of the DLm ACP and VTE components. If replicating data to another DLm, Celerra Replicator V2.0 is also required. Regardless of your experiences or technical background implementing a DLm solution will require expertise in areas for which you have no knowledge. This Implementation Guide walks through the implementation process defining how to gather required information necessary to configure each component.

Some of the areas covered include:

Summary of DLm120 and DLm960 V2.1 configuration guidelines

DLm Checklist for gathering current customer tape processing information

Required cables, IP addresses and phone numbers

PC software and hardware needed for DLm configuration

z/OS software impacting tape processing including HCD, SMS/ACS, MTL, OAM

Executing DLm Linux scripts to define Tapelibs, NFS mount points and processing options

DLm z/OS utilities DLmSCR, DLmCMD and DLmLIB

Purpose and Scope

There are several fine Corporate documents on DLm. For customers they include Physical Planning Guide, User Guide, Command Processors Users Guide and whitepapers which can be found on Powerlink under the Navigator drop down and selecting “Disk Library Tools”. This document attempts to coordinate the DLm implementation along with the logic necessary to determine what z/OS changes are required? It covers information collected while implementing DLm at customer sites.

Audience and Prerequisites

Because tape processing is critical to a mainframe customer’s production processing, EMC strongly recommends users of this guide have attended formal DLm training. Questions concerning these procedures or problems executing the commands must be handled by opening a software case with the EMC Software Assistance Center (SAC) at 800- 782-4362. Tell them to transfer you to the DLm support group.

Reference Documentation and Resources

Much of the information in this implementation guide is from the following EMC documentation:

Title Reference Number Location

DLm V2.1 Series User Guide P/N 300-009-098 Rev A02 Aug 2009 http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-098.pdf

DLm V2.1 Series Release Notes P/N 300-009-099 Rev A04 Nov 2009 http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-099.pdf

DLm V2.1 Command Processors User Guide

P/N 300-009-622 Rev A01 Aug 2009 http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-622.pdf



1 Background DLm Information

1. DLm Software

DLm (Disk Library mainframe) V1.0 was released March 2008, but the idea was developed in the field as MDL (Mainframe Data Library) starting around 2004. The MDL was comprised of separate Bustech, Celerra and Clariion components combined to provide the mainframe Tape-on-Disk solution. MDL required multiple vendors for support. The Dlm solution combines all of the components into one or more cabinets and is fully supported by EMC. DLm has been enhanced with releases V1.1 September 2008, V1.2 December 2008 and V2.1 October 2009. DLm V2.1 integrates the following software components:

ACP/VTE – SLES (SuSe Linux) 10 SP2

Awsdir – interactive VTE library utility providing the status of tapes in /tapelib

Awsprint – VTE tape library utility for listing the contents of libraries or specific volumes

Celerra Replicator – V2.0

Command Processor 501 – batch mainframe query to VTEs

Command Processor 502 – retrieve VTE logs to mainframe

DART – (Data Access in Real Time) Celerra 5.6.45.5 also called CMR8

FLARE – (Fibre Logic Array Runtime Environment) Clariion CX4 4.28.000.5.706

GENSTATS – DLmZOS.XMI program to produce DLm processing statistics

Implementation Toolkit – Comes with V2.1 contains implementation scripts

PuTTY – software to acess Alias IP Address using a SSH Telnet Shell

http://www.chiark.greenend.org.uk/~sgtatham/putty/

TightVNC – software to remotely access Control Stations and VTEs

http://www.tightvnc.com/download.htm/

VTEC – (Virtual Tape Engine Controller) front-end 6.00-30

WinSCP – Connects to Control Stations for uploading NAS or VTEC code updates or downloading logs or other files to your workstation.

http://winscp.net/eng/download.php

2. Terminology

ACP – Access Control Point, there are two ACP1 and ACP2, not attached to external network BTILOG – Contains all VTE messages at /VAR/bti/btilog, listed with Script 502. CPF – Command Passing Facility also called Script 501 and 502. ConnectEMC – handles DLm dial-home capabilities CS – Control Station, there are two Control Station 0 and Control Station 1 DAE – Disk Array Enclosure (15 1TB drives, RAID6(12+2)+1 Hot Spare, 9.5 TB Usable) Data Exchange – flat file processing DLm – Disk Library for mainframe ESRS – (EMC Secure Remote Services) controls external access to DLm FSTAB – Listing of File System details MIH – Missing Interrupt Handler DLm tape recommendation is 3000 seconds (50 minutes) MTL – Manual Tape Library with ID of 01-20 Hex, 512 maximum devices Storage Controller – also called a Data Mover or Blade, n Active + 1 Hot Spare Tilde – ~ in front of VOLSER means it’s in a scratch status in AWSPRINT listing Truncated Tapes – Expired tapes with just a HDR1 stub, 454 bytes in length Virgin Tapes – Never allocated have a HDR1 = all zeroes and are 184 bytes in length VTE – Virtual Tape Engine minimum 1, maximum 6

http://www.chiark.greenend.org.uk/%7Esgtatham/putty/



Xmap0 – Configuration file for VTEs, can be mutiple Xmaps but only 1 can be active

3. DLm Facts Summary

1. Supports z/OS tape formats 3480, 3490 and 3590 which is classified as MEDIA4

2. Tape Management Systems supported with DLm:

ASG – Zara V1.5 or > (aka Automedia V1.3 or >), CA – TLMS V5.4

BMC – Control-T V6.0 or >, CA – TMS V5.2 (aka CA-1), IBM – RMM z/OS V1.7 or >

3. Messages travel from the VTEs to the ACP, to the Control Stations then externally.

4. DLm does support JES2 AUTOSWITCH allowing multiple processors in a parallel SYSPLEX to share tape drive resources across multiple CPUs. DLm doesn’t support JES3 AUTOSWITCH.

5. ACP = White PC background, VTEs = Blue PC background

6. DLm uses IDRC compression with typical ratios of 1:2.4-1:2.7

7. DLm V2.1 doesn’t currently support encryption, possibly Q4-2010

8. Can attach external 3592/TS1120 compatible drives, 1 per VTE, for exporting to physical tape

9. There is a DLm SVC Qualifier which can be found at http://gig.corp.emc.com

10. Power up sequence = 1) Celerra, 2) ACP, 3) VTEs, 4) Vary DLm tape devices online

11. DLm devices must have an MIH setting in IECIOSxx SYS1.PARMLIB = 50 minutes

Check setting from z/OS: /D IOS MIH,DEV=xxxx (xxxx = DLm tape device UCB)

12. Implementation requires resources from 3 practices:

1) Customer Engineer to power up the DLm

2) NAS person to connect DLm to the network

3) Mainframe SA/IS to configure VTEs to match z/OS definitions

4. Hardware Summary

DLm960 – APM0009380####(2) VTEs, (3) Storage Controllers, (6) DAEs, 57TB, (90) 1TB Drives

Disk Bay VTEC BayNAS Bay

Storage HDAStorage HDA

VTE 1

10Gb Switch ‐ Replication

VTE 2

EMC

ACP 1 – 888‐123‐4567

ACP 2 – 777‐123‐4567

10Gb Switch ‐ Replication

Gig/e 2 Switch ‐ Internal

Gig/e 1 Switch ‐ Internal

Ficon

EMC

CS 1 – 10.130.##.##

555‐123‐4567

Storage Controller 3

Active


Active


Standby

CS 0 – 10.130.##.##

666‐123‐4567

System DAE

EMC

Storage DAE

Storage DAE

Storage DAE

Storage DAE

Storage DAE

Storage DAE

Alias Sign On = 10.130.##.##

http://gig.corp.emc.com/



DLm120 DLm960

Number of VTEs 1 or 2 1 to 6

Host Connectivity 4gb FICON 4 gb FICON

Number of FICON channels 2 to 4 2 to 12

Number of tape drives Up to 512 Up to 1,536

Capacity (usable) 9.5 TB to 47.5 TB 28.5 TB to 1.2 PB

DAEs 1 to 5 2 to 126

Cabinets (7 sq/ft per cabinet) 1 Only 2 to 13

Performance 200/400 MB/s 200 MB/s/1.2GB/s

External Tape Drives (Supports WORM Drives)

FC IBM 3592-J1A,TS1120 or TS11301 per VTE

FC IBM 3592-J1A, TS1120 or TS1130 1 per VTE

Replication Any-to-Any Any-to-Any

Hardware compression IDRC Avg 1:2.5 IDRC Avg 1:2.5

5. z/OS Input Data for Configuring DLm

There’s a lot of data about the customer’s current tape environment you must know to properly configure the DLm solution. Assumption is made the customer will continue to use their current tape processing while they gradually migrate new allocations to DLm. The information you must know:

1. z/OS level and model of processor(s)?

2. JES2 or JES3. Are tape devices managed by JES3, need to update HWSNAME & SETNAMES.

3. Tape Management software CA1-TMS, IBM-RMM, TLMS, Control-T or Zara?

4. Is there one shared tape catalog or many?

5. Does customer use Manual Tape Libraries (MTLs), SMS, OAM address space or UIM?

6. Is customer using STK HSC software to manage tape allocations?

7. Does IBM-GRS or CA-MIM influence tape allocations?

8. Customer using report management products like CA-SAR, Mobius or Systemware?

9. Number and name of all Production, Test and Quality Assurance LPARs

10. Are the LPARs in a SYSPLEX?

11. Does the customer share tapes between Production, Test and QA?

12. How many tape drives and tape volumes are needed for Production, Test and QA?

13. IOCDS or HCD reports for all 3480, 3490 and 3590 tape devices

14. What UCB address ranges will be used for DLm?

15. CHPID assignments from host to directors and directors to DLm?

16. Listing of all Esoterics used

17. Desired default tape size for DLm?



18. Will DLm data be replicated, if so which data and target DLm(s)?

19. How does customer want to handle DR testing?

20. Will customer migrate tapes with IDP-FATSCOPY, CA-COPYCAT or OpenTech-Tape/Copy?

6 Example Solution Set

6. Example Solution

In the following sections, we will use this example solution for completing DLm, z/OS and software parameter listings.

7. z/OS Options for Tape Allocation (Provided by Gary Morse)

One of the first configuration tasks is to determine how the customer will control z/OS tape allocations from z/OS? This will probably depend on how the customer does tape allocation today, and what software they will have available for use with the DLm. In most cases, the customer will want to gradually migrate tapes to the DLm while still doing allocations to their existing VTS for example. This means if z/OS is currently allocating 3590 tape devices to the VTS and you also want to allocate a specific group of 3590



tapes to the DLm, some piece of software has to determine which 3590 allocations remain on the VTS and which go to the DLm? This is where a decision has to be made, how to control tape allocations between existing and DLm tape devices. To help with the decision process, a dichotomous key was developed to walk you down the decision path. As you can see there are several ways to handle tape allocations but which one is the right choice? Details about choices are in the following sections. Do you have a real tape device, other than 3480, available? Fits when all current tape devices are 3480, and all new tape devices on DLm will be 3590. Yes, use that device type (3490 or 3590) for DLm tape allocations. No Does customer use STK HSC and will the software remain after DLm is active? Fits if customer is going to keep using STK HSC? Yes, use UNITATTR, VOLATTR, and TAPEREQ statements to manage tape allocations No Is the customer a JES3 site? Yes, define JES3 INISH parms SETNAME & HWSNAME to manage tape allocations No Popular Choice Is customer running SMS/ACS code to select tape storage class? Yes, define Manual Tape Library (MTL) in HCD, Need OAM (Object Access Method) address space, create TCDB (Tape Configuration Database) with DLMLIB utility No Use EMC UIM limited to 3480 only, doesn’t work with HSM or OAM No Use High/Low order UCB definitions, Example, UCBs 2000-2400 = VTS, 2500-2900 = DLm.

8. z/OS Tape Allocation Code

To help understand the tape allocation process, the following contain some examples of the necessary code depending upon your choice for implementation.

1. STK HSC

In the following example, a technique used to make the DLm tape devices unique is to define them as helical drives (MODEL(SD3) and MEDIA(DD3B)). We are selecting tapes for allocation to the DLm based upon DSN TSOID1.TEST.DLm.**. You can also select based upon JOBNAME, STEPNAME, PGMNAME DD statement or a combination of requirements. The tape devices are defined as 3490 in the HCD.

See HSC Programmer’s Guide for more details: http://dlc.sun.com/pdf/CRCM1781/CRCM1781.pdf

/*-- DLm DRIVE ADDRESSES ONLY USED ON PRODUCTION */ /*-- DLm DRIVE ADDRESSES --------- 120 DRIVES ------------------*/ UNITATTR ADDR(0610-065F) MODEL(SD3) ----------------------------------------------------------------------- ** VOLV00 ** VOLATTR SERIAL(V00000-V49999) MEDIA(DD3B) REC(HELICAL) ------------------------------------------------------------------------ ** TREQ00 **



/* CHANGE LOG */ /* 10.07.2008 ADDED DEFINITIONS FOR PROD DLm VALIDATION */ /* -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- */ /* DLm DEFINITIONS -- -- -- -- -- -- -- -- -- -- -- -- */ TAPEREQ DSN(TSOID1.TEST.DLM.**) MEDIA(DD3B) REC(HELICAL) TAPEREQ DSN(TSOID2.TEST.DLM.**) MEDIA(DD3B) REC(HELICAL) /* -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- */

2. JES3 INISH parameters HWSNAME and SETNAMES are used to control tape allocations. In the following example, the new 3590 devices in RED are for the DLm.

* DEFINE SETNAME FOR TAPE DRIVES * SETNAME,XTYPE=VTAPE,NAMES=(LDGW3495,LDG11111,LDG3591,LDB11111) SETNAME,XTYPE=OUTSIDE,NAMES=(3490OUT,TAPEOUT,SYS348XR,SYS3480R,3490) SETNAME,XTYPE=CARTT090,NAMES=(3490,CART,SILO,SYS3480R,SYS348XR,TIMBER) * * DEFINE HIGH WATERMARK SETUP NAMES FOR TAPE DRIVES * HWSNAME,TYPE=(3490OUT,TAPEOUT,SYS348XR,SYS3480R,3490) HWSNAME,TYPE=(TAPEOUT,3490OUT,SYS348XR,SYS3480R,3490) HWSNAME,TYPE=(CART,SILO,3490,TIMBER) HWSNAME,TYPE=(3490,SILO,TIMBER) HWSNAME,TYPE=(SILO,TIMBER) HWSNAME,TYPE=(TIMBER) HWSNAME,TYPE=(SYS3480R) HWSNAME,TYPE=(SYS348XR) HWSNAME,TYPE=(LDGW3495,LDG11111,LDG3591,LDB11111) HWSNAME,TYPE=(LDG3591,LDB11111) HWSNAME,TYPE=(LDG11111,LDB11111)

3. SMS/ACS Routines for Storage Class

FILTLIST VTAPEJOB INCLUDE(DLM*) FILTLIST VTAPEUNT INCLUDE('VTAPE') WHEN (&ANYVOL EQ 'REF=ST' OR &ALLVOL EQ 'REF=ST') SET &STORCLAS = 'TLIB1SC’ WHEN (&UNIT EQ 'AFF=SMST') SET &STORCLAS = 'TLIB1SC’ WHEN ((&JOB = &VTAPEJOB) && (&UNIT = &VTAPEUNT)) SET &STORCLAS = 'TLIB1SC’

4. MTL (Manual Tape Library) and ESOTERIC Definitions

0200,16 3590 OFFLINE=NO,DYNAMIC=YES,LOCANY=YES, LIBRARY=NO,AUTOSWITCH=NO,LIBRARY-ID=111111, LIBPORT-ID=01,MTL=YES 0210,16 3590 OFFLINE=NO,DYNAMIC=YES,LOCANY=YES, LIBRARY=NO,AUTOSWITCH=NO,LIBRARY-ID=111111, LIBPORT-ID=02,MTL=YES

(Continue with definition of 0220-0270 devices)



AFFINITY ALLOCATION ASSOCIATED NAME NAME TYPE VIO TOKEN PREF INDEX DEVICE TYPE GENERICS DEVICE NUMBER LIST 3590-1 GENERIC 950 0400 78048083 0200- 027F LDB11111 ESOTERIC 950 0400 78048083 3590-1 0200- 027F LDGW3495 ESOTERIC 950 0400 78048083 3590-1 0200- 027F LDG11111 ESOTERIC 950 0400 78048083 3590-1 0200- 027F LDG3591 ESOTERIC 950 0400 78048083 3590-1 0200- 027F VTAPE ESOTERIC 950 0400 78048083 3590-1 0200- 027F

9. z/OS Tape Operational Flow (Provided by John Moore)

From a high-level, the z/OS information flows from top to bottom. There are many z/OS components, all working together, needed to provide the desired solution.

HCD

TAPE DEVICE

TM VOLSERS

CHANNEL

VTEC

CONFIGURATION

TAPELIB*

TAPE DEVICE

STORAGE

Basic DLM Tape Operational Flow

HCD MTL

FiCON

ESCON

SMS/OAM

Tape Management

HSCCA-MIM

CELERRA Storage CELERRA

Replication

Current TapeDevices

Number OfLPARS

Special Tape Processing

VTEC Application

VTEC Firmware

Mount PointsFile Shares

JES3

VTEC CONFIG Options

Number OfCPUS

Some or several of these z/OS components require definitions to support the DLm. These definitions must match the VTE definitions on the DLm. The following steps assume we are using SMS/ACS routines and a MTL to control tape allocations: 1) Add the new tape volsers to the tape catalog (RMM, CA-1 etc)

100,000 volsers for normal tape processing = V00000 - V99999 20,000 volsers for DRTEST = VA0000 – VB9999

2) MTL - define MTL for production(LibraryID=11111) 3) Define OAM (Object Access Method) address space 4) Add VOLSERs to MTL creating TCDB using DLMLIB utility – see code example under DLMLIB 5) Create new tape esoteric ???? = determine if new esoteric is required? Update IOGEN Update JES3 INISH parms if applicable



6) Update SMS, create a tape storage group 7) Update HSM parms to direct backup and migration to the DLm. 8) RACF profiles if needed.

10. Strategy for Configuring VTEs

In the following example, our Target DLm has (10 = v0-v9, x 10,000 VolSers each = 100,000 VolSers V00000-V99999) Read Only production File Systems of 5 TB each. DR Testing has (2 = vA & vB, x 10,000 VolSers each = 20,000 VolSers VA0001-VB9999) Read/Write File Systems of 3.5 TB each. Notice the tapelib’s alternate between Storage Controller (aka server) 2 and 3. The DLm has absolutely no influence on the tape allocation. By default, z/OS will randomly spread the tape allocations across all of the file systems.

Example File System Layout for Target DLm

Storage Controllers 2 & 3 Active

Data Mover

File System Size in GB

DM IP Address

Mounted NFS Mount Points for XMAP0

server_2 tapelib1_V0 5000 10.224.82.11 tapelib1/V0 /tapelib1/v0 Read Only





server_2 tapelib1_VA 3500 10.224.82.11 tapelib1/VA /tapelib1/vA Read/Write

28500






server_3 tapelib1_VB 3500 10.224.82.12 tapelib1/VB /tapelib1/vB Read/Write

28500

Total 57 TB

The tape drive IOCDS statements to accompany our File Systems. In our example we have (4) FICON CHPIDs B2, B3, B4 and B5. VTE1 is using UCB addresses 0200-023F and VTE2 0240-027F. CHPID PATH=(CSS(0),B2),SHARED,PARTITION=((TST2,TST3),(TST1)), * PCHID=1B2,TYPE=FC CHPID PATH=(CSS(0),B3),SHARED,PARTITION=((TST2,TST3),(TST1)), * PCHID=1B3,TYPE=FC CHPID PATH=(CSS(0),B4),SHARED,PARTITION=((TST2,TST3),(TST1)), *



PCHID=1B4,TYPE=FC CHPID PATH=(CSS(0),B5),SHARED,PARTITION=((TST2,TST3),(TST1)), * PCHID=1B5,TYPE=FC * VTE1 0200 - 023F CNTLUNIT CUNUMBR=0200,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=0,DESC='DLm VTE1',UNIT=3590 IODEVICE ADDRESS=(0200,16),UNITADD=00,CUNUMBR=(0200),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE1',UNIT=3590 CNTLUNIT CUNUMBR=0210,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=1,DESC='DLm VTE1',UNIT=3590 IODEVICE ADDRESS=(0210,16),UNITADD=00,CUNUMBR=(0210),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE1',UNIT=3590 CNTLUNIT CUNUMBR=0220,PATH=((CSS(0),B2,B3)), * UNITADD=((00,16)),CUADD=2,DESC='DLm VTE1',UNIT=3590 IODEVICE ADDRESS=(0220,16),UNITADD=00,CUNUMBR=(0220),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE1',UNIT=3590 CNTLUNIT CUNUMBR=0230,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=3,DESC='DLm VTE1',UNIT=3590 IODEVICE ADDRESS=(0230,16),UNITADD=00,CUNUMBR=(0230),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE1',UNIT=3590 * VTE2 0240 - 027F CNTLUNIT CUNUMBR=0240,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=0,DESC='DLm VTE2',UNIT=3590 IODEVICE ADDRESS=(0240,16),UNITADD=00,CUNUMBR=(0240),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE2',UNIT=3590 CNTLUNIT CUNUMBR=0250,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=1,DESC='DLm VTE2',UNIT=3590 IODEVICE ADDRESS=(0250,16),UNITADD=00,CUNUMBR=(0250),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE2',UNIT=3590 CNTLUNIT CUNUMBR=0260,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=2,DESC='DLm VTE2',UNIT=3590 IODEVICE ADDRESS=(0260,16),UNITADD=00,CUNUMBR=(0260),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE2',UNIT=3590 CNTLUNIT CUNUMBR=0270,PATH=((CSS(0),B2,B3,B4,B5)), * UNITADD=((00,16)),CUADD=3,DESC='DLm VTE2',UNIT=3590 IODEVICE ADDRESS=(0270,16),UNITADD=00,CUNUMBR=(0270),STADET=Y,* PARTITION=((CSS(0),TST2,TST3)),DESC='DLm VTE2',UNIT=3590



The (4) FICON CHPIDs B2, B3, B4 and B5 connectivity to VTE1 and VTE2.

SYS1 SYS4IBM 2097-E12

B2 B3 B4 B5

SYS5

30230/16

20220/16

10210/16

00200/16

CUADDDevice Range

0

VTE #1 VTE #2

3C

30270/16

20260/16

10250/16

00240/16

CUADDDevice Range

0 1 1

11. Network Data for DLm Configuration

Working with the customer, you need to define the IP addresses, modem phone lines and cables required for the DLm. A summary for the DLm960 follows: DLm960 Equipment Delivered: (2) VTEs, (3) Storage Controllers, (6) DAEs, 57 TB, (90) 1TB SATA Drives (1) DLm960 for Source and (1) DLm960 for Target

Following Specifications Per Site Power Drops Single-Phase: (6) in our case - (2) for NAS Bay, (2) for VTEC Bay, (2) Storage Bay 11 Cables - (All copper Gigabit Ethernet): (2) Network cables for Control Station 0 and Control Station 1 (2) Internal Network cables for ACP1 and ACP2 (8) Network cables for replication (4 for production and 4 for backup) 7 IP Addresses: (3) IP Addresses for NAS Control Station 0 and 1, plus an Alias (2) IP Address for the ACP1 and ACP2 (3) IP Addresses for Storage Controllers 2, 3, 4 Phone Lines: (4) Phone lines for ACP1 and ACP2, Control Stations 0 and 1 FICON Cables: (4) FICON cables 30 meters long with LC connectors, Singlemode yellow 9 micron

Once the IP Addresses and phone numbers are collected, build a spreadsheet like following to summarize the details. In this Target, Storage Controllers 2 & 3 are active and 4 is in standby.



Device TypePhysical Device

Device Cable Name Port Speed IP Address Subnet MaskGateway Address

VLAN#ZB:Port

BBR3/PP26Switch Card/Port Comments

ACP N/R N/R N/R N/R N/R N/R N/R N/R N/R N/R Internal connected to Control StationsControl Station 0 eth3 DLMDRH1-CS0 10.228.82.151 255.255.255.0 10.228.82.1 218 ZB3:2 SA2DR1 2:1

DLMDRH1-CS1 10.228.82.152 255.255.255.0 10.228.82.1 218 ZB3:3 SA2DR1 3:110.228.82.153 255.255.255.0 10.228.82.1

DLMDRH1-DM2-1 10.228.82.11 255.255.255.0 10.228.82.1 218 ZB3:4 SA1DR1 2:2DLMDRH1-DM2-2 218 ZB3:5 SA1DR1 2:3DLMDRH1-DM3-1 10.228.82.12 255.255.255.0 10.228.82.1 218 ZB3:6 SA2DR1 2:2DLMDRH1-DM3-2 218 ZB3:7 SA2DR1 2:3DLMDRH1-DM4-1 218 ZB3:8 SA1DR1 3:2DLMDRH1-DM4-2 218 ZB3:9 SA1DR1 3:3

WDCDRH1 WDCDRH2

10.62.37.100 10.62.37.18

WDCDRH1 WDCDRH2

10.62.37.100 10.62.37.18

555-665-4008555-665-4009555-665-4971555-665-4973

1000/Full Mgt use onlyControl Station 1 eth3 1000/Full Mgt use onlyControl Station Alias N/R N/R N/R N/R N/R N/R N/R Used to Alias CS0 and CS1 togetherData Mover 2 cge2 1000/Full Active Replication PathData Mover 2 cge5 1000/Full N/R N/R N/R Standby Replication Path Data Mover 3 cge2 1000/Full Active Replication PathData Mover 3 cge5 1000/Full N/R N/R N/R Standby Replication Path Data Mover 4 cge2 1000/Full N/R N/R N/R Standby Data Path Data Mover 4 cge5 1000/Full N/R N/R N/R Standby Data Path

NTP Server DNS Server 1 DNS Server 2

Number CHPID PIDB2 1B2B3 1B3B4 1B4B5 1B5

Target - DLm4080 Network ConnectivityStorage Controllers 2 & 3 Active, 4 in Standby

Other Required Network InformationNetwork Object DNS Domain Name

Modem InformationDevice

Control Station 0

Fiber info

ACP 1

Control Station 0Control Station 1

Control Station 1

ACP 2

WDCDRH1.ACME.COM WDCDRH2.ACME.COM

WDCDRH1.ACME.COM WDCDRH2.ACME.COM

12 Logon and Installation

12. Using PuTTY and TightVNC (Contributed by Gary Morse)

Access to the DLm VTE’s is accomplished through a software program called PuTTY using the Alias Control Station IP Address. PuTTY will connect to ACP1 or ACP2 using TightVNC software creating a secure SSH Tunnel connection to the DLm internal Celerra Network. Access to the VTEs can also be accomplished through PuTTY and a Web Browser.

The following instructions assume you are on the customer’s network.

1. Start Putty configuration panel



2. Select SESSION

a. Type DLM PGH in the Saved Session box b. Type the ALIAS IP ADDRESS for the DLm in Pittsburgh 10.130.36.16 c. Click on Save

2. Highlight the DLM PGH session and click LOAD. 3. Select Tunnels from Category column on left side

4. Type the internal IP Addresses for the Celerra Network:



a. ACP1 Web Browser = 5801 in the Source port box and 128.221.252.40:5801 in the destination box

b. Click on ADD button c. ACP2 Web Browser = 5802 in the Source port box and 128.221.252.41:5801 in the

destination box d. Click on ADD button e. ACP1 VNC =5901 in the Source port box and 128.221.252.40:5901 in the destination

box f. Click on ADD button g. ACP2 VNC = 5902 in the Source port box and 128.221.252.41:5901 in the destination

box h. Click on ADD button

5. Return to Session panel and Click Save. 6. Click LOAD 7. Click OPEN 8. Login in as nasadmin 9. Password is nasadmin

10. Minimize this window, do not close. 11. Start VNC Viewer



12. Type in localhost:1 13. Click OK

14. Password: is password 15. First window is the ACP which has a white background

16. You are now in the ACP

17. Alternate access method through Internet explorer

a. First start PUTTY session as described above.

b. Start explorer session and type http://localhost:5801 or http://127.0.0.1:5801 in the URL address.

http://localhost:5801/

http://127.0.0.1:5801/



c. You may have to install SunJava Runtime environment.

d. Click Run Advertised Programs and select SunJava and click run to install on your computer

e. Type password, click Ok



f. Click on VTE1 or VTE2 Desktop to bring up the administrative panels.

13. DLm Implementation Toolkit V2.1

The Implementation toolkit is a set of scripts which collects configuration information from the customer and then does the DLm implementation setup based on the information provided. The toolkit configures various system parameters like:

IP addresses and IP alias for Control Stations NTP configuration DNS configuration Time zone configuration File system configuration ConnectEMC and call home configuration Replication setup

Download the Implementation Toolkit and dlm_storage_setup tool from //Powerlink.EMC.com>Navigator>Disk Library Tools>Software Downloads to a thumb drive. The ToolKit contains the following executable scripts:

Title Reference Number

dlm_keys Setup the public keys across primary Control Station 0 & 1 and ACP 1 & 2.

dlm_version Displays version for DLm Tools, Flare, DART, Celerra. Also displays Clariion model number and VTE software version.

dlm_config Records system information like IP addresses collected on the worksheets during installation planning. This script makes no changes to the system and can be run multiple times.

dlm_setup Configures the DLm according to the information collected by the dlm_config script.

dlm_install_cmdproc Installs the DLm Command Processors on VTEs.

Execute Setup Scripts



Step Description Status 1 Initial Control Station Power-On

When booting the Control Stations, you may be prompted to use CSA (Celerra Setup Assistant). Don’t use CSA because it’s not compatible with DLm. To exit CSA use the CTRL-L key combination and procede to the DLm setup scripts.

2 Copying Toolkit software to Control Station 0 Open the Tight-VNC utility and type in 192.168.200.1:1 or Open up Web Browser and type in http://192.168.200.1:5801/ Log in to CS 0 as root, type in the password of “password” to connect. Put thumb drive with Toolkit software in CS 0 USB port and enter: mount /opt/DLm cp /media/usbdisk/impl_tool.tgz /home/nasadmin/ cd /home/nasadmin/ tar –xzf impl_tool.tgz cd ImplementationTools/ cp –Rpf * /opt/DLm/implementation

3 Celerra ConnectEMC DART Patch Enter the following command: rpm –ivh connectemcpatch-0.0.2-1.i386.rpm

4 Execute dlm_keys script for CS 0, CS 1, ACP1 and ACP2 From CS 0 for distribution to CS 1, ACP1 and ACP2: cd /opt/DLm/implementation ./dlm_keys –cs From CS 0 log into CS 1 and distribute to CS 0, ACP1 and ACP2: ssh emcnasotherCS_i0 cd /opt/DLm/implementation ./dlm_keys –cs exit From CS 0 copy to ACP1 and distribute to CS 0, CS 1 and ACP2: scp /opt/DLm/implementation/dlm_keys [email protected]: /tmp ssh 128.221.252.40 cd /tmp ./dlm_keys –acp exit From CS 0 copy to ACP2 and distribute to CS 0, CS 1 and ACP1: scp /opt/DLm/implementation/dlm_keys [email protected]: /tmp ssh 128.221.252.41 cd /tmp

http://192.168.200.1:5801/

mailto:[email protected]

mailto:[email protected]



./dlm_keys –acp exit

5 Execute dlm_storage_setup Tool This script is required if you have more than 4 DAEs (1 System + 3 Storage). Expect run time of 30 minutes per 12 DAEs. For best results, completely logoff CS 0 and log back in as root. The script will ask if you want to execute the background verify. For the initial configuration, you don’t want to run the BV process. Put thumb drive with the setup software in CS 0 USB port and enter: mount /media/usbdisk cp /media/usbdisk/add_storage.tgz /home/nasadmin/ cd /home/nasadmin/ tar –xzf add_storage.tgz cd /home/nasadmin/DLmAddStorage cp –Rpf * /opt/DLm/mfg cd / unmount /media/usbdisk cd /opt/DLm/mfg ./dlm_storage_setup –add_dae

6 Execute dlm_config script dlm_config collects information you enter and stores it in a configuration file for input to dlm_setup script in the next step. dlm_config can be executed multiple times and creates a log file at /opt/DLm/implementation/log directory/dlm_config_SystemID.log.1 This is where you need the Configuration Worksheet with all of the IP addresses, DNS names and file system information. Enter the following commands to start: cd /opt/DLm/implementation ./dlm_config

7 Execute dlm_setup script Configures the Celerra using parameters specified while executing the dlm_config script. If you don’t have all the information yet, like IP addresses, the ALL flag may not perform all of the necessary configurations. In this case you have to execute dlm_setup with specific flags set like –bv (CLARiion background verification), -update_motd (update Message of the Day file), and –update_syr_xml (update DLm version # in /nas/var/log/syr_dlm.xml). ./dlm_setup ALL



./dlm_setup –bv –update_motd –update_syr_xml The bv flag will prompt you for the priority of the background verification. Select ASAP since this is a new install with no production workload.

8 Install Command Processors (CPF) Executed from the Control Station, ./dlm_install_cmdproc including with the Implementation Toolkit, copies the 501 and 502 CPF scripts to the VTEs. mount /media/usbdisk cp /media/usbdisk/DLmCommandProcessors.tgz /home/nasadmin/ cd /home/nasadmin/ tar –xzf DLmCommandProcessors.tgz cd /home/nasadmin/ DLmCommandProcessors cp –Rpf * /opt/DLm/implementation cd / unmount /media/usbdisk (Copy DLmCommandProcessors.tgz to CS 0 root/nasadmin using WinSCP) tar –xzf DLmCommandProcessors.tgz cd DLmCommandProcessors cp –Rpf * /opt/DLm/implementation cd /opt/DLm/implementation ./dlm_install_cmdproc 501 ./dlm_install_cmdproc 502

9 Reboot the Control Stations Log on CS 0 as root/nasadmin /nas/sbin/t2reset pwroff –s 1 (This command powers down CS 1) reboot (Reboot CS 0, wait 10 minutes for completion) /nas/sbin/t2reset pwron –s 1 (Power on CS 1) Want to make sure CS 0 is the primary Control Station. /nas/sbin/getreason Should get display as follows: slot_0 primary control station (Means CS 0 is the primary, Okay) slot_1 secondary control station (Means CS 1 is the secondary, Okay) Don’t want the display showing slot_0 is the secondary control station.

10 Collect DLm Information DLm V2.1 introduced a new script called dlm_version which displays the following information:



11 Configure Celerra ConnectEMC ConnectEMC sends error messages using Email, FTP or modem. Log in the Celerra Manager as root. Select Celerra>”name”>Support>ConnectHome Select the primary and tertiary delivery methods

14 Operational Considerations

14. Event Monitoring

1 Message Generation There are 3 resources which will generate event notices:

1) The DLm batch utilities will send messages to the z/OS console like any executing batch program. Messages are prefixed DLC* (DLMCMD), DLL* (DLMLIB) and DLS* (DLMSCR).

2) The Celerra Storage Controller will generate SNMP alerts which can be routed to monitoring tool like HP Openview. Follow the procedures in the “Configuring EMC Celerra Events and Notification” manual for how to route the alerts.

3) The VTE’s can also generate SNMP alerts which are listed in the “DLm V2.1 Series User Guide” Appendix G. There are 430 potential messages categorized at 3 levels (241) DLM###E, (62) DLM###W and (127) DLM###I. By default, the SNMP alerts will be in the /VAR/bti/btilog but will not generate SNMP traps.

2 Procedures to trigger VTE SNMP Alerts Putty to the DLm Control Station, minimize window Start VNC Viewer to gain access to the ACP Click VTE1 Double-click Configure Devices for VTE1 (screen CFG000) Click on Configure Devices (screen CFG100) Click on View or Modify xmap0 (screen CFG200) Click on SNMP Tracing (screen CFG400) Next to SNMP Agent, change Trap Level to 3 for all E, W and I messages



Enter Manager IP for the monitoring server like HP Openview Scroll down and click on Submit Changes, exit screen Make sure the change is reflected on the CFG200 screen Repeat for VTE 2

3 Install SNMP MIB and Agent From //Powerlink.EMC.com>Navigator>Disk Library Tools>Software Downloads get the SNMP MIB and Agent EMC-DLM-MIB-2.x.txt and EMC-DLM-AGENT-MIB-2.x.txt. Install on SNMP monitoring server



15. Changing Passwords and /dlm-keys Script

Default password for the ACPs/VTEs is “password”, for Celerra “nasadmin”. Recommendation is to keep default passwords until the DLm implementation is completed. To change passwords for the CLARiiON use nas_storage command and dlm_keys tool to distribute new passwords between Celerra Control Stations and ACPs. The /dlm_keys script must be executed from all Control Stations and all ACPs.

Action Description

Change Password

**must be done as root**

[nasadmin@ns20salescs ~]$ /nas/bin/nas_storage

| ‐modify { <name> | id=<storage_id> } ‐security

[‐username <username>] [‐password <password>]

[‐newpassword [<new‐password>]]

[nasadmin@ns20salescs ~]$ /nas/bin/nas_storage ‐list

id acl name serial_number

1 0 APM0009380#### APM0009380####

[nasadmin@ns20salescs ~]$ /nas/bin/nas_storage ‐modify APM0009380#### ‐security ‐username nasadmin ‐password nasadmin ‐newpassword fred

CS 0

To execute the tool from CS 0, log in to CS 0 and type: cd /opt/DLm/implementation

./dlm_keys -cs

This distributes the passwords from CS 0 to CS 1, ACP1, and ACP2.

CS 1 Log in to CS 1 from CS 0 by typing: ssh emcnasotherCS_i0

Execute the tool by typing: cd /opt/DLm/implementation

./dlm_keys -cs

exit

This distributes the passwords from the CS 1 to CS 0, ACP1, and ACP2.

ACP 1 To distribute the passwords from ACP1 to CS 0, CS 1, and ACP2:

Copy dlm_keys from the /opt/DLm/implementation directory to the /tmp directory on ACP by typing: scp /opt/DLm/implementation/dlm_keys [email protected]:/tmp

Execute the tool by typing: ssh 128.221.252.40

cd /tmp

./dlm_keys -acp

Exit

ACP 2 To distribute the passwords from ACP2 to CS 0, CS 1, and ACP1.

Copy dlm_keys from the /opt/DLm/implementation directory to the /tmp directory on ACP by typing: scp /opt/DLm/implementation/dlm_keys [email protected]:/tmp

Execute the tool by typing: ssh 128.221.252.41

cd /tmp

./dlm_keys -acp

Exit

mailto:[email protected]:/tmp



16. Reading a Non-Cataloged Tape

If the tape you wish to process is not in the catalog, you must BLP and provide the VOLSER, DCB and UNIT Esoteric.

1 //TDLMJOBX JOB (001,512,000),'READ BLP TAPE',CLASS=A, // MSGCLASS=Q,MSGLEVEL=(1,1),NOTIFY=&SYSUID /*JOBPARM S=SYS4 2 //STEP01 EXEC PGM=IEBGENER 3 //SYSPRINT DD SYSOUT=* 4 //SYSIN DD DUMMY 5 //SYSUT1 DD DSN=, // DISP=(OLD,KEEP), // LABEL=(2,BLP,EXPDT=98000),VOL=SER=V00056, // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120), // UNIT=VTAPE 6 //SYSUT2 DD SYSOUT=* //*

17. VTE Displays

There are two VTE displays which will help to verify your configuration and provide documentation:

1. FSTAB – provides listing of statements defining each TapeLib: 192.168.200.102:/tapelib1_V0 /tapelib1/V0 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.102:/tapelib1_V1 /tapelib1/V1 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.102:/tapelib1_V2 /tapelib1/V2 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.102:/tapelib1_V3 /tapelib1/V3 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.103:/tapelib1_V4 /tapelib1/V4 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.103:/tapelib1_V5 /tapelib1/V5 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.103:/tapelib1_V6 /tapelib1/V6 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.104:/tapelib1_V7 /tapelib1/V7 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.104:/tapelib1_V8 /tapelib1/V8 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 192.168.200.104:/tapelib1_V9 /tapelib1/V9 nfs rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg

2. VTE1 XMAP0 – listing of tape drive UCBs. Following our example VTE1 has (64) 3590 tape drives in

the 0200 - 023F range with a default size of 20gb. VTE2 would be the same except for UCBs 0240-

027F. # /etc/bti/xmap0 # # Configuration File # USERNAME xmap0 DESCRIPTION Configuration 0 TRACELEVEL 1 FWPATHTRACE 0 SNMPMESSAGELEVEL 0 WARNINGPERCENT 75 RECOVERYPERCENT 95 RECOVERYAMT 1 IMPORTEXPORT NO SCRATCHNAMES SCRTCH SCRATCHNAMES PRIVAT HOSTCOMMAND YES RUNCOMMAND YES # #Begin Device Information



# [DEVICE] ACTIVE=1 INDEX=00 NAME=0200 TYPE=3590 UNIT=00 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=01 NAME=0201 TYPE=3590 UNIT=01 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=02 NAME=0202 TYPE=3590 UNIT=02 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=03 NAME=0203 TYPE=3590 UNIT=03 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=04 NAME=0204 TYPE=3590 UNIT=04 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=05 NAME=0205 TYPE=3590 UNIT=05 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=06 NAME=0206 TYPE=3590 UNIT=06 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=02 NAME=0207 TYPE=3590 UNIT=02 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=08 NAME=0208 TYPE=3590 UNIT=08 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=09 NAME=0209 TYPE=3590 UNIT=09 CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0A NAME=020A TYPE=3590 UNIT=0A CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0B NAME=020B TYPE=3590 UNIT=0B CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0C NAME=020C TYPE=3590 UNIT=0C CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0D NAME=020D TYPE=3590 UNIT=0D CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0E NAME=020E TYPE=3590 UNIT=0E CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=0F NAME=020F TYPE=3590 UNIT=0F CU=00 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=10 NAME=0210 TYPE=3590 UNIT=00 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=11 NAME=0211 TYPE=3590 UNIT=01 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=12 NAME=0212 TYPE=3590 UNIT=02 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=13 NAME=0213 TYPE=3590 UNIT=03 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=14 NAME=0214 TYPE=3590 UNIT=04 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=15 NAME=0215 TYPE=3590 UNIT=05 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=16 NAME=0216 TYPE=3590 UNIT=06 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=17 NAME=0217 TYPE=3590 UNIT=02 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=18 NAME=0218 TYPE=3590 UNIT=08 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=19 NAME=0219 TYPE=3590 UNIT=09 CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1A NAME=021A TYPE=3590 UNIT=0A CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1B NAME=021B TYPE=3590 UNIT=0B CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1C NAME=021C TYPE=3590 UNIT=0C CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1D NAME=021D TYPE=3590 UNIT=0D CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1E NAME=021E TYPE=3590 UNIT=0E CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=1F NAME=021F TYPE=3590 UNIT=0F CU=01 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=20 NAME=0220 TYPE=3590 UNIT=00 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=21 NAME=0221 TYPE=3590 UNIT=01 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=22 NAME=0222 TYPE=3590 UNIT=02 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=23 NAME=0223 TYPE=3590 UNIT=03 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=24 NAME=0224 TYPE=3590 UNIT=04 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=25 NAME=0225 TYPE=3590 UNIT=05 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=26 NAME=0226 TYPE=3590 UNIT=06 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=27 NAME=0227 TYPE=3590 UNIT=02 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=28 NAME=0228 TYPE=3590 UNIT=08 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=29 NAME=0229 TYPE=3590 UNIT=09 CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2A NAME=022A TYPE=3590 UNIT=0A CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2B NAME=022B TYPE=3590 UNIT=0B CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2C NAME=022C TYPE=3590 UNIT=0C CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2D NAME=022D TYPE=3590 UNIT=0D CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2E NAME=022E TYPE=3590 UNIT=0E CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=2F NAME=022F TYPE=3590 UNIT=0F CU=02 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=30 NAME=0230 TYPE=3590 UNIT=00 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=31 NAME=0231 TYPE=3590 UNIT=01 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=32 NAME=0232 TYPE=3590 UNIT=02 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=33 NAME=0233 TYPE=3590 UNIT=03 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=34 NAME=0234 TYPE=3590 UNIT=04 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=35 NAME=0235 TYPE=3590 UNIT=05 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=36 NAME=0236 TYPE=3590 UNIT=06 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=37 NAME=0237 TYPE=3590 UNIT=02 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=38 NAME=0238 TYPE=3590 UNIT=08 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=39 NAME=0239 TYPE=3590 UNIT=09 CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3A NAME=023A TYPE=3590 UNIT=0A CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3B NAME=023B TYPE=3590 UNIT=0B CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3C NAME=023C TYPE=3590 UNIT=0C CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3D NAME=023D TYPE=3590 UNIT=0D CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3E NAME=023E TYPE=3590 UNIT=0E CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G [DEVICE] ACTIVE=1 INDEX=3F NAME=023F TYPE=3590 UNIT=0F CU=03 PATH=/tapelib1 IDRC=YES SIZE=20G



18. DLm Logs

There are three front-end DLm logs which may help with troubleshooting:

1. BTILOG – records all messages directed to the VTEs during runtime.

Location: /var/bti/log

2. “messages” log – all Linux NSF messages including disk or LAN errors coming from device drivers

like port failures, and loading of Channel Card Device Drivers.

Location: /var/log/messages

3. boot.msg log – all events since last boot up including processor detection and device driver loading

messages.

Location: /var/log/boot.msg

19 Modifying File Systems

19.1 Overview

During the process of monitoring the File System metrics it may be determined that either the File Systems need to be extended or additional File Systems need to be added. If additional File Systems are added to the library, they will also need to be mounted to the Connect Nodes and Replication established. Before adding new File Systems, verify Tape Management and DLMSCR scratch processing is working correctly.

19.2 Extending File Systems

As of November 2009, an RPQ is required for planning File System extensions to ensure the added capacity is balanced across the VTEs.

19.3 Add File Systems to the Library

This activity will need to be performed if the production File System Utilization exceeds 85% allocation for Active tapes and the number of Scratch Tapes is below 750 per File System. Extending File Systems will provide additional tape capacity but it doesn’t increase the number of VOLSERs within the File System. You need to watch both File System Utilization and Scratch Volume consumption to monitor growth.

19.4 Create a New File System

To add a new File System, perform the following steps:

Step Action 1 Log into the Control Station responsible for the Data Mover / File System

2 From the Main Menu, click on the File Systems folder.

This will bring up a list of existing File Systems.

3 Click the New button.

4 Enter the name of the new File System, adhering to the naming convention for File Systems in the Logical Tape Library i.e.: tapelibxyz_xx.



5 On the Storage Pool line, make sure the DLm storage pool is selected from the drop-down box.

6 Enter the size of the new File System in MB.

Make sure it’s the same size as the other File Systems contained in the Logical Tape Library.

7 Select the Data Mover from the drop-down box where this new File System is to be mounted.

8 On the Mount Point line, click the custom radio button.

9 Fill in the Pathname following the naming convention for the File Systems in the Logical Tape Library i.e.: /tapelibxyz/xx

10 Click the Apply button

11 Click the OK button

19.5 Export the NFS Exports

The newly-added File System(s) will need to be exported as NFS exports:

Step Action

1 Click on NFS Exports

2 Click the New button

3 Select the Data Mover where the File System is mounted

4 In the NFS Export Options, in the Root Hosts window, specify the subnet of the network.

The subnet is specified as: 10.130.36.0/255.255.255.0. Please reference the latest design documents for the appropriate Data Mover’s subnet and mask. Use the first three octets of the Data Mover’s IP address, leaving the last octet zero (0). This enables access by the entire subnet.

5 Place same subnet in the Access Hosts window using Windows Cut & Paste.

6 Click the OK button

19.6 Mount New File Systems to VTEs

The newly-added File System(s) will now need to be mounted on each of the VTEs requiring access.

Step Action 1 Create Tape Library Mount Points like /tapelibxyz/xx 2 Log into the ACP via the Control Station Alias IP Address 3 Select the first VTE 4 Vary all the drives on this VTE OFFLINE and verify nothing is mounted by issuing

the “q” command from the VTE Application. 5 Right click on the VTE Desktop 6 Select Administrator Shell



7 Enter your Password 8 Type chown –R 88:88 <exported File System name>

The file system name will be in the following format: /tapelibxyz/xx 9 Type exit

10 Right Click on the VTE Desktop again 11 Select NFS Shares 12 Enter Password 13 Click the Add button 14 In the NFS Server Hostname field, enter the IP address of the Data Mover that

has the desired File System exported. 15 Click the Select button 16 From the list which is presented, select the File System to be mounted 17 Click the OK button 18 Fill-in the Mount Point Field. This needs to be in the form of /tapelibxyz/xx 19 In the Options Field, enter the following:

rsize=32768,wsize=32768,hard,intr,tcp,nfsvers=3,bg 20 Click the OK button 21 Click the Finish button. The VTE will now save and refresh the FSTAB, mounting

the new File System. 22 Add the two-digit VOLSER prefix to the appropriate Scratch Synonym Table. 23 Perform Steps 3 to 22 on all the VTEs that will have access to this new File

System.

19.7 Initialize Virtual Tapes

Initialize the “tapes” in the new File System

Step Action 1 Maximize the VTE application window on one of the VTEs 2 Enter the following command: INITIALIZE VOL=<volser> DEV=<cuu>

COUNT=10000 The volser is the first volser in the range to be initialized.

The cuu is a tape drive address that has access to the File System.

The count is the number of volsers to be initialized.

Note: This step only needs to be run once from any one of the VTEs that has access to the new File System.

19.8 Recycle VTE

Recycle the VTE Application on each of the VTEs to make sure the changes are recognized.

Step Action 1 Ensure the Tape Drives are Offline only on the selected VTE 2 Click on the minimized VTE window to open up the VTE’s Desktop. 3 Open the VTE Application on the VTE by clicking on the minimized application. 4 At the Command prompt, enter restart. This will recycle the VTE. 5 When finished (takes about a minute), vary the tape drives online and repeat

Steps 1 to 4 for all the other VTEs in the Logical Tape Library.



19.9 Replication

If the newly-added File Systems are to be replicated to the remote DLm, the following procedures will need to be executed:

Step Action 1 Log into the Control Station where the new File System(s) was created. 2 Select the Replications Folder. 3 Click on the Replications tab. 4 Click New at the bottom of the screen. 5 Select the Replicate a File System radio button 6 Click the Continue button 7 In the Replication Name field, enter the name of the replication.

Use name of the File System being replicated. 8 Select the Source File System from the Drop Down box. 9 From the Checkpoint Storage Pool Drop Down box, select the DLm pool.

10 In the Destination Storage Network Server Drop Down Box, select the target Storage Controller serial number (APM00093######) for this replication session.

11 From the Source Data Mover Interconnect Drop Down Box, select the target Data Mover where you want this File System to be replicated.

12 Make sure the Create Using Storage Pool radio button is selected. 13 Select the DLm storage pool for both the Destination Pool and the

Checkpoint Storage Pool Drop Down Boxes. 14 Your Update Policy should be Time Out Of Sync. 15 The Time Out Of Sync value should be set to 15 minutes. 16 Click the Apply button. Wait for the Replication setup to complete. 17 Click on the Replications Folder and locate the new File System line. Ensure

the Status of the Replication shows OK.

20 DLm Reports and Utilities

20.1 Overview

There are several Scripts which can be submitted on the mainframe, execute commands against the VTEs, and bring the output back to the mainframe.

20.2 Script 501 Command Processing Facility

At least once a day on the data center will run Script 501 which provides command output from the “query space”, “query config”, “query paths assigned” and “show rejected paths”. The query output provides File System Statistics for every File System, grouped by logical tape library. The columns are explained at the end of the display listings.

20.2.1 query config VTE1 VT: DLm409I: Command received: 'query space' VTE1 VT: VTE1 VT: Tape library space for drives: 0200-023F VTE1 VT: VTE1 VT: Path Size Active Scratch / Qty Free Filesystem



VTE1 VT: ---------------- ---- --------- ---------------- --------- ---------- VTE1 VT: /tapelib1 20.1G 0 0% 0 0% 0 18.8G 86% LABEL=root VTE1 VT: /tapelib1/V0 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.102:/tapelib1/V0 VTE1 VT: /tapelib1/V1 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.103:/tapelib1/V1 VTE1 VT: /tapelib1/V2 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.104:/tapelib1/V2 VTE1 VT: /tapelib1/V3 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.102:/tapelib1/V3 VTE1 VT: /tapelib1/V4 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.103:/tapelib1/V4 VTE1 VT: /tapelib1/VA 3.5T 0 0% 2M 0% 10000 3.5T 99% 192.168.200.103:/tapelib1/VA VTE1 VT: ================================================== VTE1 VT: Totals: 32.0T 0 0% 12M 0% 60000 32.0T 99% VTE1 VT: ---------------------------------------------------------------------- VTE1 VT: VTE2 VT: VTE2 VT: Tape library space for drives: 0240-027F VTE2 VT: VTE2 VT: Path Size Active Scratch / Qty Free Filesystem VTE2 VT: ---------------- ---- --------- ---------------- --------- ---------- VTE2 VT: /tapelib1 20.1G 0 0% 0 0% 0 18.8G 86% LABEL=root VTE2 VT: /tapelib1/V5 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.104:/tapelib1/V5 VTE2 VT: /tapelib1/V6 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.102:/tapelib1/V6 VTE2 VT: /tapelib1/V7 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.103:/tapelib1/V7 VTE2 VT: /tapelib1/V8 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.104:/tapelib1/V8 VTE2 VT: /tapelib1/V9 5.7T 0 0% 2M 0% 10000 5.7T 99% 192.168.200.102:/tapelib1/V9 VTE2 VT: /tapelib1/VB 3.5T 0 0% 2M 0% 10000 3.5T 99% 192.168.200.104:/tapelib1/VB VTE2 VT: ================================================== VTE2 VT: Totals: 32.0T 0 0% 12M 0% 60000 32.0T 99% VTE2 VT:



20.2.2 query config

nd can be issued in the VTE application window or by running Script 501. The UCB

TE1 VT: DLm409I: Command received: 'query config' TE1 VT: DLm102I: Configuration file is /etc/bti/xmap0

VTE2 VT: ----------------------------------------------------------------------

“query config” commaoutput provides a listing for VOLSER in the File Systems. The following is a partial listing of the 0200 tape range in VTE1 and 0240 UCB tape range in VTE2.

V V

Column Description

Path This lists the File System as it is mounted to the Virtual Tape Library. Within the File System name, you will find the tapelib name and the first two characters of the VOLSER range of tapes contained in the File System (D0, D1, D2 etc) for Systyemware tapes. Each File System contains 5,000 virtual tapes. The C0-C5 tapelibs have a zero qunatity because they are created in Cleveland and replicated to Pittsburgh.

Size This is the size of the File System. The File System size will either be listed in Gigabytes (G) or Terabytes (T). The distribution of this space appears in the next three columns and is divided between Active, Scratch and Free.

Active This is the amount of space within the File System that is currently allocated to active tape volumes. These are tapes that have been created and are currently cataloged in both the ICF catalog and the Tape Management System Catalog.

Scratch This is the amount of space within the File System that is currently allocated by Scratch tapes. These are tapes that were previously used, but have expired and are no longer cataloged. They are eligible to be mounted in response to a scratch request, but have not yet been overwritten. Because of this, a user can still read the data from these tapes by coding the specific VOLSER of the tape in his JCL. This functionality mimics that of a real tape environment. Under this column, in addition to the space utilization metrics, you will also see a count field. This is the total number of scratch volumes that are currently in the specified File System.

Free This is the amount of un-allocated space within the File System. When a scratch tape is allocated to a job and is written to, the space it consumes comes from the free pool. Once the job finishes and the tape volume is closed, the space consumed by this tape will now appear under the Active column. The amount of free space is managed automatically by the Virtual Tape Emulation (VTE) Engines. When the File System contains less than 5% free space, the VTE will begin deleting the space from Scratch Tapes beginning with the oldest tapes first.

Filesystem The IP address of the Data Mover and file system Mount Point that references the file system the Data Mover manages. IP addresses ending in .20 are handled by Data Mover 2, those ending in .30 handled by Data Mover 3. This is the VTE’s path to the Data Mover to request the file share for tape activities.



elib1/ SIZE=20G elib1/ SIZE=20G

TE2 VT: DLm102I: Configuration file is /etc/bti/xmap0

--------------- elib1/ SIZE=20G elib1/ SIZE=20G

VTE1 VT: Current Values Are: VTE1 VT: Index Devicename Type CU UA Options VTE1 VT: ------------------------------------ VTE1 VT: 00 0200 3590 00 00 PATH=/tap VTE1 VT: 01 0201 3590 00 01 PATH=/tap VTE1 VT: 02 0202 3590 00 02 PATH=/tapelib1/ SIZE=20G VTE1 VT: 03 0203 3590 00 03 PATH=/tapelib1/ SIZE=20G VTE1 VT: 04 0204 3590 00 04 PATH=/tapelib1/ SIZE=20G VTE1 VT: 05 0205 3590 00 05 PATH=/tapelib1/ SIZE=20G VTE1 VT: 06 0206 3590 00 06 PATH=/tapelib1/ SIZE=20G VTE1 VT: 07 0207 3590 00 07 PATH=/tapelib1/ SIZE=20G VTE1 VT: 08 0208 3590 00 08 PATH=/tapelib1/ SIZE=20G VTE1 VT: 09 0209 3590 00 09 PATH=/tapelib1/ SIZE=20G VTE1 VT: 0A 020A 3590 00 0A PATH=/tapelib1/ SIZE=20G VTE1 VT: 0B 020B 3590 00 0B PATH=/tapelib1/ SIZE=20G VTE1 VT: 0C 020C 3590 00 0C PATH=/tapelib1/ SIZE=20G VTE1 VT: 0D 020D 3590 00 0D PATH=/tapelib1/ SIZE=20G VTE1 VT: 0E 020E 3590 00 0E PATH=/tapelib1/ SIZE=20G VTE1 VT: 0F 020F 3590 00 0F PATH=/tapelib1/ SIZE=20G VTE2 VT: DLm409I: Command received: 'query config ' V VTE2 VT: Current Values Are: VTE2 VT: Index Devicename Type CU UA Options VTE2 VT: --------------------- VTE2 VT: 00 0240 3590 00 00 PATH=/tap VTE2 VT: 01 0241 3590 00 01 PATH=/tap VTE2 VT: 02 0242 3590 00 02 PATH=/tapelib1/ SIZE=20G VTE2 VT: 03 0243 3590 00 03 PATH=/tapelib1/ SIZE=20G VTE2 VT: 04 0244 3590 00 04 PATH=/tapelib1/ SIZE=20G VTE2 VT: 05 0245 3590 00 05 PATH=/tapelib1/ SIZE=20G VTE2 VT: 06 0246 3590 00 06 PATH=/tapelib1/ SIZE=20G VTE2 VT: 07 0247 3590 00 07 PATH=/tapelib1/ SIZE=20G VTE2 VT: 08 0248 3590 00 08 PATH=/tapelib1/ SIZE=20G VTE2 VT: 09 0249 3590 00 09 PATH=/tapelib1/ SIZE=20G VTE2 VT: 0A 024A 3590 00 0A PATH=/tapelib1/ SIZE=20G VTE2 VT: 0B 024B 3590 00 0B PATH=/tapelib1/ SIZE=20G VTE2 VT: 0C 024C 3590 00 0C PATH=/tapelib1/ SIZE=20G VTE2 VT: 0D 024D 3590 00 0D PATH=/tapelib1/ SIZE=20G VTE2 VT: 0E 024E 3590 00 0E PATH=/tapelib1/ SIZE=20G VTE2 VT: 0F 024F 3590 00 0F PATH=/tapelib1/ SIZE=20G

Column Description DLm102I The message : DLm102I: Configuration file is /etc/bti/xmap0 from this query

will show which XMAP configura specified for the last start of tion file was the VTE Application. This message will also indicate if the specified XMAP file was changed/updated since the last startup of the VTE Application if it is the same XMAP file from the last startup.

Index The Hexadecimal index value for each in the specified tapelib definition. This index begins with Hex ‘00’ for the first device and continues with hex values until the last device in the specified tapelib.

Devicename The defined DLM Tape Device UCB Address for the tapelib definition.



Type The defined DLM Tape Device Type for the tapelib definition. The DLM tape devices are 3490 for Clevland SAR tapes and 3590 for SARPAC and Systemware tapes.

CU The Hexadecimal Control Unit defined for the device in the HCD Gen. UA The Hexadecimal Unit Address defined for the device in the HCD Gen. Options The tapelib directory PATH name for ths specific tapelib definition. The

PATH directory for each device in this configuration is tapelib1/. The Default logical tape size assigned to the device. The SOI default Logical Tape size is set to 800 MB for 3490 and 20GB for 3590 Tape Devices.

20.2.3 query paths assigned

uery paths assigned” command can be issued in the VTE application window or by running Script 501.

1) V2.1

hs assigned' h Group ID

319116 A

ssor Tool (501) V2.1

hs assigned' h Group ID

319116 A

“qShows the assigned channel path information for active DLm tape devices in the specified VTE. These displays start with 0200 VTE1 and 0240 VTE2.

EMC DLm VTEC Command Processor Tool (50 Tue Dec 8 11:10:58 EST 2009

eceived: 'query pat VTE1 VT: DLm409I: Command r VTE1 VT: Device Interface/Path# Port LPAR CU Device Pat VTE1 VT: 0200 0 0 B2 4 00 00 G:800002D5B02094C5 VTE1 VT: 1 0 B3 4 00 00 G:800002D5B02094C5319116 A VTE1 VT: 0201 0 0 B2 4 00 01 G:800002D5B02094C5319116 A VTE1 VT: 1 0 B3 4 00 01 G:800002D5B02094C5319116 A VTE1 VT: 0202 0 0 B2 4 00 02 G:800002D5B02094C5319116 A VTE1 VT: 1 0 B3 4 00 02 G:800002D5B02094C5319116 A VTE1 VT: 0203 0 0 B2 4 00 03 G:800002D5B02094C5319116 A VTE1 VT: 1 0 B3 4 00 03 G:800002D5B02094C5319116 A (Listing continues…..)

EMC DLm VTEC Command Proce Tue Dec 8 11:17:38 EST 2009

eceived: 'query pat VTE2 VT: DLm409I: Command r VTE2 VT: Device Interface/Path# Port LPAR CU Device Pat VTE2 VT: 0240 0 0 B4 4 00 00 G:800002D5B02094C5 VTE2 VT: 1 0 B5 4 00 00 G:800002D5B02094C5319116 A VTE2 VT: 0241 0 0 B4 4 00 01 G:800002D5B02094C5319116 A VTE2 VT: 1 0 B5 4 00 01 G:800002D5B02094C5319116 A VTE2 VT: 0242 0 0 B4 4 00 02 G:800002D5B02094C5319116 A VTE2 VT: 1 0 B4 4 00 02 G:800002D5B02094C5319116 A VTE2 VT: 0243 0 0 B4 4 00 03 G:800002D5B02094C5319116 A VTE2 VT: 1 0 B5 4 00 03 G:800002D5B02094C5319116 A (Listing continues…..)

Column Description Device The currently active tape device UCB Address. Devicename The defined DLM Tape Device UCB Address for the tapelib definition. Interface/Path# The FICON Adapter Interface assignment and path number for this

specific device. There are two FICON Adapter interfaces for each VTE.



Interface #0 and interface #1 show as being assigned to this specific device. This information may be useful for problem analysis and diagnosis.

Port The Port identifier for this specific device. This would be the FICON Switch port for each FICON Interface. See Section 1.6 FICON for the Controller and Port mapping. This information may be useful for problem analysis and diagnosis.

LPAR The VTE LPAR assigned number for the specific LPAR where this device is actively being used. This information may be useful for problem analysis and diagnosis.

CU The Hexadecimal Control Unit defined for the device in the HCD Gen. This information may be useful for problem analysis and diagnosis.

Path group ID The assigned path group for this device for each of the FICON interfaces. This information may be useful for problem analysis and diagnosis.

20.2.4 show channel paths

how channel paths” will display connections that the Host has attempted to establish with the VTE, but

and

EMC DLm VTEC Command Processor Tool (501) V2.1

nnel paths'

th Status

“swhich are not configured for this specific VTE. Displays devices to which the Host has attempted to talk toon the channel interface, but which were rejected because they were not configured devices. The presence of any rejected paths usually means a mismatch between the virtual device configurationthe Host configuration. The following is a VTE1 display.

Tue Dec 8 11:11:54 EST 2009 ceived: 'show cha VTE1 VT: DLm409I: Command re

VTE1 VT: ll paths for slot=199936 VTE1 VT: a

VTE1 VT: ChLink LPAR cuAddr Pa VTE1 VT: ------ ---- ------ ----------- VTE1 VT: B2 4 0 Established VTE1 VT: B3 4 0 Established VTE1 VT: B2 4 1 Established VTE1 VT: B3 4 1 Established VTE1 VT: B2 4 2 Established VTE1 VT: B3 4 2 Established VTE1 VT: B2 4 3 Established VTE1 VT: B3 4 3 Established

Column Description ChanLINK The switch port the mainframe is o if a switch is used. See connected t

Section 1.6 FICON for controller and port mapping. This information may be useful for problem analysis and diagnosis.

LPAR The VTE LPAR assigned number for the specific LPAR where this channel was attempted to validate a device not configured in the VTE. This information may be useful for problem analysis and diagnosis.

cuAddr The CUADD (00-FF for Ficon) in the control unit definition. The Hexadecimal Control Unit Address defined for the device in the HCD Gen. This



information may be useful for problem analysis and diagnosis. CUPort The switch port the adapter is connected to if a switch is used. This

information may be useful for problem analysis and diagnosis.

.3 Script 502 Log Copy Utility

g files, /var/log/messages, VTE xmap & ximl files, output of “ipmitool set

1 //TDLMJOBX JOB (001,0000516,00000),'DLM SCRIPT 502

20

Mainframe batch job to collect btilolist”. Transfers files to SYSOUT flat file. Script 502 can be used to document DLm activity and send information to L2 DLm Support. The following example executes Script 502 to dump the btilog file andLinux log messages from VTE1.

',

NER =BFL502,DISP=OLD,LABEL=(,NL),

T=98000

12/07/2009 02:03:09 VTE1 VT: DLm405I: Device 4540 Display: 'MD50006S'

--------------------------------------------------------------------------------

rt=x102-x17 #161: Adapter error: parms: xC x0 x0 0

// MSGCLASS=Q,NOTIFY=&SYSUID,CLASS=W /*JOBPARM S=SYS4 //********************************************************************** //* DLM V2.1 - RUN CPF 502

******************************************* //*************************** 2 //COMMAND EXEC PGM=DLMCMD

.LOADLIB,DISP=SHR 3 //STEPLIB DD DSN=SYSP.DLM 4 //DLMCTRL DD DSN=SYSP.DLM.D0005,DISP=OLD 5 //SYSUDUMP DD SYSOUT=* 6 //DLMLOG DD SYSOUT=* 7 //DLMCMD DD *

=IEBGE 8 //READBAC EXEC PGM 9 //SYSUT1 DD UNIT=0200,VOL=SER // DSN=BFL502.FLAT,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132),EXPD 10 //SYSUT2 DD SYSOUT=*,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132) 11 //SYSPRINT DD SYSOUT=* 12 //SYSIN DD DUMMY

12/07/2009 02:03:09 VTE1 VT: DLm440I: Device 4540 Volume D50006 mounted 12/07/2009 02:03:09 VTE1 VT: DLm405I: Device 4540 Display: ' D50006S'

d 12/07/2009 02:03:15 VTE1 VT: DLm490I: Device 4540 Volume D50006 unloade 12/07/2009 02:03:15 VTE1 VT: DLm405I: Device 4540 Display: 'KD50006 ' 12/07/2009 02:03:47 VTE1 VT: DLm405I: Device 455D Display: 'MD10006S' 12/07/2009 02:03:47 VTE1 VT: DLm440I: Device 455D Volume D10006 mounted 12/07/2009 02:03:47 VTE1 VT: DLm405I: Device 455D Display: ' D10006S'

d 12/07/2009 02:04:08 VTE1 VT: DLm490I: Device 455D Volume D10006 unloade 12/07/2009 02:04:08 VTE1 VT: DLm405I: Device 455D Display: 'KD10006 ' 12/07/2009 02:04:11 VTE1 VT: DLm405I: Device 4554 Display: 'MD10006S' 12/07/2009 02:04:11 VTE1 VT: DLm440I: Device 4554 Volume D10006 mounted 12/07/2009 02:04:11 VTE1 VT: DLm405I: Device 4554 Display: ' D10006S'

d 12/07/2009 02:04:19 VTE1 VT: DLm490I: Device 4554 Volume D10006 unloade 12/07/2009 02:04:19 VTE1 VT: DLm405I: Device 4554 Display: 'KD10006 '

#####Diagnostic-Data##### r/log/messages Linux System Log name : /va

ec 6 08:21:25 VTE1 kernel: PEFA-LP-0 Ale D

Dec 6 08:21:25 VTE1 BTITOOL: Alert FIFO-W: Alert-W x102-x17 received from PEFA-LP esn 19968 Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_DRIVER_TRACE, pid 9769

Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_FIRMWARE_TRACE, pid 9771



ed from PEFA-LP esn 199680



20.4 Script 998 & 999 GENSTATS Reporting

ses file /var/bti/stats/hourly which contains VTE level

lib names and is executed to list

P2 EXEC PGM=GENSTATS

LABEL=(,NL), T=98000

WAIT 996

OLSERS STILL MOUNTED :NONE ********************************

Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_FIRMWARE_TABLES, pid 9773 Dec 6 08:21:25 VTE1 BTITOOL: Alert FIFO-W: Alert-W x102-x17 receiv Dec 6 08:21:25 VTE1 kernel: PEFA-LP-0 Alert=x102-x17 #162: Adapter error: parms: xC x0 x0 Dec 6 08:21:25 VTE1 kernel: PEFA-LP-0 Alert=x102-x17 #163: Adapter error: parms: xE x1 x0 Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_DRIVER_TRACE, pid 9769 Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_FIRMWARE_TRACE, pid 9771 Dec 6 08:21:25 VTE1 BTITOOL: skip SAVE_FIRMWARE_TABLES, pid 9773 Dec 6 08:21:25 VTE1 BTITOOL: Alert FIFO-W: Alert-W x102-x17 receiv Dec 6 08:21:25 VTE1 BTITOOL-TRC: saving /opt/bti/dumps/w199680_06Dec2009_082125.tab.gz Dec 6 08:21:25 VTE1 BTITOOL-TRC: saving /opt/bti/dumps/w199680_06Dec2009_082125.trb.gz Dec 6 08:21:26 VTE1 BTITOOL-TRC: saving /opt/bti/dumps/w199680_06Dec2009_082125.fmt.gz Dec 6 08:21:37 VTE1 kernel: PEFA-LP-0 Alert=x102-x17 #164: Adapter error: parms: xC x0 x0 Dec 6 08:21:37 VTE1 kernel: PEFA-LP-0 Alert=x102-x17 #165: Adapter error: parms: xC x0 x0 Dec 6 08:21:37 VTE1 kernel: PEFA-LP-0 Alert=x102-x17 #166: Adapter error: parms: xE x1 x0 Dec 6 08:21:37 VTE1 BTITOOL: Alert FIFO-W: Alert-W x102-x17 received from PEFA-LP esn 199680 Dec 6 08:21:37 VTE1 BTITOOL: skip SAVE_DRIVER_TRACE, pid 9778 Dec 6 08:21:37 VTE1 BTITOOL: skip SAVE_FIRMWARE_TRACE, pid 9780 Dec 6 08:21:37 VTE1 BTITOOL: skip SAVE_FIRMWARE_TABLES, pid 9782 Dec 6 08:21:37 VTE1 BTITOOL: Alert FIFO-W: Alert-W x102-x17 receiv

VTE and VOLSER range statistics. Script 998 uperformance statistics. Script 999 uses file /var/bti/stats/vstats which contains VOLSER level statisticsabout tape mounts, unmounts, including R/W bytes and block counts.

In the following example, Script 998 was copied to 996 to tailor the /tapethe slowest 20 tape mounts. See DLm User Guide Appendix F for additional processing parameters.

1 //TDLMJOBX JOB (001,0000516,00000),'DLM SCRIPT 998', // MSGCLASS=Q,NOTIFY=&SYSUID,CLASS=W /*JOBPARM S=SYS1 2 //COMMAND EXEC PGM=DLMCMD,PARM='CMD=RUNWAIT 996' 3 //STEPLIB DD DSN=SYSP.DLM.LOADLIB,DISP=SHR 4 //DLMCTRL DD DISP=SHR,DSN=SYSP.DLM.D0003 5 //DLMLOG DD SYSOUT=* //* //* NOW PROCESS THE TAPE CREATED IN STEP1 AS BFLDRL //* 6 //STE 7 //STEPLIB DD DSN=SYSP.DLM.LOADLIB,DISP=SHR 8 //GENIN DD UNIT=4560,VOL=SER=BFLDRL,DISP=OLD, // DSN=BFLDRL.FLAT,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132),EXPD 9 //SYSUT2 DD SYSOUT=*,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132) 10 //SYSPRINT DD SYSOUT=* 11 //SYSIN DD * DLMCMD V 4.03 DLMCTRL = 4640 2009/12/14 14:09:30 CMD ISSUED: RUN GENSTATS VER 1.02 PARMS: SLOWMOUNTS V ********************************AVERAGE MOUNT RESPONSE (SECS.) :000.025



OP 20 SLOWEST MOUNTS (SECS.):

b1/V6

.5 AWSPRINT Utility (Contributed by John Moore)

the Administrator GUI. The AWSPRINT

ollow

on all D0 Tape volumes without DETAIL:

:28:06

rted by Name 07/29/2009 09:30:17 PM

PE INFO TAPE SIZE

1 D00018 D00018 07/28/09 20:39 S HDR1LM.CONTROL.VOLUME 454

T NODENAME TIME VOLSER DATE TIME PATH VTE2 000.282 V60001 2009/11/23 10:11:08 tapeli VTE2 000.285 V40013 2009/04/17 04:12:51 tapelib1/V4 VTE2 000.290 V10002 2009/11/17 15:30:09 tapelib1/V1 VTE1 000.290 V50009 2009/12/09 08:53:08 tapelib1/V5 VTE1 000.294 V50007 2009/12/03 13:19:33 tapelib1/V5 VTE2 000.302 V30008 2009/12/10 05:43:50 tapelib1/V3 VTE2 000.304 V30013 2009/12/08 11:02:25 tapelib1/V3 VTE1 000.309 V30005 2009/12/02 16:00:01 tapelib1/V3 VTE2 000.311 V50006 2009/12/04 21:16:12 tapelib1/V5 VTE1 000.314 V80011 2009/12/10 16:59:53 tapelib1/V8 VTE2 000.315 V50006 2009/12/05 03:02:40 tapelib1/V5 VTE1 000.323 V20007 2009/12/08 05:40:19 tapelib1/V2 VTE1 000.343 V40007 2009/12/06 18:47:41 tapelib1/V4 VTE2 000.344 V10009 2009/12/06 10:08:14 tapelib1/V1 VTE1 000.346 V40013 2009/12/09 18:03:32 tapelib1/V4 VTE1 000.349 V10017 2009/12/11 05:44:17 tapelib1/V1 VTE1 000.377 V70001 2009/11/22 09:02:45 tapelib1/V7 VTE2 000.449 V50007 2009/12/03 14:56:01 tapelib1/V5 VTE1 000.474 V10004 2009/11/27 14:55:50 tapelib1/V1

20

The AWSPRINT Utility is a VTE based command run fromcommand will produce a report of DLM volume in summary or detail form. Filtering by VOLSER in individual tapelib definitions is optional. Specific entries are case Sensitive. AWSPRINT examples ffor the PSYS1 tapelib /tapelibppgh3_D0 for Systemware 3590s.

NOTE: All commands are case sensitive!!!

Example #1 - Produce a SUMMARY Report

masadmin@VTE1:~> awsprint -p/tapelibppgh3/D0 awsprint Version 5.10, Compiled Oct 23 2008 11 SoPath: /tapelibppgh3/D0 Selection Criteria: All Tapes Without Details NO. NAME VOLSER DATE TIME L TA

2 D00027 D00027 07/28/09 21:18 S HDR1LOG.E09B.DLMFILE 6.8M 3 ~D00000 D00000 07/27/09 18:21 S HDR159.DLM.COPY.JCLJC 548 4 ~D00001 D00001 07/28/09 18:52 S HDR100000000000000000 184 5 ~D00002 D00002 07/28/09 18:52 S HDR100000000000000000 184 6 ~D00003 D00003 07/28/09 18:52 S HDR100000000000000000 184 ....................................... 4996 ~D04995 D04995 12/31/89 23:00 S HDR100000000000000000 184 4997 ~D04996 D04996 12/31/89 23:00 S HDR100000000000000000 184 4998 ~D04997 D04997 12/31/89 23:00 S HDR100000000000000000 184 4999 ~D04998 D04998 12/31/89 23:00 S HDR100000000000000000 184 5000 ~D04999 D04999 12/31/89 23:00 S HDR100000000000000000 184 *************************************************************************



ample #2 - Produce a SUMMARY Report on all D0 SCRATCH volumes without DETAIL:

rted by Name 07/29/2009 09:37:15 PM

NO. NAME VOLSER DATE TIME L TAPE INFO TAPE SIZE

1 ~D00000 D00000 07/27/09 18:21 S HDR159.DLM.COPY.JCLJC 548

4996 ~D04995 D04995 12/31/89 23:00 S HDR100000000000000000 184

Ex ple #3 - Produce a SUMMARY Report on a specific D0 volume without DETAIL:

rted by Name 07/29/2009 09:42:25 PM

18 Without Details

TAPE INFO TAPE SIZE

1 D00018 D00018 07/28/09 20:39 S HDR1LM.CONTROL.VOLUME 454

Ex ple #4 - Produce a DETAIL Report on a specific D0 volume with

Ex

masadmin@VTE1:~> awsprint -p/tapelibppgh3/D0 -s~D0* awsprint Version 5.10, Compiled Oct 23 2008 11:28:06 SoPath: /tapelibppgh3/D0 Selection Criteria: ~D0* Without Details 2 ~D00001 D00001 07/28/09 18:52 S HDR100000000000000000 184 3 ~D00002 D00002 07/28/09 18:52 S HDR100000000000000000 184 4 ~D00003 D00003 07/28/09 18:52 S HDR100000000000000000 184 ....................................... 4997 ~D04996 D04996 12/31/89 23:00 S HDR100000000000000000 184 4998 ~D04997 D04997 12/31/89 23:00 S HDR100000000000000000 184 4999 ~D04998 D04998 12/31/89 23:00 S HDR100000000000000000 184 5000 ~D04999 D04999 12/31/89 23:00 S HDR100000000000000000 184 *************************************************************************

am

masadmin@VTE1:~> awsprint -p/tapelibppgh3/D0 -sD00018 awsprint Version 5.10, Compiled Oct 23 2008 11:28:06 SoPath: /tapelibppgh3/D0 Selection Criteria: D000 NO. NAME VOLSER DATE TIME L

*************************************************************************

am DETAIL:

rted by Name 07/29/2009 09:43:03 PM


***********************************************************************

BCDIC LABELS>

masadmin@VTE1:~> awsprint -p/tapelibppgh3/D0 -sD00018 -N -d awsprint Version 5.10, Compiled Oct 23 2008 11:28:06 SoPath: /tapelibppgh3/D0 Selection Criteria: D00018 With Details ** 1 D00018 D00018 07/28/09 20:39 S HDR1LM.CONTROL.VOLUME 454 ************************************************************************* DETAILS OF /tapelibppgh3/D0/D00018 <E



TCSBT

Compressed

.CONTROL.VOLUMED0001800010001 0092090000000000000IBM OS/VS 370

Compressed

tape.

awsprint -p/tapelibppgh3/D0 -s~D033*

rted by Name 07/29/2009 09:44:30 PM

ls


1 ~D03300 D03300 12/31/89 23:00 S HDR100000000000000000 184

21. DLm Utilities

here are several DLm utilities which customers may or may not require to manage their DLm

1. DLMCMD – Allows mainframe batch job to submit DLm commands to the VTEs. Output is written to

(,KEEP)

VOL1D00018 HDR1LM.CONTROL.VOLUME30001800010001 0092090000000000000IBM OS/VS 370 HDR2U000000000000SCRATCHU/SCR P 00000 ...Tape File #1: 3 x 80-byte blocks 0 Blocks Compressed 3 Blocks not <TM> <TM> EOF1LMEOF2U000000000000SCRATCHU/SCR P 00000 ...Tape File #3: 2 x 80-byte blocks 0 Blocks Compressed 2 Blocks not <TM> <TM> End of************************************************************************* *************************************************************************

ample #5 - Produce a SUMMARY Report on a range of specific D0 volumes using a mask without ExDETAIL:

masadmin@VTE1:~> awsprint Version 5.10, Compiled Oct 23 2008 11:28:06 SoPath: /tapelibppgh3/D0

3* Without DetaiSelection Criteria: ~D03 2 ~D03301 D03301 12/31/89 23:00 S HDR100000000000000000 184 3 ~D03302 D03302 12/31/89 23:00 S HDR100000000000000000 184 4 ~D03303 D03303 12/31/89 23:00 S HDR100000000000000000 184 5 ~D03304 D03304 12/31/89 23:00 S HDR100000000000000000 184 6 ~D03305 D03305 12/31/89 23:00 S HDR100000000000000000 184 7 ~D03306 D03306 12/31/89 23:00 S HDR100000000000000000 184 (continue ~D033* listing)

********************************************************************

Tenvironment.

the VTE logs (/var/bti/log) and is not returned to the mainframe.

//CMD EXEC PGM=DLMCMD //STEPLIB DD DISP=SHR,DSN=user.apf.loadlib //DLMCTRL DD DSN=DLM.CTRL,UNIT=xxxxx,VOL=SER=,DISP=//DLMLOG DD SYSOUT=* //DLMCMD DD * QUERY ALL



2. DLMLIB – only used with SMS managed tapes with a Manual Tape Library (MTL) to define the tape

.LOG,DISP=SHR (recfm=fb,lrecl=80,blksize=4000)

O MTL AN ‘M’

GNED SURING SMS LIBRARY ADD

0

. DLMSCR – Keeps synchronization between the TMS catalog and DLm. Reads the TMS scratch

clean up specific file systems after DR testing. In our prior

//JS0010 EXEC PGM=DLMSCR,PARM='RMMDV,NOTCDB' KLIB

), DSN=&&DLMCTRL,UNIT=CART

0 FORCE

/*

devices to the Tape Configuration Database (TCDB). In the following example, we are defining

VOLSER tape ranges V00000 through VB9999 with10,000 tapes each.

//STEP1 EXEC PGM=DLMLIB //SYSUDUMP DD SYSOUT=* //OUTDD DD DSN=DLMLIB//INDD DD * * LOAD VOLUMES INT* 1ST CHARACTER MUST BE* 4-9 STARTING VOLSER * 11-18 LIBRARY NAME ASSI* 20 MEDIA TYPE DEFAULT=2, SPECIFY 4 FOR 3590 * 21-25 COUNT OF VOLSERS TO BE ADDED, MAXIMUM=1000M V00000 TAPELIB1 410000 M V10000 TAPELIB1 410000 M V20000 TAPELIB1 410000 M V30000 TAPELIB1 410000 M V40000 TAPELIB1 410000 M V50000 TAPELIB1 410000 M V60000 TAPELIB1 410000 M V70000 TAPELIB1 410000 M V80000 TAPELIB1 410000 M V90000 TAPELIB1 410000 M VA0000 TAPELIB1 410000 M VB0000 TAPELIB1 410000

3report as input looking for DLm tapes in a scratch status. The scratch utility really doesn’t delete volumes but only renames them from V00000 to ~V00000. DLMSCR only touches the VTEs and makes no changes to the TMS catalog.

One other use of the DLMSCR utility is toexamples we have tape ranges VA0000–VA9999 and VB0000–VB9999 at the DR site defined with a read/write authority. So any new tape allocations during DR testing would go only to the VA and VB file systems. At the end of each DR testing, this procedure can be used to scratch any volumes that were written and free the space in the file systems.

//STEPLIB DD DISP=SHR,DSN=SYS2.EMC.R000.DLM.LIN//DLMLOG DD SYSOUT=* //DLMCTRL DD DISP=(, DELETE//* DLMCTRL MUST BE A R/W DEVICE, R/O CAUSES AN S613 //DLMSCR DD * RMM DV VA000RMM DV VA0001 FORCE RMM DV VA0002 FORCE (continue)



EE RMM DV A0001 FREE RMM DV

easons why DLMSCR won’t scratch tapes:

der

4. AWSPRINT – produces lists of tapes in /tapelib V0* back to screen:

5. AWSDIR – review the contents of library volumes in V0

~V00001) the tape is a scratch, if the tape size = 184 bytes the tape has

6. What DLm am I On?

at least two DLms, Prod and DR. Aside from looking at the IP address of the

istrator Shell

d can be anything you

e

ll m. Many clients like this as it ,

22 Linux Commands

22. Useful DLm Linux Commands (Provided by Nick Pattison)

Command Description/Usage

VA0000 FRVVA0002 FREE RMM DV (continue)

R1) Mismatched Dataset Name 2) VOLSER Locked

OL1 hea3) Invalid or missing V4) Volume in use 5) Create date = today’s date

awsprint –p/tapelib/V0 –sV0*

Awsdir /tapelib/V0

If tape name starts with tilde (been intitialized but never used.

Most customers have ACP in the title bar of the VNC window, both DLms look identical. So how do you know which DLm you are on? You can do this on both the ACP and the VTE.

) Right click an empty area of the desktop and select Admin12) Type `cd Desktop`

_Prod` The identifier string must have no spaces an3) Type `touch This_iswant, you could use the site names, or Prod and DR.

4) On the desktop, there will be an icon titled "This_is_Prod". Drag this icon to a visible place on thdesktop. Put the icon in the upper left corner.

you are doing is creating a zero byte file with the name of your DLA

helps them ensure they are working with the right DLm. You can make these icons on just the ACPor on the ACP and VTEs.



at Types the contents of a file to the screen (aka catalog) Ex: cat /etc/bti/userscripts/filename

s the contents of a file to the screen.

c

Display

Cd Change Directory, cd ~ will go back to the Root Di

rectory

chmod Change permissions of

a file

.

ermissions. group’s permissions.

755 means the following: r can read, write, and execute the file. The group can read te the file. Everyone else can read and execute the file.

ed for a user to be tory.

y /etc/bti/userscripts to 775.

Requires a set of permissions in the form of three digits1 = execute 2 = write 4 = read The first digit dictates the owner’s pThe second digit dictates the The third digit dictates everyone else’s permissions. For example,The owneand execu Directories must have the execute permission allowable to change into and list the contents of that direc Ex: chmod 775 /etc/bti/userscripts Changes the permissions of the director

chown

correct

Change ownership of a file Ex: chown masadmin:www /etc/bti/xmap0 Changes the owner of the /etc/bti/xmap0 file to an owner of masadmin,group owner of www. This may be necessary to correct inownership of file.

df

d to bytes for output

Reports disk file systems space usage Useful flags: -h human readable. Use K,M,G, etc as oppose Ex: df –h Shows size and usage data for all mounted file systems.

du D Find

h in the path /opt

Searches for files. Ex: find /opt –name acpkeys.sh Searches for all files that match the criteria of having a name with acpkeys.s

grep Can Allows you to search output or a filename for a specific string. also handle regexp strings. Useful flags: -i case-insensitive



ted file systems to include only nfs shares.

var/log/messages hba var/log/messages files and displays only lines

-v Display all lines that do not contain the search string Ex 1: mount | grep nfs Filters the output of all moun Ex 2: grep -i /Searches through the /that contain the case-insensitive string “hba”.

head isplays the first 10 lines of a file

lines=xx displays the first xx lines

D Useful flags: -- Ex: head xmap0 Displays the first 10 lines of the xmap0 file

ifconfig ke IP address Display network interface details liless isplay the contents of a file or command output with pagination.

arrow keys> Navigate

.

e ifconfig command

D <space> Next Page <<q> Quit Ex 1: less /var/log/messages Displays the contents of the /var/log/messages file with pagination Ex 2: ifconfig | less Paginates the output of th

Ls y Contents List DirectorMan ead command manuals Rmore r command output with pagination.

space> Next Page

the /var/log/messages file with pagination.

aginates the output of the ifconfig command.

Display the contents of a file o < Ex 1: more /var/log/messages Displays the contents of Ex 2: ifconfig | more P

mount

rv rv.

Mounts a file system Ex: mount /dev/sdb1 /mnt/usbdMounts the /dev/sdb1 device (pen drive) as the filesystem /mnt/usbd

pwd isplays the present working directory Dscreen shell session (useful for celerra configuration)

resumes a previous screen session nd have your shell remain active

Invokes a detachable Useful flags: -rCTRL-AD Allows you to detach aexit or CTRL-D Terminates the shell session



itiates a screen session Ex 1: screen In Ex 2: screen –r Resumes your previous screen session

showmount x: showmount –e <data_mover>

E

ssh

seful flags: Logs in as specified username

nto VTE1 as the user root

SSH U-l <username> -X Enables X Forwarding Ex: ssh –l root VTE1 Logs i

su llows you to switch a shell to a different user.

account vtape. This is useful for running cript80 for the first time. When done running commands as vtape,

our initial shell user.

A Ex: su vtape Switches the shell to the userstype exit to return to y

sudo root when you are a non root user.

x: sudo ifconfig mand ifconfig as root.

Allows you to run a command as ERuns the com

tail

allows you to follow the file as new lines are added. C to exit

hows the last 10 lines of the messages log.

Displays the last 10 lines of a file Useful flags: --lines=xx displays the last xx lines -f Press CTRL Ex: tail /var/log/messages S

tee ut to the screen AND a file. Useful for logging command

_setup.log xecutes the dlm_setup command and all output will be displayed on

me time, being recorded to the file,

Redirects outpoutput. Ex: ./dlm_setup ALL | tee dlmEyour screen while at the sadlm_setup.log

touch , a 0 byte file will be created.

nts of the file will not be

Touches a file. Does not modify the contents of the file. If the file does not exist Ex: touch /var/bti/log/btilog_01 If this file doesn’t exist, a 0 byte file will be created with the name /var/bti/log/btilog_01. If the btilog_01 file exists, the last modified date/time attribute will be updated to the current time. The conte



odified. mumount

rv mounts the file system mounted at /mnt/usbdrv (pen drive)

Unmounts a file system Ex: umount /mnt/usbdU

which

ls

Shows which executable is being executed from the path Ex: which Returns the location of the ls binary

whoami eturns the current user R

dlm v2.1 z/os implementation guide...including emc proven professional certification dlm v2.1 z/os...

Documents