Dell Disk Library for mainframe DLm8500 storage enterprise User's guide
Below you will find brief information for Command Processors and Utilities DLm 4.x and 5.x. This guide provides details on Disk Library (DLm) command processors and utilities for z/OS environments. It covers the command processor for diagnostics, VTE commands, log information, virtual tape volume information, VNX replication, Data Domain and PowerProtect information, replication information by VOLSER, and tape activity. The document also includes information on how to create custom command processors.
Advertisement
Advertisement
Disk Library for mainframe
Command Processors and Utilities for z/OS Guide
4.x and 5.x
April 2022
Rev. 7 .0
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2021 - 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.
Contents
Contents 3
4 Contents
Contents 5
6 Contents
Contents 7
Tables
29
30
31
32
25
26
27
28
21
22
23
24
17
18
19
20
37
38
39
40
33
34
35
36
13
14
15
16
9
10
11
12
7
8
5
6
3
4
1
2
8 Tables
45
46
47
48
41
42
43
44
49
50
51
52
Tables 9
1
Overview
This chapter provides an overview of the Disk Library for mainframe (DLm) Command Processors and the DLm utilities for the z/OS environment.
Topics:
•
Introduction to Command Processors and Utilities
•
•
Install the DLm Command Processors
•
Downloading and using DLm z/OS components
Introduction to Command Processors and Utilities
DLm provides a set of utilities for the z/OS environments along with Disk Library for mainframe (DLm). It also provides a number of command processors that enable you to issue DLm commands and monitor DLm status from the mainframe.
DLm Utilities
The DLm utilities for the z/OS environments are:
● GENSTATS - A utility that generates reports from VTE and VOLSER range statistics. This utility is supported on DLm 4.x
only. DLm 5.x does not support the GENSTATS utility. For DLm 4.5.3 and later and 5.x, CP988 and CP989 perform the same operations as GENSTATS.
● DLMSCR - A scratch utility that sends VOLSER scratch requests to DLm.
● DLMCMD - A utility that allows the mainframe to send DLm commands.
● DLMLIB - A utility that is required to define scratch volumes to an MTL.
● DLMVER - A utility that reports the versions of all DLm mainframe utilities on the mainframe and the z/OS release.
● DLMHOST - A host utility that provides z/OS Console Operation support.
● DLMWTOR - A utility that allows a WTOR to be issued to the z/OS Console with up to 10 lines of user-defined text.
This utility provides a means to require z/OS operator confirmation of a DLm-related change such as halting all DLm Tape activity.
● DLMCP - A utility that provides functionality to run Command Processors through PSF/RSD CCWs (without using BFL volumes).
DLm Command Processors
This section provides an overview of DLm command processors.
DLm Command Processors (CPxxx) enable you to:
● Issue DLm commands from the mainframe
● Monitor DLm status from the mainframe
● Return the output of DLm commands and tasks to the mainframe
The following command processors are provided with DLm:
● CP499: Provide DLm diagnostics.
● CP501: Run VTE command.
● CP502: Obtain VTE log information.
● CP503: DLm Volume Inventory Report.
● CP504: DLm VNX Replication Report.
● CP601 (not supported on DLm2500): DLm Data Domain System Utilization report.
● CP602 (not supported on DLm2500): DLm Data Domain Deduplication Report.
10 Overview
● CP603 (not supported on DLm2500): DLm Data Domain Replication Report.
● CP988: [DLm 4.5.3 and later and 5.x] Obtain DLm File System Activity Statistics.
● CP989: [DLm 4.5.3 and later and 5.x] Obtain DLm VTE Activity Statistics.
● CP998: [DLm 4.x only] Obtain DLm File System Activity Statistics.
● CP999: [DLm 4.x only] Obtain DLm VTE Activity Statistics.
NOTE: Only a single execution of a particular Command Processor can run at a time. DLm does not support multiple executions of the same Command Processor simultaneously.
Gathering and Reporting DLm Statistics Information
This section provides an overview of gathering and reporting DLm statistics information.
The DLm maintains activity information that records information such as the mounts, IOs, and unloads of tape volumes.
This information can then be used for various DLm reports using:
● CP988 and CP989 for DLm 4.5.3 and later and DLm 5.x
● For DLm 4.x:
1. Gathering DLm Statistics Information. DLm Statistics can be collected for individual virtual tape engines (VTEs), using
Command Processor CP999, or for an entire tape library using Command Processor CP998. Information regarding this step is documented in
and
.
2. Reporting on DLm Activity. DLm activity reporting uses the gathered statistics information to generate activity reports.
This step is performed by a DLm z/OS utility called GENSTATS. Information regarding this DLm utility is documented in
.
3. There are a number of PROCs that consolidate the above two steps into one process for the gathering and reporting of
DLm Command Processor support
This section provides an overview of DLm command processor support.
Table 1. CPxxx commands supported by DLm 4.x, and 5.x releases
Command Processors
CP499
DLm Releases
4.x
Yes
4.5.3 and later
Yes
CP501
CP502
CP503
CP504
CP601
CP602
CP603
CP988
CP989
CP998
CP999
Yes
Yes
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
5.x
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
Overview 11
Install the DLm Command Processors
Service personnel install the DLm Command Processors during initial setup and system upgrades.
Downloading and using DLm z/OS components
There are two installation procedures for DLm Mainframe Utilities for z/OS:
● SMP/E -
Installing DLm Utilities using the SMP/E method
provides details about this procedure.
● non-SMP/E -
Installing DLm Utilities using the non-SMP/E method provides details about this procedure.
12 Overview
2
DLm Utilities for z/OS Environment
This chapter introduces the DLm utilities for z/OS environment.
Topics:
•
•
•
•
•
•
•
•
GENSTATS utility
This section provides an overview of GENSTATS utility.
The GENSTATS utility generates reports on the tape mount and unmount statistics that are logged at the VTE level and at the
VOLSER range level for DLm 4.x. It can selectively present:
● Daily and hourly throughput numbers
● Mount rates
● Concurrent tape drive usage details
● Compression ratio
● Average and slow mount response information
NOTE: DLm 5.x does not support GENSTATS. Use CP988 and CP989 instead of GENSTATS for DLm 5.x. You could also use CP988 and CP989 instead of GENSTATS for DLm 4.5.3 and later.
GENSTATS uses command processors CP998 and CP999 to summarize virtual tape activity. A GENSTATS job consists of two steps:
1. Run a command processor which accesses the appropriate statistics file and writes the data to a statistics file.
2. Run GENSTATS to generate a report from the statistics file data.
GENSTATS reports
A GENSTATS report is generated by running CP998 or CP999 to retrieve the desired statistics, and then running the
GENSTATS utility to produce the report.
Specify one of the following report types in the REPORT parameter:
● THROUGHPUT : The THROUGHPUT report consists of two parts:
○ First part gives the daily/hourly throughput data for quickly identifying peak periods per day of the reporting period.
Throughput numbers are displayed in GB/second.
○ Second part gives a throughput summary for the range of days covered.
NOTE: This is the default report.
● MAXTAPES : Produces a report detailing the highest number of concurrent tapes in use per hour for each of the days processed. If no tapes are active during a particular hour, that cell shows '***'.
● SLOWMOUNTS=count : Shows the average mount times for the entire day range specified. It lists the slowest 'count' mount times along with the related VOLSER, VTEname, Pathname, Date, and Time. Use this report to identify and investigate any peak or slow periods.
DLm Utilities for z/OS Environment 13
● STILLINUSE : Lists any tape that was mounted but has no matching unmount record. When used with the SYNCTIME parameter, this report can also be used for DR Testing by identifying volumes that were mounted at a particular point in time.
● DETAIL : Lists all DLm volsers with detail compression statistics.
GENSTATS Tapelib report examples
This section provides the information about GENSTATS tapelib report examples.
NOTE: The examples below use a Unit, (F207), that is part of an MTL. This is the reason for the SMSHONOR clause in the unit specification.
Example 1: Slow mounts report
This section describes about an example of slow mounts report.
Sample JCL:
//GO1 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='SLOWMOUNTS=5'
Sample output
GENSTATS VER 1.28 Z1CWRK PARMS: SLOWMOUNTS=5
--------------------------------------------------------------------------------
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
TOP 50 SLOWEST MOUNTS (SECS.):
NODENAME TIME VOLSER DATE TIME PATH vte1dlm0 0000.026 BG0332 2015/08/31 11:02:15 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 0000.028 BG0337 2015/09/01 11:14:09 tapelibFLR/CEL1_FLRP_FS2 vte1dlm0 0000.029 BG0323 2015/08/28 16:59:43 tapelibFLR/CEL1_FLRP_FS2 vte1dlm0 0000.033 BG0325 2015/08/28 17:08:15 tapelibFLR/CEL1_FLRP_FS2 vte1dlm0 0000.041 BFLGR1 2015/08/26 16:19:44 tapelibFLR/CEL1_FLRP_FS2
Example 2: Throughput report
This section describes an example of the throughput report.
Sample JCL:
//GO2 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='THROUGHPUT'
Sample output
NOTE: In the following report, some lines do not fit in the margins and are continued for up to four lines in the sample output below.:
GENSTATS VER 1.28 Z1CWRK PARMS: THROUGHPUT
-----------------------------------------------------------------------------------------
--------------
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
-----------------------------------------------------------------------------------------
--------------
-----------------------------------------------------------------------------------------
--------------
THROUGHPUT IN GB/HR :
14 DLm Utilities for z/OS Environment
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT 08|OUT 09|OUT 10|
OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT 20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN 08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN 20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
|15/08/26|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-----
| |0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G MAXI/HR=00000G
MOUNTS/DY=000011 MAXMNT/HR=000011
….
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|15/09/02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.62|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G MAXI/HR=00000G
MOUNTS/DY=000079 MAXMNT/HR=000054
Example 3: Detail report
This section describes an example of a detail report.
Sample JCL:
//GO4 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='DETAIL'
Sample output
GENSTATS VER 1.28 Z1CWKB PARMS: DETAIL
------ Unload ----- ------ Channel ------ ---- File System ---- Duration Compression
DLm Utilities for z/OS Environment 15
Volser Date Time 4K Writes 4K Reads 4K Writes 4K Reads Time Percent
------ ---------- -------- ---------- ---------- ---------- ---------- ----------
----------
BG0300 2015/08/26 16:11:06 0000005121 0000000001 0000000303 0000000000 1068058565 94.1%
BFLGR1 2015/08/26 16:19:44 0000000001 0000000000 0000000001 0000000000 1068058576 00.0%
BFLGR1 2015/08/26 16:19:56 0000000000 0000000000 0000000001 0000000000 1068058576
BG0301 2015/08/26 16:19:56 0000000001 0000000001 0000000001 0000000000 1068058564 00.0% .
BG0348 2015/09/02 11:52:15 0000005121 0000000001 0000000303 0000000000 1067614753 94.1%
BG0349 2015/09/02 11:53:00 0000010241 0000000001 0000000605 0000000000 1067614708 94.1%
BG0353 2015/09/02 11:53:01 0000005121 0000000001 0000000303 0000000000 1067614755 94.1%
BG0350 2015/09/02 11:53:36 0000015361 0000000001 0000000907 0000000000 1067614672 94.1%
BG0351 2015/09/02 11:54:14 0000020481 0000000001 0000001208 0000000000 1067614634 94.2%
BG0354 2015/09/02 11:54:15 0000010241 0000000001 0000000605 0000000000 1067614726 94.1%
BG0352 2015/09/02 11:54:41 0000025601 0000000001 0000001510 0000000000 1067614607 94.2%
BG0355 2015/09/02 11:55:10 0000015361 0000000001 0000000907 0000000000 1067614707 94.1%
BG0356 2015/09/02 11:55:46 0000020481 0000000001 0000001208 0000000000 1067614709 94.2%
BG0357 2015/09/02 11:56:05 0000025601 0000000001 0000001510 0000000000 1067614716 94.2%
-----------------------------------------------------------------------------------------
----
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
-----------------------------------------------------------------------------------------
----
GENSTATS VTE report examples
This section describes the GENSTATS VTE report examples.
Example 1: Slow mounts report
This section describes an example of a slow mounts report.
Sample JCL:
//GO5 EXEC GENSTAT1,CMD=999,UNIT=(/F207,,,SMSHONOR), X
// REPORT='SLOWMOUNTS=5'
Sample output
GENSTATS VER 1.28 Z1CWK4 PARMS: SLOWMOUNTS=5
NODENAME = vte1
-----------------------------------------------------------
TOP 50 SLOWEST MOUNTS (SECS.):
NODENAME TIME VOLSER DATE TIME vte1 0000.063 DV0011 2015/07/28 11:19:16 vte1 0000.064 BFL503 2015/06/23 18:07:12 vte1 0000.065 BFL502 2015/08/04 15:54:00 vte1 0000.080 BFL501 2015/06/23 18:09:47 vte1 0000.085 BFLMT7 2015/08/25 15:17:19
----------------------------------------------------------
Example 2: Throughput report
This section describes an example of a throughput report.
Sample JCL:
//GO6 EXEC GENSTAT1,CMD=999,UNIT=(/F207,,,SMSHONOR), X
// REPORT='THROUGHPUT'
Sample output
16 DLm Utilities for z/OS Environment
GENSTATS VER 1.28 Z1CWKA PARMS: THROUGHPUT
NODENAME = vte1
-----------------------------------------------------------------------------------------
------------------
THROUGHPUT IN GB/HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT 08|OUT 09|OUT 10|
OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT 20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN 08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN 20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|15/06/23|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.00|
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|15/09/02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.62|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G
MAXI/HR=00000G
MOUNTS/DY=000091 MAXMNT/HR=000054
COUNT OF UNLOAD RECORDS :0000966
COUNT OF UNLOADS W/OUTPUT STATS:0000515
COUNT OF UNLOADS W/INPUT STATS :0000005
MAXIMUM OUTPUT/HR :000000.62G
MAXIMUM OUTPUT/DAY :000000.62G
MAXIMUM INPUT/HR :000000.02G
MAXIMUM INPUT/DAY :000000.02G
MAXIMUM THROUGHPUT/HR :000000.62G
MAXIMUM THROUGHPUT/DAY :000000.62G
MAXIMUM MOUNTS/HR :000096
MAXIMUM MOUNTS/DAY :000213
EFFECTIVE COMPRESSION RATIO : 16.1 TO 1
AVERAGE MOUNT RESPONSE (SECS.) :000.003
-----------------------------------------------------------------------------------------
-----------------
DLm Utilities for z/OS Environment 17
Table 2. GENSTATS Throughput daily report fields
Field
YY/MM/DD
Description
Date of report, which is shown in the corresponding cell below the header. In this example,
Aug 26, 2015.
OUT xx
IN xx
MAXI+O/HR
TOT/DAY
OUT/DY
IN/DY
MAXO/HR
MAXI/HR
MOUNTS/DY
MAXMNT/HR
The output bucket, which is shown in the corresponding cell below the header. This is the total uncompressed GB written by the mainframe, during the specified hour. Hours 1–24 are represented by xx values 00–23.
The input bucket, which is shown in the corresponding cell below the header. This is the total uncompressed GB read by the mainframe, during the specified hour. Hours 1–24 are represented by xx values 00–23.
Maximum uncompressed GB read and written by the mainframe in any one hour bucket. In this example, the total I/O of 2 GB was observed in hour 14 (2.3 GB OUT plus 0.0 GB IN).
The total uncompressed GB read and written by the mainframe in the 24-hour period.
The total uncompressed GB written by the mainframe in the 24-hour period.
The total uncompressed GB read by the mainframe in the 24-hour period.
Maximum uncompressed GB written by the mainframe in any one hour bucket. In this example, 2 GB was observed in the hour 14 bucket.
Maximum uncompressed GB read by the mainframe in any one hour bucket. In this example, 0
GB was observed in hour 14.
Total virtual tape mounts observed in the 24-hour period.
The maximum number of virtual tape mounts observed in any one hour period.
Table 3. GENSTATS Throughput summary report fields
Field Description
Total virtual tape unloads during the range of days.
COUNT OF UNLOAD
RECORDS
COUNT OF UNLOADS W/
OUTPUT STATS
Total unloads during the range of days of virtual tapes that had been written to by the mainframe.
Total unloads during the range of days of virtual tapes that had been read by the mainframe.
COUNT OF UNLOADS W/
INPUT STATS
MAXIMUM OUTPUT/HR
MAXIMUM OUTPUT /DAY
MAXIMUM INPUT/HR
MAXIMUM INPUT/DAY
MAXIMUM
THROUGHPUT/HR
MAXIMUM
THROUGHPUT/DAY
MAXIMUM MOUNTS/HR
MAXIMUM MOUNTS/DAY
EFFECTIVE COMPRESSION
RATIO
Maximum uncompressed GB written by the mainframe in any one hour bucket during the range of days.
Maximum uncompressed GB written by the mainframe in any one day during the range of days.
Maximum uncompressed GB read by the mainframe in any one hour bucket during the range of days.
Maximum uncompressed GB read by the mainframe in any one day during the range of days.
Maximum uncompressed GB read and written by the mainframe in any one hour bucket during the range of days.
Maximum uncompressed GB read and written by the mainframe in any one day during the range of days.
Maximum virtual tape mounts in any one hour bucket during the range of days.
Maximum virtual tape mounts in any one day during the range of days.
The bytes written by the mainframe that is divided by the bytes written to back-end file systems over the range of days. This is the compression ratio that is achieved by one or more
VTEs. If the back-end file system resides on Data Domain and PowerProtect, this ratio is 1:1
(no compression is performed by the VTE).
18 DLm Utilities for z/OS Environment
Example 3: Detail report
Sample JCL:
//GO8 EXEC GENSTAT1,CMD=999,UNIT=(/F207,,,SMSHONOR), X
// REPORT='DETAIL'
Sample output
GENSTATS VER 1.28 Z1CWRK PARMS: DETAIL
------ Unload ----- ------ Channel ------ ---- File System ---- Duration Compression
Volser Date Time 4K Writes 4K Reads 4K Writes 4K Reads Time Percent
------ ---------- -------- ---------- ---------- ---------- ---------- ----------
----------
BFL503 2015/06/23 18:07:12 0000000001 0000000000 0000000001 0000000000 1071310800 00.0%
DV0001 2015/06/23 18:07:16 0000000001 0000000001 0000000001 0000000000 1071310796 00.0%
BFL503 2015/06/23 18:08:22 0000000001 0000000000 0000000001 0000000000 1071310800 00.0%
DV0002 2015/06/23 18:08:27 0000000001 0000000001 0000000001 0000000000 1071310795 00.0%
BFL501 2015/06/23 18:09:48 0000000001 0000000000 0000000001 0000000000 1071310799 00.0%
DV0005 2015/06/23 18:09:59 0000000001 0000000001 0000000001 0000000000 1071310789 00.0%
BFL501 2015/06/23 18:10:00 0000000000 0000000000 0000000005 0000000000 1071310799
DV0004 2015/06/23 18:11:33 0000005121 0000005121 0000000300 0000000000 1071310798 94.2%
BFL499 2015/07/28 11:08:38 0000000001 0000000000 0000000001 0000000000 1069485135 00.0%
BFL499 2015/07/28 11:08:51 0000000000 0000000000 0000000001 0000000000 1069485136
DV0003 2015/07/28 11:08:51 0000000001 0000000001 0000000001 0000000000 1069485123 00.0%
BFL499 2015/07/28 11:08:52 0000000000 0000000000 0000000001 0000000000 1069485136
FL499 2015/07/28 11:09:53 0000000001 0000000000 0000000001 0000000000 1069485135 00.0%
DV0008 2015/07/28 11:10:05 0000000001 0000000001 0000000001 0000000000 1069485124 00.0%
BFL499 2015/07/28 11:10:06 0000000001 0000000000 0000000001 0000000000 1069485136 00.0%
BFL499 2015/07/28 11:10:19 0000000000 0000000000 0000000001 0000000000 1069485136
DV0007 2015/07/28 11:10:19 0000000001 0000000001 0000000001 0000000000 1069485124 00.0%
….
BG0348 2015/09/02 11:52:15 0000005121 0000000001 0000000303 0000000000 1067614753 94.1%
BG0349 2015/09/02 11:53:00 0000010241 0000000001 0000000605 0000000000 1067614708 94.1%
BG0353 2015/09/02 11:53:01 0000005121 0000000001 0000000303 0000000000 1067614755 94.1%
BG0350 2015/09/02 11:53:36 0000015361 0000000001 0000000907 0000000000 1067614672 94.1%
BG0351 2015/09/02 11:54:14 0000020481 0000000001 0000001208 0000000000 1067614634 94.2%
BG0354 2015/09/02 11:54:15 0000010241 0000000001 0000000605 0000000000 1067614726 94.1%
BG0352 2015/09/02 11:54:41 0000025601 0000000001 0000001510 0000000000 1067614607 94.2%
BG0355 2015/09/02 11:55:10 0000015361 0000000001 0000000907 0000000000 1067614707 94.1%
BG0356 2015/09/02 11:55:46 0000020481 0000000001 0000001208 0000000000 1067614709 94.2%
BG0357 2015/09/02 11:56:05 0000025601 0000000001 0000001510 0000000000 1067614716 94.2%
BFL503 2015/09/02 11:58:32 0000000001 0000000000 0000000001 0000000000 1067614800 00.0%
BFL503 2015/09/02 11:58:44 0000000000 0000000000 0000000015 0000000000 1067614800
GENSTATS report filters
Any of the following optional parameters can be combined to filter the data in the report. These parameters are specified in
SYSIN DD statements, one option per line. If you choose to use these parameters in a procedure, you must specify them in a
GO.SYSIN DD statement because GENSTATS uses it in the GO step.
● DATEEND=yy/mm/dd : Excludes statistical information for records that are dated later than the date specified.
● DATESTART=yy/mm/dd : Excludes statistical information for records preceding the date that is specified.
● DAYCNT=xxxx : By default, GENSTATS processes up to 128 days of data. This parameter can be used to increase the number of days in the report. Available in GENSTATS Versions 1.11 and higher. The maximum value is 99999.
● DEVCNT=xxxx : By default, GENSTATS processes up to 2000 devices. This parameter can be used to increase the number of devices to process. Available in GENSTATS Versions 1.11 and higher. The maximum value is 99999.
● PATHCNT=xxxx : By default, GENSTATS processes up to 512 paths. This parameter can be used to increase the number of paths to process. Available in GENSTATS Versions 1.11 and higher. The maximum value is 99999.
● VOLCNT=xxxx : By default, GENSTATS processes up to 2200 VOLSERs. This parameter refers to a table containing
VOLSERs that are considered active which are mounted and never unloaded. Available in GENSTATS Versions 1.11 and higher. The maximum value is 99999. IMPORTANT notes about VOLCNT=xxxx: : The VOLCNT parameter determines the size of an in-memory table of VOLSERs in the GENSTATS execution. The default value for VOLCNT is 2200. When the number of VOLSER table entries that are needed in a GENSTATS execution exceeds the VOLSER table, GENSTATS fails with the following message:
DLm Utilities for z/OS Environment 19
GEN450I VOLSER TABLE OVERFLOW
NOTE: The above GEN450I message includes a count of the number of times this error was encountered. Adding this count with the VOLCNT used provides a new recommended VOLCNT parameter value. To avoid the above failure, it may be necessary to increase the VOLCNT parameter. Here are some ways to reduce GENSTATS processing:
○ Limit the amount of data that GENSTATS processes in one execution. Parameters for the starting and ending dates can be specified for both the collection of performance data on the DLm (Command Processor 998 and 999 processing), as well as runtime parameters to the GENSTATS execution.
Besides, parameters can be specified to filter what performance data, (.vstats files), is collected. These filter-related parameters, (VPATH, VMASK, and VDEPTH), are specified in the GENSTATP, GENSTAT1, and GENSTATW PROCs.
provide more information.
○ Another alternative is to sort the first 20 bytes of the input file into GENSTATS which will sort the input to
GENSTATS in date-time sequence. For GENSTATS processing of EFS File Systems where EFSMOVE is set to
RANDOM, this can reduce CPU usage.
● NODENAME=vtename : Filters the input data to select a particular VTE. This parameter is used for CP998 and ignored for
CP999 . An example is NODENAME=VTE1 . The parameter is not case-sensitive.
● PATHNAME=name : Filters the input data for a particular pathname or group of pathnames. This parameter is used for
CP998 and ignored for CP999 . The characters that are specified are matched against the pathnames of the input records. Only the characters that are specified, need to match for GENSTATS to accept a record. For example, if you specify PATHNAME=tapelib/G, and the VTE paths include tapelib/G0, tapelib/G1, and so on, all the tapelib/Gx records are processed. The parameter is case-sensitive.
● SYNCTIME=hh:mm:ss : This parameter can be used with the STILLINUSE report to specify (along with DATEEND ) the point at which the STILLINUSE check is applied. Besides, tapes that are mounted after SYNCTIME is listed for user evaluation purposes. Available in GENSTATS Versions 1.09 and higher.
DLMCP utility
This section provides an overview of DLMCP utility.
DLMCP utility allows you to run Command Processors directly using PSF/RSD CCWs.
DLMCP sends CP command to the VTE, obtains the CP report to the host, and prints the report using PSF/RSD CCWs without using BFL volumes.
DLMCP utility input
1.
DEV = parameter in PARM field specific control device number to send command and obtain output . Control device must be specific offline device and should not be used by other utilities.
2.
LOGFILE parameter in PARM field forces DLMCP to print report to the data set specified in the DLMCPRPT DD statement.
By default, when LOGFILE parameter is not passed, the report is printed to the SYSLOG using WTO .
3.
DLMCPCMD DD statement must point to the data set containing RUNWAIT command without report_dir_path and report_file_name parameters to run Command Processor; LRECL<=256 .
4.
DLMCPRPT DD statement must point to the data set when LOGFILE parameter is specified, where report should be printed;
LRECL=264 , RECFM=FB .
DLMCP return codes
This section provides a list of DLMCP return codes and their description.
Table 4. DLMCP Return Codes and Description
Return codes
RC=00
RC=04
Description
Utility executed successfully and CP completed successfully.
Utility executed successfully, CP completed with warning.
20 DLm Utilities for z/OS Environment
Table 4. DLMCP Return Codes and Description (continued)
Return codes
RC=08
Description
Utility executed with error.
RC=12
RC=16
Utility executed successfully, CP completed with error.
Utility executed with serious internal error.
Example
DLMSCR utility
This section provides an overview of DLMSCR utility.
DLm provides the DLMSCR utility that you can use with any of the major tape management systems to keep your TMS scratch status synchronized with the DLm scratch status.
You can also use DLMSCR to scratch tapes in DLm without a Tape Management System.
Scratching tapes in DLm without a
provides more details on how to scratch tapes without a Tape Management System.
DLMSCR runs on the mainframe and sends volume scratch requests to DLm. As the TMS may dynamically release tapes back to scratch status, you must regularly run DLMSCR to maintain synchronization between the TMS catalog and DLm. To use
DLMSCR, you must run a TMS scratch report and input that scratch report into DLMSCR. DLMSCR scans the scratch report for the DLm-owned volumes and sends the appropriate scratch requests to DLm.
NOTE: You can run only one DLMSCR at a time on a DLm. Do not run more than one DLMSCR simultaneously, whether on the same VTE or on different VTEs within the DLm.
Link the DLMSCR utility as an authorized program into an authorized library under the name DLMSCR. Dell Technologies recommends that you use security software, such as Resource Access Control Facility (RACF), to restrict the use of DLMSCR to authorized users only.
A sample of the JCL required to link DLMSCR is found in the LNKSCR member of EMC.DLMS<version>.SAMPLIBU.
A sample of the JCL required to run DLMSCR is found in the RUNSCRA and RUNSCRB members of
Running the DLMSCR utility
Use the following JCL to run the DLMSCR Utility:
//SCR EXEC PGM=DLMSCR,PARM='<SCR parameters>'
//STEPLIB DD DISP=SHR,DSN=your.DLm.library
//DLMLOG DD <SCR output>
//DLMCTRL DD <SCR control device>
//DLMSCR DD <SCR input>
For more information about these parameters, see the following sections:
●
for <SCR parameters>
●
Scratch utility output for <SCR output>
●
Scratch utility control device for <SCR control device>
●
for <SCR input>
DLm Utilities for z/OS Environment 21
DLMSCR parameters
This section provides an overview of DLMSCR parameters.
Table 5. Parameters in DLMSCR
Parameters
TYPE=x
Description
Where x is used to select the tape management system. Valid types include RMM, RMMDV, TLMS, TMS, TSM, ZARA, CTLM, AFM, or
CTLT. This is the only required parameter.
NOTE: DLMSCR expects a specific input for each TYPE.
provides more details.
PREFIX=y
PREFIXLN=n
NODSNCHK
FREESPACE
FREEAFTERSCR
NODATECHK
Where y is a string of prefix characters that limits processing to volumes whose VOLSER begins with the characters specified.
Unless otherwise specified by the PREFIXLN parameter, the default prefix length is 2. For example, PREFIX=AAABAC causes DLMSCR to process only volumes whose serial numbers begin with AA, AB, or AC. Coding this parameter prevents DLMSCR from trying to unnecessarily scratch volumes that are not stored on DLm. If no
PREFIX is specified, DLMSCR processes the entire scratch list.
Where n can be a single digit between 1 - 5. This value replaces the default prefix length of 2 for the PREFIX= parameter.
PARM='PREFIX=ABCD,PREFIXLN=1' causes DLMSCR to process only volumes whose serial numbers begin with A, B, C, or D.
DLm validates dataset names (dsname) if found in the scratch report as part of the scratch process. A scratch is not successfully completed if the dsname in the scratch report does not match the dsname in the HDR1 label on the volume being scratched.
NODSNCHK prevents the dataset name check from being performed and is not recommended for normal use.
By default, DLMSCR reclassifies volumes being scratched as eligible for scratch allocation requests, without freeing the space occupied by that volume. The FREESPACE parameter may be used to request that the space be freed. FREESPACE requires the volumes to already be in scratch status. To use DLMSCR to free the space, DLMSCR must be run twice. The first execution must run without the FREESPACE parameter to scratch the volumes, and the second execution must run with the FREESPACE parameter to release the space. Keep in mind that DLm automatically frees the space of scratched volumes when it needs space. So, it is not necessary to run DLMSCR with the FREESPACE parameter.
DLMSCR FREESPACE deletes the data on the scratch tape immediately, and the data is not recoverable if run by mistake.
While the FREESPACE parameter requires that a volume already be in a scratched state, FREEAFTERSCR frees space from a volume immediately after DLMSCR has scratched it, within a single run of
DLMSCR. Once FREEAFTERSCR frees the space that is associated with the execution of DLMSCR, the volume cannot be recovered if it was scratched by mistake.
NOTE: Do not use this parameter when you scratch WORM tapes. WORM tapes are automatically erased when they are scratched. Using this parameter causes the request to be rejected as the WORM tape is already erased.
DLm checks the creation date of a tape volume and does not allow any volume to be created and scratched in the same 24-hour period. Setting this parameter allows volumes to be created and scratched within 24 hours. This parameter ignores the default date check-in DLMSCR.
22 DLm Utilities for z/OS Environment
Table 5. Parameters in DLMSCR (continued)
Parameters
IGNLCSERR
IGNMINORERR
ALLVOLS
IGNLCSRC4
NOTCDB
NOTIFSCR
TEST
DEV=xxxx
USETMC
SYNC
TERMIFRS
Description
IGNLCSERR ignores any errors reported by Library Call Subsystem
(LCS) used by OAM with the MTL volumes. DLMSCR logs any error that is returned by LCS and stops processing scratch tapes when one of these errors occurs. If this parameter is set, DLMSCR scratch processing continues even when the LCS errors are encountered.
IGNMINORERR allows DLMSCR to continue processing even after receiving a 'REQUEST REJECT - CREATED OR MODIFIED TOO
RECENTLY' error. It ensures a return code of 0 rather than 4.
ALLVOLS allows scratch of volumes with report dsnames of hex zeros or blanks.
IGNLCSRC4 allows DLMSCR processing to continue after receiving a return code of 4 from LCS processing. It terminates if the return code from LCS processing is greater than 4.
This prevents DLMSCR from attempting any TCDB updates. This should be used only if the TMS already performs this function.
This prevents DLMSCR from attempting to change theTCDB use attribute to scratch if DLm reports that the VOLSER was already scratched.
This parameter allows for testing — no actual changes is performed.
DEV=xxxx allows the specification of an offline virtual tape device and the elimination of the DLMCTRL DD statement. The “MTL considerations for VTE drive selection” section in the DIsk Library for mainframe User Guide contains an example.
For CA-1 TMS environments only. This parameter enables DLMSCR to directly read the CA-1 Tape Management Catalog (TMC) to find DLm-resident VOLSERs which have been scratched and send the appropriate scratch requests to DLm for processing. Use of the USETMC option requires that the DLMSCR DD JCL statement point directly at the TMC or a copy of the TMC.
SYNC is for CA-1 TMS environments only. The parameter is valid only if specified along with the USETMC parameter. It enables
DLMSCR to synchronize the status of the VOLSERs in the Tape
Control Data Base (TCDB) and the DLm library with those in the
CA-1 TMC.
TERMIFRS terminates DLMSCR processing if DLMSCR receives a warning return code, (4), from CBRXLCS and the reason code exceeds 5.
Scratch utility input
DLMSCR considerations
Note these considerations when working with the DLm scratch utility:
● The DLMSCR file must point to the scratch report that you have created using the appropriate TMS utility. Generate the scratch report with a logical record length (LRECL) of 133.
● DLMSCR scratch report consideration: DLMSCR expects unique input for each TMS (parameter TYPE=). See corresponding
<TYPE> considerations section below for the details about DLMSCR input format. For TYPE=RMMDV (no-TMS), the required input is described in
Scratching tapes in DLm without a TMS
.
DLm Utilities for z/OS Environment 23
● To avoid any confusion, use a single job to generate a current scratch list file and run the DLMSCR utility against that file.
This eliminates the possibility of accidentally running the DLMSCR program against an old scratch report and causing the
TMS and DLm to be out of sync.
● For WORM tapes that need to be scratched using DLMSCR, you must enable FLR or DDRL for the control device in the
Devices > VTEx tab of DLm Console.
● DLm does not scratch a volume that is created on the current day unless NODATECHK is specified. Also, the utility does not run against a scratch report that was not created the same day.
● The Scratch utility uses the dsname information from the scratch report to verify the volumes being scratched. If the dsname written in the volume header does not match the dsname on the scratch report for that volume, the scratch request is rejected. This action can be overridden by NODSNCHK.
● After completing the DLMSCR utility, you can use or reuse tapes that the utility successfully scratched.
RMM considerations
Observe the following rules when using DLm with RMM:
● Predefine the DLm scratch volumes to RMM. If you have not predefined DLm VOLSERs as scratch in RMM, RMM rejects the new volumes, which result in an unsatisfied mount request on the mainframe. To resolve the unsatisfied mount, define the DLm volsers as scratch in RMM, and run a LOAD command at the appropriate VT console to satisfy a stalled request.
● When defining a new DLm scratch tape to RMM, set the initialize option to no. If you select yes and RMM detects that the volume must be initialized (or EDGINERS is run), RMM sends a request to mount a 'blank' VOLSER on a DLm device. DLm is not automatically ready as it cannot recognize which volume to mount. Therefore, you must use the LOAD command at the
VT console to manually mount each volume being initialized.
● DLMSCR processes two types of RMM scratch reports:
○ The scratch report that EDGRPTD creates.
○ The scratch report that EDGJRPT creates using the EDGRRPTE exec (EDGRPT01). Use the DATEFORM(I) parameter when running EDGRPTD to create scratch reports to ensure that the expected date format is used. When the REXX exec form is used, DLMSCR may not accept a user-tailored version of EDGRRPTE.
TMS considerations
DLMSCR expects Report-05, Report-06, or Report-87 to be used.
TLMS considerations
DLMSCR expects either the TLMS003 or the TLMS043 report as input.
TSM considerations
DLMSCR expects a Tivoli Storage Manager (TSM) Volume History Report to be used as input to the DLMSCR DD.
Control-M Tape considerations (TYPE=CTLM)
DLMSCR expects a CTTRFSCR Full-scratch report that is produced by CTTRPT utility to be used as input to the DLMSCR DD.
Control-M/Tape sample JCL —REPFSCR could be used to produce CTTRFSCR (full-scratch) report.
This report could be filtered by Media type and/or Pool Name using INCLUDE and EXCLUDE statements.
NOTE: See INCONTROL for z/OS Utilities Guide for more information.
24 DLm Utilities for z/OS Environment
Control-T considerations (TYPE=CTLT)
DLMSCR expects a Scratch report produced by CTTRTM utility at the end of processing.
ZARA considerations
DLMSCR expects the LIST SCRATCH type of scratch report to be used as input from ZARA.
CA-1 considerations
This section provides an overview of CA-1 considerations.
Although there are various reports that are supported by TMS (CA-1), DLMSCR expects Report-05 or Report-06 or Report-87 to be used.
The report generation parameters should request the field DSN17 instead of the default DSN. (See PRIMUS EMC204223.)
Otherwise, the report for multi-volume multi-file tapes has the incorrect DSN for all but the first VOLSER. Those volumes with incorrect DSN fail the DSN validity check that is performed by DLMSCR before scratching a tape.
Unique to CA-1 TMS environments only, DLMSCR supports the following two extra run time parameters:
● USETMC — When this parameter is specified, DLMSCR directly reads the CA-1 Tape Management Catalog (TMC) to find
DLm-resident VOLSERs which have been scratched. A separate execution of the CA-1 scratch report utility (EARL) is not required. Use of the USETMC option requires that the DLMSCR DD JCL statement point directly at the TMC (or a copy of the TMC). DLMSCR scans the TMC and sends the appropriate scratch requests to the DLm for processing.
NOTE: When using the USETMC option, DLMSCR sends a scratch request for any scratch volume (those that pass prefix filtering) it finds in the TMC. This might result in a large number of DLm0500I messages followed by DLm0524W messages being issued to the DLm VTE btilog whenever DLMSCR is run. This is normal. The DLm0500I message indicates that the VTE application has received a request to scratch a VOLSER. The DLm0524W message indicates that the VOLSER was already scratched.
● SYNC — This parameter is valid only if specified along with USETMC. The SYNC option causes DLMSCR to synchronize the
Tape Control Data Base (TCDB) and the DLm library with the CA-1 TMC. The status of the VOLSERs in the TCDB and in the DLm library will be changed from active to scratch or from scratch to active as required to match the status of the CA-1
Tape Management Catalog (TMC).
NOTE: When using the SYNC option DLMSCR sends an unscratch request for any active volume, it finds in the TMC.
This may result in a large number of DLm0500I messages followed by DLm0524W messages being issued to the VTE log whenever DLMSCR is run. This is normal. The DLm0500I message indicates that the VTE application has received a request to unscratch a VOLSER. The DLm0524W message indicates that the VOLSER was already unscratched.
Dell Technologies recommends that you use the SYNC option only periodically to clean up the occasional mismatch. Using SYNC frequently can impact performance.
The following table, lists the differences between using SYNC and a normal scratch report:
Table 6. Differences between SYNC and normal scratch report
Using SYNC
Every VOLSER that passes filtering results in either a scratch or an unscratch request to the DLm.
Not using SYNC
Only the VOLSERS in the scratch list result in a call to the
DLm. (# of calls = # of tapes in scratch status)
Every VOLSER that passes filtering, and the control device is in an MTL, results in a call to OAM's LCS process to verify the status unless NOTCDB is specified.
Only VOLSERS that successfully scratch, and the control device is in an MTL, result in a call to OAM's LCS process, unless NOTCDB is specified. (# of calls = # of tapes successfully scratched)
TMS users who use Scratch Pool Management and need to limit the eligible scratch volumes to a limited range of VOLSERs must install the TMS usermod CL05219 (CTSMSGEX exit). When this exit is linked into IGX00030, an IPL with CLPA is required to activate it. The exit causes the first 8 characters of the scratch poolname to be placed into the Load_Display mount message that is sent to the tape drive. This poolname can be defined as a scratch synonym so that the VTE application software can restrict the eligible scratch volumes to a specific prefix group.
DLm Utilities for z/OS Environment 25
Scratch utility output
DLMLOG considerations
This section provides an overview of DLMLOG considerations.
The DLMLOG file maintains a history of the results of each delete request. The file should have a logical record length (LRECL) of 133.
If an error occurs during a scratch request (such as scratching a non-existent volume), the failure is recorded in the log file.
DLMSCR report output messages
This section describes the DLMSCR report output messages.
NOTE: ALL messages precede by MM/DD/YYYY HH:MM:SS VOLUME XXXXXX. The hex codes that are listed are the error codes that the VTE returns to DLMSCR when DLMSCR requests an action on a volume.
Table 7. DLMSCR report output messages
Hex Code
0x01
0x02
0x05
0x06
0x07
0x08
Volume Rejected Message
REQUEST REJECT - INVALID LOAD/
DSPLY
Comments
Invalid data length (must be 17 bytes, 23 bytes, or 40 bytes).
Volume is already scratched.
REQUEST REJECT -ALREADY A
SCRATCH
REQUEST REJECT - INVALID VOLSER Invalid VOLSER specified—The input volume serial number does not conform to the standard volume naming convention. Check the input TMS report.
REQUEST REJECT - VOLUME IN USE Volume is mounted on another drive on this VTE.
REQUEST REJECT - VOLUME NOT
FOUND
REQUEST REJECT - I/O ERROR
Volume is not found in file system.
Ensure input tape device number hovers over correct tape library (that is, / tapelibxxx).
I/O error has occurred during scratching process—see btilog for additional information.
0x09
0x0A
0x0B
0x0C
0x0D
REQUEST REJECT - VOLSER LOCKED File is locked—volume might be in use by another tape drive on this VTE or another VTE or there is a possibility of a STALE LOCK.
REQUEST REJECT - DIRECTORY
PROBLEM A
Tape library directory is not accessible—
Verify tape unit that is selected for utility hovers over correct tape library.
REQUEST REJECT - DIRECTORY
PROBLEM B
REQUEST REJECT - INVAL/MISSING
VOL1
Tape library directory is not writable—
Verify that tape library is marked for
Read/Write.
Invalid or missing VOL1 label in volume
—Using AWSPRINT verify that volume
VOL1 record has not been overwritten.
REQUEST REJECT - VOLSER
MISMATCH
Volume serial number from the TMS report and the VOL1 label on the tape do not match; VOL1 label might have been overwritten.
26 DLm Utilities for z/OS Environment
Table 7. DLMSCR report output messages (continued)
Hex Code
0x0E
Volume Rejected Message
REQUEST REJECT - INVAL/MISSING
HDR1
0x0F
0x10
0x11
0x12
REQUEST REJECT - MISMATCHING
DSNAME
REQUEST REJECT - INVALID DATE
PASSED
REQUEST REJECT - CREATED OR
MODIFIED TOO RECENTLY
REQUEST REJECT - FILE NOT
WRITEABLE
Comments
Invalid or missing HDR1 label in volume—
The HDR1 record is not in the correct format; overlayed because of error; use
AWSPRINT utility to determine error.
The dataset name in the TMS report does not match the dataset name in the
HDR1 label on the tape; use AWSPRINT utility to determine error.
TMS input report date does not match the execution date of DLMSCR.
Date mismatch—DLMSCR defaults to no scratch same day unless overridden using NODATECHK.
File not writable—The file system directory is probably marked as Read
Only. This might be target site.
Scratch utility control device
This section provides an overview of scratch utility control device.
The DLMCTRL file allocates a DLm tape device for use as a control path to pass the scratch requests. If multiple tape libraries in the DLm are being used to contain the DLm virtual volumes, you must select a tape device address that is associated with the library in the DLm containing the volumes to be scratched. The device that is selected must be associated with a library and associated file systems that are READ/WRITE and not READ ONLY.
The DEV=xxxx parameter allows an offline tape device to be used instead of coding the DLMCTRL DD statement. For example, see RUNSCRB in the sample JCL library.
The following are some important DLMCTRL considerations:
● DLMCTRL must point to a tape drive on the DLm. It should always point to the same tape (explicitly or by cataloged dataset), because otherwise it allocates a new scratch tape each time.
● It also must NOT point to an existing tape, because the tape is wiped out when the program runs.
● If you cannot mount a scratch tape by name (MTL or other site restriction), omit the VOLSER when the job is first run, then use the same tape, either through the catalog or through explicit reference to the VOLSER, on subsequent runs.
● DLMCTRL can be replaced by using an OFFLINE tape drive address (when using this device, it must be OFFLINE to all
LPARs associated with it.
● Other special considerations for DLMCTRL:
○ If all access to the DLm is through the MTL, then DLMCTRL must also reference the MTL, whether through an esoteric or a storage group.
○ If the DLm has multiple libraries (not all drives use subdirectories under /tapelib), DLMSCR must be run separately for each library, each time using a drive in the applicable library.
Scratching tapes in DLm without a TMS
This section provides an overview of Scratching tapes in DLm without a TMS.
You can use DLMSCR to scratch tapes in DLm without a TMS by using the special parameter, RMMDV. RMMDV instructs the program to look for a special input rather than a scratch report from a Tape Management System.
Run the job with the following JCL:
//SCR EXEC PGM=DLMSCR,PARM='TYPE=RMMDV'
//STEPLIB DD DISP=SHR,DSN=your.DLm.library
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=MTL,VOL=SER=BT9999,
DLm Utilities for z/OS Environment 27
The input to DLMSCR consists of one or more of the following starting in column 1:
RMM DV xxxxxx FORCE
RMM DV xxxxxx FORCE xx...xx
RMM DV xxxxxx FREE
RMM DV xxxxxx UNSCR
RMM DV xxxxxx DELETE
RMM DV xxxxxx DELETE xx...xx
Where:
● RMM DV is a necessary value for this use of the program.
● xxxxxx is the VOLSER being processed.
● xx...xx
is the DSN (to be validated). If not given, no validation is done.
● FORCE scratches the tape.
● FREE frees the space of a scratched tape (the tape must have been SCRATCHed previously).
● UNSCR unscratches a scratched tape (assuming it has not been FREE'd or reused).
● DELETE deletes the freed tape from the file system on the DLm.
When an MTL Library is involved, there are several documented DLMSCR options that can be used to either prevent the
TCDB updates, or to ignore errors depending on the individual situation. The primary option to use is NOTCDB if the volume is removed via the above DLMSCR and reinserted by the DLm INITIALIZE command.
DLMCMD utility
The DLMCMD utility allows you to run DLm commands from the mainframe.
Link this utility as an authorized program to an authorized library under the name DLMCMD. It is highly recommended that you use security software, such as RACF, to restrict the use of DLMCMD to authorized users only.
DLm Command Processors make use of DLMCMD using PROCs such as DLMCPRUN, DLMCMDPR, DLMCMDP1, DLMCMD49,
GENSTAT1, GENSTATW, and GENSTATP. Dell Technologies recommends the use of the above Command Processor PROCs to run the various Command Processor reports and Commands.
This section provides an example of the JCL required to run DLMCMD. The sample JCL is found in the RUNCMDA and
RUNCMDB members of EMC.DLMS<version>.SAMPLIBU. RUNCMDB illustrates the use of the DEV= parameter.
Downloading and using DLm z/OS components
provides download instructions.
How the DLm command utility works:
● The DLMCMD utility reads one or more DLm commands from the DLMCMD input file, and sends each command to DLm for execution.
NOTE: The DLMCMD utility accepts input cards up to 256 characters in length. Continuation lines are not allowed.
Indication of success or failure is logged to the file to which the DLMLOG DD statement points.
NOTE: Any messages and other textual results of the command that display on the DLm Console are not returned to the host. DLMCMD does not respond to a mainframe command on the communication tape device until the VTE processing for that command is complete.
● Use the DLMCTRL file to allocate a DLm device for use as a control path for passing the DLm commands. You can use any available DLm virtual tape device as the DLMCTRL device. The “MTL considerations for VTE drive selection” section in the Disk Library for mainframe User Guide provides information about working with a Manual Tape Library. The DEV=xxxx parameter allows an offline tape device to be used instead of coding the DLMCTRL DD statement. See RUNCMDB in the sample JCL library for an example.
● The DLMCMD DD statement should point to a list of DLm commands to be sent. The LRECL of DLMCMD cannot exceed
256. Create it using the NONUM ISPF edit option to avoid sequence numbers at the end of the command line, which would otherwise be taken as part of the command. This can optionally be an in-stream input file (DLMCMD DD *) of commands.
● The DLMLOG DD statement points to a sequential file for logging the DLMCMD results. This file should have a logical record length (LRECL) of 133. If an error occurs during command processing, the failure is recorded in the log file, and a non-zero return code from DLMCMD results.
DLMCMD error messages lists the possible error codes from DLMCMD. This is a sample
DLMLOG output:
DLMCMD VER 1.0 DLMCTRL = EA82
2004/09/10 12:47:49 CMD ERR=FF: this is an invalid command
2004/09/10 12:47:49 CMD ISSUED: q all
28 DLm Utilities for z/OS Environment
2004/09/10 12:47:49 CMD ERR=FC: q xxxxxxxx
2004/09/10 12:47:49 CMD ISSUED: set size=2g dev=EA80
● The alternative methods to pass commands to DLMCMD are:
○ Use of PARM='WTOR' — Sends the message DLC070I, ENTER COMMAND, to the operator, who can reply with the command. The message is reissued after each command is accepted until END is entered as the reply. This method does not use the DLMCMD input file. For example,
//LOG EXEC PGM=DLMCMD,PARM='WTOR'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=478F,VOL=SER=BT9999,DISP=(,KEEP)
○ Use of PARM='CMD='— Allows you to pass a single command on the EXEC card instead of using the DLMCMD input file. This method also allows you to call DLMCMD from another program, and pass the command as an entry parameter.
For example:
//LOG EXEC PGM=DLMCMD,PARM='CMD=Q SPACE'
//DLMLOG DD DSN=DLM.LOGFILE,DISP=OLD
//DLMCTRL DD DSN=DLM.CTRL,UNIT=478F,VOL=SER=BT9999,DISP=(,KEEP)
NOTE: If you experience issues on the VTE for the DLm device with the DLMCMD, check the /var/log/bti/btilog file for error messages.
○ Use of PARM='TIMEOUT='— Allows you to specify the time in seconds, (nnn), that DLMCMD waits for the command to be completed. If the command is not completed in the number of seconds specified, the DLMCMD job step terminates with condition code of 12 and the following message will be written to the DLMLOG DD:
DLM080I COMMAND TIMED OUT – TERMINATING
For example:
//GO EXEC DLMCMD,PARM='TIMEOUT=600'
NOTE: In the above example, DLMCMD terminates with a condition code of 12 if the job step has not completed in 600 seconds. You can also specify the maximum time that DLMCMD waits when using the RUNWAIT command.
When both the TIMEOUT= parm is specified and the RUNWAIT command also specifies a time limit, then whichever time limit expires first terminates the DLMCMD job step. If the DLMCMD job step is terminated as a result of the RUNWAIT time limit, then the DLMCMD job step terminates with a condition code of 4 and in the DLMCMD
DLMLOG DD output, you see the following error message: CMD ERR=FB.
DLMCMD error messages
This section provides an overview of DLMCMD error messages.
Table 8. Error code from DLMCMD
Error code
0x01
0x02
0xFF(-1)
0xFC (-4)
Description
Invalid data length (must be between 1 and 256 bytes).
DLm does not accept Host-initiated console commands. This error code is generated when the HOSTCOMMAND option is set to NO in the VTE configuration. To enable it, you must remove HOSTCOMMAND NO from the configuration.
A general syntax error occurred. (The DLm console error message "DLm0891E: Invalid command syntax" was displayed.)
An "E" level error other than general syntax error occurred. (A console error message other than DLm0891E was displayed.)
DLm Utilities for z/OS Environment 29
Table 8. Error code from DLMCMD (continued)
Error code
0xFB (-5)
Description
This value is returned if the RUNWAIT command is ran using
DLMCMD, and the command does not finish in the wait time specified.
DLMVER utility
The DLMVER utility reports the versions of the DLm mainframe modules on the mainframe:
● DLMCMD
● DLMLIB
● DLMSCR
● DLMVER
● GENSTATS
● DLMHOST
● DLMWTOR
The sample JCL is found in the DLMVER member of installed SAMPLIBU library.
Downloading and using DLm z/OS components
provides download instructions and additional information.
DLMVER Messages
The messages related to DLMVER are:
● DLV010I UTILITY VERSIONS ( ):
● DLV050I LOG FILE FAILED TO OPEN
DLMWTOR utility
DLMWTOR is a z/OS utility that provides a means to obtain a z/OS operator confirmation that a proposed action is to be performed. This utility provides a safe guard against unauthorized or mistaken job executions.
DLMWTOR is included with the DLMDRC (DLm Disaster Recovery Client), feature of DLm. However, it can be used along with other DLm actions such as executing a DLm VTE command.
The following sample is provided with the SAMPLIBU samplib as member DLMWTOR2:
//JOBNAME JOB (MYJOB)
//*
//GO EXEC PGM=DLMWTOR
//STEPLIB DD DSN=user.LOADLIB,DISP=SHR
//SYSABEND DD SYSOUT=*
//WTOLINES DD * wtor message lines- up to 10 lines
//*
To use the DLMWTOR utility, insert the above sample JCL into the job stream that you need to require an z/OS Operator confirmation. Modify the STEPLIB DD to point to the installed DLm LOADLIB. DLMWTOR does not have to be APF Authorized.
Enter the operator prompt that you wish to specify. When invoked, DLMWTOR presents the message lines to the z/OS Console log. Up to 10 lines can be displayed.
The operator is instructed to reply YES or CANCEL. Replying YES results in a condition code of 0 to be returned from the
DLMWTOR job step. Replying CANCEL results in a condition code of 8 to be returned.
Code subsequent job steps to execute only if a condition code of 0, (YES), is returned from the DLMWTOR job step.
Here is an example:
//GO EXEC PGM=DLMWTOR
//STEPLIB DD DSN=RGREEN7.DLM.LINKLIB,DISP=SHR
30 DLm Utilities for z/OS Environment
//SYSABEND DD SYSOUT=*
//WTOLINES DD *
DLMC800W DLMDR VG8HALT REQUESTED FOR'
IP: 99.999.99.99 PORT: 8888'
*-------------------------------------*
* ALL TAPE DRIVE ACTIVITY MUST BE *
* QUIECED PRIOR TO THIS ACTION. *
* *
* FAILURE TO QUIECE ALL TAPE ACTIVITY *
* CAN RESULT IN DATA LOSS AND/OR *
* UNPREDICTABLE RESULTS *
*-------------------------------------*
//*
//DLMHALT EXEC DLMDRC,IP=’99.999.99.99’,PORT=8888,
// CMD=VG8HALT,PARMS='VG8-1,CHECK',
// COND=(0,NE)
SDSF output example:
15.48.54 J0013777 IEF403I RGDLMDR2 - STARTED - TIME=15.48.54
15.48.54 J0013777 +DLMC800W DLMDR VG8HALT REQUESTED FOR' 703
703 IP: 99.999.99.99 PORT: 8888'
703 *-------------------------------------*
703 * ALL TAPE DRIVE ACTIVITY MUST BE *
703 * QUIECED PRIOR TO THIS ACTION. *
703 * *
703 * FAILURE TO QUIECE ALL TAPE ACTIVITY *
703 * CAN RESULT IN DATA LOSS AND/OR *
703 * UNPREDICTABLE RESULTS *
703 *-------------------------------------*
15.48.54 J0013777 @0026 DLMWI001 DO YOU WISH TO CONTINUE? REPLY YES OR CANCEL
15.50.46 J0013777 R 26,MAYBE
15.50.46 J0013777 @0027 DLMWE002 UNKNOWN ANSWER, REPLY YES OR CANCEL
15.50.55 J0013777 R 27,CANCEL
15.50.56 J0013777 RGDLMDR2 GO DLMWTOR 0008 2 0 0
15.50.56 J0013777 RGDLMDR2 GO IKJEFT01 FLUSH 0 0 0
15.50.56 J0013777 IEF404I RGDLMDR2 - ENDED - TIME=15.50.56
15.50.56 J0013777 RGDLMDR2 RC 0008 ET 00:02:01 IO 2 CP .0/ .0
15.50.56 J0013777 $HASP395 RGDLMDR2 ENDED z/OS log output example:
$HASP373 RGDLMDR2 STARTED - INIT 6 - CLASS A - SYS H15
IEF403I RGDLMDR2 - STARTED - TIME=15.48.54
+DLMC800W DLMDR VG8HALT REQUESTED FOR' 703
IP: 99.999.99.99 PORT: 8888'
*-------------------------------------*
* ALL TAPE DRIVE ACTIVITY MUST BE *
* QUIECED PRIOR TO THIS ACTION. *
* *
* FAILURE TO QUIECE ALL TAPE ACTIVITY *
* CAN RESULT IN DATA LOSS AND/OR *
* UNPREDICTABLE RESULTS *
*-------------------------------------*
@0026 DLMWI001 DO YOU WISH TO CONTINUE? REPLY YES OR CANCEL
R 26,MAYBE
IEE600I REPLY TO 0026 IS;MAYBE
@0027 DLMWE002 UNKNOWN ANSWER, REPLY YES OR CANCEL
R 27,CANCEL
IEE600I REPLY TO 0027 IS;CANCEL
RGDLMDR2 GO DLMWTOR 0008 2 0 0
RGDLMDR2 GO IKJEFT01 FLUSH 0 0 0
IEF404I RGDLMDR2 - ENDED - TIME=15.50.56
In the above example, job RGDLMDR2 was submitted. The operator was instructed to reply YES or CANCEL to proceed. An incorrect Reply of MAYBE was entered which was not accepted. A reply of CANCEL was then entered and caused the job to terminate because of the condition code clause on the subsequent DLMHALT job step.
DLMHOST utility
DLMHOST is a host utility that provides z/OS Console Operation support.
It is used to communicate between a single logical partition's (LPAR) operator console and the DLm.
DLm Utilities for z/OS Environment 31
To use the DLm z/OS Console operation, you must install the z/OS DLMHOST utility and then configure the individual VTEs to communicate with it. Using the DLm Console program, you can configure which type (informational, warning, or error) of messages and/or which specific DLm messages are sent over the channel to the mainframe. For details about configuring the messages, see the section “Sending messages to z/OS” > “Configuring messages and recipients” in the Disk Library for mainframe User Guide .
The DLMHOST utility runs as a started task, and accepts commands from the operator. By default, DLMHOST uses Write-to-
Operator-with-Response (WTOR) capabilities for sending DLm commands. The requests to DLm are through WTOR, and the logging from DLm is through Write-to-Operator (WTO). Optionally, you may configure DLMHOST to use the z/OS MODIFY function in place of WTOR.
At startup, DLMHOST reads a configuration file that defines the VTEs to be supported as well as the device addresses, per
VTE, to be used for communication and logging. Each DLm VTE is identified with a unique name so that commands can be targeted to specific VTEs. A tape drive device address must be selected from each VTE's range of addresses that is used as the command/communication path. A second device address is required on each VTE if you want DLm to send log messages to the z/OS console. These devices will not be eligible for allocation once DLMHOST has been started.
Only log messages that have passed message filtering is received by the host.
It should be noted that, depending upon the filtering options set on the VTEs, there may be many log messages that are sent to the consoles. Optionally, DLMHOST supports a configuration option to send the messages to a host file instead of the operator's console.
DLMHOST installation
This section provides an overview of DLMHOST installation.
DLMHOST is only supported in a single Logical Partition (LPAR). You cannot connect multiple DLMHOST tasks running in multiple LPARs to the same DLm VTE.
DLMHOST is distributed in the LINKLIB.xmi and the package is available on the support website.
Downloading and using DLm z/OS components provides more details.
The DLMHOST utility must be linked as an authorized program into an authorized library under the name DLMHOST. It is highly recommended that RACF be used to restrict the use of DLMHOST to authorized users only.
Running DLMHOST
This section provides an overview of running DLMHOST.
Use the following JCL to run DLMHOST:
//DLMSTEP EXEC PGM=DLMHOST,PARM='parameters'
//DLMCFG DD DSN=PARMLIB(nodecfg),DISP=SHR
//DLMLOG DD DSN=logfilename,DISP=SHR
//* THE FORMAT OF THE CONFIG FILE IS AS
//* FOLLOWS:
//* Col 1 -10 Nodename
//* Col 12-15 Command path device address
//* Col 17-20 Log path device address
The parameters then can be specified are:
● DOCMDS — Requires the use of a DLMCMD DD card pointing to a file of commands that are to be processed during
DLMHOST startup. The commands should be in the same format as used in modify or WTOR processing.
NOTE: EOJ can be specified as the last command to terminate DLMHOST after a series of commands.
● NOLOG — Prevents DLMHOST from receiving continuous log data from any VTE. Set this parameter if you plan to use
DLMHOST only to send commands from the z/OS Console to the DLm. Command responses are returned even when
NOLOG is specified.
● NOWTOR — Prevents DLMHOST from issuing the normally outstanding WTOR. When this parameter is specified, DLm commands can be issued using the z/OS MODIFY command as the method of communication in place of WTOR.
● LOGFILE — Causes any received log data from the DLm system to be recorded in the file pointed to by the DLMLOG DD card. When LOGFILE is specified, the log messages are not sent to any console via WTO. If LOGFILE is not specified, the
DLMLOG DD card is not required in the JCL. The LOGFILE dataset should be an FB LRECL 133 file, and is opened for extend each time that the task is started.
32 DLm Utilities for z/OS Environment
● RESETLOG — Instructs DLMHOST to discard any DLm messages that had been issued prior to the startup of DLMHOST.
The default behavior of DLMHOST is to display or log any DLm messages that had been issued on the DLm prior to its startup. This parameter provides the ability to change this default behavior.
● MSGID1ST — By default, DLm messages begin with the date and time for the message. When this parameter is specified, the DLm messages begin with a message id.
NOTE: The MSGID1ST parameter impacts the log data that are received from any VTE but does not change the responses to commands from DLMHOST.
● MSGIDFMT — By default DLm message ids end with a severity code of 'E', 'W', or 'I' for error, warning, and information messages, respectively. Specify this parameter when you want to have the severity code before the message number.
NOTE: The MSGIDFMT parameter impacts the log data that are received from any VTE but does not change the responses to commands from DLMHOST.
This document provides sample JCL to run DLMHOST. See the section
Downloading and using DLm z/OS components
for information about how to download the sample JCL. This SAMPLIBU dataset includes a sample PROC member to run the
DLMHOST utility, called DLMHOST
This proc must be customized to point to the APF authorized load library that DLMHOST has been installed in. Also, one or more configuration statements must be completed for the DLMCFG DD. The customized proc should be placed into a PROCLIB that is searched when the START DLMHOST command is issued from the zOS Console.
DLMHOST configuration file
This section provides an overview of DLMHOST configuration file.
The configuration file pointed to by the DLMCFG DD card should be an FB LRECL 80 file that has a single record for each VTE to be supported. You can define up to 64 records. Comments cards can be in the input configuration file by placing an asterisk in column 1.
The layout of the configuration file records is as follows:
● Col. 1 - 10 : NODENAME — The name used by the mainframe operator to identify which with VTE to communicate.
● Col 12 - 15: CMDDEV — The 4-digit device address of the tape drive that is to be used for operator commands and responses. If this field is left blank, no operator commands can be sent to this nodename.
● Col 17 - 20: LOGDEV — The 4-digit device address of the tape drive that is to be used for logging activity whenever logging is active for this VTE. If left blank, no host logging can occur from the VTE.
The following is sample DLMCFG for DLMHOST within a 3-VTE configuration supporting both messaging and commands:
VTLNODE1 038E 038F
VTLNODE2 039E 039F
VTLNODE3 03AE 03AF
Using z/OS Console support
This section provides an overview of using z/OS console support.
If DLMHOST is active and configured to receive DLm messages, it automatically forwards any message that is received to the
Console or log file.
When DLMHOST is executed without the NOWTOR parameter, the following message is displayed on the z/OS Console:
DLH001I ENTER COMMAND, EOJ,OR ? FOR HELP
An outstanding Write to Operator Reply (WTOR) message remains pending.
To send a command to DLMHOST, you need to know the message reply number from the WTOR. To determine the WTOR message number, enter the following z/OS command on the console of the operator: d r,l (or /d r,l from SDSF)
This command returns the reply message number for any outstanding WTORs on the system.
DLm Utilities for z/OS Environment 33
To issue a command to DLMHOST, enter the command using the WTOR message number in the following format: msg#,COMMAND
Where:
● msg# is the reply message number that is returned from the d r,l command.
● COMMAND is the DLMHOST command to be executed.
When DLMHOST is executed with the NOWTOR parameter, the following message is returned:
DLH002I jobname USE MODIFY TO ENTER COMMAND, EOJ, OR ? FOR HELP
Next, you can use the z/OS Modify command to issue commands to DLMHOST using the 'jobname' indicated in the DLH002I message.
The format of the z/OS Modify command is:
F jobname,command
Where:
● jobname is the job name of DLMHOST reported in the DLH002I message.
● command is the DLMHOST command to be executed.
DLMHOST commands
This section provides an overview of DLMHOST commands.
DLMHOST recognizes the following commands:
● CMD —Sends a DLm command to a specific VTE. This command requires a nodename to be specified by using the NODE= parameter (or N =). A nodename of ALL can be specified to send the command to every VTE. All DLm Operator commands can be entered as parameters to this command. The following are examples of valid use of this command:
CMD=Q SPACE,NODE=NODE1
CMD=FIND VOL=000001,N=N1
● STOPLOG —Requests that DLMHOST stop logging VTE log messages for a specific VTE. This command requires that a nodename be specified by using the NODE= parameter (or N =). A nodename of ALL can be specified to stop host logging for all defined VTEs. For example:
STOPLOG,N=ALL
STOPLOG,N=VTLNODE1
● STARTLOG —Requests that DLMHOST start host logging of VTE log data for a specific VTE. This command requires that a nodename be specified by using the NODE=parameter (or N =). A nodename of ALL can be specified to start logging for all defined VTEs. For example:
STARTLOG,N=NODE2
STARTLOG,NODE=ALL
● STOPCMD —Requests that DLMHOST disables command interface for a specific VTE. This command requires that a nodename be specified by using the NODE= parameter (or N =). A nodename of ALL can be specified to disable command interface for all defined VTEs. For example:
STOPCMD,N=ALL
STOPCMD,N=VTLNODE1
34 DLm Utilities for z/OS Environment
● STARTCMD —Requests that DLMHOST enables command interface for a specific VTE. This command requires that a nodename be specified by using the NODE= parameter (or N =). A nodename of ALL can be specified to enable command interface for all defined VTEs. For example:
STARTCMD,N=NODE2
STARTCMD,N=ALL
● STATUS —Requests that DLMHOST display the current configuration and status of the command and logging functions.
DLMHOST issues this message followed by the status of each configured node:
DLH2401 NODENAME CMDDEV LOGDEV
NOTE: A y or n next to the device address indicates whether the command/logging function is active or inactive for that node name, respectively. For example:
DLH2401 NODENAME CMDDEV LOGDEV
NODE1 038E Y 038F Y
NODE2 048E N 048F Y
● EOJ —Terminates the DLMHOST task.
● HELP or ?
—Returns the DLH000I message with a list of the valid DLMHOST commands. DLH000I lists the following commands:
STARTLOG,N=nodename/ALL
STOPLOG,N=nodename/ALL
C=Command,N=nodename/ALL
STATUS
WTOR command examples
This section provides an overview of WTOR command examples.
When DLMHOST has been run without the NOWTOR parameter, an outstanding WTOR message reply is used to send commands to DLMHOST. The following are valid examples of DLMHOST commands:
<msg#>,STATUS
<msg#>,C=Q SPACE,N=N1
<msg#>,STOPLOG,N=ALL
Where <msg#> is the message number that is returned from the d r,l (/d r,l from SDSF).
Non-WTOR command examples
This section provides an overview of non-WTOR command examples.
The following are valid examples of the same DLMHOST commands when DLMHOST sent with a z/OS MODIFY command when
DLMHOST has been run with the NOWTOR parameter using the job name DLMHOST:
F DLMHOST,STATUS
F DLMHOST,C=Q SPACE,N=N1
F DLMHOST,STOPLOG,N=ALL
DLm Utilities for z/OS Environment 35
DLMLIB Utility
This section provides an overview of DLMLIB Utility.
If your tape devices are defined in a Manual Tape Library (MTL), you must also define them in the mainframe's tape configuration database (TCDB). DLm provide the DLMLIB utility to do this. DLMLIB invokes IBM's LCS External Services
(CBRXLCS) macro.
DLMLIB can be used to define either a single tape volume or a continuous range of tape volumes to an MTL.
An example of the JCL required to run DLMLIB is provided. The sample JCL file is found in the RUNLIB member of installed
SAMPLIBU library. Downloading and using DLm z/OS components
provides download instructions and additional information.
When running DLMLIB, input requests are specified in the INDD DD statement. The input card format varies depending on the
DLMLIB command. See
for details.
DLMLIB writes a log of its actions using the OUTDD DD statement. This log file lists the result of each tape cartridge entry request, including any error codes.
The OUTDD file should have a fixed block (FB) format and a logical record length (LRECL) of 133. The DLMLIB utility appends the log of a DLMLIB run to an existing file.
NOTE: Return codes and reason codes can be found in the chapter "OAM Diagnostic Aids, CBRXLCS Return, and Reason
Codes” of IBM’s DFSMSdfp Diagnosis (GY27-7618).
DLMLIB commands
This section provides an overview of DLMLIB commands.
To manually add volume(s), the input card format is:
● Column 1: 'M'
● Column 4: Volume serial number; 6-characters, left justified, blank padded.
● Column 11: Library name; 8-characters, left justified, blank padded.
● Column 20: Media type; values from '1' through 'F'. For example, '4' is MEDIA4 type. Default if blank is '2' for MEDIA2 type.
● Column 21: Count of number of volume(s) to be added to library; 5 characters, right justified, zero filled. The additional
VOLSERs are incremented starting from the VOLSER specified in column 4.
To change the volume attribute to private, the input card format is:
● Column 1: 'P'
● Column 4: Volume serial number; 6-characters, left justified, blank padded.
● Column 11: Library name; 8-characters, left justified, blank padded.
● Column 20: Media type; values from '1' through 'F'. For example, '4' is MEDIA4 type. Default if blank is '2' for MEDIA2 type.
To eject the volume from the library, the input card format is:
● Column 1: 'E'
● Column 4: Volume serial number; 6-characters, left justified, blank padded.
● Column 11: Library name; 8-characters, left justified, blank padded.
● Column 20: Media type; values from '1' through 'F'. For example, '4' is MEDIA4 type. Default if blank is '2' for MEDIA2 type.
DLMLIB examples
This section provides an overview of DLMLIB examples.
Example 1: Manually adding volume(s) to the library:
Entering in a range of Scratch volumes to an MTL called DLM020. VOLSERs start at BG0500 and 90 are to be created.
Sample JCL:
//LIB EXEC PGM=DLMLIB
//STEPLIB DD DISP=SHR,DSN=USER.DLM.LINKLIB
36 DLm Utilities for z/OS Environment
//OUTDD DD DISP=SHR,DSN=USER.DATALIB(D15083A)
//SYSUDUMP DD SYSOUT=*
//INDD DD *
M BG0500 DLM020 400090
Sample Output
DLMLIB VER 4.03
2015/08/28 11:10:18 M BG0500 DLM020 400090 VOLUME SUCCESSFULLY ENTERED
2015/08/28 11:10:18 M BG0501 DLM020 4 VOLUME SUCCESSFULLY ENTERED
2015/08/28 11:10:18 M BG0502 DLM020 4 VOLUME SUCCESSFULLY ENTERED
2015/08/28 11:10:18 M BG0503 DLM020 4 VOLUME SUCCESSFULLY ENTERED
2015/08/28 11:10:18 M BG0504 DLM020 4 VOLUME SUCCESSFULLY ENTERED
2015/08/28 11:10:18 M BG0505 DLM020 4 VOLUME SUCCESSFULLY ENTERED
Example 2: Changing a volume attribute to private:
Changing the attribute of a VOLSER (BG0500), to PRIVATE in an MTL called DLM020.
Sample JCL:
//LIB EXEC PGM=DLMLIB
//STEPLIB DD DISP=SHR,DSN=USER.DLM.LINKLIB
//OUTDD DD DISP=SHR,DSN=USER.DATALIB(D15083B)
//SYSUDUMP DD SYSOUT=*
//INDD DD *
P BG0500 DLM020 4
Sample Output
DLMLIB VER 4.03
2015/08/28 11:19:07 P BG0500 DLM020 4 USE ATTRIBUTE CHANGED
Example 3: Ejecting a volume from the library:
Ejecting a VOLSER (BG0502), from an MTL called DLM020:
Sample JCL:
//LIB EXEC PGM=DLMLIB
//STEPLIB DD DISP=SHR,DSN=USER.DLM.LINKLIB
//OUTDD DD DISP=SHR,DSN=USER.DATALIB(D15083C)
//SYSUDUMP DD SYSOUT=*
//INDD DD *
E BG0502 DLM020 4
Sample Output
DLMLIB VER 4.03
2015/08/28 11:23:18 E BG0502 DLM020 4 EJECT SCHEDULED
DLm Utilities for z/OS Environment 37
3
Introduction to Command Processors
This chapter introduces the different Command Processors.
Topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Creating custom Command Processors
Command Processor 499 (CP499)
CP499 - A user controllable diagnostic aid.
CP499 is a user controllable diagnostic aid. It enables the user to test the accessibility of the attached VTE components using a batch job. CP499 sends output that includes a PASSED or FAILED condition and can customize a WTO to use with its automated operations. The user can list all the components that are attached to the VTE (through the /etc/hosts file) and ping a specific component through a specific IP address or component name.
Command Processor 501 (CP501)
This section describes the details of command processor 501 (CP501).
CP501 enables the mainframe operator to pass any supported DLm Console command to a selected Virtual Tape Engine (VTE), and retrieves the output for use on the mainframe. The Disk Library for mainframe User Guide provides a complete list of DLm commands.
Multiple executions of CP501 cannot run simultaneously. The DLMHOST utility resolves this issue and provides enhanced functionality.
DLMHOST utility provides information about
DLMHOST .
Command Processor 502 (CP502)
This section describes the details of command processor 502.
CP502 enables the mainframe operator to obtain any or all set of useful log files from a selected VTE. The log files available are:
● btilog files
● /var/log/messages
● Virtuent configuration information in:
○ Gen 4: VTE xmap files
○ Gen 5: cfg-util command output
● Output of the command ipmitool sel list
38 Introduction to Command Processors
Command Processor 503 (CP503)
CP503 produces a report of the DLm VOLSER inventory.
Command Processor 504 (CP504)
This section describes the details of command processor 504.
CP504 collects the replication statistics of all the DLm VNX file systems on which replication has been enabled. It includes all file systems on the base and expansion VNX systems. It generates three types of reports:
● QUICK
● SUMMARY
● VERBOSE
Command Processor 601 (CP601)
CP601 generates Data Domain and PowerProtect system utilization statistics and makes the reports available to the mainframe.
NOTE: DLm2500 does not support CP601.
Command Processor 602 (CP602)
CP602 generates a report that provides data compression statistics for the Data Domain and PowerProtect system.
The compression report provides data compression statistics for the entire Data Domain and PowerProtect system, for particular tape libraries, or for each tape file (VOLSER) in the user-specified tape library.
CP602 generates three types of reports:
● SUMMARY
● DETAILED
● FULL
NOTE: DLm2500 does not support CP602.
Command Processor 603 (CP603)
This section describes the details of command processor 603.
CP603 generates reports that provide the following Data Domain replication information:
● Replication configuration
● Replication status
● Replication statistics
● Replication performance statistics
● Replication historical data for the past 24 hours
NOTE: DLm2500 does not support CP603.
Command Processor 804 (CP804)
This section describes the details of command processor 804.
In DLm 5.4 and later, CP804 generates reports that provide replication statistics for each file system mounted on VTE.
By using the TLIB and PREFIX parameters the CP804 report is limited to either a specific tape library or to a single specific non-scratch VOLSER. Three different report types are available:
Introduction to Command Processors 39
● SUMMARY
● DETAILED
● FULL
NOTE: CP804 is supported from DLm 5.4 and later, on DLm8500 with VNX, DD, or OneFS.
Command Processor 988 (CP988)
This section describes the detail of command processor 988.
In DLm 4.5.3 and later and DLm 5.x, CP988 captures statistics from back-end file systems that are specified by their VOLSER range and reports DLm virtual tape activity. These reports present:
● Daily and hourly throughput numbers
● Mount rates
● Concurrent tape drive usage details
● Compression ratio
● Average and slow mount response information
NOTE: CP988 is supported only on DLm 4.5.3 and later and DLm 5.x.
Command Processor 989 (CP989)
This section describes the details of command processor 989.
In DLm 4.5.3 and later and DLm 5.x, CP989 captures statistics from a local VTE and reports virtual tape activity. These reports present the same statistics as CP988 (listed above).
NOTE: CP989 is supported only on DLm 4.5.3 and later and DLm 5.x.
Command Processor 998 (CP998)
This section describes the details of command processor 998.
CP998 captures statistics from back-end file systems that are specified by their VOLSER range and then invokes the
GENSTAT utility to report DLm virtual tape activity. These reports present:
● Daily and hourly throughput numbers
● Mount rates
● Concurrent tape drive usage details
● Compression ratio
● Average and slow mount response information
NOTE: CP998 is supported only on DLm 4.x. DLm releases 5.0 and later do not support this command processor.
Command Processor 999 (CP999)
This section describes details of command processor 999.
CP999 captures statistics from a local VTE and then invokes the GENSTATS utility to report DLm virtual tape activity. These reports present the same statistics as CP998 (listed above).
NOTE: CP999 is supported only on DLm 4.x. DLm releases 5.0 and later do not support this command processor.
40 Introduction to Command Processors
Creating custom Command Processors
This section describes details of how to create custom command processors.
The Command Processor infrastructure of DLm can be used by Professional Services to implement customized Command
Processor-like operations that can be initiated from the mainframe host. CP001 to CP498 are reserved for this purpose.
Contact your representative for further details.
Introduction to Command Processors 41
4
Using Command Processors
This chapter introduces how Command Processors are invoked from the mainframe, the parameters that are provided, and sample JCL and reports.
Topics:
•
Performing DLm Diagnostics: CP499
•
•
Obtaining DLm Log Information: CP502
•
Obtaining Virtual Tape Volume Information: CP503
•
Obtaining VNX Replication Information: CP504
•
Obtaining Data Domain and PowerProtect: CP601, CP602, CP603
•
Obtaining Replication Information by VOLSER: CP804
•
Obtaining tape activity: CP988 and CP989
•
Obtaining tape activity: CP998 and CP999 (DLm 4.x only)
Performing DLm Diagnostics: CP499
This section provides an overview of performing DLm diagnostics of CP499.
This job pings DLm components that are attached to this VTE. Use it as a batch component testing function.
NOTE: The parameters are case-sensitive.
Submit CP499 from the mainframe by using DLMCMD49 or DLMCPRUN procedure.
CP499 syntax
The CP499 command syntax is:
//GO EXEC DLMCMD49,CMD=499,UNIT=unitid,
// CPARMS='CP499 Parameters'
//GO EXEC DLMCPRUN,CMD=499,UNIT=unitid,
// CPARMS='CP499 Parameters'
Table 9. CP499 parameters
Parameter
CPARMS
Description
Valid options are:
● -l all : Interrogates the /etc/host and lists its contents
● -i xxx.xxx.xxx.xxx
: Pings a specific address
● -c ComponentName : Pings a component by name
NOTE: The default option is - l all for list all.
NOTE: CP499 processing is directed to a single DLm VTE. If you are using an esoteric for the DLm Unit, the esoteric should only include DLm Units for that VTE.
42 Using Command Processors
Example 1:
The following example interrogates the /etc/host and lists its contents.
Sample JCL:
● The following JCL uses a DLm Unit (F200), that is not in an MTL:
//GO EXEC DLMCMD49,CMD=499,UNIT=/F200,
// CPARMS='-l all'
//GO EXEC DLMCPRUN,CMD=499,UNIT=/F200,
// CPARMS='-l all'
● The following JCL uses a DLm Unit (F207), that is in an MTL:
//GO EXEC DLMCMD49,CMD=499,UNIT=(/F207,,,SMSHONOR),
// CPARMS='-l all'
Sample output
20150828-15:38:20-34918
EMC ADHOC Component List and Test Report (499) v4.4.0-r5798
Fri Aug 28 15:41:26 EDT 2015
================================================================================
499 Adhoc Verification tool
*Component List Report* ( options flags -l all)
This Report Lists the DLm components that can be reached from the VTE that this CP499 utility is running on (Components that CP499 can validate)
--------------------------------------------------------------------------------
Component IP Address
--------- -------------dd1 192.168.100.110
dd1s-alias0 192.168.203.10
dd1s-alias1 192.168.203.11
dd1s-alias2 192.168.203.12
dd1s-alias3 192.168.203.13
dd2 192.168.100.120
dd2s-alias0 192.168.204.10
dd2s-alias1 192.168.204.11
dd2s-alias2 192.168.204.12
dd2s-alias3 192.168.204.13
localhost 127.0.0.1
switch10a 192.168.100.240
switch10b 192.168.100.241
switcha 192.168.100.1
switchb 192.168.100.2
vnx1 192.168.100.205
vnx1cs0 192.168.100.200
vnx1cs1 192.168.100.201
vnx1dm2-alias0 192.168.201.20
vnx1dm2-alias1 192.168.201.21
vnx1dm2-alias2 192.168.201.22
vnx1dm2-alias3 192.168.201.23
vnx1dm3-alias0 192.168.201.30
vnx1dm3-alias1 192.168.201.31
vnx1dm3-alias2 192.168.201.32
vnx1dm3-alias3 192.168.201.33
vnx1dm4-alias0 192.168.201.40
vnx1dm4-alias1 192.168.201.41
vnx1dm4-alias2 192.168.201.42
vnx1dm4-alias3 192.168.201.43
vnx1dm5-alias0 192.168.201.50
vnx1dm5-alias1 192.168.201.51
vnx1dm5-alias2 192.168.201.52
Using Command Processors 43
vnx1dm5-alias3 192.168.201.53
vnx1dm6-alias0 192.168.201.60
vnx1dm6-alias1 192.168.201.61
vnx1dm6-alias2 192.168.201.62
vnx1dm6-alias3 192.168.201.63
vnx1dm7-alias0 192.168.201.70
vnx1dm7-alias1 192.168.201.71
vnx1dm7-alias2 192.168.201.72
vnx1dm7-alias3 192.168.201.73
vnx1dm8-alias0 192.168.201.80
vnx1dm8-alias1 192.168.201.81
vnx1dm8-alias2 192.168.201.82
vnx1dm8-alias3 192.168.201.83
vnx1dm9-alias0 192.168.201.90
vnx1dm9-alias1 192.168.201.91
vnx1dm9-alias2 192.168.201.92
vnx1dm9-alias3 192.168.201.93
vnx2 192.168.100.215
vnx2cs0 192.168.100.210
vnx2cs1 192.168.100.211
vnx2dm2-alias0 192.168.202.20
vnx2dm2-alias1 192.168.202.21
vnx2dm2-alias2 192.168.202.22
vnx2dm2-alias3 192.168.202.23
vnx2dm3-alias0 192.168.202.30
vnx2dm3-alias1 192.168.202.31
vnx2dm3-alias2 192.168.202.32
vnx2dm3-alias3 192.168.202.33
vnx2dm4-alias0 192.168.202.40
vnx2dm4-alias1 192.168.202.41
vnx2dm4-alias2 192.168.202.42
vnx2dm4-alias3 192.168.202.43
vnx2dm5-alias0 192.168.202.50
vnx2dm5-alias1 192.168.202.51
vnx2dm5-alias2 192.168.202.52
vnx2dm5-alias3 192.168.202.53
vnx2dm6-alias0 192.168.202.60
vnx2dm6-alias1 192.168.202.61
vnx2dm6-alias2 192.168.202.62
vnx2dm6-alias3 192.168.202.63
vnx2dm7-alias0 192.168.202.70
vnx2dm7-alias1 192.168.202.71
vnx2dm7-alias2 192.168.202.72
vnx2dm7-alias3 192.168.202.73
vnx2dm8-alias0 192.168.202.80
vnx2dm8-alias1 192.168.202.81
vnx2dm8-alias2 192.168.202.82
vnx2dm8-alias3 192.168.202.83
vnx2dm9-alias0 192.168.202.90
vnx2dm9-alias1 192.168.202.91
vnx2dm9-alias2 192.168.202.92
vnx2dm9-alias3 192.168.202.93
vte0 192.168.100.253
vte0-rmm 192.168.100.254
vte1 192.168.100.10
vte1-rmm 192.168.100.11
vte2 192.168.100.20
vte2-rmm 192.168.100.21
vte3 192.168.100.30
vte3-rmm 192.168.100.31
vte4 192.168.100.40
vte4-rmm 192.168.100.41
vte5 192.168.100.50
vte5-rmm 192.168.100.51
vte6 192.168.100.60
vte6-rmm 192.168.100.61
vte7 192.168.100.70
vte7-rmm 192.168.100.71
vte8 192.168.100.80
vte8-rmm 192.168.100.81
vtea 192.168.100.8
PASSED
44 Using Command Processors
Example 2:
The following example Pings a specific address.
Sample JCL:
The following JCL, a DLm Unit (F207), that is in an MTL:
//GO EXEC DLMCMD49,CMD=499,UNIT=(/F207,,,SMSHONOR),
// CPARMS='-i 192.168.100.20'
Sample output
EMC ADHOC Component List and Test Report (499) v4.4.0-r5798
Fri Aug 28 15:43:00 EDT 2015
================================================================================
Pinged 192.168.100.20 3 times successfully - Component is => vte2
PASSED
--------------------------------------------------------------------------------
================================================================================
Running VTE Commands: CP501
Using CP501, you can pass a DLm Virtual Tape Operator console command to a VTE, and use the output on the mainframe as appropriate.
The Virtual Tape Operator commands enable you to control or query virtual tape drives.
CP501 supports the following VT operator commands:
● CLOSE VSTATS PATH
● CAPACITY
● DETAIL MOUNT
● DISABLE EFSMOVE
● ENABLE EFSMOV
● EXPORT
● FIND
● HELP
● IMPORT
● INITIALIZE
● KMRESTART
● LOAD
● LTR
● MIGRATE
● QUERY
● QUIESCE
● READY
● REWIND
● ROTATE
● SAVE TRACE
● SET
● SHOW
● SNMP
● UNLOAD
● UNQUIESCE
● UNREADY
NOTE: The Dell Technologies Disk Library for mainframe User Guide provides information about the Virtual Tape Operator commands.
Using Command Processors 45
NOTE: Few commands might not be supported for your DLm version, see the Dell Technologies Disk Library for mainframe
User Guide for more information.
NOTE: The DLMHOST utility provides an enhanced version of the CP501 functionality. The
provides information about DLMHOST .
Submit CP501 from the mainframe by using DLMCMDPR , DLMCMDP1 or the DLMCPRUN procedure.
CP501 syntax
This section provides an overview of CP501 syntax.
The CP501 command syntax is:
//GO EXEC DLMCMDP1,CMD=501,UNIT=unitid1,
// VCMD='VTECommand',
// CPARMS='VTECommand_parameters'
//GO EXEC DLMCMDPR,CMD=501,UNIT=unitid1,UNIT2=unit2,
// VCMD='VTECommand',
// CPARMS='VTECommand_parameters'
//GO EXEC DLMCPRUN,CMD=501,UNIT=unitid,
// VCMD='VTECommand',
// CPARMS='VTECommand_parameters'
CP501 parameters
This section provides an overview of CP501 parameters.
Table 10. CP501 parameters
Parameter
VCMD
CPARMS
Description
This parameter is required for Command Processor 501.
It specifies the Virtual Tape Operator command. See the
“Virtual Tape Operator command reference” section in the
Disk Library for mainframe User Guide for a description of available commands.
This parameter allows for VTE command parameters to be specified for the 501 Command Processors.
Example
This section provides an overview of sample JCL and sample output.
Sample JCL
//GO1 EXEC DLMCPRUN,CMD=501,UNIT=/8A00, X
// VCMD='INITIALIZE’, X
// CPARMS='VOL=VM0100 DEV=8A00 COUNT=1 CLASS=0'
Sample output The sample report output that is shown below is generated by the above example Command Processor.
EMC DLm VTEC Command Processor Tool (501) v5.0.3-9
Tue Jan 29 11:03:56 EST 2019
================================================================================
01/29/2019 11:03:56 vte1 VT: DLm0869I: 1 Standard-label volume initialized in
/tapelibTLDDRL/DD1_TLDDRL_FS1
================================================================================
46 Using Command Processors
Security concerns
The VTE Command Processing feature of CP501 allows any DLm command to be passed, hence establish appropriate security measures, for example RACF, to restrict its use to authorized personnel.
Obtaining DLm Log Information: CP502
CP502 enables the transfer of the contents of the following to a mainframe tape file:
● btilog files
● /var/log/messages
● VTE xmap file.
NOTE: This information may vary according to DLm model. For example, there is no xmap file on Gen 5 DLms. CP502 returns Virtuent configs obtained from the cfg-util command instead of xmap file on Gen 5.
● Output of command ipmitool sel list
Submit CP502 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
btilog files
Each VTE maintains log files of operations that are performed by the virtual tape emulation application. These log files are known as btilogs.
These files are a primary source of information for operation sequencing, completion, and problem determination. The btilogs are text files that contain the detailed activity of all VTEs and are located in the /var/bti/log directory on DLm 4.x and earlier and in the /var/log/bti directory on DLm 5.x and later. The most recent btilog file is btilog.
The number of btilogs to be transferred is specified by the user. The default value is 2 (the current log file and its immediate predecessor) and the maximum value is 10.
/var/log/messages
This is the standard operating system log file, which contains messages from the system software, kernel messages, non-kernel boot issues, and general system messages. As this file can be large, CP502 copies only the last 1,000 lines to the mainframe file.
VTE xmap file
In Gen 4 the VTE contains one virtual tape device configuration file—xmap0 in the /etc/bti directory.
VTE contains no xmap file in Gen 5.
ipmitool sel list
When this operating system level command is performed, the VTE baseboard controller System Event Log (SEL) is transferred to the mainframe.
CP502 syntax
This section provides an overview of CP502 syntax.
The CP502 command syntax is:
//GO EXEC DLMCMDP1,CMD=502,UNIT=unitid1,
// CPARMS='command parameters'
//GO EXEC DLMCMDPR,CMD=502,UNIT=unitid1,UNIT2=unit2,
// CPARMS='command parameters'
Using Command Processors 47
//GO EXEC DLMCPRUN,CMD=502,UNIT=unitid,
// CPARMS='command parameters'
CP502 parameters
This section provides an overview of CP502 parameters.
Table 11. CP502 parameters
Parameter
CPARMS
Description
This parameter allows for command parameters to be specified for the 502 Command Processors. Enter an optional command-specific parameters depending on the files to transfer:
● L0 - btilog files requested (see Number of btilogs to collect)
● L1 - (Default) btilogs and /var/log/messages
● L2 - btilogs, /var/log/message, current.json, and output of command ipmitool sel list
NOTE: Gen 4 includes /etc/bti/xmap
● The number of btilogs to collect: 2 to 10 files. The default value is 2.
NOTE: The default CPARMS value for Command Processor 502:
● Collection type: L1
● Number of btilogs to collect: 2
● /var/log/messages
● The above defaults specify that two btilog files are to be collected.
Example 1:
This section provides an example of JCL sample.
Sample JCL: The JCL below uses a DLm Unit (F207) that is not in an MTL:
//GO2 EXEC DLMCMDPR,CMD=502,UNIT=/F200,UNIT2=F201,
// CPARMS='L2 3'
//GO EXEC DLMCPRUN,CMD=502,UNIT=/F200,
// CPARMS='L1 2'
Sample output The sample output that is shown below is generated by the above example Command Processor.
EMC DLm VTEC Log Collection Tool (502) v4.4.0-r5798
Wed Sep 2 10:11:08 EDT 2015
================================================================================
--------------------------------------------------------------------------------
#####Diagnostic-Data#####
BTI Log name : /var/bti/log/old-logs/btilog-20150831
08/30/2015 23:59:04 vte1 VTd: ***** Rotated Virtuent log *****
08/30/2015 23:59:05 vte1 VT: DLm0409I: Command received: 'q all'
08/30/2015 23:59:05 vte1 VT:
08/30/2015 23:59:05 vte1 VT: Version 7.40-15840, built Jul 2 2015 14:11:50
08/30/2015 23:59:05 vte1 VT: Model Family: dlm8100v
08/30/2015 23:59:05 vte1 VT: Licensed Features Enabled:
08/30/2015 23:59:05 vte1 VT: EMC FLR Support
08/30/2015 23:59:05 vte1 VT: EMC DDRL Support
08/30/2015 23:59:05 vte1 VT: SCSI Tape Support
….
48 Using Command Processors
08/31/2015 11:41:18 vte1 VT: DLm0490I: Device F207 Volume BFL502 unloaded
08/31/2015 11:41:18 vte1 VT: DLm0405I: Device F207 Display: 'KBFL502 '
08/31/2015 23:59:01 vte1 VTd: ***** Rotating Virtuent log *****
--------------------------------------------------------------------------------
#####Diagnostic-Data#####
BTI Log name : /var/bti/log/old-logs/btilog-20150901
08/31/2015 23:59:04 vte1 VTd: ***** Rotated Virtuent log *****
08/31/2015 23:59:04 vte1 VT: DLm0409I: Command received: 'q all'
08/31/2015 23:59:04 vte1 VT:
08/31/2015 23:59:04 vte1 VT: Version 7.40-15840, built Jul 2 2015 14:11:50
08/31/2015 23:59:04 vte1 VT: Model Family: dlm8100v
….
09/01/2015 14:15:19 vte1 VT: DLm0409I: Command received: 'RESET CHANNEL ADAPTER'
09/01/2015 14:15:19 vte1 VT: DLm0891E: Invalid command syntax
09/01/2015 23:59:01 vte1 VTd: ***** Rotating Virtuent log *****
--------------------------------------------------------------------------------
#####Diagnostic-Data#####
BTI Log name : /var/bti/log/btilog
09/01/2015 23:59:04 vte1 VTd: ***** Rotated Virtuent log *****
09/01/2015 23:59:04 vte1 VT: DLm0409I: Command received: 'q all'
09/01/2015 23:59:04 vte1 VT:
09/01/2015 23:59:04 vte1 VT: Version 7.40-15840, built Jul 2 2015 14:11:50
09/01/2015 23:59:04 vte1 VT: Model Family: dlm8100v
09/01/2015 23:59:04 vte1 VT: Licensed Features Enabled:
….
09/02/2015 10:11:07 vte1 VT: DLm0405I: Device F207 Display: ' BG0340S'
09/02/2015 10:11:07 vte1 VT: DLm0550I: Command received from Host: device F207: cmd = 'RUNWAIT (600) 502 "L2"
"3" "DEFAULT"
09/02/2015 10:11:07 vte1 VT: DLm0554I: "RUNWAIT(600) 502" command has started
(RUN process #36)
--------------------------------------------------------------------------------
#####Diagnostic-Data#####
Linux System Log name : /var/log/messages
Sep 1 10:09:36 vte1 sshd¢125940!: Did not receive identification string from
10.241.216.65
Sep 1 10:10:01 vte1 /usr/sbin/cron¢126349!: (root) CMD (/opt/EMC_TOOLS/bin/ dlm_dd_report.pl >/dev/null 2>&1)
Sep 1 10:10:01 vte1 sudo: root : TTY=unknown ; PWD=/root ; USER=root ;
COMMAND=/usr/bin/vte_version
Sep 1 10:14:09 vte1 /etc/bti/userscripts/script501: EMC DLm VTEC Command
Processor Tool (501) v4.4.0-r5798
Sep 1 10:14:09 vte1 /etc/bti/userscripts/script501:
CP501:DEBUG_INTERNAL_STATUS_CODE : 4
Sep 1 10:14:09 vte1 /etc/bti/userscripts/script501: Executing 'HELP' command...
….
Sep 2 10:11:08 vte1 /etc/bti/userscripts/script502: Command Param : L2 3
DEFAULT BFL502.FLAT
Sep 2 10:11:08 vte1 /etc/bti/userscripts/script502: Collecting BTI Log files.
Sep 2 10:11:08 vte1 /etc/bti/userscripts/script502: Collecting Linux System Log
/var/log/messages.
--------------------------------------------------------------------------------
#####Diagnostic-Data#####
Current XMAP File : /etc/bti/xmap0
# /etc/bti/xmap0
#
# Configuration file - automatically generated by apply script - do not modify
#
#
USERNAME xmap0
DESCRIPTION
ERASEPOLICY SPACE
ERASEPOLICY 365D
TRACELEVEL 1
FWPATHTRACE 0
WARNINGPERCENT 88
….
¢DEVICE! INDEX=0C ACTIVE=1 NAME=F20C TYPE=3590 CU=00 UNIT=0C PATH=/tapelibFLR
IDRC=yes
¢DEVICE! INDEX=0D ACTIVE=1 NAME=F20D TYPE=3590 CU=00 UNIT=0D PATH=/tapelibFLR
IDRC=yes
¢DEVICE! INDEX=0E ACTIVE=1 NAME=F20E TYPE=3590 CU=00 UNIT=0E PATH=/tapelibFLR
Using Command Processors 49
IDRC=yes
¢DEVICE! INDEX=0F ACTIVE=1 NAME=F20F TYPE=3590 CU=00 UNIT=0F PATH=/tapelibFLR
IDRC=yes
--------------------------------------------------------------------------------
#####Diagnostic-Data##### ipmitool sel list Output
1 ¦ 02/22/2013 ¦ 19:36:35 ¦ Event Logging Disabled #0x07 ¦ Log area reset/ cleared ¦ Asserted
2 ¦ 02/22/2013 ¦ 20:56:55 ¦ Power Unit #0x01 ¦ Power off/down ¦ Asserted
3 ¦ 02/22/2013 ¦ 20:57:01 ¦ Power Unit #0x01 ¦ Power off/down ¦ Deasserted
4 ¦ 02/22/2013 ¦ 20:57:12 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦ Asserted
5 ¦ 02/22/2013 ¦ 20:57:12 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦ Asserted
6 ¦ 02/22/2013 ¦ 20:57:42 ¦ Physical Security #0x04 ¦ System unplugged from LAN
¦ Asserted
7 ¦ 02/22/2013 ¦ 20:58:00 ¦ Physical Security #0x04 ¦ System unplugged from LAN
¦ Deasserted
8 ¦ 02/22/2013 ¦ 20:58:40 ¦ System Event #0x83 ¦ OEM System boot event ¦
Asserted
9 ¦ 02/22/2013 ¦ 20:59:36 ¦ Physical Security #0x04 ¦ System unplugged from LAN
¦ Asserted a ¦ 02/22/2013 ¦ 21:00:04 ¦ Physical Security #0x04 ¦ System unplugged from LAN
¦ Deasserted b ¦ 02/22/2013 ¦ 21:19:00 ¦ Physical Security #0x04 ¦ System unplugged from LAN
¦ Asserted
47d ¦ 08/12/2015 ¦ 20:26:19 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦
Asserted
47e ¦ 08/12/2015 ¦ 20:26:19 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦
Asserted
47f ¦ 08/12/2015 ¦ 20:27:54 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦
Asserted
480 ¦ 08/12/2015 ¦ 20:27:54 ¦ System Event #0x83 ¦ Timestamp Clock Sync ¦
Asserted
481 ¦ 08/12/2015 ¦ 20:29:00 ¦ System Event #0x83 ¦ OEM System boot event ¦
Asserted
================================================================================
Obtaining Virtual Tape Volume Information: CP503
This section describes how to obtain Virtual Tape Volume information reports:
●
●
Using CP503 command
CP503 provides an output report of the DLm Virtual Tape Volume Inventory.
Submit CP503 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
CP503 syntax
This section provides an overview of CP503 syntax.
The CP503 command syntax is:
//GO EXEC DLMCMDP1,CMD=503,UNIT=unitid1,
// CPARMS='command parameters'
//GO EXEC DLMCPRUN,CMD=503,UNIT=unitid,
// CPARMS='command parameters'
//GO EXEC DLMCMDPR,CMD=503,UNIT=unitid1,UNIT2=unitid2,
// CPARMS='command parameters'
50 Using Command Processors
CP503 parameters
This section describes the CP503 parameters.
Table 12. awsprint parameters
Parameters
CPARMS
Option
-p
Description
Required, if not, use the DLMCMDPR or
DLMCMDP1 PROC. Path to the virtual tape library. Typically, /tapelib
NOTE: When using the DLMCMDPR or DLMCMDP1 PROCs, this parameter is overridden by the TLIB parameter, which defaults to the Virtual Tape Library associated with the UNIT parameter.
-s Optional. parameters to select a specific volume or range of volumes. For example:
● -s BT0010 — Lists only volume
BT0010
● -s BT00* — Lists all volumes from
BT0000 to BT0099
NOTE: *If -s is omitted, all volumes in the tape library are listed.
TLIB
-<sort criteria>
-d
-a
-r
--less
N/A
Sort criteria. sort by:
● -N — The filename. This is the default sort order
● -V — The volume serial number
● -D — Last modification date
● -H — Tape Header1 (HDR1) dataset name for labeled volumes and data in the TAPE INFO field for unlabeled volumes
● -I — Filename with scratch and unscratched tapes interspersed
● -S — Size
Display tape content details.
Display all, scratch and non-scratch, volumes
Recurse the directories
Displays less information (by not opening the tape file). Tape label information, the VOL1 label, label type, and Data
Set Name (DSN), are not to be displayed. Using this option speeds up the processing because each DLm
Tape volume in the directories that are processed does not need to be opened, read and closed.
This parameter specifies the path to the virtual tape library on the DLm. When this parameter is not specified, the Tape
Library folder for the PATH parameter is used.
Using Command Processors 51
Example 1:
Using CP503 to obtain the DLm Virtual Tape Volume Inventory with default reporting options.
NOTE: The following example uses a Unit (F207) which belongs to an MTL and a Unit (F200) that is not an MTL:
//GO3 EXEC DLMCMDPR,CMD=503,UNIT=(/F207,,,SMSHONOR),UNIT2=F201
//GO EXEC DLMCPRUN,CMD=503,UNIT=/F200,
// TLIB='/tapelibBACKCUP',
// CPARMS='-r -a -H'
Sample output
Sorted by Name 09/14/2015 11:25:30 AM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0310 BG0310 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0312 BG0312 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0314 BG0314 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0316 BG0316 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0318 BG0318 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0320 BG0320 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0322 BG0322 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
Example 2:
Using CP503 to obtain the DLm Virtual Tape Volume Inventory with the recursive option and to only include VOLSERs beginning in BG030.
//GO3 EXEC DLMCMDPR,CMD=503,UNIT=(/F207,,,SMSHONOR),UNIT2=F201,
// CPARMS=’-r -s BG030*’
Sample output
Sorted by Name 09/14/2015 11:29:40 AM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: BG030* Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
************************************************************************* awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Example 3:
Using CP503 to obtain the DLm Virtual Tape Volume Inventory recursive option, which is sorted by HDR1s.
//GO3 EXEC DLMCMDPR,CMD=503,UNIT=(/F207,,,SMSHONOR),UNIT2=F201,
// CPARMS='-r -H'
52 Using Command Processors
Sample output
Sorted by HDR1 09/14/2015 11:36:30 AM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 FLR_Lo 06/24/15 08:19 D Directory 80
2 ~BG0366 BG0366 12/31/89 23:00 S HDR100000000000000000 416
3 ~BG0368 BG0368 12/31/89 23:00 S HDR100000000000000000 416
4 ~BG0370 BG0370 12/31/89 23:00 S HDR100000000000000000 416
5 ~BG0372 BG0372 12/31/89 23:00 S HDR100000000000000000 416
6 ~BG0374 BG0374 12/31/89 23:00 S HDR100000000000000000 416
7 ~BG0376 BG0376 12/31/89 23:00 S HDR100000000000000000 416
8 ~BG0378 BG0378 12/31/89 23:00 S HDR100000000000000000 416
9 ~BG0380 BG0380 12/31/89 23:00 S HDR100000000000000000 416
Example 4:
Using CP503 to obtain the DLm Virtual Tape Volume Inventory with the recursive and detail reporting option.
//GO3 EXEC DLMCMDPR,CMD=503,UNIT=(/F207,,,SMSHONOR),UNIT2=F201,
// CPARMS='-r -d'
Sample output awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 11:38:19 AM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes With Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
*************************************************************************
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
*************************************************************************
DETAILS OF /tapelibFLR/CEL1_FLRP_FS1/BG0301
<EBCDIC LABELS>
VOL1BG0301 TCSBT
HDR1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
HDR2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #1: 3 x 80-byte blocks
0 Blocks Compressed 3 Blocks not Compressed
<TM>
<TM>
EOF1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
EOF2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #3: 2 x 80-byte blocks
0 Blocks Compressed 2 Blocks not Compressed
<TM>
<TM>
<1 x 32500-byte AWSMAP>
End of tape.
*************************************************************************
Example 5:
Using CP503 to obtain the DLm Virtual Tape Volume Inventory with the recursive and --fewer reporting options.
//GO3 EXEC DLMCMDPR,CMD=503,UNIT=(/F207,,,SMSHONOR),UNIT2=F201,
// CPARMS='-r --less'
Sample output awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 01:16:56 PM
Using Command Processors 53
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 08/26/15 15:19 32.7K
2 BG0302 08/26/15 15:21 32.7K
3 BG0304 08/27/15 11:01 32.7K
4 BG0306 08/28/15 15:41 32.7K
5 BG0308 08/28/15 15:42 32.7K
6 BG0310 08/28/15 15:42 32.7K
7 BG0312 08/28/15 15:42 32.7K
8 BG0314 08/28/15 15:43 32.7K
9 BG0316 08/28/15 15:43 32.7K
10 BG0318 08/28/15 15:44 32.7K
11 BG0320 08/28/15 15:44 32.7K
Note on CP503 Tape Inventory reports
This section provides an overview of note on CP503 tape inventory reports.
Command Processors typically store their output in special Virtuent files called Flat Files. These Flat Files have a name that begins with BFL and ends with .FLAT. Typically a CP503 execution creates a file that is called BFL503.FLAT and it is stored in the tapelib primary folder. These Flat Files and the File System folders are often seen in CP503 reports, before the report output containing the DLm Tape Volume inventory.
Using awsprint utility
This section provides an overview of using the awsprint utility.
Establish a CLI session on a DLm VTE to use awsprint. awsprint is a virtual tape library utility that the mainframe user can execute from the shell on the VTE to review the contents of the virtual tape library. awsprint enables you to produce lists of the tapes in the virtual tape library.
awsprint syntax
This section provides an overview of awsprint syntax.
The syntax to run the awsprint utility in a VTE Shell is: awsprint -p/tapelib -sBT00* -N -d
defines the awsprint command parameters. Also, example 1 shows the syntax and parameters available.
This report is returned by awsprint when awsprint is invoked without any parameters.
Example 1:
Executing awsprint with no options specified. This results in a report of the awsprint syntax and a description of its options.
vte1:~ # awsprint awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Usage: awsprint directory [-s pattern] [-NDVHIS] [-dar] [--less] directory Specifies the path where the AWS tapes are stored.
This is a required parameter. For backwards compatibility, directory can be specified with a "-p" switch.
-s pattern Option to select files by filename, up to six characters; or to select files by scratch filename, up to seven characters; an optional ending '*' can be used as a wildcard.
The default is to select all files in the directory.
-N Sort output by fileName.
-D Sort output by Date,
-V Sort output by VOL1 Volser.
-H Sort output by HDR1 dataset name.
54 Using Command Processors
-I Sort output by fileName, interspersing scratch and non-scratch files (which normally would collate into separate groups).
-S Sort output by file Size.
Only one sort option can be specified.
The default sort sequence is -N, by fileName.
-r --recurse Specifies that all directories should be recursed.
-a --all Specifies that all (scratch and non-scratch) volumes are to be printed regardless of selection pattern.
-h --help Displays this help information.
-V --version Displays version number.
-d --details Specifies that tape details should be printed.
-l --less Specifies that tape label information (VOL1 label, label type, DSN) are not to be displayed. Using this option will greatly speed up the program as awsprint does not need to open, read, and close every file in the directory.
Output is written to the console. You can use redirection (">") to write the awsprint output to a file.
Usage example: awsprint /tapelib -sBT00* -H >tapelist.txt
Selects all tapes starting with BT00 in path /tapelib, sorted by the
HDR1 dataset name. The output is redirected to the file tapelist.txt.
Example 2:
Executing awsprint with tapelib folder specified. Note that BFL FLAT files are stored on this folder.
vte1:~ # awsprint /tapelibFLR/CEL1_FLRP_FS1 awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:30:08 PM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0310 BG0310 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0312 BG0312 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0314 BG0314 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0316 BG0316 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0318 BG0318 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0320 BG0320 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0322 BG0322 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
13 BG0324 BG0324 08/28/15 16:05 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0326 BG0326 08/28/15 16:11 S HDR1MGDLMTL1.TEMP.H01 32.7K
15 BG0328 BG0328 08/31/15 09:56 S HDR1MGDLMTL1.TEMP.H01 32.7K
16 BG0330 BG0330 08/31/15 10:01 S HDR1MGDLMTL1.TEMP.H01 32.7K
17 BG0332 BG0332 08/31/15 10:02 S HDR1MGDLMTL1.TEMP.H01 32.7K
18 BG0334 BG0334 08/31/15 10:04 S HDR1MGDLMTL1.TEMP.H01 32.7K
19 BG0336 BG0336 09/01/15 10:08 S HDR1MGDLMTL1.TEMP.H01 32.7K
20 BG0338 BG0338 09/01/15 10:21 S HDR1MGDLMTL1.TEMP.H01 32.7K
Example 3:
Executing awsprint with the recursive option.
vte1:~ # awsprint /tapelibFLR -r awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:31:35 PM
Path: /tapelibFLR
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BFL499 08/28/15 15:45 F FLAT FILE 2.3K
2 BFL500 08/20/15 14:01 F FLAT FILE 2.2K
Using Command Processors 55
3 BFL501 09/01/15 10:14 F FLAT FILE 18.0K
4 BFL502 09/14/15 13:16 F FLAT FILE 144K
5 BFL503 09/02/15 11:07 F FLAT FILE 145K
6 BFL504 09/02/15 10:22 F FLAT FILE 2.6K
7 BFL601 09/02/15 10:23 F FLAT FILE 4.9K
8 BFL602 09/02/15 10:23 F FLAT FILE 8.0K
9 BFL603 09/02/15 10:23 F FLAT FILE 9.5K
….
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:31:35 PM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0304 BG0304 08/27/15 11:01 S HDR1MCMD.TEMPFILE.H01 32.7K
4 BG0306 BG0306 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0308 BG0308 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0310 BG0310 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0312 BG0312 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0314 BG0314 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0316 BG0316 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0318 BG0318 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0320 BG0320 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0322 BG0322 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
13 BG0324 BG0324 08/28/15 16:05 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0326 BG0326 08/28/15 16:11 S HDR1MGDLMTL1.TEMP.H01 32.7K
….
awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:31:35 PM
Path: /tapelibFLR/CEL1_FLRP_FS2
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0300 BG0300 08/26/15 15:11 S HDR1G20A.GDG.G0068V00 1.2M
2 BG0303 BG0303 08/26/15 15:20 S HDR1MCMD.TEMPFILE.H01 32.7K
3 BG0305 BG0305 08/27/15 11:00 S HDR1RGREEN7.TEMPX 32.7K
4 BG0307 BG0307 08/28/15 15:41 S HDR1P499.TEMPFILE.H01 32.7K
5 BG0309 BG0309 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
6 BG0311 BG0311 08/28/15 15:42 S HDR1P499.TEMPFILE.H01 32.7K
7 BG0313 BG0313 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
8 BG0315 BG0315 08/28/15 15:43 S HDR1P499.TEMPFILE.H01 32.7K
9 BG0317 BG0317 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
10 BG0319 BG0319 08/28/15 15:44 S HDR1P499.TEMPFILE.H01 32.7K
11 BG0321 BG0321 08/28/15 15:45 S HDR1P499.TEMPFILE.H01 32.7K
12 BG0323 BG0323 08/28/15 15:59 S HDR1MGDLMTL1.TEMP.H01 32.7K
13 BG0325 BG0325 08/28/15 16:08 S HDR1MGDLMTL1.TEMP.H01 32.7K
14 BG0327 BG0327 08/28/15 16:12 S HDR1MGDLMTL1.TEMP.H01 32.7K
15 BG0329 BG0329 08/31/15 09:59 S HDR1MGDLMTL1.TEMP.H01 32.7K
16 BG0331 BG0331 08/31/15 10:01 S HDR1MGDLMTL1.TEMP.H01 32.7K
….
Example 4:
Executing awsprint with tapelib that are specified along with recursive and detail options. This results in a report of all tape volumes in a tapelib.
vte1:~ # awsprint /tapelibFLR -r -d awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:32:05 PM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes With Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
*************************************************************************
1 BG0301 BG0301 08/26/15 15:19 S HDR1MCMD.TEMPFILE.H01 32.7K
*************************************************************************
DETAILS OF /tapelibFLR/CEL1_FLRP_FS1/BG0301
<EBCDIC LABELS>
56 Using Command Processors
VOL1BG0301 TCSBT
HDR1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
HDR2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #1: 3 x 80-byte blocks
0 Blocks Compressed 3 Blocks not Compressed
<TM>
<TM>
EOF1MCMD.TEMPFILE.H01BG030100010001 0152380000000000000IBM OS/VS 370
EOF2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #3: 2 x 80-byte blocks
0 Blocks Compressed 2 Blocks not Compressed
<TM>
<TM>
<1 x 32500-byte AWSMAP>
End of tape.
*************************************************************************
2 BG0302 BG0302 08/26/15 15:21 S HDR1MCMD.TEMPFILE.H01 32.7K
*************************************************************************
DETAILS OF /tapelibFLR/CEL1_FLRP_FS1/BG0302
<EBCDIC LABELS>
VOL1BG0302 TCSBT
HDR1MCMD.TEMPFILE.H01BG030200010001 0152380000000000000IBM OS/VS 370
HDR2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #1: 3 x 80-byte blocks
0 Blocks Compressed 3 Blocks not Compressed
<TM>
<TM>
EOF1MCMD.TEMPFILE.H01BG030200010001 0152380000000000000IBM OS/VS 370
EOF2U000000000000RGDLMCMD/STEP3 P 0004B1
...Tape File #3: 2 x 80-byte blocks
0 Blocks Compressed 2 Blocks not Compressed
<TM>
<TM>
<1 x 32500-byte AWSMAP>
End of tape.
*************************************************************************
Example 5:
Executing awsprint with recursive and fewer options.
vte1:~ # awsprint /tapelibFLR -r -l awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:32:19 PM
Path: /tapelibFLR
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BFL499 08/28/15 15:45 2.3K
2 BFL500 08/20/15 14:01 2.2K
3 BFL501 09/01/15 10:14 18.0K
4 BFL502 09/14/15 13:16 144K
5 BFL503 09/02/15 11:07 145K
6 BFL504 09/02/15 10:22 2.6K
7 BFL601 09/02/15 10:23 4.9K
8 BFL602 09/02/15 10:23 8.0K
9 BFL603 09/02/15 10:23 9.5K
10 BFL999 09/02/15 11:27 593K
11 BFLABC 08/25/15 11:01 3.4K
12 BFLBG1 09/01/15 10:29 18.0K
13 BFLBG6 08/24/15 14:33 320
14 BFLBG9 08/24/15 16:20 320
15 BFLBGA 08/25/15 11:05 5.7K
16 BFLGR1 08/27/15 11:01 145K
17 BFLM10 08/26/15 09:27 15.5K
18 BFLMT1 08/25/15 13:38 0
19 BFLMT2 08/25/15 14:00 0
20 BFLMT3 08/25/15 14:03 0
21 BFLMT4 08/25/15 14:04 0
22 BFLMT5 08/25/15 14:05 0
23 BFLMT7 08/25/15 14:17 0
Using Command Processors 57
24 BFLXXX 08/25/15 11:03 9.5K
25 CEL1_F 09/14/15 14:27 10.0K
26 CEL1_F 09/13/15 23:02 10.0K
************************************************************************* awsprint Version 7.40-15840, Compiled Jul 2 2015 14:12:01
Sorted by Name 09/14/2015 02:32:19 PM
Path: /tapelibFLR/CEL1_FLRP_FS1
Selection Criteria: All Tapes Without Details
NO. NAME VOLSER DATE TIME LBL TAPE INFO TAPE SIZE FLR EXP
1 BG0301 08/26/15 15:19 32.7K
2 BG0302 08/26/15 15:21 32.7K
3 BG0304 08/27/15 11:01 32.7K
4 BG0306 08/28/15 15:41 32.7K
5 BG0308 08/28/15 15:42 32.7K
6 BG0310 08/28/15 15:42 32.7K
7 BG0312 08/28/15 15:42 32.7K
8 BG0314 08/28/15 15:43 32.7K
9 BG0316 08/28/15 15:43 32.7K
10 BG0318 08/28/15 15:44 32.7K
11 BG0320 08/28/15 15:44 32.7K
12 BG0322 08/28/15 15:45 32.7K
13 BG0324 08/28/15 16:05 32.7K
14 BG0326 08/28/15 16:11 32.7K
15 BG0328 08/31/15 09:56 32.7K
16 BG0330 08/31/15 10:01 32.7K
17 BG0332 08/31/15 10:02 32.7K
18 BG0334 08/31/15 10:04 32.7K
19 BG0336 09/01/15 10:08 32.7
Obtaining VNX Replication Information: CP504
CP504 collects the replication statistics of all VNX/base and expansion VNX file systems on which replication has been enabled.
DLm version 4.0 and later supports collecting replication statistics from the expansion VNX.
Submit CP504 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
CP504 syntax
The CP504 command syntax is:
//GO EXEC DLMCMDP1,CMD=504,UNIT=unitid1,
// VCMD='report type'
//GO EXEC DLMCMDPR,CMD=504,UNIT=unitid1,UNIT2=unit2,
// VCMD='report type'
//GO EXEC DLMCPRUN,CMD=504,UNIT=unitid,
// VCMD='report type'
CP504 parameters
This section provides an overview of CP504 parameters.
Table 13. CP504 parameter
Parameter
VCMD
Discipline
Report types:
● QUICK
● SUMMARY
● VERBOSE
58 Using Command Processors
Sample JCL
This section provides an overview of sample JCL.
CP504:
//GO4 EXEC DLMCMDP1,CMD=504,UNIT=(/F207,,,SMSHONOR),CMD2=BG1,
// VCMD='QUICK'
//GO4 EXEC DLMCMDPR,CMD=504,UNIT=/F200,UNIT2=F201,
// VCMD='QUICK'
//GO5 EXEC DLMCMDP1,CMD=504,UNIT=(/F207,,,SMSHONOR),CMD2=BG1,
// VCMD='SUMMARY'
//GO5 EXEC DLMCMDPR,CMD=504,UNIT=/F200,UNIT2=F201,
// VCMD='SUMMARY'
//GO6 EXEC DLMCMDP1,CMD=504,UNIT=(/F207,,,SMSHONOR),CMD2=BG1,
// VCMD='VERBOSE'
//GO6 EXEC DLMCMDPR,CMD=504,UNIT=/F200,UNIT2=F201,
// VCMD='VERBOSE'
//GO EXEC DLMCPRUN,CMD=504,UNIT=/F200,
// VCMD='QUICK'
QUICK report
This section provides an overview of QUICK report.
The QUICK report displays the following replication statistics:
● Destination VOLSER Range
● Time elapsed since last sync (Minutes)
● Avg Transfer Rate (MB/s)
Sample output
This section shows the sample of a QUICK report.
Sample QUICK report:
DLMCMD1 Runtime Report 19 Sep 2013 3:15pm
Parameters:
Input: CMD(504) DEBUG() FILE(504) PATH(DEFAULT) VCMD(QUICK) WAIT(600)
COMMAND: 504
VTE COMMAND: QUICK
PATH: DEFAULT
FILE: BFL504.FLAT
TIMESTAMP: 20130919-15:15:00-52096
DEBUG: Off
Task Name: RGCMDPRO
Task ID J0016132
Task User: RGREEN7
DLMCMD2 Runtime Report 19 Sep 2013 3:15pm
Parameters:
Input: CMD(504) DEBUG() TLIB(DEFAULT) CPARMS()
COMMAND: 504
Cmd Parms:
Tape Library: DEFAULT
DEBUG:
Built Command: RUNWAIT (600) 504 "QUICK" "DEFAULT" "BFL504.FLAT"
"20130919-15:15:00-52096"
DLMCMD VER 4.11 DLMCTRL = 2100
2013/09/19 15:15:03 CMD ISSUED: RUNWAIT (600) 504 "QUICK" "DEFAULT" "BFL504.FLAT"
"20130919-15:15:00-52096"
20130919-15:15:00-52096
EMC Replication Stats Collection Tool (504) v4.0.0-r3001
Thu Sep 19 15:23:49 EDT 2013
Report Type : QUICK
Using Command Processors 59
========================================================
Base Unit
--------------------------------------------------------
Destination VOLSER Time Since Avg Transfer
Range Last Sync (Mins) Rate (MB/s)
-------------------------------------------------------tapelibTGT_50 7.67 1.58
tapelibTGT_51 15.33 0.38
tapelibTGT_52 70.83 0.50
tapelibTGT_53 73.00 0.38
tapelibTGT_54 10.33 0.35
tapelibTGT_55 7.67 1.97
tapelibTGT_56 11.67 0.09
tapelibTGT_57 71.17 0.24
tapelibTGT_58 75.50 0.38
tapelibTGT_59 11.17 0.33
tapelibTGT_60 7.67 0.09
tapelibTGT_61 8.83 0.91
tapelibTGT_62 69.33 0.39
tapelibTGT_63 71.00 0.41
tapelibTGT_64 9.50 0.03
tapelibTGT_65 8.83 0.03
tapelibTGT_66 7.33 0.33
tapelibTGT_67 71.17 0.06
tapelibTGT_68 80.33 0.27
tapelibTGT_69 9.50 0.06
tapelibTGT_70 7.00 0.52
tapelibTGT_71 8.33 0.33
tapelibTGT_72 74.83 5.21
tapelibTGT_73 79.33 0.53
tapelibTGT_74 15.50 0.34
Margin of error for Time Since Last Sync (seconds): 1
Expansion Unit
--------------------------------------------------------
Destination VOLSER Time Since Avg Transfer
Range Last Sync (Mins) Rate (MB/s)
-------------------------------------------------------tapelibTGT_50 8.03 1.58
tapelibTGT_51 15.70 0.38
tapelibTGT_52 71.20 0.50
tapelibTGT_53 73.37 0.38
tapelibTGT_54 10.70 0.35
tapelibTGT_55 8.03 1.97
tapelibTGT_56 12.03 0.09
tapelibTGT_57 71.53 0.24
tapelibTGT_58 75.87 0.38
tapelibTGT_59 11.53 0.33
tapelibTGT_60 8.03 0.09
tapelibTGT_61 9.20 0.91
tapelibTGT_62 69.70 0.39
tapelibTGT_63 71.37 0.41
tapelibTGT_64 9.87 0.03
tapelibTGT_65 9.20 0.03
tapelibTGT_66 7.70 0.33
tapelibTGT_67 71.53 0.06
tapelibTGT_68 71.03 0.27
tapelibTGT_69 9.87 0.06
tapelibTGT_70 7.37 0.52
tapelibTGT_71 8.70 0.33
tapelibTGT_72 75.20 5.21
tapelibTGT_73 79.70 0.53
tapelibTGT_74 15.87 0.34
Margin of error for Time Since Last Sync (seconds): 11
60 Using Command Processors
SUMMARY report
This section provides an overview of SUMMARY report.
Table 14. Summary report details
Report fields
Report Execution Time
Replication session name
Source VOLSER
Destination VOLSER
Max out of Sync Time
Last Data Sync Time
Time elapsed since last sync (Minutes)
Source DLm Status
Destination DLm Status
DLm Network Status
Source Network Interface
Destination Network Interface
Avg Transfer Rate (MB/s)
Margin of error since last sync
Description
Time when the report was created
Name of the replication session
VOLSER range that is the source for this replication session
VOLSER range on a remote DLm that is the destination for this replication session
Maximum time between data synchronization of the destination VOLSER range with the source VOLSER range
Time when the last data synchronization was done between the source and destination VOLSER ranges
Time elapsed since the last data synchronization
Status of the source DLm
Status of the destination DLm
Network status between the source and destination DLm systems
Network interface that is part of this replication session at the source DLm
Network interface that is part of this replication session at the destination DLm
Average data transfer rate for this replication session
Accuracy of the elapsed since last sync value in seconds
Sample output
Sample SUMMARY report is shown below:
DLMCMD1 Runtime Report 19 Sep 2013 2:51pm
Parameters:
Input: CMD(504) DEBUG() FILE(504) PATH(DEFAULT) VCMD(SUMMARY) WAIT(600)
COMMAND: 504
VTE COMMAND: SUMMARY
PATH: DEFAULT
FILE: BFL504.FLAT
TIMESTAMP: 20130919-14:51:06-42025
DEBUG: Off
Task Name: RGCMDPRO
Task ID J0016130
Task User: RGREEN7
DLMCMD2 Runtime Report 19 Sep 2013 2:51pm
Parameters:
Input: CMD(504) DEBUG() TLIB(DEFAULT) CPARMS()
COMMAND: 504
Cmd Parms:
Tape Library: DEFAULT
DEBUG:
Built Command: RUNWAIT (600) 504 "SUMMARY" "DEFAULT" "BFL504.FLAT"
"20130919-14:51:06-42025"
DLMCMD VER 4.11 DLMCTRL = 2100
2013/09/19 14:51:10 CMD ISSUED: RUNWAIT (600) 504 "SUMMARY" "DEFAULT" "BFL504.FLAT"
"20130919-14:51:06-42025"
Using Command Processors 61
20130919-14:51:06-42025
EMC Replication Stats Collection Tool (504) v4.0.0-r3001
Thu Sep 19 14:59:45 EDT 2013
Report Type : SUMMARY
========================================================
Base Unit
--------------------------------------------------------
Replication Name : Rep-50
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Thu Sep 19 14:59:46 EDT 2013
Last Data Sync Time : Thu Sep 19 14:47:20 EDT 2013
Time Since Last Sync : 12.43 minutes
Destination VOLSER : tapelibTGT_50
Destination Network Interface : 10.60.2.30
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 1.58 (MB/s)
========================================================
Margin of error for Time Since Last Sync (seconds): 1
Expansion Unit
--------------------------------------------------------
Replication Name : Rep-50
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Thu Sep 19 14:59:47 EDT 2013
Last Data Sync Time : Thu Sep 19 14:47:20 EDT 2013
Time Since Last Sync : 12.45 minutes
Destination VOLSER : tapelibTGT_50
Destination Network Interface : 10.60.2.30
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 1.58 (MB/s)
========================================================
Margin of error for Time Since Last Sync (seconds): 1
VERBOSE report
This section provides an overview of VERBOSE report.
This detailed replication data report is typically generated by Dell Technologies Customer Support personnel to analyze or troubleshoot replication issues. CP504 does not modify or format the data that are collected from the nas_replicate command. It presents the data as is to the mainframe. Therefore, it may not be comprehensive to anyone other than a Dell
Technologies Customer Support representative. The details include:
● Report Execution Time
● ID
● Name
● Source Status
● Network Status
● Destination Status
● Last Sync Time
● Type
● Celerra Network Server
● Dart Interconnect
● Peer Dart Interconnect
● Replication Role
● Source file system
● Source Data Mover
● Source Interface
● Source Control Port
● Source Current Data Port
● Destination file system
● Destination Data Mover
● Destination Interface
62 Using Command Processors
● Destination Control Port
● Destination Data Port
● Max Out of Sync Time (minutes)
● Next Transfer Size (KB)
● Current Transfer Size (KB)
● Current Transfer Remain (KB)
● Estimated Completion Time
● Current Transfer is Full Copy
● Current Transfer Rate (KB/s)
● Current Read Rate (KB/s)
● Current Write Rate (KB/s)
● Previous Transfer Rate (KB/s)
● Previous Read Rate (KB/s)
● Previous Write Rate (KB/s)
● Average Transfer Rate (KB/s)
● Average Read Rate (KB/s)
Sample output
Sample VERBOSE report is shown below:
DLMCMD1 Runtime Report 19 Sep 2013 3:16pm
Parameters:
Input: CMD(504) DEBUG() FILE(504) PATH(DEFAULT) VCMD(VERBOSE) WAIT(600)
COMMAND: 504
VTE COMMAND: VERBOSE
PATH: DEFAULT
FILE: BFL504.FLAT
TIMESTAMP: 20130919-15:16:33-99929
DEBUG: Off
Task Name: RGCMDPRO
Task ID J0016132
Task User: RGREEN7
DLMCMD2 Runtime Report 19 Sep 2013 3:16pm
Parameters:
Input: CMD(504) DEBUG() TLIB(DEFAULT) CPARMS()
COMMAND: 504
Cmd Parms:
Tape Library: DEFAULT
DEBUG:
Built Command: RUNWAIT (600) 504 "VERBOSE" "DEFAULT" "BFL504.FLAT"
"20130919-15:16:33-99929"
DLMCMD VER 4.11 DLMCTRL = 2100
2013/09/19 15:16:37 CMD ISSUED: RUNWAIT (600) 504 "VERBOSE" "DEFAULT" "BFL504.FLAT"
"20130919-15:16:33-99929"
20130919-15:16:33-99929
EMC Replication Stats Collection Tool (504) v4.0.0-r3001
Thu Sep 19 15:25:22 EDT 2013
Report Type : VERBOSE
================================================================================
Base Unit
--------------------------------------------------------------------------------
ID = 232_FNM00091100069_0000_258_APM00093100507_0000
Name = Rep-59
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Thu Sep 19 15:12:50 EDT 2013
Type = file system
Celerra Network Server = g2e
Dart Interconnect = g2bS6_g2eS6
Peer Dart Interconnect = 60003
Replication Role = source
Source file system = tapelibREP_59
Source Data Mover = server_6
Source Interface = 10.55.6.30
Source Control Port = 0
Using Command Processors 63
Source Current Data Port = 0
Destination file system = 91
Destination Data Mover = server_6
Destination Interface = 10.60.6.30
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Next Transfer Size (KB) = 0
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 220
Previous Read Rate (KB/s) = 3353
Previous Write Rate (KB/s) = 192
Average Transfer Rate (KB/s) = 343
Average Read Rate (KB/s) = 14602
Average Write Rate (KB/s) = 2574
...
ID = 262_FNM00091100069_0000_288_APM00093100507_0000
Name = Rep-74
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Thu Sep 19 15:18:10 EDT 2013
Type = file system
Celerra Network Server = g2e
Dart Interconnect = g2bS6_g2eS6
Peer Dart Interconnect = 60003
Replication Role = source
Source file system = tapelibREP_74
Source Data Mover = server_6
Source Interface = 10.55.6.30
Source Control Port = 0
Source Current Data Port = 0
Destination file system = 106
Destination Data Mover = server_6
Destination Interface = 10.60.6.30
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Next Transfer Size (KB) = 0
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 266
Previous Read Rate (KB/s) = 742
Previous Write Rate (KB/s) = 234
Average Transfer Rate (KB/s) = 350
Average Read Rate (KB/s) = 4707
Average Write Rate (KB/s) = 254
Expansion Unit
--------------------------------------------------------
ID 232_FNM00091100069_0000_258_APM00093100507_0000
Name = Rep-59
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Thu Sep 19 15:12:50 EDT 2013
Type = file system
Celerra Network Server = g2b
Dart Interconnect = g2eS6_g2bS6
Peer Dart Interconnect = 60003
Replication Role = destination
Source file system = 66
Source Data Mover = server_6
64 Using Command Processors
Source Interface = 10.55.6.30
Source Control Port = 0
Source Current Data Port = 0
Destination file system = tapelibTGT_59
Destination Data Mover = server_6
Destination Interface = 10.60.6.30
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Next Transfer Size (KB) = 0
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 220
Previous Read Rate (KB/s) = 3353
Previous Write Rate (KB/s) = 192
Average Transfer Rate (KB/s) = 343
Average Read Rate (KB/s) = 14602
Average Write Rate (KB/s) = 2574
Obtaining Data Domain and PowerProtect: CP601,
CP602, CP603
NOTE: DLm2500 does not support CP601, CP602, and CP603.
CP601
CP601 generates Data Domain and PowerProtect system utilization statistics and makes the reports available to the mainframe.
A Data Domain and PowerProtect system compresses data at two levels: global and local. Global compression compares received data with the data that are already stored on disks. Duplicate data need not be stored again, while data that is new is compressed before being written to disk. Compressing the new data is called local compression.
Global compression is the same as data deduplication while local compression is the same as hardware compression.
The data compression that is achieved through data deduplication and hardware compression is collectively referred to as total compression in this document.
Total compression = Data deduplication + hardware compression
The Data Domain and PowerProtect system deduplicates incoming tape data before storing it onto the disk. In this process, the actual amount of data to be stored on the disk is much less than the incoming data. CP601 reports the storage usage statistics, which include the following:
● Total amount of incoming data from VTEs
● Total amount of data that are stored on the disk after total compression
● Total available space for data storage
● Estimated amount of storage that will be cleaned during next Data Domain and PowerProtect clean operation
CP601 collects the system usage data and saves it in a FLAT file on the VTE in EBCDIC format. This file can be retrieved by the mainframe.
Submit CP601 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
CP601 syntax
The CP601 command syntax is:
//GO EXEC DLMCMDP1,CMD=601,UNIT=unitid1
Using Command Processors 65
//GO EXEC DLMCMDPR,CMD=601,UNIT=unitid1,UNIT2=unit2
//GO EXEC DLMCPRUN,CMD=601,UNIT=unitid
CP601 parameters
This section provides an overview of CP601 parameters.
CP601 command parameters - none .
Sample JCL:
//GO7 EXEC DLMCMDP1,CMD=601,UNIT=(/F207,,,SMSHONOR),CMD2=BG1
//GO7 EXEC DLMCMDPR,CMD=601,UNIT=/F200,UNIT2=F201
//GO EXEC DLMCPRUN,CMD=601,UNIT=/F200
Sample output
The CP601 example that is shown above produces a storage utilization report as shown in the below sample:
EMC Data Domain Storage Utilization Report (601) v4.4.0-r5798
Wed Sep 2 10:12:44 EDT 2015
Report Type : SYSTEM
================================================================================
Data Domain system: DD-1
--------------------------------------------------------------------------------
Total data received (GiB) : 7.4
Total storage capacity of Data Domain system (GiB): 21265.3
Total storage used (post compression) (GiB) : 7.9
Total storage available (GiB) : 21257.3
Use% : 0%
Cleanable storage (GiB) : 0.0
Note: * Estimated based on last cleaning of 2015/09/01 06:02:01.
--------------------------------------------------------------------------------
================================================================================
Table 15. CP601 report fields
Field
Total data received (GiB)
Total storage capacity of Data Domain and PowerProtect system (GiB)
Total storage used (post compression) (GiB)
Total storage available (GiB)
Use%
Cleanable storage (GiB)
Description
Total amount of data received by the Data Domain and
PowerProtect system.
Total storage capacity of the Data Domain and PowerProtect system.
Total storage used after achieving data deduplication and hardware compression of the data.
● Storage available
● {Total storage capacity of Data Domain and PowerProtect system - Total storage used (post compression) }
● This is the storage available for data post data deduplication and hardware compression.
● For example, if total available capacity is 100 GB then it can store 500 GB of received data if the size of received data is 100 GB after total compression.
% of storage used.
Data Domain and PowerProtect does not make space available when a file is deleted. This space is made available only after a periodic cleanup is run on Data Domain and PowerProtect.
This value shows the estimated amount of storage that will be cleaned up during next Data Domain and PowerProtect
66 Using Command Processors
Table 15. CP601 report fields (continued)
Field Description cleanup operation. This estimation is based on last cleanup operation.
CP602
This section provides an overview of CP602.
The Data Domain and PowerProtect system deduplicates incoming tape data before storing it to disk. As a result of this process, the data size to be stored on disk is much smaller than the received data size.
CP602 generates a report that provides data compression statistics for the Data Domain and PowerProtect system. The compression report could provide data compression statistics for the entire Data Domain and PowerProtect system (DEFAULT report), for particular tape libraries (SUMMARY report), or for each tape file (VOLSER) in the user-specified tape library
(DETAILED or FULL report).
Submit CP602 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
CP602 syntax
The CP602 command syntax is:
//GO EXEC DLMCMDP1,CMD=602,UNIT=unitid1,
// VCMD='SUMMARY|DETAILED|FULL'
//GO EXEC DLMCMDPR,CMD=602,UNIT=unitid1,UNIT2=unit2,
// VCMD='SUMMARY|DETAILED|FULL',
// DAYS='<days count>',
// SIZEUNIT='Bytes|KBs|MBs|GBs|TBs',
// TLIB='tapelibname|ALL'
//GO EXEC DLMCPRUN,CMD=602,UNIT=unitid,
// VCMD='SUMMARY|DETAILED|FULL',
// SIZEUNIT='Bytes|KBs|MBs|GBs|TBs',
// TLIB='tapelibname|ALL'
CP602 parameters
This section provides an overview of CP602 parameters.
Table 16. CP602 parameters
Parameter
VCMD
Description
Specifies the report type. The valid values are:
● Blank—reports compression statistics for the whole Data Domain and PowerProtect.
● SUMMARY—reports only the total information about whole tape libraries.
● DETAILED—lists all Volsers individually but hides scratch volumes;
● FULL—same as DETAILED, but includes scratch volumes
This is an optional parameter.
DAYS
SIZEUNIT tapelibname|ALL
Specifies the number of days (<days count>). The report lists only those files that were changed in the past <days count> days. Specifying a value of 0 indicates that you want the report to list all the files and no filtering is required. This is an optional parameter and is applicable to SUMMARY,
DETAILED, and FULL report types.
Specifies the unit in which the volume size must be reported. The default size unit is bytes. Other valid units are Bytes, KBs, MBs, GBs, and TBs. This is an optional parameter and is only applicable to DETAILED and FULL report types.
Name of the tape library for which you want to retrieve information. The TLIB parameter should not be more than 30 characters in length. This is an optional parameter.
Using Command Processors 67
Sample JCL
This section describes a sample JCL.
//GO8A EXEC DLMCMDP1,CMD=602,UNIT=(/F207,,,SMSHONOR),CMD2=YK1,
// WAIT=500
//GO8B EXEC DLMCMDPR,CMD=602,UNIT=/4305,UNIT2=4305,
// VCMD='SUMMARY',TLIB='ALL'
//GO8C EXEC DLMCMDPR,CMD=602,UNIT=/4305,UNIT2=4305,
// VCMD='DETAILED',DAYS='7',SIZEUNIT='GBs'
//GO EXEC DLMCPRUN,CMD=602,UNIT=/F200,
// VCMD='SUMMARY',
// DAYS='7',
// SIZEUNIT='KBs',
// TLIB='/tapelibBACKUP'
Sample output
This section provides an overview of sample output.
The SUMMARY report produces compression information about the specified tape libraries. The following is a sample summary report:
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT3
--------------------------------------------------------------------------------
MTree: /data/col1/SMT3
Total files: 18; bytes/storage_used: 3.7
Original Bytes: 18,432
Globally Compressed: 18,432
Locally Compressed: 1,657
Meta-data: 3,384
--------------------------------------------------------------------------------
MTree: /backup
Total files: 10; bytes/storage_used: 3.4
Original Bytes: 10,287
Globally Compressed: 10,287
Locally Compressed: 1,051
Meta-data: 1,952
--------------------------------------------------------------------------------
Tapelib: tapelibMTL1
--------------------------------------------------------------------------------
MTree: /data/col1/SMT1
Total files: 106; bytes/storage_used: 2.7
Original Bytes: 156,592
Globally Compressed: 156,592
Locally Compressed: 30,437
Meta-data: 27,200
--------------------------------------------------------------------------------
MTree: /backup
Total files: 1; bytes/storage_used: 3.8
Original Bytes: 1,024
Globally Compressed: 1,024
Locally Compressed: 80
Meta-data: 188
--------------------------------------------------------------------------------
The DETAILED or FULL report produces compression information about each VOLSER in the tape library.
NOTE: The FULL report type shows scratch volumes while the DETAILED report type does not.
The report displays one list of VOLSERs regardless of the MTree or file system it resides in.
68 Using Command Processors
The following is a sample FULL report with SIZEUNIT='Bytes':
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT2
--------------------------------------------------------------------------------
Volser Original Globally Locally MetaData Compression
Bytes Compressed Compressed Bytes Rate
Bytes
--------------------------------------------------------------------------------
~YK0019 416 2508 439 296 0.6
YK0001 1004033482 1007375842 77643694 4305752 12.3
YK0003 10040033482 10073739226 774817057 43284212 12.3
YK0005 10007033482 10045962442 758106885 43263764 12.5
YK0007 42939960274 42992151951 1296643935 158322140 29.5
YK0009 214739055250 59929833277 2282742736 220628708 85.8
YK0011 42939960274 43085565622 1299094014 158694020 29.5
YK0013 775996422260 507187571395 16125890311 1867861772 43.1
YK0015 214739055250 137176779584 4375873981 505198988 44.0
YK0017 131739936706 132186610279 3985585902 486862784 29.5
~YK0016 416 2508 439 296 0.6
~YK0018 416 2508 439 296 0.6
YK0000 10040033482 8683548398 672166616 37312316 14.2
YK0002 100433482 100757962 7773745 430064 12.2
~YK0004 416 2508 440 296 0.6
YK0006 42939960274 43085551788 1299151714 158697656 29.5
YK0008 42939960274 43085556044 1299066476 158680952 29.5
YK0010 42939960274 43085528115 1299091970 158685308 29.5
YK0012 214739055250 76472545373 2730207043 281599244 71.3
YK0014 214739055250 214545054444 6471522748 790163180 29.6
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Data Domain system: DD-2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
============================================================
The following is a sample DETAILED report with SIZEUNIT='GBs':
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT2
--------------------------------------------------------------------------------
Volser Original Globally Locally MetaData Compression
GBs Compressed Compressed GBs Rate
GBs GBs
--------------------------------------------------------------------------------
YK0001 0.94 0.94 0.07 0.00 12.3
YK0003 9.35 9.38 0.72 0.04 12.3
YK0005 9.32 9.36 0.71 0.04 12.5
YK0007 39.99 40.04 1.21 0.15 29.5
YK0009 199.99 55.81 2.13 0.21 85.8
YK0011 39.99 40.13 1.21 0.15 29.5
YK0013 722.70 472.36 15.02 1.74 43.1
YK0015 199.99 127.76 4.08 0.47 44.0
YK0017 122.69 123.11 3.71 0.45 29.5
YK0000 9.35 8.09 0.63 0.03 14.2
YK0002 0.09 0.09 0.01 0.00 12.2
YK0006 39.99 40.13 1.21 0.15 29.5
YK0008 39.99 40.13 1.21 0.15 29.5
YK0010 39.99 40.13 1.21 0.15 29.5
YK0012 199.99 71.22 2.54 0.26 71.3
YK0014 199.99 199.81 6.03 0.74 29.6
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Data Domain system: DD-2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
=====================================================
Using Command Processors 69
NOTE: When a tape is deleted or truncated in a Data Domain and PowerProtect filesystem, Data Domain and PowerProtect does not immediately delete the data; however, it is unavailable for reuse. It is recovered for reuse when the next scheduled
Data Domain and PowerProtect cleanup operation is run. The cleanup frees up storage. Therefore, data that are generated before the cleanup does not include the result of file deletion and truncation.
Table 17. CP602 report fields
Field
Filesystem
Volser
Original <sizeunit>
Globally Compressed
Locally Compressed
MetaData <sizeunit>
Compression Rate
Description
The file system where the volser actually resides
The Volser in the tape library
The original file size in Bytes, KBs, MBs, GBs, or TBs
File size after inline deduplication (Bytes, KBs, MBs, GBs, or
TBs)
File size after local compression is applied (Bytes, KBs, MBs,
GBs, or TBs)
Any additional information in bytes or GBs that Data Domain and PowerProtect stores for this file. The sum of the Locally
Compressed and MetaData size is the actual size that Data
Domain and PowerProtect stores for the file.
The ratio of <Original size> to (<Locally Compressed> + <
MetaData size>)
CP603
This section provides an overview of CP603.
This Command Processor reports the following Data Domain and PowerProtect replication information:
● Replication configuration
● Replication status
● Replication statistics
● Replication performance statistics
● Historical replication data for the past 24 hours
Submit CP603 from the mainframe by using the DLMCMDPR , DLMCMDP1 , or DLMCPRUN procedure.
CP603 syntax
The CP603 command syntax is:
//GO EXEC DLMCMDP1,CMD=603,UNIT=unitid1,
// CPARMS='command parameters'
//GO EXEC DLMCMDPR,CMD=603,UNIT=unitid1, UNIT2=unit2,
// CPARMS='command parameters'
//GO EXEC DLMCPRUN,CMD=603,UNIT=unitid,
// CPARMS='command parameters'
CP603 parameters
This section provides an overview of CP603 parameters.
Table 18. CP603 parameters
Parameter
CPARMS
Description
Enter one of the following reports to be generated:
70 Using Command Processors
Table 18. CP603 parameters
Parameter Description
● STATUS — Status report containing the current replication status.
● STATS —Statistics report containing replication statistics.
● PERF — Performance report containing replication performance statistics.
● HIST — History report containing replication I/O information.
● ALL — All of the above reports.
NOTE: ALL is the default value.
Sample JCL:
This section describes the sample JCL.
//GO10 EXEC DLMCMDP1,CMD=603,UNIT=(/F207,,,SMSHONOR),CMD2=BG1,
// CPARMS='STATUS'
//GO10 EXEC DLMCMDPR,CMD=603,UNIT=/F200,UNIT2=F201,
// CPARMS='STATUS'
//GO EXEC DLMCPRUN,CMD=603,UNIT=/F200,
// CPARMS='STATUS'
Sample output
This section provides an overview of sample output.
20150902-10:10:12-86950
EMC Data Domain Replication Statistics Report (603) v4.4.0-r5798
Wed Sep 2 10:13:18 EDT 2015
Report Type : REPLICATION STATUS
================================================================================
Data Domain system: DD-1
--------------------------------------------------------------------------------
REPLICATION CONFIG
--------------------------------------------------------------------------------
CTX Source Destination Connection Host and Port
--- ---------------------------- -----------------------------------------
-------------------------
2 mtree://a.b/data/col1/MTBKP1 mtree://DD1.corp.emc.com/data/col1/MTBKP1 a.b* (default)*
--- ---------------------------- ---------------------------------------- ------
----------
_______________________________
Low-bw-optim Encryption Enabled
------------ ---------- --------disabled disabled yes
--------- -------- -------
* Used for recovery only.
================================================================================
REPLICATION STATUS
--------------------------------------------------------------------------------
CTX: 2
Mode: destination
Destination: mtree://DD1.corp.emc.com/data/col1/MTBKP1
Enabled: yes
Low bandwidth optimization: disabled
Replication encryption: disabled
Replication propagate-retention-lock: disabled
Local filesystem status: enabled
Connection: idle since Wed Sep 2 10:00:03
State: normal
Error: no error
Using Command Processors 71
Sync'ed-as-of time: Wed Sep 2 10:00
Current throttle: unlimited (Recovery only)
================================================================================
Table 19. CP603 reports: REPLICATION CONFIG fields
Field Description
CTX
Source
Enabled
Destination
Connection
The context number for directory replication.
The Data Domain and PowerProtect system that receives data from backup applications.
The replication process is yes (enabled and available to replicate data) or no (disabled and not available to replicate data).
The Data Domain and PowerProtect system that receives data from the replication source Data Domain system.
A source Data Domain and PowerProtect system connects to the destination Data Domain and PowerProtect system by using the destination name as returned by the hostname command on the destination or by using a destination name or IP address and port that is given with the replication modify connection-host command. The destination hostname may not resolve to the correct IP address for the connection when connecting to an alternate interface on the destination or when a connection passes through a firewall.
Table 20. CP603 REPLICATION STATUS report fields
Field Description
CTX The context number for directory replication.
Mode
Destination
Enabled
Local file system status
Connection
State
Error
Sync'ed-as-of time
Current throttle
The role of the local system: source or destination.
The replication destination.
The enabled state (yes or no) of replication for each replication pair.
The status (enabled or disabled) of the local file system.
The most recent connection date and time or connection state for a replication pair.
The state of the replication process.
A listing of any errors in the replication process.
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ appears during replication initialization.
The current throttle setting.
Table 21. CP603 REPLICATION STATISTICS report fields
Field
CTX
Description
The context number for directory replication.
Destination
Network bytes sent
Pre-compressed bytes written to source
The replication destination.
The number of bytes sent over the network. Does not include TCP/IP headers. Includes internal replication control information, metadata, and file system data.
Indicates the number of bytes of pre-compressed data that are sent to the source.
72 Using Command Processors
Table 21. CP603 REPLICATION STATISTICS report fields (continued)
Field
Pre-compressed bytes sent to destination
Description
Indicates the number of bytes of pre-compressed data that are sent to the destination.
Pre-compressed bytes remaining
Files remaining
Compression ratio
Sync'ed-as-of time
The sum of the sizes of one or more files remaining to be replicated for this context. This includes the *entire* logical size of the current file being replicated, so if a large file is being replicated, this number may not change for a noticeable period—it changes only after the current file finishes.
The number of files that are not replicated.
The ratio of bytes transferred to network bytes transferred.
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ be displays during replication initialization.
Table 22. CP603 REPLICATION PERFORMANCE report fields
Field rctx://1
Description
Indicates the interval in seconds that the performance data represents. In this example, rctx is 1 second (default is 2 seconds).
Pre-Comp (KB/s)
Network (KB/s)
Streams
Busy Reading
Busy Meta
Waiting Dest.
Waiting Network
Virtual speed over the network. The number of kilobytes per second of pre-compressed data that were transferred over the network during the specified interval.
Data speed over the network. The number of kilobytes per second of compressed data that were transferred over the network during the specified interval.
Number of Streams used for the Context (number ranges from 1 to 9 ). If the Context is configured and enabled, the streams column displays 1 because one stream is reserved. If all eight streams are used, it displays 9.
When the source Data Domain and PowerProtect system is actively replicating data, the percent of that active time that is spent reading the source data.
When the source Data Domain and PowerProtect system is actively replicating data, the percent of that active time that is spent processing overhead data on behalf of the source data.
When the source Data Domain and PowerProtect system is waiting on an event while replicating, the percent of that time that is spent waiting on the destination Data Domain and
PowerProtect system.
When the source Data Domain and PowerProtect system is waiting on an event while replicating, the percent of that time that is spent waiting on the network.
Table 23. CP603 REPLICATION HISTORY report fields
Field Description
Sync-as-of Time
Pre-Comp (KB) Remaining
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ be displays during replication initialization.
The amount of pre-compression data that is not replicated.
Replicated (KB) Pre-Comp The amount of pre-compressed data that is replicated.
Using Command Processors 73
Table 23. CP603 REPLICATION HISTORY report fields (continued)
Field
Replicated (KB) Network
Description
The amount of compressed data sent over the network.
Obtaining Replication Information by VOLSER: CP804
CP804 is supported from DLm 5.4 and later, on DLm8500 with VNX, DD, or OneFS.
CP804 generates reports that provide replication statistics for each file system mounted on VTE. By using the TLIB and
PREFIX parameters the CP804 report is limited to either a specific tape library or to a single specific non-scratch VOLSER.
Submit CP804 from the mainframe by using the DLMCPRUN procedure.
CP804 syntax
The CP804 command syntax is:
//GO EXEC DLMCPRUN,CMD=804,UNIT=unitid1,
// REPORT='report type',
// TLIB='tape library',
// PREFIX='prefix'
CP804 parameters
The section provides an overview of CP804 parameters. All three parameters are optional.
Table 24. CP804 parameters
Parameter
REPORT
TLIB
PREFIX
Description
Type of the replication report you want to retrieve. Valid options are:
● SUMMARY (default value)
● DETAILED
● FULL
Name of the tape library for which you want to retrieve replication report. Valid options are:
● Tape library name
● ALL
By default, set to the UNIT path.
From 1 to 6 six uppercase alphanumeric characters [A-Z0-9] to filter the list of volumes, only volumes start with prefix will be processed. By default, all non-scratch volumes are processed.
SUMMARY Report: CP804
The SUMMARY report displays the replication statistics for each file system that is mounted on the VTE:
● Name
● Replication role
○ Not enabled for replication
○ Source
○ Destination
○ Cascade (Destination+Source)
74 Using Command Processors
○ Concurrent (Multi source)
○ Hybrid (Concurrent+Cascade)
● Source Status
○ Success (if all sources in success state)
○ Error (if all sources in error state)
○ Warning (some sources in success state, some sources in error state)
○ N/A (for Destination or Not enabled for replication roles)
● Last sync time (N/A for Destination and Not enabled for replication roles).
● Not replicated volumes count.
● Replicated volumes count.
Sample JCL
//GO EXEC DLMCPRUN,CMD=804,UNIT=/8700,
// REPORT='SUMMARY',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.4.0-122
Fri Aug 20 10:37:48 EDT 2021
Report Type : SUMMARY
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelibREP3/CEL1_P1_FS1
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:37:44
Not replicated volumes : 6
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes : 6
Replicated volumes : 8
=================================================================================
=================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
DETAILED Report: CP804
The DETAILED report for each file system that is mounted on the VTE displays similar statistics as SUMMARY report. The
DETAILED report also displays the 'List of not replicated volumes with mtime '.
Sample JCL
//GO EXEC DLMCPRUN,CMD=804,UNIT=/8700,
// REPORT='DETAILED',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.4.0-122
Fri Aug 20 10:39:10 EDT 2021
Report Type : DETAILED
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelibREP3/CEL1_P1_FS1
Using Command Processors 75
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:37:44
List of not replicated volumes for /tapelibREP3/CEL1_P1_FS1
Volume Mtime
VM0008 2021-08-20 10:37:57
VM0009 2021-08-20 10:39:10
VM0010 2021-08-20 10:39:15
VM0011 2021-08-20 10:39:18
VM0012 2021-08-20 10:39:19
VM0013 2021-08-20 10:39:22
Summary for /tapelibREP3/CEL1_P1_FS1
Not replicated volumes: 6
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes: 6
Replicated volumes : 8
================================================================================
================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
FULL Report: CP804
The DETAILED report for each file system that is mounted on the VTE displays similar statistics as SUMMARY report. The FULL report also displays the 'list of volumes with mtime and volume replication status (Not replicated or Replicated)'.
Sample JCL
//GO EXEC DLMCPRUN,CMD=804,UNIT=/8700,
// REPORT='FULL',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.4.0-122
Fri Aug 20 10:43:15 EDT 2021
Report Type : FULL
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelib/REP3/CEL1_P1_FS1
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:40:54
List of volumes for /tapelibREP3/CEL1_P1_FS1
Volume Mtime Replication Status
VM0000 2021-08-20 10:25:22 Replicated
VM0001 2021-08-20 10:25:29 Replicated
VM0002 2021-08-20 10:25:38 Replicated
VM0003 2021-08-20 10:25:46 Replicated
VM0004 2021-08-20 10:34:51 Replicated
VM0005 2021-08-20 10:34:53 Replicated
VM0006 2021-08-20 10:34:56 Replicated
VM0007 2021-08-20 10:34:59 Replicated
VM0008 2021-08-20 10:44:52 Not replicated
VM0009 2021-08-20 10:44:49 Not replicated
VM0010 2021-08-20 10:44:45 Not replicated
VM0011 2021-08-20 10:44:39 Not replicated
VM0012 2021-08-20 10:44:34 Not replicated
VM0013 2021-08-20 10:44:30 Not replicated
Summary for /tapelibREP3/CEL1_P1_FS1
Not replicated volumes: 6
76 Using Command Processors
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes: 6
Replicated volumes : 8
================================================================================
================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
Obtaining tape activity: CP988 and CP989
CP988 and CP989 are supported only on 4.5.3 and later and 5.x.
CP988
Command Processor CP988 retrieves statistics from a VOLSER range and generates a report of this data.
CP988 syntax
The CP988 command syntax:
//GO EXEC DLMCPRUN,CMD=988,UNIT=/unitid,
// REPORT=’report type’,
// STRTDATE=’start date’,
// ENDDATE=’end date’,
// SYNCTIME=’sync time’
CP988 parameters
This section provides an overview of CP988 parameters.
Table 25. CP988 parameters
Parameter
REPORT
STRTDATE
ENDDATE
NODENAME
NPROCS
Description throughput | maxtapes | stillinuse | slowmounts=NN | detail
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data preceding the date that is specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
vtename|ALL: Filters the input data to select a particular VTE
(or all VTEs). An example is NODENAME=vte1. The default value is ALL. This parameter is not case-sensitive.
NOTE: This parameter is used only for CP988 and ignored for CP989.
The number of processes (from 1 to 16) that can run statfmt in parallel.
NOTE: This parameter is introduced in DLm 5.0.1 and
DLm 4.5.4 releases.
Using Command Processors 77
Table 25. CP988 parameters (continued)
Parameter
TLIB
SYNCTIME
Description tapelibname|ALL:
● Filters the input data for a particular tape library or group of libraries.
● This parameter is used only for CP988 and ignored for
CP989.
The characters that are specified are matched against the tape library names of the input records. Only the characters that are specified, need to match for CP988 to accept a record. For example, if you specify TLIB=tapelib/G, and the
VTE paths include tapelib/G0, tapelib/G1, and so on, all of the tapelib/Gx records are processed.
NOTE: This parameter is case-sensitive.
HH/MM/SS: This parameter can be used only with the
STILLINUSE report (along with the ENDDATE parameter) to specify the point at which the STILLINUSE check will be applied. Besides, tapes that are mounted after SYNCTIME will be listed for user evaluation purposes.
Sample JCL
//GO EXEC DLMCPRUN,CMD=988,UNIT=/D301,
// REPORT='STILLINUSE',
// STRTDATE='01/01/2018',
// ENDDATE='02/21/2018',
// TLIB='/tapelibBACKUP',
// NODENAME='VTE1',NPROCS='2',
// SYNCTIME='01/01/01'
CP988 Sample Reports
This section provides an overview of CP988 sample reports.
THROUGHPUT report
================================================================================
PATHS INCLUDED IN STATS :
NODENAME PATH
vte1 /tapelibBACKUP2/DD1_FS1
vte2 /tapelibBACKUP2/DD1_FS1
--------------------------------------------------------------------------------
THROUGHPUT IN GB/HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT
08|OUT 09|OUT 10|OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT
20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN
08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN
20|IN 21|IN 22|IN 23|
78 Using Command Processors
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/11/21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=23 MAXMNT/HR=23
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/12/03| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 111.11| 111.11|
111.11| 111.11| 111.11| 111.11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 111.11| 111.11| 111.11| 111.11| 111.11| 111.11| 111.11| 111.11|
111.11| 111.11| 111.11| 111.11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=111G TOT/DAY=2000G OUT/DY=2000G IN/DY=0G MAXO/HR=111G MAXI/
HR=0G MOUNTS/DY=1 MAXMNT/HR=1
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/12/16| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=2 MAXMNT/HR=2
COUNT OF UNLOAD RECORDS : 26G
COUNT OF UNLOADS W/OUTPUT STATS: 13G
COUNT OF UNLOADS W/INPUT STATS : 0G
MAXIMUM OUTPUT/HR : 111G
MAXIMUM OUTPUT/DAY : 2000G
MAXIMUM INPUT/HR : 0G
Using Command Processors 79
MAXIMUM INPUT/DAY : 0G
MAXIMUM THROUGPUT/HR : 111G
MAXIMUM THROUGPUT/DAY : 2000G
MAXIMUM MOUNTS/HR : 23
MAXIMUM MOUNTS/DAY : 23
EFFECTIVE COMPRESSION RATIO : 1.0 to 1
AVERAGE MOUNT RESPONSE (SECS.) : 0.065
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (988) completed successfully!
MAXTAPES report vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
---------------------------------------------------------------------
MAX TAPES IN USE PER HR :
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
|YY/MM/DD| 00| 01| 02| 03| 04| 05| 06| 07| 08| 09| 10| 11|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
| | 12| 13| 14| 15| 16| 17| 18| 19| 20| 21| 22| 23|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
|17/05/22| ***| ***| ***| ***| ***| 2| 1| ***| ***| ***| ***| ***|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
| | ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
|17/05/31| ***| ***| ***| ***| ***| ***| ***| ***| ***| 1| 1| 1|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
| | 1| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***|
+--------+----+----+----+----+----+----+----+----+----+----+----+----+
TOP 10
SLOWEST
MOUNTS report
SLOWMOUNTS=10 report vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
------------------------------------------------------------
TOP 10 SLOWEST MOUNTS (SECS.):
NODENAME DURATION VOLSER DATE TIME PATH vte1 0.289 NLFW24 2017/05/31 12:15:26 vte1 0.267 700000 2017/05/31 09:56:15 vte1 0.210 700000 2017/05/31 09:41:57 vte1 0.208 700000 2017/05/31 11:56:26 vte1 0.200 700000 2017/05/31 10:58:21 vte1 0.193 700000 2017/05/31 09:26:15 vte1 0.170 700000 2017/05/31 10:16:39 vte1 0.157 700000 2017/05/31 09:28:57 vte1 0.156 700000 2017/05/31 11:07:30 vte1 0.148 700000 2017/05/31 10:55:41
------------------------------------------------------------
STILLINUSE report vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
------------------------------------------------------
VOLSERS IN USE AT SYNCTIME (06/06/2017 10:00:00)
NODENAME DEVICE VOLSER LAST MOUNTED vte1 F200 200915 2016/02/01 06:53:34
------------------------------------------------------
VOLSERS MOUNTED AFTER SYNCTIME (06/06/2017 10:00:00)
DATE TIME VOLSER NODENAME PATH
2017/06/19 10:17:56 BFL999 vte1
2017/06/27 06:06:12 YK5006 vte1
2017/06/27 06:09:54 YK5007 vte1
2017/06/27 06:12:36 YK5008 vte1
2017/06/27 06:12:37 BFLYK vte1
2017/06/27 06:13:39 YK5009 vte1
2017/06/27 06:14:45 YK5004 vte1
80 Using Command Processors
2017/06/28 16:02:38 YK5005 vte1
------------------------------------------------------
CP989
Command Processor CP989 retrieves statistics from a local VTE and generates a report of this data.
CP989 syntax
The CP989 command syntax:
//GO EXEC DLMCPRUN,CMD=989,UNIT=/unitid,
// REPORT=’report type’,
// STRTDATE=’start date',
// ENDDATE=’end date’
CP989 parameters
This section provides an overview of CP989 parameters.
Table 26. CP989 parameters
Parameter
REPORT
STRTDATE
ENDDATE
SYNCTIME
Description throughput | maxtapes | stillinuse | slowmounts=NN | detail
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data preceding the date that is specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
HH/MM/SS: This parameter can be used only with the
STILLINUSE report (along with the ENDDATE parameter) to specify the point at which the STILLINUSE check will be applied. Besides, tapes that are mounted after SYNCTIME will be listed for user evaluation purposes.
Sample JCL
//GO EXEC DLMCPRUN,CMD=989,UNIT=/8A00,
// REPORT='THROUGHPUT',
// STRTDATE='01/01/2018',
// ENDDATE='01/24/2018'
Using Command Processors 81
CP989 Sample Reports
This section provides an overview of CP989 sample reports.
THROUGHPUT report
================================================================================
NODENAME = vte2
--------------------------------------------------------------------------------
THROUGHPUT IN GB/HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT
08|OUT 09|OUT 10|OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT
20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN
08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN
20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/03| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.14|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.14| 0.05| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=72 MAXMNT/HR=19
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/04| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.28|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.12| 0.41| 0.26| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=1G OUT/DY=1G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=30 MAXMNT/HR=11
82 Using Command Processors
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/14| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 95.55| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=96G TOT/DAY=96G OUT/DY=96G IN/DY=0G MAXO/HR=96G MAXI/HR=0G
MOUNTS/DY=3 MAXMNT/HR=3
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/17| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 23.88| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 23.88| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=24G TOT/DAY=48G OUT/DY=48G IN/DY=0G MAXO/HR=24G MAXI/HR=0G
MOUNTS/DY=4 MAXMNT/HR=3
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/19| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=102 MAXMNT/HR=99
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/20| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
Using Command Processors 83
MAXTAPES report
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=15 MAXMNT/HR=7
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|19/06/27| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=0 MAXMNT/HR=0
COUNT OF UNLOAD RECORDS : 220G
COUNT OF UNLOADS W/OUTPUT STATS: 72G
COUNT OF UNLOADS W/INPUT STATS : 0G
MAXIMUM OUTPUT/HR : 96G
MAXIMUM OUTPUT/DAY : 96G
MAXIMUM INPUT/HR : 0G
MAXIMUM INPUT/DAY : 0G
MAXIMUM THROUGPUT/HR : 96G
MAXIMUM THROUGPUT/DAY : 96G
MAXIMUM MOUNTS/HR : 99
MAXIMUM MOUNTS/DAY : 102
EFFECTIVE COMPRESSION RATIO : 0.5 to 1
AVERAGE MOUNT RESPONSE (SECS.) : 0.229
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (989) completed successfully!
NODENAME = vte1
--------------------------------------------------------------------------------
MAX TAPES IN USE PER HR :
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
|YY/MM/DD| 00| 01| 02| 03| 04| 05| 06| 07| 08| 09| 10| 11|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
| | 12| 13| 14| 15| 16| 17| 18| 19| 20| 21| 22| 23|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
|17/05/22| ***| ***| ***| ***| ***| 2| 1| ***| ***| ***| ***| ***|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
| | ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
84 Using Command Processors
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
|17/05/31| ***| ***| ***| ***| ***| ***| ***| ***| ***| 1| 1| 1|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
| | 1| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***| ***|
+--------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----
+-----+
TOP 10
SLOWEST
MOUNTS report
SLOWMOUNTS=10 report vNODENAME = vte1
--------------------------------------------------------------
TOP 10 SLOWEST MOUNTS (SECS.):
NODENAME DURATION VOLSER DATE TIME PATH vte1 0.289 NLFW24 2017/05/31 12:15:26 vte1 0.267 700000 2017/05/31 09:56:15 vte1 0.210 700000 2017/05/31 09:41:57 vte1 0.208 700000 2017/05/31 11:56:26 vte1 0.200 700000 2017/05/31 10:58:21 vte1 0.193 700000 2017/05/31 09:26:15 vte1 0.170 700000 2017/05/31 10:16:39 vte1 0.157 700000 2017/05/31 09:28:57 vte1 0.156 700000 2017/05/31 11:07:30 vte1 0.148 700000 2017/05/31 10:55:41
--------------------------------------------------------------
STILLINUSE report
NODENAME = vte1
-----------------------------------------------------------------
VOLSERS IN USE AT SYNCTIME (06/06/2017 10:00:00)
NODENAME DEVICE VOLSER LAST MOUNTED vte1 F200 200915 2016/02/01 06:53:34
-----------------------------------------------------------------
VOLSERS MOUNTED AFTER SYNCTIME (06/06/2017 10:00:00)
DATE TIME VOLSER NODENAME PATH
2017/06/19 10:17:56 BFL999 vte1
2017/06/27 06:06:12 YK5006 vte1
2017/06/27 06:09:54 YK5007 vte1
2017/06/27 06:12:36 YK5008 vte1
2017/06/27 06:12:37 BFLYK vte1
2017/06/27 06:13:39 YK5009 vte1
2017/06/27 06:14:45 YK5004 vte1
2017/06/28 16:02:38 YK5005 vte1
-----------------------------------------------------------------
DETAIL report
NODENAME = vte1
--------------------------------------------------------------------------------
DETAIL REPORT:
------ Unload ----- ------ Channel ------ ---- File System ---- Duration
Compression
Volser Date Time 4K Writes 4K Reads 4K Writes 4K Reads Time
Percent
------ ---------- -------- ---------- -------- ---------- ---------- ----------
-----------
700000 2017/05/31 09:27:52 48829 48829 50249 0 97
700000 2017/05/31 09:30:34 48829 48829 50249 0 97
700000 2017/05/31 09:36:40 48829 48829 50249 0 95
700000 2017/05/31 09:42:52 48829 1 50249 0 55
700000 2017/05/31 09:43:49 48829 1 50249 0 56
700000 2017/05/31 09:44:44 48829 1 50249 0 55
700000 2017/05/31 09:45:39 48829 1 50249 0 54
Using Command Processors 85
700000 2017/05/31 09:46:40 48829 1 50249 0 61
700000 2017/05/31 09:57:44 48829 48829 50249 0 89
700000 2017/05/31 10:18:15 48829 48829 50249 0 96
700000 2017/05/31 10:24:57 49 49 51 0 0
700000 2017/05/31 10:24:58 49 49 51 0 1
700000 2017/05/31 10:24:59 49 49 51 0 1
700000 2017/05/31 10:24:59 49 49 51 0 0
700000 2017/05/31 10:25:00 49 49 51 0 0
700000 2017/05/31 10:57:17 48829 48829 50249 0 96
700000 2017/05/31 10:57:46 25283 1 26019 0 28
700000 2017/05/31 10:58:01 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:02 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:02 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:03 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:04 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:21 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:22 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:22 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:23 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:23 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:30 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:31 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 1 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:54 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:55 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:56 1 1 1 0 1 0.00%
700000 2017/05/31 11:10:56 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:57 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:27 1 1 1 0 1 0.00%
700000 2017/05/31 11:56:27 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:28 1 1 1 0 1 0.00%
700000 2017/05/31 11:56:28 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:29 1 1 1 0 0 0.00%
NLFW24 2017/05/31 12:23:20 1075822 0 42838 0 474 96.00%
NLFW24 2017/05/31 12:38:29 0 1075823 42838 0 909
--------------------------------------------------------------------------------
Obtaining tape activity: CP998 and CP999 (DLm 4.x
only)
CP998
Command Processor CP998 retrieves statistics from a VOLSER range and writes this data to a non-labeled tape file.
The GENSTATS program is then run to generate a report from the non-labeled tape file data.
information about the GENSTATS utility and reports.
Submit CP998 from the mainframe by using either of the GENSTATP, GENSTAT1, or GENSTATW/R PROCs.
CP998 syntax
The CP998 command syntax using the GENSTATP PROC is:
//GO EXEC GENSTATP,CMD=998,UNIT=Unit1id,UNIT2=Unit2id
86 Using Command Processors
CP998 parameters
This section provides an overview of CP998 parameters.
Table 27. CP998 parameters
Parameter
Unit
Unit2
VPATH
VMASK
VDEPTH
Startdate
Enddate
Description
Unit to transport results
Unit to transport command
Allows filtering paths containing .vstats files. Example:
VPATH='/tapelibREP/5*' limits .vstats data to that found in the folders beginning with '/tapelibREP/5'
Wildcard mask to filter .vstats files.
Numeric count of maximum number of subfolders to filter .vstats files.
STRTMM/STRTDD/STRTYYYY
● STRTMM is the 2-digit month (default 01).
● STRTDD is the 2-digit day (default 01).
● STRTYYYY is the 4-digit year (default 2000).
This optional parameter excludes statistics of data preceding the date that is specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
ENDMM/ENDDD/ENDYYYY
● ENDMM is the 2-digit month (default 01).
● ENDDD is the 2-digit day (default 01).
● ENDYYYY is the 4-digit year (default 2099).
This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
Example 1:
SLOW MOUNTS command
Sample JCL:
//GO1 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR),
X
// REPORT='SLOWMOUNTS=5'
Sample output
GENSTATS VER 1.28 Z1CWRK PARMS: SLOWMOUNTS=5
--------------------------------------------------------------------------------
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
TOP 50 SLOWEST MOUNTS (SECS.):
NODENAME TIME VOLSER DATE TIME PATH vte1dlm0 0000.026 BG0332 2015/08/31 11:02:15 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 0000.028 BG0337 2015/09/01 11:14:09 tapelibFLR/CEL1_FLRP_FS2 vte1dlm0 0000.029 BG0323 2015/08/28 16:59:43 tapelibFLR/CEL1_FLRP_FS2 vte1dlm0 0000.033 BG0325 2015/08/28 17:08:15 tapelibFLR/CEL1_FLRP_FS2
Using Command Processors 87
vte1dlm0 0000.041 BFLGR1 2015/08/26 16:19:44 tapelibFLR/CEL1_FLRP_FS2
EMC Data Domain St
Example 2:
THROUGHPUT command
Sample JCL:
//GO2 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='THROUGHPUT'
Sample output
GENSTATS VER 1.28 Z1CWRK PARMS: THROUGHPUT
----------------------------------------------------------------------------------------------------------
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
----------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------
THROUGHPUT IN GB/HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT 08|OUT 09|OUT 10|OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT 20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN 08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN 20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
|15/08/26|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G MAXI/HR=00000G
MOUNTS/DY=000011 MAXMNT/HR=000011
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
|15/09/02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.62|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G MAXI/HR=00000G
MOUNTS/DY=000079 MAXMNT/HR=000054
Example 3:
DETAIL command
Sample JCL:
//GO4 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='DETAIL'
88 Using Command Processors
Sample output
GENSTATS VER 1.28 Z1CWKB PARMS: DETAIL
------ Unload ----- ------ Channel ------ ---- File System ---- Duration Compression
Volser Date Time 4K Writes 4K Reads 4K Writes 4K Reads Time Percent
------ ---------- -------- ---------- ---------- ---------- ---------- ---------- ----------
BG0300 2015/08/26 16:11:06 0000005121 0000000001 0000000303 0000000000 1068058565 94.1%
BFLGR1 2015/08/26 16:19:44 0000000001 0000000000 0000000001 0000000000 1068058576 00.0%
BFLGR1 2015/08/26 16:19:56 0000000000 0000000000 0000000001 0000000000 1068058576
BG0301 2015/08/26 16:19:56 0000000001 0000000001 0000000001 0000000000 1068058564 00.0%
BG0348 2015/09/02 11:52:15 0000005121 0000000001 0000000303 0000000000 1067614753 94.1%
BG0349 2015/09/02 11:53:00 0000010241 0000000001 0000000605 0000000000 1067614708 94.1%
BG0353 2015/09/02 11:53:01 0000005121 0000000001 0000000303 0000000000 1067614755 94.1%
BG0350 2015/09/02 11:53:36 0000015361 0000000001 0000000907 0000000000 1067614672 94.1%
BG0351 2015/09/02 11:54:14 0000020481 0000000001 0000001208 0000000000 1067614634 94.2%
BG0354 2015/09/02 11:54:15 0000010241 0000000001 0000000605 0000000000 1067614726 94.1%
BG0352 2015/09/02 11:54:41 0000025601 0000000001 0000001510 0000000000 1067614607 94.2%
BG0355 2015/09/02 11:55:10 0000015361 0000000001 0000000907 0000000000 1067614707 94.1%
BG0356 2015/09/02 11:55:46 0000020481 0000000001 0000001208 0000000000 1067614709 94.2%
BG0357 2015/09/02 11:56:05 0000025601 0000000001 0000001510 0000000000 1067614716 94.2%
---------------------------------------------------------------------------------------------
PATHS INCLUDED IN STATS :
NODENAME PATH vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
---------------------------------------------------------------------------------------------
Filtering .vstats files
This section provides an overview of filtering .vstats files.
The VPATH, VMASK, and VDEPTH parameters can be used to filter the .vstats files that Command Processor 998 processes.
These parameters are optional and either one or all the parameters can be used. Here is a description of how these parameters can be used for this purpose:
● VPATH : Assume that we have the following .vstats files and would like to limit the .vstats files to be processed to only the .vstats files belonging in the /tapelibREP/5* folders:
○ /tapelibREP/65/.vstats
○ /tapelibREP/53/.vstats
○ /tapelibREP/69/.vstats
○ /tapelibREP/62/.vstats
○ /tapelibREP/64/.vstats
○ /tapelibREP/51/.vstats
Specifying VPATH=/tapelibREP/5* would limit the number of .vstats files to the following list:
● /tapelibREP/53/.vstats
● /tapelibREP/51/.vstats
● VMASK : Assume that we have the following .vstats files and would like to limit the .vstats files to be processed to only the .vstats files for vte1:
/tapelibBG141106/CEL1_BG141106_FS4/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F4
/tapelibBG141106/CEL1_BG141106_FS1/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F1
/tapelibBG141106/CEL1_BG141106_FS3/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F3
/tapelibBG141016/CEL1_BG141016_FS1/.vstats.vte1.tapelibBG141016.CEL1_BG141016_F1
/tapelibBG141016/CEL1_BG141016_FS1/.vstats.vte2.tapelibBG141016.CEL1_BG141016_F1
Specifying VMASK=vte1.* would limit the .vstats files to the following list:
/tapelibBG141106/CEL1_BG141106_FS4/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F4
/tapelibBG141106/CEL1_BG141106_FS1/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F1
/tapelibBG141106/CEL1_BG141106_FS3/.vstats.vte1.tapelibBG141106.CEL1_BG141106_F3
/tapelibBG141016/CEL1_BG141016_FS1/.vstats.vte1.tapelibBG141016.CEL1_BG141016_F1
Using Command Processors 89
● VDEPTH : The VDEPTH parameter defines the numeric count of the maximum number of subfolders to filter .vstats files. The parameter allows .vstats files to be filtered by limiting the depth of subfolders. Assume that we have the following .vstats
files:
/tapelibDDR/DD1_DD_FS1/.snapshot/ scheduled-2014-07-11-07-00/.vstats.vte1.tapelibDDR.DD1_FS1
/tapelibDDR/DD1_DD_FS1/.snapshot/ scheduled-2014-07-11-07-00/.vstats.vte2.tapelibDDR.DD1_FS1
/tapelibDDR/DD1_DD_FS1/.snapshot/ scheduled-2014-07-11-13-00/.vstats.vte1.tapelibDDR.DD1_FS1
/tapelibDDR/DD1_DD_FS1/.vstats.vte1.tapelibDDR.DD1_FS1
/tapelibDDR/DD1_DD_FS1/.vstats.vte2.tapelibDDR.DD1_FS1
Specifying VDEPTH=4 limits the .vstats files to the following list:
/tapelibDDR/DD1_DD_FS1/.vstats.vte1.tapelibDDR.DD1_FS1
/tapelibDDR/DD1_DD_FS1/.vstats.vte2.tapelibDDR.DD1_FS1
Considerations for DLm2100 with Data Domain and PowerProtect
This section provides an overview of considerations for DLm2100 with data domain and PowerProtect.
Prerequisites
For DLm2100 with Data Domain and PowerProtect, ensure the .vstats
file exists in every /tapelib filesystem.
About this task
If the .vstats
file does not exist in every tapelib file system:
Steps
1. Logon to a Linux terminal session on a VTE on the DLm using a tool such as PuTTY.
NOTE: Log in as root.
2. Create a .vstats file in each directory in the library. Enter the following command to create a .vstats file in a single directory: touch /<libraryname>/<mountpoint>/.vstats
. Where:
● <libraryname> is the top-level qualifier identifying the virtual library; for example, /tapelib.
● <mountpoint> is the mount point that is used to mount the directory where the .vstats file is to be created. For example: touch /tapelib/DISK1/.vstats
NOTE: Repeat this procedure to create a .vstats file in each of the directories you want your Virtuent controller to log statistics. Normally, if your library has four directories, you would execute four touch commands so that all directories would be logging statistics.
Create .vstats from one DLm accessing the library. If you have more than one DLm controller sharing the virtual library do not create a .vstats from each controller. Create the control files from a single controller. All controllers recognize the presence of the .vstats file(s) and perform the required logging. If there are two DLm2100 units sharing the same Data
Domain and PowerProtect system, the DLms must have unique controller names. If the controller names are not unique, set them using the DLm Console.
3. Access the DLm Console: a. Open a web browser.
b. Type the Management VTE IP address: https://<ip_address>. Where <ip_address> is the address of the VTE on the customer LAN. For example: https://192.168.1.1.
4. Enter the user ID and password. The default user id is dlmadmin and the default password is password.
5. Click the Network menu tab.
6. Change the name of the host in the Host name field under Global Options .
7. To save the configuration and install it, click the Configurations menu tab.
8. Click the Save changes button.
90 Using Command Processors
9. Click the Install button which becomes active when you save the configuration.
NOTE: Use the Check if restart required option to check if the configuration change requires a restart of the
Virtuent virtual tape application. If Virtuent must be restarted when the configuration is installed, you must vary all DLm devices offline before installing it.
CP999
This section provides an overview of CP999.
This Command Processor retrieves statistics files from a local VTE and writes this data to a non-labeled tape file. The
GENSTATS program is then run to generate a report from the non-labeled tape file data.
provides information about the GENSTATS utility and reports.
Submit CP999 from the mainframe by using either of the GENSTATP, GENSTAT1, or GENSTATW PROCs.
CP999 syntax
The CP999 command syntax is:
//GO EXEC GENSTATP,CMD=999,UNIT=Unit1id,UNIT2=Unit2id
CP999 parameters
This section provides an overview of CP999 parameters.
Table 28. CP999 parameters
Parameter
Unit
Unit2
Startdate
Enddate
Description
Unit to transport results
Unit to transport command
STRTMM/STRTDD/STRTYYYY
● STRTMM is the 2-digit month (default 01).
● STRTDD is the 2-digit day (default 01).
● STRTYYYY is the 4-digit year (default 2000).
This optional parameter excludes statistics data preceding the date that is specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
ENDMM/ENDDD/ENDYYYY
● ENDMM is the 2-digit month (default 01).
● ENDDD is the 2-digit day (default 01).
● ENDYYYY is the 4-digit year (default 2099).
This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
Example 1:
SLOW MOUNTS
Sample JCL:
//GO5 EXEC GENSTAT1,CMD=999,UNIT=(/F207,,,SMSHONOR), X
// REPORT='SLOWMOUNTS=5'
Using Command Processors 91
Sample output
GENSTATS VER 1.28 Z1CWK4 PARMS: SLOWMOUNTS=5
NODENAME = vte1
----------------------------------------------------
TOP 50 SLOWEST MOUNTS (SECS.):
NODENAME TIME VOLSER DATE TIME vte1 0000.063 DV0011 2015/07/28 11:19:16 vte1 0000.064 BFL503 2015/06/23 18:07:12 vte1 0000.065 BFL502 2015/08/04 15:54:00 vte1 0000.080 BFL501 2015/06/23 18:09:47 vte1 0000.085 BFLMT7 2015/08/25 15:17:19
-----------------------------------------------------
Example 2:
THROUGHPUT
Sample JCL
//GO6 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='THROUGHPUT'
Sample output
GENSTATS VER 1.28 Z1CWKA PARMS: THROUGHPUT
NODENAME = vte1
-----------------------------------------------------------------------------------------
----------------
THROUGHPUT IN GB/HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT 08|OUT 09|OUT 10|
OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT 20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN 08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN 20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|15/06/23|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.02|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
|15/09/02|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|0000.62|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
92 Using Command Processors
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
| |0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|0000.00|
0000.00|0000.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+
MAXI+O/HR=00000G TOT/DAY=00000G OUT/DY=00000G IN/DY=00000G MAXO/HR=00000G MAXI/HR=00000G
MOUNTS/DY=000091 MAXMNT/HR=000054
COUNT OF UNLOAD RECORDS :0000966
COUNT OF UNLOADS W/OUTPUT STATS:0000515
COUNT OF UNLOADS W/INPUT STATS :0000005
MAXIMUM OUTPUT/HR :000000.62G
MAXIMUM OUTPUT/DAY :000000.62G
MAXIMUM INPUT/HR :000000.02G
MAXIMUM INPUT/DAY :000000.02G
MAXIMUM THROUGHPUT/HR :000000.62G
MAXIMUM THROUGHPUT/DAY :000000.62G
MAXIMUM MOUNTS/HR :000096
MAXIMUM MOUNTS/DAY :000213
EFFECTIVE COMPRESSION RATIO :16.1 TO 1
AVERAGE MOUNT RESPONSE (SECS.) :000.003
--------------------------------------------------------------------
Example 3:
Sample JCL
//GO8 EXEC GENSTAT1,CMD=998,UNIT=(/F207,,,SMSHONOR), X
// REPORT='DETAIL'
Sample output
GENSTATS VER 1.28 Z1CWRK PARMS: DETAIL
------ Unload ----- ------ Channel ------ ---- File System ---- Duration Compression
Volser Date Time 4K Writes 4 K Reads 4K Writes 4K Reads Time Percent
------ ---------- -------- ---------- ---------- ---------- ---------- ----------
----------
BFL503 2015/06/23 18:07:12 0000000001 0000000000 0000000001 0000000000 1071310800 00.0%
DV0001 2015/06/23 18:07:16 0000000001 0000000001 0000000001 0000000000 1071310796 00.0%
BFL503 2015/06/23 18:08:22 0000000001 0000000000 0000000001 0000000000 1071310800 00.0%
DV0002 2015/06/23 18:08:27 0000000001 0000000001 0000000001 0000000000 1071310795 00.0%
BFL501 2015/06/23 18:09:48 0000000001 0000000000 0000000001 0000000000 1071310799 00.0%
DV0005 2015/06/23 18:09:59 0000000001 0000000001 0000000001 0000000000 1071310789 00.0%
BFL501 2015/06/23 18:10:00 0000000000 0000000000 0000000005 0000000000 1071310799
DV0004 2015/06/23 18:11:33 0000005121 0000005121 0000000300 0000000000 1071310798 94.2%
BFL499 2015/07/28 11:08:38 0000000001 0000000000 0000000001 0000000000 1069485135 00.0%
BFL499 2015/07/28 11:08:51 0000000000 0000000000 0000000001 0000000000 1069485136
DV0003 2015/07/28 11:08:51 0000000001 0000000001 0000000001 0000000000 1069485123 00.0%
BFL499 2015/07/28 11:08:52 0000000000 0000000000 0000000001 0000000000 1069485136
BFL499 2015/07/28 11:09:53 0000000001 0000000000 0000000001 0000000000 1069485135 00.0%
DV0008 2015/07/28 11:10:05 0000000001 0000000001 0000000001 0000000000 1069485124 00.0%
BFL499 2015/07/28 11:10:06 0000000001 0000000000 0000000001 0000000000 1069485136 00.0%
BFL499 2015/07/28 11:10:19 0000000000 0000000000 0000000001 0000000000 1069485136
DV0007 2015/07/28 11:10:19 0000000001 0000000001 0000000001 0000000000 1069485124 00.0%
….
BG0348 2015/09/02 11:52:15 0000005121 0000000001 0000000303 0000000000 1067614753 94.1%
BG0349 2015/09/02 11:53:00 0000010241 0000000001 0000000605 0000000000 1067614708 94.1%
BG0353 2015/09/02 11:53:01 0000005121 0000000001 0000000303 0000000000 1067614755 94.1%
BG0350 2015/09/02 11:53:36 0000015361 0000000001 0000000907 0000000000 1067614672 94.1%
BG0351 2015/09/02 11:54:14 0000020481 0000000001 0000001208 0000000000 1067614634 94.2%
BG0354 2015/09/02 11:54:15 0000010241 0000000001 0000000605 0000000000 1067614726 94.1%
BG0352 2015/09/02 11:54:41 0000025601 0000000001 0000001510 0000000000 1067614607 94.2%
BG0355 2015/09/02 11:55:10 0000015361 0000000001 0000000907 0000000000 1067614707 94.1%
BG0356 2015/09/02 11:55:46 0000020481 0000000001 0000001208 0000000000 1067614709 94.2%
BG0357 2015/09/02 11:56:05 0000025601 0000000001 0000001510 0000000000 1067614716 94.2%
BFL503 2015/09/02 11:58:32 0000000001 0000000000 0000000001 0000000000 1067614800 00.0%
BFL503 2015/09/02 11:58:44 0000000000 0000000000 0000000015 0000000000 1067614800
Using Command Processors 93
5
Using Command Processors with new
DLMCPPRC procedure
This chapter introduces the new procedure DLMCPPRC that is compatible only with DLm 5.5 version. DLMCPPRC provides functionality to run Command Processors with new DLMCP utility without using BFL volumes, solving all BFL-related limitations of old Command Processors' procedures.
NOTE: DLMCPPRC procedure is introduced in DLm Mainframe Utilities 2.7.0.0.
Topics:
•
•
DLMCPPRC procedure general parameters
•
Performing DLm Diagnostics: CP499
•
•
Obtaining DLm Log Information: CP502
•
Obtaining Virtual Tape Volume Information: CP503
•
Obtaining VNX Replication Information: CP504
•
Obtaining Data Domain and PowerProtect: CP601, CP602, CP603
•
Obtaining Replication Information by VOLSER: CP804
•
Obtaining tape activity: CP988 and CP989
DLMCPPRC procedure parameters
This section provides the list of DLMCPPRC procedure parameters and their description.
Table 29. Parameters in DLMCPPRC
Parameters Value Default value
CMD xxx -
Required/Optional Command
Processor
Required General
UNIT
PRINTTO
LINKLIB
REXXLIB xxx -
LOGFILE |
SYSLOG
USER.DLM.LINK
LIB
LOGFILE
-
USER.DLM.REX
XCMD
-
WAIT seconds_numbe r
PINGOPTS -l all | -i xxx.xxx.xxx.xxx |
-c
600
-l all
Required
Optional
Required
Required
Optional
Optional
General
General
General
General
General
CP499
Description
Number of the
Command Processor
Unit to send CP command to VTE and obtain the report back
Indicates where to print the report
Data set where
DLMCP load module resides
Data set where
DLMPARM and
DLMCPBLD REXX scripts reside
Wait time in seconds
Options to ping DLm components
94 Using Command Processors with new DLMCPPRC procedure
Table 29. Parameters in DLMCPPRC (continued)
Parameters Value Default value Required/Optional Command
Processor component_nam e
VCMD vte_command Required CP501
LOGTYPE L0 | L1 | L2 L1 Optional CP502
BTILOGN
AWSOPTS
TLIB
2 | 3 | 4 | 5 | 6 |
7 | 8 | 9 | 10 awsprint_option s
/tapelibXXX
2 all -a -r -l all
Optional
Optional
Optional
REPORT
CP502
CP503
● CP503
● CP602
● CP804
● CP988
● CP504
● CP602
● CP603
● CP804
● CP988
● CP989
DAYS
● SUMMARY |
QUICK |
VERBOSE
● SUMMARY |
DETAILED |
FULL
● ALL |
STATUS |
PERF |
STATS |
HIST
● SUMMARY |
DETAILED |
FULL
● THROUGHP
UT |
MAXTAPES |
STILLINUSE
| DETAIL |
SLOWMOUN
TS=nn days_number
● -
● default
● -
● SUMMARY
● THROUGHPUT
● THROUGHPUT
-
● Required
● Optional
● Required
● Optional
● Optional
● Optional
Optional CP602
SIZEUNIT Bytes | KBs |
MBs | GBs | TBs
Bytes
PREFIX 1-6 uppercase alphanumeric characters
NODENAME vteN
-
ALL
NPROCS processes_num ber
16
Description
VTE console command to run
Type of VTE log to collect
Number of btilogs to collect
Awsprint options
Tape library path on
VTE
Report type
Optional
Optional
Optional
Optional
CP602
CP804
CP988
CP988
Report will be collected for files that were modified in the last <days_number> days.
Unit type in which the volume size must be reported.
Only volumes start with prefix will be processed.
The name of the VTE on which the report should be collected
The number of processes that will run statfmt in parallel
Using Command Processors with new DLMCPPRC procedure 95
Table 29. Parameters in DLMCPPRC (continued)
Parameters Value Default value
STRTDATE MM/DD/YYYY -
Required/Optional Command
Processor
Optional CP988, CP989
ENDDATE MM/DD/YYYY -
SYNCTIME HH/MM/SS -
Optional
Optional
CP988, CP989
CP988, CP989
Description
Only statistic data after the date specified will be processed
Only statistic data before the date specified will be processed
Only tapes mounted after the time specified will be processed (applicable only for STILLINUSE report type).
DLMCPPRC procedure general parameters
This section describes DLMCPPRC procedure parameters which are common for all Command Processors. Parameters which are not described in this section are specific for each Command Processor.
CMD parameter
This parameter specifies Command Processor to be run. This parameter is required.
UNIT parameter
This parameter specifies the DLm device to be used as a control path to send Command Processor's command to the VTE and obtain a report back to the host. Must be offline. To obtain Command
Processor's report from a VTE, choose the device pointing to this VTE. This parameter is required.
NOTE:
● Reserve one device for each VTE for DLMCPPRC and keep it offline.
● Esoteric and generic devices are not supported in DLMCPPRC.
MIH Considerations
By default, all DLm device’s MIH timeout values should be set to 50 minutes as it is described in the
DLm User Guide. This specific timeout is only considered after the first VARY OFFLINE after each IPL or VTE restart. Before the first VARY OFFLINE default value of 3 minutes for a device class is used for each device of this class. Potentially it might lead to I/O errors during Command Processors’ runs after
IPL or VTE restart and before the first VARY ONLINE of the device used as the UNIT parameter value in the DLMCPPRC procedure. To avoid such situations, it is strongly recommended to set the MIH timeout value for the TAPE device class to 50 minutes as well.
To set the MIH I/O timeout value of 50 minutes for the TAPE device class use the following MVS command:
SETIOS MIH,TAPE=50:00
To display MIH timeout value use the following MVS command:
D IOS,MIH
For more details about MIH timeouts, refer to the z/OS MVS Initialization and Tuning Reference and z/OS MVS System Commands .
NOTE: It is recommended to vary the device online and back offline before using it in the
DLMCPPRC procedure the first time after each IPL or VTE restart to avoid potential I/O errors caused by MIH timeouts described in the "MIH Considerations" section.
PRINTTO parameter
96 Using Command Processors with new DLMCPPRC procedure
This parameter specifies whether to print Command Processor’s report to the SYSLOG or to the
LOGFILE. This parameter is optional, the default value is LOGFILE which is pointing to the JOBLOG.
Printing report to the custom dataset
To print the report to the specific custom dataset instead of printing it to the JOBLOG specify this dataset in the DLMCPRPT DD statement of the DLMCP step of the DLMCPPRC procedure. For example:
//PRNTODS EXEC DLMCPPRC,CMD=804,UNIT=/8700,
// LINKLIB=USER.DLM.LINKLIB,
// REXXLIB=USER.DLM.REXXCMD
//DLMCP.DLMCPRPT DD DSN=USER.DLM.RPRT804,
// UNIT=SYSALLDA,
// DISP=(NEW,CATLG),
// LRECL=264,
// RECFM=FB,
// SPACE=(CYL,(2,1))
LINKLIB parameter
This parameter specifies the dataset where the DLMCP utility load module resides. This parameter is required.
REXXLIB parameter
This parameter specifies the dataset where DLMPARM and DLMCPBLD REXX scripts reside. This parameter is required.
WAIT parameter
This parameter specifies the timeout period in seconds for Command Processor to be executed on VTE.
This parameter is optional, the default value is 600 seconds.
Performing DLm Diagnostics: CP499
This section provides an overview of performing DLm diagnostics of CP499.
This job pings DLm components that are attached to this VTE. Use it as a batch component testing function.
NOTE: The parameters are case-sensitive.
CP499 syntax
The CP499 command syntax is:
//CP499 EXEC DLMCPPRC,CMD=499,UNIT=unitid,
// PINGOPTS='CP499 Parameters'
Table 30. CP499 parameters
Parameter
PINGOPTS
Description
Valid options are:
● -l all : Interrogates the /etc/host and lists its contents
● -i xxx.xxx.xxx.xxx
: Pings a specific address
● -c ComponentName : Pings a component by name
NOTE: The default option is -l all for list all.
NOTE: CP499 processing is directed to a single DLm VTE.
Using Command Processors with new DLMCPPRC procedure 97
Example 1:
The following example interrogates the /etc/host and lists its contents.
Sample JCL:
//CP499 EXEC DLMCPPRC,CMD=499,UNIT=/8700,
// PINGOPTS='-l all'
Sample output
STATUS: SUCCESS
EMC CP499 ADHOC TESTING Tool (499) v5.5.0-142
Thu Apr 28 12:29:49 +03 2022
================================================================================
499 Adhoc Verification tool
*Component List Report* ( options flags -l all)
This Report Lists the DLm components that can be reached from the VTE that
this CP499 utility is running on (Components that CP499 can validate)
--------------------------------------------------------------------------------
Component IP Address
--------- --------------
10.246.169.6 nas1s-alias0
10.246.169.7 nas1s-alias1
127.0.0.1 localhost
::1 localhost
acp 127.0.0.1
acp1 127.0.0.1
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
ipv6-allhosts ff02::3
ipv6-allnodes ff02::1
ipv6-allrouters ff02::2
ipv6-localhost ::1
ipv6-localnet fe00::0
ipv6-loopback ::1
ipv6-mcastprefix ff00::0
localhost ::1
nas1s 10.246.169.6
nas1s-alias0 10.246.169.6
nas1s-alias1 10.246.169.7
vte1 127.0.0.1
vtea 127.0.0.1
--------------------------------------------------------------------------------
================================================================================
INFO : EMC CP499 ADHOC TESTING Tool (499) completed successfully!
Running VTE Commands: CP501
Using CP501, you can pass a DLm Virtual Tape Operator console command to a VTE, and use the output on the mainframe as appropriate.
The Virtual Tape Operator commands enable you to control or query virtual tape drives.
CP501 supports the following VT operator commands:
NOTE: The Dell Technologies Disk Library for mainframe User Guide provides information about the Virtual Tape Operator commands.
98 Using Command Processors with new DLMCPPRC procedure
NOTE: The DLMHOST utility provides an enhanced version of the CP501 functionality. The
provides information about DLMHOST .
CP501 syntax
This section provides an overview of CP501 syntax.
The CP501 command syntax is:
//CP501 EXEC DLMCPPRC,CMD=501,UNIT=unitid,
// VCMD='VTECommand'
CP501 parameters
This section provides an overview of CP501 parameters.
Table 31. CP501 parameters
Parameter
VCMD
Description
This parameter is required for Command Processor 501.
It specifies the Virtual Tape Operator command. See the
“Virtual Tape Operator command reference” section in the
Disk Library for mainframe User Guide for a description of available commands.
Example
This section provides an overview of sample JCL and sample output.
Sample JCL
//CP501 EXEC DLMCPPRC,CMD=501,UNIT=/8700,
// VCMD='INIT VOL=VM0100 DEV=8701 COUNT=1 CLASS=0'
Sample output The sample report output that is shown below is generated by the above example Command Processor.
STATUS:
SUCCESS
EMC DLm VTEC Command Processor Tool (501) v5.5.0-142
Fri Apr 22 11:14:38 EDT
2022
================================================================================
04/22/2022 11:14:38 vte1 VT: DLm0869I: 1 Standard-label volume initialized in / tapelibTEST/CEL1_POOL1_FS4
================================================================================
INFO : EMC DLm VTEC Command Processor Tool (501) completed successfully!
Using Command Processors with new DLMCPPRC procedure 99
Security concerns
The VTE Command Processing feature of CP501 allows any DLm command to be passed, hence establish appropriate security measures, for example RACF, to restrict its use to authorized personnel.
Obtaining DLm Log Information: CP502
CP502 enables the transfer of the contents of the following to a mainframe tape file:
● btilog files
● /var/log/messages
● Output of command cfg-util show .
● Output of command ipmitool sel list
btilog files
Each VTE maintains log files of operations that are performed by the virtual tape emulation application. These log files are known as btilogs.
These files are a primary source of information for operation sequencing, completion, and problem determination. The btilogs are text files that contain the detailed activity of all VTEs and are located in the /var/log/bti directory. The most recent btilog file is btilog.
The number of btilogs to be transferred is specified by the user. The default value is 2 (the current log file and its immediate predecessor) and the maximum value is 10.
/var/log/messages
This is the standard operating system log file, which contains messages from the system software, kernel messages, non-kernel boot issues, and general system messages. As this file can be large, CP502 copies only the last 1,000 lines to the mainframe file.
cfg-util show
Provides DLm configuration file.
ipmitool sel list
When this operating system level command is performed, the VTE baseboard controller System Event Log (SEL) is transferred to the mainframe.
CP502 syntax
This section provides an overview of CP502 syntax.
The CP502 command syntax is:
//CP502 EXEC DLMCPPRC,CMD=502,UNIT=unitid,
// LOGTYPE='type_of_logs',BTILOGN='btilog_num'
100 Using Command Processors with new DLMCPPRC procedure
CP502 parameters
This section provides an overview of CP502 parameters.
Table 32. CP502 parameters
Parameter
LOGTYPE
BTILOGN
Description
This parameter specifies what type of logs need to be requested:
● L0 - btilog files requested (see Number of btilogs to collect)
● L1 - (Default) btilogs and /var/log/messages
● L2 - btilogs, /var/log/message, current.json, and output of commands cfg-util show and ipmitool sel list
The number of btilogs to collect: 2 to 10 files. The default value is 2.
Example 1:
This section provides an example of JCL sample.
Sample JCL:
//CP502 EXEC DLMCPPRC,CMD=502,UNIT=/8700,
// LOGTYPE='L1',BTILOGN='5'
Sample output The sample output that is shown below is generated by the above example Command Processor.
STATUS:
SUCCESS
EMC DLm VTEC Log Collection Tool (502) v5.5.0-142
Wed Apr 27 14:42:22 +03
2022
================================================================================
--------------------------------------------------------------------------------
#####Diagnostic-
Data#####
BTI Log name : /var/log/bti/old-logs/ btilog-20220426
04/25/2022 23:59:04 vte1 VT: DLm0409I: Command received: 'q all'
04/25/2022 23:59:04 vte1 VT: Copyright (c) 2017-2021 Dell Inc. or its subsidiaries. All rights reserved.
04/25/2022 23:59:04 vte1 VT: Virtuent version
8.5.0.0.54
04/25/2022 23:59:04 vte1 VT: Model Family: dlm2500
04/25/2022 23:59:04 vte1 VT: Program started at Fri Apr 22 17:28:40
2022
04/25/2022 23:59:04 vte1 VT: DLm1000I: DLm PSNT S/N:
DLMIP246165038
04/25/2022 23:59:04 vte1 VT: DLm1001I: VTE node number:
1
04/25/2022 23:59:04 vte1 VT: DLm0056I: Channel driver version is
Using Command Processors with new DLMCPPRC procedure 101
6.1.2
04/25/2022 23:59:04 vte1 VT: DLm0075I: Interface #1: 1 (0x000001) bus:101 slot:0 port:1 type:0 (QLogic 2-port 16Gb FC HBA/no op)
04/25/2022 23:59:04 vte1 VT: DLm0076I: Interface #1: hardware s/ n:
04/25/2022 23:59:04 vte1 VT: DLm0070I: Interface #1: TRANSX emulation version set to 16
04/25/2022 23:59:04 vte1 VT: DLm0081I: Interface #1: Current state: running;
Desired state: running; Media Up, Loop Up
04/25/2022 23:59:04 vte1 VT: DLm0075I: Interface #2: 2 (0x000002) bus:101 slot:0 port:2 type:0 (QLogic 2-port 16Gb FC HBA/no op)
04/25/2022 23:59:04 vte1 VT: DLm0076I: Interface #2: hardware s/ n:
04/25/2022 23:59:04 vte1 VT: DLm0070I: Interface #2: TRANSX emulation version set to 16
04/25/2022 23:59:04 vte1 VT: DLm0081I: Interface #2: Current state: running;
Desired state: running; Media Down, Loop Down
04/25/2022 23:59:04 vte1 VT: DLm0841I: System tracelevel is currently set to
0
04/25/2022 23:59:04 vte1 VT: DLm0842I: System debuglevel is currently set to
0
04/25/2022 23:59:04 vte1 VT: DLm0188I: SNMP is enabled, queue is operational with 0 pending requests
04/25/2022 23:59:04 vte1 VT: DLm0856I: Tape Library /tapelibDDVE has 2 scratch synonyms:
04/25/2022 23:59:04 vte1 VT: PRIVAT=(CLASS=CLASS0): 0 scratches
04/25/2022 23:59:04 vte1 VT: SCRTCH=(CLASS=CLASS0): 0 scratches
04/25/2022 23:59:04 vte1 VT: DLm3720I: Space erase policy configured
OFF
04/25/2022 23:59:04 vte1 VT: DLm0096I: Erase Policy: retain for up to 1 hour
(configured this way)
04/25/2022 23:59:04 vte1 VT: DLm0097I: Maximum continuous erase time set to 30 seconds
04/25/2022 23:59:04 vte1 VT: DLm0096I: Erase Policy: Space needed (capacity)
(configured this way)
04/25/2022 23:59:04 vte1 VT: DLm0703I: Max stalled FS time set for 2700 seconds
04/25/2022 23:59:04 vte1 VT: DLm0705I: Display interval for message DLm0702E set for 3600 seconds
04/25/2022 23:59:04 vte1 VT: DLm0147I: LEOT (Logical End Of Tape) value set to
10M
04/25/2022 23:59:04 vte1 VT: DLm0078I: Disk usage SPACEWARNING level set to
88%
04/25/2022 23:59:04 vte1 VT: DLm3720I: Space erase policy configured
OFF
04/25/2022 23:59:04 vte1 VT: DLm0127I: Disk space ERASEPOLICYTTL set to 1H
(config)
04/25/2022 23:59:04 vte1 VT: DLm0101I: Capacity usage CAPACITYWARNING level set to 88%
04/25/2022 23:59:04 vte1 VT: DLm0079I: Capacity usage CAPACITYRECOVER level set to 85%
04/25/2022 23:59:04 vte1 VT: DLm0084I: Capacity usage CAPACITYRECOVERAMT set to
5%
04/25/2022 23:59:04 vte1 VT: DLm0360I: Capacity usage CAPACITYRECOVERYUPDATE set to 24 hours
04/25/2022 23:59:04 vte1 VT: DLm0851I: ProtectVOL1 set
ON
04/25/2022 23:59:04 vte1 VT: DLm0099I: New mount on already-mounted drive will be allowed
04/25/2022 23:59:04 vte1 VT: DLm0069I: Resetting Events will not be sent to firmware
04/25/2022 23:59:04 vte1 VT: DLm0114I: Using RR method of filesystem allocation
04/25/2022 23:59:04 vte1 VT: DLm0109I: Scratch mounts will ignore full filesystems (UseFullFS=FALSE)
04/25/2022 23:59:04 vte1 VT: DLm0835I: RescratchIfRead option set to
OFF
04/25/2022 23:59:04 vte1 VT: DLm0010I: Compression hardware not available
...
102 Using Command Processors with new DLMCPPRC procedure
#####Diagnostic-
Data#####
BTI Log name : /var/log/bti/ btilog
04/26/2022 23:59:04 vte1 VT: DLm0409I: Command received: 'q all'
04/26/2022 23:59:04 vte1 VT: Copyright (c) 2017-2021 Dell Inc. or its subsidiaries. All rights reserved.
04/26/2022 23:59:04 vte1 VT: Virtuent version
8.5.0.0.54
04/26/2022 23:59:04 vte1 VT: Model Family: dlm2500
04/26/2022 23:59:04 vte1 VT: Program started at Fri Apr 22 17:28:40
2022
04/26/2022 23:59:04 vte1 VT: DLm1000I: DLm PSNT S/N:
DLMIP246165038
04/26/2022 23:59:04 vte1 VT: DLm1001I: VTE node number:
1
04/26/2022 23:59:04 vte1 VT: DLm0056I: Channel driver version is
6.1.2
04/26/2022 23:59:04 vte1 VT: DLm0075I: Interface #1: 1 (0x000001) bus:101 slot:0 port:1 type:0 (QLogic 2-port 16Gb FC HBA/no op)
04/26/2022 23:59:04 vte1 VT: DLm0076I: Interface #1: hardware s/ n:
04/26/2022 23:59:04 vte1 VT: DLm0070I: Interface #1: TRANSX emulation version set to 16
04/26/2022 23:59:04 vte1 VT: DLm0081I: Interface #1: Current state: running;
Desired state: running; Media Up, Loop Up
04/26/2022 23:59:04 vte1 VT: DLm0075I: Interface #2: 2 (0x000002) bus:101 slot:0 port:2 type:0 (QLogic 2-port 16Gb FC HBA/no op)
04/26/2022 23:59:04 vte1 VT: DLm0076I: Interface #2: hardware s/ n:
04/26/2022 23:59:04 vte1 VT: DLm0070I: Interface #2: TRANSX emulation version set to 16
04/26/2022 23:59:04 vte1 VT: DLm0081I: Interface #2: Current state: running;
Desired state: running; Media Down, Loop Down
04/26/2022 23:59:04 vte1 VT: DLm0841I: System tracelevel is currently set to
0
04/26/2022 23:59:04 vte1 VT: DLm0842I: System debuglevel is currently set to
0
04/26/2022 23:59:04 vte1 VT: DLm0188I: SNMP is enabled, queue is operational with 0 pending requests
04/26/2022 23:59:04 vte1 VT: DLm0856I: Tape Library /tapelibDDVE has 2 scratch synonyms:
04/26/2022 23:59:04 vte1 VT: PRIVAT=(CLASS=CLASS0): 0 scratches
04/26/2022 23:59:04 vte1 VT: SCRTCH=(CLASS=CLASS0): 0 scratches
04/26/2022 23:59:04 vte1 VT: DLm3720I: Space erase policy configured
OFF
04/26/2022 23:59:04 vte1 VT: DLm0096I: Erase Policy: retain for up to 1 hour
(configured this way)
04/26/2022 23:59:04 vte1 VT: DLm0097I: Maximum continuous erase time set to 30 seconds
04/26/2022 23:59:04 vte1 VT: DLm0096I: Erase Policy: Space needed (capacity)
(configured this way)
04/26/2022 23:59:04 vte1 VT: DLm0703I: Max stalled FS time set for 2700 seconds
04/26/2022 23:59:04 vte1 VT: DLm0705I: Display interval for message DLm0702E set for 3600 seconds
04/26/2022 23:59:04 vte1 VT: DLm0147I: LEOT (Logical End Of Tape) value set to
10M
04/26/2022 23:59:04 vte1 VT: DLm0078I: Disk usage SPACEWARNING level set to
88%
04/26/2022 23:59:04 vte1 VT: DLm3720I: Space erase policy configured
OFF
04/26/2022 23:59:04 vte1 VT: DLm0127I: Disk space ERASEPOLICYTTL set to 1H
(config)
Using Command Processors with new DLMCPPRC procedure 103
...
04/27/2022 14:42:22 vte1 VT: DLm0550I: Command received from Host: device D700: cmd = 'RUNWAIT (600) 502 "L0" "2"'
04/27/2022 14:42:22 vte1 VT: DLm0409I: Command received: 'RUNWAIT (600) 502
"L0" "2"'
04/27/2022 14:42:22 vte1 VT: DLm0554I: "RUNWAIT(600) 502" command has started
(RUN process #1)
================================================================================
INFO : EMC DLm VTEC Log Collection Tool (502) completed successfully!
Obtaining Virtual Tape Volume Information: CP503
This section describes how to obtain Virtual Tape Volume information reports
Using CP503 command
CP503 provides an output report of the DLm Virtual Tape Volume Inventory.
CP503 syntax
This section provides an overview of CP503 syntax.
The CP503 command syntax is:
//CP503 EXEC DLMCPPRC,CMD=503,UNIT=unitid,
// AWSOPTS='awsprint_options',TLIB='directory_path'
CP503 parameters
This section describes the CP503 parameters.
Table 33. awsprint parameters
Parameters
AWSOPTS
Option Description
-s Optional. parameters to select a specific volume or range of volumes. For example:
● -s BT0010 — Lists only volume BT0010
● -s BT00* — Lists all volumes from BT0000 to BT0099
NOTE: *If -s is omitted, all volumes in the tape library are listed.
-<sort criteria>
-d
Sort criteria. sort by:
● -N — The filename. This is the default sort order
● -V — The volume serial number
● -D — Last modification date
● -H — Tape Header1 (HDR1) dataset name for labeled volumes and data in the TAPE INFO field for unlabeled volumes
● -I — Filename with scratch and unscratched tapes interspersed
● -S — Size
Display tape content details.
104 Using Command Processors with new DLMCPPRC procedure
Table 33. awsprint parameters (continued)
Parameters Option
-a
-r
--less
TLIB directory_path | all
Description
Display all, scratch and non-scratch, volumes
Recurse the directories
Displays less information (by not opening the tape file). Tape label information, the VOL1 label, label type, and Data
Set Name (DSN), are not to be displayed. Using this option speeds up the processing because each DLm
Tape volume in the directories that are processed does not need to be opened, read and closed.
This parameter specifies the path to the virtual tape library on the DLm. When this parameter is not specified, the statistics are collected for all mounted on VTE tape libraries.
NOTE:
● The default value for the TLIB parameter is all .
● The default value for AWSOPTS parameter is -a -r -l .
Example 1:
//CP503 EXEC DLMCPPRC,CMD=503,UNIT=/8700,
// TLIB='/tapelibTEST',
// AWSOPTS='-r -a -H'
Sample output
STATUS:
SUCCESS
EMC DLm AWSPRINT Command Processor Tool (503) v5.5.0-142
Wed Apr 27 15:02:13 +03
2022
================================================================================
Copyright (c) 2017-2021 Dell Inc. or its subsidiaries. All rights reserved. awsprint Version 8.5.0.0.54, Compiled Mar 30 2022
15:54:56
Sorted by HDR1 04/27/2022 03:02:13
PM
Path: tapelibDDVE
Selection Criteria: All Tapes Without
Details
NO. NAME VOLSER DATE TIME LBL TAPE
INFO TAPE SIZE WORM EXP
1 DDVE_1 04/27/2022 15:05 D
Directory 21.0K
*************************************************************************
Copyright (c) 2017-2021 Dell Inc. or its subsidiaries. All rights reserved. awsprint Version 8.5.0.0.54, Compiled Mar 30 2022
Using Command Processors with new DLMCPPRC procedure 105
15:54:56
Sorted by HDR1 04/27/2022 03:02:13
PM
Path: tapelibDDVE/
DDVE_1
Selection Criteria: All Tapes Without
Details
NO. NAME VOLSER DATE TIME LBL TAPE
INFO TAPE SIZE WORM EXP
1 TEST 12/16/2020 13:34 EMPTY
FILE 0
2 test 03/10/2022 11:02 EMPTY
FILE 0
3 AS0028 AS0028 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV000 52.4K
4 AS0058 AS0058 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV001 52.4K
5 AS0037 AS0037 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV002 52.4K
6 AS0042 AS0042 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV003 52.4K
7 AS0047 AS0047 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV004 52.4K
8 AS0014 AS0014 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV005 52.4K
9 AS0025 AS0025 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV006 52.4K
10 AS0024 AS0024 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV007 52.4K
11 AS0057 AS0057 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV008 52.4K
12 AS0006 AS0006 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV009 52.4K
13 AS0031 AS0031 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV010 52.4K
14 AS0010 AS0010 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV011 52.4K
15 AS0029 AS0029 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV012 52.4K
16 AS0003 AS0003 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV013 52.4K
17 AS0048 AS0048 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV014 52.4K
18 AS0009 AS0009 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV015 52.4K
19 AS0030 AS0030 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV016 52.4K
20 AS0008 AS0008 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV017 52.4K
21 AS0044 AS0044 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV018 52.4K
22 AS0017 AS0017 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV019 52.4K
23 AS0040 AS0040 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV020 52.4K
24 AS0005 AS0005 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV021 52.4K
25 AS0007 AS0007 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV022 52.4K
26 AS0049 AS0049 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV023 52.4K
27 AS0038 AS0038 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV024 52.4K
28 AS0022 AS0022 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV025 52.4K
29 AS0011 AS0011 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV026 52.4K
30 AS0032 AS0032 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV027 52.4K
31 AS0063 AS0063 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV028 52.4K
106 Using Command Processors with new DLMCPPRC procedure
32 AS0050 AS0050 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV029 52.4K
33 AS0045 AS0045 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV030 52.4K
34 AS0061 AS0061 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV031 52.4K
35 AS0018 AS0018 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV032 52.4K
36 AS0041 AS0041 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV033 52.4K
37 AS0035 AS0035 04/05/2022 14:16 S
HDR1DLMZOS.G.UDV034 52.4K
*************************************************************************
================================================================================
INFO : EMC DLm AWSPRINT Command Processor Tool (503) completed successfully!
Using awsprint utility
This section provides an overview of using the awsprint utility.
Establish a CLI session on a DLm VTE to use awsprint. awsprint is a virtual tape library utility that the mainframe user can execute from the shell on the VTE to review the contents of the virtual tape library. awsprint enables you to produce lists of the tapes in the virtual tape library.
awsprint syntax
This section provides an overview of awsprint syntax.
The syntax to run the awsprint utility in a VTE Shell is: awsprint /tapelib -sBT00* -N -d
defines the awsprint command parameters. Also, example 1 shows the syntax and parameters available.
This report is returned by awsprint when awsprint is invoked without any parameters.
Example 1:
Executing awsprint with no options specified. This results in a report of the awsprint syntax and a description of its options.
Copyright (c) 2017-2021 Dell Inc. or its subsidiaries. All rights reserved.
awsprint Version 8.5.0.0.54, Compiled Mar 30 2022 15:54:56
Usage: awsprint directory [-s pattern] [-NDVHIS] [-dar] [--less]
directory Specifies the path where the AWS tapes are stored.
This is a required parameter. For backwards compatibility,
directory can be specified with a "-p" switch.
-s pattern Option to select files by filename, up to six characters;
or to select files by scratch filename, up to seven characters;
an optional ending '*' can be used as a wildcard.
Only non-scratch files are printed by default. To display scratch
tapes specify pattern starting with '~' or use -a option.
The default pattern value is "*" to select all
non-scratch files in the directory.
-N Sort output by fileName.
-D Sort output by Date,
-V Sort output by VOL1 Volser.
-H Sort output by HDR1 dataset name.
-I Sort output by fileName, interspersing scratch and non-scratch
files (which normally would collate into separate groups).
-S Sort output by file Size.
Only one sort option can be specified.
The default sort sequence is -N, by fileName.
Using Command Processors with new DLMCPPRC procedure 107
-r --recurse Specifies that all directories should be recursed.
-a --all Specifies that all (scratch and non-scratch) volumes with name
that matches selection pattern should be printed.
In case search pattern starts with '~' symbol -a option would be
ignored, only scratch tapes would be displayed.
-h --help Displays this help information.
-v --version Displays version number.
-d --details Specifies that tape details should be printed.
-l --less Specifies that tape label information (VOL1 label, label
type, DSN) are not to be displayed. Using this option will
greatly speed up the program as awsprint does not need
to open, read, and close every file in the directory.
Output is written to the console. You can use redirection (">") to
write the awsprint output to a file.
Usage example: awsprint /tapelib -sBT00* -H >tapelist.txt
Selects all tapes starting with BT00 in path /tapelib, sorted by the
HDR1 dataset name. The output is redirected to the file tapelist.txt.
Obtaining VNX Replication Information: CP504
CP504 collects the replication statistics of all VNX/base and expansion VNX file systems on which replication has been enabled.
CP504 syntax
The CP504 command syntax is:
//CP504 EXEC DLMCPPRC,CMD=504,UNIT=unitid,
// REPORT='report type'
CP504 parameters
This section provides an overview of CP504 parameters.
Table 34. CP504 parameter
Parameter
REPORT
Discipline
Report types:
● QUICK
● SUMMARY
● VERBOSE
Sample JCL
This section provides an overview of sample JCL.
CP504:
//CP504 EXEC DLMCPPRC,CMD=504,UNIT=/8700,
// REPORT='QUICK'
QUICK report
This section provides an overview of QUICK report.
The QUICK report displays the following replication statistics:
108 Using Command Processors with new DLMCPPRC procedure
● Destination VOLSER Range
● Time elapsed since last sync (Minutes)
● Avg Transfer Rate (MB/s)
Sample output
This section shows the sample of a QUICK report.
Sample QUICK report:
STATUS: WARNING
EMC Replication Stats Collection Tool (504) v5.5.0-142
Tue Apr 26 11:40:34 EDT 2022
Report Type : QUICK
================================================================================
Base Unit
--------------------------------------------------------------------------------
Destination Filesystem Time Since Avg Transfer
Range Last Sync (Mins) Rate (MB/s)
-------------------------------------------------------------------------------- tapelibTAPEPROC_CEL1_TAPEPROC_FS51 545869.00 0.00 tapelibREP3ST_CEL1_P1_FS 7.00 0.48 tapelibREPDLMD_CEL1_P1_FS1 5.00 0.55 tapelibVARTEN_CEL1_POOL_FS1 5.00 8.40 tapelibVARTEN2_CEL1_POOL_FS1 0.00 19.15 tapelibVGRDST_CEL1_GR_FS1 9.00 7.06
--------------------------------------------------------------------------------
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibREP3ST_CEL1_P1_FS)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibREPDLMD_CEL1_P1_FS1)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibVARTEN_CEL1_POOL_FS1)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibVARTEN2_CEL1_POOL_FS1)!
--------------------------------------------------------------------------------
================================================================================
WARNING : EMC Replication Stats Collection Tool (504) completed with warning!
SUMMARY report
This section provides an overview of SUMMARY report.
Table 35. Summary report details
Report fields
Report Execution Time
Replication session name
Source VOLSER
Destination VOLSER
Max out of Sync Time
Last Data Sync Time
Time elapsed since last sync (Minutes)
Source DLm Status
Destination DLm Status
Description
Time when the report was created
Name of the replication session
VOLSER range that is the source for this replication session
VOLSER range on a remote DLm that is the destination for this replication session
Maximum time between data synchronization of the destination VOLSER range with the source VOLSER range
Time when the last data synchronization was done between the source and destination VOLSER ranges
Time elapsed since the last data synchronization
Status of the source DLm
Status of the destination DLm
Using Command Processors with new DLMCPPRC procedure 109
Table 35. Summary report details (continued)
Report fields
DLm Network Status
Source Network Interface
Destination Network Interface
Avg Transfer Rate (MB/s)
Margin of error since last sync
Description
Network status between the source and destination DLm systems
Network interface that is part of this replication session at the source DLm
Network interface that is part of this replication session at the destination DLm
Average data transfer rate for this replication session
Accuracy of the elapsed since last sync value in seconds
Sample output
Sample SUMMARY report is shown below:
STATUS: WARNING
EMC Replication Stats Collection Tool (504) v5.5.0-142
Tue Apr 26 11:52:31 EDT 2022
Report Type : SUMMARY
================================================================================
Base Unit
--------------------------------------------------------------------------------
Replication Name : criticalGR
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 12 Apr 2021 09:56:19
Time Since Last Sync : 545881.00 (minutes)
Destination Filesystem : tapelibTAPEPROC_CEL1_TAPEPROC_FS51
Destination Network Interface : 127.0.0.1
Max out of Sync Time : Manual Refresh (minutes)
Avg Transfer Rate : 0.00 (MB/s)
================================================================================
Replication Name : REP3ST8
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 26 Apr 2022 11:47:59
Time Since Last Sync : 9.00 (minutes)
Destination Filesystem : tapelibREP3ST_CEL1_P1_FS
Destination Network Interface : 192.168.188.3
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 0.48 (MB/s)
================================================================================
Replication Name : VREPL1
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 26 Apr 2022 11:50:07
Time Since Last Sync : 7.00 (minutes)
Destination Filesystem : tapelibVARTEN_CEL1_POOL_FS1
Destination Network Interface : 192.168.182.3
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 8.40 (MB/s)
================================================================================
Replication Name : REPL3_tapelibREPDLMD_CEL1_P1_FS1_DC3_VNX1_DM2
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 26 Apr 2022 11:49:47
Time Since Last Sync : 7.00 (minutes)
110 Using Command Processors with new DLMCPPRC procedure
Destination Filesystem : tapelibREPDLMD_CEL1_P1_FS1
Destination Network Interface : 192.168.182.3
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 0.55 (MB/s)
================================================================================
Replication Name : VREPL2
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 26 Apr 2022 11:54:27
Time Since Last Sync : 3.00 (minutes)
Destination Filesystem : tapelibVARTEN2_CEL1_POOL_FS1
Destination Network Interface : 192.168.182.3
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 19.15 (MB/s)
================================================================================
Replication Name : LOOPBACK_REPL_1
Source DLm Status : OK
DLm Network Status : OK
Destination DLm Status : OK
Report Execution Time : Tue Apr 26 11:57:03 EDT 2022
Last Data Sync Time : 26 Apr 2022 11:55:46
Time Since Last Sync : 1.00 (minutes)
Destination Filesystem : tapelibVGRDST_CEL1_GR_FS1
Destination Network Interface : 127.0.0.1
Max out of Sync Time : 10 (minutes)
Avg Transfer Rate : 7.06 (MB/s)
================================================================================
--------------------------------------------------------------------------------
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibREP3ST_CEL1_P1_FS)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibVARTEN_CEL1_POOL_FS1)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibREPDLMD_CEL1_P1_FS1)!
WARNING: It is destination site,
Time Since Last Sync might be incorrect (tapelibVARTEN2_CEL1_POOL_FS1)!
--------------------------------------------------------------------------------
================================================================================
WARNING : EMC Replication Stats Collection Tool (504) completed with warning!
VERBOSE report
This section provides an overview of VERBOSE report.
This detailed replication data report is typically generated by Dell Technologies Customer Support personnel to analyze or troubleshoot replication issues. CP504 does not modify or format the data that are collected from the nas_replicate command. It presents the data as is to the mainframe. Therefore, it may not be comprehensive to anyone other than a Dell
Technologies Customer Support representative. The details include:
● Report Execution Time
● ID
● Name
● Source Status
● Network Status
● Destination Status
● Last Sync Time
● Type
● Celerra Network Server
● Dart Interconnect
● Peer Dart Interconnect
● Replication Role
● Source file system
● Source Data Mover
● Source Interface
Using Command Processors with new DLMCPPRC procedure 111
● Source Control Port
● Source Current Data Port
● Destination file system
● Destination Data Mover
● Destination Interface
● Destination Control Port
● Destination Data Port
● Max Out of Sync Time (minutes)
● Next Transfer Size (KB)
● Current Transfer Size (KB)
● Current Transfer Remain (KB)
● Estimated Completion Time
● Current Transfer is Full Copy
● Current Transfer Rate (KB/s)
● Current Read Rate (KB/s)
● Current Write Rate (KB/s)
● Previous Transfer Rate (KB/s)
● Previous Read Rate (KB/s)
● Previous Write Rate (KB/s)
● Average Transfer Rate (KB/s)
● Average Read Rate (KB/s)
Sample output
Sample VERBOSE report is shown below:
STATUS: SUCCESS
EMC Replication Stats Collection Tool (504) v5.5.0-142
Tue Apr 26 11:58:27 EDT 2022
Report Type : VERBOSE
================================================================================
Base Unit
--------------------------------------------------------------------------------
ID = 2227_APM00150319059_2007_2235_APM00150319059_2007
Name = criticalGR
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Mon Apr 12 09:56:19 EDT 2021
Type = filesystem
Celerra Network Server = CS0
Dart Interconnect = loopback
Peer Dart Interconnect = loopback
Replication Role = loopback
Source Filesystem = tapelibTAPEPROC_CEL1_TAPEPROC_FS41
Source Data Mover = server_2
Source Interface = 127.0.0.1
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibTAPEPROC_CEL1_TAPEPROC_FS51
Destination Data Mover = server_2
Destination Interface = 127.0.0.1
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = Manual Refresh
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 0
Previous Read Rate (KB/s) = 0
Previous Write Rate (KB/s) = 0
112 Using Command Processors with new DLMCPPRC procedure
Average Transfer Rate (KB/s) = 0
Average Read Rate (KB/s) = 0
Average Write Rate (KB/s) = 0
================================================================================
ID = 3198_APM00150319059_2007_3136_APM00140518657_2007
Name = REP3ST8
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Tue Apr 26 11:57:39 EDT 2022
Type = filesystem
Celerra Network Server = dot180
Dart Interconnect = s40_s180
Peer Dart Interconnect = s180_s40
Replication Role = destination
Source Filesystem = tapelibREP3ST_CEL1_P1_FS
Source Data Mover = server_2
Source Interface = 192.168.188.2
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibREP3ST_CEL1_P1_FS
Destination Data Mover = server_2
Destination Interface = 192.168.188.3
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 800
Previous Read Rate (KB/s) = 179649
Previous Write Rate (KB/s) = 1059
Average Transfer Rate (KB/s) = 491
Average Read Rate (KB/s) = 173364
Average Write Rate (KB/s) = 1863
================================================================================
ID = 13879_APM00150419850_2007_15587_APM00150319059_2007
Name = VREPL1
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Tue Apr 26 11:50:07 EDT 2022
Type = filesystem
Celerra Network Server = to50
Dart Interconnect = 40_50
Peer Dart Interconnect = 20006
Replication Role = destination
Source Filesystem = 9123
Source Data Mover = server_2
Source Interface = 192.168.182.2
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibVARTEN_CEL1_POOL_FS1
Destination Data Mover = server_2
Destination Interface = 192.168.182.3
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 8598
Previous Read Rate (KB/s) = 25621
Previous Write Rate (KB/s) = 42492
Average Transfer Rate (KB/s) = 8598
Using Command Processors with new DLMCPPRC procedure 113
Average Read Rate (KB/s) = 25621
Average Write Rate (KB/s) = 42492
================================================================================
ID = 12574_APM00150419850_2007_15308_APM00150319059_2007
Name = REPL3_tapelibREPDLMD_CEL1_P1_FS1_DC3_VNX1_DM2
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Tue Apr 26 11:49:47 EDT 2022
Type = filesystem
Celerra Network Server = to50
Dart Interconnect = 40_50
Peer Dart Interconnect = 20006
Replication Role = destination
Source Filesystem = 8369
Source Data Mover = server_2
Source Interface = 192.168.182.2
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibREPDLMD_CEL1_P1_FS1
Destination Data Mover = server_2
Destination Interface = 192.168.182.3
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 208
Previous Read Rate (KB/s) = 36312
Previous Write Rate (KB/s) = 1364
Average Transfer Rate (KB/s) = 561
Average Read Rate (KB/s) = 38914
Average Write Rate (KB/s) = 10400
================================================================================
ID = 13884_APM00150419850_2007_15592_APM00150319059_2007
Name = VREPL2
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Tue Apr 26 11:54:27 EDT 2022
Type = filesystem
Celerra Network Server = to50
Dart Interconnect = 40_50
Peer Dart Interconnect = 20006
Replication Role = destination
Source Filesystem = 9127
Source Data Mover = server_2
Source Interface = 192.168.182.2
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibVARTEN2_CEL1_POOL_FS1
Destination Data Mover = server_2
Destination Interface = 192.168.182.3
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 19609
Previous Read Rate (KB/s) = 22627
Previous Write Rate (KB/s) = 152575
Average Transfer Rate (KB/s) = 19609
Average Read Rate (KB/s) = 22627
114 Using Command Processors with new DLMCPPRC procedure
Average Write Rate (KB/s) = 152575
================================================================================
ID = 1597_APM00150319059_2007_1599_APM00150319059_2007
Name = LOOPBACK_REPL_1
Source Status = OK
Network Status = OK
Destination Status = OK
Last Sync Time = Tue Apr 26 11:55:46 EDT 2022
Type = filesystem
Celerra Network Server = CS0
Dart Interconnect = loopback
Peer Dart Interconnect = loopback
Replication Role = loopback
Source Filesystem = tapelibVGRSRC_CEL1_GR_FS1
Source Data Mover = server_2
Source Interface = 127.0.0.1
Source Control Port = 0
Source Current Data Port = 0
Destination Filesystem = tapelibVGRDST_CEL1_GR_FS1
Destination Data Mover = server_2
Destination Interface = 127.0.0.1
Destination Control Port = 5085
Destination Data Port = 8888
Max Out of Sync Time (minutes) = 10
Current Transfer Size (KB) = 0
Current Transfer Remain (KB) = 0
Estimated Completion Time =
Current Transfer is Full Copy = No
Current Transfer Rate (KB/s) = 0
Current Read Rate (KB/s) = 0
Current Write Rate (KB/s) = 0
Previous Transfer Rate (KB/s) = 0
Previous Read Rate (KB/s) = 26298
Previous Write Rate (KB/s) = 6544
Average Transfer Rate (KB/s) = 7226
Average Read Rate (KB/s) = 38969
Average Write Rate (KB/s) = 3410
================================================================================
================================================================================
INFO : EMC Replication Stats Collection Tool (504) completed successfully!
Obtaining Data Domain and PowerProtect: CP601,
CP602, CP603
NOTE: DLm2500 does not support CP601, CP602, and CP603.
CP601
CP601 generates Data Domain and PowerProtect system utilization statistics and makes the reports available to the mainframe.
A Data Domain and PowerProtect system compresses data at two levels: global and local. Global compression compares received data with the data that are already stored on disks. Duplicate data need not be stored again, while data that is new is compressed before being written to disk. Compressing the new data is called local compression.
Global compression is the same as data deduplication while local compression is the same as hardware compression.
The data compression that is achieved through data deduplication and hardware compression is collectively referred to as total compression in this document.
Total compression = Data deduplication + hardware compression
The Data Domain and PowerProtect system deduplicates incoming tape data before storing it onto the disk. In this process, the actual amount of data to be stored on the disk is much less than the incoming data. CP601 reports the storage usage statistics, which include the following:
● Total amount of incoming data from VTEs
Using Command Processors with new DLMCPPRC procedure 115
● Total amount of data that are stored on the disk after total compression
● Total available space for data storage
● Estimated amount of storage that will be cleaned during next Data Domain and PowerProtect clean operation
CP601 syntax
The CP601 command syntax is:
//CP601 EXEC DLMCPPRC,CMD=601,UNIT=unitid
CP601 parameters
This section provides an overview of CP601 parameters.
CP601 command parameters - none .
Sample JCL:
//CP601 EXEC DLMCPPRC,CMD=601,UNIT=/8700
Sample output
The CP601 example that is shown above produces a storage utilization report as shown in the below sample:
STATUS: SUCCESS
EMC Data Domain Storage Utilization Reporting Tool (601) v5.5.0-142
Fri Apr 22 11:40:34 EDT 2022
Report Type : SYSTEM
================================================================================
Data Domain system: DD-1
--------------------------------------------------------------------------------
Total data received (GiB) : 48174.6
Total storage capacity of Data Domain system (GiB): 13630.9
Total storage used (post compression) (GiB) : 49.9
Total storage available (GiB) : 13581.0
Use% : 0%
Cleanable storage (GiB) : 0.0
Note: * Estimated based on last cleaning of 2022/04/22 11:16:17.
--------------------------------------------------------------------------------
================================================================================
INFO : EMC Data Domain Storage Utilization Reporting Tool (601) completed successfully!
Table 36. CP601 report fields
Field
Total data received (GiB)
Total storage capacity of Data Domain and PowerProtect system (GiB)
Total storage used (post compression) (GiB)
Total storage available (GiB)
Description
Total amount of data received by the Data Domain and
PowerProtect system.
Total storage capacity of the Data Domain and PowerProtect system.
Total storage used after achieving data deduplication and hardware compression of the data.
● Storage available
● {Total storage capacity of Data Domain and PowerProtect system - Total storage used (post compression) }
● This is the storage available for data post data deduplication and hardware compression.
116 Using Command Processors with new DLMCPPRC procedure
Table 36. CP601 report fields (continued)
Field
Use%
Cleanable storage (GiB)
Description
● For example, if total available capacity is 100 GB then it can store 500 GB of received data if the size of received data is 100 GB after total compression.
% of storage used.
Data Domain and PowerProtect does not make space available when a file is deleted. This space is made available only after a periodic cleanup is run on Data Domain and PowerProtect.
This value shows the estimated amount of storage that will be cleaned up during next Data Domain and PowerProtect cleanup operation. This estimation is based on last cleanup operation.
CP602
This section provides an overview of CP602.
The Data Domain and PowerProtect system deduplicates incoming tape data before storing it to disk. As a result of this process, the data size to be stored on disk is much smaller than the received data size.
CP602 generates a report that provides data compression statistics for the Data Domain and PowerProtect system. The compression report could provide data compression statistics for the entire Data Domain and PowerProtect system (DEFAULT report), for particular tape libraries (SUMMARY report), or for each tape file (VOLSER) in the user-specified tape library
(DETAILED or FULL report).
CP602 syntax
The CP602 command syntax is:
//CP602 EXEC DLMCPPRC,CMD=602,UNIT=unitid,
// REPORT='SUMMARY|DETAILED|FULL',DAYS='days COUNT',
// SIZEUNIT='Bytes|KBs|MBs|GBs|TBs',
// TLIB='tapelibname|ALL'
CP602 parameters
This section provides an overview of CP602 parameters.
Table 37. CP602 parameters
Parameter Description
REPORT Specifies the report type. The valid values are:
● Blank—reports compression statistics for the whole Data Domain and PowerProtect.
● SUMMARY—reports only the total information about whole tape libraries.
● DETAILED—lists all Volsers individually but hides scratch volumes;
● FULL—same as DETAILED, but includes scratch volumes
This is an optional parameter.
DAYS
SIZEUNIT
Specifies the number of days (<days count>). The report lists only those files that were changed in the past <days count> days. Specifying a value of 0 indicates that you want the report to list all the files and no filtering is required. This is an optional parameter and is applicable to SUMMARY,
DETAILED, and FULL report types.
Specifies the unit in which the volume size must be reported. The default size unit is bytes. Other valid units are Bytes, KBs, MBs, GBs, and TBs. This is an optional parameter and is only applicable to DETAILED and FULL report types.
Using Command Processors with new DLMCPPRC procedure 117
Table 37. CP602 parameters (continued)
Parameter tapelibname|ALL
Description
Name of the tape library for which you want to retrieve information. The TLIB parameter should not be more than 30 characters in length. This is an optional parameter.
Sample JCL
This section describes a sample JCL.
//CP602 EXEC DLMCPPRC,CMD=602,UNIT=/8700,
// REPORT='SUMMARY',
// DAYS='7',
// SIZEUNIT='KBs',
// TLIB='/tapelibBACKUP'
Sample output
This section provides an overview of sample output.
The SUMMARY report produces compression information about the specified tape libraries. The following is a sample summary report:
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT3
--------------------------------------------------------------------------------
MTree: /data/col1/SMT3
Total files: 18; bytes/storage_used: 3.7
Original Bytes: 18,432
Globally Compressed: 18,432
Locally Compressed: 1,657
Meta-data: 3,384
--------------------------------------------------------------------------------
MTree: /backup
Total files: 10; bytes/storage_used: 3.4
Original Bytes: 10,287
Globally Compressed: 10,287
Locally Compressed: 1,051
Meta-data: 1,952
--------------------------------------------------------------------------------
Tapelib: tapelibMTL1
--------------------------------------------------------------------------------
MTree: /data/col1/SMT1
Total files: 106; bytes/storage_used: 2.7
Original Bytes: 156,592
Globally Compressed: 156,592
Locally Compressed: 30,437
Meta-data: 27,200
--------------------------------------------------------------------------------
MTree: /backup
Total files: 1; bytes/storage_used: 3.8
Original Bytes: 1,024
Globally Compressed: 1,024
Locally Compressed: 80
Meta-data: 188
--------------------------------------------------------------------------------
The DETAILED or FULL report produces compression information about each VOLSER in the tape library.
NOTE: The FULL report type shows scratch volumes while the DETAILED report type does not.
The report displays one list of VOLSERs regardless of the MTree or file system it resides in.
118 Using Command Processors with new DLMCPPRC procedure
The following is a sample FULL report with SIZEUNIT='Bytes':
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT2
--------------------------------------------------------------------------------
Volser Original Globally Locally MetaData Compression
Bytes Compressed Compressed Bytes Rate
Bytes
--------------------------------------------------------------------------------
~YK0019 416 2508 439 296 0.6
YK0001 1004033482 1007375842 77643694 4305752 12.3
YK0003 10040033482 10073739226 774817057 43284212 12.3
YK0005 10007033482 10045962442 758106885 43263764 12.5
YK0007 42939960274 42992151951 1296643935 158322140 29.5
YK0009 214739055250 59929833277 2282742736 220628708 85.8
YK0011 42939960274 43085565622 1299094014 158694020 29.5
YK0013 775996422260 507187571395 16125890311 1867861772 43.1
YK0015 214739055250 137176779584 4375873981 505198988 44.0
YK0017 131739936706 132186610279 3985585902 486862784 29.5
~YK0016 416 2508 439 296 0.6
~YK0018 416 2508 439 296 0.6
YK0000 10040033482 8683548398 672166616 37312316 14.2
YK0002 100433482 100757962 7773745 430064 12.2
~YK0004 416 2508 440 296 0.6
YK0006 42939960274 43085551788 1299151714 158697656 29.5
YK0008 42939960274 43085556044 1299066476 158680952 29.5
YK0010 42939960274 43085528115 1299091970 158685308 29.5
YK0012 214739055250 76472545373 2730207043 281599244 71.3
YK0014 214739055250 214545054444 6471522748 790163180 29.6
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Data Domain system: DD-2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
============================================================
The following is a sample DETAILED report with SIZEUNIT='GBs':
Data Domain system: DD-1
--------------------------------------------------------------------------------
Tapelib: tapelibSMT2
--------------------------------------------------------------------------------
Volser Original Globally Locally MetaData Compression
GBs Compressed Compressed GBs Rate
GBs GBs
--------------------------------------------------------------------------------
YK0001 0.94 0.94 0.07 0.00 12.3
YK0003 9.35 9.38 0.72 0.04 12.3
YK0005 9.32 9.36 0.71 0.04 12.5
YK0007 39.99 40.04 1.21 0.15 29.5
YK0009 199.99 55.81 2.13 0.21 85.8
YK0011 39.99 40.13 1.21 0.15 29.5
YK0013 722.70 472.36 15.02 1.74 43.1
YK0015 199.99 127.76 4.08 0.47 44.0
YK0017 122.69 123.11 3.71 0.45 29.5
YK0000 9.35 8.09 0.63 0.03 14.2
YK0002 0.09 0.09 0.01 0.00 12.2
YK0006 39.99 40.13 1.21 0.15 29.5
YK0008 39.99 40.13 1.21 0.15 29.5
YK0010 39.99 40.13 1.21 0.15 29.5
YK0012 199.99 71.22 2.54 0.26 71.3
YK0014 199.99 199.81 6.03 0.74 29.6
-------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Data Domain system: DD-2
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
=====================================================
Using Command Processors with new DLMCPPRC procedure 119
NOTE: When a tape is deleted or truncated in a Data Domain and PowerProtect filesystem, Data Domain and PowerProtect does not immediately delete the data; however, it is unavailable for reuse. It is recovered for reuse when the next scheduled
Data Domain and PowerProtect cleanup operation is run. The cleanup frees up storage. Therefore, data that are generated before the cleanup does not include the result of file deletion and truncation.
Table 38. CP602 report fields
Field
Filesystem
Volser
Original <sizeunit>
Globally Compressed
Locally Compressed
MetaData <sizeunit>
Compression Rate
Description
The file system where the volser actually resides
The Volser in the tape library
The original file size in Bytes, KBs, MBs, GBs, or TBs
File size after inline deduplication (Bytes, KBs, MBs, GBs, or
TBs)
File size after local compression is applied (Bytes, KBs, MBs,
GBs, or TBs)
Any additional information in bytes or GBs that Data Domain and PowerProtect stores for this file. The sum of the Locally
Compressed and MetaData size is the actual size that Data
Domain and PowerProtect stores for the file.
The ratio of <Original size> to (<Locally Compressed> + <
MetaData size>)
CP603
This section provides an overview of CP603.
This Command Processor reports the following Data Domain and PowerProtect replication information:
● Replication configuration
● Replication status
● Replication statistics
● Replication performance statistics
● Historical replication data for the past 24 hours
CP603 syntax
The CP603 command syntax is:
//CP603 EXEC DLMCPPRC,CMD=603,UNIT=unitid,
// REPORT='report type'
CP603 parameters
This section provides an overview of CP603 parameters.
Table 39. CP603 parameters
Parameter
REPORT
Description
Enter one of the following reports to be generated:
● STATUS — Status report containing the current replication status.
● STATS —Statistics report containing replication statistics.
● PERF — Performance report containing replication performance statistics.
120 Using Command Processors with new DLMCPPRC procedure
Table 39. CP603 parameters
Parameter Description
● HIST — History report containing replication I/O information.
● ALL — All of the above reports.
NOTE: ALL is the default value.
Sample JCL:
This section describes the sample JCL.
//CP603 EXEC DLMCPPRC,CMD=603,UNIT=/8700,
// REPORT='STATS'
Sample output
This section provides an overview of sample output.
STATUS: SUCCESS
EMC Data Domain Replication Statistics Reporting Tool (603) v5.5.0-142
Tue Apr 26 12:40:39 EDT 2022
Report Type : REPLICATION STATS
================================================================================
Data Domain system: DD-1
--------------------------------------------------------------------------------
REPLICATION CONFIG
--------------------------------------------------------------------------------
CTX Source Destination
Connection Low-bw-optim
Crepl-gc-bw-optim Encryption Enabled Max-repl-streams
Host and Port
--- -------------------------------------------------
--------------------------------------------------
------------------------------------ ------------ ----------------- -----------
------- -------
1 mtree://dd1n0.lss.emc.com/data/col1/REPL mtree://dd1-170130.lss.emc.com/ data/col1/REPLMTREE 10.246.165.210* (default)* disabled disabled
disabled yes 24
2 mtree://DD1-30160.corp.emc.com/data/col1/CMTREE mtree://DD2-30160.corp.emc.com/ data/col1/CMTREE DD1-30160.corp.emc.com* (default)* disabled disabled
disabled yes 24
3 mtree://DD1-170130.lss.emc.com/data/col1/KIA mtree://170170.lss.emc.com/ data/col1/KIA 10.246.170.176 (default) disabled disabled
disabled yes 24
4 mtree://G5P1DD9500.lss.emc.com/data/col1/DD1TODD1 mtree://DD1-170130.lss.emc.com/ data/col1/DD1TODD1 10.246.168.175* (default)* disabled disabled
disabled yes 24
5 mtree://dd168130.lss.emc.com/data/col1/VARMT0 mtree://dd1-170130.lss.emc.com/ data/col1/VARMT0 10.246.168.131* (default)* disabled disabled
disabled yes 24
6 mtree://DD1-170130.lss.emc.com/data/col1/KIA mtree://dd168130.lss.emc.com/ data/col1/KIA 10.246.168.131 (default) disabled disabled
disabled yes 24
7 mtree://dd1n0.lss.emc.com/data/col1/IGOR mtree://dd1-170130.lss.emc.com/
Using Command Processors with new DLMCPPRC procedure 121
data/col1/IGOR 10.246.170.139* (default)* disabled disabled
disabled yes 24
--- -------------------------------------------------
-------------------------------------------------- -----------------
DD System default Max-repl-streams per context: 24
* Used for recovery only.
================================================================================
REPLICATION STATISTICS
--------------------------------------------------------------------------------
CTX: 1
Destination: mtree://dd1-170130.lss.emc.com/data/col1/
REPLMTREE
Network bytes received from source: 1,263,124
Pre-compressed bytes written to source: 22,176,380,239
Pre-compressed bytes sent to destination: 928
Pre-compressed bytes remaining: 0
Compression ratio: N/A
Sync'ed-as-of time: Tue Apr 26 12:27
CTX: 2
Destination: mtree://DD2-30160.corp.emc.com/data/col1/
CMTREE
Network bytes received from source: 118,442,976
Pre-compressed bytes written to source: 11,543,605,422
Pre-compressed bytes sent to destination: 0
Pre-compressed bytes remaining: 0
Compression ratio: N/A
Sync'ed-as-of time: Fri May 29 13:14
CTX: 3
Destination: mtree://170170.lss.emc.com/data/col1/KIA
Network bytes sent to destination: 1,113,471,804
Pre-compressed bytes written to source: 2,227,318,335
Pre-compressed bytes sent to destination: 2,227,289,617
Pre-compressed bytes remaining: 0
Compression ratio: 2.0
Sync'ed-as-of time: Tue Apr 26 12:40
CTX: 4
Destination: mtree://DD1-170130.lss.emc.com/data/col1/
DD1TODD1
Network bytes received from source: 5,407,108,276
Pre-compressed bytes written to source: 5,246,771,205
Pre-compressed bytes sent to destination: 5,246,765,941
Pre-compressed bytes remaining: 0
122 Using Command Processors with new DLMCPPRC procedure
Compression ratio: 1.0
Sync'ed-as-of time: Tue Apr 26 12:29
CTX: 5
Destination: mtree://dd1-170130.lss.emc.com/data/col1/
VARMT0
Network bytes received from source: 138,576
Pre-compressed bytes written to source: 0
Pre-compressed bytes sent to destination: 0
Pre-compressed bytes remaining: 0
Compression ratio: N/A
Sync'ed-as-of time: Wed Mar 16 05:53
CTX: 6
Destination: mtree://dd168130.lss.emc.com/data/col1/KIA
Network bytes sent to destination: 1,108,656,308
Pre-compressed bytes written to source: 2,227,318,335
Pre-compressed bytes sent to destination: 2,227,289,617
Pre-compressed bytes remaining: 0
Compression ratio: 2.0
Sync'ed-as-of time: Tue Apr 26 12:25
CTX: 7
Destination: mtree://dd1-170130.lss.emc.com/data/col1/
IGOR
Network bytes received from source: 545,072
Pre-compressed bytes written to source: 0
Pre-compressed bytes sent to destination: 0
Pre-compressed bytes remaining: 0
Compression ratio: N/A
Sync'ed-as-of time: Tue Apr 26 12:27
================================================================================
--------------------------------------------------------------------------------
================================================================================
INFO : EMC Data Domain Replication Statistics Reporting Tool (603) completed successfully!
Table 40. CP603 reports: REPLICATION CONFIG fields
Field Description
CTX
Source
The context number for directory replication.
The Data Domain and PowerProtect system that receives data from backup applications.
Using Command Processors with new DLMCPPRC procedure 123
Table 40. CP603 reports: REPLICATION CONFIG fields (continued)
Field
Enabled
Destination
Description
The replication process is yes (enabled and available to replicate data) or no (disabled and not available to replicate data).
The Data Domain and PowerProtect system that receives data from the replication source Data Domain system.
Connection A source Data Domain and PowerProtect system connects to the destination Data Domain and PowerProtect system by using the destination name as returned by the hostname command on the destination or by using a destination name or IP address and port that is given with the replication modify connection-host command. The destination hostname may not resolve to the correct IP address for the connection when connecting to an alternate interface on the destination or when a connection passes through a firewall.
Table 41. CP603 REPLICATION STATUS report fields
Field Description
CTX The context number for directory replication.
Mode
Destination
Enabled
Local file system status
Connection
State
Error
Sync'ed-as-of time
Current throttle
The role of the local system: source or destination.
The replication destination.
The enabled state (yes or no) of replication for each replication pair.
The status (enabled or disabled) of the local file system.
The most recent connection date and time or connection state for a replication pair.
The state of the replication process.
A listing of any errors in the replication process.
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ appears during replication initialization.
The current throttle setting.
Table 42. CP603 REPLICATION STATISTICS report fields
Field
CTX
Description
The context number for directory replication.
Destination
Network bytes sent
Pre-compressed bytes written to source
Pre-compressed bytes sent to destination
Pre-compressed bytes remaining
The replication destination.
The number of bytes sent over the network. Does not include TCP/IP headers. Includes internal replication control information, metadata, and file system data.
Indicates the number of bytes of pre-compressed data that are sent to the source.
Indicates the number of bytes of pre-compressed data that are sent to the destination.
The sum of the sizes of one or more files remaining to be replicated for this context. This includes the *entire* logical size of the current file being replicated, so if a large file is being replicated, this number may not change for a noticeable period—it changes only after the current file finishes.
124 Using Command Processors with new DLMCPPRC procedure
Table 42. CP603 REPLICATION STATISTICS report fields (continued)
Field
Files remaining
Description
The number of files that are not replicated.
Compression ratio
Sync'ed-as-of time
The ratio of bytes transferred to network bytes transferred.
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ be displays during replication initialization.
Table 43. CP603 REPLICATION PERFORMANCE report fields
Field Description rctx://1
Pre-Comp (KB/s)
Network (KB/s)
Streams
Busy Reading
Busy Meta
Waiting Dest.
Waiting Network
Indicates the interval in seconds that the performance data represents. In this example, rctx is 1 second (default is 2 seconds).
Virtual speed over the network. The number of kilobytes per second of pre-compressed data that were transferred over the network during the specified interval.
Data speed over the network. The number of kilobytes per second of compressed data that were transferred over the network during the specified interval.
Number of Streams used for the Context (number ranges from 1 to 9 ). If the Context is configured and enabled, the streams column displays 1 because one stream is reserved. If all eight streams are used, it displays 9.
When the source Data Domain and PowerProtect system is actively replicating data, the percent of that active time that is spent reading the source data.
When the source Data Domain and PowerProtect system is actively replicating data, the percent of that active time that is spent processing overhead data on behalf of the source data.
When the source Data Domain and PowerProtect system is waiting on an event while replicating, the percent of that time that is spent waiting on the destination Data Domain and
PowerProtect system.
When the source Data Domain and PowerProtect system is waiting on an event while replicating, the percent of that time that is spent waiting on the network.
Table 44. CP603 REPLICATION HISTORY report fields
Field
Sync-as-of Time
Description
The time when the most recently replicated data on the destination was generated on the source. A value ‘unknown’ be displays during replication initialization.
Pre-Comp (KB) Remaining
Replicated (KB) Pre-Comp
Replicated (KB) Network
The amount of pre-compression data that is not replicated.
The amount of pre-compressed data that is replicated.
The amount of compressed data sent over the network.
Using Command Processors with new DLMCPPRC procedure 125
Obtaining Replication Information by VOLSER: CP804
CP804 is supported from DLm 5.4 and later, on DLm8500 with VNX, DD, or OneFS.
CP804 generates reports that provide replication statistics for each file system mounted on VTE. By using the TLIB and
PREFIX parameters the CP804 report is limited to either a specific tape library or to a single specific non-scratch VOLSER.
CP804 syntax
The CP804 command syntax is:
//CP804 EXEC DLMCPPRC,CMD=804,UNIT=unitid,
// REPORT='report type',
// TLIB='tape library',
// PREFIX='prefix'
CP804 parameters
The section provides an overview of CP804 parameters. All three parameters are optional.
Table 45. CP804 parameters
Parameter
REPORT
TLIB
PREFIX
Description
Type of the replication report you want to retrieve. Valid options are:
● SUMMARY (default value)
● DETAILED
● FULL
Name of the tape library for which you want to retrieve replication report. Valid options are:
● Tape library name
● ALL (default value)
From 1 to 6 six uppercase alphanumeric characters [A-Z0-9] to filter the list of volumes, only volumes start with prefix will be processed. By default, all non-scratch volumes are processed.
SUMMARY Report: CP804
The SUMMARY report displays the replication statistics for each file system that is mounted on the VTE:
● Name
● Replication role
○ Not enabled for replication
○ Source
○ Destination
○ Cascade (Destination+Source)
○ Concurrent (Multi source)
○ Hybrid (Concurrent+Cascade)
● Source Status
○ Success (if all sources in success state)
○ Error (if all sources in error state)
○ Warning (some sources in success state, some sources in error state)
○ N/A (for Destination or Not enabled for replication roles)
126 Using Command Processors with new DLMCPPRC procedure
● Last sync time (N/A for Destination and Not enabled for replication roles).
● Not replicated volumes count.
● Replicated volumes count.
Sample JCL
//CP804 EXEC DLMCPPRC,CMD=804,UNIT=/8700,
// REPORT='SUMMARY',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.5.0-142
Tue Apr 26 12:47:59 EDT 2022
Report Type : SUMMARY
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelibREP3/CEL1_P1_FS1
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:37:44
Not replicated volumes : 6
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes : 6
Replicated volumes : 8
=================================================================================
=================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
DETAILED Report: CP804
The DETAILED report for each file system that is mounted on the VTE displays similar statistics as SUMMARY report. The
DETAILED report also displays the 'List of not replicated volumes with mtime '.
Sample JCL
//CP804 EXEC DLMCPPRC,CMD=804,UNIT=/8700,
// REPORT='DETAILED',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.5.0-142
Tue Apr 26 12:47:59 EDT 2022
Report Type : DETAILED
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelibREP3/CEL1_P1_FS1
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:37:44
List of not replicated volumes for /tapelibREP3/CEL1_P1_FS1
Volume Mtime
VM0008 2021-08-20 10:37:57
VM0009 2021-08-20 10:39:10
VM0010 2021-08-20 10:39:15
VM0011 2021-08-20 10:39:18
Using Command Processors with new DLMCPPRC procedure 127
VM0012 2021-08-20 10:39:19
VM0013 2021-08-20 10:39:22
Summary for /tapelibREP3/CEL1_P1_FS1
Not replicated volumes: 6
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes: 6
Replicated volumes : 8
================================================================================
================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
FULL Report: CP804
The DETAILED report for each file system that is mounted on the VTE displays similar statistics as SUMMARY report. The FULL report also displays the 'list of volumes with mtime and volume replication status (Not replicated or Replicated)'.
Sample JCL
//CP804 EXEC DLMCPPRC,CMD=804,UNIT=/8700,
// REPORT='FULL',
// TLIB='tapelibREP3',
// PREFIX='VM'
Sample Report
STATUS: SUCCESS
Dell Replication Stats Collection Tool (804) v5.5.0-142
Tue Apr 26 12:47:59 EDT 2022
Report Type : FULL
================================================================================
Tape library: tapelibREP3
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
File system : /tapelib/REP3/CEL1_P1_FS1
Replication role : Concurrent
Source status : Success
Last sync time : 2021-08-20 10:40:54
List of volumes for /tapelibREP3/CEL1_P1_FS1
Volume Mtime Replication Status
VM0000 2021-08-20 10:25:22 Replicated
VM0001 2021-08-20 10:25:29 Replicated
VM0002 2021-08-20 10:25:38 Replicated
VM0003 2021-08-20 10:25:46 Replicated
VM0004 2021-08-20 10:34:51 Replicated
VM0005 2021-08-20 10:34:53 Replicated
VM0006 2021-08-20 10:34:56 Replicated
VM0007 2021-08-20 10:34:59 Replicated
VM0008 2021-08-20 10:44:52 Not replicated
VM0009 2021-08-20 10:44:49 Not replicated
VM0010 2021-08-20 10:44:45 Not replicated
VM0011 2021-08-20 10:44:39 Not replicated
VM0012 2021-08-20 10:44:34 Not replicated
VM0013 2021-08-20 10:44:30 Not replicated
Summary for /tapelibREP3/CEL1_P1_FS1
Not replicated volumes: 6
Replicated volumes : 8
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Summary for tapelibREP3
Not replicated volumes: 6
Replicated volumes : 8
================================================================================
================================================================================
WARNING : Dell Replication Stats Collection Tool (804) completed successfully!
128 Using Command Processors with new DLMCPPRC procedure
Obtaining tape activity: CP988 and CP989
CP988 and CP989 are supported only on 4.5.3 and later and 5.x.
CP988
Command Processor CP988 retrieves statistics from a VOLSER range and generates a report of this data.
CP988 syntax
The CP988 command syntax:
//CP988 EXEC DLMCPPRC,CMD=988,UNIT=/unitid,
// REPORT=’report type’,
// STRTDATE=’start date’,
// ENDDATE=’end date’,
// SYNCTIME=’sync time’
CP988 parameters
This section provides an overview of CP988 parameters.
Table 46. CP988 parameters
Parameter
REPORT
STRTDATE
ENDDATE
NODENAME
NPROCS
TLIB
Description throughput | maxtapes | stillinuse | slowmounts=NN | detail
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data preceding the date that is specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
vtename|ALL: Filters the input data to select a particular VTE
(or all VTEs). An example is NODENAME=vte1. The default value is ALL. This parameter is not case-sensitive.
NOTE: This parameter is used only for CP988 and ignored for CP989.
The number of processes (from 1 to 16) that can run statfmt in parallel.
NOTE: This parameter is introduced in DLm 5.0.1 and
DLm 4.5.4 releases.
tapelibname|ALL:
● Filters the input data for a particular tape library or group of libraries.
● This parameter is used only for CP988 and ignored for
CP989.
The characters that are specified are matched against the tape library names of the input records. Only the characters that are specified, need to match for CP988 to accept a record. For example, if you specify TLIB=tapelib/G, and the
Using Command Processors with new DLMCPPRC procedure 129
Table 46. CP988 parameters (continued)
Parameter
SYNCTIME
Description
VTE paths include tapelib/G0, tapelib/G1, and so on, all of the tapelib/Gx records are processed.
NOTE: This parameter is case-sensitive.
HH/MM/SS: This parameter can be used only with the
STILLINUSE report (along with the ENDDATE parameter) to specify the point at which the STILLINUSE check will be applied. Besides, tapes that are mounted after SYNCTIME will be listed for user evaluation purposes.
Sample JCL
//CP988 EXEC DLMCPPRC,CMD=988,UNIT=/8700,
// REPORT='STILLINUSE',
// STRTDATE='01/01/2018',
// ENDDATE='02/21/2018',
// TLIB='/tapelibBACKUP',
// NODENAME='VTE1',NPROCS='2',
// SYNCTIME='01/01/01'
CP988 Sample Reports
This section provides an overview of CP988 sample reports.
THROUGHPUT report
STATUS:
SUCCESS
DLm Virtual Tape Activity Reporting Tool (988) v5.5.0-142
Tue Apr 26 12:26:12 EDT
2022
================================================================================
PATHS INCLUDED IN
STATS :
NODENAME
PATH vte1 /tapelibC/
CEL1_P1_FS2 vte2 /tapelibC/
CEL1_P1_FS2
--------------------------------------------------------------------------------
THROUGHPUT IN GB/
HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT
08|OUT 09|OUT 10|OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT
20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
130 Using Command Processors with new DLMCPPRC procedure
+-------+-------+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN
08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN
20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/07/29| 0.00| 0.00| 23.84| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=24G TOT/DAY=24G OUT/DY=24G IN/DY=0G MAXO/HR=24G MAXI/HR=0G
MOUNTS/DY=1 MAXMNT/HR=1
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/10/29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
86.52| 577.43| 146.69| 227.11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 136.71| 204.16|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=577G TOT/DAY=1379G OUT/DY=1038G IN/DY=341G MAXO/HR=577G MAXI/
HR=204G MOUNTS/DY=553 MAXMNT/HR=231
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/11/02| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=5 MAXMNT/HR=4
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/11/09| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
Using Command Processors with new DLMCPPRC procedure 131
MAXTAPES report
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=0 MAXMNT/HR=0
COUNT OF UNLOAD RECORDS :
559
COUNT OF UNLOADS W/OUTPUT STATS:
417
COUNT OF UNLOADS W/INPUT STATS :
139
MAXIMUM OUTPUT/HR :
577G
MAXIMUM OUTPUT/DAY :
1038G
MAXIMUM INPUT/HR :
204G
MAXIMUM INPUT/DAY :
341G
MAXIMUM THROUGPUT/HR :
577G
MAXIMUM THROUGPUT/DAY :
1379G
MAXIMUM MOUNTS/HR :
231
MAXIMUM MOUNTS/DAY :
553
EFFECTIVE COMPRESSION RATIO : 2.9 to
1
AVERAGE MOUNT RESPONSE (SECS.) :
0.039
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (988) completed successfully!
STATUS:
SUCCESS
DLm Virtual Tape Activity Reporting Tool (988) v5.5.0-142
Tue Apr 26 12:24:03 EDT
2022
================================================================================
PATHS INCLUDED IN
STATS :
NODENAME
PATH vte1 /tapelibC/
CEL1_P1_FS2 vte2 /tapelibC/
CEL1_P1_FS2
--------------------------------------------------------------------------------
132 Using Command Processors with new DLMCPPRC procedure
MAX TAPES IN USE PER
HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD| 00| 01| 02| 03| 04| 05| 06| 07|
08| 09| 10| 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 12| 13| 14| 15| 16| 17| 18| 19|
20| 21| 22| 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/07/29| ***| 1| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/10/29| ***| ***| ***| ***| ***| ***| ***| ***|
2| 2| 2| 2|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/11/02| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| 1|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 1| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/11/09| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (988) completed successfully!
TOP 10
SLOWEST
MOUNTS report
SLOWMOUNTS=10 report
STATUS: SUCCESS
DLm Virtual Tape Activity Reporting Tool (988) v5.5.0-142
Tue Apr 26 12:28:16 EDT 2022
================================================================================
PATHS INCLUDED IN STATS :
NODENAME PATH vte1 /tapelibC/CEL1_P1_FS2 vte2 /tapelibC/CEL1_P1_FS2
--------------------------------------------------------------------------------
TOP 10 SLOWEST MOUNTS (SECS.):
Using Command Processors with new DLMCPPRC procedure 133
NODENAME DURATION VOLSER DATE TIME PATH vte1 4.004 TES000 2021/11/02 12:56:26 /tapelibC/CEL1_P1_FS2 vte1 0.163 TES111 2021/10/29 10:46:00 /tapelibC/CEL1_P1_FS2 vte1 0.141 TES233 2021/10/29 10:59:12 /tapelibC/CEL1_P1_FS2 vte1 0.115 TES108 2021/10/29 11:17:46 /tapelibC/CEL1_P1_FS2 vte1 0.114 TES236 2021/10/29 11:07:09 /tapelibC/CEL1_P1_FS2 vte1 0.108 TES128 2021/10/29 11:23:34 /tapelibC/CEL1_P1_FS2 vte1 0.107 TES276 2021/10/29 11:43:26 /tapelibC/CEL1_P1_FS2 vte1 0.107 TES159 2021/10/29 11:09:46 /tapelibC/CEL1_P1_FS2 vte1 0.104 TES168 2021/10/29 11:37:53 /tapelibC/CEL1_P1_FS2 vte1 0.103 TEST76 2021/10/29 11:13:14 /tapelibC/CEL1_P1_FS2
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (988) completed successfully!
STILLINUSE report vte1dlm0 tapelibFLR/CEL1_FLRP_FS1 vte1dlm0 tapelibFLR/CEL1_FLRP_FS2
------------------------------------------------------
VOLSERS IN USE AT SYNCTIME (06/06/2017 10:00:00)
NODENAME DEVICE VOLSER LAST MOUNTED vte1 F200 200915 2016/02/01 06:53:34
------------------------------------------------------
VOLSERS MOUNTED AFTER SYNCTIME (06/06/2017 10:00:00)
DATE TIME VOLSER NODENAME PATH
2017/06/19 10:17:56 BFL999 vte1
2017/06/27 06:06:12 YK5006 vte1
2017/06/27 06:09:54 YK5007 vte1
2017/06/27 06:12:36 YK5008 vte1
2017/06/27 06:12:37 BFLYK vte1
2017/06/27 06:13:39 YK5009 vte1
2017/06/27 06:14:45 YK5004 vte1
2017/06/28 16:02:38 YK5005 vte1
------------------------------------------------------
CP989
Command Processor CP989 retrieves statistics from a local VTE and generates a report of this data.
CP989 syntax
The CP989 command syntax:
//CP989 EXEC DLMCPPRC,CMD=989,UNIT=/unitid,
// REPORT=’report type’,
// STRTDATE=’start date',
// ENDDATE=’end date’
CP989 parameters
This section provides an overview of CP989 parameters.
Table 47. CP989 parameters
Parameter
REPORT
STRTDATE
Description throughput | maxtapes | stillinuse | slowmounts=NN | detail
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data preceding the date that is specified. Use of this parameter
134 Using Command Processors with new DLMCPPRC procedure
Table 47. CP989 parameters (continued)
Parameter
ENDDATE
SYNCTIME
Description can result in improved performance when dealing with large amounts of statistical data.
MM/DD/YYYY: MM (2 digit month), DD (2 digit day), YYYY
(4 digit year). This optional parameter excludes statistics data after the date specified. Use of this parameter can result in improved performance when dealing with large amounts of statistical data.
HH/MM/SS: This parameter can be used only with the
STILLINUSE report (along with the ENDDATE parameter) to specify the point at which the STILLINUSE check will be applied. Besides, tapes that are mounted after SYNCTIME will be listed for user evaluation purposes.
Sample JCL
//CP989 EXEC DLMCPPRC,CMD=989,UNIT=/8700,
// REPORT='THROUGHPUT',
// STRTDATE='06/01/2021',
// ENDDATE='04/01/2022'
CP989 Sample Reports
This section provides an overview of CP989 sample reports.
THROUGHPUT report
STATUS:
SUCCESS
DLm Virtual Tape Activity Reporting Tool (989) v5.5.0-142
Tue Apr 26 12:15:03 EDT
2022
================================================================================
NODENAME = vte1
--------------------------------------------------------------------------------
THROUGHPUT IN GB/
HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD|OUT 00|OUT 01|OUT 02|OUT 03|OUT 04|OUT 05|OUT 06|OUT 07|OUT
08|OUT 09|OUT 10|OUT 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |OUT 12|OUT 13|OUT 14|OUT 15|OUT 16|OUT 17|OUT 18|OUT 19|OUT
20|OUT 21|OUT 22|OUT 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 00|IN 01|IN 02|IN 03|IN 04|IN 05|IN 06|IN 07|IN
08|IN 09|IN 10|IN 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| |IN 12|IN 13|IN 14|IN 15|IN 16|IN 17|IN 18|IN 19|IN
20|IN 21|IN 22|IN 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
Using Command Processors with new DLMCPPRC procedure 135
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/17| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 3.68|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=4G TOT/DAY=4G OUT/DY=4G IN/DY=0G MAXO/HR=4G MAXI/HR=0G MOUNTS/
DY=5 MAXMNT/HR=5
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 20.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=20G TOT/DAY=20G OUT/DY=20G IN/DY=0G MAXO/HR=20G MAXI/HR=0G
MOUNTS/DY=10 MAXMNT/HR=3
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/22| 0.00| 0.00| 0.00| 0.00| 0.00| 0.22| 0.41| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=1G OUT/DY=1G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=5 MAXMNT/HR=2
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/23| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
136 Using Command Processors with new DLMCPPRC procedure
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=12 MAXMNT/HR=6
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/24| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=7 MAXMNT/HR=3
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/25| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=4 MAXMNT/HR=4
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=232 MAXMNT/HR=232
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/01/12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
Using Command Processors with new DLMCPPRC procedure 137
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=2 MAXMNT/HR=2
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/01/19| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 93.13| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=93G TOT/DAY=93G OUT/DY=0G IN/DY=93G MAXO/HR=0G MAXI/HR=93G
MOUNTS/DY=8 MAXMNT/HR=3
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/02/15| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=1 MAXMNT/HR=1
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/03/18| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 4.09| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
138 Using Command Processors with new DLMCPPRC procedure
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=4G TOT/DAY=4G OUT/DY=0G IN/DY=4G MAXO/HR=0G MAXI/HR=4G MOUNTS/
DY=4 MAXMNT/HR=4
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/03/30| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=8 MAXMNT/HR=8
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/04/01| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00| 0.00| 0.00| 0.00|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
MAXI+O/HR=0G TOT/DAY=0G OUT/DY=0G IN/DY=0G MAXO/HR=0G MAXI/HR=0G MOUNTS/
DY=2 MAXMNT/HR=2
COUNT OF UNLOAD RECORDS :
300
COUNT OF UNLOADS W/OUTPUT STATS:
259
COUNT OF UNLOADS W/INPUT STATS :
235
MAXIMUM OUTPUT/HR :
20G
MAXIMUM OUTPUT/DAY :
20G
MAXIMUM INPUT/HR :
93G
MAXIMUM INPUT/DAY :
93G
MAXIMUM THROUGPUT/HR :
93G
MAXIMUM THROUGPUT/DAY :
93G
MAXIMUM MOUNTS/HR :
232
MAXIMUM MOUNTS/DAY :
232
EFFECTIVE COMPRESSION RATIO : 11.3 to
1
AVERAGE MOUNT RESPONSE (SECS.) :
0.089
================================================================================
Using Command Processors with new DLMCPPRC procedure 139
MAXTAPES report
INFO : DLm Virtual Tape Activity Reporting Tool (989) completed successfully!
STATUS:
SUCCESS
DLm Virtual Tape Activity Reporting Tool (989) v5.5.0-142
Tue Apr 26 12:18:15 EDT
2022
================================================================================
NODENAME = vte1
--------------------------------------------------------------------------------
MAX TAPES IN USE PER
HR :
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|YY/MM/DD| 00| 01| 02| 03| 04| 05| 06| 07|
08| 09| 10| 11|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 12| 13| 14| 15| 16| 17| 18| 19|
20| 21| 22| 23|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/17| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| 1|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/21| ***| ***| 1| ***| ***| ***| 1| ***|
***| ***| ***| 1|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 1| 2| 1| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/22| ***| ***| 1| ***| ***| 1| 1| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/23| ***| ***| ***| 1| ***| ***| ***| ***|
***| ***| ***| 1|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 1| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
140 Using Command Processors with new DLMCPPRC procedure
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/24| ***| ***| 1| 2| 2| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| 1| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/25| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| 1| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|21/12/29| ***| ***| ***| ***| ***| ***| ***| 16|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/01/12| ***| ***| ***| ***| ***| ***| ***| 1|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/01/19| ***| 1| 1| 2| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/02/15| ***| ***| ***| ***| ***| ***| ***| 1|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/03/18| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| 1| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
Using Command Processors with new DLMCPPRC procedure 141
+-------+-------+-------+-------+
|22/03/30| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | 1| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
|22/04/01| ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| 1| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
| | ***| ***| ***| ***| ***| ***| ***| ***|
***| ***| ***| ***|
+--------+-------+-------+-------+-------+-------+-------+-------+-------
+-------+-------+-------+-------+
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (989) completed successfully!
TOP 10
SLOWEST
MOUNTS report
SLOWMOUNTS=10 report
STATUS: SUCCESS
DLm Virtual Tape Activity Reporting Tool (989) v5.5.0-142
Tue Apr 26 12:20:31 EDT 2022
================================================================================
NODENAME = vte1
--------------------------------------------------------------------------------
TOP 10 SLOWEST MOUNTS (SECS.):
NODENAME DURATION VOLSER DATE TIME PATH vte1 9.128 L00944 2021/12/21 11:11:36 vte1 9.121 L00944 2021/12/21 11:15:39 vte1 0.385 AE0098 2021/12/29 07:54:46 vte1 0.253 AE0090 2021/12/29 07:54:37 vte1 0.243 TT7532 2021/12/23 03:37:12 vte1 0.240 OB0002 2021/12/29 07:55:02 vte1 0.236 OB0003 2021/12/29 07:55:02 vte1 0.235 OB0001 2021/12/29 07:55:02 vte1 0.232 OB0000 2021/12/29 07:55:02 vte1 0.161 OB0004 2021/12/29 07:55:02
================================================================================
INFO : DLm Virtual Tape Activity Reporting Tool (989) completed successfully!
STILLINUSE report
NODENAME = vte1
-----------------------------------------------------------------
VOLSERS IN USE AT SYNCTIME (06/06/2017 10:00:00)
NODENAME DEVICE VOLSER LAST MOUNTED vte1 F200 200915 2016/02/01 06:53:34
-----------------------------------------------------------------
VOLSERS MOUNTED AFTER SYNCTIME (06/06/2017 10:00:00)
DATE TIME VOLSER NODENAME PATH
2017/06/19 10:17:56 BFL999 vte1
2017/06/27 06:06:12 YK5006 vte1
2017/06/27 06:09:54 YK5007 vte1
2017/06/27 06:12:36 YK5008 vte1
2017/06/27 06:12:37 BFLYK vte1
2017/06/27 06:13:39 YK5009 vte1
2017/06/27 06:14:45 YK5004 vte1
2017/06/28 16:02:38 YK5005 vte1
-----------------------------------------------------------------
142 Using Command Processors with new DLMCPPRC procedure
DETAIL report
NODENAME = vte1
--------------------------------------------------------------------------------
DETAIL REPORT:
------ Unload ----- ------ Channel ------ ---- File System ---- Duration
Compression
Volser Date Time 4K Writes 4K Reads 4K Writes 4K Reads Time
Percent
------ ---------- -------- ---------- -------- ---------- ---------- ----------
-----------
700000 2017/05/31 09:27:52 48829 48829 50249 0 97
700000 2017/05/31 09:30:34 48829 48829 50249 0 97
700000 2017/05/31 09:36:40 48829 48829 50249 0 95
700000 2017/05/31 09:42:52 48829 1 50249 0 55
700000 2017/05/31 09:43:49 48829 1 50249 0 56
700000 2017/05/31 09:44:44 48829 1 50249 0 55
700000 2017/05/31 09:45:39 48829 1 50249 0 54
700000 2017/05/31 09:46:40 48829 1 50249 0 61
700000 2017/05/31 09:57:44 48829 48829 50249 0 89
700000 2017/05/31 10:18:15 48829 48829 50249 0 96
700000 2017/05/31 10:24:57 49 49 51 0 0
700000 2017/05/31 10:24:58 49 49 51 0 1
700000 2017/05/31 10:24:59 49 49 51 0 1
700000 2017/05/31 10:24:59 49 49 51 0 0
700000 2017/05/31 10:25:00 49 49 51 0 0
700000 2017/05/31 10:57:17 48829 48829 50249 0 96
700000 2017/05/31 10:57:46 25283 1 26019 0 28
700000 2017/05/31 10:58:01 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:02 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:02 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:03 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:04 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:21 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:22 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:22 1 1 1 0 0 0.00%
700000 2017/05/31 10:58:23 1 1 1 0 1 0.00%
700000 2017/05/31 10:58:23 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:30 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:31 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 1 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 0 0.00%
700000 2017/05/31 11:07:32 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:54 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:55 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:56 1 1 1 0 1 0.00%
700000 2017/05/31 11:10:56 1 1 1 0 0 0.00%
700000 2017/05/31 11:10:57 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:27 1 1 1 0 1 0.00%
700000 2017/05/31 11:56:27 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:28 1 1 1 0 1 0.00%
700000 2017/05/31 11:56:28 1 1 1 0 0 0.00%
700000 2017/05/31 11:56:29 1 1 1 0 0 0.00%
NLFW24 2017/05/31 12:23:20 1075822 0 42838 0 474 96.00%
NLFW24 2017/05/31 12:38:29 0 1075823 42838 0 909
--------------------------------------------------------------------------------
Using Command Processors with new DLMCPPRC procedure 143
6
Command Processor Procedures
This chapter describes the procedures for DLMTRPT, DLMCMDPR, DLMCMDP1, GENSTATP, GENSTAT1, and GENSTATW/R utilities.
Topics:
•
MTL Considerations for VTE Drive Selection
•
DLMTRPT: z/OS Catalog and DLm repository matching report procedure
•
Command Processor parameters used in procedures
•
•
DLMCMDPR, DLMCMDP1 and DLMCMD49 Procedures
•
•
•
•
MTL Considerations for VTE Drive Selection
This section provides an overview of MTL Considerations for VTE Drive Selection.
About this task
When a request is made for a tape drive that is defined in an MTL, the Automatic Class Selection (ACS) routines select the appropriate tape storage group for the library. Allocation subsequently chooses any available drive in that library.
This is not an issue if only one VTE is defined as part of the library. However, an MTL can span multiple VTEs for performance and failover considerations. In this case, targeting a specific VTE for batch utilities is required.
The SMSHONOR parameter is now supported in all supported z/OS releases. With this parameter, a particular Unit that is part of an MTL can be specified. For example:
//GO EXEC DLMCPRUN,CMD=601,UNIT=/860F,SMSHNR=SMSHONOR,FLATDISP=OLD
NOTE: FLATDISP=OLD is required when using MTL device in DLMCPRUN procedure.
//GO EXEC DLMCMDP1,CMD=503,UNIT=(/4305,,,SMSHONOR)
NOTE: The SMSHONOR clause is not supported for the UNIT2 parameter in the DLMCMDPR and GENSTATP PROCs.
(UNIT2 is the Unit parameter that must be offline.)
Use one of the following methods to enable a batch utility to communicate with a specific VTE:
Steps
1. If the MTL spans across multiple VTEs, omit a single drive from the MTL in each VTE's device group. For example, consider an MTL defined with two VTEs, each configured with 64 devices: a. In each VTE, define 63 devices as MTL=YES in the HCD. One device would be MTL=NO in the HCD.
b. After, use demand allocation in JCL to select the specific drive address that is outside the MTL.
2. Define a separate MTL for each VTE to enable VTE selection: a. Similar to the previous method, define only 63 devices on each VTE as part of the same MTL.
b. For each VTE, define a separate MTL (different LIB-ID) for the remaining device, and a new esoteric.
c. Use ACS routines to select the appropriate library that limits the available drive selection to that one drive.
144 Command Processor Procedures
Results
It is recommended that you leave this drive offline to prevent inadvertent allocation by other jobs. One way to accomplish this is to bookend your jobs with steps to vary the device online and offline with an operator command utility program.
Defining BFL volume to the TCDB
About this task
It is required to define a BFL volume in the TCDB if you are going to use MTL drive in Command Processors Procedures. For example, if you are going to run CP601, BFL601 volume is used by default to keep Command Processor output (you can use
CMD2 parameter to change default volser name, see Command Processor parameters used in procedures
).
Steps
1. To define a BFL volume to the TCDB, use the following JCL sample:
//JOBNAME JOB (MYJOB)
// EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
CREATE VOLUMEENTRY ( -
NAME (V BFLxxx ) -
LIBRARYNAME ( LIBNAME ) -
STORAGEGROUP ( STGRPNAME ) -
USEATTRIBUTE(PRIVATE) MEDIATYPE( MEDIAx ) LOCATION(LIBRARY) -
NOCHECKPOINT COMPACTION(YES) RECORDING( xxxTRACK ))
2. In the JCL sample mentioned above, replace the following:
● BFLxxx with the actual BFL volume name
● LIBNAME with the actual library name
● STGRPNAME with the actual storage group name
● MEDIAx with the actual media type of the volume
● xxxTRACK with the actual tape recording technology
3. The following is an example of defining BFL volume to TCDB:
//JOBNAME JOB (MYJOB)
// EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
CREATE VOLUMEENTRY ( -
NAME (V BFL601 ) -
LIBRARYNAME ( DLM020 ) -
STORAGEGROUP ( DLM020 ) -
USEATTRIBUTE(PRIVATE) MEDIATYPE( MEDIA4 ) LOCATION(LIBRARY) -
NOCHECKPOINT COMPACTION(YES) RECORDING( 128TRACK ))
DLMTRPT: z/OS Catalog and DLm repository matching report procedure
This section provides an overview of z/OS Catalog and DLm repository matching report procedure.
About this task
Follow this procedure for the DLMTRPT zOS Catalog and DLm Tape repository to produce the following reports:
● Cataloged DLm Tape Volumes
● Uncataloged DLm Tape Volumes
● Cataloged Non-DLm Tape Volumes
Command Processor Procedures 145
DLMTRPT produces each report to the separate DD:
● RPTMATCH DD for Cataloged DLm Tape Volumes
● RPTCAT DD for Uncataloged DLm Tape Volumes
● RPTDLM DD for Cataloged Non-DLm Tape Volumes
By default, the RPTMATCH DD associated with SYSOUT=*, RPTCAT and RPTDLM DDs with DD DUMMY. As a result, only the
Cataloged DLm Tape Volumes report is generated.
To generate other reports RPTCAT and/or RPTDLM DD on DLMCPR1 step have to be overridden.
//DLMCPR1.RPTCAT DD SYSOUT=
//DLMCPR1.RPTDLM DD SYSOUT=*
To run the DLMTRPT procedure, you must:
Steps
1. Run the CP503 Command Processor.
2. Save the output report to a dataset.
3. Specify this DSN name as CP503DSN parameter of DLMTRPT procedure.
4. Use the following DLMTRPT procedure parameters:
● CSIKEY: A CSI generic filter key. It is a 44-character string that describes the catalog entry names for which you want information that is returned. See the IBM DFSMS Managing Catalogs; Catalog Search Interface User’s Guide, and
Selection Criteria Fields for more information. Default is '**'.
● CP503DSN: This is the name of the CP503 Command Processor output report dataset that is passed to the DLMTRPT for processing and report creation.
● REXXLIB: This parameter specifies the library where the DLMCPCI, DLMCPEX, DLMCPMA, and DLMCPR1 REXX programs are stored. It is expected that this parameter is initially set in the DLMTRPT procedure when the DLm product is installed and overridden if/when a different REXX library is to be used.
● DEBUG: This parameter is used for debugging output. Valid values are:
○ All
○ Commands
○ Error
○ Failure
○ Intermediates
○ Labels
○ Off
○ Results
○ Scan
Values can be specified with only the first character. For example, DEBUG=INTERMEDIATES and DEBUG=I are equivalent.
See the IBM REXX Reference Guide TRACE command for more information about the meaning of the above DEBUG values.
● TUNIT: This parameter is supplied into JCL UNIT parameter for temporary datasets. See the IBM JCL Reference Guide
UNIT parameter more information. Default is 'SYSALLDA'.
● TSPACE: This parameter is supplied into JCL SPACE parameter for temporary datasets. See the IBM JCL Reference
Guide SPACE parameter more information. Default is '(CYL,(30,30))'.
Example
Example 1 Run CP503 and produce default DLMTRPT report:
//C503 EXEC DLMCMDPR,CMD=503,UNIT=/unit1,UNIT2=unit2,
// PATH='/tapelib',TLIB='/tapelib'
//STEP4.PRINT DD DSN=USER.C503.PRINT,DISP=SHR
//GO EXEC DLMTRPT,CSIKEY='**',CP503DSN='USER.C503.PRINT'
Tape volumes that are present on DLm and in z/OS Catalog is listed in the RPTMATCH DD.
146 Command Processor Procedures
Example 2 Produce all 3 DLMTRPT reports with existing CP503 output and catalogued datasets with ‘USER’ HLQ:
//GO EXEC DLMTRPT,CSIKEY='USER.*',CP503DSN='USER.C503.PRINT'
//DLMCPR1.RPTCAT DD SYSOUT=*
//DLMCPR1.RPTDLM DD SYSOUT=*
Results:
● Tape volumes that present on DLm and in z/OS Catalog are listed in the RPTMATCH DD.
● Tape volumes that present in z/OS Catalog, but not on DLm are listed in the RPTCAT DD.
● Tape volumes that present on DLm only are listed in the RPTDLM DD.
Command Processor parameters used in procedures
This section provides an overview of Command Processor parameters.
The following are the Command Processor parameters that are commonly used in procedures:
● UNIT: This specifies the DLm Unit to be used to obtain a Command Processor's output. When using the DLMCMDPR procedure, it is important that the Unit value points to the same DLm VTE as the UNIT2 parameter. The UNIT2 parameter is used to send a Command Processor command to the DLm for processing. The output of the Command Processor is stored on a local folder within the VTE. As a result, the UNIT and UNIT2 point to the same Virtual Tape Controller (VTE).
The UNIT parameter can be specified as an esoteric Unit name or a specific Unit number. Here are some examples of valid specifications:
UNIT=DLM43XX
UNIT=/4308
UNIT=(/4400,,,SMSHONOR)
UNIT=(/C600,,DEFER) [only for DLMCMD49,DLMCMDP1,GENSTAT1]
NOTE: Separate parameter SMSHNR should be used for specifying SMSHONOR option in the DLMCPRUN procedure.
In the first example above, an esoteric unit name is used that specifies a range of Units from 4300-43FF. In the second example a specific Unit, (4308), is specified. In the third example, a specific unit is also selected but the unit is in an MTL.
The advantage of the esoteric unit name is that a Unit can be allocated from a range of Units. When using an esoteric unit name for the UNIT parameter, ensure that all Units within the esoteric unit name point to the same VTE and are defined to have the same Mount Point. In the fourth example, the DEFER parameter is used. It allows you to save scratch tapes.
NOTE: Ensure that the Unit specified or at least one Unit for an esoteric unit name is online.
● UNIT2: This specifies the DLm Unit to be used to send a Command Processor command to the DLm. The UNIT2 parameter must specify a specific Unit and that Unit should be offline. The Unit that is specified for UNIT2 must be synchronized with the UNIT parameter. The Unit number should not contain a slash. Example: UNIT2=750F.
NOTE: The SMSHONOR clause is not supported for the UNIT2 parameter. See the above description of the UNIT parameter for more information. If the Unit specified by UNIT2 is not offline, then message DLC182I is issued and processing terminates with either a non-zero condition code or an abend.
● CMD: This parameter specifies the Command Processor to be started.
502
503
504
601
Table 48. Available Command Processors
Value
499
501
Description
Batch diagnostic aid for component responsiveness
Run Virtual Tape Operator command
Collect Virtual Tape Controller Logs
Tape Volume Library Report
VNX Replication Report
Data Domain and PowerProtect System Utilization Report
(Not supported on DLm2500)
Command Processor Procedures 147
Table 48. Available Command Processors (continued)
Value
602
Description
Data Domain and PowerProtect Deduplication Report (Not supported on DLm2500)
603
988
Data Domain and PowerProtect Replication Report (Not supported on DLm2500)
[For DLm 4.5.3 and later and DLm 5.x] DLm File System
Activity Statistics.
989 [For DLm 4.5.3 and later and DLm 5.x] DLm VTE Activity
Statistics.
998 [For DLm 4.x only] DLm File System Activity Statistics.
999 [For DLm 4.x only] DLm VTE Activity Statistics.
● PATH: When this parameter is not specified, the DLMCMDPx procedures locates and use the correct folder for the
DLm UNIT parameter. If overridden, this parameter must point to the same VTE and mount point of the UNIT and UNIT2 parameters. See the above discussion on the UNIT parameter for more information about this requirement.
● CMD2: The Command Processor output is stored in DLm in a volume with a VOLSER that begins with BFL.
For example, the output from executing Command Processor 502 (CMD=502) is stored in DLm as volume BFL502. If the CMD2 parameter is specified, its value is used in the volume label (volser). For example, specifying CMD2=ABC results in a volser
BFLABC.
● FLATDSN: The Command Processor output is stored in DLm in a file. By default the name of that file begins with BFL and ends with .FLAT.
For example, the output from executing Command Processor 502 (CMD=502) is stored in DLm in the file BFL502.FLAT. If the FLATDSN parameter is specified, its value is used as the file name. For example, specifying
FLATDSN=ABC.FLAT results in a file named ABC.FLAT.
● WAIT: The z/OS job that is executing the Command Processor waits while the Command Processor is executing on the
DLm. This parameter allows for a maximum wait time to be specified. The default is 600 seconds. If the Wait state time exceeds a z/OS maximum wait time for an IO to complete, the Unit that is specified in the UNIT parameter becomes Boxed.
If this happens, the Unit should be brought back Online to be usable.
● BTILIB: This parameter specifies the load library where the DLMCMD executable is stored. It is expected that this parameter will be initially set in the Command Processors PROCs when the DLm product is installed and overridden if/when a different load library is to be used.
● REXXLIB: This parameter specifies the library where the DLMBUILD, DLMPARM, DLMCMD1, DLMCMD2, and DLMCMD3
REXX programs are stored. It is expected that this parameter will be initially set in the Command Processors PROCs procedures when the DLm product is installed and overridden if/when a different REXX library is to be used.
There is a step at the end of the PROC which allows the user to create a customized WTO and MSGID, Error Message Text, and Return Code between 0000 - 9999.
NOTE: DLMCPRUN procedure does not support this and the following three parameters.
● WTOID: This parameter is a message ID defined as per the users discretion. The default value is ‘DLM8888E’.
● WTOTXT: This parameter is the text of the WTO message and is defined as per the users discretion. The default value is ‘An
ERROR Has Occurred in last step’.
● XRC: is the completion code that is desired for the WTO step between 0000-9999. The default value is ‘0012’.
DLMCPRUN Procedure
This section provides an overview of DLMCPRUN procedure.
The DLMCPRUN procedure is used to run command processors. The listing for the DLMCPRUN procedure can be found in the
SAMPLIBC PDS.
Non-CP specific parameters used in DLMCPRUN procedure:
● UNIT: Specifies the DLm Unit to be used to send a Command Processor command to the DLm and to obtain a Command
Processor's output. The UNIT parameter can be specified as an esoteric unit name or a specific Unit ID. Here are some examples of valid specifications:
○ UNIT=DLM8AXX
○ UNIT=/8A00
148 Command Processor Procedures
○ In the first example above, an esoteric unit name is used that specifies a range of units: 8A00-8AFF. In the second example a specific unit, (8A00), is specified.
○ Ensure that the unit specified or at least one unit for an esoteric unit name is online.
● SMSHNR: Allows unit allocation to be honored.
○ Example: SMSHNR=SMSHONOR.
● FLATDISP: Configurable DISP for FLAT file (default value is NEW). If you are using MTL device, then it should be OLD.
Example: FLATDISP=OLD.
● CMD: This parameter specifies the Command Processor to be run. Available Command Processors are:
○ 499
○ 501
○ 502
○ 503
○ 504
○ 601
○ 602
○ 603
○ 988
○ 989
Other non-CP specific parameters that are used in DLMCPRUN procedure are the same as those in
DLMCPJ1 is a sample JCL to run DLm Command Processors using DLMCPRUN.
DLMCMDPR, DLMCMDP1 and DLMCMD49 Procedures
These procedures simplify Command Processor usage by providing clearly defined parameters to be specified along with default values.
The DLMCMDPR and DLMCMDP1 procedures are identical except for the usage of DLm units. The DLMCMDP1 procedure only uses one DLm Unit which must be online. This is the preferred procedure but is slightly slower than the DLMCMDPR procedure.
The DLMCMD49 procedure is used to ping the DLm components that are attached to the respective VTE. It is used as a batch component testing function.
Parameters
This section provides an overview of parameters.
See the following sections for Command Processor parameters:
●
For non-CP-specific parameters: See Command Processor parameters used in procedures
●
For CP-specific parameters: See Using Command Processors
.
Procedure listings
The Listing for DLMCMDP1/R and DLMCMD49 procedures can be found in SAMPLIBC PDS.
JCL samples
The JCL samples are available in SAMPLIBC.xmi file in the DLm-Mainframe-Utilities-<version>.zip package on the Dell Online
Support Site.
See the JCL samples provided in the following sections:
●
●
Obtaining DLm Log Information: CP502
●
●
Command Processor Procedures 149
●
NOTE: See the $INDEX member of the sample JCL library for a description of each sample.
Running GENSTATS
This section provides an overview of running GENSTATS.
The GENSTATS reports can be created by running any of the three sets of procedures that are listed in the following table:
Table 49. GENSTATS procedure to create reports
Procedure Name Sample JCL
GENSTATP GENJCL1
GENSTAT1
GENSTATW and GENSTATR
GENJCL2
GENJCL3
Description
This procedure runs the standard
GENSTATS Proc with standard use of 2 tapes (1 online and 1 offline).
This procedure uses a single tape drive (this can be used for an MTL environment by invoking the SMSHONOR parameter).
This breaks the GENSTATS procedure into a data extract procedure and a data reporting procedure ( GENSTATW , for write the extract file and GENSTATR for read the extract file and create the GENSTATS report). This enables the user to create a single extract file and run multiple reports against it, saving time by creating the extract file only once.
GENSTATP Procedure
The GENSTATP procedure simplifies GENSTATS usage by providing clearly defined parameters to be specified along with default values.
Using the GENSTATP procedure has the following advantages:
● Some GENSTATS parameters require changes to multiple places in the JCL. This can be avoided by using the GENSTATP procedure which also provides clearly defined values for each parameter.
● Typical JCL streams using the GENSTATP procedure require only 1 or 2 JCL statements.
● The GENSTATP procedure builds the GENSTATS syntax and ensures that the output received from the DLm matches the command that sent to the DLm. This is done by passing a unique timestamp along with the command that sent to the DLm that is validated in the output response.
● Use of the GENSTATP procedure allows for installation wide parameters to be specified in one place, (the GENSTATP procedure), instead of replicating multiple job streams.
● The GENSTATP procedure eliminates possible user errors because it simplifies Command Processors into clearly defined parameters.
Optional parameters
This section provides an overview of optional parameters.
● REPORT: This parameter specifies the type of GENSTATS Report requested. Valid values are THROUGHPUT, MAXTAPES,
SLOWMOUNTS, DETAIL, and STILLINUSE. If not specified, the default is THROUGHPUT. See the description of Report
Types in the
section for more information about this parameter.
150 Command Processor Procedures
● STRTMM/DD/YYYY: This parameter excludes GENSTATS data before a given start date. This parameter is in the format of
Month, Day, Year. That is, MM/DD/YYYY. For example:
STRTMM='11'
STRTDD='15'
STRTYYYY='2013'
● ENDMM/DD/YYYY: This parameter excludes GENSTATS data to a given end date. This parameter is in the format of Month,
Day, Year. That is, MM/DD/YYYY. For example:
ENDMM='12'
ENDDD='03'
ENDYYYY='2013
● VMASK: This filter allows you to specify a mask for the vstats files. For example, on the following statement: my
@vstat_list=`find $FindVPath -group vtape -name .vstats.$VMask 2> /tmp/err998.$pid | sort
-u `; . The VMASK filter used for the $VMask variable above defaults to '*'. Users can specify a different mask.
● VDEPTH: This filter specifies a maximum depth of folders. For example, setting this value to 4 will only allow.vstats files that are direct subfolders of the /tapelib folder.
GENSTAT1 Procedure
This section provides an overview of the GENSTAT1 procedure.
The GENSTAT1 utility enables the user to generate statistics reports that summarize DLM virtual tape activity. The GENSTAT1
PROC is identical to the GENSTATP PROC, except it only requires one DLm unit, which must be online.
Run the GENSTATS report using a single DLm unit during execution.
NOTE: GENSTAT1 has the same parameters and creates the same outputs as GENSTATP . The only difference is that it uses a single UNIT parameter.
All GENTATS report outputs are the same and consistent for all versions of the GENSTAT procedures.
Handling large quantities of statistics
This section provides an overview of handling large quantities of statistics.
The GENSTATP, GENSTAT1, and GENSTATW PROCs write DLm statistics information to a temporary disk dataset. This dataset has the following SPACE parameter:
SPACE=(CYL,(50,50))
When processing large amounts of statistics information, either of the following actions must be taken:
● The space parameter must be overridden.
● The statistics data must be redirected to a DLm tape volume.
The following is an example of redirecting the intermediate statistics file to a DLm tape volume:
//GO1 EXEC GENSTAT1,CMD=998,UNIT=/F200,
// REPORT='THROUGHPUT'
//STEP4.PRINT DD DSN=&STATFILE,UNIT=/F201,DISP=(NEW,PASS)
In the example above, the STEP4.PRINT DD is being overridden to store the temporary dataset that is called &STATFILE on a
DLm tape volume using the DLm unit F201.
Also, the STEP4.PRINT DD can be overridden to allocate more DASD for the statistics dataset.
Command Processor Procedures 151
GENSTATW/R Procedure
This section provides an overview of GENSTATW/R procedure.
The GENSTATS processing can be separated using the GENSTATW and GENSTATR PROCS to form an extract and process set of procedures.
The GENSTATW and GENSTATR procedures give the user the flexibility to create the data that are needed to generate multiple reports concurrently. This saves the user’s time, space, and cycles. For instance, when this is run as a single process, each report is considered as a single job stream, and the statistics data had to be created each time. The GENSTATW and
GENSTATR PROCs procedures enable you to extract the statistics data only once.
GENSTATW Procedure
This section provides an overview of GENSTATW procedure.
GENSTATW uses the same parameters as GENSTATP with the following additions:
● RPTDSN - This is the name of the extract report dataset that is passed to the GENSTATR for processing and report creation.
● UNIT3 : It is used to store the report extract dataset to be used by GENSTATR .
● DISP1 = This is the report dataset extract file disposition. The default is (NEW,CATLG,DELETE).
Use the GENSTATW procedure to write the statistics file.
Handling large quantities of statistics
This section provides an overview of handling large quantities of statistics.
The GENSTATW PROC writes DLm statistics information to a temporary disk dataset. This dataset has the following SPACE parameter:
SPACE=(CYL,(50,50))
While processing large amounts of statistics information, either of the following actions must be taken:
● The space parameter must be overridden.
● The statistics data must be redirected to a DLm tape volume.
The following is an example of redirecting the intermediate statistics file to a DLm tape volume:
//GO1WR EXEC GENSTATW,CMD=998,UNIT=/F200,UNIT2='F203',
// UNIT3='/F201',RPTDSN=RGREEN7.D150210.STATFILE
In the example above, the UNIT3 parameter is used to specify a DLm unit to store the RGREEN7.D140210.STATFILE dataset on a DLm tape volume.
GENSTATR Procedure
This section provides an overview of GENSTATR procedure.
The GENSTATR procedure is used to report on the data extracted. The additional parameters are:
● REPORT - The GENSTATS report you want to run. The default is THROUGHPUT .
● RPTDSN - The extract report dataset created by GENSTATW .
● UNIT3 - The same unit that the report extract was created on in the GENSTATW run.
● DISP1 - Disposition for the report extract dataset. The default is SHR .
All GENSTATS report outputs are the same and consistent for all versions of the GENSTAT procedures.
152 Command Processor Procedures
7
Command Processor SAMPLIBC Members
This chapter introduces the different Command Processors.
Topics:
•
•
Command Processor sample JCL streams
SAMPLIBC sample JCL members
The installed SAMPLIBC PDS contains sample JCL and PROCs for Command Processor usage.
Some of these members have already been discussed in
Command Processor Procedures . The member $INDEXC contains an
index of the SAMPLIBC members with a description of their use.
After installation, the PROCs should either be moved to a common PROCLIB or should have a JCLLIB statement that is placed in each Command Processor Job Stream. Below is a sample JCLLIB statement pointing to the PDS containing the installed
Command Processor procedures:
//LIB JCLLIB ORDER=EMC.CP400.PROCLIB
After placing it in the PROCs in the common PROCLIB, there are common parameter replacements that help to avoid specifying them in individual Job Streams. Below is a list of the possible replacements:
● BTILIB: Installed Link Library containing the DLm utilities such as DLMCMD .
● REXXLIB: Installed REXX Library containing the REXX programs that are used by Command Processors.
Below is a list of the Command Processor Procedures:
● DLMCMDPR: Sample procedure to run DLm Command Processors.
● DLMCMDP1: Sample procedure to run DLm Command Processors for single unit use.
● DLMCMD49: Sample procedure to run DLm Command Processor 499. CP499 is used to list/ping components that are attached to the VTE giving the ability for batch controlled additional diagnostic tool.
● GENSTATP: Sample procedure to run DLm GENSTATS reports.
● GENSTAT1: Sample procedure to run DLm GENSTAT1 reports for single unit use.
● GENSTATW: Sample procedure to extract DLm statistics data.
● GENSTATR: Sample procedure to run the GENSTATS DLm z/OS utility.
● DLMTRPT: Sample procedure to run Cataloged DLm Library Report.
Command Processor sample JCL streams
This section provides an overview of Command Processor sample JCL streams.
After installation, the following SAMPLIBC members should be copied to another PDS for customization. The following changes must be considered:
● Include JCLLIB statement to point to the library containing the Command Processor Procedures.
Example:
//LIB JCLLIB ORDER=EMC.CP400.PROCLIB
● Include a JOB Card that conforms to the installation standards.
● Specify any procedure specific parameters. See the
for more information.
Below is a list of the Command Processor Sample JCL members that are contained in the SAMPLIBC library:
● DLMCPRUN: Sample procedure to run DLm Command Processors.
Command Processor SAMPLIBC Members 153
● DLMCPJ1: Sample JCL to run DLm Command Processors using DLMCPRUN .
● DLMCMDJ1: Sample JCL to run DLm Command Processors using DLMCMDPR .
● DLMCMDJ2: Sample JCL to run DLm Command Processors using IEBGENER .
● DLMCMDJ3: Sample JCL to run DLm Command Processors using DLMCMDP1 for single unit use.
● GENJCL1: Sample JCL for running GENSTATS reports using GENSTATP .
● GENJCL2: Sample JCL for running GENSTATS reports using GENSTAT1 for single unit use.
● GENJCL3: Sample JCL for running GENSTATS reports using GENSTATW and GENSTATR for processing multiple reports from a single input.
● CP499J: Sample JCL to run DLm Command Processor 499 using DLMCMD49 .
154 Command Processor SAMPLIBC Members
8
Invoke Command Processors directly with
JCL
There are a number of advantages in using the supplied procedures such as DLMCPRUN to invoke Command Processors. These include ease of use and elimination of many possible user input errors. This chapter provides a sample showing the method to invoke Command Processors directly with JCL and sample commands to execute various Command Processors.
Topics:
•
Invoking Command Processors directly with JCL
Invoking Command Processors directly with JCL
Command Processors can also be invoked with "open" JCL.
Example
The following is an example:
//JOBNAME JOB (MYJOB)
//SENDCMD EXEC PGM=DLMCMD
//STEPLIB DD DISP=SHR,DSN=USER.DLM.LINKLIB
//DLMCTRL DD UNIT=(/8A00,,DEFER)
//DLMLOG DD SYSOUT=*
//DLMCMD DD *
RUNWAIT (600) 501 "QUERY" "/tapelibTLDDRL" "BFLXXX.FLAT"
//*
//READOUT EXEC PGM=IEBGENER
//SYSUT1 DD DISP=OLD,DSN=BFLXXX.FLAT,VOL=SER=BFLXXX,UNIT=/8A00,
// DCB=(RECFM=FB,LRECL=132,BLKSIZE=132),LABEL=(,NL)
//SYSUT2 DD SYSOUT=*,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
In the JCL example above:
● Replace USER.DLM.LINKLIB with the name of the dataset where the DLMCMD load module resides.
● The tape library for the virtual tape devices that are specified above is tapelibTLDDRL. This value can be seen on the
DLmConfig Device panel in the Tape Library column for the device.
NOTE: For DLm2500, you can see this value in the DLM System Manager:
1. In the DLm System Manager , click Configuration panel.
2. Under Configuration panel, click Devices and see tapelib column for the device.
● The Command Processor command must be specified in the DLMCMD DD of the SENDCMD job step. It could be sequential dataset with the LRECL not higher than 256 or in-stream dataset (as in example above). For more information, see
.
NOTE: You cannot specify the DEFAULT value for tapelib when running a Command Processor directly with JCL. Instead, you must use a Command Processor procedure such as DLMCPRUN.
Sample output
EMC DLm VTEC Command Processor Tool (501) v5.0.3-9 Wed Jan 16 06:51:55 EST 2019
Invoke Command Processors directly with JCL 155
======================================================================
01/16/2019 06:51:56 vte1 VT: Devicename VOLSER/L
01/16/2019 06:51:56 vte1 VT: ---------- --------
01/16/2019 06:51:56 vte1 VT: 8A00 NR-A2
01/16/2019 06:51:56 vte1 VT: 8A01 NR-A2
01/16/2019 06:51:56 vte1 VT: 8A02 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A03 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A04 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A05 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A06 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A07 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A08 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A09 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0A NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0B NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0C NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0D NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0E NR-UA
01/16/2019 06:51:56 vte1 VT: 8A0F NR-UA
01/16/2019 06:51:56 vte1 VT: 8A10 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A11 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A12 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A13 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A14 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A15 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A16 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A17 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A18 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A19 NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1A NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1B NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1C NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1D NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1E NR-UA
01/16/2019 06:51:56 vte1 VT: 8A1F NR-UA
======================================================================
156 Invoke Command Processors directly with JCL
A
Troubleshooting Command Processors
This appendix provides troubleshooting information for command processors.
Topics:
•
Troubleshooting Command Processors
•
•
•
How to terminate the Command Processor process
Troubleshooting Command Processors
DLm Command Processor processing is composed of both mainframe and DLm.
This chapter contains the following topics:
●
●
●
How to terminate the Command Processor process
Command Processor framework
The DLm utility DLMCMD is used to send a request to run a Command Processor script on the DLm. DLMCMD uses a DLm
Virtual Tape Drive unit to send the request to Virtuent on a DLm Virtual Tape Engine (VTE). Virtuent then invokes the specified
Command Processor on the VTE and passes it the parameters that are specified in the request.
Typically, the Command Processor script that runs on the DLm receives input parameters that specify where to place its output.
This is typically an output file whose name is in the format of BFLxxx.FLAT.
Typically, Command Processing mainframe processing includes a job step where the output from a Command Processor is retrieved. This is done by reading the BFLxxx.FLAT file referred to above. Special logic in Virtuent allows for reading these
‘FLAT’ files when a DD statement includes a DSN of BFLxxx.FLAT and a VOLSER of BFLxxx.
In the above framework, there are few possible trouble spots:
● Communication errors and failures while sending Command Processor requests to the DLm.
● Command Processor script failures while executing on the DLm.
● User parameter errors.
● Failures to obtain Command Processor outputs.
DLm Command Processors include PROCs that include special processing to ensure that any errors from the above trouble spots are detected. These PROCs are DLMCPRUN, DLMCMDP1, DLMCMDPR, GENSTATP, GENSTAT1, GENSTATW, and
DLMCMD49. Information about these PROCs is contained elsewhere in this manual. However, each of these PROCs contains the following features that ensure that Command Processor failures are detected:
● Each Command Processor request sent to the DLm contains a unique token that is matched against the Command
Processor output.
● Special processing is provided to ensure that the location for the Command Processor output is correct.
● Mainframe edit processing is performed on input user edits before being sent to the DLm.
You can invoke Command Processors directly if you do not want to use the above PROCs. See
Invoking Command Processors directly with JCL
.
Troubleshooting Command Processors 157
What to do if errors occur
The following sections describe the steps to perform when an error does occur.
z/OS-based verifications
If a Command Processor job failed then look through all the output for any error messages. Besides, any communication problems might be indicated in the DLMLOG DD output that is created in the job step which executes the DLm z/OS utility
DLMCMD.
DLMLOG output
This section provides an overview of DLMLOG output.
Within the job output for the failing job, the DLMLOG DD contains a log of the DLMCMD processing. When an error has been returned by Virtuent, the error code is displayed as ERR=xx, where the xx is the error code.
Table 50. DLMLOG Output Error Codes
Error Code
FF
FC
FB
Description
Unknown command or a command with invalid or wrong parameters passed.
Corrective Action
Specify a correct Command Processor number and/or fix parameter list.
Error encountered executing command.
Locate error in btilog and correct it.
Note: The btilog can be found on the
VTE of the DLm.
Script did not complete within time that is specified.
Increase the RUNWAIT seconds.
Example:
This section provides some examples.
In the following example, the GENSTATP PROC is used to generate a Slow Mounts report but fails in the job step which invokes the DLm Command Processor. This failure occurs because the Command Processor script did not complete within the specified number of seconds, which is defaulted to 600 seconds.
The following is the example JCL for the failing job:
//GO1 EXEC GENSTATP,CMD=998,UNIT=/F200,UNIT2=F201, X
// REPORT='SLOWMOUNTS=5'
The following is example output:
DLMCMD VER 4.12 DLMCTRL = F201
2015/09/02 13:13:44 CMD ERR=FB: RUNWAIT (600) 998 "DEFAULT" "BFL998.FLAT"
"startdate=01/01/2000" "enddate=01/01/2099" "20150902-13
2015/09/02 13:13:44 cont'd: 13:43-12072"
To resolve the above problem, the GENSTATP job step could be changed to increase the number of seconds to wait with the
WAIT parameter. Here is an example of this with the changes in bold:
//GO1 EXEC GENSTATP,CMD=998,UNIT=/F200,UNIT2=F201, X
// REPORT='SLOWMOUNTS=5', WAIT=1200
158 Troubleshooting Command Processors
DLm-based verifications
This section provides an overview of DLm-based verifications.
If a Command Processor failure occurred during processing on the DLm, there are few files where error information can be found. The Command Processor output report must be reviewed for possible error messages. Below are some possible locations for error information about the DLm:
VTCon output
Current Virtuent output can be obtained from the Virtuent Console.
This console output can be viewed in a CLI session on the VTE by entering vtcon at the command line or by clicking the Console push button on the DLmConsole Status panel.
NOTE: DLmConsole has been replaced by the DLm System Manager from DLm 5.2 and later.
For DLm2500, you can view Virtuent console output using the following method:
1. In the DLm System Manager , click System panel.
2. Under System panel, click Command Interface .
In the Command Interface panel, in the Virtuent console on VTE1 window, you can view the Virtuent console output.
Message logs
This section provides an overview of message logs.
The /var/log/bti/btilog file on the VTE can be viewed for any Virtuent messages that have occurred. Below is an example message that can be found:
DLm556E RUNWAIT process #xx has not finished in nn seconds
NOTE: With regards to the above message, even though the RUNWAIT may time out, the Command Processor script will still run to completion.
Also, Command Processor messages can be found in the /var/log/dlmtools/dlmcplog file. For DLm 4.x, Command
Processors messages can be found in the /var/log/messages file.
Both of the above message logs can be retrieved using the DLmConsole System Status panel Log push button, and the
DLmConsole Gather panel Gather push button.
NOTE: DLmConsole is replaced by the DLm System Manager from DLm 5.2 and later.
For DLm2500, you can retrieve both the above message logs using the following methods:
For DLm:
1. In the DLm System Manager , click System panel.
2. In the Dashboard panel, under the Components list, click DLM .
NOTE: Dashboard is the default page that you see after login to DLm System Manager.
3. In the DLm panel, click Logs .
4. Click COLLECT button to collect the logs or click
For the specific VTE:
to download the logs for DLm.
1. In the DLm System Manager , click System panel.
2. In the Dashboard panel, under the Components list, click VTE1 .
NOTE: Dashboard is the default page that you see after login to DLm System Manager.
3. In VTE1 panel, click Logs .
4. Click COLLECT button to collect the logs or click to download the logs for the specific VTE.
Troubleshooting Command Processors 159
How to terminate the Command Processor process
When a RUNWAIT command to run a Command Processor has timed out, it may be necessary to terminate the associated
Command Processor thread(s) that are still running on the VTE.
About this task
The following commands require that you have established a CLI session on that VTE:
Steps
1. Check to see if the command processor is running: vte1:~ # ps -ef|grep script502 root 70833 56032 1 08:49 pts/5 00:00:00 script502 502 "L1" "2" "DEFAULT"
"BFL502.FLAT 20150731-14:50:50-57843 root 70916 58966 0 08:49 pts/7 00:00:00 grep script502
In the example above, there is one process executing Command Processor 502. Its process ID is 70833.
2. Issue the following command to kill the above Command Processor process: kill -9 70833
Communication verifications
This section provides an overview of communication verifications.
As described earlier in this section, Command Processor commands are sent from z/OS using the DLm z/OS Utility DLMCMD through the FICON channel attached to the DLm VTE.
This is done using the UNIT (or UNIT2 for some PROCs) parameter of the Command Processor PROCs. With regards to these
DLm Units:
● When using both the UNIT and UNIT2 parameters, ensure that the DLm Units are attached to the same VTE. Command
Processors store their report output on local storage on the VTE. As a result, if the DLm Unit that is specified for the
UNIT parameter is attached to one VTE while the DLm Unit specified for the UNIT2 parameter is attached to a different
VTE, the Command Processor fails because it cannot locate the correct output report. When using an esoteric for the UNIT parameter, ensure that the esoteric only includes DLm Units for the correct VTE.
● Ensure that the following Command Processors are run on the correct VTE. For example, Command Processor 501 issues
VTE commands. As a result, you must ensure that you are running this Command Processor on the VTE that is to run the
VTE command.
●
Table 51. VTE-oriented command processors
Command Processor Description
499 Perform diagnostics
501
502
989
999
Run VTE command
Obtain logs
Obtain VTE activity statistics in DLm 4.5.3 and later and
DLm 5.x
Obtain VTE activity statistics in DLm 4.x only
NOTE: Command Processor 503 (Virtual Tape Volume Information), may include local files for a VTE in its report. These files may include Command Processor output report files from previous Command Processor executions.
● When the UNIT2 parameter is used, ensure that this DLm Unit is offline. Bringing it online first, then offline ensures that a path to the VTE has been established.
Ensure that the DLm Unit that is specified in the UNIT parameter is online.
160 Troubleshooting Command Processors
B
Downloading and Installing DLm Mainframe
Utilities for z/OS
This appendix provides information on how to install DLm Mainframe Utilities for z/OS using SMP/E and non-SMP/E installation methods.
Topics:
•
Downloading and using DLm z/OS components
•
Installing DLm Utilities using the SMP/E method
•
•
Installing DLm Utilities using the non-SMP/E method
•
Downloading and using DLm z/OS components
This section provides an overview of downloading and using DLm z/OS components.
There are two installation procedures for DLm Mainframe Utilities for z/OS, using the DLm downloadable files designed for an
SMP/E install. This chapter contains the following procedures:
●
Installing DLm Utilities using the SMP/E method
●
Installing DLm Utilities using the non-SMP/E method
Installing DLm Utilities using the SMP/E method
This section provides an overview of installing DLm utilities using the SMP/E method.
Introduction
DLm supports SMP/E-based installation procedures for DLm Utilities for z/OS.
NOTE: In this section, x.y.z is used to denote the release number. For example, for DLm Mainframe Utilities SMP/E release
DLMS500, x.y.z refers 5.0.0 and xyz refers to 500.
The DLm kit consists of a flattened file (DLMSxyz.xmitfile) that contains a PDS of TSO TRANSMIT images of files, and the JCL needed to perform an SMP/E indirect-library installation on the product.
The PDS is packaged as a TSO TRANSMIT file on a CD or in an open systems .zip file, DLMSxyz.zip, for an electronic download from the Downloads section of Dell Online Support.
Also included on the CD, or within the .zip file, is a ReadMe_DLMSxyz.txt text file which contains installation instructions.
Installing DLm Utilities using the SMP/E method
This section provides an overview of installing DLm utilities using the SMP/E method.
About this task
Follow the installation procedure:
Downloading and Installing DLm Mainframe Utilities for z/OS 161
Steps
1. Load DLMSxyz.XMITLIB to disk.
2. Prepare DLMSxyz.XMITLIB(#EXTRACT).
3. Customize the RIMLIB JCL.
4. Run the installation jobs.
5. Perform cleanup.
6. Apply maintenance.
7. Shut down and restart DLMHOST.
Loading DLMSxyz.XMITLIB to disk
This section provides an overview of loading DLMSxyz.XMITLIB to disk.
Steps
1. Download the software.
If you are installing DLm from a CD: a. Mount the CD on an open systems host. The host must have FTP installed.
b. Allocate a working directory on the open system for the installation.
c. Copy the contents of the CD to that working directory.
d. Continue on to
.
Or
If you are installing DLm from the online Dell Technologies Support web page, perform the following steps: a. Log in to a privileged account on an open systems host (root on UNIX or administrator on Windows).
b. Allocate a working directory on the open system for the installation.
c. Log on to the Dell Technologies Support home page https://www.dell.com/support/ .
d. Click Downloads . In the Find a Product field , type Disk Library for mainframe immediately followed by the applicable DLm model (for example, "DLm2100," "DLm8100," and so on) for which you are searching. Select the text that automatically displays for the appropriate DLm model and click the Search button.
e. Click DLm Mainframe Utilities SMP/E (DLMSxyz) to download. This .zip file contains the installation kit and the installation instructions.
f. Download the installation kit into the working directory that you selected above.
g. Continue on to
.
2. If your current host is a Windows system, extract the file in the working directory. If your current host is a UNIX system, extract and untar the file in the working directory.
3. Locate the DLMSxyz.XMITFILE
. This file is in the TSO TRANSMIT format and contains a flattened copy of
DLMSxyz.XMITLIB
, a PDS that holds other TRANSMIT images, the JCL to extract them, and necessary SMP/E installation files.
4. On the target mainframe, allocate a file to which you can FTP the DLMSxyz.XMITFILE
. Use the Data Set name prefix that you intend to use for product installation. For example, if you intend to install the product with the recommended Data Set name prefix of EMC.DLMSxyz, name the file EMC.DLMSxyz.XMITFILE
.
5. Allocate the file with the following characteristics:
● LRECL=80
● BLKSIZE=3120 (IMPORTANT: You MUST use 3120!)
● DSORG=PS
● SPACE=(CYL,(5,2)) Assumes 3390 devices
NOTE: The SPACE parameter here and elsewhere assumes that you are allocating the dataset on a 3390 device.
6. FTP the DLMSxyz.XMITFILE to the mainframe in binary format (as-is without translation or encoding).
Your FTP session may look similar to: ftp> binary
200 Representation type is Image ftp> put DLMS430.xmitfile 'emc.dlms430.xmitfile'
200 Port request OK.
125 Storing data set EMC.DLMS430.XMITFILE
162 Downloading and Installing DLm Mainframe Utilities for z/OS
250 Transfer completed successfully.
ftp: 1401360 bytes sent in 2.70Seconds 519.21Kbytes/sec.
ftp>
NOTE: If you use another method, such as IND$FILE, ensure that you use the equivalent of the ftp binary format.
7. Use TSO RECEIVE to receive the file into a PDS. The PDS is created by the RECEIVE command and does not have to be pre-allocated. However, you must specify a Data Set name using the DA[taset] parameter; otherwise the file is allocated using your TSO prefix (usually your logon id). Use the Data Set prefix that you intend to use for the product libraries.
Example
Menu List Mode Functions Utilities Help
------------------------------------------------------------------------------
ISPF Command Shell
Enter TSO or Workstation commands below:
===> receive INDA('EMC.DLMS430.XMITFILE')
INMR901I Dataset EMC.DLMS430.XMITLIB from LLINKE1 on NODENAME INMR906A Enter restore parameters or 'DELETE' or 'END' +
DA('EMC.DLMS430.XMITLIB')
S PAGE 1
IEBCOPY MESSAGES AND CONTROL STATEMENT
IEB1135I IEBCOPYFMID HDZ1C10SERVICE LEVEL UA56546DATED 20100830 DFSMS 01.
12.00 z/OS01.12.00 HBB7770CPU 2818
Û}
IEB1035I RGUSER7IKJACCNT IKJACCNT 10:08:19 THU 09 APR 2015 PARM='WORK=4M,SIZE
=1M'
COPY INDD=((SYS00081,R)),OUTDD=SYS00080
IEB1013I COPYING FROM PDSUINDD=SYS00081 VOL=Z1CWK9 DSN=SYS15099.T100819.RA000
.RGUSER7.R0103201
IEB1014ITO PDSOUTDD=SYS00080 VOL=W54753 DSN=EMC.DLMS430.XMITLIB
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00081
IEB154I $$README HAS BEEN SUCCESSFULLY LOADED
IEB154I $$VERHAS BEEN SUCCESSFULLY LOADED
IEB154I #EXTRACT HAS BEEN SUCCESSFULLY LOADED
IEB154I RIMLIBHAS BEEN SUCCESSFULLY LOADED
IEB154I SETUPHAS BEEN SUCCESSFULLY LOADED
IEB154I SMPMCSHAS BEEN SUCCESSFULLY LOADED
***
IEB154I XEXELIBHAS BEEN SUCCESSFULLY LOADED IEB154I XJCLLIBHAS BEEN SUCCESSFULLY
LOADED IEB154I XMITJCLHAS BEEN SUCCESSFULLY LOADED IEB154I XMTWIN1HAS BEEN
SUCCESSFULLY LOADED IEB154I XOBJLIBHAS BEEN SUCCESSFULLY LOADED IEB154I XPNLLIBHAS
BEEN SUCCESSFULLY LOADED IEB154I XSAMLIBHAS BEEN SUCCESSFULLY LOADED
IEB1098I 13 OF 13 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00081
IEB144I THERE ARE 16 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY SYS00080
IEB149I THERE ARE 5 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
INMR001I Restore successful to dataset 'EMC.DLMS430.XMITLIB'
***
NOTE: If you did not specify "DA(…)" as above, the Data Set would be allocated as user ID.XMITLIB
.
Preparing DLMSxyz.XMITLIB (#EXTRACT)
This section provides an overview of preparing DLMSxyz.XMITLIB (#EXTRACT).
About this task
Prepare DLMSxyz.XMITLIB(#EXTRACT) to extract ds-prefix.RIMLIB and the SMP/E indirect libraries by completing the following steps:
Steps
1. Edit the #EXTRACT member of the newly RECEIVED library. You can edit the #EXTRACT job by running the SETUP REXX program in the XMITLIB Data Set. The SETUP REXX program prompts you for all the information that is needed to edit the
JOB.
Downloading and Installing DLm Mainframe Utilities for z/OS 163
For example:
Menu Functions Confirm Utilities Help
------------------------------------------------------------------------------
DSLIST EMC.DLMS430.XMITLIB Row 00001 of 00013
Command ===> Scroll ===> CSR
Name Prompt Size Created Changed ID
________ $$README 287 2006/08/31 2015/02/11 11:09:02 DLMS430
________ $$VER 1 2010/11/11 2015/02/11 11:09:23 DLMS430
________ #EXTRACT 103 2015/02/11 2015/02/11 14:28:15 DLMS430
________ RIMLIB 1441 2015/02/11 2015/02/11 14:28:15 DLMS430
EX______ SETUP 21 2015/02/11 2015/02/11 14:28:15 DLMS430
________ SMPMCS 131 2015/02/11 2015/02/11 14:28:15 DLMS430
________ XEXELIB 9702 2015/02/11 2015/02/11 14:28:15 DLMS430
________ XJCLLIB 82 2015/02/11 2015/02/11 14:28:15 DLMS430
________ XMITJCL 254 2006/08/31 2014/06/10 16:32:28 DLMS430
________ XMTWIN1 48 2006/08/31 2015/02/11 11:17:39 DLMS430
________ XOBJLIB 1667 2015/02/11 2015/02/11 14:28:15 DLMS430
________ XPNLLIB 1258 2015/02/11 2015/02/11 14:28:15 DLMS430
________ XSAMLIB 2278 2015/02/11 2015/02/11 14:28:15 DLMS430
**End**
In the above example, the received dataset is listed in an ISPF 3.4 member list, EX has been entered next to the SETUP member, and Enter is pressed. The following is a sample of the SETUP Customization panel:
+---------------------- EMC JCL Customization Utility ----------------------+
| COMMAND ==> _________________________________________________________|
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library ==> 'EMC.DLMS430.XMITLIB'|
| Edit macro name ==> XMIT|
| XMITLIB dsname prefix ==> EMC.DLMS430|
| |
| |
| Install-to disk volser==> ________ Disk unit name ==> SYSDA|
|
| Enter your job card below ('%MEMBER%' will be replaced by member name):|
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1)|
+---------------------------------------------------------------------------+
2. Specify the job card and install-to VOLSER and change any defaults as required. Then press Enter to update the #EXTRACT member with the correct JCL customization.
3. To edit the #EXTRACT manually, make the following changes: a. Change the job card to one that conforms to your standards.
b. Globally change ds-prefix to the Data Set prefix of this library (to be the Data Set prefix for the product libraries).
c. Globally change DVOL to a disk VOLSER that can be used to hold the extracted libraries.
d. Globally change DISK-UNIT to a site-appropriate unit name.
4. Submit #EXTRACT. All step completion codes must be 0, except for the DELETE step, which has a step completion code of
8, unless the job is a rerun. The #EXTRACT JOB creates all the data sets needed to do an SMP/E install.
Customizing the RIMLIB JCL
This section provides an overview of customizing the RIMLIB JCL.
About this task
Continue the installation process by editing the JCL in the RIMLIB created by the #EXTRACT JOB .
Table 52. RIMLIB File Contents
Contents
#01ALLOC
#02DDDEF
Description
Allocates product datasets
Adds required DDDEF and other required UCLIN to SMP/E
CSI
164 Downloading and Installing DLm Mainframe Utilities for z/OS
Table 52. RIMLIB File Contents (continued)
Contents
#03RECEV
#04APPLY
#05ACCPT
#06CLEAN
#99MAINT
SETUP
DLMJCL
DLMWIN1
Description
Receives DLm x.y.z function
Applies DLm x.y.z function
Accepts DLm x.y.z function
Deletes indirect libraries and DDDEFs used for them
A sample file for SMP/E RECEIVE and APPLY service
REXX to simplify the customization process
JCL customization dialog driver
JCL customization dialog data entry panel
The RIMLIB library (ds-prefix.RIMLIB) is a PDS containing JCL to install the product. After you have extracted the RIMLIB PDS,
RIMLIB has the contents that are shown in the table above.
NOTE: The RIMLIB dataset also includes a $$README member with includes installation instructions.
NOTE: Dell Technologies strongly suggests that you use the DLMJCL utility, contained in the RIMLIB dataset to perform this task. However, if you prefer to do it manually, see the $$README member for manual editing instructions.
To customize the installation JCL using the DLMJCL utility with SETUP REXX, follow these steps:
Steps
1. While in the EDIT or BROWSE member list, use the EX command on the SETUP member and press <Enter>. A panel similar to the following is displayed:
+---------------------- EMC JCL Customization Utility ----------------------+
| COMMAND ==> |
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library==> 'EMC.DLM430.RIMLIB'|
| Edit macro name==> DLM|
| Product dsname prefix ==> EMC.DLM430|
| SMP/E dsname prefix==> EMC.SMPE|
| SMP/E datasets volser ==>
| Install-to disk volser==>
| Disk unit name ==> SYSDA|
| Enter your job card below ('%MEMBER%' will be replaced by member name):|
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1)|
+---------------------------------------------------------------------------+
2. Customize the JCL: a. The CLIST library field is set by default to the name of the RIMLIB library. This field must contain the name of a library in which you want the edit macro that is created by this dialog to be stored. The default value is fine for most users and need not be changed.
b. In the Edit macro name field, perform one of the following:
● Accept the default name displayed.
● If necessary, change the name of the edit macro.
NOTE: Normally, you should not have to change the name.
c. In the Product dsname prefix field, enter the Data Set name prefix that you want to use for the DLm target datasets. Dell
Technologies suggests EMC.fmid
.
d. In the SMP/E dsname prefix field, enter the Data Set name prefix of the SMP/E datasets into which you installed DLm
Mainframe Utilities.
e. In the SMP/E datasets volser field, enter the six-character volume serial number of the disk volume on which you want to allocate the SMP/E distribution libraries for DLm.
Downloading and Installing DLm Mainframe Utilities for z/OS 165
This volume may be the same as the volume you specify in the SMP/E dsname prefix field, or you may elect to keep these datasets on a separate volume.
f. In the Install-to disk volser field, enter the six-character volume serial number of the disk volume to which you want to install the DLm libraries.
g. In the Disk unit name field, you can specify an esoteric disk name that is appropriate to your site. SYSDA is the default, but you can overtype it with another esoteric disk name.
h. Enter a site-appropriate job card.
NOTE: NOTIFY=&SYSUID. An ampersand in the job card can cause edit-macro errors. The job card is initially set to a value that is suitable to many users. The first seven characters of the job name are set to your TSO user ID, plus
X. You can set the job name to %MEMBER%. This causes the edit macro to set each job name equal to the JCL member name Do not use any parameter that contains an ampersand (&), such as:
3. Enter the following information in the Dell Technologies JCL Customization Utility panel to customize your installation:
+---------------------- EMC JCL Customization Utility ----------------------+
| COMMAND ==> |
| |
| Type EXEC on the command line and press ENTER to proceed, or PF3 to exit. |
| |
| CLIST library==> 'EMC.DLM430.RIMLIB'|
| Edit macro name==> DLM|
| Product dsname prefix ==> EMC.DLM430|
| SMP/E dsname prefix==> EMC.SMPE|
| SMP/E datasets volser ==> DVOL01|
| Install-to disk volser==> DVOL02Disk unit name ==> SYSDA|
| |
| Enter your job card below ('%MEMBER%' will be replaced by member name):|
| => //RGREEN7X JOB MSGCLASS=A,CLASS=A,MSGLEVEL=(1,1)|
+---------------------------------------------------------------------------+
4. Type EXEC on the Command line and press Enter. You see an output similar to the following:
BUILDING AN EDIT MACRO(DLM) IN 'EMC.DLMS430.RIMLIB' Processing
Member: #U1ALLOC
Processing Member: #U2DFZON
Processing Member: #U3REPRO
Processing Member: #U4DDDEF
Processing Member: #01ALLOC
Processing Member: #02DFZON
Processing Member: #03REPRO
Processing Member: #04DDDEF
Processing Member: #05RECEV
Processing Member: #06APPLY
Processing Member: #07ACCPT
Processing Member: #08CLEAN
Processing Member: #99MAINT
***
Running the installation jobs
This section provides an overview of running the installation jobs.
About this task
Carefully examine each job before you submit it to ensure that it was customized the way that you intended. Submit the customized jobs in the following order, making sure that each job completes successfully before submitting the next one:
Follow this procedure:
Steps
1. Installing into a new SMP/E CSI: a. #01ALLOC b. #02DFZON
166 Downloading and Installing DLm Mainframe Utilities for z/OS
c. #03REPRO d. #04DDDEF e. #05RECEV f. #06APPLY g. #07ACCPT h. #08CLEAN
2. Installing into an old SMP/E CSI from a previous version of DLM or a version of DLm Mainframe Utilities: a. #U1ALLOC b. #U4DDDEF c. #05RECEV d. #06APPLY e. #07ACCPT f. #08CLEAN g. #02DFZON
You should expect completion codes of 00 for all jobs except for #04DDDEF and #U4DDDEF, where 04 is acceptable if this is a new installation rather than an upgrade, and #07ACCPT, where 07 is acceptable on the SMP/E accept JOB.
Perform a cleanup
This section provides an overview of performing a cleanup.
After you are satisfied that DLm is correctly installed and functioning properly, run the job #08CLEAN to delete data sets and
DDDEFS used during the installation process that are no longer required.
Applying SMP/E maintenance
This section provides an overview of applying maintenance.
About this task
If there is no current maintenance, keep these instructions for future maintenance downloads:
● Install any available maintenance for DLm before you start running.
● You can obtain the latest maintenance updates and current release or service notes (identical to release notes) from the
Downloads section on the Support menu in the Dell Online Support website. See the “Loading DLMxyz.XMITLIB to disk” section using DLMSxyz for the search.
● Maintenance that must be applied to this release is in an item called DLm Mainframe Utilities SMP/E Fixes <version>
(DLMSxyz) .
NOTE: For earlier DLm Mainframe Utilities Releases maintenance could also be called DLm Mainframe Utilities
SMP/E Fixes (DLMSxyz) or DLm x.y.z SMP/E z/OS fixes (xyz) .
NOTE: If this file does not exist, there is no current maintenance to be applied.
This .zip file contains the following:
● ReadMe_DLMxyz_Fixes.txt: lists the fixes that are included in the release.
● DLMSxyz_Fixes.zip: contains
○ ReadMe_DLMxyz_Fixes.txt
○ DLMSxyzFIX.BIN—a software patch file
○ SMPJOB.txt—a sample job with instructions about how to apply the maintenance
To download maintenance from Dell Online Support:
Steps
1. Click Downloads and type DLMSxyz in the Search for Product text box, and press Enter .
2. Click the DLm Mainframe Utilities SMP/E Fixes <version> (DLMSxyz) . Download the zip file to your home system, unpack the zip file, and follow the instructions that it contains.
Downloading and Installing DLm Mainframe Utilities for z/OS 167
NOTE: For earlier DLm Mainframe Utilities Releases maintenance could also be called DLm Mainframe Utilities
SMP/E Fixes (DLMSxyz) or DLm x.y.z SMP/E z/OS fixes (xyz) .
3. When you are finished reading or copying from Dell Online Support, return to the previous pages to view other products and services, or choose Logout from the menu bar at the top of any page.
Installing DLm Utilities using the non-SMP/E method
To use any of these utilities for a non-SMP/E installation, follow these steps:
Steps
1. Download the latest dlm-mainframe-utilities-<version>-release-build<n>.zip file from the Dell Technologies support website:
NOTE: In earlier versions of DLm Mainframe Utilities, the file is called DLm-Mainframe-Utilities-<version>.zip
a. Go to https://dell.com/support .
b. Click Downloads.
c. In the Find a Product field , type “Disk Library for mainframe” immediately followed by the applicable DLm model (for example, "DLm2100," "DLm8100," and so on) for which you are searching. Select the text that automatically displays for the appropriate DLm model and d. Click the Search button.
e. Click DLm Mainframe Utilities to download the utilities.
f. Extract the dlm-mainframe-utilities-<version>-release-build<n>.zip. It contains the following XMIT files:
● LINKLIB.xmi is an offloaded PDS containing DLm Utilities load modules
● SAMPLIBU.xmi is an offloaded PDS containing JCL samples to run the DLm Utilities
● SAMPLIBC.xmi is an offloaded PDS containing JCL procedures and samples to run DLm Command Processors
● REXXCMD.xmi is an offloaded PDS containing REXX scripts to build commands to run DLm Command Processors using JCL procedures mentioned above (from SAMPLIBC.xmi)
● REXXAUTC.xmi is an offloaded PDS containing TCP/IP DLMAUT mainframe client
● SAMPLIBA.xmi is an offloaded PDS containing sample JCL scripts and DLMAUTC JCL procedure to run DLMAUT mainframe client.
NOTE: REXXAUTC and SAMPLIBA added to the non-SMP/E package since DLm Mainframe Utilities 2.4.0 Release.
2. Transfer the extracted LINKLIB.xmi file to the mainframe as follows: ftp target_system_name
(Satisfy login requirements of the mainframe.) quote site recfm=fb lrecl=80 bin put LINKLIB.xmi 'dsnname' quit
3. After transferring the file, use ISPF function 6 (Command Shell) and type: receive indataset('uid.linklib.xmi')
4. Type da('uid.EMC.DLMS<version>.LINKLIB') at the following prompt:
Enter restore parameter or delete or end.
uid.EMC.DLMS<version>.LINKLIB is created for the following members:
● DLMLIB—The utility required to add volumes to a DLm MTL
● DLMSCR—The DLm scratch utility
● DLMCMD—The DLm command utility
● DLMVER—The DLm utility version reporting utility
● GENSTATS—The report formatting utility
168 Downloading and Installing DLm Mainframe Utilities for z/OS
● DLMHOST—The DLm utility that provides a command interface to VTEs and a mechanism to list selected VTE log messages.
● DLMWTOR—A DLm utility that allows for placement of a z/OS Operator prompt jobstep to allow for operator verification of a job to proceed.
5. Authorize DLm LINKLIB.
The installed LINKLIB must be APF-Authorized. Add it to your existing authorized dataset list and/or enter a SETPROG z/OS Console command to mark it as authorized until the next IPL for your LPAR. Enter:
SETPROG APF,ADD,DSNAME=uid.EMC.DLMS<version>.LINKLIB,SMS
6. Upload REXXCMD.xmi, SAMPLIBC.xmi, REXXAUTC.xmi, SAMPLIBA.xmi, and SAMPLIBU.xmi to the mainframe: ftp target_system_name
(Satisfy login requirements of the mainframe.) quote site recfm=fb lrecl=80 bin put REXXCMD.xmi
(The file is placed on the host as 'uid.rexxcmd.xmi', where uid is the login userid that is used for the FTP.) put SAMPLIBC.xmi
(The file is placed on the host as 'uid.samplibc.xmi', where uid is the login userid that is used for the FTP.) put REXXAUTC.xmi
(The file is placed on the host as 'uid.rexxautc.xmi', where uid is the login userid that is used for the FTP.) put SAMPLIBA.xmi
(The file is placed on the host as 'uid.sampliba.xmi', where uid is the login userid that is used for the FTP.) put SAMPLIBU.xmi
(The file is placed on the host as 'uid.samplibu.xmi', where uid is the login userid that is used for the FTP.) quit
The following is a sample Unload of REXX and SAMPLIB upload:
C:\temp\DLm-Mainframe-Utilities-2.4.0-43>ftp 10.246.139.63
Connected to 10.246.139.63.
220-FTPD1 IBM FTP CS V2R3 at K10A, 14:10:14 on 2020-02-21.
220 Connection will close if idle for more than 60 minutes.
501 command OPTS aborted -- no options supported for UTF8
User (10.246.139.63:(none)): vmiron1
331 Send password please.
Password:
230 VMIRON1 is logged on. Working directory is "VMIRON1.".
ftp> quote site recfm=fb lrecl=80
200-BLOCKSIZE must be a multiple of LRECL for RECFM FB
200-BLOCKSIZE being set to 6160
200 SITE command was accepted ftp> bin
200 Representation type is Image ftp> put REXXCMD.xmi
200 Port request OK.
125 Storing data set VMIRON1.REXXCMD.XMI
250 Transfer completed successfully.
ftp: 345040 bytes sent in 1.04Seconds 330.81Kbytes/sec.
ftp> put SAMPLIBC.xmi
Downloading and Installing DLm Mainframe Utilities for z/OS 169
200 Port request OK.
125 Storing data set VMIRON1.SAMPLIBC.XMI
250 Transfer completed successfully.
ftp: 130480 bytes sent in 0.84Seconds 155.33Kbytes/sec.
ftp> put REXXAUTC.xmi
200 Port request OK.
125 Storing data set VMIRON1.REXXAUTC.XMI
250 Transfer completed successfully.
ftp: 85200 bytes sent in 0.42Seconds 203.83Kbytes/sec.
ftp> put SAMPLIBA.xmi
200 Port request OK.
125 Storing data set VMIRON1.SAMPLIBA.XMI
250 Transfer completed successfully.
ftp: 23680 bytes sent in 0.50Seconds 47.17Kbytes/sec.
ftp> put SAMPLIBU.xmi
200 Port request OK.
125 Storing data set VMIRON1.SAMPLIBU.XMI
250 Transfer completed successfully.
ftp: 31200 bytes sent in 0.29Seconds 108.71Kbytes/sec.
ftp> quit
221 Quit command received. Goodbye.
7. After transferring the files, use ISPF function 6 (Command Shell) and receive the uid.REXXCMD.XMI, uid.SAMPLIBC.XMI, uid.REXXAUTC.XMI, uid.SAMPLIBA.XMI, and uid.SAMPLIBU.XMI datasets: a. Type the following to receive uid.REXXCMD.XMI: receive indataset('uid.REXXCMD.XMI') b. At the prompt, Enter restore parameters or delete or end , type: da('uid.EMC.DLMS<version>.REXXCMD') . uid.EMC.DLMS<version>.REXXCMD will then be populated with the
DLm REXX program library.
c. Type the following to receive uid.SAMPLIBU.XMI: receive indataset('uid.SAMPLIBU.XMI') d. At the prompt, Enter restore parameters or delete or end , type: da('uid.EMC.DLMS<version>.SAMPLIBU') . uid.EMC.DLMS<version>.SAMPLIBU is populated with the DLm samplib library to run the various DLm Utilities. See member $INDEXU for a list of its contents.
e. Type the following to receive uid.SAMPLIBC.XMI: receive indataset('uid.SAMPLIBC.XMI') f. At the prompt, Enter restore parameters or delete or end , type: da('uid.EMC.DLMS<version>.SAMPLIBC') . uid.EMC.DLMS<version>.SAMPLIBC is populated with the DLm samplib library that contains PROCs and sample JCL to run DLm Command Processors. See member $INDEXC for a list of its contents.
g. Type the following to receive uid.REXXAUTC.XMI: receive indataset('uid.REXXAUTC.XMI') h. At the prompt, Enter restore parameters or delete or end , type: da('uid.EMC.DLMS<version>.REXXAUTC') . uid.EMC.DLMS<version>.REXXAUTC will then be populated with the
TCP/IP DLMAUT mainframe client.
i.
Type the following to receive uid.SAMPLIBA.XMI: receive indataset('uid.SAMPLIBA.XMI') j.
At the prompt, Enter restore parameters or delete or end , type: da('uid.EMC.DLMS<version>.SAMPLIBA') uid.EMC.DLMS<version>.SAMPLIBA is populated with the DLm samplib library that contains PROC and sample JCL to run DLMAUT mainframe client. See member $INDEXA for a list of its contents.
8. Move the DLm PROCs to a common Proclib and customize them for your installation.
Changes must be made for the following PROCs:
170 Downloading and Installing DLm Mainframe Utilities for z/OS
● DLMCPRUN
● DLMCMDPR
● DLMCMDP1
● DLMCMD49
● GENSTATP
● GENSTAT1
● GENSTATW
● GENSTATR
You can also set BTILIB and REXXLIB as parameters.
BTILIB: Dataset name for the DLm utilities that are referenced above as uid.EMC.DLMS<version>.LINKLIB.
REXXLIB: Dataset name for the DLm REXX library that is referenced above as uid.EMC.DLMS<version>.REXXCMD.
There are other optional changes to the GENSTATP, GENSTAT1, and GENSTATW Procs. By default, these create a temporary dataset on DASD for the STATSFILE which contains all .vstats records obtained from the DLm. These Procs use a default SPACE allocation of SPACE=(CYL,(50,50)). This space allocation may be changed or the DD can be modified to use DLm storage such as the examples below.
For large GENSTAT reports, the default SPACE allocation may not be sufficient. It is recommended that you expose the allocation size using a GENSTAT parameter.
NOTE: When storing the &STATFILE on DLm storage, you must specify an additional DLm unit in your override DD statement and it must be online. Below is an example using a non-MTL unit 4502:
● Changing the temporary STATFILE to use DLm storage:
//STEP4.PRINT DD DSN=&STATFILE,DISP=(NEW,PASS),
// UNIT=/4502,DCB=(LRECL=320,RECFM=FB,BLKSIZE=3200)
● Here is an example of overriding the DASD space allocation for the STATFILE DD, (Changing the primary and secondary space allocations to 100 cylinders each):
//STEP4.PRINT DD DSN=&STATFILE,
// DISP=(,PASS),SPACE=(CYL,(100,100)),
// UNIT=SYSDA,
// DCB=(LRECL=320,RECFM=FB,BLKSIZE=3200)
Post installation steps
This section describes the post installation steps.
Authorizing DLm LINKLIB
The installed Linklib must be APF-Authorized. Add it to your existing authorized dataset list and/or enter a
SETPROG z/OS Console command to mark it as authorized until the next IPL for your LPAR. Enter: SETPROG
APF,ADD,DSNAME=EMC.DLMSxyz.LINKLIB,SMS
Shutting down and restarting DLMHOST
After you install this release of DLm and performed the above authorization, you must recycle DLMHOST (if it is running).
Ensure that your DLMHOST JCL points to the installed LINKLIB.
Downloading and Installing DLm Mainframe Utilities for z/OS 171
C
DLm Utilities for z/OS Environment
Messages
The z/OS system messages are generated by these utilities:
Topics:
•
•
•
•
•
•
•
DLMCMD Messages
This section provides an overview of DLMCMD Messages.
The following messages can be returned by the DLMCMD program running on the mainframe:
DLC010I
I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XXXXXXXX XXXXXXXX
An I/O error occurred on the DLMCMD control tape. See the CSW and SENSE information and any additional messages on the z/OS and controller consoles to resolve the problem.
DLC050I
LOG FILE FAILED TO OPEN
DLMCMD was unable to open the DLMLOG log file. Check the JCL and any additional messages on the joblog to resolve the problem.
DLC060I
COMMAND FILE FAILED TO OPEN
DLMCMD was unable to open the input DLMCMD file. Check the JCL and any additional messages on the joblog to resolve the problem.
DLC070I
ENTER COMMAND or END
The PARM=WTOR parameter told DLMCMD to read input from the console. Type a command to send to the controller, or END to terminate DLMCMD.
DLC080I
COMMAND TIMED OUT – TERMINATING
The TIMEOUT= parameter was specified, and the DLm command did not complete within the timeout period.
DLC150I
INVALID DEV SPECIFIED
An invalid DEV= value was specified. Specify a valid DEV= parameter.
172 DLm Utilities for z/OS Environment Messages
DLC155I
DLC156I
DLC160I
DLC170I
DLC180I
DLC181I
DLC182I
DLC190I
ERROR DURING DLMCTRL DD PROCESSING. IEFDDSRV ERROR RC=xx, RS=xx
DLMCMD was unable to obtain allocated device from DLMCTRL DD. Check the JCL if DLMCTRL is properly specified and any additional messages on the job log to resolve the problem.
INVALID UCB ADDRESS AFTER DLMCTRL DD PROCESSING. UCB ADDRESS = 0
DLMCMD was unable to obtain nonzero UCB address after DLMCTRL DD processing. Check the JCL if
DLMCTRL DD is properly specified.
DEVICE NOT FOUND DURING UCBLOOK
An invalid DEV= value was specified. Specify a valid DEV= parameter.
ERROR DURING UCB CAPTURE/UNCAPTURE
The application was not able to free the DEV= device at termination. Contact Customer Support for assistance.
DRIVE IS ALREADY ALLOCATED or BOXED
The DEV= device is not available for use by DLMHOST. Specify a device that is not in use.
DRIVE HAS NO ONLINE PATHS
The DEV= device has no online paths. Specify a device that has one or more online paths.
TERMINATING – DRIVE xxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=
The DEV= device is varied online. Specify a device that is varied offline.
DEBCHK FAILED
The application was not able to free the DEV= device at termination. Contact Customer Support for assistance.
DLMHOST Messages
This section provides an overview of DLMHOST Messages.
The following messages might be returned by z/OS which is actively running the started task DLMHOST:
DLH000I
COMMANDS ARE:
STARTLOG,N=nodename/ALL
STOPLOG,N=nodename/ALL
STARTCMD,N=nodename/ALL
STOPCMD,N=nodename/ALL
N=nodename/ALL,C=command
STATUS
Issued in response to a help or ? command. Followed by a list of eligible commands:
● STARTLOG initiates/restarts logging from a single node or all nodes. Logging device paths must exist.
● STOPLOG terminates logging from a single node or all nodes.
● STARTCMD initiates/restarts the command path from a single node or all nodes.
● STOPCMD terminates the command path from a single node or all nodes.
DLm Utilities for z/OS Environment Messages 173
DLH001I
DLH002I
DLH003I
DLH010I
DLH030I
DLH035I
DLH040I
DLH050I
DLH055I
DLH060I
DLH150I
DLH160I
● N=nodename C=command passes the specified command to the designated node. The response goes to the operator or to the file designated by DLMLOG if parameter LOGFILE is used.
● STATUS shows the status as indicated in DLH240I.
jobname ENTER COMMAND, EOJ, OR ? FOR HELP
If the WTOR option is used, this is issued as the outstanding WTOR that the operator can reply to.
jobname USE MODIFY TO ENTER COMMAND, EOJ OR ? FOR HELP
If the NOWTOR option is specified, this message indicates to the operator that the MODIFY command is available to issue requests.
ENDING BY OPERATOR REQUEST
An EOJ or STOP command was processed.
I/O ERROR ON DEVICE XXXX: CSW=XXXX SENSE=XXXXXXXX XXXXXXXX
An error occurred on one of the control paths. Appropriate CSW and sense data are provided. The control path is marked as inactive.
CONFIG FILE FAILED TO OPEN
The file pointed to by the DLHCFG DD failed to open.
CONFIG FILE HAS NO ENTRIES
An end of file was detected on the configuration file without any entries being processed.
CONFIG FILE INVALID RECFM
The recfm of the DLHCFG file is not F or FB.
LOG FILE FAILED TO OPEN
The file pointed by the DLHLOG DD card, failed to open.
INPUT COMMAND FILE FAILED TO OPEN -IGNORING DOCMDS PARM
If the DOCMDS parameter is used, the DLMCMD DD card is missing or file that is failed to open.
CANNOT START – PROGRAM ALREADY ACTIVE
Only one copy of DLMHOST is allowed to run at a time. This can be overridden by specifying parameter
NOENQ.
INVALID DEV SPECIFIED
One of the devices that are specified is not a tape device.
DEVICE xxxx NOT FOUND DURING UCBLOOK
The DEV= parameter is specified, but the device does not exist in the current configuration.
174 DLm Utilities for z/OS Environment Messages
DLH170I
DLH180I
DLH181I
DLH182I
DLH210I
DLH220I
DLH230I
DLH231E
DLH232E
DLH190I
DLH200I
DLH233E
DLH240I
ERROR DURING UCB CAPTURE/UNCAPTURE
An error occurred while capturing/uncapturing a 24-bit UCB address from a 31-bit UCB.
DRIVE xxxx IS ALREADY ALLOCATED or BOXED
The designated device is already in use or is boxed.
DRIVE xxxx HAS NO OPERATIONAL PATHS
The designated device is marked as having no operational paths.
DEVICE ACTIVATION FAILED – DRIVE WAS ONLINE. CONTROL PATHS MUST BE
OFFLINE.
The control drive being used should be an offline device. Results are unpredictable if an online device is used.
DEBCHK FAILED
An error was detected while creating the device control blocks to access the device.
NODENAME NOT FOUND IN CONFIG TABLE
The nodename that is specified in a command/modify request does not exist in the configuration table.
Use the STATUS command to list the available nodenames.
INVALID DEVICE xxxx IN CONFIG TABLE
The specified device contains invalid hexadecimal digits.
NODENAME NOT SPECIFIED IN COMMAND
A command was entered, and did not contain a nodename as the target of the command.
NO COMMAND FOUND IN RESPONSE
There was no C= or CMD= in the operator request.
ERROR: UNBALANCED PARENTHESES IN COMMAND
Check parenthesis in command.
ERROR: INVALID OR MISSING NODENAME IN COMMAND
A command was entered, and contained invalid nodename or did not contain nodename as the target of the command.
ERROR: ERROR: NO COMMAND SPECIFIED IN INPUT
Specify the command.
NODENAME CMDDEV LOGDEV
This is followed by one line showing the status for each node, path, and console assignment:
DLm Utilities for z/OS Environment Messages 175
DLH250I
DLH260I
● NODENAME is the name that is assigned in the config table.
● CMDDEV shows the device (if any) assigned as the command path. A y/n indicates if it is active.
● LOGDEV shows the device (if any) assigned as the log path. A y/n indicates if it is active.
NODE nodename PATH xxxx INACTIVE
A command was requested to be issued to a command path that is marked inactive.
PROCESSING COMMAND: command line
The DOCMDS parameter was used. This lists each command that is processed from the DLHCMD file as it is being processed.
DLMLIB Messages
This section provides an overview of DLMLIB Messages.
The following message can be returned by the DLMLIB program running on the mainframe:
DLL100I
INVALID VOLSER xxxxxx SPECIFIED
An invalid volser was specified in the input file. Correct the input and rerun.
DLL110I
ZERO VOLUME COUNT SPECIFIED
Zero count was specified in the input file when trying to manually add volume. Specify non-zero volume count or remove this input card and rerun.
DLMSCR Messages
This section provides an overview of DLMSCR Messages.
The following messages can be returned by the DLMSCR program running on the mainframe:
DLS010I
I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX
The control tape that sends scratch requests to the controller had an I/O error. Check to ensure that the controller is still running. If so, use the CSW and SENSE provided to correct the problem. <Description>.
DLS012I
UNEXPECTED HEADER IN SCRATCH REPORT
While processing the scratch report DLMSCR found a header it not expecting. First ensure that the TYPE parameter is correct for the scratch report you are running. If so, ensure that the scratch report is of the correct format.
DLS020I
NO VALID SCRATCH REQUESTS PROCESSED
DLMSCR processed the entire scratch report and found no valid scratch requests. First check the
PREFIX and PREFIXLN parameters to ensure they correctly match the tape prefixes used on the VTE controller. If they are correct ensure that the scratch report contains tapes with those prefixes.
DLS030I
INPUT SCRATCH REPORT FAILED TO OPEN
The DLMSCR input scratch report failed to open. Check the DD statement for the DLMSCR input file and ensure it refers to a valid scratch report file.
176 DLm Utilities for z/OS Environment Messages
DLS110I
DLS111I
DLS120I
DLS130I
DLS031I
DLS040I
DLS050I
DLS060I
DLS070I
DLS080I
DLS081I
DLS100I
INPUT SCRATCH REPORT RECFM NOT FBA AS EXPECTED
The scratch report, which is created by the customer's TMS, must have a LRECL of 133 and a RECFM of
F or FB.
CONTROL PATH FAILED TO OPEN
The DLMSCR control tape failed to open. Ensure that the controller is up and running and the unit address that is used for the DLMSCR control tape is a valid controller device and has been varied online to the mainframe.
LOG FILE FAILED TO OPEN
DLMSCR maintains a log file with all the error and informational messages from any DLMSCR runs. Check the mainframe job log to determine why it did not open properly.
SORTIN FILE FALED TO OPEN
DLMSCR requires a sortin file when processing a Tivoli Storage Manager (TSM) report.
INPUT FILE IS NOT A NEW SCRATCH REPORT
DLMSCR requires the date on the Scratch Report that is created by the customer's TMS to be today's date. This is to prevent the inadvertent use of an old scratch report. Run a new scratch report.
This is a request to free space from scratch tapes. Reply YES to continue
DLMSCR requests operator intervention before it frees space from scratched tapes. This is because after space is freed the data on scratched tape cannot be retrieved.
FREExxxxx NOT ALLOWED WITH TYPE RMMDV
RMMDV has its own format, See the documentation on RMMDV.
NO INPUT PARAMETERS FOUND
DLMSCR requires at least the TYPE= parameter be configured. Check the format of your input parameters.
NO type FOUND IN INPUT PARAMETERS
DLMSCR requires the TYPE= parameter. Check your input parameters.
UNKNOWN type FOUND IN INPUT PARMS
DLMSCR has found an incorrect TYPE= parameter. Check your input parameters.
Free space not confirmed - terminating
PREFIX LENGTH INVALID
The default for the PREFIXLN is 2. Usually the customer uses 2 for their prefix length. If the tape library resides on Centera a prefix length of 1 is common. In that case PREFIXLN=1 should be coded. Check your input parameters.
DLm Utilities for z/OS Environment Messages 177
DLS140I
DLS150I
DLS160I
DLS170I
DLS180I
DLS181I
DLS182I
DLS185I
DLS190I
DLS200I
DLS210I
SORT FAILED
The internal sort performed on a Tivoli Storage Manager (TSM) report failed. See the preceding console messages for the reason.
INVALID DEV SPECIFIED
The parameter that is specified in the DEV= field is < 3 or >4 characters, or contains non-hexadecimal characters.
DEVICE NOT FOUND DURING UCBLOOK
The device that is specified on the DEV= parameter was not found in the active configuration. Correct the parameter and retry.
ERROR DURING UCB CAPTURE/UNCAPTURE
A failure occurred attempting to capture/uncapture a 24-bit UCB address from a 31-bit one. Contact support.
DRIVE IS ALREADY ALLOCATED or BOXED
The device that is specified on the DEV= parameter is either already in use or is boxed and cannot be used. Select a different drive and retry the job.
DRIVE HAS NO ONLINE PATHS
The device that is specified on the DEV= parameter has no online paths available. Select a different drive and retry the job.
DEVICE IS ASSIGNED ELSEWHERE
The device that is specified on the DEV= parameter is already assigned to another job. Select a different drive and retry the job.
TERMINATING – DRIVE IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=.
The control drive being used should be an offline device. Results are unpredictable if an online device is used.
DEBCHK FAILED
An internal DEBCHK macro returned a non-zero return code. Contact Customer Support.
ERROR GETTING DEVICE CLASS EXTENSION
A failure occurred attempting to get Device Class Extension information. Contact Customer Support.
TERMINATING - VOLSER xxxxxx IS NOT IN MTL LIBRARY
DLMSCR was unable to update TCDB use attribute for xxxxxx volser because the volser is not in MTL
Library. Check if the volser proper configured in the Library.
178 DLm Utilities for z/OS Environment Messages
DLMVER Messages
This section provides an overview of DLMVER Messages.
The following message is returned by the DLMVER program running on the mainframe:
DLV010I
UTILITY VERSIONS (<z/OS release level>):
This message is written to the file pointed to by the DLMLOG DD card, or to the operator if the WTO parm is used. The execution environment’s z/OS release level is displayed within parentheses. The release levels of the other DLm utilities follow the DLV010I header line.
GENSTATS Messages
This section provides an overview of GENSTATS Messages.
The following messages can be returned by the GENSTATS program running on the mainframe:
GEN010I
I/O ERROR ON CTRL DEVICE: CSW=XXXX SENSE=XX:
An I/O error has occurred on the GENSTATS control tape device that is named with the DEV= parm.
Processing stops. Try rerunning the job. Contact Customer Support if the problem recurs.
GEN030I
INPUT STATISTICS FILE FAILED TO OPEN
GENSTATS was unable to open the input file. Check your JCL and rerun. Contact Customer Support if the problem recurs.
GEN031I
OUTPUT REPORT FILE FAILED TO OPEN
GENSTATS failed to open the SYSPRINT file. Check your JCL and retry.
GEN032I
SORTIN FILE FAILED TO OPEN - REQUIRED FOR STILLINUSE PARM
GENSTATS requires the following JCL when the STILLINUSE report is requested:
GEN040I
GEN050I
GEN060I
//SORTIN DD (temporary work file)
//SORTOUT DD (temporary work file)
//SYSOUT DD SYSOUT=*
Ensure that these DD statements are in your JCL and rerun the job.
VOL= PARM REQUIRED WHEN DEV= IS USED
When DEV= is used, GENSTATS must be told which VOLSER it is to process. Add the VOL= parameter and rerun the job.
MOUNT FOR VOLSER XXXXXX FAILED TO COMPLETE
GENSTATS was trying to mount a virtual tape volume and the mount failed to complete. Check your JCL and retry.
INPUT BLOCK LENGTH NOT A MULTIPLE OF 320
The input GENIN DD dataset must be set to fixed length records that are 320 bytes long with a BLKSIZE that is a multiple of that record length. Check your JCL and retry.
DLm Utilities for z/OS Environment Messages 179
GEN100I
GEN140I
GEN150I
GEN160I
GEN170I
GEN180I
GEN181I
GEN182I
GEN183I
GEN190I
GEN100I INPUT RECORDS
This is an informational message that precedes a list of record counts. No action is required.
SORT FAILED - CHECK LISTING
GENSTATS requires the following JCL when the STILLINUSE report is requested:
//SORTIN DD (temporary work file)
//SORTOUT DD (temporary work file)
//SYSOUT DD SYSOUT=*
Ensure that these DD statements are in your JCL and rerun the job. If the job still fails, check the sort
SYSOUT messages to identify the reason for the sort failure.
INVALID DEV SPECIFIED
The parameter that is specified in the DEV= field must be 3 or 4 characters and must be a hexadecimal number.
DEVICE NOT FOUND DURING UCBLOOK
The device that is specified on the DEV= parameter was not found in the active configuration. Correct the parameter and rerun the job.
ERROR DURING UCB CAPTURE/UNCAPTURE
A failure occurred attempting to capture or uncapture a 24-bit UCB address from a 31-bit address.
Contact Customer Support.
DRIVE IS ALREADY ALLOCATED or BOXED
A device that is specified on the DEV= parameter is either already in use or is boxed and cannot be used.
Select a different drive and retry the job.
DRIVE HAS NO ONLINE PATHS
The device that is specified on the DEV= parameter has no online paths available. Select a different drive and retry the job.
DEVICE IS ASSIGNED ELSEWHERE
The device that is specified on the DEV= parameter is already assigned to another job. Select a different drive and retry the job.
TERMINATING – DRIVE xxxx IS ONLINE. SHOULD BE OFFLINE WHEN USING DEV=
The device that is specified on the DEV= parameter is online. Vary this drive offline or select a different drive and retry the job.
DEBCHK FAILED
An internal DEBCHK macro returned a non-zero return code. Contact Customer Support.
180 DLm Utilities for z/OS Environment Messages
GEN200I
GEN300I
GEN310I
GEN320I
GEN400I
GEN450I
GEN500I
DEVICE TABLE OVERFLOW
More than 2000 active devices were found in the input GENIN file. Add the DEVCNT=xxxx parameter to increase the tape size appropriately and rerun the job.
DATE TABLE OVERFLOW - LIMIT RANGE
The internal date tape default of 128 days was exceeded. Either limit the range with DATESTART /
DATEEND, or increase the default date table size with DAYCNT=xxxx.
SYNCTIME REQUIRES THAT DATEEND BE SPECIFIED
The SYNCTIME parameter can only be used with the DATEEND parameter. Add an appropriate DATEEND parameter and retry the job.
SYNCTIME FORMAT INVALID (HH:MM:SS)
The SYNCTIME parameter must be specified in the format HH:MM:SS. Correct the parameter and retry the job.
PATHNAME TABLE OVERFLOW
The internal pathname table default of 512 pathnames was exceeded. Add the PATHCNT=xxxx parameter and rerun the job.
VOLSER TABLE OVERFLOW. EXCEEDED nnnnnnn TIMES
The internal VOLSER table of currently mounted volumes was exceeded. Add the VOLCNT=xxxx parameter and rerun the job. The VOLCNT parameter default value is 2200. Increase the VOLCNT parameter at least the number of times indicated in this message.
INPUT FILE WAS EMPTY - PROBABLE SCRIPT ERROR
The GENIN input file is empty. This is likely caused by a script error in the first step of the GENSTATS job.
Check the script being run by VTCMD and then retry the job.
DLMCP Messages
This section provides an overview of DLMCP Messages.
The following messages can be returned by the DLMCP utility:
DLP005E
UNABLE TO OPEN DLMCPRPT DATASET
LOGFILE parameter was specified, and DLMCP utility was unable to open dataset specified in the
DLMCPRPT DD statement. Check that this dataset is available and is correctly set up (LRECL=264,
RECFM=FB).
DLP010E
INVALID DEV PARAMETER SPECIFIED: XXXX
An invalid DEV parameter value was specified. Specify a valid DEV= parameter.
DLP015E
DEV PARAMETER VALUE IS MISSED
DEV parameter value should be specified.
DLm Utilities for z/OS Environment Messages 181
DLP060E
DLP070E
DLP080E
DLP090E
DLP100E
DLP020E
DLP025E
DLP030E
DLP035E
DLP040E
DLP050E
UNABLE TO OPEN DLMCPCMD DATASET
DLMCP utility was unable to open the input dataset specified in the DLMCMD DD statement. Check that this dataset is available and is correctly set up (LRECL no longer than 256). Ensure that these DD statements are in your JCL and rerun the job.
REPORT IS UNAVAILABLE OR INVALID
DLMCP utility was unable to obtain the report file, or the formatting of the obtained report is invalid.
CONTROL DEVICE XXXX IS ALREADY ALLOCATED
A Device used as the DEV parameter value is allocated by some other JOB when must be offline.
CONTROL DEVICE XXXX IS ALREADY BEING USED
Device used as the DEV parameter value is offline and already used by some other utility when should not be simultaneously used.
CONTROL DEVICE XXXX IS ONLINE. MUST BE OFFLINE
A device used as the DEV parameter value is online when must be offline.
CONTROL DEVICE XXXX HAS NO OPERATIONAL PATH
Device used as the DEV parameter value has no operational path. Check that the path is physically available and operational.
CONTROL DEVICE XXXX IS NOT A TAPE DEVICE
Only tape device is allowed to be used as the DEV parameter.
CONTROL DEVICE XXXX NOT FOUND DURING UCBLOOK
Internal configuration error.
CONTROL DEVICE XXXX UCB CAPTURE/UNCAPTURE FAILED
Internal configuration error.
CONTROL DEVICE XXXX DEBCHK FAILED
Internal configuration error.
I/O ERROR ON CTRL DEVICE XXXX
An I/O error occurred on the DLMCP control device. See the CSW and SENSE information in the
JOBLOG.
182 DLm Utilities for z/OS Environment Messages
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
- DLm Utilities for z/OS
- Command Processor diagnostics (CP499)
- VTE Command execution (CP501)
- DLm Log Information retrieval (CP502)
- Virtual Tape Volume info (CP503)
- VNX Replication info (CP504)
- Data Domain/PowerProtect info (CP601, CP602, CP603)
- Replication info by VOLSER (CP804)
- Tape activity monitoring (CP988, CP989, CP998, CP999)
