CA Dynam For VSE User Guide

CA Dynam for VSE
User Guide
r7.1
Second Edition
This documentation and any related computer software help programs (hereinafter referred to as the
“Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at
any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in
part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA
and protected by the copyright laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for
their own internal use, and may make one copy of the related software as reasonably required for back-up and
disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy.
Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for
the product are permitted to have access to such copies.
The right to print copies of the documentation and to make a copy of the related software is limited to the period
during which the applicable license for the Product remains in full force and effect. Should the license terminate for
any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the
Documentation have been returned to CA or destroyed.
EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY
APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING
WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY
LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT
LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY
ADVISED OF SUCH LOSS OR DAMAGE.
The use of any product referenced in the Documentation is governed by the end user’s applicable license
agreement.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-
7014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Copyright © 2008 CA. All rights reserved.

CA Product References
This document references the following CA products:
CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)
CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)
CA Dynam®/FI File Independence (CA Dynam/FI)
CA TLMS Tape Management (CA TLMS)
CA Common Infrastructure Services for z/VSE (CA CIS)

CA Earl™ (CA Earl)
CA 1® MVS (CA 1)
CA Sort® for z/VSE (CA Sort)
CA Audit
Contact CA
Contact Technical Support
For online technical assistance and a complete list of locations, primary service
hours, and telephone numbers, contact Technical Support at
http://ca.com/support.
Provide Feedback
If you have comments or questions about CA product documentation, you can

send a message to techpubs@ca.com.
If you would like to provide feedback about CA product documentation, please

complete our short customer survey, which is also available on the CA Support
website.
Contents
Chapter 1: Introduction
CA Dynam for VSE Products ................................................................... 1-1
CA Dynam/T Tape Management............................................................ 1-1
CA Dynam/D Disk Management ............................................................ 1-1
CA Dynam/FI File Independence ........................................................... 1-2
Common Subset Features ..................................................................... 1-2
CA Dynam Catalog and Audit Trail Files .................................................... 1-2
Data Set Control .......................................................................... 1-3
Backup, Restore, and Recover ............................................................. 1-3
Report on the Catalog ..................................................................... 1-3
Start and Deactivate CA Dynam ............................................................... 1-4
Start CA Dynam .......................................................................... 1-4
Deactivate CA Dynam ..................................................................... 1-4
CA Dynam Extended Operator Communication Facility .......................................... 1-4
Critical System Function Integrity .............................................................. 1-5
System Adapter CANCEL-DELAY Support ....................................................... 1-6
TLBL/DLBL Extensions ........................................................................ 1-6
TLBL Extensions .......................................................................... 1-6
DLBL Extensions ......................................................................... 1-12
Delete Label Option Blocks—RESET Statement................................................. 1-15
RESET Format ........................................................................... 1-16
Chapter 2: Maintaining Tape Files

Preparing for CA Dynam/T .................................................................... 2-1
Audit Data Set ............................................................................ 2-1
Catalog File............................................................................... 2-2
Establishing Data Sets .................................................................... 2-2
Initializing Scratch Tapes .................................................................. 2-3
Modifying JCL ............................................................................. 2-5
Implementing CA Dynam/T.................................................................... 2-6
Using CA Dynam/T ........................................................................... 2-7
Controlling Data Sets ..................................................................... 2-7
Protecting Controlled Data Sets ............................................................ 2-8
CA Dynam/T Support Exceptions ........................................................... 2-8
Establishing Retention Characteristics ...................................................... 2-8
Contents v
Modifying Retention Characteristics ....................................................... 2-10
Scratching Eligible Data Set Versions ..................................................... 2-10
Data Set Name Listing ................................................................... 2-12
Automatic Volume Recognition (AVR) ..................................................... 2-12
Using the Early Drive Release ............................................................ 2-14
Dynamic LUB Allocation .................................................................. 2-14
Mounting Tapes ......................................................................... 2-15
TLBL Statement Extensions and Format ................................................... 2-30
Tape Reel Length Specification ........................................................... 2-39
Recording Density (MODE) Specification .................................................. 2-42
Tape Cartridges ......................................................................... 2-46
Managing Special Files ...................................................................... 2-48
Using Work Data Sets ................................................................... 2-48
Altering Retention Characteristics ........................................................ 2-48
Releasing Work Data Sets................................................................ 2-49
Defining Independent Files ............................................................... 2-49
Running Tests with Production JCL........................................................ 2-53
Using Cataloged Information ................................................................. 2-54
Daily Catalog Maintenance ............................................................... 2-54
Protecting the Catalog ................................................................... 2-56
Protecting Data Sets ..................................................................... 2-57
IBM Hardware Based Tape Encryption Support ................................................ 2-60
Automatic Cataloging/Uncataloging ....................................................... 2-60
Sending File-Dependent System Messages ................................................ 2-61
Processing Predefined Multifile Volume Data Sets.............................................. 2-62
Redefining Retention Characteristics ...................................................... 2-63
Maintaining Predefined Multifile Volume Data Sets ......................................... 2-64
Automatic Tape Positioning .............................................................. 2-64
Processing Without Additional Positioning ................................................. 2-65
Processing Unchained Multifile Tapes ......................................................... 2-67
Using Automatic Multifile (AMF) Data Sets .................................................... 2-69
Generating AMF File Numbers ............................................................ 2-69
Creating an Automatic Multifile Data Set .................................................. 2-69
Volume Switching with AMF Data Sets .................................................... 2-70
Scratching More Than the Last AMF DSN .................................................. 2-71
Inputting AMF Data Sets ................................................................. 2-71
Renaming and Resetting AMF Data Sets .................................................. 2-72
Forced Standard Label Support .............................................................. 2-72
Support for Read Backwards ................................................................. 2-73
ASCII Tape Support ......................................................................... 2-73
Using Other Software with CA Dynam/T ...................................................... 2-73
Sort and Utility Package Support ......................................................... 2-73
Processing FORTRAN Tape Files .......................................................... 2-74
vi User Guide
LIBR Backups and Restores ............................................................... 2-75
Controlling Single and Multi-Volume POWER Offload Tapes ..................................... 2-80
Controlling POWER Job Accounting Tapes ..................................................... 2-82
Enforcing Volume Serial Number Standards ................................................... 2-82
Specifying the SET Command ................................................................ 2-82
SET Command Syntax Rules .............................................................. 2-83
Summary of SET Command Syntax ....................................................... 2-83
Tape Drives ................................................................................. 2-84
Pooling Tape Drives (DTPOOL Option Record) .............................................. 2-84
Locking Tape Drives (DTLOCK Option Record) ............................................. 2-84
Using the Console Alarm Facility .............................................................. 2-85
Chapter 3: Supporting Tape File Management

Tape File Management Utilities ................................................................ 3-1
Tape Assignment Program—TDYNASN ...................................................... 3-1
Tape Copy Utility—TDYNCOPY ............................................................. 3-8
Tape Label Generator—TDYNLBL .......................................................... 3-12
CHKPT/RSTRT Program—TDYNRST ........................................................ 3-14
Synchronizing Volumes (using XSYSTEM)—TDYNSYNC ..................................... 3-16
Reporting on Tape Files ...................................................................... 3-27
Cataloged Tape Files Report—TAPES ...................................................... 3-28
Tape Cleaning and Error Report—TDYNCLEN ............................................... 3-29
Pull List Utility—TDYNLIST ................................................................ 3-31
JCL-driven Pull-list Utility—TDYNPULL ..................................................... 3-33
Utility Reporting Program—TDYNUTL ...................................................... 3-38
Vault Location Control Program—TDYNVLT .................................................... 3-45
Establishing Vault Locations .............................................................. 3-46
Running TDYNVLT ....................................................................... 3-47
TDYNVLT Commands ..................................................................... 3-49
IBM 3494 Tape Library Interface.............................................................. 3-52
Controlling Scratch Pools ................................................................. 3-52
IBM 3494 Multiple Library Support ........................................................ 3-53
Forcing a Re-Scan of the IBM 3494 Tape Drives ............................................ 3-53
Using CA Dynam/T MODON 11, 22, and 23 with the IBM Robot System...................... 3-54
IBM Virtual Tape Facility (VTAPE) Support ..................................................... 3-55
IBM VTAPE Command Format............................................................. 3-55
Overview of CA Dynam/T Support of VTAPE ............................................... 3-55
CA Dynam/T Enhanced Support for Virtual Tapes .......................................... 3-57
Contents vii
Chapter 4: Disk File Management
Basic Components ........................................................................... 4-2
Allocate Disk Space ....................................................................... 4-2
Catalog File .............................................................................. 4-6
Temporary Data Sets ..................................................................... 4-8
Logical Units ............................................................................. 4-9
File Type ................................................................................. 4-9
Default Allocation Support ............................................................... 4-10
Managing the VTOC ......................................................................... 4-10
VTOC Indexes ........................................................................... 4-11
Processing the VTOC .................................................................... 4-11
Building the VTOC Index ................................................................. 4-11
Searching the VTOC ..................................................................... 4-12
Creating New VTOC Records ............................................................. 4-12
Deleting Expired Files .................................................................... 4-13
Indexed VTOC Processing ................................................................ 4-13
Defining File ID Option Codes ................................................................ 4-14
Syntax Conventions ..................................................................... 4-14
Common Syntax Errors .................................................................. 4-14
Controlling Generation Data Sets ............................................................. 4-20
Defining Generation Data Sets ........................................................... 4-20
Changing Generation Numbers ........................................................... 4-21
Deleting Generation Data Sets ........................................................... 4-22
Generation Data Set Option .............................................................. 4-22
Automatic Volume Assignment and Recognition (AVR) ......................................... 4-24
Using AVR Processing .................................................................... 4-24
Bypassing AVR Processing ............................................................... 4-24
Selecting Logical Units....................................................................... 4-25
Overriding SYS Numbers ................................................................. 4-25
Specifying Other Option Codes ........................................................... 4-25
LUB Availability ......................................................................... 4-26
SYS Number Considerations.............................................................. 4-26
Modifying Logical Unit Assignments (LUBS) ................................................... 4-27
Dynamic LUB Allocation .................................................................. 4-27
Defining LUB Ranges .................................................................... 4-27
COMLUB Option Record Processing ....................................................... 4-28
LUB Assignments ........................................................................ 4-28
Extending ISAM Files ........................................................................ 4-29
Adding a File to the Catalog .................................................................. 4-29
Controlling Disk Pools ....................................................................... 4-30
Defining Disk Pool Volumes (COMPOOL) .................................................. 4-30
Rotating Disk Pool Volumes .............................................................. 4-31
viii User Guide

Defining Disk Pools for AVR (COMAVR) .................................................... 4-32
Attention Routine (AR) Commands ........................................................ 4-32
Allocating Space across Generic Volumes ...................................................... 4-33
Automatic Secondary Allocation ........................................................... 4-34
Disk Pool Management ................................................................... 4-34
Catalog Management..................................................................... 4-34
Defining Minimum Space Allocation ........................................................... 4-35
Recovering from Lack of Allocated Space ...................................................... 4-36
Recovery Process Description ............................................................. 4-36
Operator Recovery Actions ............................................................... 4-36
Defining Independent Files ................................................................... 4-38
JCL-Defined Partition and CPU Independent Files ........................................... 4-38
Catalog-Defined Partition and CPU Independent Files ....................................... 4-40
Releasing Unused Disk Space................................................................. 4-40
Truncating Files .......................................................................... 4-41
Deleting Files ................................................................................ 4-42
Deleting Data Files ....................................................................... 4-42
Deleting Work Files ...................................................................... 4-42
CA SORT Work Files ...................................................................... 4-42
Processing Expired Files ...................................................................... 4-43
Retention and Expiration Date Criteria..................................................... 4-43
Retention and Expiration Date Processing ................................................. 4-43
Processing of Equal File IDs .................................................................. 4-45
Sending File-Dependent System Messages .................................................... 4-45
SORT Considerations ........................................................................ 4-46
CA SORT Interface ....................................................................... 4-46
IBM Sort/Merge Program ................................................................. 4-47
Using Option S .......................................................................... 4-48
Specifying the SET Command ................................................................ 4-48
Restarting Checkpointed Files ............................................................. 4-52
Chapter 5: Supporting Disk File Management

Disk File Maintenance Utilities ................................................................. 5-1
Modifying the VTOC—CAINTDK ............................................................ 5-1
Converting EXTENTs—DYNCONV ........................................................... 5-3
Pre-Open Processing—DYNOPEN ........................................................... 5-8
Controlling Disk Files—DYNUTIL .......................................................... 5-11
Reporting on Disk Files....................................................................... 5-42
Disk Space Usage Analysis—SPACEUSE ................................................... 5-43
Volume Table of Contents—VTOCS ........................................................ 5-47
Contents ix
Chapter 6: Controlling File Independence
Introducing CA Dynam/FI ..................................................................... 6-1
Supported Program DTF Types ................................................................ 6-2
Physical Files ................................................................................ 6-3
Restrictions on DTF Types .................................................................... 6-3
Special Considerations .................................................................... 6-3
Unsupported DTFs ........................................................................ 6-3
Hierarchy of File Information .................................................................. 6-4
Unit Record Simulation ....................................................................... 6-4
CICS Command Level Preprocessor Support................................................ 6-6
CICS Macro Level Preprocessor Support.................................................... 6-7
Dynamic File Sorting ......................................................................... 6-8
Changing File Characteristics ................................................................ 6-10
TLBL/DLBL Extensions and Format........................................................ 6-10
TLBL Statement ......................................................................... 6-11
DLBL Statement ......................................................................... 6-15
Cataloged Data Set Definitions ........................................................... 6-20
Considerations for CA Dynam/FI Options .................................................. 6-21
Storage Requirements ................................................................... 6-22
Block Sizes and Logical Record Lengths ................................................... 6-22
Concatenated Data Sets ................................................................. 6-24
Controlling System Actions .................................................................. 6-26
Setting System Controls - SET Statement ................................................. 6-26
SYSLOG Support - ASSGN Statement ..................................................... 6-28
Operator Device Switching Facility ........................................................... 6-34
Requirements ........................................................................... 6-35
Operation ............................................................................... 6-35
Restrictions ............................................................................. 6-36
Using Other Software with CA Dynam/FI ...................................................... 6-36
With CA Dynam/D and CA Dynam/T ...................................................... 6-36
With System Utilities .................................................................... 6-38
With Sort Packages ...................................................................... 6-39
With Existing Programs .................................................................. 6-40
Limiting File-independence Processing .................................................... 6-42
Direct Access File Independence Facility (VCKD) .............................................. 6-43
Utility Programs ......................................................................... 6-43
Record Formats ......................................................................... 6-43
Data Records ........................................................................... 6-43
System Restrictions ..................................................................... 6-44
Activating VCKD ......................................................................... 6-44
VCKD File Parameters ................................................................... 6-44
FBA Disk Files ........................................................................... 6-46
x User Guide
VCKD Utility Programs ................................................................... 6-48
Catalog Support for CA Dynam/FI ............................................................ 6-52
Catalog File.............................................................................. 6-52
Setting Catalog Support .................................................................. 6-52
Maintaining Catalog Information .......................................................... 6-53
Chapter 7: Using Online Panels−CAICUI

Introduction to the File Management System ................................................... 7-1
PF Keys .................................................................................. 7-1
Available Command Types ................................................................. 7-2
Global Display Command Summary ............................................................ 7-4
DYNCAT Command ........................................................................... 7-6
Local Command Summary .................................................................... 7-6
Accessing the File Management System ........................................................ 7-7
File Management Panel (CAYD-0000) .......................................................... 7-9
System Options ............................................................................. 7-10
Data Set Maintenance........................................................................ 7-10
Data Set Selection Panel (CAYD-2000) .................................................... 7-11
Data Set Directory Panel (CAYD-2100) .................................................... 7-13
Data Set Detail Panel (CAYD-2110) ....................................................... 7-15
Data Set Disk Option Panel (CAYD-2120) .................................................. 7-22
Data Set Option Panel (CAYD-2130) ...................................................... 7-24
Auxiliary Record Panel (CAYD-2140) ...................................................... 7-26
Disk Version List Panel (CAYD-2150) ...................................................... 7-29
Tape Version List Panel (CAYD-2160) ..................................................... 7-31
FI Version List Panel (CAYD-2170) ........................................................ 7-32
DISK Version Detail Panel (CAYD-2180) ................................................... 7-34
TAPE Version Detail Panel (CAYD-2190) ................................................... 7-37
Tape Volume Maintenance ................................................................... 7-39
Tape Selection Panel (CAYD-3000) ........................................................ 7-40
Tape Directory Panel (CAYD-3100) ........................................................ 7-44
Tape Volume Detail Panel (CAYD-3110) ................................................... 7-46
Data Sets on Volume Panel (CAYD-3120) .................................................. 7-50
Chapter 8: Maintaining the Catalog−DYNCAT Program

DYNCAT Control Statement Format ............................................................ 8-2
DYNCAT Functions ............................................................................ 8-3
Summary of Control Statement Syntax ........................................................ 8-5
DYNCAT Commands ......................................................................... 8-11
Contents xi
ACTION Command ...................................................................... 8-11
ADD Command .......................................................................... 8-12
ALTER Command ........................................................................ 8-17
BACKUP Command ...................................................................... 8-41
DEFINE Command ....................................................................... 8-44
DELETE Command ....................................................................... 8-63
DEQUEUE Command..................................................................... 8-66
END Command .......................................................................... 8-67
INITIAL Command....................................................................... 8-67
INT and INTR Commands ................................................................ 8-69
LISTCAT Command ...................................................................... 8-73
MACC Command ........................................................................ 8-75
MCAT Command ........................................................................ 8-76
OWN Command ......................................................................... 8-77
RENAME Command ...................................................................... 8-78
RESTORE Command ..................................................................... 8-80
SCRATCH Command ..................................................................... 8-83
SCRPOOL Command ..................................................................... 8-86
STATUS Command ...................................................................... 8-90
VAULT Command ........................................................................ 8-91
VTOC Command......................................................................... 8-93
Chapter 9: CA Dynam Reporting Utilities

General Reporting−DYNPRINT ................................................................ 9-1
DYNPRINT Control Statements ............................................................ 9-2
ACCESS Command ....................................................................... 9-3
REPORT and COMPILE Commands ......................................................... 9-3
Standard DYNPRINT Reports .............................................................. 9-6
Creating Customized Reports.............................................................. 9-8
DYNPRINT VSE Operation ................................................................ 9-10
The DYNREAD Interface.................................................................. 9-14
Functions of DYNREAD ................................................................... 9-15
Reporting on the Catalog .................................................................... 9-16
Active Catalog Files−ACTVFILE ........................................................... 9-16
Catalog File Definitions−FILEDEFS ........................................................ 9-19
File Usage Frequency−FREQUSE.......................................................... 9-21
Displaying the VTOC−DYNVTOC .............................................................. 9-24
Using DYNVTOC ......................................................................... 9-24
xii User Guide

Chapter 10: Accessing the Catalog
Supported Languages ........................................................................ 10-1
Using DYNACC .............................................................................. 10-1
Testing DYNACC Programs ............................................................... 10-2
DYNINFO Parameter List Generation ...................................................... 10-2
Using DYNACC .............................................................................. 10-2
Linkage Conventions ..................................................................... 10-3
Parameter List Contents .................................................................. 10-3
Service Module Processing ................................................................ 10-4
DYNINFO Parameter List ..................................................................... 10-4
Invoking DYNACC from COBOL and CA Earl Programs ...................................... 10-4
Invoking DYNACC from Assembler Programs ............................................... 10-4
DYNINFO Layout ......................................................................... 10-6
DYNACC Request Codes .................................................................. 10-6
DYNACC Request Code Descriptions ....................................................... 10-7
DYNINFO Request Fields ................................................................10-12
DYNINFO Return Fields ..................................................................10-15
DYNACC User Exits .........................................................................10-17
DYNAEXIT EXCP Exit ....................................................................10-17
DYNEEXIT Catalog Logical Error Exit .....................................................10-18
Test Program Generator - DYNATEST ........................................................10-18
DYNATEST Functions ....................................................................10-18
DYNATEST Syntax ......................................................................10-19
DYNACC Version 2 Parameter List Contents ..................................................10-23
Chapter 11: CAIAUDIT in Prompt Mode

Primary Selection Panel (CUI-MENU) .......................................................... 11-1
AUDIT Data Set Browse Selection Panel (AUDT-1000) .......................................... 11-2
Selection Field Descriptions ............................................................... 11-2
AUDIT Data Set Directory Panel—All Products (AUDT-1100) .................................... 11-4
AUDIT Data Set Directory Panel—CA Dynam/T (AUDT-1900) ................................... 11-6
AUDIT Data Set Detail Panel—DYNAM/T (AUDT-1910) ......................................... 11-8
AUDIT Data Set Detail Panel—CA Dynam/T (AUDT-1920) ...................................... 11-9
AUDIT Data Set Directory Panel—CA Dynam/D (AUDT-1A00) .................................. 11-9
AUDIT Data Set Detail Panel—CA Dynam/D (AUDT-1A10) ....................................11-11
AUDIT Data Set Directory Panel—CA Dynam/FI (AUDT-1B00) .................................11-12
AUDIT Data Set Detail Panel—CA Dynam/FI (AUDT-1B10) ....................................11-14
CAIAUDIT in Command Mode ................................................................11-14
SELECT AUDITRECORDS ................................................................11-14
DISPLAY AUDIT .........................................................................11-15
Contents xiii
Batch Reporting for CAJAUDIT .............................................................. 11-17
Printable Fields ............................................................................ 11-17
CA DYNAM/T Header Fields ............................................................. 11-17
CA DYNAM/FI Header Fields ............................................................. 11-19
Chapter 12: Maintaining and Reporting on the Audit Trail

Maintaining the Audit Trail File ............................................................... 12-2
The Audit Trail Facility - AUDTUTIL ....................................................... 12-2
Audit Trail Logging ...................................................................... 12-2
Creating Audit Trail Records .............................................................. 12-2
Using the Catalog Recovery Facility ....................................................... 12-4
AUDTUTIL Control Statement Syntax ......................................................... 12-5
Maintenance Commands ..................................................................... 12-5
BACKUP Command ...................................................................... 12-6
CATALOG RECOVERY Command .......................................................... 12-7
DATASET Command .................................................................... 12-10
Reporting Commands ...................................................................... 12-11
Predefined Reports ..................................................................... 12-12
User-defined Reports ................................................................... 12-14
Multiple Reports in One Execution ....................................................... 12-14
FIELDS Command ...................................................................... 12-15
GENERATE Command ................................................................... 12-17
INPUT Command ....................................................................... 12-17
PROGRAM Command ................................................................... 12-19
REPORT Command ..................................................................... 12-20
CA Dynam/T Auditing ................................................................... 12-21
CA Dynam/D Auditing .................................................................. 12-21
CA Dynam/FI Auditing .................................................................. 12-22
SELECT Command ...................................................................... 12-22
TITLE Command ....................................................................... 12-26
Report Fields .............................................................................. 12-29
Chapter 13: DYNCOPY−CA Dynam File Utility Program

Operation .................................................................................. 13-1
Parameter Statements ...................................................................... 13-2
Parameters ................................................................................. 13-2
Sample JCL ................................................................................. 13-6
xiv User Guide

Appendix A: CA Dynam Report Examples
TDYNUTL Reports ............................................................................. A-4
DYNCAT Reports .............................................................................. A-9
TDYNVLT Reports ............................................................................ A-12
TDYNLIST Reports ........................................................................... A-14
TDYNSYNC Reports .......................................................................... A-16
Standard DYNPRINT Reports ................................................................. A-19
Appendix B: Audit Trail Report Examples

Audit Trail Reports ............................................................................ B-1
Glossary
Index
Contents xv
Chapter 1: Introduction
The CA Dynam for VSE software system is designed to provide a
comprehensive file management facility for the data center using all releases
of VSE currently supported by IBM. It is most effective when used as an
integrated system; its three products work together to efficiently manage tape
and disk files and provide file independence.
The following table summarizes the functions of the three products of CA

Dynam:
Subset System Purpose
CA Dynam/T Tape Management Tape data set management
CA Dynam/D Disk Management Disk data set management
CA Dynam/FI File Independence File independence between data and

user programs
This guide provides specific chapters detailing each product in the CA Dynam
family.
CA Dynam for VSE Products

CA Dynam for VSE is composed of three products for managing tapes, disks,
and file management.
CA Dynam/T Tape Management
CA Dynam/T helps you manage your tape library in the following ways:
Automatically controls tape data set usage and retention
Prevents active tape data sets from being scratched
Controls remote site tape movement and retention
CA Dynam/D Disk Management
CA Dynam/D manages your disk data sets in the following ways:
Allocates primary and secondary disk space
Permits automatic space release
Chapter 1: Introduction 1–1

Common Subset Features
Protects disk data sets from overlapping and deleting active files
Provides device independence for automatic conversion to new DASD

devices
CA Dynam/FI File Independence
CA Dynam/FI allows files to be switched from most sequential media to either

tape or disk in the following ways:
Dynamically reblocks files for specified devices.
Dynamically changes record formats.
Simulates unit-record to multi-record device types, such as card reader to

tape.

Certain utility and reporting programs were designed to support the combined
CA Dynam for VSE system. Each subset shares these programs. The programs
perform the following jobs:
Data set control using the CA Dynam Catalog File
Disaster recovery using the CA Dynam Audit Trail File
Interfacing with your data center's operating system
Reporting on CA Dynam and your operating system data
Creation of the CA Dynam Catalog is a requirement of CA Dynam/T, the tape

management subset. For information about creating the Audit and Catalog
files, see the "Maintaining Tape Files" chapter.
Throughout this guide, all comments that refer to the combined CA Dynam
system (commonly known as CA Dynam) apply equally to each of the three
products, regardless of their individual or combined installation. Individually,
the products are referred to by their commonly known names: CA Dynam/T,
CA Dynam/D, and CA Dynam/FI.
CA Dynam Catalog and Audit Trail Files
Use of the Catalog file is required for CA Dynam/T and is optional for CA
Dynam/D and CA Dynam/FI.
Use of the Audit Trail file is optional for all subset systems.
1–2 User Guide

Instructions for creating the Catalog and Audit Trail files are included in the
"Maintaining Tape Files" chapter of this guide. For more information about
Catalog and Audit Trail files, see the chapters "Accessing The Catalog" and
“Maintaining and Reporting On The Audit Trail.”
While the Audit Trail and Catalog files are optional features of CA Dynam/D
and CA Dynam/FI, their use provides for more effective management of your
data center's files.
Data Set Control
The CA Dynam Catalog is a common file shared by the three subset systems.
This disk file records information about every file controlled by CA Dynam in
much the same way a card catalog stores data about all the books in a library.
While your production jobs are running, CA Dynam automatically catalogs
pertinent data for each file that is opened or closed, including the following
details:
Volume serial number
Data set name and characteristics
Retention and location information
To ensure that this information is always current and accurate, CA Dynam is

constantly updating the Catalog. You can also update the Catalog manually
from the online screen transactions (CUI File Management) or from the batch
functions (DYNCAT) provided by CA Dynam.
Backup, Restore, and Recover
The CA Dynam Audit Trail file, stored on disk, provides a simple and efficient
means of protecting your data sets in the event of disaster. In addition to
logging data about production job files, it writes an Audit Trail record each
time the CA Dynam Catalog is updated from batch or online processing.
Whenever the need arises, you can backup, restore, and recover the CA
Dynam Catalog from the Audit Trail records.
Report on the Catalog
A common reporting facility, DYNPRINT, enables you to report on the CA

Dynam Catalog and disk VTOCs. It is the CA Dynam family's reporting tool
that lets you generate standard and customized reports using a subset of CA
Earl.

Start and Deactivate CA Dynam
Start and Deactivate CA Dynam

This section describes how to start and deactivate CA Dynam.
Start CA Dynam
To start the CA Dynam system, complete the following steps:
1. IPL your operating system.
2. Run the startup program, CASAUTIL, from an ASI PROC to initialize CA

Dynam.
CASAUTIL can be run at any time (not just from an ASI PROC), but the system
can protect data sets only when active. Thus, we recommend that it be started
as early in the IPL procedure as possible. For more information about
CASAUTIL, see the Programming Guide.
After activation, all the subsets that comprise the complete CA Dynam family
remain active.
Deactivate CA Dynam
To temporarily deactivate one or more of the subset systems, the profile phase
for the subsets can be deleted from the core image library or renamed, and an
IPL performed. Alternatively, through the use of CASAUTIL START statements,
various subsets of the CA Dynam family can be activated while leaving others
inactive, without requiring deletion or renaming of any library entries. For
more information, see the Programming Guide.
CA Dynam Extended Operator Communication Facility

To implement extended operator communications support, CA Dynam provides
an interface through attention routine (AR) commands. You can enter AR
commands only when CA Dynam is active; the commands are effective
immediately. Commands relevant to particular products are, of course, only
active if that product is installed.
CA-CP | CP Passes a VM command to the CP processor and displays the returned

message. For example:
CA-CP QUERY STORAGE

CADS335 STORAGE = 4096K
1–4 User Guide

Critical System Function Integrity
Any CP command valid for the userid's privilege class(es) will be processed.
For instance, this facility could be used to attach or detach tape devices.
CA-CANcl nn and CA-FLUSH nn

These CANCEL-DELAY commands enable cancellation for partition nn.
CASTART fn Starts partitions, either static or dynamic, which were previously stopped by
CA Dynam.
CA? The STATUS commands display information about the CPU, operating system,
and CA products currently active in the system, as follows:
AR 0015 CADS330I *---- CA - CA - CA - CA - CA - CA - CA - CA ----*

AR 0015 CADS330I * *
AR 0015 CADS330I * CPU=A (FF00005496720000) z/VSE 4.1 *
AR 0015 CADS330I * VSE/AF 5686-CF8 8.1.0 USERID=Z.VSE.SUPI *
AR 0015 CADS330I * *
AR 0015 CADS330I * VM/ESA USERID=JHNMIN 16M *
AR 0015 CADS330I * *
AR 0015 CADS330I * CA-CIS Srvlevel 02 0008 CGN *
AR 0015 CADS330I * ESA/SYSTEM ADAPTER 6.1 02 0008 AY5 *
AR 0015 CADS330I * CAICUI 1.4 02 0008 CGN *
AR 0015 CADS330I * CAIAUDIT 1.4 02 0008 AAU *
AR 0015 CADS330I *------------------------------------------------*
AR 0015 CADS330I * Product Release Service Level *
AR 0015 CADS330I * -------------- ------- ------------- *
AR 0015 CADS330I * CA-CATLG/MGMT 6.0 02 0008 AY3 *
AR 0015 CADS330I * CA DYNAM/D 7.1 00 0012 ADD *
AR 0015 CADS330I * CA DYNAM/T 7.1 00 0012 ATD *
AR 0015 CADS330I * CA DYNAM/FI 7.1 00 0012 AFD *
AR 0015 CADS330I * *
AR 0015 CADS330I *------------------------------------------------*
Critical System Function Integrity

To ensure the integrity of certain critical system functions (such as CATALOG
DEQUEUE), the System Adapter provides support for a CANCEL-DELAY
function, which uses a standard IBM facility to prevent operator-generated
cancellation of a job from becoming effective until the critical function has
completed.
This facility only affects cancellations originating with the operator (not those
generated by program-check interruption, I/O errors or other causes) and
delays; it does not prevent operator cancellation. The System Adapter ensures
that critical CA Dynam system tasks, such as CATALOG DEQUEUE, complete
without interruption, preventing Catalog corruption which might otherwise
occur.

System Adapter CANCEL-DELAY Support
System Adapter CANCEL-DELAY Support

This support is provided automatically without user intervention. When an
operator issues the CANCEL BG command, if CANCEL-DELAY is in effect, the
task is set to be canceled as usual; however, the cancellation does not occur
until the CA Dynam function in progress has completed. If the POWER/VS(E)
PFLUSH (F BG) command is issued while CANCEL-DELAY is in effect, message
CADS327E PFLUSH IGNORED is issued, and the command is ignored.
In either case, no further action should be taken until a reasonable time has
elapsed to permit the critical function to complete. If it is suspected that the
partition which has been canceled or flushed is in an unending loop or wait
condition, an override to the CANCEL-DELAY facility has been provided. The
operator can enter, to the attention routing (AR), any one of the following:
CA-CANCL nn or
CA-CAN nn or
CA-FLUSH nn where nn = partition ID of the partition to be canceled.
These commands disable the CANCEL-DELAY condition if it is in effect for the

partition specified and allow the previously entered CANCEL to take effect.
Note that these commands do not cause the job to be canceled, but merely
allow the cancellation to proceed.
TLBL/DLBL Extensions
CA Dynam products extend the TLBL and DLBL statements so that CA Dynam
processing options can be defined. The following charts summarize the
extensions.
TLBL Extensions
The TLBL Extensions include Standard TLBL and TLBL with CA Dynam
Extensions.
Standard TLBL
The Standard TLBL Extensions include the following:
// TLBL filename,'file-id', [ date ]

[ ,volser ]
[ ,volseq ]
[ ,fileseq ]
[ ,generation ]
[ ,version ]
1–6 User Guide

TLBL with CA Dynam Extensions
The TLBL with CA Dynam Extensions include the following:
// TLBL filename,'file-id.(gen)Topt', [ date ]

[ ,volser ]
[ ,volseq ]
[ ,fileseq ]
[ ,generation ]
[ ,Topt ]
[ ,FIopt ... ]
Detailed descriptions of these parameters are presented below.
filename 1—7 alphanumeric characters. Name of file in program DTF.
file-id 1—44 alphanumeric characters enclosed in single quotes. Equals data set
name in CA Dynam Catalog.
File-id can contain the following extensions:

Relative generation at end of file-id, enclosed in parentheses and preceded
by period.
For example:
// TLBL FILEX,'DSNAME.(-1)'
CA Dynam/T tape processing option codes at end of file-id, separated by

commas.
For example:
// TLBL FILEX,'DSNAME,W,H'
R Release at CLOSE
U Unload at CLOSE
W Rewind at CLOSE
N No rewind at CLOSE
A Alter filename at OPEN to SYS0nnn
C Catalog data set at OPEN
D Drop TLBL at CLOSE
H Hold logical unit assignment
I Identify DTF HDR1 information
P Prohibit dynamic LUB allocation
Z Multitask
L Long tape
ML Medium long tape

M Medium tape
MS Medium short tape
S Short tape
XS Extra short tape
30 1600 BPI (streaming, high speed, short gap)
50 1600 BPI (start stop, high speed, long gap)
60 1600 BPI (start stop, low speed, short gap)
90 1600 BPI (streaming, high speed, long gap)
C0 1600 BPI phase encoding mode
C8 800 BPI NRZI mode

D0 6250 BPI
D8 Tape cartridge
00 Tape cartridge—buffered write mode
00E Tape cartridge—buffered write mode (3490E)
00M Tape cartridge—buffered write mode (3590)
00MH Tape cartridge—buffered write mode (3590H)
00W Tape cartridge—buffered write mode (3592)
00WE Tape cartridge—buffered write mode (3592E)
03WE Tape cartridge—encrypted buffered write mode (3592E)
08 Tape cartridge—data compaction with buffered write
08E Tape cartridge—data compaction with buffered write (3490E)
08M Tape cartridge—data compaction with buffered write (3590)
08MH Tape cartridge—data compaction with buffered write (3590H)
08W Tape cartridge—data compaction with buffered write (3592)
08WE Tape cartridge—data compaction with buffered write (3592E)
0BWE Tape cartridge—encrypted data compaction with buffered write

(3592E)
20 Tape cartridge—unbuffered write mode
20E Tape cartridge—unbuffered write mode (3490E)
20M Tape cartridge—unbuffered write mode (3590)
20MH Tape cartridge—unbuffered write mode (3590H)
20W Tape cartridge—unbuffered write mode (3592)
20WE Tape cartridge—unbuffered write mode (3592E)
23WE Tape cartridge—encrypted unbuffered write mode (3592E)
1–8 User Guide

28 Tape cartridge—data compaction with unbuffered write
28E Tape cartridge—data compaction with unbuffered write

(3490E)
28M Tape cartridge—data compaction with unbuffered write (3590)
28MH Tape cartridge—data compaction with unbuffered write

(3590H)
28W Tape cartridge—data compaction with unbuffered write (3592)
28WE Tape cartridge—data compaction with unbuffered write

(3592E)
2BWE Tape cartridge—encrypted data compaction with unbuffered

write (3592E)
42 1600 BPI (9348 buffered write mode)
62 1600 BPI (9348 unbuffered write mode)
C2 6250 BPI (9348 buffered write mode)
E2 6250 BPI (9348 unbuffered write mode)
S:nnn Logical unit override and assignment to dummy device at JCL

time
JX Delete controlled file at end of job after processing file
SX Delete controlled file at end of step after processing file
OW=xx Override owner id
Partition, CPU independence
Add to file-id To Specify
== partition independence
@ or CPU— CPU independence
==@ CPU and partition independence
Examples
// TLBL FILEX,'==WORK'
// TLBL FILEX,'WORK=='
Automatic multifile data set indicator (3 asterisks within the file-id)
Note: If you specify any generation, options, or independence, then File-id

must adhere to the following:
− File-id can contain only alphabetic and numeric characters.

− Total length of file-id, including generation and options, cannot exceed

59.
− Relative generation must precede option codes.
− Parentheses are supported.
If the actual data set name length (after the options are stripped) is
greater than 17, the last 17 significant characters are written to the HDR1
label on the tape.
date Expiration date (yy/ddd or yyyy/ddd) or number of days retention (nnnn). This
date is calculated using the greatest number of retention days specified in any
one of the following places:
The catalog for the data set

The TLBL
The default from the DYNAM/T option record
volser Volume serial number of first input volume. Omit for output.
volseq Volume sequence number of specific volume of multivolume data set. Omit for
output.
fileseq The file sequence number field is not used by CA DYNAM/T and should be
omitted in all cases. The multifile data set control provided by CA DYNAM/T is
based upon the data set name and control records in the Catalog.
gen Specific version of input data set; 1-4 digits. Place generation number here
instead of within file-id if the file-id is too large or contains special symbols.
Gen=nnn Specific, absolute generation number assigned to a new version of a data set.
Entering this generation number lets you to access a particular data set
version for input. Place the absolute generation number here instead of within
file-id if the file-id is too large or contains special symbols. Processing options
must be separated by commas. If the first option is a keyword and IBM
options are omitted, at least 1 comma after file-id is required; otherwise, at
least 2 commas are needed.
Topt CA Dynam/T numeric processing options. Place option codes here instead of
within file-id if the file-id is too large or contains special symbols.
1 Rewind at CLOSE
2 Unload at CLOSE
4 Release at CLOSE
8 Hold logical unit assignment
16 Drop TLBL at CLOSE
32 No rewind at CLOSE
1–10 User Guide

64 Alter filename at OPEN to SYS0nnn
Multiple numeric options can be specified by adding the values of the options
and placing the sum in this field. If you specify both numeric and alphabetic
options, the numeric options are ignored.
FIopt CA Dynam/FI processing options, separated by commas. If first option is a

keyword and IBM options are omitted, at least 1 comma after file-id is
required; otherwise, at least 2 commas are needed.
Option Description
BLKSZ={nnnnn|OPT} Block size
CONCat File concatenation
CONCAT={ALL|nnn} File concatenation
FIOPT=(option,option...) Options:
AUDIT Audit support
NOCNTRL Ignore CNTRL requests
NORELSE Ignore RELSE requests
NOTM No tape mark
NOTRUNC Ignore TRUNC requests
RELEASE Release LUB at CLOSE
RUN|NORWD Rewind/unload at CLOSE
SB|DB Single/double buffer
SKR Skip rewind at OPEN
SL|UL Standard/unlabeled
IGNore ASSGN IGNORE
LRECL=nnnnn Record length
NODISK No operator switching
NOFI No FI processing
RECFM={F|FB|V|VB|U} Record format

SRTCORE=nnnnnn Storage for sort
SORTIN={(keys)|keyname} Keys to sort on input
SORTOUT={(keys)|keyname} Keys to sort on output
SORTWRK=(filename,SYSnnn) Work file for sort
SYSnnn Logical unit
DLBL Extensions
Standard DLBL
// DLBL filename,'file-id', [ date ]

[ ,code ]
[ ,DSF ]
[ ,BUFSP=n ]
[ ,CAT=x ]
[ ,BLKSIZE=n ]
[ ,CISIZE=n ]
[ ,DISP=x ]
[ ,RECORDS=n ]
[ ,RECSIZE=n ]
DLBL with CA Dynam Extensions
// DLBL filename,'file-id(Dopt)', [ date ]

[ ,code ]
[ ,DSF ]
[ ,BUFSP=n ]
[ ,CAT=x ]
[ ,BLKSIZE=n ]
[ ,CISIZE=n ]
[ ,DISP=x ]
[ ,RECORDS=n ]
[ ,RECSIZE=n ]
[ ,FIopt ... ]
filename 1—7 alphanumeric characters. Name of file in program DTF.
1–12 User Guide

file-id 1—44 alphanumeric characters enclosed in single quotes. Equals data set
name in CA Dynam Catalog.
File-id can contain the following extensions:
CA Dynam/D disk processing option codes, separated by commas with no

intervening blanks and enclosed in parentheses (or beginning and ending
symbols as defined in the DDOPTS option record).
Example
// DLBL SDDOUT,'DISK.FILE(A,I)'
File-id length, including option codes, cannot be greater than 59.

A Align on cylinder boundary
B Bypass AVR and DASD device independence
C Catalog data set
D Delete file from VTOC at input close
D1 Do diagnostic trace of CA Dynam processing
E Enqueue file opened for input, update or output
F Fragment space allocation
G= Access this absolute generation number
G# Access this generation number
G- Access this relative generation number
I Send messages to SYSLST
IE ISAM extend
K Keep SD file after close
L Lock file for read-only usage
M Send messages to SYSLOG
N Do not truncate at close
NA No automatic secondary allocation
NF Do not fragment
O Access existing file; do not reallocate
S Use same space for SORTIN/SORTOUT
S:nnn Override with this SYS number
T Truncate ISAM extent or SD work file
W Delete SORTWK file at close

X Delete file from VTOC at close
JX Delete controlled file at end of job after processing file
SX Delete controlled file at end of step after processing file
Partition, CPU independence
Add to file-id To Specify
== Partition independence
@ or CPU— CPU independence
=== CPU & partition independence
For temporary data sets, prefix the 1- to 8-character FILEID with ##.
date Expiration date (yy/ddd or yyyy/ddd) or number of days retention (nnnn).
Value of Dates Influence on Value Used
Retention date is not 0 CA Dynam uses that value

and expiration date is
greater than the current
date
Retention date is 0 or CA Dynam uses the default value defined in

expiration date is less DYNAM/D option record
than or equal to the
current date
Retention date is omitted CA Dynam uses the VSE default of 7 days

on DLBL and in the
Catalog
code IBM file type code, two to four alphabetic characters. Omit if data set is
defined to CA Dynam Catalog. Examples are SD, DA, DU, ISC, ISE, and VSAM.
DSF, BUFSP=n, CAT=x, BLKSIZE=n, CISIZE=n, DISP=x, RECORDS=n, RECSIZE=n

IBM processing options for DASD files. For more information, see the IBM
documentation.
FIopt CA Dynam/FI processing options, separated by commas. If first option is a

keyword and IBM options are omitted, at least 1 comma after file-id is
required; otherwise, at least 3 commas are needed.
BLKSZ={nnnnn|OPT} Block size
CONCat File concatenation
CONCAT={nnn|ALL} File concatenation
1–14 User Guide

Delete Label Option Blocks—RESET Statement
FIOPT=(option,option...) Options:
AUDIT Audit support
NOCNTRL Ignore CNTRL requests
NORELSE Ignore RELSE requests
NOTRUNC Ignore TRUNC requests
RELEASE Release LUB at CLOSE
SB|DB Single/double buffer
VERIFY Use DTF VERIFY option
FIVSAM|NOFIVSAM VSAM DLBL support
IGNore ASSGN IGNORE
LRECL=nnnnn Record length
MAXCI=nnnnn Maximum CI size
NOFI No FI processing
NOTAPE No operator switching
RECFM={F|FB|V|VB|U} Record format
SRTCORE=nnnnnn Storage for sort
SORTIN={(keys)|keyname} Keys to sort on input
SORTOUT={(keys)|keyname} Keys to sort on output
SORTWRK=(filename,SYSnnn) Work file for sort
SYSnnn Logical unit

CA Dynam label option blocks are normally kept for as long as the label they
are associated with exists on the VSE label area. You may, however, strip
(nullify) the CA Dynam options entered this way, without submitting another
TLBL or DLBL statement. You can do this using the RESET statement.

RESET Format
[//] RESET FILE={*filename|filename|ALL}
FILE= Operands are:
*Filename Deletes the label option block (TLBL or DLBL) for every
group (user, partition, system) for which this file is a
member.
filename Deletes the user label option block for this file.
1–16 User Guide

Chapter 2: Maintaining Tape Files
CA Dynam/T is a software system providing tape data set management for
IBM and compatible mainframe computers operating under all releases of VSE
currently supported by IBM. This chapter addresses the basic components of
CA Dynam/T. For information about using the utilities that support tape
management, see the chapter “Supporting Tape File Management.”
Preparing for CA Dynam/T
Audit Data Set
The CA Dynam Audit facility records information concerning the following:
Every OPEN or CLOSE tape
Every modification to the Catalog
Audit information requested by CA Dynam/FI and CA Dynam/D (if installed

with audit support)
Defining the Audit Data Set
After you have selected the Audit option, you must first define and format the
CA Dynam Audit Data Set (audit trail). The Audit facility is shared by all
components of CA Dynam; therefore, you have to submit only one label and
initialize it only once.
Use the file name CAIAUDT to define the Audit Data Set. The system accesses
the data set using direct physical IOCS. However, define it as an SD file for
label purposes.
Locating the Audit Data Set
Review the Audit Trail Facility chapter before determining the location and size
of the data set.
Place the data set on a different disk volume from the Catalog file; if a
hardware failure destroys the Catalog, the Audit data set will still be available
for recovery.
For information about labeling the Audit data set, see the Programming Guide.
Chapter 2: Maintaining Tape Files 2–1

Catalog File
The Catalog file controls the tape library. It is a direct access file shared by all
CA Dynam software components.
The Catalog file stores all information necessary to perform the following
actions:
Select the correct input tape
Allocate a valid scratch tape
Report on controlled tape processing
The Catalog file is also used by the following:

CA Dynam/D for storing information about the management of disk files
CA Dynam/FI for storing information about file independence
Defining the Catalog File
Use the file name CAICATL to define the CA Dynam Catalog. The system
directly accesses the Catalog with physical IOCS; however, define the Catalog
as an SD file for label purposes.
Locating the Catalog File
Review the Programming Guide before deciding where to place the Catalog
file, its size, and which logical unit will access it.
Audit and Catalog Data Sets
For more information about the Audit and Catalog files, see the chapters
"Accessing the Catalog" and "Maintaining and Reporting on the Audit Trail."
Establishing Data Sets
The batch program, DYNCAT, and the online program, CUI File Management,,
establish and define to the Catalog those data sets that CA Dynam/T is to
control. You can also define data sets to the Catalog at output OPEN through
use of the optional automatic cataloging facility.
A data set must have a unique name. You can include retention information; a
default can be specified in the DYNAM/T option record.
2–2 User Guide

Example:
Defining a data set
// JOB DEFINE A DATASET TO THE CATALOG

// EXEC DYNCAT, SIZE=128K
DEFINE 'DYNAM/T BACKUP' NGEN=003 RETAIN=003
/*
/&
This creates a data set named DYNAM/T BACKUP. When members of this data
set are created, they are retained for at least three generations and for at
least three days.
A tape data set name is composed of up to 44 alphabetic or numeric

characters and can include blanks and periods. Do not use any other special
characters. You can incorporate your installation's existing data set naming
conventions by simply entering the existing names and retention information
into the Catalog. If your installation has no existing conventions, it is highly
recommended that conventions be formulated and used as a part of the
CA Dynam/T implementation process.
You can enter existing generations of data sets with the DYNCAT ADD
command.
Initializing Scratch Tapes
If you will be using tapes as output for CA Dynam/T controlled data sets,
initially define them to the Catalog as scratch tapes by doing any one of the
following:
By issuing the DYNCAT INT (or INTR) command

Through the online initialization facility at output OPEN time
When a volume is entered into the Catalog, a search is made to verify that it
has a unique volume serial number. Recognition characters are placed in the
HDR1 label to identify it as a CA Dynam/T controlled tape. You can use the
batch program TDYNLBL to create block printed serial number labels. When
these are placed on initialized tapes, they enable the operator to easily
recognize tapes which are under the control of CA Dynam/T. For more
information about TDYNLBL, see the chapter "Supporting Tape File
Management."

Examples:
Initialization of scratch tapes with DYNCAT
DYNCAT is executed from the console and the tapes on drives 299 and 29A are
initialized and rewound. The absence of a volume serial number in the
CADT009D message indicates that the tapes were originally unlabeled. The
operator enters the new volume serial numbers 100732 and 100733 and
enters EOB/END in response to the repeated CADT009D message, to indicate
that those numbers are to be used.
BG // JOB DYNCAT INITIALIZE TAPES

DATE 01/22/00,CLOCK 19/51/53
BG // EXEC DYNCAT
BG CADC800D ENTER DYNCAT COMMAND
BG INTR 299
BG CADT009D VERIFY VOLUME NO=
BG 100732
BG CADT009D VERIFY VOLUME NO=100732
BG
BG CADC821I 299 100732 INITIALIZED
BG INTR 29A
BG CADT009D VERIFY VOLUME NO=
BG 100733
BG
BG CADC821I 29A 100733 INITIALIZED
BG
BG READY FOR COMMUNICATIONS
BG
BG EOJ DYNCAT
DATE 01/22/00,CLOCK 19/53/08,DURATION 00/01/14
Initialization of scratch tape at OPEN time
A CADT008D MOUNT message is issued requesting a scratch tape. The

operator responds with the tape drive address, 299, which contains a labeled,
but non-CA Dynam/T controlled volume, number 100867. The operator enters
EOB/END to indicate that the existing number should be used.
BG CADT008D MOUNT SCRATCH TAPEOUT SYS011 DSN=AR TRANS

BG 299
BG CADT009D VERIFY NO=100867
BG
BG CADT007I **** LABEL TAPEOUT SYS011=299 100867 0001 *AR TRANS*
BG CADT031I *CLOSED* TAPEOUT SYS011=299 100867 AR TRANS BLK=12
2–4 User Guide

Modifying JCL
The final step in preparing to use CA Dynam/T includes the following JCL
changes:
1. In order for the system to recognize a tape file that is to be controlled, the
FILE-ID field of the TLBL must match a data set name in the Catalog.
− Such TLBLs already exist in installations with existing conventions and

standard labeled tape files. However, review the JCL to make sure that
each data set name uniquely identifies one tape data set.
− For installations without existing naming conventions or whose tape

files are unlabeled, a TLBL must be created referencing a data set
name in the Catalog.
2. Remove all logical unit assignments to tape drives to enable the Automatic
Volume Recognition facility to function. This change is not required
because CA Dynam/T respects existing assignments. However, not using
this facility defeats the purpose of an automated tape management
system.
The following example displays a job stream before and after conversion to
CA Dynam/T control:
Before Conversion
// JOB LOAD AND EDIT PR TIME CARDS

// ASSGN SYS008,280 UNLABELED TC TAPE OUT
// EXEC PRTPLD
...TIME CARD INPUT...
/*
// ASSGN SYS008,280 UNLABELED TC TAPE IN
// ASSGN SYS010,281
// TLBL SYS010,'TIME CARDS' EDIT TC FILE
// ASSGN SYS012,282
// TLBL SYS012,'MASTER FILE' MASTER FILE IN FOR EDIT
// EXEC PREDIT
/*
/&

Implementing CA Dynam/T
After Conversion
// JOB LOAD AND EDIT PR TIME CARDS

// TLBL SYS008,'PR TIME CARDS'
// EXEC PRTPLD
...TIME CARD INPUT...
/*
// TLBL SYS008,'PR TIME CARDS'
// TLBL SYS010,'PR TIME CARDS EDT'
// TLBL SYS012,'PR MASTER'
// EXEC PREDIT
/*
/&
The // ASSGN statements are removed to enable AVR. Also, the Forced
Labeled Tape facility is used to change the file on SYS008 from unlabeled to
standard label so that it can be controlled. Finally, the data set names are
standardized to begin with PR, thus identifying these as PAYROLL data sets.
Implementing CA Dynam/T
You can implement CA Dynam/T all at once or gradually, depending upon the
needs of your installation. However, one specific person should be responsible
for coordinating the implementation. Convert a few frequently run jobs to
allow the operations staff to become accustomed to CA Dynam; usually one to
two weeks is sufficient. After the operators are familiar with the system, it can
be implemented as quickly as the data sets can be cataloged. If a different
automated file management system was previously used, operators will be
familiar with the concepts involved and will only need to learn the new
message formats.
The following are the implementation requirements:
All tapes must be assigned unique volume serial numbers. They should be
standard label tapes. After the system is activated, convert any unlabeled
tapes in use (created by other than 1400 programs) to standard label
tapes by including TLBL statements for these files in the JCL. The next
time the file is created it will be a standard label file.
All file names in the TLBL statements must uniquely identify a data file.
The same file name cannot refer to two different data sets. Review all JCL
to make sure these requirements are met.
Appropriate data set names for each tape file must be entered in the
Catalog using the DEFINE command of the DYNCAT program.
2–6 User Guide

Using CA Dynam/T
While it is not a requirement that ASSGN statements for tape files be

removed from JCL, it permits full use of Automatic Volume Recognition
(AVR). ASSGN statements for SORT, Westinghouse, Panvalet, and other
utilities that determine DVCTYP before OPEN must be replaced with the
ASSGN function of TDYNASN.
Tapes must be entered in the Catalog to indicate which volumes are under
control. A unique identifier (TC) is placed in the SYSTEM CODE field of the
VOL1 label of the tape volume. The identifier is written on the tape either
with the DYNCAT INT or INTR commands, or when CA Dynam/T requests
an output scratch tape in normal processing.
In either case, the operator should look at the volume serial number
displayed on the console with the external label on the tape. A new label
should be placed on each tape as it is brought under CA Dynam/T control
so that the operator knows at a glance whether a tape has been initialized.
A utility label print program (TDYNLBL) is provided for this purpose.
Bring 1400 Emulator tapes and system logical unit tape files under
CA Dynam/T control with the TDYNASN OPEN and CLOSE commands.
Using CA Dynam/T
Controlling Data Sets
CA Dynam/T controls and protects data sets by intercepting all OPEN and
CLOSE requests issued for tape files. Using information in the Catalog file,
CA Dynam/T verifies that the correct tape is being used, as follows:
For input OPEN requests, a specific volume serial number is required. If it

is not already mounted, a message is issued to the operator instructing
him to mount the required volume.
For output OPEN requests, a tape that has been initialized under
CA Dynam/T control and listed in the file in scratch status is required.
CA Dynam/T issues a message requesting that a scratch tape be mounted
if it does not find one already mounted. Specific responses to these
messages are discussed later.
If CA Dynam/T has been activated but is unable to access the Catalog for
any reason, it makes sure that no file is written to a volume that has been
initialized to CA Dynam/T, as determined by the special identification
characters. This protects controlled data sets from being overwritten even
in exceptional situations.
In response to OPEN requests for tape files that have not been placed
under CA Dynam/T control.

Using CA Dynam/T
CA Dynam/T checks that the logical unit being opened has been assigned
to a tape drive to prevent abnormal termination with the IBM message
4883I INVALID LOGICAL UNIT (input).
CA Dynam/T makes sure that the specified drive does not contain a tape
that is an active generation of a controlled data set (output).
Protecting Controlled Data Sets
CA Dynam/T does not permit an active tape that is a member of a controlled

data set to be opened for use as an output tape under any circumstances.
When the program issues a CLOSE for the file, CA Dynam/T updates the
Catalog for output-controlled data sets to indicate that a new generation has
been created.
CA Dynam/T Support Exceptions
CA Dynam/T controls and protects data sets through OPEN/CLOSE intercepts.

Therefore, it does not support the following:
Programs and utility packages that do not open and close files (for
example, DITTO)
Programs that perform physical I/O operations that violate VSE LIOCS
conventions
CA Dynam/T is designed to process and control IBM standard labeled and

unlabeled tape files. It does not support the following tape files:
Tape files with nonstandard or user label processing
DTFMT TYPE=WORK
Tape files opened as input, then processed as output
Establishing Retention Characteristics
Data set retention characteristics tell CA Dynam the following:
How long to retain each generation?
Under what conditions can a generation be scratched?
CA Dynam/T is flexible regarding data set retention. You can use the various
retention methods it provides individually or in combination. You can also
modify individual generations within a data set to allow for exceptional or
permanent retention independent of the characteristics of the data set as a
whole.
2–8 User Guide

Using CA Dynam/T
Establish the retention characteristics with the DYNCAT DEFINE command. You
can alter them with the DYNCAT ALTER command.
Before the system permits a generation to be scratched, the generation must

be eligible for scratch under all the retention schemes associated with the data
set.
Data Set Retention Options
You may retain a data set for a specific number of the following:
Days, or until a specific expiration date has been reached (date retention)
Generations
AS-OF-DATE cycles (also known as PERIOD ENDING DATE cycles)
Days since last access
Date Retention
Date retention is based upon an expiration date calculated from the creation
date and the number of retention days specified either in the Catalog or on the
TLBL statement used in the creation of the generation.
If retention days are specified in both the Catalog and the TLBL, the larger
number is used. This provides the longest possible retention. When the
expiration date is reached, the version is eligible for scratch.
Generation Retention
Generation retention is based on the number of cycles specified in the Catalog.

For example, if four cycles have been created but the Catalog specifies only
three, the fourth (the oldest) becomes eligible for scratch.
AS-OF-DATE Retention
CA Dynam/T is the only tape management system that provides AS-OF-DATE

retention. It is based on the number of AS-OF-DATE cycles specified in the
Catalog.
The AS-OF-DATE is a characteristic of each version of a data set. When a

version is created for a data set with AS-OF-DATE control, the AS-OF-DATE for
that version is established in any one of the following ways:
Permanently with the DYNCAT DEFINE or ALTER commands
According to the partition communications region date, as set by // DATE

mm/dd/yy, if no permanent AS-OF-DATE characteristic has been set

Using CA Dynam/T
When the DYNCAT SCRATCH command is performed to scratch eligible data

set versions, if a data set has AS-OF-DATE cycles specified, as many versions
will be retained as have AS-OF-DATES different from the next most current
version.
Days Since Last Access Retention
Each time you access a version, CA Dynam updates the last access date field
in the Catalog. This value is compared with the current date. If the last access
date plus the NOACC value (number of days that version is to be retained after
last access) is less than the current date, the version is eligible for scratch
under this retention option.
Modifying Retention Characteristics
The DYNCAT ALTER command enables you to modify the existing retention
characteristics of a data set.
For example, this ALTER command assures that a particular version will not be
scratched until December 31, 2020.
ALTER 'PR MASTER' VERSION=1 EXPDATE=12/31/2020
The expiration date of version 1 of the data set is changed to December 31,
2020. DYNCAT accepts American and European date formats. For more
information about acceptable dates, see the DYNCAT ALTER command.
Scratching Eligible Data Set Versions
The SCRATCH command of the batch program DYNCAT analyzes each data set
and scratches eligible versions. A version remains a protected member of the
data set until the SCRATCH command is run, even if its expiration date has
passed. This lets you control the process by which tapes are returned to the
scratch pool.
However, a version of a data set becomes a scratch tape available for

immediate use if the following conditions are met:
You run the DYNCAT DELETE command.
For example:
DELETE 'PR MASTER' VERSION=1

or
DELETE 'PR MASTER' VOLSER=(845)
A version of a released WORK data set becomes a scratch.
2–10 User Guide

Using CA Dynam/T
The automatic scratch option (TAPEOPT=AUTOSCR) is specified for the

data set (any expired versions are automatically scratched when a new
version is closed and cataloged)
The TAPEOPT=ROTATE option is specified for the data set (the oldest
version is used for output when a new version is created)
In order to explain how the various retention schemes work, we will refer to
the following sample DATA SET NAME LISTING. An asterisk beside the version
number indicates that the version is eligible for scratch.
1. Notice the multifile data sets AR.DESC.1, AR.DESC.2 and, AR.DESC.3.

Retention criteria for these data sets are simply two cycles (NGEN). Zero
days retention and no AS-OF-DATE retention are specified. Version three is
eligible for scratch, because three cycles exist.
2. Also note data set AR.MASTER, which has retention criteria of zero cycles,
30 days, and three AS-OF-DATE cycles (PEDCYC). The current AS-OF-
DATE for the data set is 12/31/**. Also, the AS-OF-DATE for each version
is 12/31/20, as indicated on each version line (PED). All the version AS-
OF-DATES are considered members of the same AS-OF-DATE cycle,
because all the version AS-OF-DATES are identical. Therefore, only the
most current will be retained because of AS-OF-DATE. Only data set
versions less than 30 days old will be retained, because 30 days retention
has been specified.
3. Finally, note data set AR.BACKUP, which has 2 cycles and 4 AS-OF-DATE
cycles retention. Versions 1 and 2 will always be retained because of the
2-cycle retention; (Version 1 would also be retained because of AS-OF-
DATE retention). Version 3 is a member of a different AS-OF-DATE group
(12/31/20), so it will be retained.

Using CA Dynam/T
Data Set Name Listing

DATA SET NAME LISTING as DYNAM/T RETENTION EXAMPLE
CA DATA SET NAME LISTING TDYNUTL-01 PAGE 1
CA Dynam 7.1 0709YD000 23 JAN 2007 23.42.29
DSN VLT VOLSER VER VOL FIL OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION------------ PED PED TAPE MSG
ID ID ID DAY NGEN NOAC EXP-DATE DATE TIME CPU PT CUU MODE LEN JOB-NAME CYC ERRS
AR.BACKUP
ACCTS RECEIVABLE BACKUP
A 100486 1 1 0 2 01/20/20 01/20/20 23.42 A BG ARBACKUP 4 01/31/20
B 100423 2 1 0 2 01/06/20 01/06/20 23.42 A BG ARBACKUP 4 01/31/20
C 100659 3 1 0 2 12/24/19 12/24/19 23.42 A BG ARBACKUP 4 12/31/19
AR.DESC.1 MF
ACCTS RECEIVABLE DESCRIPTION - FILE 1
A 100744 1 1 1 0 2 01/21/20 01/21/20 23.41 A BG ARDESCUP 01/23/20
A 100723 2 1 1 0 2 01/14/20 01/14/20 23.41 A BG ARDESCUP 01/23/20
A 009876 3* 1 1 0 2 01/07/20 01/07/20 23.41 A BG ARDESCUP 01/23/20
AR.DESC.2 MF
A 100744 1 1 2 0 2 01/21/20 01/21/20 23.41 A BG ARDESCUP 01/23/20
A 100723 2 1 2 0 2 01/14/20 01/14/20 23.41 A BG ARDESCUP 01/23/20
A 009876 3* 1 2 0 2 01/07/20 01/07/20 23.41 A BG ARDESCUP 01/23/20
AR.DESC.3 MF
A 100744 1 1 3 0 2 01/21/20 01/21/20 23.41 A BG ARDESCUP 01/23/20
A 100723 2 1 3 0 2 01/14/20 01/14/20 23.41 A BG ARDESCUP 01/23/20
A 009876 3* 1 3 0 2 01/07/20 01/07/20 23.41 A BG ARDESCUP 01/23/20
AR.MASTER
ACCTS RECEIVABLE MASTER FILE
A 100733 1 1 30 01/29/20 12/30/19 23.41 A BG ARMSTRUP 3 12/31/19
A 080655 2* 1 30 12/29/19 11/29/19 23.41 A BG ARMSTRUP 3 12/31/19
A 051234 3* 1 30 11/30/19 10/31/19 23.41 A BG ARMSTRUP 3 12/31/19
A 099976 4* 1 30 10/30/19 09/30/19 23.41 A BG ARMSTRUP 3 12/31/19
Automatic Volume Recognition (AVR)
The Automatic Volume Recognition facility (AVR) of CA Dynam/T frees

controlled tape files from specific physical unit assignments in JCL and allows
the operator greater flexibility in using the tape resources available.
Activating AVR
AVR is activated when a program for a controlled tape file issues an OPEN
request and the logical unit to be used (SYS-number) is not assigned to a tape
device. It can be either assigned to a device other than tape or unassigned.
AVR is not activated if the logical unit is assigned IGN. In that case,
CA Dynam/T performs no processing for this file; normal IGNORE processing
occurs.
2–12 User Guide

Using CA Dynam/T
CA Dynam/T determines which tape is required (either a specific volume for an

input file, or a scratch tape for an output file) and searches all available tape
drives for the tape. A tape drive is considered available if all of the following
conditions are satisfied:
The unit is in DVCUP status.
The unit is not assigned to any logical unit in any partition, either through
a temporary or standard assignment.
The unit is a member of a defined POOL of tape drives available for the
CPU and partition issuing the OPEN (see DTPOOL option record), or no
tape drive pools have been defined in the DTPOOL option record.
The unit is not locked against cross-CPU use by CA Dynam/T (see DTLOCK
option record).
The unit is physically accessible (has not been DETACHed under VM, or has
not been placed offline).
The unit is ready and contains a tape that is at load point.
The tape on the unit has a recording density compatible with the tape
drive, and no I/O errors occur when the VOL1/HDR1 labels are read.
The tape unit is of the same type as the tape currently being opened.
If all of the above conditions are met, CA Dynam/T reads the tape on the unit
to determine if it is the desired volume. Depending on whether it is the desired
volume, CA Dynam/T does the following:
If it is the desired volume, the assignment is made, and a message is

issued to the operator informing him of the volume, data set name, logical
unit, and selected tape drive.
If it is not the desired volume, the tape is returned to load point and
CA Dynam/T continues searching until all available tape units defined in
the applicable DTPOOL table have been searched. If no DTPOOL option
records are defined, the search continues through all tape drives in the
PUB table. If the correct volume has not been located, CA Dynam/T
instructs the operator to mount the desired volume (input) or a scratch
volume (output). When the operator responds, CA Dynam/T is again
activated and processing continues.

Using CA Dynam/T
Using the Early Drive Release
When necessary, the Automatic Volume Recognition facility automatically

positions multifile data sets. In conjunction with AVR, the Early Drive Release
facility releases a tape unit assignment as soon as the accessed file is closed
by the problem program. Together, these facilities maximize the efficiency of
tape units in a multiprogramming environment, as follows:
A tape unit is assigned only while in actual use between OPEN and CLOSE
of the accessed file, instead of remaining assigned for the duration of an
entire job.
For multivolume files, the volume switch can take place as soon as EOV
occurs. Alternate assignments requiring that two tape units be assigned
while only one is in use are not necessary.
You can override the AVR facility at any time through JCL assignments. It can
also be limited to selected drives through the DTPOOL option record.
Dynamic LUB Allocation
Dynamic LUB allocation is performed automatically, unless specifically

prohibited on the TLBL or with the DTLUBEX option record. The order in which
CA Dynam/T allocates LUB for a tape DTF is as follows:
1. Logical unit as specified with the S:nnn option of the TLBL statement (LUB
override).
2. Logical unit as found in the user DTF.
3. Logical unit as defined for the partition in the COMLUB option record.
4. Highest logical unit in the partition assigned UA.
To exclude a particular file from dynamic LUB allocation, code the P (to
prohibit) or H option (to hold) on the TLBL statement. The DTLUBEX option
record can be used to exclude a group of DTF names or phase names from
dynamic LUB allocation.
Note: To prohibit dynamic LUB allocation entirely, specify either DTFNAME=*

or PHASNAME=* in the DTLUBEX option record.
2–14 User Guide

Using CA Dynam/T
Mounting Tapes
The following tables display possible responses to the CA Dynam/T MOUNT

messages. For more information about the descriptions of valid responses to
individual MOUNT messages, see the CADT messages in the Message Guide.
To Issue This Response
Perform AVR EOB / END

(after mounting the requested
volume)
Display the present status of each tape unit STATUS

in the PUB table so the operator can
determine which units are available.
Display the present status of a particular STATUS cuu

tape unit.
(For more information about using STATUS

with this storage medium, see Tape
Cartridges.)
Display the status of all tape drives that are FREE

ready with no tape mounted, unassigned,
and attached to this machine.
Place the partition in stopped status, STOP

freeing the console.
(This status continues until you issue an

CASTART command for the partition; then
AVR is performed again.)
Direct CA Dynam/T to a specific tape unit if cuu

it is available.
If you are requesting a scratch tape and the

tape on the indicated drive is eligible, it is
initialized as a controlled scratch.
All available tape units in the PUB table are

eligible (responses of cuu are not limited by
DTPOOL specifications).
Drop the currently processed TLBLs from ALTER

the label area and reissue the OPEN (by generation option)
request.

Using CA Dynam/T
Flag the most current generation of the RERUN

requested data set for scratch and reissue (by generation option; only for
the OPEN request. input)
The tape is returned to scratch status when

you run the next scratch command.
Request the next most current version of PREV

this data set.
List available scratch tapes from the SCRTCH

Catalog on SYSLOG to help you find a valid
scratch tape.
List the number of scratch tapes specified SCRTCH, nnn

by nnn on SYSLOG.
Assign UA to the logical unit specified in the REL

MOUNT message. Full AVR can now take
place.
(Valid only if the file has a present

assignment through an explicit job control
assignment or as the result of a HOLD
option from a previous controlled file.)
Use these tape control commands with any

tape drive that is not LOCKED or owned by
a partition other than the one issuing the
message.
To rewind the indicated tapes REW cuu|ALL
To rewind and unload the indicated tapes RUN cuu|ALL
Forward space the indicated number of files FSF cuu,nnn
Forward space the indicated number of

records FSR cuu,nnn
Back space the indicated number of files BSF cuu,nnn
Back space the indicated number of records BSR cuu,nnn
Cancel the job. CANCEL
Reissue the OPEN and search for the ACCEPT DSN=dataset name,
indicated data set, version, or volume [VER=nnn|,VOL=xxxxxx]
instead of the one called from the JCL.
Force the system to accept the mounted ACCEPT

volume.
2–16 User Guide

Using CA Dynam/T
Reissue the OPEN for the newly mounted NEWTAP

tape.
Switch to a disk device. DISK
Answering Mount Messages
Examples of JCL and Console Logs:
Output tape selection through AVR
BG // JOB ARDUMP
DATE 01/07/09,CLOCK 23/07/07
BG // TLBL TAPEOUT,'AR TRANS,W' X
BG // EXEC MSTROUT
BG CADT007I **** LABEL TAPEOUT SYS011=299 100732 1 *AR TRANS* Y
BG CADT031I *CLOSED* TAPEOUT SYS011=299 100732 *AR TRANS* BLK=12 Z
BG EOJ ARDUMP
DATE 01/07/09, CLOCK 23/08/09, DURATION 00/01/02
1. This creates the file TAPEOUT, data set AR TRANS. Rewinds the tape at
CLOSE.
2. AVR locates a scratch tape on drive 299, and the CADT007I message is
issued.
3. The file is closed and the CADT031I message is issued. The Catalog is
updated; tape 100732 is now version 1 of data set AR TRANS.
Mounting a scratch tape
BG // JOB ARUPD
DATE 01/21/09, CLOCK 20/03/14
BG // TLBL TAPEOUT,'AR TRANS,W' X
BG // EXEC MSTROUT
BG CADT008D MOUNT SCRATCH TAPEOUT SYS011 DSN=AR TRANS MODE=1600 Y
BG STATUS Z
BG CADT015I 298-UA-* DOWN * [
BG CADT015I 299-UA-RDY LP/W 100732 AR TRANS
BG CADT015I 29A-UA-RDY LP/W 100733 AR MASTER
BG CADT015I 29B-UA-*AVRLOCK*
BG CADT008D MOUNT SCRATCH TAPEOUT SYS011 DSN=AR TRANS MODE=1600
BG 29A \
BG CADT010D VOLSER 100733 ALREADY IN FILE AS AR MASTER ]
BG STOP ^
F2 EOJ PAUSE
F1 1Q34I F2 WAITING FOR WORK

Using CA Dynam/T
AR CASTART BG _
BG 299 `
BG
BG CADT007I **** LABEL TAPEOUT SYS011=299 100867 1 *AR TRANS*
BG CADT031I *CLOSED* TAPEOUT SYS011=299 100867 AR TRANS BLK=12
BG EOJ ARUPD
1. This creates file TAPEOUT, data set AR TRANS. Rewinds tape at close.
2. No SCRATCH tape is found during AVR, so the CADT008D message is

issued. A mode of 1600 BPI is required.
3. The operator responds STATUS to get a report of tape drives.
4. Drive 298 is DVCDN, 299 and 29A are available, ready at load point and
write enabled, with the indicated volumes mounted. Drive 29B is LOCKED
for use by another CPU.
5. The operator directs CA Dynam/T to 29A.
6. 29A contains an active data set volume; the MOUNT message is reissued.
7. The operator responds STOP to free the console while a SCRATCH tape is
mounted.
8. The operator reactivates the job with the CASTART command, and the
MOUNT message is reissued.
9. The operator directs CA Dynam/T to 299, which contains an uninitialized

labeled tape. The tape is initialized and processing continues.
Uncontrolled input, controlled output tape
BG // JOB COPY UNLABELED TAPE TO LABELED TAPE

DATE 01/23/09,CLOCK 20/30/33
BG // UPSI 001 TDYNCOPY CONTROL UPSI X
BG // TLBL UOUT,'AR MASTER',,,,,,1
BG // EXEC TDYNCOPY
BG CADT001D UNASSIGNED INPUT TAPE UIN SYS004 Y
BG 299 Z
BG CADT008D MOUNT SCRATCH UOUT SYS005 DSN=AR MASTER MODE=1600 [
BG STATUS
BG CADT015I 298-UA-*DOWN*
BG CADT015I 299-BG-SYS004
BG CADT015I 29A-UA-RDY LP/W 999999 TEMP MASTER A
BG CADT015I 29B-UA-RDY LP/W 003912 PAY MASTER A
BG CADT008D MOUNT SCRATCH UOUT SYS005 DSN=AR MASTER MODE=1600
BG 29A
BG 100456
2–18 User Guide

Using CA Dynam/T
BG
BG CADT007I **** LABEL UOUT SYS005=29A 1004561 *AR MASTER*
BG CADT509I BLOCK COUNT=0000002 INPUT
BG CADT510I BLOCK COUNT=0000002 OUTPUT
BG CADT031I *CLOSED* UOUT SYS005=29A 100456 AR MASTER BLK=53
BG EOJ COPY
1. This copies an unlabeled tape file, UIN, to a labeled tape file, UOUT,data
set AR MASTER. Rewinds output tape at CLOSE.
2. No assignment is in effect for the input tape; the CADT001D message is

issued.
3. The operator directs CA Dynam/T to drive 299 for input.
4. No SCRATCH tape is available. After getting a status report of the tape

drives, the operator initializes the tape on 29A as volume 100456, and
processing continues. Note that the STATUS shows drive 299 already
assigned to SYS004 in BG.
JCL assignments for controlled tapes
F2 // JOB ARDESCUP
DATE 01/22/09,CLOCK 20/46/38
F2 // ASSGN SYS010,299
F2 // TLBL TAPEIN,'AR DESC 1',,,,,,2
F2 // ASSGN SYS011,29A
F2 // TLBL TAPEOUT,'AR DESC 1',,,,,,2
F2 // EXEC MSTRIO
F2 CADT032I ASSIGNED TAPEIN SYS010=299 100723 AR DESC 1
F2 CADT008I MOUNT SCRATCH TAPEOUT on 29A DSN=AR DESC 1 MODE=1600
F2 CADT017D *INTERV-REQ* 29A
F2 STATUS
F2 CADT015I 298 - UA- NOT AVBL
F2 CADT015I 299 - F2 - SYS010
F2 CADT015I 29A - F2 - SYS011
F2 CADT008I MOUNT SCRATCH TAPEOUT ON 29A DSN=AR DESC 1 MODE=1600
F2 CADT017D *INTERV REQ* 29A
F2
F2 CADT007I **** LABEL TAPEOUT SYS011=29A 100744 1 *AR DESC 1*
F2 CADT031I *CLOSED* TAPEOUT SYS011=29A 100744 AR DESC BLK=14
OJ ARDESCUP
F2 DATE 01/22/09, CLOCK 20/49/40,DURATION 00/03/02
JCL assignments for SYS010 and SYS011 are in effect. Note the difference in
the CADT008I message, and the CADT017D *INTERV REQ* message. The
operator is required to use drive 29A for the output file, because JCL
assignments are in effect. Note that STATUS shows 298 is not available for
processing, probably having been placed offline or detached.

Using CA Dynam/T
REWIND (response to MOUNT message)
BG // JOB ARUPD
DATE 01/23/09,CLOCK 20/00/43
BG // TLBL TAPEIN,'AR TRANS,U'
BG // TLBL TAPEOUT,'AR MASTER,W'
BG // EXEC MSTRIO
BG CADT004D MOUNT VOLUME 100372 AR TRANS SYS010
BG STATUS
BG CADT015I 298 - UA - RDY LP/W *NOT-CAP*
BG CADT015I 299 - UA - RDY NLPW
BG CADT015I 29A - UA - RDY LP/W 100733 BGWORK
BG 299
BG CADT002D *NOT LD PNT* SYS010=299
BG REWIND
BG
BG CADT032I ASSIGNED TAPEIN SYS010=299 100732 AR TRANS
BG CADT007I ****** LABEL TAPEOUT SYS011=29A 100733 1 *AR MASTER*
BG CADT031I *CLOSED* TAPEOUT SYS011=29A 100733 AR MASTER BLK=54
BG EOJ ARUPD
CA Dynam/T is unable to locate the desired volume during AVR; the

CADT004D MOUNT message is issued. A STATUS reveals that drive 299 is
unassigned, but not at load point. The operator directs CA Dynam/T to drive
299 and receives CADT002D NOT LD PNT. The operator replies REWIND to
cause the tape to be rewound. The next time AVR is performed, the desired
volume is located, the CADT032I message is issued and processing continues.
Note that STATUS shows that the density of the tape on drive 298 makes it
incapable of being read by the tape drive.
RERUN (response to MOUNT message, to rerun AVR of input tape)
BG // JOB ARRPLOAD
DATE 01/22/09,CLOCK 20/26/49
BG // TLBL TAPEIN,'AR RP MAST,W'
BG // EXEC MSTRIN
BG CADT004D MOUNT VOLUME 028768 AR RP MAST SYS010
BG RERUN
BG CADT032I ASSIGNED TAPEIN SYS010=29A 100665 AR RP MSTR
BG EOJ ARRPLOAD
2–20 User Guide

Using CA Dynam/T
The operator responds RERUN to the CADT004D MOUNT message to force

CA Dynam/T to flag Version 1 of AP RP MASTER for scratch. Note that volume
100665 (which was Version 2) becomes Version 1 and is located immediately
by AVR. The CADT032I message indicates that the desired volume has been
located and the assignment made. Tape 28768 will be scratched the next time
the DYNCAT SCRATCH command is run.
ACCEPT (response to MOUNT message)
BG // JOB ARRPLOAD
DATE 01/22/09,CLOCK 20/25/24
BG // TLBL TAPEIN,'AR RP MSTR,W'
BG // EXEC MSTRIN
BG CADT004D MOUNT VOLUME 028768 AR RP MSTR SYS010
BG 29A
BG CADT005D WRONG TAPE:VOL=100665 HDR1='AR RP MSTR' SYS010=29A
BG ACCEPT
BG EOJ ARRPLOAD
The operator has directed CA Dynam/T to a tape other than the one called for,
and the CADT005D message is issued showing the volume serial number and
file ID of the tape actually found. An ACCEPT response allows the operator to
override CA Dynam/T and input volume 100665 instead of volume 028768.
ALTER (response to MOUNT message)
BG // JOB ARRPLOAD
DATE 01/22/09,CLOCK 20/26/04
BG // TLBL TAPEIN,'AR RP MSTR,W'
BG // TLBL TAPEIN,'AR RP MSTR,W',,,,,2
BG // EXEC MSTRIN
BG CADT004D MOUNT VOLUME 028768 AR RP MSTR SYS010
BG ALTER
BG EOJ ARRPLOAD
The operator responds ALTER to the CADT004D MOUNT message to force

CA Dynam/T to drop the first TLBL and instead use the second. The second
TLBL calls for Version 2 of the data set. If the ALTER response is to be used,
the second TLBL must be available; otherwise, the job will cancel with NO
LABEL INFORMATION.

Using CA Dynam/T
SCRTCH (response to MOUNT message)
BG // JOB ARBKUP
DATE 01/22/09,CLOCK 20/28/10
BG // TLBL SYS006,'AR MSTR BKUP,U'
BG // EXEC ARMBKUP
BG CADT008D MOUNT SCRATCH SYS006 SYS006 DSN=AR MSTR BKUP
OWNER=AR SIZE=L
BG SCRTCH
BG CADT048I 000774 OWN=AR VLT=A L
BG CADT048I 000814 OWN=AR VLT=A M
BG CADT048I 001303 OWN=AR VLT=A M
BG CADT048I 000034 OWN=** VLT=A L
BG CADT048I 002035 OWN=** VLT=A L
BG CADT048I 000499 OWN=** VLT=A M
BG CADT048I 000611 OWN=** VLT=A M
BG CADT008D MOUNT SCRATCH SYS006 SYS006 DSN=AR MSTR BKUP
OWNER=AR SIZE=L
BG STOP
AR CASTART BG
BG CADT007I ****** LABEL SYS006=299 000379 1 *AR MSTR BKUP*
BG CADT031I *CLOSE* SYS006 SYS006=299 000379 AR MSTR BKUP BLK=54
BG EOJ ARBKUP
The data set AR MSTR BKUP is to be created. CA Dynam/T issues a MOUNT

message because it cannot find a scratch tape owned by AR with a reel length
of LONG. The SCRTCH response forces CA Dynam/T to produce a list of the
first ten scratch tapes found in the library on the console, so that an
appropriate scratch can be located.
The scratch tapes that meet the qualification criteria (Owner=AR and
Length=L) are listed first, followed by those that match only the owner ID,
then by those matching the length, and finally by unqualified scratches to fill
out a full list of ten tapes. The volume, 000379, appears on the list as being a
scratch with owner AR and size L; the operator stops the partition, locates the
tape and mounts it on drive 299. When the operator restarts the partition,
CA Dynam/T locates the tape through AVR, and the file is created.
2–22 User Guide

Using CA Dynam/T
REL (response to MOUNT message)
BG // JOB LOADMSTR
DATE 01/22/09,CLOCK 20/52/31
BG // TLBL SYS005,'AR MSTR BKUP,U'
BG // ASSGN SYS005,29A
BG // EXEC ARLOAD
BG CADT004I MOUNT VOLUME 000379 DSN=AR MSTR BKUP SYS005
BG CADT002D *INTERV REQ* SYS005=29A
BG STATUS
BG CADT015I 298 - F2 - SYS021
BG CADT015I 299 - UA - RDY LP/W 000379 AR MSTR BKUP
BG CADT015I 29A - BG - SYS005
BG CADT0041 MOUNT VOLUME 000379 DSN=AR MSTR BKUP SYS005
BG CADT002D *INTERV REQ* SYS005=29A
BG REL
BG CADT032I ASSIGNED SYS006 SYS006=299 000379 AR MSTR BKUP
BG EOJ LOADMSTR
The tape volume called for was mounted on a drive other than the one to
which the JCL assigned it. The operator responds REL to release the
assignment and force AVR rather than move the tape from 299, where it was
mounted and ready, to its assignment at 29A. CA Dynam/T locates the tape
and the file is processed.
Had the JCL been originally submitted without the // ASSGN SYS005,29A
statement to take full advantage of AVR, the volume would have been located
on the first AVR scan, and none of the console dialog would have been
required.
DISK (response to MOUNT message)
BG // JOB BUILDMST
DATE 01/22/09,CLOCK 20/52/31
BG // TLBL ARMTAP,'AR MSTR OUT,U'
BG // EXEC ARCREATE
BG CADT008D MOUNT SCRATCH ARMTAP SYS006 DSN=AR MASTER OUT BUILDMST
BG STATUS
BG CADT015I 298 - F2 - SYS021
BG CADT015I 299 - F2 - SYS022
BG CADT015I 29A - UA - *LOCKED*
BG CADT008D MOUNT SCRATCH ARMTAP SYS006 DSN=AR MASTER OUT BUILDMST
BG DISK
BG CADD002I ALLOCATED FILE=ARMTAP SYS038=15C SYSWK1 IX=00/204/40 (G#06)
BG EOJ BUILDMST

Using CA Dynam/T
An output tape file, ARMTAP, is to be created on SYS006, under the data set
name AR MSTR OUT. When the CADT008D MOUNT message is issued, STATUS
shows no tape drives available. The operator could reply STOP and allow the
job in F2 to complete; then, he could restart BG. Instead, he chooses to
respond DISK, requesting CA Dynam to change the device type from tape to
disk and use the disk allocation characteristics stored in the Catalog to control
the allocation of the file. CA Dynam/FI is invoked to modify the file type, and
CA Dynam/D to locate the space; the file is successfully created on DASD
volume SYSWK1.
Note that another logical unit is used by CA Dynam/D for the file. When the
file is called for as input, CA Dynam/FI intervenes to locate the file on disk and
allow it to be inputted from there automatically, even though JCL can call for
the file on tape.
In order for processing such as this to take place, all of the following must be
true:
The complete CA Dynam system must be installed.
FISWTCH must be active.
The file must be defined in the Catalog as eligible for switching.
For more information, see Operator Device Switching Facility in the chapter
"Controlling File Independence."
Attention Routine (AR) Commands
Tape Drive Status and Control Commands
These commands can be issued from the operator console to position tapes or
display status without issuing DITTO or MTC commands.
DT BSF cuu,nnn Backspace a tape drive nnn files.
DT BSR cuu,nnn Backspace a tape drive nnn records.
DT FSF cuu,nnn Forward space a tape drive nnn files.
DT FSR cuu,nnn Forward space a tape drive nnn records.
DT LOCK cuu|TAPES nnn|ALL

Issue lock for specified tape drives.
DT READY cuu|ALL Ready a tape that is left in NOT AVRABLE status.**
DT REW cuu|ALL Rewind the named tape drives.
2–24 User Guide

Using CA Dynam/T
DT RUN cuu|ALL Unload the named tape drives.
DT STATUS Show status of all tape drives.
DT STATUS cuu Show status of a particular tape drive.
DT STATUS pp Show status of all tape drives available to the partition specified (pp). Drives
are shown in the order in which they will be AVRed in this partition.
DT STATUS FREE Show status of all tape drives that are in a ready status with no tape mounted,
are unassigned, and are attached to the machine issuing the command.
DT UNLOCK cuu|TAPES nnn|ALL

Issue unlock for specified tape drives.
** This is only seen when using the IUCV interface and an unusual situation
occurs.
Note: The format of these commands has changed from previous releases of
CA Dynam. However, for reasons of compatibility, the previous command
format of 'CA-D/T xxx' is still supported.
The DT PATH Command
The DTPATH command can be used to query and manipulate the

communication paths defined by the DTPATH option record.
For more information about the DTPATH option record, see the chapters
"Installation Options" and "Using CA Dynam with Special Environments" in the
Programming Guide.
DT Path [ Query {ALL|pathid } ]

[ ]
[ ENable {ALL|pathid } ]
[ ]
[ DISAble {ALL|pathid } ]
[ ]
[ TRace {ON|OFF } {ALL|pathid } [ ADAPT]]
[ [ PATH ] ]
[ [ CAT ] ]
[ [ ALL ] ]
[ ]
[ Log {ON|OFF } {ALL|pathid } [ PLIST]]
[ [ VERIFY ] ]
[ [ RECEIVE ] ]
[ [ ALL ] ]
[ ]
[ DISPatch {ALL|pathid } ]

Using CA Dynam/T
All parameters for the DT PATH command are positional and must be specified
in the format shown above.
DISABLE Disables a specific receive path or all receive paths for this CPUID.
DISPATCH Forces a specific receive path or all receive paths for this CPUID to be read,
even though it has been disabled.
ENABLE Enables a specific receive path or all receive paths for this CPUID. A receive
path is one defined for another CPUID with a TO value specifying this CPUID.
LOG Enables logging of various events for a specific receive path or all receive
paths. The events to be logged can be indicated as:
PLIST Displays a list of adapter calls and requesters, to be used

in the event of an unexpected return code.
VERIFY Logs all VERIFY transactions sent or received by this

CPUID.
RECEIVE Logs all VOLUME transactions received by this CPUID.
ALL Default. Enables logging for the PLIST, VERIFY, and

RECEIVE.
You can specify one type of event or a combination of event types listed above
for LOG.
QUERY Displays the status of a specific path or all paths for this CPUID.
TRACE Enables the trace facility to trace various events for a specific receive path or
all receive paths. The events to be traced can be indicated as:
ADAPT All adapter type calls, except PATH and CATALOG type
calls.
PATH PATH function adapter calls only.
CAT CATALOG function adapter calls only.
ALL For all adapter type calls, is the default.
Use this parameter only at the request of CA Technical Support personnel. You
can specify one type of event or a combination of event types listed above for
TRACE.
2–26 User Guide

Using CA Dynam/T
Examples:
DTNODE and DTPATH Option Records
The following is an example defining DTNODE and DTPATH option records for
communicating across three systems, the first running CA Dynam/T VSE, the
second also running CA Dynam/T VSE, and the third running CA 1. The two
CA Dynam/T systems share a catalog, and as such only one receiver is active.
Two Multi:ACCESS queue files (DYN2CA1 and CA12DYN) are used to describe
the two physical links, with a separate PATH description for communication in
each direction active on each link.
// JOB DBU0
// EXEC CACCDBU0
DEF DTNODE CPU(*) DUPREC(DELETE) -
NODEID(VSE.SYSA) -
NCPUID(A)
DEF DTNODE CPU(*) DUPREC(APPEND) -

NODEID(VSE.SYSB) -
NCPUID(B)
DEF DTNODE CPU(*) DUPREC(APPEND) -

NODEID(CA1MVS) -
NCPUID(Z)
DEF DTPATH CPU(*) DUPREC(DELETE) -

PATHID(DYN2CA1) -
FROM(A) -
TO(Z) -
RWAIT(0020) -
VERIFY(0040)
DEF DTPATH CPU(*) DUPREC(APPEND) -

PATHID(DYN2CA1) -
FROM(B) -
TO(Z) -
RWAIT(0030) -
VERIFY(0050)
DEF DTPATH CPU(*) DUPREC(APPEND) -

PATHID(CA12DYN) -
FROM(Z) -
TO(A) -
RWAIT(0010) -
VERIFY(0020)
/*
/&

Using CA Dynam/T
Shown next are examples of DTPATH commands that correspond to paths

defined in this DTPATH option record example.
DT PATH Examples:
Display the status of all paths for this CPUID.
DT PATH QUERY ALL
The following messages are issued in response to querying ALL paths. They
show the status for all paths controlled by this CPU. (CA1MVS) is the NODEID
of the CPUID sending transactions on this path and the return code is the
highest recorded for this path. The status will display whether the path is
currently enabled, and whether any traces or logs are pending for this path.
AR 015 CADC540I RECEIVE PATH=CA12DYN (CA1MVS) ADDR=0048AB98

AR 015 CADC540I LAST EXEC=12:12:05 LAST REC=________
AR 015 CADC540I NUM REC=0 ERRS=0 : RC=00000020 : STATUS=ENABLED
AR 015 CADC541I SEND PATH=DYN2CA1 : STATUS=ENABLED
Display the status of the CA12DYN path for this CPUID.
DT PATH QUERY CA12DYN
If a particular path, in this case CA12DYN, is queried, the following messages

result:
AR 015 CADC540I RECEIVE PATH=CA12DYN (CA1MVS) ADDR=0048AB98

AR 015 CADC540I LAST EXEC=12:12:25 LAST REC=________
AR 015 CADC540I NUM REC=0 ERRS=0 : RC=00000020 : STATUS=ENABLED
Enable or disable all receive paths for this CPUID.
DT PATH ENABLE ALL
DT PATH DISABLE ALL
When enabling/disabling ALL paths, a message is displayed for each affected

path of this CPUID. In this case, only the CA12DYN pathid corresponds.
AR 015 CADC544I RECEIVE PATH CA12DYN (CA1MVS) ENABLED
AR 015 CADC544I RECEIVE PATH CA12DYN (CA1MVS) DISABLED
Enable or disable a particular receive path, in this case CA12DYN, for this
CPUID.
DT PATH ENABLE CA12DYN
DT PATH DISABLE CA12DYN
2–28 User Guide

Using CA Dynam/T
When enabling/disabling a particular path, a message is displayed for this

CPU.
AR 015 CADC544I RECEIVE PATH CA12DYN (CA1MVS) ENABLED
AR 015 CADC544I RECEIVE PATH CA12DYN (CA1MVS) DISABLED
Request or discontinue logging of events for the CA12DYN pathid. The type of
event is unspecified here, defaulting to ALL three event types (PLIST, VERIFY,
and RECEIVE).
DT PATH LOG ON CA12DYN
DT PATH LOG OFF CA12DYN
When requesting/discontinuing logging of a particular pathid, a message

appears for the RECEIVE pathid specified. In this example, it is the CA12DYN
path.
AR 015 CADC545I LOG STARTED FOR RECEIVE PATH CA12DYN (CA1MVS)
AR 015 CADC545I LOG ENDED FOR RECEIVE PATH CA12DYN (CA1MVS)
Request or discontinue tracing of events for the CA12DYN pathid. The type of
event is unspecified here, defaulting to ALL three event types (PLIST, VERIFY,
and RECEIVE).
DT PATH TRACE ON CA12DYN
DT PATH TRACE OFF CA12DYN
When requesting/discontinuing tracing of a particular pathid, a message

appears for the RECEIVE pathid specified.
AR 015 CADC545I TRACE STARTED FOR RECEIVE PATH CA12DYN (CA1MVS)
AR 015 CADC545I TRACE ENDED FOR RECEIVE PATH pathid (CA1MVS)
Automatic Retry Facility
CA Dynam/T provides an automatic retry of the AVR scan for input or output
tapes if you so specify in the DYNAM/T option record. This facility notifies the
operator of a required mount for a specific input tape or a scratch tape using
the normal mount message, then goes to sleep for a user-specified interval
without requiring an operator response, allowing the operator to locate the
volume and mount it on an available drive.

Using CA Dynam/T
When the interval expires, CA Dynam/T wakes up and performs AVR to

attempt to locate the desired tape. If it has been mounted, processing
continues without operator console activity. If CA Dynam/T still cannot locate
the tape, it again waits the specified number of seconds, then repeats AVR.
This sequence is repeated until the operator has either mounted the tape, or
the user-specified number of tries has been exhausted, at which time the
mount message is reissued (this time with an operator response required).
With proper education and procedures, this facility can significantly reduce the
number of operator console interactions. A reasonable time between AVR
requests (for example, 30 seconds) allows tapes to be located in a timely
fashion, but does not cause undue overhead through AVR if operator
intervention is to be needed. You can select the ALARM(YES) parameter in the
DYNAM/T option record to ensure the operator is aware of the informational
MOUNT messages which appear while AUTO-RETRY is in progress; a console
alarm is sounded whenever a MOUNT message is issued. For more information
about instructions in the coding and use of the DYNAM/T option record, see
the Programming Guide.
TLBL Statement Extensions and Format
CA Dynam/T requires a VSE standard TLBL for each controlled file. You can
submit the TLBL in the job stream, or place it in the partition or system
standard label area. All normal VSE labeling conventions apply.
Some of the fields of the TLBL have been functionally extended to provide
additional information to CA Dynam/T, allowing the user to better control the
processing of tape files. These extensions permit you to specify the following:
Data set names up to 44 characters
Retention
Version (generation)
Volume sequence number

TLBL options
TLBL Statement Format
The VSE standard TLBL format is used by CA Dynam/T.
// TLBL filename,'file-id',ret,volser,volseq,fileseq,gen,ver
2–30 User Guide

Using CA Dynam/T
TLBL Parameters
The following list describes the parameters for each of the TLBL fields.
filename(dtfname) Required parameter, 1 to 7 alphanumeric characters long. The file name must
be the same as the name specified for the file in the program's DTF.
file-id This parameter is required for CA Dynam/T to control the file. It is up to 44

alphanumeric characters long and must be enclosed in single quotation marks.
The file-ID must also be identical to the data set name as it appears in the
CA Dynam Catalog. Additionally, it can contain relative generation information
to call for a particular version of an input file and alphabetic option codes to
control various processing options.
If you are including relative generation information or alphabetic codes, then

there are additional requirements for the data set name format. They are as
follows:
Data set name field
− It can contain only alphabetic and numeric characters, and blanks.
− It cannot exceed 59 characters in total length, including relative

generation and options.
Relative generation must be appended to the data set name, enclosed in

parentheses and preceded by a period.
Comma must precede each alphabetic option.
Parentheses are supported.
Relative generation must precede alphabetic options if you specify both.

For example,
// TLBL filename,'FILEID.(-1),W,H,D'
Version 2 of the data set FILEID is requested. At CLOSE, the REWIND, HOLD,
and DROP options are performed.
Note: If the actual data set name field length is greater than 17 (after the
options have been stripped) the LAST 17 significant characters are written to
the HDR1 label on the tape.
ret Specify exceptional retention for output files in this field with any one of the
following:
A Julian date (yy/ddd or yyyy/ddd)
A 1- to 4-digit number, 0—9999
Omit this field for input files.
volser Request a specific volume for input files in this field with a 1- to 6- character
alphanumeric volume serial number. Omit this field for output files.

Using CA Dynam/T
volseq Use this field to request a specific volume of a multivolume data set for input
files with a 1- to 4-digit number from 0 to 9999. Omit this field for output files.
fileseq The file sequence number field is not used by CA Dynam/T and should be
omitted in all cases. The multifile data set control provided by CA Dynam/T is
based upon the data set name and control records in the Catalog.
gen In this field, request a specific version of a data set for input files with a 1-to
4-digit version number from 0 to 9999. Omit this field for output files.
ver Use this field to specify option codes that control various processing functions.
Enter a 1- to 2-digit number, 0—99.
G=nnnnn or GEN=nnnnn
Use the field to specify an absolute generation number from 1 to 65535 for the
data set. This number lets you always access this particular version of the data
set. This is a positional entry and must be coded after all other parameters. If
the first option is a keyword and IBM options are omitted, at least 1 comma
after file-id is required; otherwise, at least 2 commas are needed.
Example:
// TLBL filename,'file-id',,G=123.
Retention The value specified in the TLBL date field overrides the number of retention
days specified in the Catalog only if it is the larger of the two. It applies only to
the version created using that TLBL.
Examples:
// TLBL FILENAME,'FILE-ID',10 (number of retention days)
// TLBL FILENAME,'FILE-ID',2099/365 (expiration date in Julian format)
Version (Generation) CA Dynam/T defaults to the current version of the data set requested for
Specification input files. You can select another version three ways.
If the length of the data set name is as follows:
Does not exceed 59 characters, including the generation specification,

append the relative generation number to the data set name as part of the
file ID field. Place the number within parentheses after the period which
follows the data set name. Indicate a generation by specifying the number
of generations prior to the current generation with a minus sign before the
number.
2–32 User Guide

Using CA Dynam/T
This statement Calls for
// TLBL FILENAME,'FILE-ID' the current version
// TLBL FILENAME,'FILE-ID.(-1)' the father
// TLBL FILENAME,'FILE-ID.(-2)' the grandfather
Plus the absolute generation specification exceeds 59 characters and no

IBM options are included, at least one comma after the file-id is required.
Here, the generation is expressed as an absolute value associated with the
data set version.
This Statement Calls For
// TLBL FILENAME,'FILE-ID,G=1' absolute generation 1
Plus the relative generation specification exceeds 59 characters or contains

any special symbols, place the generation in the Generation Number field
of the TLBL. Here, the generation is expressed as a positive integer
relative to the current generation, which is considered generation 1.
This Statement Calls For
// TLBL FILENAME,'FILE-ID' the current generation
// TLBL FILENAME,'FILE-ID',,,,,2 the father
// TLBL FILENAME,'FILE-ID',,,,,3 the grandfather
Volume Serial Number Use the File Serial Number field of the TLBL to select a specific volume with
which to begin processing for input files. The volume can be any reel of any
version, as long as it is a member of the requested data set.
If the requested volume is not a member of the data set, a mount for that
volume serial number is issued. A valid entry is a 1- to 6-character volume
serial number. The following example calls for volume number 765:
// TLBL FILENAME,'FILE-ID',,000765
Volume Sequence Use the Volume Sequence Number field to select a specific volume of a
Number multivolume version of a data set with which to begin processing for input
files. The default is volume one.

Using CA Dynam/T
If you specify a volume that does not exist, CA Dynam/T issues a mount for
that volume serial number. A valid entry is a 1- to 4-digit volume sequence
number. The following example calls for volume sequence number two.
// TLBL FILENAME,'FILE-ID',,,2
CA Dynam/T Processing Options
The TLBL options enable you to control certain system actions at OPEN and
CLOSE. You can communicate these options to CA Dynam/T as any one of the
following:
Alphabetic option codes appended to the data set name in the FILE-ID field
Numeric option codes in the Version Number field
CA Dynam/T ignores numeric options if the alphabetic option codes are used in
a TLBL. You can specify certain options only with alphabetic option codes.
Options Alphabetic Numeric
Release R 04
Unload U 02
Rewind W 01
Norewind N 32
Prohibit P
Catalog C
Drop D 16
Hold H 08
Identify I
Modify A 64
Multitask Z
Long L
medium long ML
Medium M
medium short MS
Short S
extra short XS
800 BPI C8
2–34 User Guide

Using CA Dynam/T
1600 BPI (START-STOP) 30
1600 BPI (START-STOP) 50
1600 BPI (STREAMING) 60
1600 BPI (STREAMING) 90
1600 BPI C0
6250 BPI D0
TAPE CARTRIDGE D8
buffered write mode 00
buffered write mode (3490E) 00E
buffered write mode (3590) 00M
buffered write mode (3590E) 00ME
buffered write mode (3590H) 00MH
buffered write mode (3592) 00W
buffered write mode (3592E) 00WE
encrypted buffered write mode 03WE

(3592E)
data compaction with buffered write 08
data compaction with buffered write 08E

(3490E)
data compaction with buffered write 08M

(3590)
data compaction with buffered write 08ME

(3590E)
data compaction with buffered write 08MH

(3590H)
data compaction with buffered write 08W

(3592)
data compaction with buffered write 08WE

(3592E)
encrypted data compaction with 0BWE

buffered write (3592E)
unbuffered write mode 20
unbuffered write mode (3490E) 20E

Using CA Dynam/T
unbuffered write mode (3590) 20M
unbuffered write mode (3590E) 20ME
unbuffered write mode (3590H) 20MH
unbuffered write mode (3592) 20W
unbuffered write mode (3592E) 20WE
encrypted unbuffered write mode 23WE

(3592E)
data compaction with unbuffered 28

write
data compaction with unbuffered 28E

write (3490E)
data compaction with unbuffered 28M

write (3590)
data compaction with unbuffered 28ME

write (3590E)
data compaction with unbuffered 28MH

write (3590H)
data compaction with unbuffered 28W

write (3592)
data compaction with unbuffered 28WE

write (3592E)
encrypted data compaction with 2BWE

unbuffered write (3592E)
1600 BPI (9348 buffered write mode) 42
1600 BPI (9348 unbuffered write 62

mode)
6250 BPI (9348 buffered write mode) C2
6250 BPI (9348 unbuffered write E2

mode)
logical unit override S:nnn
delete label at close DL
delete file at end of job after JX

processing
2–36 User Guide

Using CA Dynam/T
delete file at end of step after SX

processing
two-byte overriding ownerid OW=xx
eject cartridge from robotic device E
Note: If the JX or SX option is specified for an input file and the job step
abnormally terminates, the file is not deleted. This allows the job to be rerun.
JX and SX options are not supported for multifile data sets.
Examples:
You can specify multiple options on the same TLBL:
// TLBL FILEB,'DSNB,W,H,D' (using the alphabetic options)
// TLBL FILEB,'DSNB',,,,,,25 (using the numeric options)
Both result in the REWIND, HOLD, and DROP options being performed.
To specify multiple numeric options, add the numeric values of the option
codes and place the sum in the Version Number field.
To specify multiple alphabetic options, append them to the DSN separated by

commas. You cannot mix alphabetic and numeric options on a TLBL. If you
specify both, CA Dynam/T ignores the numeric options.
The following charts detail the TLBL options.
Option Specified Purpose Examples

As
release R or 04 Scratches current work data set // TLBL FILE1,'ABC,R'

version when the file is closed.
// TLBL FILE1,'ABC',,,,,,04
rewind W or 01 Alters the DTF to rewind the file to // TLBL FILE1,'ABC,W'

load point when the file is closed.
unload U or 02 Alters the DTF to unload the file when // TLBL FILE1,'ABC,U'
the file is closed.
norewind N or 32 Alters the DTF, so the file is not // TLBL FILE1,'ABC,N'

rewound when the file is closed.
Catalog data C Automatically adds the data set name // TLBL dtfname,'DSN,C'
set name in the TLBL to the Catalog when it is
first opened for output.

Using CA Dynam/T
Option Specified Purpose Examples

As
drop D or 16 Erases the TLBL from the label track // TLBL dtfname,'DSN,D'
for the file when it is closed. A
// TLBL dtfname,'DSN'...16
subsequent OPEN can process the
next TLBL with the same DTFname
hold H or 08 Prevents early drive release when the // TLBL FILE1,'ABC,H'

file is closed. Assignment is reset by
JCL at EOJ.
identify HDR1 I Forces the IBM OPEN transients to // TLBL dtfname,'DSN,I'

type HDR1 information from the tape
being processed on the SYSLOG
device.
modify A or 64 Modifies the open DTF file name when // TLBL dtfname,'DSN,A'
there is more than one open tape file
// TLBL dtfname,'DSN'...64
with the same name (see Notes.)
multitask Z The CA Dynam/T work area used // TLBL dtfname,'DSN,Z'

LIOCS between OPEN and CLOSE is released
whenever the task that opens the
tape is ended. The Z option will only
release the work area when the main
task ends. Therefore, the Z option
should be used if a sub-task that
opens a tape is ended before the tape
is closed.
prohibit P Prohibits dynamic LUB allocation for // TLBL dtfname,'DSN,P'

this DTF.
logical unit S:nnn Overrides the logical unit defined in // TLBL dtfname,'DSN,S:030'
override the DTF with the value (nnn) specified
and assigns the logical unit to a
dummy device.
delete label at DL Delete the label for the file at the // TLBL dtfname,'DSN,DL'
close close of the file.
EJECT E Eject cartridge from the robot at the // TLBL dtfname,'DSN,E'

close of the file.
Notes on the MODIFY option:
CA Dynam/T modifies the file name of the DTF being opened to SYS0nnn,
where nnn is the logical unit being used for the file. This is necessary when a
program has two tape files with the same file name concurrently open (usually
one input and one output). This rare occurrence is most likely to appear in
ANSI COBOL programs with two SELECT statements for tape files, both
specifying the same external name.
2–38 User Guide

Using CA Dynam/T
SELECT TAPE-FILE ASSIGN TO SYS010-UT-3420-S-MASTER.

SELECT TAPE-OUT ASSIGN TO SYS011-UT-3420-S-MASTER.
Both files are referred to as MASTER, because of the above COBOL

statements. A second OPEN results in the file being treated as uncontrolled,
because CA Dynam/T requires a separate TLBL for each controlled file.
Both files can be controlled if you use the dynamic file name modification
option on the first of the two TLBLs with the file name MASTER:
// TLBL MASTER,'DSN,A'
// TLBL MASTER,'DSN'
or
// TLBL MASTER,'DSN',,,,,,64
// TLBL MASTER,'DSN'
Suppose the logical unit for the first of the two files to be opened was SYS010.
At OPEN, CA Dynam/T would change the file name to SYS0010 in the program
and on the label track.
Note that if you use the DROP option in conjunction with MODIFY, successive
label records (TLBLs) must use the modified file name (in this case, SYS0010).
Tape Reel Length Specification
CA Dynam/T lets you specify the size of tape reels for specific data sets. This
maximizes your magnetic tape resources. You can indicate tape reel length in
any one of the following ways:
In the Catalog as an attribute of the data set

As an alphabetic TLBL option in the file-ID field
CA Dynam/T provides six length codes (XS, S, MS, M, ML, L) ranging from
extra short to long. They allow for data sets of various lengths.
The chart below details the permitted length specifications, as defined to the
Catalog using the DYNCAT DEFINE statement.
This DYNCAT DEFINE Establishes This Tape Length

Statement
DEFINE 'ERROR FILE' NGEN=2 extra short (200 ft.)

LENGTH=XS
DEFINE 'TRANS FILE' NGEN=3 short (400 ft.)

LENGTH=S

Using CA Dynam/T
This DYNCAT DEFINE Establishes This Tape Length

Statement
DEFINE 'UPDAT FILE' NGEN=1 medium short (600 ft.)

LENGTH=MS
DEFINE 'DESCR FILE' NGEN=7 medium (800 ft.)

LENGTH=M
DEFINE 'REPT FILE' NGEN=1 medium long (1200 ft.)

LENGTH=ML
DEFINE 'MSTR FILE' NGEN=12 long (2400 ft.)

LENGTH=L
In a TLBL Statement
Here is an example of length specification on the TLBL statement:
// TLBL EFILE,'ERROR FILE,XS'
In DYNCAT Commands
Establish the length of the tape when initializing the volume with the DYNCAT
INT or INTR commands. This information is maintained in the Catalog, not on
the physical VOL1/HDR1 of the tape. Specifying length is unnecessary if your
tape library has only one size of tape reel. Several examples follow:
Examples:
The tape on drive 280 is initialized with volume serial number 1001 as an
extra short tape.
INT 280 VOLSER=(1001) LENGTH=XS
The tape on the drive to which SYS008 is assigned is initialized with volume
serial number 1002 as a short tape, owned by PR.
INT SYS008 VOLSER=(1002) LENGTH=S OWNER=PR
The tape on drive 281 is read to determine the volume serial number so that
the operator can verify that it is correct. Next the tape is initialized with its
previous number (unless the operator overrides it) as a medium short tape.
INT 281 LENGTH=MS
2–40 User Guide

Using CA Dynam/T
The tape on drive 282 is initialized with volume serial number 1003 as a
medium length tape. It will be flagged in the Catalog for cleaning when more
than 100 temporary read/write errors have been recorded for it.
INT 282 VOLSER=(1003) LENGTH=M CLEAN=100
The tape on drive 283 is initialized with volume serial number 1004 as a
medium long tape at a recording density of 1600 BPI phase encoding.
INT 283 VOLSER=(1004) LENGTH=ML DENSITY=C0
The tape on drive 284 is initialized with volume serial number 1005 as a long
tape. The tape will be rewound when initialization is complete.
INTR 284 VOLSER=(1005) LENGTH=L
Length checking is done only during AVR scanning. CA Dynam/T does not
associate any length attribute with the tape if you do not specify one when
initializing it. CA Dynam/T will not select a tape of unspecified length for a data
set of a specified length.
Use the DYNCAT SCRPOOL command to change the length of an existing

scratch tape, or the ALTER volser command to change the length of an active
tape.
Examples:
Tape volumes 1005, 1006, and 1007 are redefined in the Catalog as long
tapes.
SCRPOOL VOLSER=(1005,1006,1007) LENGTH=L
Tape volume 1007 is redefined in the Catalog as a short tape owned by PR.
SCRPOOL VOLSER=(1007) LENGTH=S OWNER=PR
Tape volume 1008 is redefined in the Catalog as a long tape, and the owner ID
is reset to blanks.
ALTER 1008 LENGTH=L OWNER=NO
Overriding Length Attributes
You can use a tape whose length is different from the specified length of the
data set. This does not alter the tape's length attribute. The operator must
direct CA Dynam/T to the drive containing the scratch tape you will be using;
no other operator action is required to override the specified length. However,
the tape must be in scratch status.

Using CA Dynam/T
Recording Density (MODE) Specification
CA Dynam/T enables you to decide the recording density (or mode) of a data
set. You can indicate tape density in the following ways:
As a TLBL option in the file-ID field
In the Catalog as a data set attribute
The TLBL specification overrides a Catalog specification for the data set.
In TLBL Statements
Although recording density is actually a characteristic of a data set rather than

of a particular job stream, you can specify recording density on the TLBL in the
file-ID field. Place an alphanumeric CA Dynam/T option code in the file-ID
field—no numeric option codes exist for recording density. These are the
permitted file-ID option codes:
30 1600 BPI Streaming: high speed and short gap (8809 only)
50 1600 BPI Start-Stop: low speed and long gap (8809 only)
60 1600 BPI Start-Stop: low speed and short gap (8809 only)
90 1600 BPI Streaming: high speed and long gap (8809 only)
C0 1600 BPI phase encoding mode
C8 800 BPI NRZI mode
D0 6250 BPI
D8 Tape cartridge
00 Tape cartridge—buffered write mode
00E Tape cartridge—buffered write mode (3490E)
00M Tape cartridge—buffered write mode (3590)
00ME Tape cartridge—buffered write mode (3590E)
00MH Tape cartridge—buffered write mode (3590H)
00W Tape cartridge—buffered write mode (3592)
00WE Tape cartridge—buffered write mode (3592E)
2–42 User Guide

Using CA Dynam/T
03WE Tape cartridge—encrypted buffered write mode (3592E)
08 Tape cartridge—data compaction with buffered write
08E Tape cartridge—data compaction with buffered write (3490E)
08M Tape cartridge—data compaction buffered write mode (3590)
08ME Tape cartridge—data compaction buffered write mode (3590E)
08MH Tape cartridge—data compaction buffered write mode (3590H)
08W Tape cartridge—data compaction buffered write mode (3592)
08WE Tape cartridge—data compaction buffered write mode (3592E)
0BWE Tape cartridge—encrypted data compaction with buffered write mode (3592E)
20 Tape cartridge—unbuffered write mode
20E Tape cartridge—unbuffered write mode (3490E)
20M Tape cartridge—unbuffered write mode (3590)
20ME Tape cartridge—unbuffered write mode (3590E)
20MH Tape cartridge—unbuffered write mode (3590H)
20W Tape cartridge—unbuffered write mode (3592)
20WE Tape cartridge—unbuffered write mode (3592E)
23WE Tape cartridge—encrypted unbuffered write mode (3592E)
28 Tape cartridge—data compaction with unbuffered write
28E Tape cartridge—data compaction with unbuffered write (3490E)
28M Tape cartridge—data compaction with unbuffered write (3590)
28ME Tape cartridge—data compaction with unbuffered write (3590E)
28MH Tape cartridge—data compaction with unbuffered write (3590H)
28W Tape cartridge—data compaction with unbuffered write (3592)
28WE Tape cartridge—data compaction with unbuffered write (3592E)
2BWE Tape cartridge—encrypted data compaction with unbuffered write (3592E)

Using CA Dynam/T
42 Tape cartridge—1600 BPI buffered write mode (9348E)
62 Tape cartridge—1600 BPI unbuffered write mode (9348E)
C2 Tape cartridge—6250 BPI buffered write mode (9348E)
E2 Tape cartridge—6250 BPI unbuffered write mode (9348E)
Example:
// TLBL EFILE,'ERROR FILE,C8'
In the Catalog
You can indicate the data set mode in the Catalog by using the DEN=
parameter of DYNCAT's DEFINE/ALTER commands.
DEN=800 800 BPI
DEN=1600 1600 BPI
DEN=6250 6250 BPI
DEN=CART Tape cartridge
DEN=00 Tape cartridge (buffered write mode)
DEN=00E Tape cartridge (buffered write mode—3490E)
DEN=00M Tape cartridge (buffered write mode—3590)
DEN=00ME Tape cartridge (buffered write mode—3590E)
DEN=00MH Tape cartridge (buffered write mode—3590H)
DEN=00W Tape cartridge (buffered write mode—3592)
DEN=00WE Tape cartridge (buffered write mode—3592E)
DEN=03WE Tape cartridge (encrypted buffered write mode—3592E)
DEN=08 Tape cartridge (data compaction with buffered write)
DEN=08E Tape cartridge (data compaction with buffered write—3490E)
DEN=08M Tape cartridge (data compaction with buffered write—3590)
DEN=08ME Tape cartridge (data compaction with buffered write—3590E)
2–44 User Guide

Using CA Dynam/T
DEN=08MH Tape cartridge (data compaction with buffered write—3590H)
DEN=08W Tape cartridge (data compaction with buffered write—3592)
DEN=08WE Tape cartridge (data compaction with buffered write—3592E)
DEN=0BWE Tape cartridge (encrypted data compaction with buffered write—3592E)
DEN=20 Tape cartridge (unbuffered write mode)
DEN=20E Tape cartridge (unbuffered write mode—3490E)
DEN=20M Tape cartridge (unbuffered write mode—3590)
DEN=20ME Tape cartridge (unbuffered write mode—3590E)
DEN=20MH Tape cartridge (unbuffered write mode—3590H)
DEN=20W Tape cartridge (unbuffered write mode—3592)
DEN=20WE Tape cartridge (unbuffered write mode—3592E)
DEN=23WE Tape cartridge (encrypted unbuffered write mode—3592E)
DEN=28 Tape cartridge (data compaction with unbuffered write)
DEN=28E Tape cartridge (data compaction with unbuffered write 3490E)
DEN=28M Tape cartridge (data compaction with unbuffered write—3590)
DEN=28ME Tape cartridge (data compaction with unbuffered write—3590E)
DEN=28MH Tape cartridge (data compaction with unbuffered write—3590H)
DEN=28W Tape cartridge (data compaction with unbuffered write—3592)
DEN=28WE Tape cartridge (data compaction with unbuffered write—3592E)
DEN=2BWE Tape cartridge (encrypted data compaction with unbuffered write mode—
3592E)
DEN=42 1600 BPI (9348 buffered write mode)
DEN=62 1600 BPI (9348 unbuffered write mode)
DEN=C2 6250 BPI (9348 buffered write mode)
DEN=E2 6250 BPI (9348 unbuffered write mode)

Using CA Dynam/T
For example, the following commands establish four data sets with the
appropriate recording densities:
DEFINE 'FILE ONE' NGEN=1 DEN=800

DEFINE 'FILE TWO' NGEN=1 DEN=1600
DEFINE 'FILE THREE' NGEN=1 DEN=6250
DEFINE 'FILE FOUR' NGEN=1 DEN=CART
Setting the Mode on Scratch Tapes
CA Dynam/T only selects a scratch tape on a drive capable of writing in the

desired mode when AVR is performed for output. If CA Dynam/T cannot find
one, it issues message CADT008D:
CADT008D MOUNT SCRATCH dtfname SYSnnn DSN=data-set-name OWNER=xx

MODE=xxxx SIZE=xx JOB=jobname
CADT008D MOUNT SCRATCH dtfname ON cuu DSN=data-set-name OWNER=xx
MODE=xxxx SIZE=xx JOB=jobname
You can reply with the responses mentioned in Answering Mount Messages.
When the message specifies a particular drive, CA Dynam/T verifies that the
requested mode can be written before making the assignment. You can
respond cuumm to override the requested mode for this version only. For
example, if you reply 280D0 to the MOUNT message above, CA Dynam/T
creates the tape on drive 280 in 6250 mode.
If no mode is specified for the data set, CA Dynam/T does not check or set the
mode. It uses the mode specified in the PUB for the device allocated (VSE
standard).
Setting the Mode for Uncontrolled Tape Files
You can also assign recording density in the following ways:
For uncontrolled tape files in response to the CADT001D unassigned

output message; a response of cuumm sets the specified mode when the
assignment is made.
In the file-ID field of the TLBL statement
Tape Cartridges
CA Dynam/T capabilities in utilizing tape cartridges enable it to do the

following:
Stack nonstandard files and locate them.
Free up the channel for other activity.
2–46 User Guide

Using CA Dynam/T
Speed up the positioning for tape cartridge devices.
Use the Tape Status Display for tape drive and volume information.
Read stacked standard and nonstandard files in ascending, but not

necessarily sequential, order.
Multifile Positioning and Locating
CA Dynam/T uses the READ BLOCKID and LOCATE BLOCK channel commands
for positioning and locating files within multifile data sets for tape cartridges.
This facilitates tape reel positioning for multifile data sets that contain
nonstandard file structures.
When a file is created on a tape cartridge, CA Dynam/T issues the READ

BLOCKID command to retrieve the physical location and the logical block
position of the file. This information is stored in the CA Dynam Catalog. When
the file is requested for input, CA Dynam/T uses that information to issue a
LOCATE BLOCK command. The same method is used to position a tape to the
end of current files on a volume when writing the second or subsequent file in
a multifile data set.
Stacking Files
Standard and nonstandard files can be stacked on the same tape. For
example, VSAM and non-VSAM files can be backed up to the same tape. Thus,
you can avoid creating largely empty tapes on tape cartridges.
The Status Display
CA Dynam/T uses the status display to communicate volume and drive

information. This display is updated during the following times during
CA Dynam/T processing:
During AVR (when a drive is eligible for AVR), up to the point when a tape
is selected for use
When the CA Dynam/T STATUS command is issued
During final input/output processing for controlled, unlabeled volumes or

for volumes initialized on the fly
Format:
iiiiii u
or
iiiiii f

Managing Special Files
iiiiii the tape drive status; it can be one of the following:
NOVOL1 Tape is at loadpoint but does not contain a VOL1 record.
NT RDY Sense information received from the drive shows that the
drive is not ready.
NLDPNT Sense information received from the drive shows that the
drive is ready, but not at load point.
volser Drive is at load point and contains a VOL1 record.
u an unprotected, write capable tape.
f a protected file.
The Status Display will remain until the volume is physically removed from the
drive, or until the next load/unload cycle.
Using Work Data Sets
The CA Dynam/T work data set lets you use tape as intermediate storage for a
file while processing a job, then return the tape to the scratch pool when
processing is completed.
Establish the work data set with the DYNCAT DEFINE command. Include the
WORK=YES parameter. For example, this DEFINE statement establishes a
work data set named BGWORK:
DEFINE 'BGWORK' WORK=YES TAPE
Altering Retention Characteristics
You cannot specify retention characteristics for a work data set (such as
cycles, days, or AS-OF-DATE), because a work data set is, by definition,
temporary. You can modify its retention criteria, however, with the DYNCAT
ALTER command.
2–48 User Guide

Releasing Work Data Sets
Work data sets have two characteristics which differentiate them from other
data sets. They are as follows:
You can release work data sets and return them to the scratch pool
immediately at CLOSE by specifying the RELEASE option (R or 04) on the
TLBL statement.
Unreleased work data sets are retained for as long as specified in the
CA Dynam/T option record. While in use, work data sets are completely
protected. You can release them at any CLOSE (input or output).
Defining Independent Files
Both partition-independent and CPU-independent files are supported by all

CA Dynam/T batch programs.
Partition-Independent Files
CA Dynam/T's support for partition-independent files allows work data sets to

be used in any partition without JCL modification. If the two characters '=='
are found in the file ID when a TLBL is processed at program OPEN,
CA Dynam/T replaces them with the SYSLOG ID (partition identifier) of the
partition in which the job is running.
For example, if the following TLBL were processed in the BG partition,

CA Dynam/T would replace the file ID '==WORK' with BGWORK.
// TLBL SYS010,'==WORK'
If the same TLBL were processed in the F3 partition, the resulting file ID would
be F3WORK.
Establish one (or more) work data set names for each partition with DYNCAT;
CA Dynam/T makes sure that the same name is never used in more than one
partition simultaneously.
Example:
DEFINE 'BGWORK' WORK=YES

DEFINE 'F1WORK' WORK=YES
DEFINE 'F2WORK' WORK=YES
For users running other software which changes the SYSLOG ID, the special ID
characters (==) are replaced with the appropriate SYSLOG ID found in the
PUB2.

CPU-Independent Files
It may be necessary to differentiate between systems, as well as between

partitions, in a multi-CPU environment (multiple real or multiple virtual
systems). Generate this support by doing both of the following:
Specifying the MULTCPU(YES) in the DYNAM/T option record
Updating the system adapter option record. This option record, the same
used for multi-CPU support for CA Dynam/D, produces a table of CPU
serial numbers, each associated with a unique identification character.
These characters are used to provide CPU-independent data set names in
conjunction with partition-independent data set names.
Examples:
// TLBL dtfname,'==@WORK' (partition- and CPU-independent)

// TLBL dtfname,'@WORK' (CPU-independent)
The special character @ will be replaced with the CPU ID established for the
machine. The CPU ID character can appear in either of the following ways:
Following or preceding the partition ID characters as in the first example
Alone as the ID in the second example
If the TLBLs above were processed in the BG partition in machine A, the

resulting data set names would be BGAWORK and AWORK, respectively.
The following CPU-independent substitutions are supported by CA Dynam/T:
Substitution Example Resolved Data Set Name
@ @WORK AWORK
== ==FILE BGFILE
@== @==WORK ABGWORK
==@ ==@FILE BGAFILE
=== ===WORK BGAWORK
If the CPUID definition phase has not been cataloged, a default value of A is
used whenever the CPUID is required by the system.
For more information about instructions on updating the CPUID System

Adapter option record and an illustration of how to use it, see the CA CIS
Administrator Guide.
2–50 User Guide

Example:
Partition- and CPU-independent work files
BG // JOB ARRPUPD
DATE 01/22/00, CLOCK 20/14/03
BG // TLBL TAPEOUT,'==@WORK,W'
BG // EXEC MSTROUT
BG CADT007I ***** WORK TAPEOUT SYS011=299 100524 1 *BGAWORK*
BG CADT031I *CLOSED* TAPEOUT SYS011=299 100524 BGAWORK BLK=29
BG // TLBL TAPEIN,'==@WORK,W,R'
BG // TLBL TAPEOUT,'AR RP MSTR,W'
BG // EXEC MSTRIO
BG CADT032I ASSIGNED TAPEIN SYS010=299 100524 BGAWORK
BG CADT007I ***** LABEL TAPEOUT SYS011=29A 100699 1 *AR RP MSTR*
BG CADT028I RELEASED TAPEIN INPUT 100524 BGAWORK
BG CADT031I *CLOSED* TAPEOUT SYS011=29A 100699 AR RP MSTR BLK=29
BG CADA102I AUDIT TRAIL FILE IS 10 PERCENT FULL.
BG EOJ AURPUPD
A temporary data set is created in one step, which can then be inputted or
scratched. The TLBL contains the partition- and CPU-independent data set
name '==@WORK'. CA Dynam/T replaces '==@' with BGA, creating the data
set name BGAWORK, because the job is run in BG partition in CPU A. The W
option forces the file to be rewound, ready for the next step. In the next step,
the file is used for input and both the W and D options are indicated, causing
the tape to be both of the following:
Released or returned to SCRATCH status
Rewound, ready for use as output when next needed
Also note the informational message, CADA102I, above from AUDIT.
Partition- and CPU-independent work files
F2 // JOB ARRPUPD
DATE 01/22/00,CLOCK 20/19/06
F2 // TLBL TAPEOUT,'==@WORK,W'
F2 // EXEC MSTROUT
F2 CADT008D MOUNT SCRATCH TAPEOUT SYS011 DSN=F2AWORK JOB=ARRPUPD
F2 STATUS
F2 CADT015I 298-UA-*DOWN*
F2 CADT015I 299 - BG - SYS010,*
F2 CADT015I 29A - BG - SYS011,*
F2 CADT008D MOUNT SCRATCH TAPEOUT SYS011 DSN=F2AWORK
F2 STOP

AR CASTART BG
BG
BG EOJ PAUSE
F1 1Q34I BG WAITING FOR WORK
F1 1Q34I LST WAITING FOR WORK ON 02E
AR CASTART F2
F2 CADT007I **** WORK TAPEOUT SYS011=299 100723 1 *F2AWORK*

F2 CADT031I *CLOSED* TAPEOUT SYS011=299 100723 F2AWORK BLK=5
F2 // TLBL TAPEIN,'==@WORK,W,R'
F2 // TLBL TAPEOUT,'AR RP MSTR,W'
F2 // EXEC MSTRIO
F2 CADT032I ASSIGNED TAPEIN SYS010=299 100723 F2AWORK
F2 CADT007I **** LABEL TAPEOUT SYS011=29A 100665 1 *AR RP MSTR*
F2 CADT028I RELEASED TAPEIN INPUT 100723 F2AWORK
F2 CADT031I *CLOSED* TAPEOUT SYS011=29A 100665 AR RP MSTR BLK=55
F2 EOJ ARRPUPD
The same job stream as in the previous example is run in partition F2. When
no available scratch tape is found during AVR, CA Dynam/T issues the
CADT008D MOUNT message. The operator responds with STATUS, and finds
that tape drives are either DVCDN (298) or assigned in another partition (299
and 29A). Then the operator issues the STOP command to place the partition
in a wait state and free the console until a tape drive becomes available. The
job running in BG finishes, F2 is restarted with the CASTART command, and
processing continues.
Following a CASTART to awaken a STOPPED partition, CA Dynam/T performs

AVR again before reissuing the MOUNT message. The scratch tape, which is
now available, is automatically allocated as F2AWORK; the job stream
continues as in the first example.
2–52 User Guide

Running Tests with Production JCL
You do not have to catalog new versions of output data sets when running
tests with production JCL. The programmer test option enables you to define a
$TEST jobname in the following ways:
In the DYNAM/T option record, you can define test jobs by specifying an
identifying character string and its starting position within the jobname.
For example, if the DYNAM/T option record specifies:
TESTJOB($$$,6)
then the following job names will be considered test jobs:
PRODT$$$ but not $$$PRODT

PAYRL$$$ but not PAY$$$
If no user-defined name is specified in the DYNAM/T option record,

CA Dynam/T defaults to the string $TEST at position 1 of the jobname.
When you run a test job, CA Dynam/T does not update the Catalog file at
CLOSE for output data sets. Otherwise, the system functions as usual. All
input files are selected through AVR; output scratch tapes are allocated.
Examples:
DYNAM/T option record Valid test job JCL statement
TESTJOB(TJOB,3) // JOB PRTJOB

// JOB ARTJOB1
(default) // JOB $TESTPR

// JOB $TESTAR1
Cataloging Output Tapes
Output tapes do not become new versions of the data sets. They are cataloged
as TEST status tapes and are retained until the next DYNCAT SCRATCH
command is run, returning them to SCRATCH status. They will not be called
for as input to production runs. If you request their data set name as input
during a subsequent step of a $TEST job, CA Dynam/T calls the most current
$TEST version as though it were a member of the data set.
You can fully test JCL for jobs that create a file in one step, and then read the
newly created file in a later step. If you request a data set on input which
contains no test versions, CA Dynam/T inputs the appropriate production
version.

Using Cataloged Information
Note: All output $TEST multifile data sets are created as single file data sets
with a file sequence of one on separate volumes, because of the many
combinations of production and $TEST tapes possible in a multifile set. This is
to allow testing of a production jobstream that might start by creating other
than the first file in a multifile sequence where the previous files were created
by a true production job. In this way, the mixing of production and test data
on the same volume is prohibited.
Inputting Test Versions
You must use one of the following methods to input test versions to production
runs:
As uncontrolled files
Through use of the ACCEPT response to a MOUNT message
By adding them to the production data set by DYNCAT maintenance
Daily Catalog Maintenance
DYNCAT is the general purpose utility program for CA Dynam.
Basic Catalog Functions
Schedule a run of DYNCAT at least once daily to do the following:

Perform the SCRATCH command
Back up the Catalog file
Produce a current data set list
The following sample job stream performs these functions. You can perform
other functions, as well.
2–54 User Guide

Example:
// JOB DAILY REPORTS

// TLBL IJSYSBK,'CA Dynam/T BKUP',,,,,,2
// DLBL WORK1,'WORK FILE',O,SD
// EXTENT SYS001...
// EXEC DYNCAT,SIZE=128K
BACKUP
SCRATCH
/*
/&
This job stream produces all required daily reports. It first backs up the
Catalog file and verifies its integrity. Then it returns all eligible volumes to the
SCRATCH pool. It also provides the following:
A list of all scratched tapes
An exception list
A list of all active data sets and their associated volumes in alphabetic
sequence
A list of all volumes in numeric sequence
The sequence in this example is highly recommended; the backup step

ensures that you will be notified of any errors found in the Catalog. It also
produces a tape file from which you can rebuild the Catalog if necessary.
Use only the DYNCAT BACKUP command to back up the Catalog. No other
utility or user-written program properly resolves the internal pointers used in
the Catalog file.
Reporting Exceptional Occurrences
CA Dynam/T enables you to record exceptional occurrences. You can report

these occurrences upon request or whenever the DYNCAT SCRATCH command
is performed.
Also, transactions can be logged to the audit file and can be reported upon
using AUDTUTIL.
Exceptional occurrences include the following:
Manually cataloging a version of a data set
Returning a tape which has not been initialized under CA Dynam/T to

SCRATCH status
Using a CA Dynam/T initialized scratch tape as output for an uncontrolled

file (generation option)

Responding ACCEPT to a MOUNT message to force input of a data set or

version other than the one called for by the system (generation option)
Responding ALTER to drop a TLBL, thus forcing an alternate TLBL to be

used (generation option)
There are other Catalog maintenance and reporting utilities besides DYNCAT.
This guide describes them in detail.
Protecting the Catalog
Catalog Owner ID
CA Dynam/T places a 16-character owner ID in the VOL1 label of every tape

created under its control. The first ten characters of this ID associate the
volume with the CA Dynam Catalog, controlling it. The 16-character name is
established when you initialize the Catalog and is derived from the ID
parameter of the DYNCAT INITIAL command:
INITIAL id='COMPANY ID NAME' PASSWORD='PASSWORD'
You can use the DYNCAT OWN command to change the Catalog ID at any
time. It is best, however, to establish a unique ID when first initializing the
Catalog and to maintain that ID for the life of the Catalog.
Catalog Password
The CA Dynam Catalog is password protected. Specify an eight-character

literal for the password in the DYNCAT INITIAL command when creating the
Catalog. There is no default password. This password cannot be modified. It
also cannot be accessed by any report, and must therefore be carefully saved.
You must specify the Catalog password to gain access to the passwords of
individual password-protected data sets.
Examples:
This DYNCAT statement initializes the Catalog and specifies a Catalog

password of UNLOCK.
INITIAL id='COMPANY ID NAME' PASSWORD='UNLOCK'
This TDYNUTL statement produces a list of all password-protected data sets

with their passwords. Access to the Catalog password should be controlled.
LIST PASSWORD='UNLOCK'
2–56 User Guide

Protecting Data Sets
Password Protection
Specify a data set password in the DYNCAT DEFINE command to protect

individual data sets from unauthorized access.
The following example assigns the password RESTRICT to the data set. The
password is required before the characteristics of the data set can be manually
modified.
DEFINE 'PAYROLL FILE' NGEN=7 PASSWORD='RESTRICT'
To modify the number of retention generations for PAYROLL FILE, you must
issue the following command:
ALTER 'PAYROLL FILE' PASSWORD='RESTRICT' NGEN=5
The password is not required for online access to the data set or DYNCAT ADD
modifications of the data set. Use the ALTER command's LOCK option to
prohibit all modifications to a data set (locking the data set):
ALTER 'PAYROLL FILE' LOCK PASSWORD='RESTRICT' (The proper password unlocks the
data set.)
There can be no maintenance on a locked data set; no new versions can be

created. The existing versions of the data set can still be called for as input,
however. You can lock out input access, as well:
ALTER 'PAYROLL FILE' UNLOCK PASSWORD='RESTRICT'

ALTER 'PAYROLL FILE' VERSION=1 LOCK PASSWORD='RESTRICT'
ALTER 'PAYROLL FILE' LOCK PASSWORD=RESTRICT
To lock a particular version, the data set as a whole must first be unlocked.
To change a data set password, use the ALTER command. The following
example replaces the PAYROLL FILE password, RESTRICT, with the new
password, SECURITY.
ALTER 'PAYROLL FILE' PASSWORD='RESTRICT' NEWPSWD='SECURITY'
Establishing Data Set Ownership
You can establish data set ownership with the DYNCAT DEFINE and ALTER
commands. This is different from Catalog ownership. Data set ownership
enables you to divide the tape library into sublibraries.

Limiting Tape Allocation
The tapes that can be allocated for a data set are limited by data set
ownership to a particular group of volumes, as follows:
All active owned versions of a data set retain the ownership, even after
scratching. Ownership is specified on all data set reports. During AVR,
CA Dynam/T selects output scratch tapes with the same owner as the data
set for which they are required (if the data set has an established owner).
If a scratch tape with the same owner is not available, the operator can
reinitialize another scratch tape to the requested owner.
Retaining Data Set Ownership
A volume's data set ownership code is not a physical part of the VOL1 or HDR1
of the tape. Thus, if a scratch volume is added to a data set which has a
certain owner code, the volume is immediately considered a member of that
owner group. You do not have to reinitialize the tape. When this volume is
scratched, it retains the ownership of the last data set of which it was a
member.
Verifying Tape Ownership
The Catalog owner ID enables CA Dynam/T to verify the ownership of tapes

during AVR. This prevents tapes received from other installations using
CA Dynam/T from being confused with your installation's tapes.
Most installations use numeric volume serial numbers; a tape received from
another CA Dynam/T user could easily contain a volume serial identical to one
in the Catalog as a scratch tape.
By placing a unique owner ID on the VOL1 label of tapes associated with a

particular Catalog, and specifying CATCHK(YES) in the DYNAM/T option record,
CA Dynam/T can be directed to require output scratch tapes to have an owner
ID matching that of the installation. If CATCHK(NO) is specified, the owner ID
will be placed in the VOL1, but no Catalog ownership checking will be
performed during AVR.
Use the DYNCAT INT, INTR, SCRPOOL, and ALTER volser commands to
establish an ownership code for a volume. These two-character ownership
attributes are maintained in the Catalog file.
2–58 User Guide

Example:
Mode control and data set ownership
BG // JOB DYNCAT BACKUP

DATE 01/22/00,CLOCK 21/02/48
BG // TLBL IJSYSBK,'CA Dynam/T BKUP',,,,,,2
BG // EXEC DYNCAT
BG
BG CADC426I DYNAM BACKUP
BG CADT008D MOUNT SCRATCH IJSYSBK SYS006 DSN=CA Dynam/T BKUP
OWNER=OP MODE=1600 JOB=DYNCAT
BG 299
BG CADT010D VOLSER 100034 ALREADY IN FILE AS AR OWNER=MD
BG
BG CADT008D MOUNT SCRATCH IJSYSBK SYS006 DSN=CA Dynam/T BKUP
OWNER=OP MODE=1600 JOB=DYNCAT
BG
BG CADT007I **** LABEL IJSYSBK SYS006=29A 100007 1 *CA Dynam/T BKUP*
BG CADC003I ENQUEUED FOR BATCH PROCESSING DDNAME=CAICATL
BG CADC004I CATALOG DEQUEUED DDNAME=CAICATL
BG CADT031I *CLOSED* IJSYSBK SYS006=29A 100007 CA Dynam/T BKUP BLK=107
BG
BG EOJ DYNCAT
The DYNCAT BACKUP command backs up the Catalog files. Data set
CA Dynam/T BKUP is established with mode 1600 and owner OP. Option 2 is
used on the TLBL to force unload at CLOSE. A scratch tape with the specified
owner is not found on a drive capable of writing in 1600 mode; a subsequent
CADT008D MOUNT message is issued specifying owner OP and mode 1600.
The operator responds 299.
However, the tape on 299 has a mismatching owner, so message CADT010D is

issued. The operator responds EOB/END, and mounts a tape with owner OP on
29A. 29A is capable of writing in 1600 mode, the volume is allocated and
processing continues.
The operator could also have responded to the CADT010D message with
ACCEPT; then the indicated volume would be reinitialized with owner OP.

IBM Hardware Based Tape Encryption Support

The IBM JCL statement, Key Encryption Key Label (KEKL), allows a user to
associate a tape unit with one or two key-encryption-key labels. The key-
encryption-key labels are passed to the control unit by the VSE supervisor
which in turn communicates with the Encryption Key Manager (EKM), to
validate the encryption keys. If the key verification is successful, the tape data
will be encrypted when written to the tape. The tape unit specified in the KEKL
statement must already be assigned to an encryption-capable drive before the
KEKL statement is processed by job control.
The KEKL information specified on the KEKL statement can be maintained in

the Dynam catalog. Dynam/T passes the KEKL information to VSE using the
VSE MODCTB macro interface. When requested to do so, Dynam/T finds an
available encryption-capable drive, makes the assignment, and then passes
the appropriate KEKL information to VSE. Defining the KEKL information in the
catalog removes the need to pre-assign encryption capable drives, thus
allowing for automated tape encryption processing. The KEKL information can
be maintained online using CUI and in batch using the DYNCAT DEFIINE and
ALTER commands.
IBM has added four modes to indicate a file should be encrypted when written
to tape. Accordingly, support for new density values has been added to Dynam
which, when specified, indicates that a particular data set should be encrypted
when written to tape.
Note: Even if a dataset is defined with KEKL information, the dataset will only
be encrypted if the dataset is defined with an encryption type density. If the
density specification for the dataset is a non-encryption mode the KEKL
information for the dataset is ignored by CA Dynam/T.
Automatic Cataloging/Uncataloging
Activating Automatic Cataloging
The AUTOCAT(YES) option in the DYNAM/T option record permits automatic

cataloging of new data sets when the first output OPEN is issued; a DYNCAT
DEFINE is not necessary for the data set. If you have selected AUTOCAT(NO),
automatic cataloging is available when the CA Dynam/T TLBL option C is
specified.
Automatic cataloging occurs if all of the following is true:
An output OPEN request is issued.
A TLBL exists in the label area matching the dtfname.
2–60 User Guide

The TLBL contains a valid file ID.
The file ID found does not exist in the Catalog.
If all four of these conditions are met, CA Dynam/T generates a Catalog data
set base record for the data set name in the TLBL. The default values are
those specified in the DYNAM/T option record. You can use the DYNCAT ALTER
command to change these values for the new data set.
Removing Catalog Entries Automatically
Data sets which have been added to the Catalog by way of the automatic
catalog feature can be automatically removed from the Catalog. If you
specified AUTCATD(YES) in the DYNAM/T option record, CA Dynam/T
automatically deletes any data set that was automatically added when the last
active version in the data set is scratched.
This option provides a powerful tool for testing and controlling temporary data
sets on tape without requiring Catalog maintenance. You can create a test
version under a unique data set name with specific retention by simply coding
options on the output TLBL. When the specified retention has passed,
CA Dynam/T returns the tape to SCRATCH status, automatically removing the
test data set name from the Catalog.
Example:
Create the data set JOES.TEST and retain it for thirty days.
// TLBL MYFILE,'JOES.TEST,C',30
At the end of the thirty days, CA Dynam/T deletes the data set without any
manual Catalog intervention.
Sending File-Dependent System Messages
There is often a need to communicate with your Operations staff concerning

specific processing for a certain file at a certain time. Supplementary message
support provides a flexible means of defining your own messages and sending
them to the system console or printer at one or more of four points in file
processing.
You can define these messages in the Catalog by using the DYNCAT DEFINE or
ALTER commands. They will be issued automatically by the system at the
indicated point. For more information, see the chapter "Maintaining the
Catalog—DYNCAT Program."

Processing Predefined Multifile Volume Data Sets
For example, this statement defines a message to be sent at output CLOSE

time:
DEFINE 'CONVERT.FILE' COMSG='SEND TAPE TO DALLAS WITH COURIER TONIGHT'
At output CLOSE time, the following message displays on the console:
CADT999I SEND TAPE TO DALLAS WITH COURIER TONIGHT
Supplementary message definitions can be specified as follows:
To Issue A At Specify
CADT996I message Open Input time OIMSG=msg text
CADT997I message Open Output time OOMSG=msg text
CADT998I message Close Input time CIMSG=msg text
CADT999I message Close Output time COMSG=msg text
Supplementary messages are supported for both CA Dynam/D and

CA Dynam/T users. If a data set contains a supplementary message, the
message will be issued regardless of whether the file is processed as a tape or
a disk file.
Message output can be optionally directed to SYSLST, SYSLOG, or both. For

more information about instructions on maintaining these messages, see the
DYNCAT DEFINE/ALTER commands.

CA Dynam/T provides extensive support for multifile-volume data sets. Each
file is cataloged to the system and controlled separately, but always in the
desired sequence. Define multifile data sets with the DYNCAT DEFINE
command. Catalog the first file in the following manner:
Specify all of the multifile data set attributes only for the first file.
Catalog all subsequent files with the DEFINE command, specifying only the
data set name for the file being cataloged and the data set name for the
previous file on the volume. For example,
DEFINE 'DATA SET NAME' PREVFILE='PRIOR FILE'
Multifile data sets can also be supported as predefined or unchained data sets.
This means the data sets do not need to be written to tape in an exact order
and the data sets do not need to be predefined to the Catalog as multifile data
sets. The TLBL STACK option lets you specify a file's place within a multifile
data set.
2–62 User Guide

Redefining Retention Characteristics
Retention attributes defined for the first file are automatically defined for all
subsequent files. Use the DYNCAT ALTER command to assign different
retention characteristics to any but the first file.
Keep in mind that predefined multifile data sets are listed alphabetically on
CA Dynam/T reports. Name these data sets so that they will appear together
on the reports.
Examples:
Defining a multifile-volume
This job stream catalogs four files for a multifile-volume, each with 3-cycle
retention. The files will always be written in the specified sequence: FILE 1 is
the first file on the tape and FILE 4 is the last.
// JOB DEFINE MULTI-FILE SET TO CATALOG

// EXEC DYNCAT
DEFINE 'FILE 1' NGEN=003
DEFINE 'FILE 2' PREVFILE='FILE 1'
/*
/&
You can add a file to the end of the tape.
Example:
// JOB DEFINE ADDITIONAL FILE

// EXEC DYNCAT
/*
/&
Note:
You cannot directly catalog a file between two existing files on a multifile-
volume data set. Delete the first data set, which deletes all following data
sets. Then catalog all data sets correctly.
CA Dynam/T takes the file sequence number from the Catalog. Do not
include it on the TLBL statement—it will be ignored.
Creating versions of the same multifile data set simultaneously can lead to
errors and is unsupported.

Maintaining Predefined Multifile Volume Data Sets
The following restrictions apply to DYNCAT maintenance of predefined

multifile-volume data sets:
You cannot perform the RENAME command on any file of a multifile set.
If you perform the DELETE command on one file, CA Dynam/T applies it to

all subsequent files of the multifile set, as well.
If you perform the ALTER command on one file, it is performed only on the
named file—not on all files of a multifile set.
If you use the ADD command for a multifile data set, the ADD commands
must be performed in proper order.
For multifile data sets, you cannot specify TAPEOPT=AUTOSCR as a

parameter of the DEFINE or ALTER commands.
Example:
Volume 4685 is to be added as the current version of FILE 1, FILE 2, FILE 3,

FILE 4, and FILE 5.
// JOB ADD TO A MULTIFILE SET

// EXEC DYNCAT
ADD 'FILE 1' VOLSER=(4685)
/*
/&
Automatic Tape Positioning
AVR functions in its usual manner for the first file of a multifile data set.
However, CA Dynam/T automatically positions subsequent files only if AVR can
locate the volumes. The tape must be at load point. Otherwise, you must
assign the logical unit external to the AVR facility by doing the following:
Indicate the HOLD option to use a logical unit from the previous file
Respond cuu to the MOUNT message
CA Dynam/T fully supports multifile, multivolume data sets, as follows:

Suppose one file has been created on a volume and another file is to be
created next. CA Dynam/T issues a MOUNT message for the required
volume if AVR cannot locate it. When you try to create a subsequent file,
CA Dynam/T issues an error message and cancels the job if all prior files
do not already exist on the tape.
2–64 User Guide

Suppose file three ends on volume one. When you create file four,
CA Dynam/T calls for volume one and correctly positions the tape.
You can issue the ACCEPT override for multifile data sets in response to the
CADT004D MOUNT message (not the CADT005D WRONG TAPE message):
ACCEPT DSN='data set name',VER=nnn

ACCEPT DSN='data set name',VOL=nnnnnn
This ensures that the correct multifile version is read. Correct positioning can
be performed only through the Catalog definition for multifile versions.
Processing Without Additional Positioning
When opening tape files that are members of a multifile set, CA Dynam/T
modifies the DTF to NOREWIND. The file can subsequently be processed
without additional positioning, so that you can process files as multifile data
sets even if they were not originally so intended. Use any of the tape
positioning options on the TLBL or in the Catalog to override the default
specification.
Assure maximum efficiency by carefully planning multifile data set processing

and applying the appropriate TLBL options. Although CA Dynam/T makes sure
that the tape is correctly positioned and the proper file read when requested,
excessive time may be spent rewinding and forward-spacing the tape.
Example:
Creating a multifile-volume data set
BG // JOB ARDESCUP
DATE 01/22/00,CLOCK 20/34/09
BG // TLBL TAPEOUT,'AR DESC 1',,,,,,24
BG // EXEC MSTROUT
BG CADT007I **** LABEL TAPEOUT SYS011=299 100723 1 *AR DESC 1*
BG CADT031I *CLOSED* TAPEOUT SYS011=299 100723 AR DESC 1 BLK=12
BG // EXEC MSTROUT
BG CADT023I **** DSN 'AR DESC 2' FILE NO. 2 BEING CREATED ON TAPE
100723 299
BG EOJ ARDESCUP
BG // JOB ARDESCUP
DATE 01/22/00,CLOCK 20/35/25
BG // EXEC MSTROUT
BG CADT020D MOUNT VOLUME 100723 FOR FILE NO. 3 DSN='AR DESC 3' SYS011
BG CADT023I **** DSN 'AR DESC 3'FILE NO. 3 BEING CREATED ON TAPE

100723 299
BG EOJ ARDESCUP
Data sets AR DESC 1, AR DESC 2, and AR DESC 3 have been previously

defined with DYNCAT commands. In the first job, the first TLBL is submitted
with option 24 (8 to prevent early drive release, and 16 to drop the TLBL at
CLOSE).
Option 8 prevents AVR for the second OPEN, directing CA Dynam/T to the
same drive used for file 1, because the same volume is to be used for file 2 on
the same logical unit. The 16 option is required, because the same dtfname is
used for both TLBLs; when the file is opened the second time, the current TLBL
will be used.
In the second job, AVR cannot locate the required volume; the CADT020D
message is issued. When the volume is located, it is assigned and positioned
for file 3, which is then created.
Example:
Multifile volume input and output
F2 // JOB ARDESCUP
DATE 01/22/00,CLOCK 20/46/38
F2 // ASSGN SYS010,299
F2 // TLBL TAPEIN,'AR DESC 1,H,D'
F2 // TLBL TAPEIN,'AR DESC 2,H,D'
F2 // TLBL TAPEIN,'AR DESC 3,U'
F2 // ASSGN SYS011,29A
F2 // TLBL TAPEOUT,'AR DESC 1,H,D'
F2 // TLBL TAPEOUT,'AR DESC 2,H,D'
F2 // TLBL TAPEOUT,'AR DESC 3,W'
F2 // EXEC MSTRIO
F2 CADT007I **** LABEL TAPEOUT SYS011=29A 100744 1 *AR DESC 1*
F2 CADT031I *CLOSED* TAPEOUT SYS011=29A 100744 AR DESC 1 BLK=12
F2 // EXEC MSTRIO
F2 CADT023I **** DSN 'AR DESC 2' FILE NO. 2 BEING CREATED ON TAPE
100744 29A
F2 // EXEC MSTRIO
F2 CADT023I **** DSN 'AR DESC3' FILE NO. 3 BEING CREATED ON TAPE
100744 29A
F2 EOJ ARDESCUP
2–66 User Guide

Processing Unchained Multifile Tapes
A multifile-volume is to be read and a new version created in one job stream.

Options direct CA Dynam/T to the correct tape drives for the second and third
files.
Example:
Multiple TLBLs with identical DTFNAMES
Submit identical dtfnames consecutively if you are including them in one job
step. This restriction is imposed by IBM label record management routines.
// TLBL UIN,'FILE1,H,D'
// TLBL UIN,'FILE3,W'
// TLBL UOUT,'OUTPUT FILE1,H,D'
// TLBL UOUT,'OUTPUT FILE3,H'
NOT
// TLBL UIN,'FILE3,W'
// TLBL UOUT,'OUTPUT FILE3,W'

The STACK= TLBL option can be used to specify that a file is to be part of a
multifile set. To use this feature you have to code a STACK= parameter on
each TLBL of a multifile set.
Valid STACK parameters are A to Z, 1 to 9, and ‘*’. By default, A to Z cause

the tape to rewind at close and 1 to 9, or ‘*’, cause the tape not to rewind at
close. Aside from this, there is no difference between one STACK= parameter
and another. They simply allow a way to differentiate one unchained multifile
tape from another within the same jobstream.
By using the HOLD(H) TLBL option with no close tape disposition, R, U, and so
on, the rewind default for the A to Z parameters can be overridden so that the
tape does not rewind at close. You cannot have chained DSNs and unchained
DSNs on the same tape.
To stack other files on a tape you must always reference the last active file on
that tape.

The first DSN in the unchained multifile set dictates all volume criteria,
density, tape length, and so on, for that tape and subsequent files, regardless
of what is specified on the TLBL or the Catalog.
All output $TEST multifile data sets (unchained or predefined) are created as
single file data sets with a file sequence of one on separate volumes.
Unchained multifile versions are scratched when they become eligible

regardless of the location of the file on the tape. After a volume contains no
active files (all unchained files are in scratch status), the volume is returned to
scratch status.
File sequence numbers for unchained multifile versions are relative to the start
of the volume on which the file exists. File sequence numbers for predefined
multifiles are relative to the volume that starts the whole multifile set. In
effect, the file sequence for unchained versions start over with each new tape
volume, where predefined versions continue incrementing from the first file on
the first volume of the set.
The following illustrates this point:
DSN VOLSER FILESEQ FILESEQ

PREDEFINED UNCHAINED
dsn1 tape01 1 1
dsn2 tape01 2 2
tape02 2 1
dsn3 tape02 3 2
dsn4 tape02 4 3
tape03 4 1
The following JCL examples show how to create multifile data sets using the
STACK= option.
Examples:
Adding a file to an active tape
Note: REF must be used as the DTFNAME and filea must be the last active file
on that VOLSER.
// TLBL REF,'filea',STACK=A
// TLBL NEWFILE,'fileb',STACK=A
// EXEC pgm
Create a new multifile set on a scratch volume:
// TLBL OUT1,'filea',STACK=B
// TLBL OUT2,'fileb',STACK=B
// TLBL OUT3,'filec',STACK=B
2–68 User Guide

Using Automatic Multifile (AMF) Data Sets
Creating a new multifile set in multiple steps:
// TLBL OUT,'filea',STACK=*
// EXEC pgm
// TLBL REF,'filea',STACK=*
// TLBL OUT,'fileb',STACK=*
// EXEC pgm
// TLBL REF,'fileb',STACK=*
// TLBL OUT,'filec',STACK=*
// EXEC pgm

CA Dynam/T incorporates a special feature to automatically generate multifile
data set names at output open time. The system adds another data set to the
multifile set if both the following conditions are satisfied:
The first data set on the multifile set was cataloged with this option.
The special data set for the file is in the TLBL.
Generating AMF File Numbers
Three asterisks (***) in the TLBL's DSN indicate to CA Dynam/T that this
could be an automatic multifile (AMF) data set. CA Dynam/T replaces the three
asterisks with a three-digit number if the following conditions are satisfied:
If you are opening the file as output, CA Dynam/T generates this number
by adding one to the number of the previous file in the AMF set.
If the file is opened as input, CA Dynam/T retrieves this number from the
Catalog. The number is determined by any one of the following, in the
same order of priority shown here:
1. File sequence number from the TLBL
2. Version number from the TLBL or the relative generation
3. Three numbers of the last-created AMF data set
Creating an Automatic Multifile Data Set
Create automatic multifile data sets with the DYNCAT DEFINE command. The
parameter MF=AUTO in the DEFINE statement indicates this is an AMF data
set. The PREVFILE parameter is not permitted. The DSN must contain three
asterisks (***), or it will be rejected. This defines the base data set name for
the AMF set. This name should permanently reside in the Catalog.

Any combination of letters and numbers can be used as with any other DSN.
The only restriction is that there must be three asterisks (***) somewhere in
the DSN; they indicate where the three-digit numbers will be inserted.
The following are valid data set names for AMF data sets:
'AMF***'
'PAYROLL BACKUP***'
'FILE***PR TRANS'
Example:
This DEFINE statement creates a multifile data set named 'AMF***'. It is the
prototype for the AMF set.
DEFINE 'AMF***' NGEN=1 MF=AUTO
A program creating the file above using file name OUTFILE would require a
TLBL as below:
// TLBL OUTFILE,'AMF***'
The first time this job is run, CA Dynam/T creates version one of data set
AMF001. The next time, CA Dynam/T finds a valid version for AMF001; it
subsequently creates a new data set, AMF002.
If the data set AMF002 was not closed or if it was closed and later scratched
manually, this same DSN would be used the next time the job was run. In
other words, the last file on the existing AMF set is checked to see if it contains
a good version. Depending on whether it contains a valid version CA Dynam/T
does the following:
If it does contain a valid version, CA Dynam/T adds one to the DSN and
creates a new DSN as the last file on the AMF set. Each data set created
will have the same characteristics (retention, owner, and so on.) as the
base data set.
If it does not contain a valid version, CA Dynam/T uses the DSN again.
Volume Switching with AMF Data Sets
CA Dynam/T provides automatic volume switching when end-of-volume is

reached.
Use the DYNCAT ALTER command whenever you want to start the next file on
a separate volume:
ALTER 'AMF***' MF=NEW
2–70 User Guide

This statement creates the next AMF data set name in sequence. For instance,
if the last DSN on the current set was AMF008, CA Dynam/T would create DSN
AMF009 and place it in the Catalog as file one of a new AMF set. The next time
the job creating the AMF DSN is run, AMF009 is used. You can then delete
DSNs AMF002 through AMF008. This frees space in the Catalog. The base
DSN, AMF***, must remain in the Catalog; it contains pointers to the data set
names currently in use.
Scratching More Than the Last AMF DSN
If you manually scratch a tape other than the last DSN of an AMF set, you
must tell CA Dynam/T which DSN to use next for output.
For instance, suppose data sets AMF001 through AMF008 had been created,
but data sets AMF005 through AMF008 contained bad data and had to be
recreated, then do the following:
1. Scratch DSN AMF005 using DYNCAT DELETE. This would scratch AMF005
through AMF008 because CA Dynam/T always scratches forward on
chained multifile data sets:
DELETE 'AMF005' ALL
2. Issue the following DYNCAT update statement:
ALTER 'AMF***' MF=005
This update statement tells CA Dynam/T to use DSN AMF005 for outputting
the next file of this AMF set. The same procedure must be followed when
members of the current AMF set are deleted.
Inputting AMF Data Sets
Several methods are available to call for the desired input AMF data set. The
following examples assume that AMF001 through AMF014 have all been
created on the same tape. AMF014 is the latest (last) file. Each of the
following will result in DSN AMF007 being the data set requested (provided the
file is being opened for input):
// TLBL INFILE,'AMF***',,,,,8 (version number field)

// TLBL INFILE,'AMF***',,,,7 (file sequence number field)
// TLBL INFILE,'AMF***.(-7)' (relative generation)
// TLBL INFILE,'AMF007' (real DSN)
// TLBL INFILE,'AMF***',,,,7,2 (file sequence overriding version)
Subsequent files of AMF sets are also subsequent generations; thus, cyclic
control of these data sets does not apply. You can set retention dates and use
the MF=NEW option to divide the AMF data sets into easily manageable groups
of tapes.

Forced Standard Label Support
Note: Partition ID substitution, CPU ID substitution, or both, are not allowed

for AMF data sets.
Renaming and Resetting AMF Data Sets
The DYNCAT RENAME command enables you to rename an entire AMF group
and begin the AMF group processing over again with file one and 001 as the
name.
Example:
Suppose that three versions of the AMF group PAY*** were created in
December, that it is desirable to save the December versions, and that
processing begins again in January.
Existing AMF versions:
PAY001 (file 1)
PAY002 (file 2)
PAY003 (file 3)
If you issue the following DYNCAT RENAME statement,
RENAME OLDNAME='PAY***' MF=RESET NEWNAME='PAYDEC***'
the new multifile data sets will be:
PAYDEC001 (file 1)
PAYDEC002 (file 2)
PAYDEC003 (file 3)
The versions created in December are retained. The next time the AMF name
'PAY***' is used to create a file, the data set will be created as file one of the
scratch tape, using the name PAY001. The PAYDECnnn data sets are changed
from AMF status to normal multifile status, which prevents anyone from
accidentally adding another file to the tape after PAYDEC003. You can apply
normal retention to the new data set names.
Forced Standard Label Support

CA Dynam/T modifies your DTF to specify standard labels if the following is
true:
An OPEN occurs for a DTF defined as unlabeled.
A TLBL exists with the same dtfname.
The data set name appears in the Catalog.
2–72 User Guide

Support for Read Backwards
The label processing area is always automatically available without your

intervention. Forced label tape support is controlled by the FLT option of the
DYNAM/T option record, and cannot be used for nonstandard or user label
processing. For more information, see the Programming Guide.
Note that RPG unlabeled tapes defined using the M operand are really
nonstandard labeled tapes and cannot be used with the FLT option.
Support for Read Backwards

If the DTF being opened has Read Backwards specified, the tape will be
positioned to the end of file before passing control to IBM. Only single volume
data sets are supported. Multifile single volume data sets are also supported.
ASCII Tape Support

If ASCII = YES is specified in the DTF, the VOL1/HDR1 will be rewritten by
DYNAM/T in ASCII before passing control to IBM. If an ASCII scratch tape is
used for output for an EBCDIC file, the VOL1/HDR1 will be rewritten by
DYNAM/T in EBCDIC.
ASCII input tapes will now be AVRed by DYNAM/T.
Using Other Software with CA Dynam/T
Sort and Utility Package Support
You may be using a utility package that provides tape/disk independence by

performing pre-OPEN checking of logical unit assignments to determine the
device type to be used. However, to fully implement CA Dynam/T's AVR
facility, you must do any one of the following:
Eliminate pre-OPEN logical unit checking using CA SORT, r6.1 or greater.
Replace permanent or temporary tape assignments used by these

packages with a special CA Dynam/T facility called TDYNASN.

TDYNASN allows AVR to function while fulfilling the pre-OPEN requirements of

these packages. You must be familiar with TDYNASN before attempting to use
AVR for tape files processed by the following packages:
Sorts
Tape Utilities
DUMP/RESTORE Packages
Source Library Maintenance Packages
Report Writer Packages
Using the TDYNASN OPEN/CLOSE Function
Tape files which are not opened and closed using tape DTFs can nevertheless
be placed under CA Dynam/T control through use of the TDYNASN
OPEN/CLOSE function. Do not use TDYNASN DUMMY assignments for this type
of file or for any file that uses physical IOCS without performing a logical
OPEN. For more information about TDYNASN, see the chapter "Supporting
Tape File Management."
Processing FORTRAN Tape Files
Use DTFCP, a special device-independent DTF, to process FORTRAN tape files.

You must provide a TLBL for the tape file to be controlled to activate standard
label support for FORTRAN tape files. The FORTRAN file dtfname is IJSYSnn,
where nn is the last two digits of the logical unit that accesses the files. For
example, this is the TLBL for the file accessed using SYS004:
// TLBL IJSYS04,'DSN'
FORTRAN Support Exceptions
CA Dynam/T does not support the REWIND and UNLOAD tape control options
because of the FORTRAN DTF type. Also, you cannot release work data sets at
CLOSE or use FORTRAN tape files that violate VSE LIOCS conventions for tape
files.
CA Dynam/T does not support multifile FORTRAN data sets.
2–74 User Guide

LIBR Backups and Restores
With TAPEL= Parameter
VSE Version 3 and higher support standard label tapes for backup and restore.
With RESTORE=ONLINE, no special CA Dynam processing is required. With
RESTORE=STANDALONE, LIBR performs pre-OPEN processing. The following is
an example of the necessary job control:
// JOB BACKUP STANDALONE

// TLBL BACKUP,'LIBR.BACKUP',0,,,,,08
// EXEC TDYNASN,SIZE=128K
ASSGN BACKUP,SYS006,OUTPUT
/*
// ASSGN SYS010,SYS006 */ SAVE TAPE ADDRESS FOR MTC RUN */
// EXEC LIBR
BACKUP LIB=IJSYSRS TAPE=SYS006 RESTORE=STANDALONE TAPEL=BACKUP
/*
// MTC RUN,SYS010
/&
Note: The Dynam/T HOLD option must be specified, because LIBR will access
the tape drive after close. If the tape drive was dynamically attached by either
the DYNT/VM or 3494 interface, it will not be automatically detached at close
because of the HOLD option. After the LIBR job completes, run a TDYNASN
DETACH job to detach any dynamically attached tape drive.
The following is for VSE/ESA Version 2 users only.
When running VSE/ESA Version 2 (VSE/ESA), output tapes are created in a

nonstandard organization by the LIBR program's BACKUP, RESTORE
commands, or both. The structure of these tapes is as follows:
STANDALONE PHASES
IF PRESENT
HEADER LIBRARY MEMBER
IF PRESENT
******** TAPE MARK #1 *********
LIBR BFID RECORD
HISTORY FILE IF PRESENT
******** TAPE MARK #2 *********
LIBR FHDR RECORD -
LIBRARY DATA RECORDS multiple occurrences if more than
LIBR EOBF RECORDS one (sub)library is processed
LIBR DRID RECORDS -
******** TAPE MARK #3 *********
******** TAPE MARK #4 *********
LIBR EOB RECORD
******** TAPE MARK #5 *********
******** TAPE MARK #6 *********

CA Dynam/T offers various methods of dealing with LIBR's nonstandard tape

structure. It provides support for LIBR's BACKUP, RESTORE, or both, using the
following files:
CA Dynam/T-controlled files, with either
− The NOLABEL option, or
− Forced label tape support
Non-CA Dynam/T-controlled files
Using CA Dynam/T-controlled Files
With the NOLABEL CA Dynam/T supports most variations of LIBR backup tapes through use of
Option the NOLABEL option in conjunction with TDYNASN job control statements.
Multifile data sets under CA Dynam/T's control, however, are not supported.
We recommend that before creating CA Dynam/T-controlled data sets used for

LIBR backups, you include TAPEOPT=NOLABEL in their catalog definitions. This
lets you use TDYNASN, as shown in the JCL examples, to perform the
following:
Multiple (sub)library backup/restores to CA Dynam/T-controlled data sets
RESTORE=STANDALONE backups to CA Dynam/T-controlled data sets
The example job control shows that TDYNASN JCL statements have the
following properties:
Include a TDYNASN preopen DUMMY assignment
Use the OPEN file name SYSxxx,mode,U TDYNASN function. It is necessary

because standalone phases (if specified) will be written to tape by LIBR
before any OPEN, or preopen, logical unit assignment checking is done.
Specify option U on the OPEN statement to identify the unlabeled DTF to

TDYNASN
Be sure to reinitialize the tape volume the next time it is used for output when
using TAPEOPT=NOLABEL; the VOL1 label has been overwritten by LIBR.
Exceptions The information provided so far applies to both online and standalone LIBR
backups, with the following exceptions:
When specifying RESTORE=STANDALONE with a CA Dynam/T-controlled tape,

you must use the TDYNASN OPEN function, as the VOL1 label is overwritten
with the standalone phases prior to open by LIBR. The TDYNASN ASSGN
function only allows for preopen ASSGN checking, not actual I/O. This means
that you must use a different DTFNAME for TDYNASN than you do for LIBR,
thereby preventing a double OPEN and any ensuing problems.
2–76 User Guide

Consequently, when the volume is opened by LIBR (after having already been
AVR'd and opened by TDYNASN), it is not treated as a controlled data set, and
thus EOV would be uncontrolled, and second and subsequent volumes would
not be associated with data sets in the CA Dynam Catalog. Therefore, make
note of the following:
Multivolume files are not supported if RESTORE=STANDALONE is specified

for backup
The CLOSE file name,SYSxxx,mode is required for Catalog update at close

time when RESTORE=STANDALONE is specified
There can be no intervening labels between the TDYNASN OPEN and the
TDYNASN CLOSE steps
Message number CADT039W ** OPENED OFF LD PT ** is displayed for

each (sub)library accessed
The following pages show various examples of the job control used to back up
and restore catalog-controlled files.
An example of the job control required to back up LIBR (sub)libraries to a

CA Dynam/T-controlled data set (including support for multivolume files) using
RESTORE=ONLINE is shown next.
// JOB BACKUP MULTIPLE

// TLBL UOUT,'DATASET.NAME,H' /* CATALOGED - TAPEOPT=NOLABEL */
// EXEC PGM=TDYNASN
// ASSGN SYSXXX,DUMMY /* HANDLE PREOPEN ASSGN CHECK */
/*
// EXEC PGM=LIBR
BACKUP LIB=XXXXXXX /* OBJECTS TO BACKUP */
XXXXXXX /* - LIB(S) OR SUBLIB(S) */
id='ID-FOR-BFID-RECD' - /* OPTIONAL IDENTIFIER */
HEADER=LIB.SUB.MEMBER.TYPE -/* OPTIONAL MEMBER (LABEL) */
INCLUDE=HISTORYFILE - /* OPTIONAL */
TAPE=SYSXXX -
RESTORE=ONLINE - /* STANDALONE NEEDS "OPEN" */
/*
// MTC CCC,SYSXXX /* POSITION LAST TAPE VOLUME */
/&

The following example shows the job control required to RESTORE an online
backup from a CA Dynam/T-controlled data set created by the job above:
// JOB RESTORE LIBR BACKUP CREATED ABOVE

// TLBL UIN,'DATASET.NAME,H' /* CAT CONTROL TAPEOPT=NOLABEL */
// EXEC PGM=TDYNASN
// ASSGN SYSXXX,DUMMY /* ALLOW PREOPEN ASSGN CHECK */
/*
// EXEC PGM=LIBR
RESTORE LIB=XXXXXXX TAPE=SYSXXX R=Y
/*
/&
This is an example of the job control required to BACKUP LIBR objects to a one
volume CA Dynam/T-controlled data set using RESTORE=STANDALONE.
// JOB BACKUP
// TLBL DUMMY,'DATASET.NAME,H' /* CAT CONTROL TAPEOPT=NOLABEL */
// EXEC PGM=TDYNASN
OPEN DUMMY,SYSXXX,OUTPUT,U /* AVR AND OPEN UNLABELLED */
/* /* SCRATCH TAPE */
// EXEC PGM=LIBR
BACKUP LIB=XXXXXXX - /* MUST BE SYSTEM LIBRARY(S) */
RESTORE=STANDALONE - /* ALL VALID LIBR BACKUP */
TAPE=SYSXXX - /* OPTIONS ARE SUPPORTED */
/*
// EXEC PGM=TDYNASN
CLOSE DUMMY,SYSXXX,OUTPUT /* UPDATE CATALOG, NO LABELS */
/* /* SINCE LAST TDYNASN */
// MTC CCC,SYSXXX /* POSITION TAPE */
/&
The following example shows the job control required for an online RESTORE
of a member from a CA Dynam/T-controlled data set created by the job above.

// TLBL DUMMY,'DATASET.NAME,H' /* CAT CONTROL TAPEOPT=NOLABEL */
// EXEC PGM=TDYNASN
OPEN DUMMY,SYSXXX,INPUT,U /* MOUNT AND OPEN UNLABELLED */
/* /* INPUT TAPE
// MTC FSF,SYSXXX,1 /* SPACE PAST STANDALONE PHASES */
// EXEC PGM=LIBR
ACCESS SUBLIBRARY=LIB.SUB
RESTORE LIB.SUB.MEMBER.TYPE TAPE=SYSXXX R=Y
/*
// MTC CCC,SYSXXX /* POSITION TAPE VOLUME */
/&
2–78 User Guide

Note that the data set created by the above job stream must be entirely
contained on one tape volume. Multivolume data sets under CA Dynam/T's
control are not supported when using the RESTORE=STANDALONE option.
With Forced Label You may choose to use Forced Label Tape support, instead of specifying
Tape Support TAPEOPT=NOLABEL in the catalog definitions of LIBR data sets, with LIBR
files.
It lets you BACKUP and RESTORE a single (sub)library from a standard labeled
CA Dynam/T-controlled data set. For example:
// JOB BACKUP VERSION 2 LIBRARY TO CA Dynam/T CONTROLLED TAPE

// TLBL UOUT,'DATASET.NAME,H' /* CAT CONTROLLED WITH HOLD */
// EXEC PGM=TDYNASN /* ALLOW PREOPEN CHECKING */
// ASSGN SYSXXX,DUMMY
/*
// EXEC PGM=LIBR
BACKUP SUBLIB=XXX.XXXX TAPE=SYSXXX R=O /* SINGLE OBJECT ONLY */
/*
/&
Note that when producing a CA Dynam/T-controlled LIBR backup tape, as in

the previous example, the following conditions apply:
Tape positioning through TLBL or catalog option will cause errors, because
positioning takes place at close, before the LIBR EOB record/file has been
written.
Trailer labels are written at close, before the LIBR EOB record. This does
not interfere with the RESTORE of the backed up library but may affect
other LIBR functions.
Multiple (sub)libraries cannot be written to one data set, because the DTF
in use has been modified to specify standard labels using Forced Label
Tape support. This means that trailer labels are written at CLOSE, which
occurs once for each (sub)library backed up.
LIBR backups of multiple (sub)libraries using Forced Label Tape support

will complete successfully, but the resulting backups cannot be restored!

Controlling Single and Multi-Volume POWER Offload Tapes
The following example shows the job control required to RESTORE a single
(sub)library backed up to a CA Dynam/T-controlled data set as above:

// TLBL UIN,'DATASET.NAME,H' /* CAT CONTROL WITH HOLD */
// EXEC PGM=TDYNASN
// ASSGN SYSXXX,DUMMY /* ALLOW PREOPEN CHECKING */
/*
// EXEC PGM=LIBR
RESTORE SUBLIB=XXX.XXX TAPE=SYSXXX R=Y /* SINGLE (SUB)LIB ONLY */
/*
// MTC CCC,SYSXXX /* TAPE POSITIONING */
/&
Using Non-CA Dynam/T-Controlled Files
Any LIBR tape can be produced or accessed without standard labels on

non-CA Dynam/T-controlled tapes. Release of the logical unit used by LIBR at
close must be avoided and the assignment carried over to the second and
subsequent volume (if applicable) by use of the JCL assignment.

To use CA Dynam/T to control a POWER offload tape, a label for the DTF name
specified must be present either in system standard labels or partition labels
(standard or user) for the POWER partition. IBM issues an open for the tape if
TLBL= is specified on the POFFLOAD command. Additionally, the Z option must
be specified on the TLBL because different IBM tasks issue the open and close
for the tape.
The POFFLOAD command requires that a CUU be specified. However, to get

around pre-assigning a tape drive for use by the POFFLOAD command, use the
CA Dynam/T System option PWRCUU to define a dummy CUU to be specified
on the POFFLOAD command. This definition can be done either batch or online.
The CUU specified in the PWRCUU parameter should be a deviced up non-
existent device.
At OPEN time, CA Dynam/T releases the assignment and AVRs an appropriate

tape if the PWRCUU was specified on the POFFLOAD command. Note that IBM
can issue an I/O after close, so if there is no output for the POFFLOAD
command to process, an I/O error can be issued. You can use the H TLBL
option to prevent this situation; however the assignment is not released, and
for CA Dynam/T VM users, the drive is not detached.
2–80 User Guide

To control single and multi-volume POWER Offload tapes with CA Dynam/T, do

the following:
1. Define a tape device in the IPL procedure that does NOT exist.
For example:
ADD CAA,3480
2. Define that device to CA Dynam/T by using CACCDBU0 or on CUI screen

CAYD1214.
For example:
// EXEC CACCDBU0
ALT DTOPTIONS CPU(*) PWRCUU(CAA) REFRESH(YES)
/*
3. Include the following TLBL in either standard labels or in partition standard

labels in the POWER partition:
// TLBL xxxx,'dsn.name,Z,DL'
where:
Xxxx is the DTFNAME specified on the TLBL= parameter of the

POFFLOAD command.
dsn.name is the CA Dynam/T data set name.
,Z allows CA Dynam/T to detect POWER closing the POFFLOAD

tapes.
,DL Deletes the label for the file at the close of the file.
4. To perform the POWER OFFLOAD, issue one of the following commands:

O cmd,Queue,CAA,,*,TLBL=xxxx
or
O cmd,XMT,CAA,TLBL=xxxx
where:
Cmd is one of the following POFFLOAD commands: BACKUP,

PICKUP, or SAVE.
CAA is the tape address that was added to the IPL procedure and
defined to CA Dynam/T with the PWRCUU parameter.
Xxxx is the DTFNAME specified in the Standard or Partition label

associated with this POFFLOAD command.
Queue is the queue: LST, PUN, RDR, or XMT.
* is the output class.

Controlling POWER Job Accounting Tapes
Controlling POWER Job Accounting Tapes

In order for CA Dynam/T to control POWER job accounting tapes, the Z option
must be specified on the TLBL in the POWER partition, the partition standard
label or the standard label, as follows:
// TLBL dtfname,'dsn,Z'
To create the tape, issue the following POWER PACCOUNT command with the
dtfname as specified in the TLBL:
{PACCOUNT|J } tapeaddr,,dtfname
Note: Do not specify a density, it will be automatically assigned by the

CA Dynam catalog.
Enforcing Volume Serial Number Standards

CA Dynam/T enables you to automatically enforce standards for volume serial
numbers. You can require that all volume serial numbers introduced into the
CA Dynam Catalog are numeric or fall within a certain range by using the
VOLSER parameter of the DYNAM/T option record.
If a nonstandard serial number is introduced into the CA Dynam Catalog, it

causes one of the following:
An error, if a DYNCAT command is being used
The operator response to be ignored if the operator is initializing a tape

using the inline initialization facility
For more information about coding and using the DYNAM/T option record, see
Specifying the SET Command

The SET command lets you control various options of the CA Dynam/T system.
It can be entered either through the system operator's console or along with
other JCL in an input job stream. The command affects only the partition in
which it is entered.
2–82 User Guide

SET Command Syntax Rules
Syntax rules for the SET command are:
Enter the SET command in position 1, followed by at least one space.
All operands are optional.
You can issue an individual SET command for each operand defined or a
single SET command specifying all of the operands.
If you specify a single SET command with multiple options, separate the
operands by a comma (no blank spaces).
Summary of SET Command Syntax
The syntax for the SET command is as follows:
[ CPCMD='command' ]
SET [ DYNAMT= {OFF|ON } ]
[ $JOBEXIT= {AFTER|BEFORE } ]
[ LABELMSG= {ON|OFF } ]
The following list describes the SET command operands more fully. They are
presented alphabetically.
CPCMD= Passes a command to CP when running under VM.
DYNAMT= Indicates whether CA Dynam/T is to process in the partition in which the SET
command is issued.
ON Enables CA Dynam/T to process in that partition.
OFF Disables CA Dynam/T processing in that partition.
The effect of this command is permanent in static partitions until the next SET
DYNAMT command is issued in the same partition or until the VSE machine is
IPLed.
In dynamic partitions, CA Dynam/T intercepts can be disabled only until the

end of the POWER job.
$JOBEXIT= Specifies whether the standard job exit ($JOBEXIT) will be

processed BEFORE or AFTER the CA Dynam common Job Exit.
If you have specified processing in the standard $JOBEXIT which will effect
CA Dynam processing, (i.e. CA Dynam option substitution for TLBL|DLBLs),
code the SET $JOBEXIT=BEFORE command.
The default is AFTER.

Tape Drives
LABELMSG= Determines whether the CADC950I message will appear for TLBL statements
containing CA Dynam option codes. This message displays the original file ID
information before processing options are removed by the CA Dynam common
Job Exit.
The CADC950I message will appear on SYSLST if '// OPTION LOG' is coded, on
SYSLOG if LOG is coded and on both SYSLST and SYSLOG if both options are
coded.
Note: The SET LABELMSG command affects all partitions.
Tape Drives
Pooling Tape Drives (DTPOOL Option Record)
The DTPOOL option record provides tape drive pooling support for CA
Dynam/T. The available tape drives are defined into pools for the installation
as a whole, by both the CPU ID and the partition, or by either the CPU ID or
the partition. When CA Dynam/T AVR is attempting to locate a tape, only the
drives in the pool are searched (in the desired order). If there is no DTPOOL
option record, AVR searches all available drives in the order in which they
were defined in the PUB table by ADD statements at IPL. You can thus exclude
certain tape units from AVR, such as dummy tape units or tape units with
limited speed or mode capability.
Tape drive pooling also facilitates the mounting of tapes because you can
change the sequence in which tapes are searched for. For instance, you can
search the drives nearest the tape library first.
Note that DTPOOL only affects CA Dynam/T during AVR scans; you can select
any drive defined in the PUB table in a cuu response to the MOUNT message.
For more information, see the DTPOOL option record in the Programming
Guide.
Locking Tape Drives (DTLOCK Option Record)
A multi-CPU installation that is sharing tape drives can use tape drive locking
(DTLOCK) if both of the following conditions are satisfied:
AVRLCK(YES) is specified in the DYNAM/T option record.
The DTLOCK option record is coded to define a common LOCK name which
can be referenced by all CPUs for a specific tape unit.
2–84 User Guide

Using the Console Alarm Facility
IBM does not provide a standard facility for protection of shared tape drives in
a multiple system environment. With DTLOCK, an external LOCK option record
is issued whenever CA Dynam/T is ready to access a tape drive. This assures
that the tape drive is not in use by CA Dynam/T from another CPU. If it is in
use, the drive is bypassed during AVR or considered NOT AVAILABLE if the
operator attempts to override AVR. The LOCK is released when CA Dynam/T
decides not to use the drive or processing for the file is completed.
The standard VSE LOCK option record (available on VSE r2 and above) is used,
so abnormal termination of any kind results in the LOCK being cleared by end-
of-job routines automatically. In addition, the AR command interface provides
for operator-controlled locking or unlocking of the tape drive.
Using the Console Alarm Facility

The console alarm rings whenever a message requiring operator action or
response is issued (-A or -D messages) if you specify ALARM(YES) in the
DYNAM/T option record. This is especially useful if the console is unattended
for periods of time.

Chapter 3: Supporting Tape File
Management
Tape File Management Utilities

The series of support and utility programs provided with CA Dynam/T permit a
wide range of functions. For instance, you can make dummy pre-assignments
to allow utility programs to take advantage of AVR. You can even convert from
other tape management systems to CA Dynam/T. The functions are discussed
later in this text.
Tape Assignment Program—TDYNASN
The TDYNASN program is designed to perform the following functions:
Open and close files when this is not accomplished by the programs that
read and write them.
Establish ASSGNs for tape drives before executing the program that opens
the file.
Issue ASSGNs to dummy devices so that AVR functions can be performed.
Equate one programmer logical unit to another.
Note: It is not necessary to use TDYNASN for CA Sort r6.1 or greater if CA

Sort has been properly generated.
Chapter 3: Supporting Tape File Management 3–1

Using the ASSGN Statement
The // ASSGN statement has two formats:
[//] ASSGN SYSnnn[,DUMMY]

or
// ASSGN SYSxxx,SYSyyy
Format One The first format is shown below.
[//] ASSGN SYS001[,DUMMY]
This format makes the specified logical unit assignment to a dummy device.
The logical unit assignment must be correctly made before opening the file,
because some programs, such as CA SORT, can use either tape or disk
devices. A dummy ASSGN satisfies this requirement, allowing AVR to be used
at OPEN time. The default dummy devices are 7F0 through 7FF, but can be
altered by changing the DYNAM/T option record. TDYNASN uses as many of
these devices as are necessary. The dummy devices are in device-down
(DVCDN) status and ownership bits are not set on. This prevents job control
from ever trying to use such a device.
Each dummy ASSGN statement generates an assignment to a different dummy

device unless an UPSI 01 statement is present. In this case, all ASSGNs are
made to the same device.
You can normally use UPSI 01 to assign all LUBS to the same dummy PUB.
However, this is not permitted with the MERGE and TP functions of CA SORT.
They verify that all input files are assigned to different devices.
Never use the // ASSGN SYSxxx,DUMMY format of TDYNASN for any program
that does I/O on a tape file without opening it (such as DITTO).
Examples:
Assume DUMMY(7F0,7FF) set up in DYNAM/T option record
// EXEC TDYNASN
// ASSGN SYS001,DUMMY (would be assigned to 7F0)
/*
// UPSI 01 (make all assigns to same dummy device)
// EXEC TDYNASN
/*
3–2 User Guide

Normally, all ASSGNs can be made to the same dummy device by using UPSI
01. However, when performing the CA SORT MERGE function, you must use
different dummy devices to satisfy all of the checks of the MERGE function.
Note: Specifying S:nnn on the TLBL causes an assignment to a dummy device

at JCL time. This method would avoid the need, in some cases, of executing
TDYNASN.
Format Two The second format of the ASSGN statement assigns the first SYS number to
the same device as the second SYS number.
// ASSGN SYS004,SYS005
Example:
This JCL assigns SYS004 to the same device as SYS005.
// EXEC TDYNASN
/*
Issuing the ASSGN Command
This command locates the proper tape and makes the logical unit assignment:
ASSGN filename,SYSxxx{,INPUT|OUTPUT}[,S|U]
You must include a TLBL for the file name before executing TDYNASN.
INPUT locates the data set specified in the TLBL statement and makes the logical unit
assignment to that drive.
OUTPUT locates a scratch tape and makes the assignment to that drive.
S creates a DTF with standard labels for input or output. S is the default.
U creates an unlabeled DTF for input or output.
Example:
// TLBL SORTOUT,'DSN'
// TLBL SORTIN1,'DSN'
// EXEC TDYNASN
ASSGN SORTOUT,SYS001,OUTPUT
ASSGN SORTIN1,SYS002,INPUT
/*

Note: The ASSGN FILENAME,SYSNNN,OUTPUT function:
Should be avoided in a multiple-CPU environment sharing tape drives

because it causes cross-AVR
Results in a CADT010D message unless the DYNAM/T option record

includes REUSE(YES) support
SORTIN Files
The case of Filename SORTINx is special. TDYNASN finds the specified data set
for the first SORTINx ASSGN encountered. Then, an ASSGN for SORTIN2-9 is
equated to the first SORTIN assignment. Any time SORTIN1 is encountered, it
is assigned to the tape drive on which the specified data set is found. UPSI 1
overrides this and causes actual assignments to be made for each SORTIN file.
The following options provide a variety of methods for handling SORTIN files:
Option One Using dummy ASSGNs to permit AVR when SORT needs each input file.
Examples of this option are shown under Format One of "Using The ASSGN
Statement."
Option Two Using one tape drive for all SORTIN files, locating the drive with AVR. For
example, in this case, an ASSGN is made to the same tape drive for each
SORTIN file.
// TLBL SORTIN1,'DSN A',,,,,,8

// TLBL SORTIN2,'DSN B',,,,,,8
// TLBL SORTIN3,'DSN C',,,,,,8
// TLBL SORTOUT,'DSN D'
// EXEC TDYNASN
ASSGN SORTOUT,SYS001,OUTPUT
/*
Option Three Alternating SORTIN files between two tape drives, locating the first two input
files with AVR, as shown in the example below.
The sequence of the ASSGN statements is critical; without UPSI 1, SORTIN2-9

is equated to the first SORTIN encountered. An ASSGN for SORTIN1 is always
made to the tape drive on which the correct data set is found. Any ASSGNs
following SORTIN1 are equated to the same device unless UPSI 1 overrides
them.
3–4 User Guide

// TLBL SORTIN1,'DSN A',,,,,,8

// TLBL SORTIN2,'DSN B',,,,,,8
// TLBL SORTIN3,'DSN C'
// TLBL SORTIN4,'DSN D'
// TLBL SORTOUT,'DSN E'
// EXEC TDYNASN
ASSGN SORTIN4,SYS005,INPUT (Equated to SYS003)
ASSGN SORTIN3,SYS004,INPUT (Equated to SYS002)
/*
Option Four Locating all input files prior to sorting. This option would have to be used for a
merge where all SORTIN tapes have to be opened at the same time, for
example,
// TLBL SORTIN1,'DSN A'

// TLBL SORTIN2,'DSN B'
// TLBL SORTIN3,'DSN C'
// TLBL SORTIN4,'DSN D'
// TLBL SORTOUT,'DSN E'
// UPSI 1
// EXEC TDYNASN
/*
OPEN, CLOSE, DETACH, and VTSTOP Functions
TDYNASN performs the OPEN and CLOSE functions so that CA Dynam/T can
control tape files not opened and closed with tape DTFs. Use these functions to
control SYSIPT, SYSLST, SYSPCH, and 1400 Emulator tapes.
The OPEN and CLOSE commands have the same format as the ASSGN
command. They are effective for single volume files only. Volume switching is
not supported.
OPEN Command The OPEN command does the folllowing:
Performs an actual open for the tape file
Invokes AVR to locate a valid scratch
Makes the assignment
Writes the header records on the tape
Leaves the tape positioned following the header records and tape mark

The tape should not be subsequently rewound by the user program.
TDYNASN normally reads input from SYSIPT. When the OPEN function is used
for SYSIPT, TDYNASN must be directed to read its input from SYSRDR. The
use of UPSI 001 reassigns SYSIPT and causes the TDYNASN OPEN function to
read its input from SYSRDR instead.
CLOSE Command The CLOSE command causes the CA Dynam Catalog to be updated but does
not actually close the file; it does not write an EOF1 record and tape mark.
This can be done with an MTC job control command; the TDYNASN CLOSE
function does not release the assignment.
Note: The CLOSE command has to access the original label (TLBL) that was
opened, generally by the OPEN command. If this is not done, the CLOSE will
be unsuccessful.
Example:
// JOB CREATE SYSPCH TAPE

// TLBL FILEA,'DSN,P'
// EXEC TDYNASN
OPEN FILEA,SYSPCH,OUTPUT
/*
// EXEC ASSEMBLY
ASSEMBLY PROGRAM INPUT
/*
// EXEC TDYNASN
CLOSE FILEA,SYSPCH,OUTPUT
/*
// MTC REW,SYSPCH (The close only Catalogs the data set.)
/&
// JOB READ SYSPCH TAPE
// TLBL FILEA,'DSN'
// UPSI 001 READ FROM SYSRDR
// EXEC TDYNASN
OPEN FILEA,SYSIPT,INPUT
/*
// EXEC LIBR
/*
// MTC RUN,SYSIPT
/&
This example uses TDYNASN to create a SYSPCH tape, then reads it as

SYSIPT.
Note: Dynamic LUB allocation must be bypassed for the SYSPCH tape.
3–6 User Guide

DETACH Command Issue the DETACH command only if the DYNVM Extension interface is active.
This command passes a request to DYNVM to detach the indicated tape drive
from the VSE pool and assign it to the VM free tape pool. The format is:
DETACH filename,SYSnnn
Example:
// JOB DETACH SYS010 TAPE

// TLBL FILEA,'DSN'
// EXEC TDYNASN
DETACH FILEA,SYS010
/*
/&
VTSTOP Command Issue the VTSTOP command if the HOLD option was used when creating a
VTAPE using the Dynam/T automatic VTAPE interface. The VTSTOP command
will release the assignment to the specified logical unit and then issue the
appropriate VTAPE STOP command. The format is:
VTSTOP SYSnnn
Example:
// JOB VTAPE STOP SYS010

// EXEC TDYNASN
VTSTOP SYS010
/*
/&
TDYNASN UPSI Settings
UPSI 1 Do not equate SORTIN2-9 (indicates MERGE)
UPSI 01 Assign all LUBS to same DUMMY PUB
UPSI 001 Read input from SYSRDR
UPSI 0001 Cause TDYNASN to indicate 80-byte records when assigning/opening SYSIPT
tapes.
User Labels
User labels required by a program must always precede TDYNASN if any labels
are also required by a TDYNASN function. Otherwise, when encountering label
information after TDYNASN, job control writes over any labels encountered
prior to TDYNASN.

TDYNASN prints control statements on SYSLST only if // OPTION LOG is in

effect.
Tape Copy Utility—TDYNCOPY
TDYNCOPY is a tape-to-tape copy program. The tapes can be either labeled or

unlabeled. TDYNCOPY can be used to do the following:
Copy single or multiple files, multifile volumes, and multivolume files
Reblock fixed length files
Output one file on the same volume, from multiple input files on separate
volumes
Output multiple files on separate volumes, from multiple input files on the
same volume
Output multiple files on the same volume, from multiple input files on
separate volumes
TDYNCOPY uses the Filename UIN for input files on SYS004 and the Filename
UOUT for output files on SYS005. If SYS005 is assigned to IGNORE, processing
for the output file is bypassed.
Storage Requirements
TDYNCOPY no longer requires execution with a SIZE=128K parameter.

TDYNCOPY will allocate storage for I/O buffers from partition GETVIS storage.
A 64 KB buffer will be needed to accommodate the largest physical block that
can be written to a tape. The file can copy blocks up to 65535 bytes, because
it is copied with physical I/O.
Determining Block and Record Size
TDYNCOPY determines the block and record size inline. A second I/O area will
be allocated from the partition GETVIS to do the reblocking. The size of the
second I/O area will be the NEW blocksize. Valid output blocksize is up to
65535 bytes.
TDYNCOPY conditionally supports multiple input files of different formats (that

is, fixed, variable, and so on) to multiple output files. This support is activated
by using MODON 10. Care must be taken when using this feature, especially
when copying multiple input files to stacked output, (UPSI combination of
1xxx1xxx).
3–8 User Guide

With the advent of HDR2 labels being maintained, the HDR2 could contain
information inconsistent with the actual tape contents. Without MODON 10
activated (OFF), TDYNCOPY issues message CADT572E and cancels. With
MODON 10 activated (ON), CADT572W is issued as a warning only message.
Optional Functions
The optional functions are indicated by // UPSI statements. You can use any
combination of UPSI settings, except for // UPSI x1xx1xxx (48).
// UPSI Setting Meaning
UPSI 1xxxxxxx Multiple input files.
This bit prevents the tape from being rewound at OPEN or CLOSE (unless the
TLBL option is present to force a REWIND or UNLOAD). Therefore, either
multiple single-file volumes or multifile volumes can be processed. The last
input file is unloaded at CLOSE, however, unless the TLBL option overrides it.
UPSI x1xxxxxx Multifile volume output.
This bit causes the output files to be written to the same volume (or multiple
volumes, if the files are controlled by CA Dynam/T).
UPSI xx1xxxxx Unlabeled input.
Use this setting if the input is an unlabeled tape.
UPSI xxx1xxxx Unlabeled output.
Use this setting if the output is an unlabeled tape.
UPSI xxxx1xxx Stack output (only one output file).
The stack bit concatenates all input files as one output file. This is similar to a
merge function. The absence of this bit causes each input file to be copied as a
separate output file.
UPSI xxxxx1xx Reblock file.
This function causes TDYNCOPY to request the logical record size and new
blocking factor from the console. If either the stacking or reblocking function is
being used, all checkpoint records from the input files are bypassed and a
console message is issued. Only one set of reblocking parameters is accepted.

UPSI xxxxxx1x Accept control statements from SYSIPT.
This setting indicates that TDYNCOPY is to accept control statements from

SYSIPT, rather than from the operator console. You can use this UPSI bit in
conjunction with any of the others to do the following:
Run job streams which use TDYNCOPY for copying multiple files, either
both stacking and reblocking without operator intervention, or stacking or
reblocking without operator intervention.
Take user control of the rewind and unload options at CLOSE.
UPSI xxxxxxx1 Unload each input file.
This setting is necessary only when the input files are not CA
Dynam/T-controlled data sets. In this case, use options U or 2. Be sure to use
this setting when the multiple input files indication is set and the uncontrolled
input files are not on the same volume.
If TDYNCOPY is executed with UPSI xxxxxx1x in effect, the following optional

control statements are accepted from SYSIPT:
FILES=nnnn The user-specified number of files to be copied (in place of the operator
response to the CADT501D message).
Valid only if UPSI 80 (MULTIPLE INPUT FILES) is on. It must appear on the
first control statement.
LRECL=nnnn, NRECS=nnn
The values specified by the user indicate to TDYNCOPY the logical record
length and desired number of records per block (in place of the operator
responses to the CADT503D and CADT504D messages). LRECL and NRECS
must immediately follow the FILES= parameters and can only be specified
once.
Valid only if UPSI 04 (reblock) is on.
UIN=REW|RUN|NOR
UOUT=REW|RUN|NOR
They indicate the desired disposition of the tape when the indicated file is
closed. If not specified, the default is to unload the tape.
UIN and UOUT apply separately to each file. If the user has specified UPSI 02
in conjunction with UPSI 80 and the FILES= operand, every time a new file is
opened, another input statement will be accepted to process options for the
file. This means that UIN and UOUT parameters for separate files must appear
on separate commands.
UIN and UOUT are valid with any other UPSI settings, as long as UPSI
xxxxxx1x is on.
3–10 User Guide

Examples:
One input file and one output file, standard labels
// JOB TDYNCOPY
// UPSI 00000000
// TLBL UIN,'INPUT DSN',,,,,,2
// TLBL UOUT,'OUTPUT DSN',,,,,,2
// EXEC TDYNCOPY,SIZE=128K
/&
Three input files on separate volumes to be written as three output files on the
same volume
// JOB TDYNCOPY
// UPSI 11000000
// TLBL UIN,'INPUT DSN 1',,,,,,18
// TLBL UIN,'INPUT DSN 3'
// TLBL UOUT,'OUTPUT DSN 1',,,,,,24
// TLBL UOUT,'OUTPUT DSN 3'
/&
Two input files on the same volume to be written as two output files on
separate volumes
// JOB TDYNCOPY
// UPSI 10000000
// TLBL UOUT,'OUTPUT DSN 2'
/&
Three input files on separate volumes to be written as one output file
// JOB TDYNCOPY
// UPSI 10001000
// TLBL UIN,'INPUT DSN'2',,,,,,18
// TLBL UOUT,'OUTPUT DSN'
/&
Two unlabeled input files on separate volumes to be written as two data sets
on the same multifile volume

// JOB TDYNCOPY
// UPSI 11100001
/&
Note: Establish multifile input or output data sets in the Catalog if they are to
be controlled by CA Dynam/T.
This job stream is an example of using // UPSI nnnnnn1n in combination with

other UPSI settings to force multifile processing and reblocking. Note that the
control statements can be submitted on separate statements or on the same
statement.
// JOB TDYNCOPY READ FROM SYSIPT

// UPSI 11001110
// TLBL UIN,'INPUT1',,,,,,16
// TLBL UIN,'INPUT2',,,,,,16
// TLBL UIN,'INPUT3'
// TLBL UOUT,'COPY FILE1',,,,,,24
// TLBL UOUT,'COPY FILE2'
// TLBL UOUT,'COPY FILE3',,,,,,24
FILES=3
LRECL=00090
NRECS=20
UIN=REW
UOUT=NOR
UIN=REW,UOUT=NOR
UOUT=REW,UIN=REW
/*
/&
Tape Label Generator—TDYNLBL
TDYNLBL prints large block alphanumeric volume serial numbers on gummed

labels to assist operators in easily recognizing CA Dynam/T controlled tapes.
If executed from the console, TDYNLBL requests the following:
The number of desired test patterns
The starting and ending numbers
The number of digits
A prefix
3–12 User Guide

The number of blank lines between labels (normally 9 for CA Dynam/T

labels)
A number to increment for nonsequentially numbered labels
This program does not skip to any channels. It therefore needs to know the
number of blank lines to skip between printed numbers.
If executed from job control, TDYNLBL reads free-form parameter statements

between positions 1 and 71. Do not enter any characters beyond position 71.
Continuation statements are not allowed.
TDYNLBL Control Statement Format
BEGIN=nnnnnn END=nnnnnn [ DIGITS=n ]

[ INCrement=nnnnnn ]
[ PREFIX=xxxxxx ]
[ SKIP=n ]
[ TEST=n ]
The following parameters are allowed:
BEGIN=nnnnnn Indicates the beginning, numeric part of the VOLSER.
a 1- to 6-digit number
END=nnnnnn Specifies the ending, numeric part of the VOLSER. It must be greater than or
equal to BEGIN.
DIGITS=nnnnnn Optional. Signifies the size of the numeric part of the label. The default is 6
minus the length of the prefix.
a 1-digit number, 1-6
INCrement=nnnnnn Optional. Specifies a number to add to each label number to determine the
next label number to print.
PREFIX Optional. Identifies the label prefix.
1-6 alphanumeric characters
SKIP=n Optional. Indicates the number of blank lines between labels. The default is 9.

TEST=n Optional. Specifies the number of test patterns to print.
Example:
// JOB TDYNLBL PRODUCE GUMMED LABELS

// EXEC TDYNLBL,SIZE=128K
BEGIN=11 END=222 DIGITS=3 PREFIX=DT
BEGIN=100000 END=999999 TEST=5
/*
/&
CHKPT/RSTRT Program—TDYNRST
TDYNRST provides support for CA Dynam/T-controlled tape files in conjunction

with the VSE CHKPT/RSTRT facility. You do not have to make special
provisions for CA Dynam/T support when a program that has CHKPT/RSTRT
capability is initially executed.
If the program terminates normally, all files are cataloged as usual. However,
if it terminates early for any reason, and a restart is to be performed,
TDYNRST must be executed immediately before the RSTRT statement. The
operator is prompted to enter parameters that define the CA
Dynam/T-controlled files involved in the restart. When these have been
defined, TDYNRST does the following:
Verifies that the volumes specified by the operator are the correct
volumes.
Updates the label records and the Catalog entries to allow processing to
continue under CA Dynam/T control.
Use of this facility is subject to the following conditions:

Submit all necessary TLBLs and ASSGNs before executing TDYNRST.
Mount the input and output tapes on the correct drives, and assign the
logical unit through job control. TDYNRST does not perform AVR and does
not verify that the assigned physical tape has the correct volume serial
number.
Establish the desired mode specification for output tapes on the ASSGN
statement. However, all other CA Dynam/T options are recognized from
the TLBL.
Do not perform the DYNCAT SCRATCH function between the original

execution of the problem program and the restart.
3–14 User Guide

Make sure to specify the correct volume serial and sequence numbers when
entering the parameters; the Catalog is updated as soon as the numbers are
verified. Define each tape file to be restarted under CA Dynam/T control to
TDYNRST. When the last tape file has been defined, enter EOB/END to
terminate TDYNRST processing.
TDYNRST Control Statement Format
filename,volser,volseq,{I|O}
filename Indicates the 1- to 7-character file name.
volser Specifies the 1- to 6-character volume serial number.
volseq Identifies the 1- to 4-numeric volume sequence number.
I|O Symbolizes whether the file is to be used as Input or Output.
Example:
Original JCL for checkpointed program
// JOB UPDATE
// ASSGN SYS010,283 CHECKPOINT FILE
// TLBL TAPEIN,'MASTER FILE' USES SYS008
// TLBL TAPEOUT,'MASTER FILE' USES SYS009
// EXEC UPDATE
/&
The data set MASTER FILE is a CA Dynam/T-controlled data set. TAPEIN uses
SYS008 and TAPEOUT uses SYS009. The checkpoint file is SYS010 on drive
283. Checkpoint number 0007 was taken in volume two of TAPEIN, serial
number 000817, and volume three of TAPEOUT, serial number 000243. The
restart JCL might be:
// JOB UPDATE
// ASSGN SYS010,283 CHECKPOINT FILE
// ASSGN SYS008,280
// TLBL TAPEIN,'MASTER FILE' USES SYS008
// ASSGN SYS009,281
// TLBL TAPEOUT,'MASTER FILE' USES SYS009
// EXEC TDYNRST
TAPEIN,817,2,I
TAPEOUT,243,3,O
/&

The console dialog would be:
// JOB UPDATE
CADT550I TDYNRST BEGIN
CADT570D ENTER 'Y' FOR TDYNRST PARAMETERS
(EOB)
CADT551D ENTER TDYNRST PARAMETERS
TAPEIN,817,2,I
CADT561I FILE TAPEIN LABEL HAS BEEN UPDATED
TAPEOUT,243,3,0
CADT561I FILE TAPEOUT LABEL HAS BEEN UPDATED
(EOB)
CADT563I TDYNRST END
(REGULAR DOS RESTART MESSAGES)
Note: TDYNRST reads control statements from SYSIPT rather than SYSLOG
when executed with an UPSI 1.
Synchronizing Volumes (using XSYSTEM)—TDYNSYNC
The TDYNSYNC utility program provides for synchronization between two

catalogs that share tape volume status information by way of the
Cross-system (XSYSTEM) interface. CA Dynam/T and CA 1 MVS are two
systems that utilize this interface. XSYSTEM can also be shared among
multiple CA Dynam/T catalogs running on separate physical or virtual CPUs.
Before establishing a cross-system interface, review all relevant

documentation for all sharing systems. For more information about the
DTNODE and DTPATH option records, see the Programming Guide.
Described later in this section are the control statements TDYNSYNC uses to
perform a variety of functions.
Creating Multi:ACCESS Queue Files for an External Tape System
In order to use the XSYSTEM interface, you must define Multi:ACCESS (MACC)
queue files formatted as DOS- or OS-formatted files. The MACC queue files
serve as data transmission media, or message paths. They are defined in the
PATHID parameter of the DTPATH option record. A separate MACC queue file
must be created and initialized once for each pathid specified in the DTPATH
option record.
The MACC queue files must reside on DASD devices accessible by the FROM
and TO systems using the corresponding paths defined in the DTPATH option
record.
3–16 User Guide

Message paths are accessed by the system using direct physical IOCS and
should be defined as SD files for label purposes. It is recommended that you
locate MACC queue files on physical disk volumes other than those that
contain the Catalog or Audit Trail data sets.
Initializing Multi:ACCESS Queue Files
Use the MACC INITIAL command of the DYNCAT utility program:
MACC INITIAL DDNAME=DYN2CA1
The DDNAME must be one of the PATHID values specified in the DTPATH
option record.
Execute the MACC INITIAL command once for each unique PATHID specified in
the DTPATH option record. When DYNCAT has completed processing, the
message paths will be ready for use.
Note: If any of the participating systems run MVS, the MACC queue files
should be allocated on MVS to ensure inclusion in the MVS Master Catalog.
Performing Catalog Synchronization
Catalog synchronization is a process by which a catalog on one system is

updated with information extracted from another system, so that both systems
maintain the same volume status information.
An extract facility is supplied with each system to convert tape database

information into a common format so that it can be compared to determine if
any discrepancies exist between the two systems. Volumes from each system
are marked as either in active or scratch status.
The synchronization facilities accept the extracts from each system as input
and perform the analysis. All discrepancies are indicated on an exception
report, and the information needed to resolve the discrepancies is written to
two distinct update files, one for each system.
Each system also provides a product-specific update utility used to apply

synchronization information to its respective database. Any updates that
cannot be performed are detailed in error reports. These errors may require
additional research and manual correction.

The following diagram illustrates the synchronization process:
Before catalog synchronization is performed, it is highly recommended that the

Catalogs on both systems be backed up using the product specific utilities
provided by each system.
Avoid updating the Catalogs between EXTRACT and APPLY functions. The
APPLY uses the status information in effect at the time when the EXTRACT was
performed; any intermediate updates followed by an APPLY can cause serious
errors.
TDYNSYNC Control Statements
Each TDYNSYNC control statement starts with one of the commands shown
below in logical processing order:
CATNAME= Optional. Can be specified with other TDYNSYNC commands. It defines the
source catalog for the EXTRACT, and the target catalog for the APPLY and
REMOVE commands.
EXTRACT Produces a file (dtfname=CAT1OUT) and a report that represent all entries in
the Catalog.
SYNC Takes as input the files produced by the EXTRACTs of the two catalogs
(dtfnames of CAT1IN and CAT2IN), synchronizes the information, then
produces two output files, one for each Catalog (dtfnames CAT1OUT and
CAT2OUT). A report of catalog entries is also produced.
APPLY Takes as input one of the output files (dtfname=CAT1IN) from the SYNC
command and updates the catalog.
3–18 User Guide

REMOVE Optional. Removes all catalog entries for a particular CPUID.
Detailed descriptions of the commands follow, presented in alphabetical order.
APPLY Command The APPLY command takes as input one of the two output files from the SYNC
processing and updates the CA Dynam Catalog with tape volume status
information. When the CA Dynam/T TDYNSYNC APPLY commands for each CA
Dynam Catalog, and the equivalent commands for each participating database
(such as DYNUPDTE for CA 1 MVS) are completed, the tape management
systems will be synchronized with respect to tape volume status.
Format:
APPLY
Examples:
// JOB APPLY // JOB APPLY

// DLBL CAT1IN,'DOSVSE.APPLY' - OR - // TLBL CAT1IN,'DOSVSE.APPLY'
// EXTENT SYS004, // ASSGN SYS004,CUU
// ASSGN SYS004,CUU // EXEC TDYNSYNC,SIZE=128K
// EXEC TDYNSYNC,SIZE=128K APPLY
APPLY /*
/* /&
/&
Note:
TDYNSYNC output files can be created on disk or on tape.
The dtfname for the input file must be specified as CAT1IN, even if the file
being used as input was created using dtfname CAT2OUT from the SYNC
step.
TDYNSYNC can only APPLY data to the CA Dynam Catalog. To update

volume status information for the CA 1 TMC, use the CA 1 supplied
DYNUPDTE utility.
The default dtfname of the catalog from which the volume status
information is to be extracted is CAICATL. If you are extracting data from
another catalog, use the CATNAME control statement to specify the
dtfname of the catalog.

CATNAME Command The CATNAME command is used to define the source catalog for the EXTRACT
command, and the target catalog for the APPLY and REMOVE commands.
Format:
CATNAME=dtfname
where:
dtfname
is the dtfname of the catalog. A DLBL and EXTENT must be specified for the
dtfname.
Note:
If the CATNAME control statement is used, it must be specified before the
EXTRACT, APPLY or REMOVE commands.
If the CATNAME control statement is not specified, the default dtfname for
the catalog is CAICATL.
EXTRACT Command The EXTRACT command is used to extract volume status information and
produce an output file from the input catalog. The output file is created using
dtfname=CAT1OUT.
Format:
EXTRACT
Example:
// JOB EXTRACT // JOB EXTRACT

// DLBL CAT1OUT,'DOSVSE.EXTRACT' -OR- // TLBL CAT1OUT,'DOSVSE.EXTRACT'
// EXTENT SYS006, // ASSGN SYS006,CUU
// ASSGN SYS006,CUU // EXEC TDYNSYNC,SIZE=128K
// EXEC TDYNSYNC,SIZE=128K EXTRACT
EXTRACT /*
/* /&
/&
Note:
TDYNSYNC can only extract volume status data from the CA Dynam
Catalog. To extract information from the CA 1 Catalog, use the CA 1
supplied DYNEXTR utility.
3–20 User Guide

The default dtfname of the catalog from which the volume status
another catalog, use the CATNAME control statement to specify the
dtfname of the catalog.
The EXTRACT command is controlled by the DTPATH option record. Each

CPUID present in the input CA Dynam Catalog must be defined in the
DTNODE option record.
REMOVE Command The REMOVE command is used to remove externally controlled volume records
from the CA Dynam Catalog. In effect, the REMOVE command reverses the
processes of the APPLY command for the specified node (CPUID).
Format:
REMOVE CPUID=cpu
where:
CPUID=cpu
corresponds to the CPUID as specified by the NCPUID parameter of the

DTNODE option record.
Example:
// JOB REMOVE
// EXEC TDYNSYNC,SIZE=128K
REMOVE CPUID=Z
/*
/&
Note: The default dtfname of the catalog from which the volume status
another catalog, use the CATNAME control statement to specify the dtfname of
the catalog.
SYNC Command The SYNC command takes as input two extract files (one from each of two
systems) and creates two output files (one for each of the systems) that
contain updates to synchronize the two tape catalogs. The input files are
assigned to dtfnames CAT1IN and CAT2IN. The output files are created using
dtfnames CAT1OUT and CAT2OUT. The output file CAT1OUT is an update file
for the catalog used to create the file CAT1IN, while the file CAT2OUT is an
update file for the catalog used to create the file CAT2IN.
Format:
SYNC

Examples:
// JOB SYNC
// TLBL CAT1IN,'DOSVSE.EXTRACT'
// DLBL CAT2IN,'OS.EXTRACT'
// EXTENT SYS005,
// ASSGN SYS005,CUU
// DLBL CAT1OUT,'DOSVSE.APPLY'
// EXTENT SYS006,
// ASSGN SYS006,CUU
// TLBL CAT2OUT,'OS.APPLY'
// EXEC TDYNSYNC,SIZE=128K
SYNC
/*
/&
In the above example CAT1IN was created using the TDYNSYNC EXTRACT
command, while CAT2IN was created using the DYNEXTR utility of CA 1 MVS.
CAT1IN is a tape file, while CAT2IN is an MVS disk data set.
CAT1OUT, which will be used to update the CA Dynam catalog, is produced to

a disk file, while CAT2OUT, which will be used to update the CA 1 TMC, is
output to tape.
Note:
The SYNC command of TDYNSYNC is equivalent to the DYNSYNC utility of

CA 1 MVS.
Checklist for Synchronization
The following steps should be completed in order to ensure proper

synchronization of the CA Dynam Catalog and the CA 1 MVS TMC:
1. Define the DTNODE and DTPATH option records.
2. Terminate existing VSE PATH activity, if any, by using the Attention

Routine command: DT PATH DISABLE ALL. For more information, see
Attention Routine (AR) Commands in the chapter "Maintaining Tape Files."
Ensure that existing MVS PATH activity, if any, is terminated by taking the
appropriate action.
3. Execute the EXTRACT command of the CA Dynam/T TDYNSYNC utility. This

creates the file CAT1OUT and a report. Inspect the report to reconcile any
unextracted volumes.
Do not allow any tape activity after the EXTRACT until the APPLY function
completes.
3–22 User Guide

4. Execute the DYNEXTR utility of CA 1 MVS. This creates the file CAT2OUT
and a report. Inspect the report to reconcile any unextracted volumes.
5. Execute the SYNC command of the CA Dynam/T TDYNSYNC utility, or

execute the DYNSYNC utility of CA 1 MVS. These commands create the
files CAT1OUT and CAT2OUT (one for CA Dynam/T and one for CA 1) and
a report. Inspect the report to determine what action to take for conflicting
volumes.
6. Execute the APPLY command of the CA Dynam/T TDYNSYNC utility and

inspect the report for errors.
7. Execute the DYNUPDTE utility of CA 1 MVS and inspect the report for
errors.
8. Update the DYNAM/T option record.

9. Initialize the MACC queue files required for communication between
systems. This ensures that the MACC files will be available when
communication is initiated by the next step, and will discard any
unprocessed transactions.
Use the DYNCAT MACC INITIAL DDNAME=filename command or the

equivalent MVS utility.
10. IPL system to activate the XSYSTEM task.
11. Start the DYNCOMM task of CA 1 MVS to initiate communication from the
MVS side.
Note: If the XSYSTEM task fails from either system, resynchronization of the
catalogs will be required.
Report Samples
For more information about TDYNSYNC reports (Catalog APPLY report, Catalog
EXTRACT report, and Catalog SYNC report), see the chapter "CA Dynam
Report Examples."
Report Fields and Comments
APPLY Report Fields
DATA SET NAME Contains the last 17 characters of the data set name to be placed in the
volume record.
EXT OWN Specifies the CPUID of the current owner of the volume, if already owned by
an XSYSTEM participant.
VOLSER Contains the volume serial number associated with the transaction.

VER Specifies the relative generation of the data set.
VOL SEQ Specifies the volume sequence number of the data set.
FIL SEQ Specifies the file sequence number of the data set.
VLT Specifies the current vault location.
SLOT Specifies the current slot location.
MESSAGE Indicates the action performed on the data set.
EXTRACT Report Fields
DATA SET NAME Contains the last 17 characters of the data set name.
EXT OWN Specifies the CPUID of the current owner of the volume, if already owned by
an XSYSTEM participant.
VOLSER Contains the volume serial number associated with the data set.
VER Specifies the relative generation of the data set.
VOL SEQ Specifies the volume sequence number of the data set.
FIL SEQ Specifies the file sequence number of the data set.
VLT Specifies the current vault location.
SLOT Specifies the current slot location.
MESSAGE Indicates whether the volume is ACTIVE or SCRATCHed.
SYNC Report Fields
VOLSER Represents the volume in error.
DATA SET NAME Contains the last 17 characters of the data set name for the volume being
compared. For ANSI version 3 tapes, this is the last 17 characters before the
generation number (GDG). This field can be blank for volumes in a
multivolume multi-data set group, or for scratch tapes that have never been
used.
STAT Indicates the status of the volume on the system it is listed under. The value
SCR represents volumes in scratch status; ACT represents volumes that are in
active status.
CREATED Represents the creation date and time of the data set currently on the volume.
3–24 User Guide

SYSTEM Represents the NODEID value of the system that currently owns the volume.
This field will be blank for volumes in scratch status.
DEST Indicates the system which will receive the synchronization information for the
volume. SYS1 indicates the system represented by the data sets CAT1IN and
CAT1OUT, which is displayed on the left side of the report. SYS2 indicates the
other system. BOTH indicates that both systems are to receive information
about this volume. NONE indicates that a critical data error was detected for
the volume. The MESSAGE field contains more information.
MESSAGE Contains additional information for determining why a discrepancy occurred. If

this field is blank, a discrepancy was found in the information stored for the
volume (that is, data set name, creation date, and so on). The synchronization
utility assumes that the volume with the most current creation date and time
is accurate and sends this information to the other system.
Depending on the type of discrepancy that occurs, you can receive any of the
following messages:
CREATION DATE/TIME DOES NOT MATCH
Indicates that the creation date and time are not the same on both systems.
The conflict is resolved automatically by selecting the volume with the most
recent date and time.
DATA SET NAMES DO NOT MATCH
Indicates that the data set names are not the same on both systems. The
conflict is resolved automatically by selecting the volume with the most recent
creation date and time. If both volumes have the same date and time, the
owning system is assumed to have the correct data set name and will be used
to update the other system.
EACH SYSTEM CLAIMS OWNERSHIP
Indicates conflicting ownership of the volume. Each system thinks the tape is
under its control. The conflict is resolved automatically based upon the most
recent creation date and time.
NEITHER SYSTEM CLAIMS OWNERSHIP
Indicates that each system thinks the other system is controlling the tape. The
conflict is resolved automatically by scratching the volume on both systems.
The information from the record with the most recent creation date and time is
used to update the volumes on each system.

SYSTEM NODEIDS DO NOT MATCH
Indicates that the NODEIDs (under the column SYSTEM) do not reflect the
same information about the owning system. The conflict is resolved
automatically by selecting the volume with the most recent creation date and
time. If both volumes have the same date and time, the owning system is
assumed to have the correct NODEID and will be used to update the other
system.
SYSn EXTRACT HAS BAD STATUS/OWNER
Indicates that the volume or owner information for the volume in question
does not contain appropriate values. This may indicate a problem in the
extract utility. If attempting to resolve this error, contact a CA Technical
Support representative for the system indicated in the message.
VOLSER NOT ON SYSn EXTRACT
Indicates that the volume is active on one system and either not defined or
out-of-service (DELETE status) on the other system. The system that does not
have the volume defined is notified of the status of the volume on the owning
system.
VOLUME STATUS DOES NOT MATCH
Indicates that the volumes are not in the same status on both systems. The
conflict is resolved automatically by selecting the volume with the most recent
creation date and time. If both volumes have the same date and time, the
owning system is assumed to have the correct status, and will be used to
update the other system.
If processing cannot be performed, the following messages appear:
END-OF-FILE ON SYSTEMn EXTRACT, EXPECTED SYSTEM IDENTIFICATION

RECORD
The extract for the system specified does not contain any data. Verify that the
data set is specified correctly and that it was created by the appropriate
extract utility.
END-OF-FILE ON SYSTEMn EXTRACT, EXPECTED VOLUME INFORMATION

RECORDS
The extract of the system specified does not contain any volume information.
Verify that the data set is specified correctly and that it was created by the
appropriate extract utility. If attempting to resolve this error, contact a CA
Technical Support representative for the system indicated in the message.
3–26 User Guide

Reporting on Tape Files
FIRST RECORD ON SYSTEMn EXTRACT IS NOT AN IDENTIFICATION RECORD
The extract for the system specified was not created by the appropriate
extract utility. Verify that the data set is specified correctly and that it was
created by the appropriate extract utility.
TOTAL RECORDS READ

Displays the total number of records (excluding the identification record) that
were read from the CATnIN files.
TOTAL RECORDS Displays the total number of records (excluding the identification record) that
WRITTEN were written to the CATnOUT files.
TOTAL RECORDS INVALID

Displays the total number of volumes that contained invalid information. These
volumes have the value NONE in the DEST field of the report.

CA Dynam supplies a standard precompiled report, in addition to batch utilities
for reporting on the management of tape files. They are as follows:
Cataloged Tape Files Report—TAPES
Batch utilities, including the following:
− TDYNCLEN
− TDYNUTL
− TDYNLIST
− TDYNPULL
The TAPES report lists information about data sets on tape. It provides reports
of active tapes, scratch tapes, or all tapes. Data is retrieved from the Catalog
in volser sequence. Several options available to TAPES enhance its basic
capabilities.
The TDYNCLEN batch utility program lists tapes due for cleaning based upon
the number of OPENs and the number of I/O errors recorded for the volume.
TDYNLIST and TDYNPULL generate the following pull lists, which are listings of
the tapes necessary to run a job or series of jobs:
TDYNLIST—creates the listings by reading free-form parameter

statements.
TDYNPULL—is JCL-driven and provides a pull list for any job stream
submitted.

The TDYNUTL program performs a variety of utility and reporting functions.

Use TDYNUTL to obtain certain standard information about tapes managed by
the CA Dynam/T Tape Management System.
A complete description of these reports is provided on the following pages.
Cataloged Tape Files Report—TAPES
The TAPES report is a standard, catalog-based, volser-entry DYNPRINT report

supplied with CA Dynam. It provides overviews of how catalog-controlled tapes
are being used.
Specific features let you do the following:
Print in three different formats—reporting all tapes, active tapes only, or

scratch tapes only.
End the report at an arbitrary number of volumes.
Report on any CA Dynam Catalog, whether it is the current one.
Reports are always sorted on tape volser.
TAPES supersedes the TDYNUTL reports generated by the LIST ALL, LIST
VOL=ALL, and LIST SCRATCH commands.
Invoking the Report
Use the following DYNPRINT command sequence to invoke TAPES:
ACCESS CATALOG
REPORT TAPES [ BANNER ]
[ CATNM ]
[ CBUFN ]
[ EROPT ]
[ MAXLINES ]
[ MAXRETR ]
[ SELECT={option[,option..]} ]
[ VOL ]
The SELECT options are described here. For more information about all other
TAPES options and their application, see the chapter "General Reporting—
DYNPRINT."
3–28 User Guide

SELECT Options
The SELECT options for TAPES are all report-formatting options. Any or all of
them can be used to produce up to three reports from one command. They
are:
ALLTAPES All tape volumes are reported on, whether scratch or active. This is the default
option if the SELECT keyword is omitted.
ACTIVE Only active tapes are reported on.
SCRATCH Only scratch tapes are reported on.
SELECT=ALL prints all three reports.
You can closely approximate the three TDYNUTL reports mentioned above by
invoking TAPES with the command:
REPORT TAPES SELECT ALL
Source Code for The CA Earl source for the TAPES report is CA Dynam's library member
TAPES Report DYNTA.0.
Report Headings The report headings are self-explanatory.
Report Samples For more information, see Standard DYNPRINT Reports in the appendix “CA
Dynam Report Example.”
Tape Cleaning and Error Report—TDYNCLEN
TDYNCLEN is a batch utility program that lists tapes due for cleaning based
upon the number of OPENs and the number of I/O errors recorded for the
volume.
TDYNCLEN accesses the CA Dynam Catalog in read-only mode. It requires

temporary external storage for sorting, using the Filename WORK1 on SYS001.
Output is to SYSLST. Input is from either the SYSIPT device or the operator
console, as free-form parameter statements.
TDYNCLEN Control Statement Syntax
Apply the following rules to TDYNCLEN statements:
Use only positions 1—72 of any statement.
Enter a blank or comma after each operand.
You can enter keywords in any order, starting from any position.
Tapes will print if they meet either OPENS or ERRORS criteria.

The following table describes the keywords associated with TDYNCLEN

parameter statements.
Parameter Description Required?
OPENS=nnn Includes a tape in the report if the total number Yes

of OPENs is greater than or equal to this
operand.
a 1- to 3-digit number.
ERRORS= Includes a tape in the report if the total number Yes

of errors is greater than or equal to this
operand.
THR—causes a tape to be included if the total

number of errors is greater than or equal to the
error threshold.
STATUS= Determines which tapes to scan. No
SCRATCH—scans all tapes in SCRATCH status.
ALL—scans all CA Dynam/T tapes.
The default is SCRATCH.
Examples:
OPENS=185 ERRORS=00 STATUS=SCRATCH
ERRORS=3 OPENS=7
OPENS=35 STATUS=ALL ERRORS=7
STATUS=ALL ERRORS=THR OPENS=5
If you omit the control statement, the following defaults are used.
OPENS=0 ERRORS=0 STATUS=ALL
A report is produced containing the following information:
Volser
Number of OPENS for input, output, and total
Number of ERRORS for input, output, and total
Volume threshold—if a tape was initialized using the INT(R) function of

DYNCAT with the CLEAN keyword, the value of the error threshold is
printed
Date first and last initialized
3–30 User Guide

Date last scratched and last cleaned
Tape status
C active tape
S scratch tapes
O opened, but never closed
L created when data set was locked
T created under job $TEST
D the owning data set was deleted
Note that if the tape status cannot be determined, a question mark is printed
preceded by the hexadecimal representation of the status byte according to
the CA Dynam Catalog.
Example:
// JOB TDYNCLEN
// DLBL WORK1,'WORK.01'
// EXTENT SYS001,. . .extent information. . .
// ASSGN SYS001,cuu
// EXEC TDYNCLEN,size=128k
ERRORS=3 OPENS=5 STATUS=ALL
/*
/&
After a tape has been cleaned, use the DYNCAT SCRPOOL command to reset
the number of tape errors and reflect the date cleaned in the CA Dynam
Catalog.
Pull List Utility—TDYNLIST
TDYNLIST reads free-form parameter statements and generates a listing of the

tapes necessary to run a job or series of jobs. For more information about
TDYNLIST reports, see the chapter "CA Dynam Report Examples."
TDYNLIST accesses the CA Dynam Catalog in read-only mode, and requires

the use of temporary external storage for sorting, using the dtfname WORK1
on SYS001. Output is to SYSLST and input is from the SYSIPT device.

In addition to a pull list, you can include comments and instructions to the
operator, tape librarian, or data control clerk. They are printed in the same
sequence in which the parameter statements are processed. A second report is
also printed listing all tapes to be pulled in volume serial number sequence
along with an estimated number of required SCRATCH tapes.
TITLE= Skips to a new page. The 48 characters following the equal sign are new page
heading. Supply a TITLE statement anywhere in the input stream to start a
new page and heading.
STEP= Skips two lines and prints the 48 characters that follow the equal sign. Each
step is numbered to permit references to already created data sets currently
needed for input.
DN= Indicates a data set is being used for input or created for output. Specify a 1-
to 44-character data set name enclosed in single quotation marks.
DN parameters:
VR= An input version from 1 to 255. The data set name and
numbers for the specified version are printed. Version 1
is the default.
NOTE= or N= Up to 53 characters of comments to be printed to the

right of the volume serial numbers. If this parameter is
specified, the comment for this data set is printed.
JOB= or J= An 8-character jobname to force printing of new step

name if this jobname is different from the jobname on
the previous DN statement.
SCRATCH or SCRATCH=nn
Indicates a scratch tape needed because a data set is

being created for future reference with the NEW
parameter. You can also specify SCRATCH=NN to indicate
how many scratch tapes are needed.
NEW Indicates that the data set was created in a previous

step. Prints the step number that created this data set as
a reference for the operator.
NOTE= Prints the 53 characters that follow the equal sign as comments on the listing.
Use the NOTE= statement to print instructions to the operator, tape librarian,
or control clerk on the pull list.
ROUTE Prints a routing sheet to serve as a check for each section through which the
listing is routed.
3–32 User Guide

Example:
TDYNLIST input stream
// JOB TDYNLIST GENERATE CA Dynam/T PULL LIST

// EXTENT SYS001,. . .extent information. . .
// EXEC TDYNLIST,SIZE=128k
TITLE=PAYROLL SYSTEM PULL LIST
STEP=EDIT TRANSACTIONS
DN='PR TRANS',SCRATCH,NOTE=EDITED PAYROLL TRANSACTIONS
STEP=UPDATE PAYROLL MASTER
DN='PR MASTER',NOTE=INPUT PAYROLL MASTER
DN='PR MASTER',SCRATCH
DN='PR TRANS',NEW
NOTE=ANY SPECIAL HANDLING INSTRUCTIONS MAY APPEAR HERE
ROUTE
/*
/&
JCL-driven Pull-list Utility—TDYNPULL
TDYNPULL generates a list of the volume serial numbers and total number of
scratch tapes needed for any job stream you submit. Any combination of CA
Dynam DLBL and TLBL statements are accepted along with the standard VSE
JCL.
TDYNPULL accesses the CA Dynam Catalog in read-only mode. It requires the

use of temporary external storage, and a dtfname of WORK1 on SYS001, for
sorting. Output is directed to SYSLST.
You can execute TDYNPULL from the console or from SYSRDR. Acceptance of
input and end of input, varies as follows, depending on where TDYNPULL is
executed from:
If executed from the console—Input is accepted from SYSLOG; the end of

input is denoted by a null response to the CADT650I message.
If executed from SYSRDR—Input is accepted from SYSIPT; a statement

(starting in position 1) containing the words TDYNPULL END signals the
end of input.
A report line is produced for each valid input statement that follows:
// JOB
// EXEC
// DLBL
// TLBL

TDYNPULL Processing
To determine a file's input or output status, TDYNPULL uses the following

hierarchy of methods:
Checks the IBM DISP= parameter on the TLBL statement. Depending on

the parameter, the file is assumed to be either input or output.
– If the value is DISP=OLD, the file is assumed to be input.
– If the value is DISP=NEW, the file is assumed to be output.
Looks for an input or output indication in the comment portion of a TLBL

statement
Compares the user-defined pull table to the dtf name and, optionally, job
name, phase name, or both. If a match is found, the user-defined input or
output status is used.
Searches the CA Dynam Catalog, reading all the versions for the data set
name. Matching is done against the CA Dynam Catalog creation job name
and phase name. If a match is found, the file is assumed to be output.
Otherwise, the file is considered to be input.
A TLBL with a dtfname of REF indicates the first stack TLBL represents a
reference to a controlled version of the data set. Otherwise the first stack
for a particular stack id will cause a scratch tape to be allocated.
Note that after a file is determined to be input, the most current version's
volser is used unless specifically overridden by TLBL options (volseq, volser,
generation).
Example:
TDYNPULL Input Stream
// JOB TDYNPULL JCL DRIVEN PULL LIST

// DLBL WORK1
// EXTENT SYS001, . . .extent information. . .
// EXEC TDYNPULL,SIZE=128K
// JOB UPDATE MASTER
// TLBL INMAST,'MASTER.FILE' INPUT
// TLBL OTMAST,'MASTER.FILE' OUTPUT
// TLBL UPDATE,'UPDATE.FILE'
// EXEC UPDATEM
/*
/&
TDYNPULL END
/*
/&
3–34 User Guide

Input JCL The following are considered for input JCL statements:
If POWER is active, you must remove the POWER JECL statements, such
as the following, before running TDYNPULL:
− * $$ JOB
− * $$ LST
− * $$ PUN
Only * $$ SLI statements are supported.
A maximum of 100 TLBL/DLBL statements per job step is allowed.
// EXEC PROC statements are not supported.
Only DLBLs that point to input tape versions are supported.
TDYNPULL Output
After all input TLBL/DLBL statements for a given step are processed, and prior
to printing the EXEC statement, TDYNPULL scans the pull table. During this
scan, TDYNPULL looks for entries marked as STD=YES. Entries that match this
step's phase or job are processed, producing a report line showing necessary
input volumes or scratch tapes. These lines are marked by the word STD to
the right of the generated TLBL statement.
Note that if an input TLBL with a matching dtf name and phase or job name is
encountered in the pull table, the pull table entry is ignored for this input job
step.
Report Lines
The TDYNPULL report line consists of a comment on the left and the JCL
statement to the right. Shown below are the comments that can appear on a
TDYNPULL report.
Comment Meaning
CONTROLLED, VERSION NOT A TLBL/DLBL called for a specific version

FOUND as input, but that version could not be
found in the CA Dynam Catalog.
SCRATCH TAPE REQUIRED A scratch volume is required for this

output file. A count of total scratch tapes
required is produced at EOJ.
UNCONTROLLED A TLBL/DLBL contains a data set name

that could not be found in the CA Dynam
Catalog, and input/output could not be
determined.

UNCONTROLLED INPUT A TLBL/DLBL contains a data set name

Catalog, but TDYNPULL determined that
this file is input.
UNCONTROLLED OUTPUT A TLBL/DLBL contains a data set name

Catalog, but TDYNPULL determined that
this file is output.
VOLSER VOLSER VOLSER These are the input volumes required for
this file. They are also summarized at
EOJ.
DYNPULL PULLTAB Option Record
TDYNPULL uses the PULLTAB option record to determine the following:
The status (input/output) of a particular file created by a specific job,

phase, or both.
Whether a particular job or phase uses TLBL/DLBL information from

partition or standard labels; whether a particular job and phase use
TLBL/DLBL information from partition or standard labels.
PULLTAB Parameters
Standard IBM syntax rules for assembling an option record apply. The
parameters available for the PULLTAB option record are detailed in the
following table:
IOIND= {I|O } Specifies how the file is used:
I - as input
O - for output
JOB=jobname Optional. Identifies the job name you want to associate with this file. (Follow
IBM syntax rules.)
DTF=dtfname Supplies the dtf name. (Follow IBM syntax rules.)
PHASE=phasename Optional. Indicates the phase name of the phase you want to associate with
this file. (Follow IBM syntax rules.)
DSN=dsn Required when specifying STD=YES. Specifies the data set name. The data set
name can contain CA Dynam/T options with a maximum length of 44
characters (59 including options).
3–36 User Guide

STD= {YES|NO } Optional. Indicates whether the label information is in standard labels.
YES
NO
END=YES You must include END=YES as the last statement of the PULLTAB option
record. END=YES causes the start of the TDYNPULT phase generation.
Coding the PULLTAB Option Record
The following job stream is used to generate and catalog the phase TDYNPULT.
At installation time, the source book called TDYNPULT is cataloged into
Sublibrary A. An example of the assembly is contained in the source book
CAYDMACS in Sublibrary Z.
// JOB TDYNPULT CATALOG THE TDYNPULL PULL TABLE

// OPTION CATAL
PHASE TDYNPULT,*
// EXEC ASSEMBLY
PULLTAB TYPE=BEGIN
PULLTAB IOIND=O,JOB=,DTF=SORTOUT,PHASE=SORT,DSN=, C
STD=NO
PULLTAB IOIND=I,JOB=,DTF=SORTIN1,PHASE=SORT,DSN=, C
STD=NO
STD=NO
STD=NO
STD=NO
STD=NO
STD=NO
STD=NO
STD=NO
STD=NO
PULLTAB IOIND=I,JOB=,DTF=UIN,PHASE=,DSN=,STD=NO
PULLTAB IOIND=O,JOB=,DTF=UOUT,PHASE=,DSN=,STD=NO
PULLTAB END=YES
END
/*
// EXEC LNKEDT
/&

Note:
Submit the more-specific entries (those with phase and job names) before
the more-generic (those without phase or job name).
Limit your PULLTAB entries to the current 200 maximum.
Utility Reporting Program—TDYNUTL
The TDYNUTL program performs a variety of utility and reporting functions.

Use TDYNUTL to obtain certain standard information about tapes managed by
the CA Dynam/T Tape Management System. For more information about
TDYNUTL reports, see the chapter "CA Dynam Report Examples."
Control statements request the TDYNUTL functions. Depending on where the

program is executed from, the following conditions apply:
If the program is executed from the console, they are issued from the
SYSLOG device.
If the program is executed from a job stream, they are read from the
SYSIPT device. You can assign SYSIPT to a card reader, magnetic tape
unit, or DASD. It must consist of 80-byte records.
The chart below lists the TDYNUTL commands and their functions:
To Use
Command
display selected portions of the tape library on the console DISPLAY
end the program when issued from SYSLOG END
format the number of lines and line spacing on a report page FORMAT
list tapes created or processed under exceptional circumstances EXCEPTS
list all or part of the tape library on SYSLST LIST
TDYNUTL Commands
You can abbreviate all TDYNUTL commands using any number of characters.
For example, the following commands all perform the same function:
DISPLAY DSN='data set name'
DISP DSN='data set name'
3–38 User Guide

D DSN='data set name'
You can use the keywords DSN and DN interchangeably.
The generated report is printed in the same sequence in which the control
statements were processed, except for the following commands:
LIST DN='data set name'

LIST VOL=123456
The reports generated from these commands are printed last.
Note: All LIST functions require a sorting function. CA SRAM accomplishes this
sorting function and is cataloged as a part of TDYNUTL. CA SRAM requires
external DASD storage for the Filename, WORK1. The logical unit used is
SYS001.
DISPLAY Command
Issue the DISPLAY command to list information about selected tapes or data
sets on the operator console.
DSN= Displays the characteristics (volume serial number, creation and expiration
dates, owner ID, vault ID, etc.) of the indicated data set along with the three
most current versions of the data set on the console.
a 1- to 44-character data set name of the file to be displayed, enclosed in

single quotation marks.
VOL= Displays the characteristics of the indicated volume on the console.
a 1- to 6-character volume serial number of the volume to be displayed; the

number will be left-justified with zeros.
NVER= Controls the number of versions displayed on the console. Any numeric value
is valid. (default is 3).
Example:
// JOB DISPLAY EXAMPLE

// EXEC TDYNUTL,SIZE=128K
DISPLAY VOL=1234
DISPLAY DSN='FILE1'
/*
/&

This job stream logs the following on the console:
Selected data from the tape with volume serial number 1234
The first three volumes associated with the file FILE1 in version number
sequence, listing the current version first
Example of Console Log for 2:
BG CADT000I DATA-SET-NAME-VOLSER OW VER VOL FIL CREATION EXPIRY-- CYC PEC VT

BG CADT000I FILE1
BG CADT000I VOL333 EP 001 001 001 01/22/00 01/24/00 002 000 A
BG CADT000I VOL444 EP 002 001 001 01/22/00 01/24/00 002 000 A
BG CADT000I VOL555 EP 003 001 001 01/22/00 01/24/00 002 000 A
EXCEPTS Command
This command generates a report, in Data Set Name sequence, of all files that
were created or processed under the following exceptional circumstances:
Operator accepted an input tape version other than the one called for by
the system.
Tape was manually cataloged into the system.
An alternate input tape for this data set was used.
Tape was scratched with the RERUN command.
Running this report clears the condition that caused a tape to appear on this
report.
Example:
// JOB PRINT EXCEPTION

// ASSGN SYS001,130 DISK WORK FILE
// DLBL WORK1,'WORKAREA',0,SD
// EXTENT SYS001,...
EXCEPTS
/*
/&
Note: The Audit facility provides more complete reporting on unusual

occurrences.
3–40 User Guide

FORMAT Command
The FORMAT command sets the number of lines and the line spacing on any of
the reports generated by TDYNUTL. The FORMAT control statement is
free-form with the command FORMAT followed by two required positional
parameters. The two parameters are separated by a comma.
Positional parameter-1 Two-digit number from 10 to 99 that specifies the number of lines to be
printed on a report page.
Positional parameter-2 One-digit number from 1 to 3 that specifies the number of lines to space
between print lines.
Example:
// JOB LIST OF ALL TAPES DOUBLE SPACED

FORMAT 28,2
LIST ALL
/*
/&
Note: Make sure that the number of lines and the line spacing are
compatible—for instance, if double spacing and 60 lines are specified, there
will be a page overrun.
LIST Command
The LIST function creates various reports that are output to SYSLST. You
indicate the type of report through one or more of the keyword or positional
parameters. LIST has a free-form format. The operation code LIST is followed
by one or more of these keyword or positional parameters:
ALL Generates a listing of all volumes in the library in volume serial number
sequence.
DSN= Generates a listing of all or selected data sets in the library. Valid entries are:
1- to 44-character data set name enclosed in single quotation marks
ALL - for all data sets
NEW Generates two listings of all tapes that have been cataloged manually or by
the system since the last time the LIST NEW function was executed. One
listing is in volume serial number sequence, and the other is in data set name
sequence.

Important! Run the LIST NEW report only when there are no tape files being
created in other partitions.
PASSWORD= Generates a list of all data sets which are password-protected, along with the
associated password.
Eight-character catalog password enclosed in single quotation marks.
SCRATCH Generates a listing of all scratch tapes in the library in volume serial number
sequence.
VOL= Generates a listing of all active tapes or tapes selected by volume serial
number. The list is in volume serial number sequence. Valid entries are:
1- to 6-character volume serial number
ALL - for all active tapes
Example:
// JOB PRINT VARIOUS REPORTS

LIST ALL X
LIST DSN='ALL' or LIST DSN=ALL Y
LIST DSN='FILE NAME' Z
LIST VOL=ALL [
LIST VOL=234 \
LIST NEW ]
LIST SCRATCH ^
/*
/&
This job stream generates the following listings:

X All tapes in volume serial number sequence
Y All data sets in data set name sequence
Z All tapes associated with the file FILE NAME in ascending sequence by
version number (the current version is listed first)
[ All active tapes in volume serial number sequence
\ Volume serial number 234
] Two lists of all tapes cataloged in the library since the last time this
function was performed. One list is in volume serial number sequence and
the other one in Data Set Name sequence
^ All scratch tapes in the library in volume serial number sequence
3–42 User Guide

Report Fields and Comments
Each of the reports produced by TDYNUTL and DYNCAT uses a similar format.
The following lists describe the fields and special comments that can appear on
the reports:
CPU Alphabetic CPU ID of the CPU on which this version was created. It is
determined by the System Adapter option record.
CUU Tape unit on which this version was created. If the version was created using
the DYNCAT ADD function, this field is blank.
DATE Creation date of this version. This is taken from the system date in the
supervisor—not the temporary COMRG date. You can modify it with the
DYNCAT ALTER function.
DAY Number of days from creation date that data set versions are to be retained.
DSN Name of the data set as it appears in the catalog file.
EXP-DATE Expiration date of this version. If days retention is specified, this value is
calculated when the version is created or taken from the TLBL. You can modify
it with the DYNCAT ALTER function.
FIL File sequence number.
JOB-NAME Jobname in which this version of the data set was created.
LEN Length specified for the data set, tape volume, or both.
MODE Mode at which the version was created.
MSG Additional notes about this version; for example, MF for multifile data set and
AMF for automatic multifile data set.
NGEN Number of versions to be retained.
NOAC Number of days to retain this version since it was last accessed as input.
OW ID Data set owner identification characters—blank if there is no ownership for the

data set.

PED AS-OF-DATE in effect when this version of the data set was created. This field
is blank if the following conditions are true:
The AS-OF-DATE in effect is the same as the creation date.
There is no AS-OF-DATE control. (To the left of the 8-character

AS-OF-DATE is the number of AS-OF-DATE cycles established for the data
set. If the value of the AS-OF-DATE field is not equal to the creation date—
as is the case if a // DATE was in effect when the version was created—
and there is no AS-OF-DATE control, a C appears in place of the number of
cycles.)
PED CYC AS-OF-DATE cycles in effect for this data set.
PT Partition in which this version was created. If the version was created using
the DYNCAT ADD function, the partition in which DYNCAT was executed is
used.
SY ID System identification characters (for reporting purposes only).
TAPE ERRS Number of recoverable write errors that occurred on this volume when this
version was created. This field is blank if there were none.
TIME The time this version was created.
US ID User identification characters (for reporting purposes only).
VER Version number of this version (generation). One is the most current. An
asterisk (*) beside the version number indicates that the version is eligible for
SCRATCH and will be returned to SCRATCH status the next time the SCRATCH
function is performed.
VLT Current vault location of this version--blank if there is no vault control for this
data set.
VOL Volume sequence number.
VOLSER Volume serial number.
In addition to these fields, each data set has a comment line (if a comment
has been established for it).
CREATED AS TEST TAPE

The volume was used as output in a $TEST job.
CREATED WHEN LOCKED FOR OUTPUT

The volume was created when the data set was locked.
MANUALLY SCRATCHED
The volume was scratched using the DYNCAT DELETE function.
3–44 User Guide

Vault Location Control Program—TDYNVLT
NOT CLOSED The volume was opened but never successfully closed.
NOT INITIALIZED CA Dynam/T has never initialized the volume.
SCRATCHED ON mm/dd/yy
The date the volume was returned to SCRATCH status.
TAPE USED FOR UNCONTROLLED FILE

This volume (which is in SCRATCH status) has been used as output for an
uncontrolled file.

CA Dynam Vault Location Control is designed to help you control the location
of data sets that require off-site storage. TDYNVLT updates, verifies, and
reports on vault locations. It produces two types of reports for controlled files:
movement reports and inventory reports. For more information about
TDYNVLT reports, see the appendix “CA Dynam Report Examples."
TDYNVLT compares the current location of each version of all vault-controlled

data sets against the desired location. If the two are not the same, TDYNVLT
does the following:
Displays the volume serial number on the movement report
Updates the Catalog to reflect the current location
CA Dynam/T considers the tape actually moved when it appears on a

movement report. If the tape is to be kept somewhere other than the specified
location, inform CA Dynam/T with a manual update (using DYNCAT).
If this movement occurs, the tape is reported in its new location until TDYNVLT
is run again. At that time, normal rotation takes place. If the change is to be
permanent (making normal rotation undesirable), be sure to indicate the PERM
specification (PERM=YES) through DYNCAT. This specification remains intact
until the version is altered with PERM=NO.
There will also be no vault movement if any of the following is true:
The data set is locked
The version is $TEST
The version is locked

Establishing Vault Locations
To establish the desired location for each version of a data set, you can do the
following:
Specify a location for each of the first 999 versions.
Specify up to 26 different locations.
Attach to each location, a 77-character description to be printed on the

vault reports.
If a version does not have a specified vault location, TDYNVLT uses the data
set's default vault location.
You can specify the starting version of a data set for the vault location by
including the VLTSEQ=nnn parameter with VLTLOC. Vault sequencing lets you
define which of up to 999 versions of a data set has vault control. VLTSEQ
must be used with VLTLOC on a DYNCAT ALTER command.
You can also define slot numbers within all vault locations, except vault A.
These slot numbers enable you to further control the vault locations. For each
vault, you can do the following:
Define up to 10 ranges of slot numbers, with a maximum of 65,536 slots

per range.
Define and delete slot-number ranges using the DYNCAT program.
Defining Slots
To define slots within vaults, use the DYNCAT VAULT control statement, as
follows:
VAULT VLTLOC=x [DESC='xxxxx'] SLOTS=(x1,y1)
You can define up to 10 ranges of slot numbers, but only one range per
statement. Each slot range must be uniquely associated with a VLTLOC=
parameter and a VAULT command. For example,
VAULT VLTLOC=B SLOTS=(100,200)

VAULT VLTLOC=C SLOTS=(50,100)
To place slot numbers within your CA Dynam Catalog, run the following as the
first VAULT movement after the conversion:
// JOB TDYNVLT
// EXTENT SYS001..........
// ASSGN SYS001,cuu
3–46 User Guide

// EXTENT SYS002..........
// ASSGN SYS002,cuu
// EXEC TDYNVLT,SIZE=128K
MOVEMENT
VERIFY
/*
The MOVEMENT function activates the vault movement. The VERIFY function
gets a slot number for all volumes whose vault is not rotated and for whose
vault location slot support is defined. You can run this first with the DUMMY
option to avoid CA Dynam Catalog update.
For more information about these functions, see TDYNVLT Commands.
Running TDYNVLT
Run TDYNVLT daily or weekly, depending on how often you transfer tapes from
one location to another. By definition, vault location A is the main tape library.
The DYNCAT SCRATCH function will scratch expired versions only if they
currently reside in location A. Therefore, if you run both programs each day,
run TDYNVLT before DYNCAT.
TDYNVLT has the following six phases of execution:
1. Gathers all vaults that will require an automatic verify
2. Collects vault location changes
3. Verifies, frees, and gets slot numbers; also updates the CA Dynam Catalog
4. Prints movement reports
5. Generates inventory reports
6. Prints the inventory reports
If TDYNVLT cancels for any reason during execution, run the DYNCAT BACKUP
function to verify the integrity of the Catalog: Vault movement information
may have been lost. (DYNCAT RESTORE is unnecessary if you are running
TDYNVLT with the DUMMY option, or if the CADT602I message has not been
issued.)
You can activate TDYNVLT functions with control statements. If you do not
submit any control statements, TDYNVLT will end normally unless TDYNVLT
detects that an automatic verify is required. In that case, TDYNVLT continues
as if the VERIFY control statement had been submitted.

The following JCL example for TDYNVLT shows the necessary job control:
// JOB TDYNVLT
// EXTENT SYS001. . .
// EXTENT SYS002. . .
. . . control statements . . .
/*
/&
Note that DLBLs and EXTENTs are required for WORK1 and WORK2. These files
must use SYS001 and SYS002 respectively. Both WORK1 and WORK2 can be
allocated using VSAM/SAM.
Use the DYNCAT maintenance program for the following:
Vault location descriptions
Vault locations for data sets
Defining slots
TDYNVLT Control Statement Format
All TDYNVLT control statements have the same general format:
Positions:
1 71 72 73 80
+--------------------------------------------------------------+ + +--------+
<operation > cc
TDYNVLT Control Statement Syntax
The following rules apply to TDYNVLT statement syntax:
Control statements are free-form. They begin in position 1 and can

continue through position 71.
Unless it is a continuation, each statement must begin with a command. If

they are required, one or more operands follow the command. Use blanks
to separate the command from the operands and the operands from each
other.
You can continue any control statement by placing a non-blank character

in position 72 and continuing the information between positions 1 and 71
of the next statements. Up to 10 continuations per statement are allowed.
3–48 User Guide

TDYNVLT Commands
Description Use Command
Generates inventory reports for all or selected vault INVENTORY

locations.
Creates a file which contains a list of all the tapes in the INVENTORY
Catalog. This file can be downloaded to a CA WORKSTATION EXTRACT
basic system.
Activates location movement. MOVEMENT
Creates a file with a ddname of CAIEXTR, which contains a MOVEMENT

list of all the tapes in the Catalog. EXTRACT
Checks all volumes to make sure that the slot numbers are VERIFY
correct and generates new slots for a vault location (if the
location's slots are changed).
INVENTORY Command
Format:
INVentory [ SEQ= {VLTVOL|SLOT|DSN } ]

[ INCLVLT=(x,x,.....x,x)|EXCLVLT=(x,x,.....x,x) ]
[ MDSN=NO|YES ]
OR
INVentory EXTRACT
All INVENTORY parameters are optional.
SEQ= Specifies the sorting sequence to be used for the report.
VLTVOL Vault location and volume serial number sequence
SLOT Vault location and slot number sequence
DSN Data set name sequence
The default is VLTVOL.
The INCLVLT AND EXCLVLT operands are mutually exclusive.

INCLVLT=(x,x,.....x,x) Selects the vault locations to be reported on. If you omit this operand,
TDYNVLT reports on the following:
All vault locations, unless EXCLVLT is defined
All vault locations except those defined by EXCLVLT
EXCLVLT=(x,x,.....x,x) Indicates which vault locations to leave out of the report. If you omit this
operand, TDYNVLT reports on the following:
All vault locations, unless INCLVLT is defined
Only vault locations defined in INCLVLT
MDSN= Determines which data set names of a multifile volume are to be listed on the
report.
YES Prints all the data set names of a multifile volume.
NO Prints only the first data set name.
The default is NO. If the report sequence is based on data set name, it is
always based on the first data set name of a multifile.
EXTRACT Creates a file (with a ddname of CAIEXTR), that contains a list of all the tapes
in the Catalog.
This command should be executed only once.
Note: The TDYNIBM program EJECT command can be used to read the
CAIEXTR file and eject volumes from the 3494 Tape Library. For more
information, see IBM 3494 Tape Library Interface.
Inventory Report Location Inventory (Verification) Report (TDYNVLT-05)
Lists all tapes in each vault. TDYNVLT can generate this report for all or
specific vault locations. If the report is by volume serial number, it lists only
the first data set of a multifile, unless you specify MDSN=YES.
3–50 User Guide

MOVEMENT and VERIFY Commands
MOVEMENT Command The format for the MOVEMENT command is:
MOVement {EXTRACT|DUMmy|TRace }
VERIFY Command The format for the VERIFY command is:
VERify {DUMmy|TRace }
Command Parameters
The parameters for the MOVEMENT and VERIFY commands follow.
EXTRACT Must be the only parameter specified. Creates a file with a ddname of
CAIEXTR, which contains a list of all the tapes in the Catalog.
Note: The TDYNIBM program EJECT command can be used to read the
CAIEXTR file and eject volumes from the 3494 Tape Library. For more
information, see IBM 3494 Tape Library Interface.
DUMMY Does not update the Catalog.
TRACE Supplies a trace of all Catalog updates.
Movement Reports
Location Exit Report (TDYNVLT-01)

TDYNVLT generates this report every time volumes are moved from one
location to another. It produces up to 26 different Location Exit reports, one
for each location under its control.
Location Entry Report (TDYNVLT-02)

TDYNVLT generates this report every time volumes are moved from one
location to another. It produces up to 26 different Location Entry reports, one
for each location under its control.
Movement Summary TDYNVLT lists, by volume serial number, all tapes that have been
Report transferred. This is primarily for auditing or historical purposes.
(TDYNVLT-03)
Vault Exception Report (TDYNVLT-04)

TDYNVLT lists all tapes in vaults other than the one specified for normal
rotation. This occurs because of one of the following:
DYNCAT specifies PERM=YES
TDYNVLT includes the VERIFY option

IBM 3494 Tape Library Interface

The CA Dynam/T interface with the IBM 3494/3495 family of tape libraries
reduces operator intervention for mounting and dismounting cartridge
volumes. You are no longer required to search for and mount a volume for an
open request. This interface removes the need for a response to CA Dynam/T
to mount a tape.
CA Dynam/T communicates with the IBM Tape Library Dataserver using the
IBM LBSERV macro interface. IBM supports communication with the Tape
Library Dataserver on VSE natively using the VSE Library Control Device Driver
(LCDD). LCDD is an IBM VTAM application which runs in a separate VSE
partition. Alternately if VSE is running as a guest under VM the VSE Guest
Server (VGS) may be used by IBM to communicate with the Tape Library
Dataserver.
In order to activate the CA Dynam/T VSE LBSERV interface, when using either
LCDD or VGS, MODON=11 must be set ON in the CA Dynam/T System option
record. For more information about how to setup either LCDD or VGS see the
appropriate IBM documentation.
Controlling Scratch Pools
The 2-byte CA Dynam/T OWNERID is used to support the IBM Tape Library
scratch poolid. If a dataset has a CA Dynam/T OWNERID of 00 through 31, the
corresponding IBM scratch poolid (for example, SCRATCH00—SCRATCH31) is
used to allocate a scratch tape for output processing. When an active tape
with a CA Dynam/T OWNERID of 00 through 31 is scratched it is returned to
the appropriate IBM Tape Library scratch pool.
The IBM VGS service machine only supports scratch poolids SCRATCH00
through SCRATCH15 therefore the only valid CA Dynam/T OWNERIDs are 00
to 15 when using the VGS.
MODON 22 must be set ON in the CA Dynam/T system option record when

using the VGS so appropriate checks can be made concerning the limited
support of scratch poolids.
Using the CA DYNAM/T-VM Service Machine
Communication to the IBM Tape Library Dataserver can also be done using CA
Dynam/T VM which communicates directly with the server.
If CA Dynam/T VM is used as the communication tool to the robot, both

MODON=11 and MODON=22 must be set to OFF in the CA Dynam/T system
option record.
3–52 User Guide

For information about how to set up the IBM 3494 using CA Dynam/T VM, see
the CA Dynam/T VM documentation.
IBM 3494 Multiple Library Support
IBM supports multiple tape libraries each with its own unique name which can
be up to 8 characters long. The CA Dynam/T DTLIB option record can be used
to associate a 1 byte library id with the 8 character library name when multiple
libraries are used.
The 2-byte CA Dynam/T OWNERID can be used to specify both the library id
and the scratch poolid by setting MODON=23 ON in the CA Dynam/T system
option record. The first byte of the CA Dynam/T OWNERID is used to specify
the library id. The only valid characters are 0 (zero) through 9 and letters A
through Z. The second byte of the CA Dynam/T OWNERID is used to specify
the scratch poolid. The only valid characters are 0 (zero) through 9 and letters
A through F, where A = 10, B = 11, C = 12, D = 13, E = 14, and F = 15. A CA
Dynam/T OWNERID of FF translates to a library id of F and a scratch poolid of
SCRATCH15.
IF MODON=23 is OFF, all LBSERV calls set the library name to BLANKS (X40)
so that the default library name is always accessed even if two or more
libraries are defined in the IBM robot system.
Forcing a Re-Scan of the IBM 3494 Tape Drives
Before the first CA Dynam/T tape mount is requested, either the IBM LCDD
partition or the IBM VGS server machine must be running. If neither is
running, the CA Dynam/T table that holds all the tape drive addresses of the
IBM tape robot system will be 0 (zero), and you cannot access the IBM tape
robot system using CA Dynam/T.
If you cannot access the IBM tape robot system and either the IBM LCDD
partition or the IBM VGS server machine is running, try reloading phase
CATNLOG0. This forces CA Dynam/T to scan the IBM robot system and update
an internal table with all the tape drive addresses found in the IBM tape robot
system.
Use the following JCL to reload CATNLOG0:
// JOB RELOAD
// UPSI 01
// EXEC CASAUTIL
RELOAD CATNLOG0
/*

Note: The IBM LCDD or the IBM VGS VM service machine must be active
before the reload is executed.
Using CA Dynam/T MODON 11, 22, and 23 with the IBM Robot System
The following table illustrates the MODON settings required for each type of
server:
--------- DYNAM/T ---------

MODON MODON MODON
11 22 23
IBM LCDD ON OFF OPTIONAL

IBM VGS Server ON ON OPTIONAL
CA Dynam/T VM Server OFF OFF OFF
If MODON 23 is OFF, only one library in the IBM 3494 robot system is
recognized. If MODON 23 is ON, more than one library in the IBM 3494 robot
system is recognized.
TDYNIBM, a synchronization program, is provided which reads the CA

Dynam/T catalog sequentially and sends requests to the IBM 3494 library to
update the volume status of any volume with a different status than that
found in the catalog. Two commands are currently supported by TDYNIBM:
SYNC FIRSTVOL=nnnnnn LASTVOL=nnnnnn OWNER=xx

EJECT FIRSTVOL=nnnnnn LASTVOL=nnnnnn OWNER=xx
SYNC and EJECT Commands
SYNC Command Synchronizes the 3494 Tape library with the CA Dynam catalog. The
synchronization can be limited by specifying first and last volumes and by
specifying a specific owner of the data set. The default is to synchronize all
volumes and owner ids. The format for the SYNC command follows:
SYNC [FIRSTVOL=xxxxxx LASTVOL=xxxxxx OWNER=xx]
EJECT Command The EJECT command can be used to read a CAIEXTR file created by TDYNVLT
MOVEMENT EXTRACT to eject all volumes from the 3494 that are moved out of
vault A. As with the SYNC command, the EJECT command can be limited to a
range of volsers, a specific owner id, or both. The format for the EJECT
command follows:
EJECT [FIRSTVOL=xxxxxx LASTVOL=xxxxxx OWNER=xx]
In conjunction with MODON=23, OWNER=x* can be specified on both the

SYNC and EJECT commands to limit the processing to one library at a time.
For example, SYNC OWNER=A* only synchronizes volumes in library A.
3–54 User Guide

IBM Virtual Tape Facility (VTAPE) Support

The IBM Virtual Tape Facility (VTAPE) allows tape data to reside either in a
VSAM file or on a remote system such as Linux, UNIX, or Windows. The VTAPE
command is used to communicate with the Virtual Tape Facility to start and
stop Virtual Tape support.
IBM VTAPE Command Format
The IBM VTAPE command has the following format:
VTAPE START,UNIT=cuu,LOC=ipaddress:portnumber,FILE='filename',WRITE
VSAM SCRATCH
READ
VTAPE STOP,UNIT=cuu
Note: Up to three FILE= parameters can be specified, each of which can be up

to 100 bytes in length.
Overview of CA Dynam/T Support of VTAPE
Users can use CA Dynam/T to control input and output processing of VTAPE
files. Additionally, VTAPE information can be maintained in the Catalog file and
VTAPE volumes are indicated in reports.
Input Processing
For input processing of VTAPE files, users can specify a data set name using
the DSN=data set name parameter on the VTAPE command instead of
specifying the LOC and FILE parameters.
Example:
VTAPE START,UNIT=cuu,DSN=’dataset’
When the DSN parameter is specified on the VTAPE START command, CA

Dynam/T checks the catalog at job exit time and, if the VTAPE information
exists in the catalog for the volume the appropriate LOC and FILE parameters
are substituted on the VTAPE command. If the VTAPE information or data set
name does not exist in the catalog, an error message is issued.

Versions other than the most current can be specified on the DSN=data set
name parameter:
A relative version can be accessed by appending .(-nn) to the data set

name. For example,
DSN='TAPE.(-2)'
An absolute version can be accessed by appending ,G=nn to the data set

name. For example,
DSN='TAPE,G=3'
Output Processing
The full IBM VTAPE command must be specified for output processing. CA
Dynam/T saves the specified VTAPE information at Job Control time. The
VTAPE information is then stored in the catalog and associated with the
volume being created at open output time for controlled tapes.
CUU Assignment The VTAPE CUU must be pre-assigned for both controlled and uncontrolled
output tapes. CA Dynam/T does not allow the operator to assign a VTAPE
CUU when responding to a mount message.
However, CA Dynam/T will AVR the VTAPE and dynamically make the
assignment, if a specific volume is requested for output in any of the following
situations:
Other than file one of a multifile set
A cycle controlled volume
DISP=OLD processing
Catalog Information, Panels, and Reports
VTAPE versions can be added manually to the catalog using the DYNCAT ADD
command by specifying the VTAPLOC and VTAPFILE parameters. For more
information about using the DYNCAT ADD command for VTAPE support, see
ADD Command in the chapter “Maintaining the Catalog—DYNCAT Program.”
VTAPE volumes are denoted by a (V) appended to the volser for most online
panels and batch reports.
3–56 User Guide

CA Dynam/T Enhanced Support for Virtual Tapes
CA Dynam/T automatically mounts both input and output virtual tapes.

Currently IBM’s VTAPE and Fundamental Software’s FakeTape virtual tapes are
supported. CA Dynam/T VTAPE support requires z/VSE 3.1 or higher. The
FakeTape support requires both CA Dynam/T and FakeTape to be running on a
Flex-ES system.
If a CA Dynam/T controlled data set is written to a VTAPE, CA Dynam/T

automatically issues the required VTAPE START command when the file is
opened and issues a VTAPE STOP command when the file is closed. If the
data set is written to a FakeTape, CA Dynam/T issues a special mount CCW
that invokes FakeTape to mount the requested tape.
Define Virtual CUUs
To use the automatic virtual tape support, a list of virtual CUUs must be
defined to CA Dynam/T for use when mounting virtual volumes. The system
option record DTVIRT was created for this purpose. It can be defined and
maintained online using CUI, or in batch using program CACCDBU0. The CUUs
defined must be added as cartridge devices in the VSE IPL procedures.
An example ADD statement would be: ADD CA2:CA4,3480
The CUUs must be in a DVCUP status. No real devices can use any of the
defined virtual CUU addresses.
Define Default File Name and Location
A default VTAPE file name and location also can be defined in the DTVIRT
system option record. This default is the file name and location passed on the
VTAPE START command if no virtual tape information is defined for the
selected virtual scratch tape. For instructions on defining virtual scratch tapes,
see the DYNCAT SCRPOOL command.
A default FakeTape file name also can be defined in the DTVIRT option record.
All VTAPE and FakeTape file names must contain the volser somewhere within
the file name, thus ensuring all virtual file names are unique. The default
VTAPE/FakeTape file name must contain the literal VOLSER. When using the
default file name, CA Dynam/T substitutes the actual volser in place of the
literal VOLSER. For example, if the default file name chosen is
CA DYNAM/T.VOLSER, when volume CA0001 is written for output, and no
overriding file name is defined for the volume, the file name passed on the
VTAPE START command or in the FakeTape CCW would be
CA DYNAM/T.CA0001.

Normally, CA Dynam/T scans all available tape drives searching for a scratch
tape to use when creating a data set on a real tape. Unlike real tapes, when a
virtual tape is requested for output, CA Dynam/T must search the Dynam
catalog for an appropriate virtual volser to specify on either the VTAPE START
command or in the special FakeTape mount CCW request. If a volume is to be
selected by CA Dynam/T for use as a virtual volume, the volser must be
defined in the Dynam catalog as a virtual scratch tape.
Define Virtual Volumes
The DYNCAT SCRPOOL command is used to define virtual volumes in the

catalog. Specifying either the VIRTAPE=VTAPE/FTAPE parameter, or the
VTAPLOC=‘location’ and VTAPFILE=‘filename’ parameters on the SCRPOOL
command, will define the volumes as virtual scratch tapes. The VTAPLOC and
VTAPFILE parameters must be specified together and are mutually exclusive
with the VIRTAPE parameter. The VTAPLOC and VTAPFILE parameters define
the location and file name where the file is to be created. This virtual tape
information is stored in the catalog when the SCRPOOL command is processed.
If a VTAPE volume is being defined, specify VTAPLOC=‘VSAM’ or
VTAPLOC=‘ipaddress:portnumber’. If a FakeTape volume is being defined,
specify VTAPLOC=‘FTAPE’.
If VIRTAPE=FTAPE or VIRTAPE=VTAPE is specified on the SCRPOOL command,

the default file name and location defined in the DTVIRT option record will be
passed on the VTAPE START command or in the FakeTape CCW when the
data set is opened.
The virtual tape information associated with a volume remains intact unless
the volume is deleted from the catalog, or if a SCRPOOL command is issued
with new virtual tape information specified. The virtual tape information
remains associated with the volume even after the virtual volume is scratched.
Virtual tape volumes do not need to be pre-initialized. CA Dynam/T writes the

VOL1 and HDR1 labels the first time the virtual volume is used to create an
output file.
If a particular data set should always be created on a virtual volume, specify

VIRTAPE=FTAPE or VIRTAPE=VTAPE on the DYNCAT DEFINE or ALTER
command. To create a controlled version on a virtual tape on an as-needed
basis, specify the TLBL option VT for a VTAPE, or FT for a FakeTape. Specifying
the TLBL option causes a virtual tape to be created regardless of the VIRTAPE
specification for the data set.
3–58 User Guide

If CA Dynam/T automatically creates a virtual tape, the logical unit must be

unassigned when a single file or the first file of a multi-file set is opened. If the
logical unit is preassigned, message CADT107D is issued. At that point, the
operator can either release the assignment by replying 'REL' to the CADT107D
message or cancel the job. The only time the logical unit can be preassigned is
if other than file one of a multi-file set is being opened and the previous file
used the HOLD option. See the section entitled "IBM limitation when writing to
VSAM Virtual Tapes" for more information and an example on how to create
multi-file VSAM VTAPE files.
Precautions for Virtual Tapes
The following precautions need to be taken when using virtual tapes:

Due to a conflict between the JCLIF macro interface and POWER, do not
create or read POFFLOAD tapes using the automatic VTAPE interface.
To prevent simultaneous use, CA Dynam/T locks virtual CUUs. An internal

method of locking is used, which requires no additional setup or options to
be set. To unlock a virtual CUU that remains locked due to cancellation or
abnormal termination of a job, use the new AR command DT READY
VCUU=cuu. The AR command DT STATUS shows NOT AVRABLE next to
any virtual CUU currently in locked status.
To reduce the amount of I/O when searching the catalog for an eligible
virtual scratch tape, specify the VOLID parameter for data sets that are to
be written to virtual tapes. If a data set is defined with a VOLID, CA
Dynam/T performs a generic search looking only for volumes where the
first two characters match the specified VOLID. For example, if there are
no eligible virtual scratch tapes in the catalog, and no VOLID is specified,
every volume in the catalog will be accessed. However, if a VOLID is
specified, then only the volumes whose first two characters match the
VOLID will be accessed. Using the VOLID parameter limits searches only to
virtual volumes, thus reducing unnecessary catalog I/O.
To use VSAM and FakeTape files as virtual tapes, you must define them
before they can be used by CA Dynam/T. For details about defining files to
be used as virtual tapes, see IBM or FakeTape documentation.
Example
The following is an example of how to create and read a VTAPE that will reside
in a VSAM file:
* $$ JOB JNM=VTAPE,CLASS=0,DISP=D
// JOB VTAPE CREATE VIRTUAL TAPE FILE
* STEP 1 - DEFINE VTAPE VSAM CLUSTER
// EXEC IDCAMS,SIZE=AUTO
DELETE (VTAPE.FILE) PURGE CL -
CATALOG(VSAM.USER.CATALOG)
DEFINE CLUSTER (NAME(VTAPE.FILE) -

RECORDS (5 5) -
TO (99366) -
REUSE -
NONINDEXED -
SHAREOPTIONS (1) -
SPANNED -
RECORDSIZE (32758 32758) -
VOLUMES (WORK01)) -
DATA (NAME(VTAPE.FILE.@D@) -
CISZ (32768)) -
CATALOG (VSAM.USER.CATALOG)
/*
* STEP 2 - ADD LABEL FOR VSAM VTAPE FILE
// OPTION STDLABEL=DELETE
VT0001
/*
// OPTION STDLABEL=ADD
// DLBL VT0001,'VTAPE.FILE',99/366,VSAM,CAT=IJSYSUC
/*
* STEP 3 - DEFINE DATASET AND VIRTUAL SCRATCH TAPE TO DYNAM CATALOG
// EXEC DYNCAT
DEF 'VTAPE.DATASET' TAPE VIRTAPE=VTAPE VOLID=VT
SCRPOOL VOL=VT0001 VTAPLOC='VSAM' VTAPFILE='VOLSER'
/*
* STEP 4 - CREATE VIRTUAL TAPE
// TLBL SDDLBL,'VTAPE.DATASET'
// UPSI 10000010
// EXEC DYNTEST
50
/*
* STEP 5 - READ VIRTUAL TAPE
// TLBL SDDLBL,'VTAPE.DATASET'
// UPSI 01000000
// EXEC DYNTEST
/*
/&
$$ EOJ
Note: If the VTAPE is a VSAM file, the maximum length of the VTAPE file name
is seven characters; since that is the maximum DLBL name length. Six of the
seven characters must be the volser. In the example above, VT0001 is the
filename passed on the VTAPE START command if virtual scratch tape VT0001
is selected for use.
3–60 User Guide

IBM limitation when writing to VSAM Virtual Tapes
WRITE can only start at the beginning of a VSAM virtual tape. No rewrite or
overwrite of existing data is possible except from the beginning of a tape.
Once a VTAPE STOP command is issued, the remaining buffer contents is
written to tape, the tape is closed, and an end-of-volume (EOV) indicator is
written. This means no further data can be added to the virtual tape after the
VTAPE STOP is issued.
Therefore, in order to create a multi-file VSAM VTAPE all files must be created
using just one VTAPE START and one VTAPE STOP command. To prevent
Dynam/T from automatically issuing the VTAPE STOP command, specify the
HOLD option for each file of the multi-file set. Use the TDYNASN VTSTOP
command to issue the VTAPE STOP command after all the files of the multi-file
set are created.
The following example assumes your virtual tape CUUs have been defined in
the DTVIRT system option record, and that the necessary VSAM files have
been created. The example creates a 3 file unchained multi-file VTAPE set:
// JOB VTAPE
// EXEC DYNCAT
DEF 'TAPE.VTAPE.1' TAPE NGEN=2 VIRTAPE=VTAPE
/*
* CREATE FILE 1
* USE THE HOLD OPTION TO PREVENT AUTOMATIC VTAPE STOP
// TLBL SDDLBL,'TAPE.VTAPE.1,H',,,STACK=A
// UPSI 10000010
// EXEC DYNTEST
50
/*
* CREATE FILE 2
// UPSI 10000010
// EXEC DYNTEST
50
/*
* CREATE FILE 3
// UPSI 10000010
// EXEC DYNTEST
50

/*
* RELEASE ASSIGNMENT AND ISSUE VTAPE STOP COMMAND
// EXEC TDYNASN
VTSTOP SYS004
/*
/&
3–62 User Guide

Chapter 4: Disk File Management
CA Dynam/D is a software system providing disk data set management for
IBM and compatible mainframe computers operating under all releases of VSE
currently supported by IBM. This chapter deals with the basic components of
CA Dynam/D. For more information about using the utilities that support disk
management, see the chapter "Supporting Disk File Management."
CA Dynam/D provides the following benefits:
Basic disk space management
Catalog management
Device independence shared DASD for multiple CPU support
Disk pool management
BACKUP/RESTORE utility
VTOC management with support for both indexed and nonindexed VTOCs
Disk space management is the dynamic allocation of disk space on a specified

disk volume. You specify the amount of space required for a file, and
CA Dynam/D automatically finds the available disk space and allocates it.
CA Dynam/D also releases unused disk space when the file is closed.
Catalog Management is the CA Dynam facility for accessing a file using only
the file ID supplied through VSE Job Control. With the CA Dynam Catalog
Management facility, you can define or alter the allocation attributes of disk
files without modifying JCL statements. This provides more power and
flexibility in controlling DASD file attributes.
Disk pool management lets you specify a pool of disk volumes to be used for
disk space allocation. It also provides for a balanced allocation of space across
multiple disk volumes.
With the CA Dynam/D DYNUTIL program, you can save and restore any DASD
file to and from tape.
Shared DASD for multiple CPUs enables you to share disk space allocations
from among multiple CPUs. Each CPU may or may not have CA Dynam/D
processing and accessing a common disk pack.
Chapter 4: Disk File Management 4–1

Basic Components
The enhanced VTOC management facility improves upon VSE VTOC

management in the following areas:
Rotational position sensing (RPS) is used on CKD devices, reducing

channel busy time.
Software position maintenance is used on FBA devices to eliminate

redundant VTOC I/O.
VTOC indexes can be built on DASD volumes as desired. These indexes are
used to even further reduce VTOC I/O and channel busy time.
CA Dynam/D requires no modifications to the supervisor or its components. Its

front-end processors are invoked before calling the unmodified IBM
OPEN/CLOSE transient programs.
Basic Components
To effectively use CA Dynam/D, you must understand the following basic
components of the system:
Disk space allocation
Catalog management
VTOC management
These components form the nucleus of CA Dynam/D and direct you to other
facilities available in the system. For example, if you want CA Dynam/D to
control disk file management and to distribute the allocation of disk space
across several disk volumes, utilize disk pool management.
Details for using the CA Dynam/D system effectively are supplied in this
chapter.
Allocate Disk Space
This section describes how to allocate disk space using CA Dynam/D.
Primary Disk Space
CA Dynam/D is designed to control and allocate disk space for the VSE user.
The user can request space to be allocated by CA Dynam/D in one of two
ways, depending on whether a file is defined in the CA Dynam Catalog.
4–2 User Guide

Basic Components
To request space for a file not defined in the Catalog, use an EXTENT Job
Control statement. Indicate in that statement a relative track (or block) value
of 1 or the value specified for TRIGGER in the DYNAM/D option record. The
trigger indicates that CA Dynam/D should allocate the file.
For example,
// JOB SINGLE EXTENT EXAMPLE

// DLBL SDDOUT,'DISK.FILE',2099/360
// EXTENT SYS006,POOL01,1,0,1,8
// EXEC PROGRAM
CADD002I ALLOCATED FILE=SDDOUT SYS006=202 SYSWK1 X=0/12/8
Note: Relative track value = 1 and number of tracks to allocate = 8
CA Dynam/D does not allocate any EXTENT not defined with the TRIGGER
value from the DYNAM/D option record. Instead, the requested EXTENT is
passed directly to the standard operating system OPEN routine.
A Job Control exit is provided with CA Dynam/D. This exit will automatically
change the EXTENT statements in any supplied Job Control stream to force
dynamic allocation.
For a file defined in the CA Dynam Catalog File, the EXTENT statement is
omitted; space is allocated based on the specification in the Catalog entry for
that file.
For example,
// JOB GENERATE FILE FROM CATALOG

// DLBL SDDOUT,'DISK.FILE'
// EXEC PROGRAM
CADD002I ALLOCATED FILE=SDDOUT SYS001=202 DOSVS2 X=0/6/8
CADD022I RELEASED 00008 TRACKS FILE=SDDOUT VOL=SYSWK1
Note that the disk file can be defined in the Catalog with a specific number of
tracks (CKD devices), blocks (FBA devices), cylinders, or records (logical
allocation).
If a number of records is defined, CA Dynam/D will calculate the correct

number of tracks or blocks for the allocation based upon the blocking factor in
use and the device type.
If a number of cylinders is defined, CA Dynam/D will allocate the requested

number of cylinders or cylinder equivalents on the allocated device type.

Basic Components
Disk Space Availability
CA Dynam/D allocates disk space for files at OPEN time by searching the
specified disk volumes for available contiguous space. CA Dynam/D considers
disk space to be available on a volume when one of the following conditions
prevails:
Disk space is unused
Disk space is occupied by a file whose expiration date is less than the
current date
Files with an expiration date equal to the current date (0 retention days) are
considered unexpired by CA Dynam/D. The disk space occupied by these files
will not be released by CA Dynam/D until the following day (after midnight of
the day when the file was created).
Note: For FBA allocations, CA Dynam/D rounds all user allocation requests up
to an even multiple of 8 physical blocks for optimum performance. If, for
example, 7 blocks are requested either through JCL or the Catalog, 8 blocks
are allocated by CA Dynam/D.
Secondary Disk Space
Secondary disk space allocation lets you automatically acquire disk space
during program execution whenever the original EXTENT of a sequential disk
(SD) file is filled. This eliminates the problem of allocating a single large,
contiguous area of disk space big enough for a maximal amount of data.
This capability is important for files which vary in size from one job execution
to another. The allocated disk space can grow according to the file size.
You can define secondary space for a file in several ways. Firstly, you can use
Automatic Secondary Allocation. In this way, you define only the size of the
primary allocation. If secondary allocations are required, they are generated
based upon constants defined to the system using the DYNAM/D option record.
Secondly, for complete control over all the allocations permitted for a file, on a
file-by-file basis, define the following:
Size of the primary allocation
Size of the secondary allocation to be used if needed
Number of desired secondary allocations
These definitions can be specified either with EXTENT statements, or in the

Catalog entry. To use each of the methods, see the examples that follow.
4–4 User Guide

Basic Components
We recommend using Automatic Secondary Allocation, because it enhances

both performance and reliability. Performance is improved because with
Automatic Secondary Allocation active, CA Dynam/D generates only two
labels. Reliability is improved because all extents of a multi-extent input file
are found and read even if there are more of them than the number of EXTENT
statements in the JCL.
Examples
Following are three examples of defining files to the Catalog. For more
information, see the chapter "Maintaining the Catalog—DYNCAT Program."
Method One Defining the file in the CA Dynam Catalog with a primary allocation only, and
allowing automatic secondary allocation to provide secondary extents. The
example assumes that the DYNAM/D option record has ASAAMT(30) (30%
primary allocation can be used for secondary allocation) and ASAMAX(3)
(maximum of 3 secondary allocations).
DISK.FILE is defined to the Catalog with 10 tracks for primary allocation, of

which 30% percent (3 tracks) is allowed for secondary allocation.
// JOB DEFINE ALLOCATION

// EXEC DYNCAT
DEFINE 'DISK.FILE' ALLOC=(SYSWK1,TRK,10)
/*
/&
// JOB USE FILE
// EXEC PROGRAM
Automatic Secondary Allocation (ASA) works in the same fashion from JCL
(that is, supply only one extent). Certain restrictions apply to using ASA for
files which are opened and closed multiple times in the same program. For
these files, if a generic volume serial number is used (for example, WORK**),
it is only effective for the first open which uses the label record.
Subsequent opens will use the resolved volume serial number where the file
was actually accessed or created (possibly WORK01). ASA is not supported for
SD TYPE=WORK files (compiler work files, FORTRAN disk files, and so on), or
ISAM or DA files.

Basic Components
Method Two Submitting multiple EXTENT statements, all with a relative track equal to the
trigger value defined in the DYNAM/D option record for a file. For example:
// JOB MULTIPLE EXTENTS EXAMPLE

// DLBL SDDOUT,'DISK.FILE',,SD
// EXEC DYNGENR
Note that the secondary extents will only be used if the primary extent is
filled.
Method Three First defining a file in the CA Dynam Catalog as eligible for secondary
allocation, and then supplying a DLBL statement with no EXTENT statements.
In the following example, DISK.FILE is defined to the Catalog with 10 tracks
for primary allocation, 5 tracks for each secondary allocation, and a maximum
of 3 secondary allocations.
// JOB DEFINE ALLOCATION

// EXEC DYNCAT
DEFINE 'DISK.FILE' ALLOC=(SYSWK1,TRK,10,5,3)
/*
/&
// JOB USE FILE
// EXEC PROGRAM
Catalog File
The Catalog File, shared by all CA Dynam software components, is used by CA

Dynam/D to gather and maintain vital information relating to disk files and the
space they occupy. It provides CA Dynam/D with the information needed to
allocate disk space for a file, to maintain the latest disk volume location, and
to maintain various usage statistics relating to a file.
4–6 User Guide

Basic Components
Some of the disk file characteristics you can specify in the Catalog File include
the following:
Number of tracks for primary and secondary allocation
Disk volumes to be used for space allocation
Disk volumes on which the file currently resides
Expiration, retention dates, or both
Option or disposition codes for a file
Password for a file
Generation data set definition
File creation and usage statistics
The Catalog File acts as the central source of information which CA Dynam/D
uses when creating and accessing disk files. In this way, all the information
relating to user disk files can be organized in one central location to provide
secure and efficient disk file processing.
Catalog Management
With the Catalog Management Facility of CA Dynam/D, you can easily control
DASD file allocation and access.
These components are provided to enable you to perform the following:
Create a Catalog file.
Define, alter, and delete entries in the Catalog.
Display the attributes of files defined in the Catalog.
BACKUP/RESTORE the Catalog File using a tape device.
A file defined in the CA Dynam Catalog can be accessed simply by specifying

that file's ID on a DLBL statement and omitting all EXTENT statements. For
example, to access the cataloged file DISK.FILE, use the following JCL:
// JOB ACCESS FILE

// DLBL USER,'DISK.FILE'
// EXEC PROGRAM
/*
The CA Dynam/D system locates the DISK.FILE entry in the Catalog and
creates EXTENT information for it. If the data set is not found in the Catalog,
CA Dynam/D searches all mounted volumes in PUB order to find it.

Basic Components
Overriding Cataloged Expiration Dates
The expiration date defined in a Catalog entry will be used at file creation
time. You can temporarily override it by specifying a new expiration date on
the DLBL statement for that file.
VOLSER Identification
CA Dynam Catalog management identifies the actual VOLSER for each extent
as it is allocated for a file. Using this real VOLSER when the file is opened for
input, the time required to locate the file is reduced, because CA Dynam/D
does not have to scan through a POOL of disk volumes.
Catalog-Controlled Files
CA Dynam/D Catalog-controlled files can be accessed or created through

IDCAMS by including a blank EXTENT statement behind each file's DLBL.
Example,
// DLBL FILEIN,'Catalog.Controlled.File1'
// EXTENT
// DLBL FILEOUT,'Catalog.Controlled.File2'
// EXTENT
// EXEC IDCAMS,SIZE=AUTO
REPRO INFILE (FILEIN ENV(BLKSZ(500),RECFM(FB))) -
OUTFILE (FILEOUT ENV(BLKSZ(5000),RECFM(FB)))
The EXTENT statement with no parameters has the following purposes:
It avoids IDCAMS cancelling during pre-OPEN checking for lack of EXTENT

information.
It signals CA Dynam/D that processing is necessary on behalf of this file so

that when the OPEN is issued by IDCAMS, CA Dynam/D will locate the file
in the CA Dynam Catalog and perform dynamic LUB allocation as
necessary.
Temporary Data Sets
Any data set that is created and deleted within the same job is a temporary
data set. To define a temporary data set, specify a 3—10 character data set
name including the following:
## as a 2-character prefix (pound or hash signs)
8 additional alphanumeric characters
4–8 User Guide

Basic Components
For example,
// DLBL SDDOUT,'##TEMP01'
// EXTENT ,SYS006,POOL01,1,0,1,15
If the data set name is longer than 8 characters, the name will be truncated. A
temporary data set will always be CPU- and partition-dependent. Any
expiration date or retention days specified on the DLBL statement will be
ignored.
Note: A temporary data set can never be catalog-controlled. If no EXTENT

statement is submitted, CA Dynam/D uses the default allocation defined in the
DYNAM/D option record (with DEFALOC).
Logical Units
We recommend that you omit logical unit specifications from JCL for all files
processed under CA Dynam/D control. In regard to Direct Access (DA) files,
the main requirement made by VSE concerns the logical units assigned to
them, if they contain multiple extents or span multiple volumes.
For more information about logical unit assignments in general, and

specifically for DA files, see SYS Number Considerations and Modifying Logical
Unit Assignments (LUBS).
File Type
Restrictions are placed on the file type, especially when EXTENT statements
will be omitted so that allocation information is taken from the Catalog. Either
omit the file type from the DLBL statement, or specify it as SD.
If an ISAM or DA file is defined in the Catalog, the DLBL statement must still
indicate SD. CA Dynam/D will override the SD value to match the file type
specified in a program's DTF. You must follow this convention because VSE Job
Control will only allow a DLBL statement without an EXTENT statement for SD
files.
Example,
// JOB ACCESS CATALOGED DATA SET

// DLBL SDDINP,'DISK.FILE'
// EXEC PROGRAM
CADD028I ACCESSED FILE=SDDINP SYS001=202 SYSWK1 X=0/72/1

Managing the VTOC
Default Allocation Support
You can specify a system default to allocate disk space globally. This default is
specified by the DEFALOC parameter of the DYNAM/D option record, and can
be used to simplify the creation of temporary or test data sets. To create the
default specification, add the DEFALOC parameter to the DYNAM/D option
record, and specify desired allocation information in it. For example:
DEFALOC(POOL01,100)
This sets a default allocation of 100 tracks primary allocation, with automatic
secondary allocation, to be taken from POOL01. To use the system default,
code a bare DLBL with a data set name which does not exist in the catalog; CA
Dynam/D will use the default allocation information to allocate the file.
The same procedure is used to input the file. In this fashion, a programmer
who needs temporary space can get it and use it without coding the EXTENT
information or creating a catalog entry.
// JOB TEST PROGRAM

// DLBL MYFILE,'TEST.FILE',30
// EXEC PROGRAM
/&
The example shown above causes CA Dynam/D to allocate 100 tracks from
POOL01 (the default setting) to TEST.FILE, and sets a retention period of 30
days. At the end of 30 days, the file would be automatically deleted.
Managing the VTOC

A volume table of contents (VTOC) contains entries made up of seven types of
data set control blocks (DSCBs) called format-0, format-1, ..., format-6
records. (The format-6 record is only used by OS systems.) These records
describe the type and location of data sets on a DASD volume.
CA Dynam/D VTOC management provides the following:
Rotational Position Sensing (RPS) for CKD devices, significantly reduces

channel busy time. The VSE VTOC management routines do not use RPS.
A software technique for position maintenance on FBA devices, eliminates

redundant reads of VTOC control intervals.
VTOC indexes built on selected volumes and used for processing both
dynamic and nondynamic files, greatly reduce VTOC I/Os and channel
busy time.
4–10 User Guide

Managing the VTOC
VTOC Indexes
A VTOC index is a separate data set on a volume. Each index record identifies
a data set residing on the volume, with a pointer to the DSCB for that file. This
allows direct access by data set name, without resource-consuming scans. To
locate the file, the VTOC index is read into storage, and the search for the data
set name is made there.
To locate a data set by data set name in a nonindexed VTOC, it is necessary to

sequentially scan DSCBs on the device. This scan involves use of the channel,
the DASD control unit, and the device itself.
The VTOC is open for shorter periods of time, allowing more

multiprogramming and multi-CPU activity to progress in a given period of
time, because the processing of an indexed VTOC is streamlined. In short,
system throughput is significantly enhanced, whether DASD files are controlled
by CA Dynam/D.
Processing the VTOC
Depending on whether a volume has a VTOC index, the VTOC itself is

maintained in native IBM format, and can be processed by any IBM operating
system. If a volume has a VTOC index, however, all systems updating the
VTOC must also be running CA Dynam VTOC management.
A VTOC is normally initialized using the IBM utility, ICKDSF. This program also
can build a VTOC index for the OS user. CA Dynam, while able to process a
VTOC built with ICKDSF, cannot process a VTOC index built with this utility. If
a VTOC index is built this way, it will be ignored. (For more information about
the program ICKDSF, see the IBM publication Device Support Facilities User's
Guide and Reference.)
Building the VTOC Index
A CA Dynam VTOC index is built using the CA Dynam utility, DYNCAT.

Thereafter, each call to the VSE VTOC management routines is processed
through the VTOC index.

Managing the VTOC
Searching the VTOC
A request for a format-1 record would normally result in a hardware search

(on CKD devices) of the entire VTOC, or a sequential reading (on FBA devices)
of the VTOC.
With the presence of a VTOC index, the following search method is used:
Looking up the data set name in the VTOC index (usually a single I/O)
Reading the format-1 record directly from the VTOC (a single, short I/O)
Thus the channel is freed for other work, and I/O to the VTOC is minimized.
The index to the VTOC is built as a prefix-balanced tree structure. A balanced

tree structure is one in which an equal number of index records must be
searched (one record for each index level) for all entries in the index. A prefix-
balanced tree, or prefix B-tree, is a balanced tree in which common portions of
keys (in this case, data set names) are stored only on higher index levels,
conserving space on lower levels.
A VTOC index also contains a record of all space on the volume, depending on
whether it is occupied. This information is used to allocate new data sets and
check for overlapping extents, greatly reducing the time (and resources) spent
performing these functions.
Creating New VTOC Records
When a new VTOC record is to be created, a free (format-0) VTOC record must
be found. This operation is usually similar to the format-1 record lookup
described above, except that a search is made for a record having a key of
binary zeros. The process is subject to the same problems as the format-1
lookup described above.
In order to alleviate this situation, a VTOC index contains a bit map describing
the VTOC itself. When free VTOC records are required, they are found by
examining the VTOC allocation map, instead of the conventional search.
4–12 User Guide

Managing the VTOC
Deleting Expired Files
When you are processing an allocation request for a volume without a VTOC
index, expired files that were allocated by CA Dynam/D are automatically
deleted.
But automatic deletion is not performed on volumes having VTOC indexes,

because all allocation information is maintained within the VTOC index.
Instead, the indexes are automatically rebuilt each day on or after 8:00 a.m.
Any expired data sets that were allocated by CA Dynam/D are deleted at this
time.
Benchmark tests have shown that the use of indexed VTOCs can significantly
improve performance and overall system throughput, even when used on
DASD volumes not under the control of CA Dynam/D.
Indexed VTOC Processing
CA Dynam-indexed VTOC processing can be used effectively on all CKD

volumes except perhaps volumes which contain only VSAM data spaces. On
FBA devices, VTOC indexes should be used only if there are more than 200
files on the volume. Increase the VTOC CISIZE to 4K or 8K to improve
performance on FBA volumes with fewer than 200 files.
To use VTOC indexes, all systems must be running VSE r2 and above. If
volumes having VTOC indexes are to be updated by more than one CPU, all
updating systems must be running CA Dynam VTOC management. For more
information about how to define and initialize VTOC indexes, see the DYNCAT
VTOC command in the chapter "Maintaining the Catalog DYNCAT Program."
CA Dynam/D VTOC management is similar in concept to the OS Data Facility

Device Support VTOC management. For more information, see the IBM
publication, Data Facility Device Support: General Information.

Defining File ID Option Codes

You can specify one-character file ID option codes as part of the JCL's DLBL
statement to indicate the disposition of a file. Option codes must be the last
field specified in the file ID and must be enclosed within parentheses. Multiple
option codes can be entered in any sequence within the parentheses, but must
be separated by commas as follows:
Format:
// DLBL filename,'file-id(option codes)',...
Example,
// DLBL FNAME,'DISK.FILE(A,B,C)'
CA Dynam/D eliminates the option codes and the parentheses from the file ID
before passing the file to IBM OPEN (this occurs for both CA Dynam/D and
non-CA Dynam/D controlled files).
Syntax Conventions
Syntax conventions are listed below:
Separate option codes with a comma.
Allow no intervening blank spaces.
Enclose option codes within parentheses.
Any syntax error found causes all option codes to be ignored.
The file ID cannot be greater than 59 characters, including the option code
characters.
Common Syntax Errors
If CA Dynam/D encounters a syntax error while processing the option codes,

the parentheses and option codes are not eliminated from the file ID; CA
Dynam/D treats it as part of the file ID. Some examples of syntax errors
follow:
Extra comma between option codes
// DLBL FN,'FILE(S,,A)'
Missing comma between option codes
// DLBL FN,'FILE(BCD)'
4–14 User Guide

The following list describes the file ID option codes you can specify on the
DLBL statement.
A Align on cylinder boundary
Dynamically allocated area must be on a cylinder boundary. ALIGN is the

default setting only for ISAM prime EXTENT files.
B Bypass AVR
Causes AVR to be bypassed for a specified file. DASD device-independence is

also bypassed.
C Catalog data set
Catalogs a data set. Remember that C is not a default option and must be
specified in order to catalog a data set from Job Control.
Note that only CA Dynam/D-controlled files (relative starting track containing

the trigger value) can be cataloged using the C code.
D Delete file at input CLOSE
Deletes the VTOC entry when closing an input SD (sequential disk), ISAM
(indexed sequential), or a DA (Direct Access) file.
Note that D is not the default and must be specified for deletion to take place.
The D option applies only to CA Dynam/D-controlled files.
DL Delete the incore label for the file at close.
D1 Diagnostic trace
Traces CA Dynam/D's internal activities in processing a disk file. For more

information, see the Programming Guide.
E Enqueue File
The E option is used to enqueue files opened for input, update or output. This
file, once opened, cannot be accessed by any other job which executes in the
system or in other systems sharing the same IBM Lock file. When an
enqueued file is closed, it becomes accessible to other programs. The enqueue
facility is available to CA Dynam/D users with or without Catalog Management
support.
Note that the E option applies to both CA Dynam/D-controlled and

noncontrolled files. The E option must be specified for all files where enqueue
validation/processing is desired. If omitted, it is possible to successfully access
a file which is currently enqueued by another program.

F Fragment allocation
This option code can be specified to force CA Dynam/D to fragment space

allocation for the file. When this option is specified and the requested amount
of DASD space is not available on the specified volume, the largest piece of
contiguous space is allocated to the data set.
If the DASD space becomes full, the user must have supplied additional extent
definitions or must have the automatic secondary allocation facility available.
Otherwise, the job will be canceled with the IBM NO MORE AVAILABLE
EXTENTS message. Note that there is no minimum space limit for the
allocation.
The largest amount of free space available on the volume will be allocated,
regardless of how small it is. If the specified volume is a CA Dynam/D pool,
the space will be allocated from the first pool volume containing free space.
If, for example, the second volume defined in the pool had enough free space
to allocate the complete request, but the first volume contained only half the
requested amount of free space, the extent would be allocated from the first
volume.
G#nn Generational number
This option requests access to the file version whose generation number,
assigned in the catalog at file creation time, is specified here. For example,
To reference the first version created, specify G#01.
To reference the second version, specify G#02.
G-nn Relative generation number
Requests access to the file version relative to the most current one, which is
designated as version G-0. Specifying option code G-0 would access the most
current version; G-1 accesses the next most current one. For example,
To reference the most current version, specify G-0.
To reference the next oldest version, specify G-1.
Gen=nnn This option requests access to the absolute generation number assigned when
the version is created.
I Informative messages to SYSLST
Indicates that CA Dynam/D informative messages are to be directed to

SYSLST. Note that, if informative messages are not requested at the time CA
Dynam/D is installed, then the option code I must be specified in order to
obtain these messages on SYSLST.
4–16 User Guide

IE ISAM extend
Indicate ISE DLBL function for catalog-controlled files.
JX Causes a controlled file to be deleted at end of job after the file is processed.
If JX is specified for an input file and the job step abnormally terminates, the
file is not deleted and the job can be rerun.
K Keep SD file
The K option causes the sequential disk file to be kept after closing the file,
even when the user program indicates deletion of the file. The K option, if
specified for sort work files, prevents CA Dynam/D from deleting the file. The
purpose of this option is to override any specification to delete a file.
L Locked file
Data set is locked for read-only usage. If L is not specified, then the file will
not be locked. The L option applies to both CA Dynam/D-controlled and
noncontrolled files.
M Messages to SYSLOG
Indicates that informative messages produced by CA Dynam/D are to be

directed to SYSLOG. Note that, if informative messages are not requested at
the time CA Dynam/D is installed, then the option code M must be specified in
order to obtain these messages on SYSLOG.
N No truncate at CLOSE
Inhibits truncation of SD files at CLOSE time. Overrides the default option of

automatic truncation of SD files. The truncation facility applies only to CA
Dynam/D-controlled files.
NA No automatic secondary allocation
Prevents automatic secondary allocation for this file. Unnecessary if more than
one allocation is already defined.
NF No fragmentation
The NF option code unconditionally prevents fragmentation or minimum

percentage space allocation for the file.

O Old file
Enables the user to access existing SD files and open the file without
reallocating the file. The O option causes CA Dynam/D to search for the
specified file in the VTOC and use the existing EXTENT information. This option
is not a default option and cannot be used with files controlled using automatic
secondary allocation.
The P option prohibits the use of dynamic LUB allocation for a file. The default
is to allow dynamic LUB allocation with the following exceptions:
System work file (files beginning IJSYS)
System logical units (for example, SYSRDR, SYSIPT, SYSLST, and so on)
DA (direct access) files having more than one extent
The files described above are always prohibited from dynamic LUB allocation.
S Same space for SORTIN and SORTOUT
This option is useful for conserving space during SORT or MERGE runs. When a
SORTOUT file is opened, it is assigned the same area defined for the SORTIN1
file. In this way, the SORT input and output files occupy the same area.
Note that S is not the default.
The S code should be specified on the DLBL statement for SORTOUT, and the
file IDs specified on the DLBL for SORTIN1 and SORTOUT must be identical.
Note that option code S causes CA Dynam/D to search for the specified file in
the VTOC. If the file cannot be found, an error message will be issued and the
job will cancel.
The S code applies only to CA Dynam/D-controlled files (relative starting track

equal to trigger value).
Note: Option S will be ignored when using CA SORT, the CA Sort/Merge

software product. CA SORT does not open its SORTOUT file until the SORTIN
files have been closed.
S:nnn SYS number override
The S:nnn option is used to override the logical unit defined in the program's
DTF, in the Catalog, or both. It is rarely used because CA Dynam/D allocates
an available SYS number at OPEN time.
4–18 User Guide

SX Causes a controlled file to be deleted at the end of a step after the file is
processed.
If SX is specified for an input file and the job step abnormally terminates, the
file is not deleted and the job can be rerun.
T Truncate ISAM prime EXTENT or SD work file
The T option causes the ISAM (LOAD) prime EXTENT or SD work file to be
truncated. The T code is not a default option. This option applies only to CA
Dynam/D-controlled files.
W Delete SORTWK files at CLOSE of this file
The W option is valid only on a DLBL statement and instructs CA Dynam/D to

delete currently open SORTWK files when the file containing the W option is
closed. (This option has no meaning for CA SORT users, because CA SORT's
work file is always deleted by CA Dynam/D.)
X Delete file at input or output CLOSE
The X option causes a file to be deleted from the VTOC whenever it is closed
(for input or output).
Examples
The following examples illustrate the use of various CA Dynam/D option codes.
// JOB OPTION CODE EXAMPLE 1

* ALIGN OPTION CODE
// DLBL SDDOUT,'DISK.FILE (A,I)',2099/360
// EXEC PROGRAM


* DELETE OPTION CODE
* GENERATE FILE TO TEST DELETE
// DLBL SDDOUT,'DISK.FILE (D,I)',2099/360
// EXEC PROGRAM


* NOW DELETE SHOULD WORK

Controlling Generation Data Sets
// DLBL SDDINP,'DISK.FILE (D,I)'

// DLBL SDDOUT,'TEMP.FILE (I)',1,SD
// EXEC PROGRAM

CADD028I ACCESSED FILE=SDDINP SYS005=201 SYSWK1 X=0/3/1
CADD003I AUTO-DELETE VOL=SYSWK1 FILE=SDDINP FILE-ID=DISK.FILE

* TRUNCATE ISAM OPTION CODE
// DLBL ISMOUT,'ISAM.FILE (T,I)',12,ISC
// EXEC PROGRAM
CADD002I ALLOCATED FILE=ISMOUT SYS006=202 SYSWK2 X=1/1/3
CADD022I RELEASED 19 TRACKS FILE=ISMOUT VOL=SYSWK1

By controlling generation data sets, CA Dynam/D lets you maintain multiple
versions of the same file. For example, you may wish to create a disk file
containing order data each day, and at the same time, process the order data
created the previous day. Under normal VSE operation, this would require
renaming or copying the previous day's file before the creation of the new file.
Another example would be to keep a disk file created the first business day of
each month or to keep a disk file created the first day of each fiscal quarter.
These types of multiple data set versions are called generation data sets.
Defining Generation Data Sets
With CA Dynam/D, you need only define the file in the CA Dynam/D Catalog as
a generation data set and specify the number of generations to be available.
When CA Dynam/D is called to open a generation-type data set as output, the
current generation number is incremented by 1, creating a new generation
number for that output. Keep in mind that this is the file's generation number.
4–20 User Guide

Generation numbers defined by G#nn are put in the last four bytes of the file
ID within the disk's VTOC. So, do not use positions 41—44 of the file ID when
defining the data set to the Catalog. The generation number, which can range
from 1—99 (with full wraparound), is entered in the following format:
G#nn
where nn is the generation number
Example,
'PAY.MASTER.FILE.........................G#15'
CA Dynam 7.1 data sets can also be defined by appending .G#nnnnn to the
end of the data set name by defining the data set with GDGLONG=YES. An
input version from either format is specified by G#nn within the data set name
on the DLBL.
When CA Dynam/D is called by the creation program to close the file, it

records this new generation number as the current one. The current
generation number of a file can be identified from the following:
You can use the DYNCAT utility program to display the current generation
number and the maximum number of generations. You can also ALTER the
next generation number to be created.
You can use the system messages to display current generation

information.
You can use the DYNVTOC utility program to display the current
generation number.
You can use CUI File Management to display the current generation
number.
Changing Generation Numbers
If it is necessary to change the current generation number to a lower value,

the VTOC entries for the already existing files above this number should be
removed from the DASD devices upon which they reside. (For more
information about the DYNUTIL DELETE command, see Supporting Disk File
Management.)
In addition, remove their associated version records from the Catalog before
the generation ID is updated with NEXTGEN.

Deleting Generation Data Sets
CA Dynam/D will also delete any outdated generations based on the number of
generations defined in the Catalog for this file. If, for any reason, the program
abends, the current generation number remains intact and thus allows the
program to be rerun without any JCL changes. The current generation number
will remain unchanged until the next creation of the file. It is used by CA
Dynam/D to determine which version to access when the file is subsequently
processed as input.
The CA Dynam/D DASD allocation routines will assume that any expired CA
Dynam/D-created file is available for deletion. Generation data sets are always
allocated as permanent files to ensure that they are controlled exclusively by
version.
Generation Data Set Option
You can specify an option on the DLBL to control which file generation is to be
accessed. If you don't specify an option, CA Dynam/D will read the most
current file. (To follow the syntax rules defined for CA Dynam/D option codes,
enclose the file generation option in parentheses.) With this option, you can
request access to a version by specifying any one of the following about the
files:
Generational number
Absolute generation number
Relative generation number
Generational Numbers
The generational number is recorded in the file ID of the disk VTOC for each
version. To request a version by its generational number, include that number
as an option in the file ID field of the DLBL statement. For example, to request
the sixth version of a file (defined as G#06 in the VTOC entry for that file), use
the following option code:
// DLBL FILE,'DISK.FILE(G#06)'
4–22 User Guide

Absolute Generation Numbers
Absolute generation numbers are internal numbers recorded in the CA Dynam

Catalog for each version. To access a version by its absolute generation
number, include that number as an option in the file ID field of the DLBL
statement. For example, to access version with an absolute version number of
3, specify:
// DLBL FILE,'DISK.FILE(G=3)'
Relative Generation Numbers
The relative generation number refers to a file as it relates to the most current
version, which is designated as G-0. To request a version by its relative
generation number, include that number as an option in the file ID field of the
DLBL statement. The option code for the relative generation number ranges
from G-0 to G-98:
G-0 Requests that the current generation be accessed
G-98 Asks for the file created 99 generations ago (if it still exists)
If you request the relative version G-2 (2 generations older than the current
one), you will access the Grandfather of the latest version. Specify this option
as follows:
// DLBL FILE,'DISK.FILE(G-2)'
The following examples show the ways of using the generation data set option
to access the same file version. Assuming that six versions of the file exist,
you can access the most current version by specifying the following:
Generational Number Absolute Generation Number Relative Generation Number
// DLBL // DLBL DTF,'PAY.MASTER(G=6)' // DLBL DTF,'PAY.MASTER(G-0)'

DTF,'PAY.MASTER(G#6)'

Automatic Volume Assignment and Recognition (AVR)
Automatic Volume Assignment and Recognition (AVR)
Using AVR Processing
The Automatic Volume Recognition (AVR) facility of CA Dynam/D makes logical

unit assignments by analyzing the volume serial number of the EXTENT
statement for a given SYS number. In this way, an ASSGN statement is not
needed and the user need not know the physical device address in advance.
You can regulate the scope of AVR by specifying the following parameters in
the DYNAM/D option record:
To provide AVR for all files, specify AVR(ALL).
To provide AVR for CA Dynam/D-controlled files only, specify

AVR(DYNAMIC).
Whenever there is a missing ASSGN statement for a given logical unit, CA

Dynam/D (at OPEN time) automatically searches for a volume serial number
which matches the serial number requested. When a match is encountered, a
temporary assignment is made to the appropriate device address. In the event
that a matching serial number cannot be found, a mount message requiring a
response appears on the console.
However, if you included an ASSGN specifying the wrong device, CA Dynam/D

AVR will either correct the assignment or choose another LUB with which to
make the assignment.
At the end of the job, the AVR assignment is cleared.
Bypassing AVR Processing
You can temporarily bypass CA Dynam AVR processing by specifying option B

on the DLBL statement, for example:
// DLBL DISKOUT,'FILE.OUT(B)'
Note: Programs such as IBM Sort/Merge and the IBM compilers check the
device type assigned to each file before opening any files. Therefore, these
files should be assigned to some DASD device. Thus, at OPEN, CA Dynam/D
AVR will change the assignments to the correct DASD devices.
The assignment should be to a device of the same type as one of the devices
to which CA Dynam/D will change the assignment, because the device type is
determined prior to OPEN, in mixed DASD installations.
4–24 User Guide

Selecting Logical Units

We recommend omitting any logical unit specifications from JCL for all files
processed under CA Dynam/D control. The following description explains how
CA Dynam/D selects logical units.
CA Dynam/D first decides on which physical device the file belongs. It then
begins searching for an appropriate logical unit. The order of priority for
choosing a logical unit is as follows:
Logical unit as specified in the EXTENT statement
Logical unit as specified with S:nnn option from DLBL statement
Logical unit as found in user DTF

Logical unit as defined for the data set in the Catalog
Highest logical unit in the partition, if none of the above has been specified
The search for a logical unit ends when a valid LUB is found.
Overriding SYS Numbers
You can override the DTF or cataloged SYS number by using the DLBL file ID
option code S:nnn. The SYS NUMBER OVERRIDE option code must be enclosed
within parentheses as the last part of the file ID. Use the following format:
// DLBL FN,'file-ID (S:nnn)'
where nnn represents the logical unit number. Only programmer LUBs are
valid.
Specifying Other Option Codes
In conjunction with the S:nnn specifications, other option codes can also be
specified within the parentheses. For example, to specify that SYS005 is to be
used as the logical unit for the file and option codes D and I are also to be in
effect, submit this DLBL statement:
// DLBL FN,'file-ID (S:005,D,I)'

LUB Availability
Once a primary LUB is established, CA Dynam/D next checks to see if the

primary LUB is available—already assigned to the correct device, or
unassigned (UA). In either case, it will be used and no access to the COMLUB
option record for dynamic LUB (DYNLUB) processing will be made. But if the
primary LUB is already assigned to another device, then the primary is
discarded and COMLUB processing is entered to choose another acceptable
LUB.
If a COMLUB range has been established for the partition, all LUBs in the range
are searched to locate one which is available (either already assigned to the
correct device, or unassigned—UA). If no COMLUB range has been established,
all programmer LUBs in the partition are searched, beginning with the top and
working down.
SYS Number Considerations
IJSYS Files
IJSYS files are never subject to COMLUB. If an assignment for one of these
files must be made, CA Dynam/D will change the assignment instead of
choosing another logical unit.
SD Work Files
When using SD work files, CA Dynam/D searches the volume or pool specified.
If the file is found, CA Dynam/D will access it; otherwise, CA Dynam/D will
allocate it.
DA Files
VSE requires you to include a specific logical unit specification on each EXTENT
statement in the JCL for a DA file. If there are multiple extents on one volume,
the logical unit specified must be the same for each extent. When the file
spans another volume, the SYS number for the first extent on the new volume
must be one number higher than the SYS number for the preceding extent.
Further extents on the new volume must again have the same SYS number as
the first extent on that volume, and so on.
4–26 User Guide

Modifying Logical Unit Assignments (LUBS)
When CA Dynam/D controls the file, logical unit assignments given in the JCL
are checked to ensure that they conform to these rules; they are replaced by
correct ones if they are in error. If no logical unit numbers are given in the
JCL, or if the specified ones are already either assigned to other disks or have
been replaced as described above, then dynamic LUB allocation is invoked.
When a sufficiently long consecutive series of available SYS numbers is found,
it is allocated to the file.
Dynamic LUB Allocation
The Dynamic LUB Allocation facility enables you to define ranges of LUBs for
use by CA Dynam/D, whenever an assignment needs to be modified. In order
to use this facility, the COMLUB option record must be defined. For more
information about the use of the COMLUB option record, see the Programming
Guide.
This facility ensures that disk files will not be cross-assigned. For example, if a
program opens two files simultaneously on separate disk volumes with the
same SYS number, CA Dynam/D will use the specified logical unit for the first
file, and will choose another logical unit for the second file from a user-defined
range.
Thus, the two files will have unique SYS numbers pointing to different disk
volumes. This eliminates the danger of cross-assignment.
Defining LUB Ranges
You can define a range of LUB entries for CA Dynam/D to use, or even a series
of LUB entries. For example, you can define ranges SYS030 through SYS039,
SYS050 through SYS052, and SYS058 through SYS070 as available LUB
entries.
CA Dynam/D uses dynamic LUB allocation to find an available LUB or

programmer logical SYS number. The existence of the COMLUB option record
is checked whenever CA Dynam/D needs to find an available logical unit to
assign to a disk address.
In the case of multivolume DA files, CA Dynam/D uses dynamic LUB allocation

to find a consecutive series of available programmer logical SYS numbers long
enough for all the volumes used by the file. If you work with this type of file
under CA Dynam/D control you should be sure that the LUB entry ranges
defined in your COMLUB option record include plenty of room in the form of
consecutive series.

COMLUB Option Record Processing
If you specify a range of LUB entries with the COMLUB option record, then CA
Dynam/D checks each LUB entry specified and uses the first free LUB in the
range. Multiple LUB ranges can be specified for each active partition.
LUB Assignments
If all of the LUB entries specified are in use and none are assigned to the
desired disk address, an error message NO FREE LUBS AVAILABLE appears
and the job is canceled. However, if one of the LUB entries is available or is
already assigned to the correct disk address, then the original assignment is
overridden.
If the COMLUB option record is not available, CA Dynam/D will scan all LUB
entries for the partition (in descending order) to find either an available LUB or
a LUB which is assigned to the desired disk address. If such a LUB is found, it
is the one used. Otherwise, an error message appears and the job is canceled.
Dynamic LUB allocation ensures that an existing logical unit assignment is

generally never modified. Thus, the danger of cross-assignment of files
assigned to the wrong disk volume is eliminated.
Note: Whenever CA Dynam/D must change an existing assignment, the

message CADD037A ASSIGNMENT OVERRIDE appears on the operator's
console (For more information, see message explanation.). The possible
actions to be taken in response to this message are:
To Type
Cancel the job CANCEL
Specify the nnn assignment to use instead SYSnnn
Allow dynamic LUB allocation to find a new logical unit COMLUB
Change the assignment IGNORE
4–28 User Guide

Extending ISAM Files
Extending ISAM Files

If it is necessary to extend an existing ISAM file defined in the Catalog, you
must specify the option code IE in the file's DLBL statement. This code
indicates to CA Dynam/D that the ISAM file is to be extended rather than
created. Again, no EXTENT statements are used. For example,
// DLBL FILEA,'ISAM FILE (IE)'
Note: IE should only be used with files defined in the Catalog.
Adding a File to the Catalog

You can catalog any file by specifying the option code C as part of the DLBL
file ID or by executing the DYNCAT utility program. For more information
about DYNCAT, see the chapter "Maintaining the Catalog—DYNCAT Program."
The DYNCAT program enables you to create an entry in the CA Dynam Catalog
which records a data file's characteristics and disk space requirements.
Alternatively, you can specify option code C on a DLBL statement, which
automatically creates (or recreates) a catalog entry when the file is closed.
The option code C takes effect only when the data file is being created. The
catalog entry created (at CLOSE) includes information such as the disk volume
the file was created on and the number of tracks allocated and used.
Examples To catalog an SD file:
// JOB GENERATE SD WORK

// DLBL SDDOUT,'DISK.FILE (C,I)'
// EXEC PROGRAM

Note that the character C enclosed within the parentheses indicates the file is
to be cataloged when the file is closed.

Controlling Disk Pools
To catalog an ISAM file:
// JOB CATALOG ISAM FILE

// DLBL ISMOUT,'ISAM.FILE (C,I)',12,ISC
// EXEC PROGRAM

Two facilities are provided for controlling allocation and access to DASD
devices by CA Dynam/D: the COMPOOL option record, and the COMAVR option
record.
Defining Disk Pool Volumes (COMPOOL)
Disk pool management is a feature which lets you select a volume from a
group or pool of disk volume serial numbers. Defining a pool of disk volumes
provides a better balance of disk volume usage, thereby increasing efficiency.
In addition, you can specify different disk pools for each partition defined in
the operating system.
You can also define protected areas on a disk pool volume, thus ensuring that
these areas are never used by CA Dynam/D for disk space allocation. While CA
Dynam/D will not allocate in these areas, the files therein are still scanned
during mapping, and can be deleted if found to be expired.
When defining a pool of disk volumes, you must specify the following:
A virtual volume serial number which does not exist as a physical DASD
volume
A group of real or existing volume serial numbers which are related to the
virtual serial number
Make certain that the virtual serial number you specify matches the VOLSER
number entered either in an EXTENT statement or in the CA Dynam Catalog.
4–30 User Guide

In order to use the Disk Pool Management facility, the following conditions
must be satisfied:
COMPOOL option record must be defined. For more information about

using the COMPOOL option record, see the Programming Guide.
Data file must be under the control of CA Dynam/D (relative track equal to
the CA Dynam/D trigger value or defined in the Catalog).
Rotating Disk Pool Volumes
Rotation of disk pool volumes is a vital feature of disk pool management. In

order to achieve well-balanced disk volume usage, CA Dynam/D will optionally
use the volumes defined in the disk pool on an equal basis. When this option,
ROTATE(YES), is in use, CA Dynam/D remembers the last volume used and
searches for the next volume in the pool when attempting a subsequent space
allocation.
This rotation of disk volume usage ensures that data files are spread across
several volumes defined in the pool, thereby creating an environment of
optimum file-accessing efficiency.
When using pool rotation, CA Dynam/D begins searching for free space
starting at the volume which follows the one last used. If the previous open
began its search at the last volume in the pool, the next starting point is at the
first volume defined.
The rotation of starting volumes is performed regardless of the partition

issuing the open request. As mentioned, the rotation only affects the starting
point for the free space search.
If the starting volume does not contain the required amount of available
space, or is not mounted, the search continues to the next volume. Full
wraparound from the last volume defined in the pool to the first volume is
supported.
The only exception to pool rotation is the secondary allocation of sequential

disk files. If the open is for a secondary extent, CA Dynam/D attempts to start
the free space search on the volume containing the primary extent for the file.
This avoids exhausting all available volumes with secondary extents.

For example, assume the following:
"virtual" VOLSER = POOL01

POOL volume serial numbers, in order:
(1) SYSWK1
(2) SYSWK2
The JCL:
// DLBL DTF,'DSN'
// EXTENT SYS008,POOL01,1,0,1,100
In the above example, CA Dynam/D will perform its pool management function
because relative track 1 (the trigger value) is specified and the serial number
POOL01 is defined in the disk pool table. CA Dynam/D then tries to allocate
100 tracks on disk volume SYSWK1, and, if there is insufficient space,
SYSWK2 will be used.
Defining Disk Pools for AVR (COMAVR)
The COMAVR option record is used to specify the DASD devices available to
the CA Dynam system. It can be used to control access to devices by partition,
class, and by CPU, as well as globally for the entire system.
If the COMAVR option record is not defined, all DASD devices attached to the
system are assumed to be controlled by CA Dynam.
If specified, only the indicated devices are processed. Any DASD devices which
are attached to the system but not specified in the COMAVR option record are
ignored by the system, and are not processed while searching for a mounted
DASD volume.
For more information about using the COMAVR option record, see the
Programming Guide.
Attention Routine (AR) Commands
Disk Status and Control Commands
These commands can be issued from the operator console to allow temporary
bypass of DASD processing and to display the status of a volume.
DD OFFline volser Disable a DASD volume for input and output.
DD ONLine volser Return a DASD volume to full processing.
DD QUIesce volser Make a DASD volume ineligible for controlled output.
4–32 User Guide

Allocating Space across Generic Volumes
DD STATUS volser Display the status of a volume that has been taken offline, put online, or
quiesced.
DD STATUS ALL Display a list of all offline and quiesced volumes.

Cross-volume allocation, in conjunction with the AVR facility, is used when it is
desirable to allocate disk space from a group of disk packs. These disk packs
are scanned generically in PUB order to determine the proper device address.
CA Dynam/D searches for a certain group of volume serial numbers, or all the
volume serial numbers defined in the PUB table. (The PUB table describes all
of the devices defined for the operating system.)
To request cross-volume allocation, enter from one to six asterisks (*) on the
EXTENT statement or in the Catalog for the volumes you want referenced. The
number of asterisks you specify within the serial number parameter will
determine the scope of the generic search.
Shown below is the format for specifying each of the six possible methods of
cross-volume allocation:
// EXTENT SYSnnn,vvvvv*
vvvv**
vvv***
vv****
v*****
******
If you specify a volume serial number (volser) of less than six characters and
ending with an asterisk, CA Dynam/D will left-justify the volser and pad
additional asterisks to construct the full six-character volser.
To Search for Volume Enter Generic Serial Number

Beginning With
vvvvv vvvvv*
vvvv vvvv**
vvv vvv***
vv vv****
v v*****
To search for all volumes, enter the generic serial number ******.

For example, if you enter serial number SYSWK*, CA Dynam/D searches for a
volume serial beginning with SYSWK. Once such a disk is found, CA Dynam/D
checks if there is enough available space. If not, the next occurrence of that
VOLID beginning with these characters is located. The process continues until
sufficient space is found to meet the allocation requirements for the specified
volume serial number.
Each of the other generic volume serial numbers shown in the table will cause
CA Dynam/D to follow the same method of searching the disks and verifying
their space. The only difference is the scope of the disk search; the more
asterisks you include in the generic VOLSER, the broader the search.
Finally, the serial number ****** causes CA Dynam/D to allocate the file on
any disk, searching each disk volume in PUB or COMAVR order.
Automatic Secondary Allocation
For files controlled using automatic secondary allocation, cross-volume

allocation will only be effective for the first allocation using a particular label
record. Subsequent opens will use the physical volume serial number on which
the file was placed the first time.
Disk Pool Management
The generic serial numbers can be used as pack POOLIDs in conjunction with
Disk Pool Management.
Catalog Management
Cross-volume allocation can be implemented using the Catalog Management

facility. For more information, see DYNCAT in the chapter "Maintaining the
Sample JCL:
// JOB DYNAM CROSS VOLUME ALLOCATION

// DLBL SDDINP,'DISK.FILE (D,I)',1,SD
// EXTENT SYS008,SYS***,1,0,1,38
// EXEC PROGRAM
CADD002I ALLOCATED FILE=SDDINP SYS008=205 SYSWK1 X=0/153/38
CADD003I AUTO-DELETE VOL=SYSWK1 FILE=SDDINP FILE-ID='DISK.FILE'
4–34 User Guide

Defining Minimum Space Allocation
The serial number SYS*** causes CA Dynam/D to search the disks for the first
occurrence of a VOLID beginning with the characters SYS. The first disk found
with 38 contiguous tracks available was SYSWK1 at address 205. Note that the
space was allocated starting at relative track 153. A temporary assignment
was then made for logical unit SYS008 to device address 205.
Defining Minimum Space Allocation

The minimum percentage allocation value is used to define the minimum value
CA Dynam/D will accept in allocating disk space. Your data center defines this
value at CA Dynam/D installation time (ARFACTR).
This facility offers you great flexibility in allocating disk space because CA
Dynam/D will adapt its space allocation algorithm to the particular disk volume
it is processing. Thus, programmers' jobs are much less likely to be
interrupted because of insufficient disk space.
With minimum percentage space allocation defined, CA Dynam/D searches the

VTOC once only for available disk space; no additional overhead is incurred.
CA Dynam/D will always attempt to initially allocate the requested number of

tracks. If this allocation request cannot be satisfied, then CA Dynam/D
continues to search for available disk space. This is accomplished by allocating
the largest contiguous free space available that is greater than the minimum
percentage defined in the DYNAM/D option record.
In order to illustrate the processing logic of CA Dynam/D minimum percentage

allocation, consider the following example. Assume that the minimum
percentage value is 95%.
// USER'S JOB CONTROL FOR THE FILE

// DLBL FILEA,'DISK.FILE'
// EXTENT SYS008,999999,1,0,1,100
At OPEN, CA Dynam/D initially attempts to allocate 100 tracks on disk volume

999999. If there is not sufficient disk space available, CA Dynam/D searches
for the largest contiguous space which is available. From the example above, if
the largest available space is found to contain more than 95 contiguous tracks
(96—100 tracks), CA Dynam/D automatically allocates the necessary disk
space, and processing continues.
Otherwise, CA Dynam/D begins its RECOVERY process, because the minimum

percentage value of 95% has not been reached.

Recovering from Lack of Allocated Space
Recovery Process Description
Use this facility when a request for disk space on a specific disk pack has failed
before the file or extent is opened. When a request for disk space on a specific
disk pack has failed before the file or extent is opened, the following occur:
First a console message is displayed. It informs you that there is

insufficient space available to meet the allocation request for the
requested disk pack.
The files listed on the VTOC are then displayed one-by-one, allowing you
to take the appropriate action.
Consider the following:
A volume can only be used once during the recovery.
Files with an expiration date greater than MANDTE cannot be deleted by

the operator.
Recovery actions cannot be used to change volumes for IJSYS-type

(DTFCP) files.
A list of available recovery actions is presented next.
Operator Recovery Actions
Shown below is a table listing all possible responses you can enter on the
system console to affect a recovery action. For more information about which
specific messages they apply to, see the Message Guide.
To Type
Allocate the largest piece of space on the volume MAX
Bypass the file, and display on SYSLOG the next file recorded BYPASS
in the VTOC
Cancel the job immediately CANCEL
Delete the file whose file ID was last displayed on SYSLOG DELETE
Invoke CA Dynam/FI to change the open request from disk to TAPE

tape
Rebuild the VTOC index, if you suspect that there are still BLDINDEX
undeleted expired files on a volume containing a VTOC index
Retry allocating disk space EOB|END
4–36 User Guide

To Type
Retry allocating the disk space originally requested on same RETRY

disk volume
Retry allocating disk space, requesting the number of nnnn

tracks/blocks you specify as nnnn; if a pool volume is used,
CA Dynam/D will search for the first volume defined in the
POOL
Select the next generic volume when using cross-volume NEWPAC

allocation or pool management
Stop the job, temporarily, by placing the partition into a wait STOP
state until you restart the job
Specify the volser (pool or nonpool) for which you want to V=volser
allocate space on the disk volume
Note that V=* causes CA Dynam/D to search all volumes

defined in the PUB (or COMAVR option record, if defined).
Example This example illustrates the capability of recovery from insufficient disk space:
// JOB ALLOCATE
// DLBL SDDOUT,'DISK.FILE (I,M)'
// EXTENT SYS006,DOSV**,1,0,1,787
// EXEC PROGRAM
CADD010W INSUFFICIENT DISK SPACE FILE=SDDOUT SYS006=201 SYSWK1 (787)
CADD021D PERM.FILE(300) CRE=29 DEC 1985 EXP=20 DEC 1999 MAX=100

NEWPAC
CADD010W INSUFFICIENT DISK SPACE FILE=SDDOUT SYS006=202 SYSWK2 (787)
CADD021D ISAM.FILE(200) CRE=23 DEC 1985 EXP=20 DEC 1999 MAX=400

BYPASS
CADD021D TEMP.FILE(100) CRE=11 NOV 1985 EXP=30 DEC 1985 MAX=400

DELETE
CADD021D DA.FILE(400) CRE=20 DEC 1985 EXP=20 DEC 1999 MAX=500

300


CA Dynam lets you use certain ID codes to define independent files. The
following describes how these ID codes provide protection for both partition-
independent and CPU-independent files:
Partition IDs ensure the uniqueness of File IDs across multiple partitions,
Volume serial numbers for a particular partition, or both.
CPU IDs ensure file uniqueness among different CPUs in a multi-CPU

environment.
When these files are processed, CA Dynam/D substitutes the appropriate ID of

the partition, CPU, or both, to replace the ID code you supplied. All the codes
supported for this function, and their substitutions, are shown in the table
below:
== Partition SYSLOG ID
=== Partition SYSLOG ID and CPUID character
CPU-- CPU-x, where x is the CPUID character
@ CPUID character
JCL-Defined Partition and CPU Independent Files
This section describes the JCL defined partition and CPU independent files.
Multi-Partition Files
File Uniqueness:
To ensure file uniqueness across multiple partitions, enter the partition ID

code on the DLBL statement in the format illustrated below:
// DLBL filename,'==.file-id',...
When the file is processed, CA Dynam/D will replace the two equal signs
('==') with the partition (BG, F1, F2, and so on) in which the job is running.
4–38 User Guide

SORT and Compiler Work File Considerations:
An important application of partition IDs is the definition of SORT work files or

any compiler work files. With the partition ID feature of CA Dynam/D, you
eliminate the need for separate sets of DLBL and EXTENT statements for each
partition.
Files must be defined for all partitions. However, the same label information
can be used for all jobs in any partition.
Multi-CPU Files
In a multi-CPU environment (real or virtual) using a shared DASD facility, you

can use CPU IDs to ensure file uniqueness from different CPUs. (Remember
that CPU IDs can be used together with partition IDs.) To define
CPU-independent files, enter the information on the DLBL statement in the
following format:
// DLBL filename,'CPU--.file-id'
At processing time, CA Dynam/D will substitute the second '-' with the single-
letter CPU ID generated from the System adapter option record.
Use with Identical File IDs
An important application of partition and CPU IDs is the definition of disk files
(such as sort, compiler, or library files) that can have identical file IDs in two
or more machines or partitions. CA Dynam/D eliminates the maintenance of
multiple sets of labels. Thus, the same Job Control statements can be run from
anywhere with complete file uniqueness. For example:
// JOB DYNAM
// DLBL IJSYSLN,'===.SYSLNK'
// EXTENT SYSLNK,POOL01,1,0,1,12
This is run on a machine with the serial number 32315, in the BG partition.
System Adapter option record is coded in the following ways:
CPUID id=A,SERIAL=0000215043810000
CPUID id=B,SERIAL=0003231543410000
CPUID id=C,SERIAL=0002096843610000
Note: For more information about updating the System Adapter option record,
see the CA CIS Administration Guide.
The VTOC entry for this file would appear as follows:
'BGB.SYSLNK'

Releasing Unused Disk Space
Single-Partition Volumes
You can also use the partition ID to uniquely define a volume serial number for
a particular partition. To do this, supply two hyphens ('--') as the last two
characters of the volume serial number on an EXTENT statement. For
example:
// JOB DEFINE PARTITION INDEPENDENT FILE

// DLBL SDDOUT,'==DISK.FILE(I,M)',2
// EXTENT SYS006,POOL--,1,0,1,8
// EXEC PROGRAM

The partition ID substitution will occur before CA Dynam/D determines if the

volume serial number corresponds to a COMPOOL volume serial number.
Catalog-Defined Partition and CPU Independent Files
To use partition independence and CPU independence for catalog-controlled

data sets, you must first define each of those data sets separately in the
Catalog. Each possible combination must be defined as a unique entry in order
to maintain each file's allocation information.
The following example illustrates the DYNCAT DEFINE statements required. For
more information about the DEFINE command, see the chapter "Maintaining
The Catalog."
// JOB DEFINE
// EXEC DYNCAT
DEFINE'BG.CPU-A.IJSY01' DISK ALLOC=(POOL01,TRK,100)
DEFINE'F3.CPU-A.IJSY01' DISK ALLOC=(POOL01,TRK,100)
DEFINE'BG.CPU-B.IJSY01' DISK ALLOC=(POOL01,TRK,100)
DEFINE'F3.CPU-B.IJSY01' DISK ALLOC=(POOL01,TRK,100)
/*
/&

This feature lets you recover significant amounts of disk space for subsequent
use. When a sequential disk (SD) file or an ISAM file is closed, CA Dynam/D
can truncate (release all unused space) allocated for the file. This facility is
standard for sequential disk files and is performed upon request for ISAM files.
However, only files allocated by CA Dynam/D are truncated.
4–40 User Guide

Truncating Files
SD Files
For SD data files, CA Dynam/D performs truncation automatically by default.

You can suppress truncation by overriding the default for a given SD file.
Simply specify option code N for No truncate in the DLBL statement, as
follows:
// JOB DYNAM SD FILE

// DLBL SYMBOL,'DISK.FILE(N)',10,SD
// EXTENT SYS008,POOL01,1,0,1,100
// EXEC PROGRAM
CADD002I ALLOCATED FILE=SYMBOL SYS008=203 SYSWK1 X=0/19/100
In this example, the file is not truncated in EXTENT size to the amount of disk
storage actually utilized. The corresponding VTOC entry for this file remains
unmodified.
ISAM Files
For ISAM files, you can truncate the specified prime EXTENT by specifying
option code T in the DLBL statement.
Sequential Work Files
To perform truncation on sequential work files, you must specify option T on

the DLBL statement.
FBA DASD Files
Truncation will take place on FBA DASD in even multiples of 8 physical blocks
(512 bytes each physical block).
For example, if a file were to be created with an allocation of 160 blocks, and
only 147 blocks were used, the file would be truncated to block 152 rather
than 147. This restriction allows CA Dynam/D to control allocations on these
volumes with a bit map, greatly reducing system overhead.
CKD DASD Files
Truncation on CKD DASD will take place to the track following the last record
of EOF.

Deleting Files
DA Files
No truncation is performed on DA files because no EOF record is written.
Deleting Files
This section describes how to delete data and work files.
Deleting Data Files
You can specify in the JCL that a sequential disk (SD), direct access (DA) or
ISAM file is to be deleted when closed. The JCL entry overrides the default
option (no deletion). To request deletion, specify either of these DLBL option
codes:
Option code D DELETE at input CLOSE
Option code X DELETE at input or output CLOSE
When deleting a file, the VTOC entry for that file is deleted—not the actual
data on the disk.
Deleting Work Files
A special case is encountered for IBM SORT work files. The IBM Sort/Merge
program does not close the SORTWK files. Therefore, CA Dynam/D will only
analyze the DLBL statements for the SORT work files when a SORTOUT
file name is closed. CA Dynam/D will then assume the D (delete) option.
If you do not specify the file name SORTOUT for the file used as the sort
output, you should include the option code W for that file; otherwise, the
SORTWK files will not be deleted. When a sort output file defined with option
code W is closed, CA Dynam/D will delete the SORTWK files used during the
job.
CA SORT Work Files
Sort work files used for CA SORT are always deleted if no longer needed.
4–42 User Guide

Processing Expired Files

When CA Dynam/D is mapping a volume to perform allocation, any VTOC
entries containing expired dates will be deleted if—and only if—those entries
are for existing files created under the control of CA Dynam/D. Files are
considered to have been created under control if any of the facilities of CA
Dynam/D were invoked when the file was created (for example, AVR,
COMLUB, Device Independence, and so on), regardless of whether CA
Dynam/D allocated the file.
Retention and Expiration Date Criteria
The processing of expired files depends on the following factors:
Whether the files are cataloged
Whether you specify retention/expiration on the DLBL statement
Whether you use certain retention defaults
The retention and expiration date criteria by which CA Dynam/D determines

how to process expired files are presented on the next two pages under
Retention and Expiration Date Processing.
Retention and Expiration Date Processing
CA Dynam/D analyzes your DLBL statement and any associated catalog-

defined information in order to determine the retention/expiration dates to be
used. To illustrate, consider the following cases:
Without using the CA Dynam Catalog

Using the CA Dynam Catalog
Without Catalog Use
In the following examples, the Catalog is not being used and DLBL and
EXTENT statements are supplied.
If the retention/expiration specification is omitted from the DLBL statement,

then the VSE default of seven (7) days retention is used by CA Dynam/D.
Example:
// DLBL DTF,'DSN',,SD
// EXTENT SYS001,VOLSER,,,1,100

If the retention/expiration specified on the DLBL statement is nonzero and is

greater than the current date, then that value is used by CA Dynam/D.
Example:
// DLBL DTF,'DSN',2099/365,SD
If the retention specified is zero, or the expiration is less than or equal to the
current date, the DEFRET value from the DYNAM/D option record is used.
Example:
Using the Catalog
In the following examples, the CA Dynam Catalog is being used and only a
DLBL statement is supplied:
If the retention/expiration specification is omitted from the DLBL statement,

then the retention/expiration date specified in the Catalog is used. If the
retention/expiration dates are omitted from both the DLBL statement and the
Catalog, then a default of seven (7) days retention is used.
Example:
// DLBL DTF,'DSN',,SD
If the retention/expiration specification on the DLBL statement is nonzero and

is greater than the current date, then that value is used by CA Dynam/D.
Example:
If the selected retention/expiration specification from the DLBL statement or, if

omitted, from the Catalog is less than or equal to the current date, then the
DEFRET value from the DYNAM/D option record is used.
Example:
// DLBL DTF,'DSN',0,SD
4–44 User Guide

Processing of Equal File IDs
Processing of Equal File IDs

A permanent file is defined as a file with an expiration date of 2099/365 or
greater. Any file with an expiration date less than 2099/365 or the value
specified for AUTODTE in the DYNAM/D option record is considered
nonpermanent.
CA Dynam/D will always check for an equal file ID when allocating disk space
for an output file. If an equal file is found, and the file is nonpermanent, the
original file is immediately deleted from the VTOC without displaying an EQUAL
FILE-ID message on the operator's console.
For permanent files, if an equal file ID condition occurs, the CA Dynam/D

message CADD036D appears on the operator's console. For more information
about possible operator actions, see the Message Guide. At that point, the
operator can either CANCEL the job, DELETE the file and reallocate the new
file, or REWRITE the file using the existing extent limits as defined in the
VTOC.
CA Dynam/D will also attempt to find this permanent file on other volumes
(only if a pool or generic volume is specified), and the operator can either
DELETE the equal file found or IGNORE the file found.
Sending File-Dependent System Messages

There is often a need to communicate with your Operations staff concerning
specific processing for a certain file at a certain time. Supplementary Message
support provides a flexible means of defining your own messages and sending
them to the system console or printer at one or more of four points in file
processing.
These messages are defined in the Catalog by using the DYNCAT DEFINE or
ALTER functions. For more information, see the chapter "Maintaining the
They will be issued automatically by the system at the indicated point in the
job.
For example,
DEFINE 'MASTER.FILE' OOMSG='ISAM MASTER RELOAD HAS BEGUN'

COMSG='ISAM MASTER RELOAD IS NOW COMPLETE'
would result in the following two messages for the output file:
CADD997I ISAM MASTER RELOAD HAS BEGUN (issued at OPEN)

CADD999I ISAM MASTER RELOAD IS NOW COMPLETE (issued at CLOSE)

SORT Considerations
Supplementary message definitions can be specified as follows:
To Issue At Specify
CADD996I message Open Input time OIMSG=msg text
CADD997I message Open Output time OOMSG=msg text
CADD998I message Close Input time CIMSG=msg text
CADD999I message Close Output time COMSG=msg text
Supplementary messages are supported for both CA Dynam/D and CA

Dynam/T users. If a data set contains a supplementary message, the message
will be issued regardless of whether the file is processed as a tape or a disk
file.
Message output can be optionally directed to SYSLST, SYSLOG, or both.
SORT Considerations
Many considerations apply when using CA Dynam/D with sort utility programs
other than CA SORT, CA Sort/Merge software product.
CA SORT is a SORT and MERGE program which completely replaces the IBM
Sort/Merge. CA Dynam/D and CA SORT have been designed to complement
one another. Thus, if your data center uses CA SORT 7.2 or above, CA
Dynam/D provides an interface for it.
CA SORT Interface
The CA Dynam/D interface to CA SORT does all of the following:
Assigns the appropriate DASD device before open.

Builds the SORTWKn labels if not specified within the job control.
Provides the correct block and record size so that the CA Dynam Catalog
and the VTOC for the SORTOUT file are correctly updated.
Specifies the input file size, if you do not, and passes it to CA SORT
(SIZE=n of SORT control statement).
Truncates the SORTOUT file; all unused DASD space allocated for this file
is released when the SORTOUT file is closed.
4–46 User Guide

SORT Considerations
Allocates secondary disk space only for the last of the SORTWKn files.
Deletes the SORTWKn files from the VTOC as soon they are no longer
needed.
Truncates SORTWKn files, if appropriate.
Note: If the facility to build the SORTWKn labels is used, the allocation of
DASD space is calculated either by CA SORT (based on information you pass in
the SIZE=n parameter) or by CA Dynam/D (from VTOC information collected
from all volumes where the requested SORTINn files reside). Normally, the
information passed is correct. But to avoid running out of available extents for
SORTWKn, generate CA Dynam/D with Automatic Secondary Allocation.
Thus by using CA SORT and CA Dynam/D, it is not necessary to specify
// ASSGN and
// DLBL SORTWKn statements; the file information in the CA Dynam Catalog

and the VTOC is correct.
IBM Sort/Merge Program
IBM sort files must be assigned to the proper device type before the SORT is
invoked. Otherwise the sort message UNIT ASSGN ERROR or a channel
program error can appear, and the SORT job will cancel. For example, if the
SORT files are to be read or created on a 3380 disk volume, these files must
be assigned to a 3380 device prior to running the SORT.
IBM Sort Work Files
CA Dynam/D does not support secondary allocation for IBM sort work files.
These files are deleted from the VTOC if all the following conditions are met:
SORTOUT is closed
DTFname of the sort work files is SORTWK
DTFname for the sort output is SORTOUT
IBM Sort Output Files
The VTOC and CA Dynam Catalog are not correctly updated, because there is
no block and record size available for the IBM sort output file. This is because
IBM's Sort/Merge defines SORTOUT as a DTFPH file.

Using Option S
Option code S will be ignored for CA SORT. The same file ID can be used
without special processing, because CA SORT opens the output file after the
input files are closed.
This option code causes CA Dynam/D to open the SORTOUT (or equivalent) file
to write over the SORTIN file if it exists. Otherwise the file will be allocated as
a normal SORTOUT file. With the IBM Sort/Merge, option code S can cause
problems and should be used with caution. For example, if the SORTOUT file
has a smaller block size than the SORTIN file, the SORTOUT file can exceed
the existing SORTIN file capacity. This causes the VSE message NO MORE
AVAILABLE EXTENTS to appear.
In addition, if multiple SORTIN files are processed, option code S should not be
specified unless the output from the SORT will fit within the extents for
SORTIN1.
Note: The IBM Sort/Merge performs extensive pre-open checking of SORTIN

files. This may require you to provide a resolved label record under some
conditions. If so, the DYNOPEN utility program can be used for this purpose.
For more information about DYNOPEN, see the chapter "Supporting Disk File
Management."

CA Dynam/D provides you with the SET Job Control command. This command
lets you control various options of the CA Dynam/D system through Job
Control. It can be entered either through the system operator's console or
along with other JCL in an input job stream. The command affects only the
partition in which it is entered. Both permanent and temporary options are
available with the SET command.
The permanent option (PERM) sets values that will remain in effect until the
next IPL or until changed by another SET command with the permanent
option. (PERM is also the default for the SET command.)
You can override the permanent values on a job-by-job basis by using the
temporary option (TEMP). Any options specified with the TEMP option of the
SET command remain in effect until either another SET command is entered,
which changes the previous specifications, or END-OF-JOB. The values then
revert to the permanent settings or null values.
4–48 User Guide

The following options are available:
CA Dynam/D informational messages can be directed to the system

console or disabled from the SYSLST output.
CA Dynam/D can be temporarily deactivated and reactivated.
The job control exit can be used to convert JCL which was created to
operate on one type of DASD device to operate on a different DASD device
type. The user supplies information necessary to perform the desired
conversion.
SET Command Syntax Rules
The SET command syntax rules are as follows:

Enter the SET command in position 1, followed by at least one space.
You can issue an individual SET command for each operand defined or a
single SET command specifying all of the operands.
If you specify a single SET command with multiple options, separate the
operands by a comma (no blank spaces).
Summary of SET Command Syntax
The SET command syntax appears as follows:
[ CPCMD='command' ]
[ CONSOLE= {ON|OFF|NULL } ]
SET [ DYNAMD= {OFF|ON } ]
[ $JOBEXIT= {AFTER|BEFORE } ]
[ LABELMSG= {ON|OFF } ]
[ {PERM|TEMP } ]
[ PRINT= {AFTER|BOTH|OFF|ON|NULL } ]
The following tables describe the SET command operands more fully. They are
presented alphabetically.

CONSOLE= Indicates whether system messages are to display on the system console.
ON Prints all CA Dynam/D informative messages on the

system console.
OFF Suppresses the CA Dynam/D messages which were

directed to the console using CONSOLE=ON.
If CONSOLE=OFF is specified, the M option code always takes precedence.
NULL resets this option to value specified in the DYNAM/D

option record.
CPCMD= Lets you pass a command to CP while running under VM.
DYNAMD= Indicates whether CA Dynam/D is to process in the partition in which the SET
command is issued.
ON Enables CA Dynam/D to process in that partition.
OFF Disables CA Dynam/D processing in that partition.
DYNAMD command is issued in the same partition or until the VSE machine is
IPLed.
In dynamic partitions, CA Dynam/D intercepts can be disabled only until the

$JOBEXIT= Specifies whether the standard job exit ($JOBEXIT) will be processed BEFORE
or AFTER the CA Dynam common job exit.
If you have specified processing in the standard $JOBEXIT which will effect CA
Dynam processing, (i.e. CA Dynam option substitution for TLBL|DLBLs), code
the SET $JOBEXIT=BEFORE command.
LABELMSG= Determines whether the CADC950I message will appear for TLBL|DLBL
statements containing CA Dynam option codes. This message displays the
original file ID information before processing options are removed by the CA
Dynam Job Exit.
The CADC950I message will appear on SYSLST if // OPTION LOG is coded, on

SYSLOG if LOG is coded and on both SYSLST and SYSLOG if both options are
coded.
Note: The SET LABELMSG command affects all partitions.
4–50 User Guide

PERM|TEMP PERM is the default if you specify neither PERM nor TEMP.
PERM Indicates that the CONSOLE= and PRINT= options on this

SET command are to remain in effect for the duration of
the processing session, unless overridden (for a single
job) by a temporary SET command or changed by a
subsequent SET command with the PERM option.
TEMP Indicates that the CONSOLE= and PRINT= options on this

SET command are to remain in effect for the duration of
this job only or until changed by a subsequent SET
command.
PRINT= Relates to the printing of CA Dynam/D informative messages. The value set
for PRINT takes precedence over any option codes defined for a file. For
example, if PRINT=OFF is specified, the I option code for a file will be ignored.
The options AFTER and BOTH determine the carriage control position for
printing messages on SYSLST. They protect CA Dynam/D messages from
being overwritten by user programs which issue WRITE statements without
ADVANCE instructions.
AFTER Prints a CA Dynam/D message after breaking to the next

print line.
BOTH Breaks to a new line, prints a CA Dynam/D message, and

then breaks to the next line.
OFF Suppresses the messages which are directed to SYSLST

through the CA Dynam/D generation option.
ON Prints CA Dynam/D informative messages on SYSLST,

overriding PRINT=OFF which suppresses them.
NULL Resets the option to that specified in the DYNAM/D option

record.

Examples Examples of the SET command follow:
SET PRINT=OFF,CONSOLE=ON (until changed or IPL)
SET PERM,CONSOLE=ON,PRINT=ON (until changed or IPL)
SET CONSOLE=ON,TEMP,PRINT=OFF (console and print for

Job duration only)
SET PRINT=OFF (until changed or IPL)
SET PRINT=AFTER (until changed or IPL)
SET PRINT=BOTH (until changed or IPL)
SET CONSOLE=ON (until changed or IPL)
SET DYNAMD=OFF (until changed or IPL)
Restarting Checkpointed Files
CA Dynam/D provides the DYNOPEN utility program to let you restart trigger-
driven and catalog-controlled single or multi-extent files. However, multi-
extent files created through the automatic secondary allocation facility cannot
be successfully restarted. Generation data sets can also be restarted if you use
the DYNCAT utility program prior to restarting, as described below.
For more information about using DYNOPEN, see the chapter "Supporting Disk
File Management."
Restart Processing
In order to ensure a successful restart, the following must be done:
DYNOPEN must be executed before the RESTART job control statement.

All output files must be opened with mode equal to input.
The logical unit must be specified as the same logical unit that was
assigned when the checkpoints were taken. During RESTART processing,
the logical unit is checked against the checkpoint record, and if they are
not the same, an IBM error message is issued.
4–52 User Guide

Checkpointed Generation Data Sets
Before restarting a checkpointed generation data set, you must manually add
that version to the Catalog prior to running DYNOPEN. It must be added
manually because the Catalog update which normally occurs during CLOSE
processing might not have occurred if the job terminated abnormally. You
must use the DYNCAT ADD function to add that version.

Chapter 5: Supporting Disk File
Management
Disk File Maintenance Utilities

A set of utility programs is provided with CA Dynam/D to enable you to do the
following:
Move entire disk volumes or data sets between tape and disk.
Modify the retention period of a file.
Delete a file from the VTOC.
Display the contents of files in hexadecimal or character format.
Provide a sorted VTOC listing.
Produce frequency and space utilization reports.
Pre-open disk files so that utility programs can take advantage of the
facilities of CA Dynam/D.
Migrate data sets from one device type to another.
Modifying the VTOC—CAINTDK
The CAINTDK utility program provided with CA Dynam/D helps reformat

existing disk volume VTOCs to improve performance in conjunction with the
CA Dynam/D Indexed VTOC facility. CAINTDK accepts control statements that
are compatible with those used by the IBM VTOC utility, INTDK, and functions
on all supported DASD. When executed, CAINTDK rebuilds an existing volume
VTOC without disturbing the files that already exist on that volume.
Two types of control statements (VTOC and VOL) are needed to run the
CAINTDK program. Each has its own format and set of syntax rules, as
described in the following topics.
VTOC Control Statement
This statement describes the format of the VTOC.
Chapter 5: Supporting Disk File Management 5–1

VTOC Statement Syntax
Apply the following rules to the VTOC statement:
The VTOC control statement uses a free-form keyword format.
Start the VTOC command in position one, followed by at least one space.
Separate all operands with commas.
Positions 72—80 of each input command are ignored.
Continuation statements are not supported.
Do not include any comments in the statement.
This command has the following format:
VTOC STRTADR= {nnnnnn|cccchh }, EXTENTS=nnnnn[, CISIZE=nnnnn ]

[, SYSNO=nnn ]
[, OLDVOLID=xxxxxx ]
VTOC Controls the characteristics of the new VTOC.
STRTADR= {nnnnnn|cccchh }
Defines the beginning address of the VTOC extent, PBN if FBA, or CCCCHH if
CKD. It can overlap the old extent.
EXTENTS=nnnnn Indicates the number of Format 4 and Format 5 records for FBA; number of
tracks desired in new VTOC for CKD.
CISIZE=nnnnn Optional operand. Specifies the CISIZE in bytes desired for the new VTOC for
FBA. The recommended size is 2048. This operand is ignored for CKD. The
default is 1024.
OLDVOLID=xxxxxx Optional operand. Identifies the volume serial number of the DASD volume to
be reformatted. If omitted, the default is whatever volser is found on the
assigned volume.
SYSNO=nnn Optional operand. Defines the logical unit to be used to read the old VTOC and
write a new one. The logical unit must be assigned to the proper device. If not
specified, SYS001 is the default.
5–2 User Guide

VOL Control Statement
This statement defines the volume to be modified.
VOL Statement Syntax
The VOL control statement uses the fixed format shown below. Start the VOL
command in position one.
VOLnxxxxxx,ownerid
VOL Specifies which DASD volume is to be modified.
n Indicates the relative position (1—6) of a volume label within a group of

volume labels, normally a 1.
xxxxxx Identifies the volume to be modified. We recommend using all six characters.
(For more information, see the IBM Initialize Disk Utility Manual.)
Ownerid Optional operand. Specifies the code that identifies the owner to be entered
into the volume label. 1—14 alphanumeric characters; embedded blanks
acceptable.
Example
// JOB CAINTDK
// ASSGN SYS001,1E8 /* DASD VOLUME TO BE MODIFIED */
// EXEC CAINTDK
VTOC STRTADR=002,EXTENTS=600,CISIZE=2048,SYSNO=001,OLDVOLID=OLDFBA
VOL1NEWFBA,USERS-NAME
/*
/&
Converting EXTENTs—DYNCONV
The DYNCONV program lets you convert the EXTENT statements in a job
stream to accommodate the value of the CA Dynam/D trigger. It produces a
listing of the old and new EXTENT statements.
This program also accepts an optional statement, the CONVERT control

statement, as the first input statement to DYNCONV. The CONVERT command
lets you convert the number of allocated tracks/blocks to a new value based
upon new and old device types or a user-defined conversion ratio.
If you want to modify only the relative track/block value to the CA Dynam/D
trigger value, omit the CONVERT control statement. However, if you supply a
CONVERT statement for a job stream whose EXTENTs already specify the CA
Dynam/D trigger, the allocation value conversion is still performed.

DYNCONV Control Statement Syntax
Apply the following rules when using the DYNCONV control statement:
The control statement is in free-form format beginning in any statement

position.
Leave at least one space following the CONVERT command.
All operands must be separated by one or more blanks.
Continuation statements are not supported.
CONVERT OLDDEV=nnnn NEWDEV=nnnn [SECNO=nnn] [PERCENT=nnn]
CONVERT Optional command. Converts the number of allocated tracks/blocks to a new

value.
OLDDEV=nnnn Specifies either the device type, for which the input job stream is set up, or a
device conversion value to be used for the conversion calculations.
For device type values, you can specify 2311, 2314, 3310, 3330, 3340, 3350,
3370, 3375, 3380, 3390 or 9345. For any other FBA devices specify 3370.
Device conversion values can be specified as a 1- to 4-digit number.
NEWDEV=nnnn Specifies either the device type on which the output job stream is to be used,
or a conversion constant value to be used for the conversion calculations. You
can use any of the values listed above.
PERCENT=nnn Optional operand. Specifies a percentage of the primary extent allocation that
is to be used for the generated secondary extents.
If the JCL is being converted to operate on a new device type (OLDDEV and
NEWDEV parameters), the calculated percentage is based on the allocation
value of the primary extent after the device conversion calculations have been
performed.
SECNO=nnn Optional operand. Designates a number of secondary extents to be generated

for each sequential disk file. For SD only, any existing secondary extent
statements are dropped from the output JCL if this parameter is included.
Notes on the DYNCONV Program:
The input file must be assigned to SYS001.
The output is directed to SYSPCH.
Denote the end of the input by including a *END statement in the input job
stream.
5–4 User Guide

If the OLDDEV and NEWDEV parameters are specified as a device type,

the track/block capacity of that device is used as the device value for the
conversion.
The allocation value conversion is performed by calculating a capacity ratio

between the old and new device types. The number of tracks/blocks
specified on each input EXTENT statement is then multiplied by the
calculated conversion ratio.
The conversion ratio is computed by dividing the old device value by the
new device value.
Example 1:
Convert a job stream that operates on 3330 devices to run on 3310 FBA
devices. The computed conversion ratio is 25.45:1 (13030 / 512).
Input:
// JOB DYNCONV CONVERT JCL FOR FBA

// ASSGN SYS001,READER INPUT
// ASSGN SYSPCH,PUNCH OUTPUT
// EXEC DYNCONV
CONVERT OLDDEV=3330 NEWDEV=3310
// JOB PAYROLL WEEKLY RUN
// DLBL PAYIN,'COMPANY NO.5 PAYROLL MASTER IN',2099/365
// EXTENT SYS010,PAYPAK,1,0,5396,665
// DLBL PAYOUT,'COMPANY NO.5 PAYROLL MASTER OUT',2099/365
// ASSGN SYS010,DISK,VOL=PAYPAK,SHR
// DLBL TRNIN,'COMPANY NO.5 TRANSACTIONS'
// EXTENT SYS010,PAYPAK,1,0,1,380,19
// EXEC PAYUPD
/*
/&
*END
/*
/&

Output:
// JOB PAYROLL WEEKLY RUN

// DLBL PAYIN,'COMPANY NO.5 PAYROLL MASTER IN',2099/365
// DLBL PAYOUT,'COMPANY NO.5 PAYROLL MASTER OUT',2099/365
// ASSGN SYS010,DISK,VOL=PAYPAK,SHR
// DLBL TRNIN,'COMPANY NO.5 TRANSACTIONS'
// EXEC PAYUPD
/*
/&
Example 2:
You have determined that a 2:1 allocation ratio is required for the files in a job
stream. The files are already controlled by CA Dynam/D.
Input:
// JOB DYNCONV DYNAMIC JCL

// ASSGN SYS001,READER
// ASSGN SYSPCH,PUNCH
// EXEC DYNCONV
CONVERT OLDDEV=2 NEWDEV=1
// JOB EDIT RUN
// DLBL INPUT,'INPUT.TRANSACTIONS'
// DLBL OUTPUT,'EDITED.TRANSACTIONS'
// DLBL REJECTS,'EDIT.ERROR.TRANSACTIONS'
// EXEC EDITPROG
/&
*END
/&
Output:
// JOB EDIT RUN

// DLBL INPUT,'INPUT.TRANSACTIONS'
// DLBL OUTPUT,'EDITED.TRANSACTIONS'
// DLBL REJECTS,'EDIT.ERROR.TRANSACTIONS'
// EXEC EDITPROG
/&
5–6 User Guide

Example 3:
Convert a job stream to relative track/block 1 without performing the

conversion of number of tracks/blocks.
Input:
// JOB DYNCONV TO REL TRACK 1

// EXEC DYNCONV
// JOB UPDATE
// DLBL MASTER,'MASTER FILE INPUT',2099/365
// EXTENT SYS010,111111,1,0,19,38
// DLBL RPTS,'UPDATE REPORT FILE',0
// EXTENT SYS010,111111,1,0,57,19
// ASSGN SYS010,DISK,VOL=111111,SHR
// EXEC UPDPROG
/*
/&
// JOB PRINT UPDATE RPTS
// DLBL RPTS,'UPDATE REPORT FILE'
// EXTENT SYS010,111111,1,0,57,19
// EXEC REPORTS
/&
*END
/&
Output:
// JOB UPDATE
// DLBL MASTER,'MASTER FILE INPUT',2099/365
// EXTENT SYS010,111111,1,0,1,38
// DLBL RPTS,'UPDATE REPORT FILE',0
// EXTENT SYS010,111111,1,0,1,19
// EXEC UPDPROG
/*
/&
// JOB PRINT UPDATE RPTS
// DLBL RPTS,'UPDATE REPORT FILE'
// EXTENT SYS010,111111,0,1,1,19
// EXEC REPORTS
/&

Pre-Open Processing—DYNOPEN
The DYNOPEN utility program lets you pre-open a disk data set. It performs
basic CA Dynam/D and Catalog Management services for files that are to be
processed by other utility programs (such as IBM's DITTO or IDCAMS utilities).
It also supports programs that do not issue opens when restarting from
checkpoint.
These other utility programs access the label information and validate the
logical unit assignment of files to be processed before the files are actually
opened. DITTO and IDCAMS require the use of DYNOPEN. Without the use of
DYNOPEN, these types of programs can cancel because CA Dynam/D has not
been invoked to perform its open processing.
DYNOPEN provides the following services:
Dynamic creation of label information
Disk pool management
Automatic Volume Recognition and Assignment (AVR)
DYNOPEN can also be used to resolve labels for the IBM SORT product, SM2.
SM2 performs pre-open checking of volume serial number and extents for
input files, which is not compatible with CA Dynam/D catalog-controlled files,
POOL volume serial numbers, and AVR facilities, unless DYNOPEN is used.
Pre-open processing is performed by a dummy open call to CA Dynam/D.

Therefore, all CA Dynam/D processing is done for a file before the next OPEN
input statement is read.
OPEN Control Statement Syntax
The DYNOPEN program uses only one type of control statement, the OPEN
statement. Apply the following syntax rules to this statement:
Use free-form format starting in any position in the SYSIPT file.

Leave at least one space following the OPEN command.
Separate all operands by either a blank or a comma.
Exclude any comments from statements.
Do not continue any statements; positions 72—80 are ignored.
DYNOPEN normally reads input from SYSIPT. When the OPEN function is used
for SYSIPT, DYNOPEN must be directed to read its input from SYSRDR. The
use of UPSI 001 reassigns SYSIPT and causes the DYNOPEN OPEN function to
read its input from SYSRDR instead.
5–8 User Guide

This control statement has the following format:
OPEN FILE=dtfname [ UNIT=SYSxxx ]

[ MODE=INPUT|OUTPUT ]
[ TYPE=DA|SD|IS ]
[ DISK=dvctyp ]
OPEN Preopens a disk data set.
FILE=dtfname Defines the dtfname to be used for the file. This name must be the same as
the dtfname specified on the file's DLBL statement.
DISK= Optional operand. Defines the disk device type of the file. Valid parameters are
2311, 2314, 3310, 3330, 3340, 3350, 3370, 3375, 3380, 3390, and 9345. The
default is 3330.
MODE= Optional operand. Specifies if the file is to be input or output. INPUT causes
the existing file to be located. A specification of OUTPUT causes the file to be
allocated. This parameter defaults to INPUT.
TYPE= Optional operand. Defines the file's access method: SD (sequential), DA

(direct access), or IS (indexed sequential). The default value is SD.
UNIT=SYSxxx Optional operand. Defines the logical unit to be used for the file. It can be
specified as either a programmer or system logical unit:
where xxx must be less than 255
SYS001 is the default.
Notes about the OPEN control statement:

The input values are used to construct a DTF table for the appropriate
access method.
DYNOPEN prints control statements upon SYSLST only if // OPTION LOG is

in effect.
DYNOPEN normally reads its input from SYSIPT. The use of UPSI 001
causes DYNOPEN to read its input from SYSRDR instead.
Examples of Opening Files:
Open an SD input file using Catalog Management:
// DLBL MASTER,'PAYROLL.MASTER'
// EXEC DYNOPEN
OPEN FILE=MASTER UNIT=SYS011 MODE=INPUT TYPE=SD
/*

Open an ISAM output file with Catalog Management:
// DLBL ISFILE,'ACCT.FILE',10
// EXEC DYNOPEN
OPEN FILE=ISFILE MODE=OUTPUT TYPE=IS DISK=3340 UNIT=SYS002
/*
Examples of Restarting Files:
Restart trigger-driven multi-extent files:
// JOB EXAMPLE1
// DLBL UIN,'TEST.INPUT'
// EXTENT SYS040,335000,1,0,1,3
// EXTENT SYS040,335000,1,3,1,2
// DLBL UOUT,'TEST.OUTPUT'
// EXTENT SYS041,335001,1,0,1,3
// EXTENT SYS041,335001,1,1,1,2
// ASSGN SYS007,181
// TLBL CHKPT
// MTC REW,SYS007
// EXEC DYNOPEN,SIZE=DYNOPEN
OPEN FILE=UIN,UNIT=SYS040,MODE=INPUT
OPEN FILE=UOUT,UNIT=SYS041,MODE=INPUT
/*
// RSTRT SYS007,10,CHKPT
/*
/&
* $$ EOJ
Restart a catalog-controlled generation data set:
// JOB EXAMPLE2
* ADD CHECKPOINTED GDG #3 AS CURRENT VERSION FOR RESTART *
ADD 'TEST.OUTPUT.CAT' DISK VOL=335001 GDSID=03 VER=001
/*
// DLBL UIN,'TEST.INPUT.CAT'
// DLBL UOUT,'TEST.OUTPUT.CAT'
// ASSGN SYS007,181
// TLBL CHKPT
// MTC REW,SYS007
// EXEC DYNOPEN,SIZE=DYNOPEN
OPEN FILE=UIN,UNIT=SYS040,MODE=INPUT
OPEN FILE=UOUT,UNIT=SYS041,MODE=INPUT
/*
// RSTRT SYS007,10,CHKPT
/*
/&
* $$ EOJ
5–10 User Guide

Controlling Disk Files—DYNUTIL
Overview of DYNUTIL
DYNUTIL is a complete disk file maintenance utility program. The following

features highlight the capabilities of DYNUTIL:
change A file's expiration date
data secure A file
delete Any file
display Data files in hexadecimal or character format; the home address and count
fields of disk records
dump Any disk file or entire volume to tape.

Dump a specific, relative (G-nn), or absolute (G#nn) generation of a file to
tape.
Dump only the unexpired or permanent files on a disk volume to tape.
Dump a disk file to tape using the CA Dynam/D partition independence

(==) facility, the CPU ID (CPU—) facility, or both.
Dump a disk file from a volume defined in a CA Dynam/D pool.
open/close The tape file with such options as rewind, no rewind, as well as rewind and
unload
remove Data security for a file
rename Any disk file
restore A specific file or entire disk volume from tape to disk or a group of files
(generic) to disk
Error and warning messages issued by DYNUTIL are highlighted with the word
ERROR or WARNING on the far right side of the message.
Preparing to Use DYNUTIL
Before running DYNUTIL, CA Dynam/D must be initialized and active.
You can enter DYNUTIL commands from the operator console, if desired. If a
command function cancels, the next command is processed by DYNUTIL. You
can define all commands in a SYSIPT file, which is device-independent. Error
messages are directed to SYSLST, which is also device-independent.

Using UPSI JCL Statement
The Job Control statement // UPSI can be specified to designate the following
parameters for running DYNUTIL:
UPSI 1000000 DYNUTIL commands can be entered from the operator's console.
UPSI 0100000 If DYNUTIL cannot locate the volume specified in a VOL= parameter, it is to
search for a matching pool definition.
UPSI 00100000 The DYNUTIL program cancels in the event any function experiences an error.
UPSI 00010000 The DYNUTIL program cancels with a dump in the event any function
experiences an error.
UPSI 00001000 The DYNUTIL program will not access the Catalog to obtain GDG information if
this bit is on, unless the CATALOG parameter is also used.
UPSI 00000100 When the DYNUTIL DELETE command is specified for a GDG data set, the file
will be deleted, but the CADD567 message will not be issued.
UPSI 00000001 Reserved for internal use. Must be 0 for normal execution of DYNUTIL.
DYNUTIL Commands
The DYNUTIL program consists of the following commands:
ALTER Alter a file's expiration date or file ID.
CLOSE Close the DYNUTIL tape file with the selected options. (Optional command—
overrides defaults for file CLOSE.)
DELETE Delete a disk file from a VTOC.
DISPLAY Display a data file in hexadecimal or character format.
DUMP Dump a disk file or volume to tape.
LISTTAPE List the data set name of each file found on DYNUTIL-created tapes.
OPEN Open the DYNUTIL tape file with the selected options. (Optional command—
overrides defaults for file OPEN.)
REORG Restore SD files using dynamic disk space allocation.
RESTORE Restore disk files or volumes from a DYNUTIL created tape.
TAPE Rewind, rewind/unload, and back and forward space a DYNUTIL-created tape.
5–12 User Guide

TRACE Enable/disable DYNUTIL internal tracing facility.
A detailed explanation of each command is presented following the DYNUTIL

command syntax description.
DYNUTIL Command Syntax
Apply the following rules when specifying DYNUTIL commands:
Specify commands in free-form format beginning in any position on the

statement.
Leave at least one blank space following the command.
Separate all operands by one or more blanks.

Continuation statements can begin in any position on the next statement.
You can use a maximum of 3 of these statements. Continuations are
denoted by writing a space and a hyphen (-) as the last character on the
command line. Make sure not to split an operand between two statements.
For example, both of the following ALTER statements are acceptable:
ALTER 'OLD.FILE' CATALOG -

RENAME='NEW.FILE'
ALTER 'OLD.FILE' CATALOG RENAME='NEW.FILE'
Comments are not allowed on commands.
Default Information
Default information is listed in the following table:
Function Defaults For TLBL dtfname Logical Unit
DUMP DUMP SYS005
LISTTAPE RESTORE SYS006
REORG RESTORE SYS006
RESTORE RESTORE SYS006
ALTER Command
The ALTER command changes the expiration date, file ID of files, or both. You
can also data-secure or remove data security for a file.

{'file-id' } {CATALOG } {EXPDATE=[yy/ddd|yyyy/ddd] }[DSFON|DSFOFF ]

ALTER {'file-id*'} {POOL=poolid} {PERM }[PARTIAL ]
{'*' } {VOL=volser } {RETAIN }[RENAME='new file']
Required Parameter
The following operands are mutually exclusive:
'file-id' Identifies the file to be altered. Use the 44-character file identification for the
desired file. You can omit trailing blanks.
'file-id*' Indicates that all files starting with the file ID specified are to be altered.
'*' Requests that all files in the VTOC be altered.
Required Parameter
CATALOG Causes the Catalog to be searched to locate the data set. This greatly
improves efficiency because only the volume recorded in the Catalog as
containing the file will be searched.
VOL=volser Defines the six-character volume serial number of the disk volume to be
searched for the desired file. It can be a generic volser. For example,
VOL=WRK*** searches all volumes whose VOL1 begins with WRK.
POOL=poolid Defines the six-character serial number of the disk pool to be searched for the
desired file. The poolid specified must be defined as a virtual volume with the
COMPOOL option record.
Optional Parameter
EXPDATE=yy/ddd|yyyy/ddd
Changes the file's expiration date to the one you specify here (yy or yyyy is
the year, and ddd is a day of that year). To designate the file as expired,
specify an expiration date that is less than the current one. To extend a file's
retention period, increase the expiration date.
PERM Changes the file's expiration date to 2099/366.
RETAIN Changes the file's expiration date to 2099/365.
DSFON|DSFOFF Optional parameter. Enables/disables the data-secure feature for the file.
5–14 User Guide

PARTIAL Optional parameter for SD files only. Controls the alteration of disk files that
have multiple extents existing on multiple volumes. If either VOL= or POOL=
is specified for a file residing on multiple volumes, the ALTER will not complete
without the PARTIAL parameter. PARTIAL allows ALTER to complete even if
only a portion of the file resides on the specified volumes. If you omit
PARTIAL, only complete files will be altered (unless PARTIAL(NO) is defined in
the DYNAM/D option record).
PARTIAL has no effect when used with the CATALOG parameter.
Disk File Without|ALTER With |ALTER

Description PARTIAL|(Y/N) PARTIAL|(Y/N)
---------------- -------+------ -------+------
Single extent VOL= | Y VOL= | Y
single volume POOL= | Y POOL= | Y
| |
Multiple extents VOL= | Y VOL= | Y
| |
Multiple extents VOL= | N VOL= | Y
multiple volumes POOL= | N POOL= | Y
Y ALTER executes.
N ALTER does not execute; message CADD595 is displayed.
RENAME='new-file' Optional parameter. Redefines the file ID currently in the VTOC. The new file
ID must be enclosed within apostrophes. Do not specify RENAME= when using
a generic file ID; it could create duplicate file IDs in a VTOC.
Note: Error messages CADD566 and CADD567 are produced when DSFON is
specified and a file is found that has an expiration date of 2099/366 (PERM) or
is a data-secured file. The operator can respond with IGNORE, CANCEL or
BYPASS to these messages. For more information, see the Message Guide.
Examples:
Alter the expiration date of a file to 2099/366.
ALTER '==.WORK.FILE' VOL=WRKPAC PERM
Alter a file that resides in the pool DYNPAC to be expired.
ALTER 'OLD.TRANSACTIONS' POOL=DYNPAC EXPDATE=89/001
Alter all files on the pack WORK01 to be expired.
ALTER '*' VOL=WORK01 EXPDATE=89/001
Rename a file in the pool POOL02.

ALTER 'MASTER' POOL=POOL02 RENAME='EOM.MASTER'
Make the CA Dynam Catalog file data-secured.
ALTER 'INTEGRATED.DYNAM.CATALOG' VOL=RESPAC DSFON
CLOSE Command
The CLOSE command selects options for the tape file at close and writes the
EOF record. It must be specified to close the current tape data set before
opening a different tape (OPEN); otherwise, it is optional.
Use of this command is also necessary in order to place an end-of-file marker

on the tape and to perform the selected options. The CLOSE should be entered
after a series of DUMP or RESTORE commands in order to close the tape file.
If omitted, DYNUTIL defaults to REW and no tape release.
CLOSE dtfname ([REW|RUN|NORWD] [RELEASE])
dtfname Identifies the file name or DTFname of the tape file to be closed.
Optional Parameters
The following parameters are optional. REW, RUN, and NORWD are mutually
exclusive.
RELEASE Releases the logical unit assignment for the tape. The default is not to release
the assignment.
REW Rewinds the tape to load point (default option).
RUN Rewinds and unloads the tape.
NORWD Indicates that the tape is not to be rewound.
Notes on the CLOSE command:

The options defined within parentheses can be specified in any order and
must be separated by one or more blanks.
At the end of DYNUTIL processing (EOJ), any tape file that is currently
open is automatically closed with the default options.
Examples:
Dump all files to tape and selectively restore files as follows:
5–16 User Guide

X Restores all files whose expiration date is January 1, 1998, or greater.
Y Restores files beginning with the characters PAY from a different tape volume.
// JOB DUMPREST
// TLBL TAPE1
// ASSGN SYS009,281 TAPE ASSIGNMENT
// TLBL TAPE2
// ASSGN SYS019,283
// EXEC DYNUTIL
OPEN TAPE1 (OUTPUT REW SYS009)
DUMP VOL=WORK01
CLOSE TAPE1
OPEN TAPE1 (SYS009 REW INPUT)
RESTORE VOL=WORK01 EXPIRE=98/001 X
CLOSE TAPE1 (RUN)
OPEN TAPE2 (REW SYS019)
RESTORE 'PAY*' Y
CLOSE TAPE2
/*
/&
DELETE Command
The DELETE command deletes (completely eliminates) file IDs from the VTOC
of a disk volume.
DELETE { 'file-id' } { CATALOG } [ EXPIRE ]

{ 'file-id* ' } { POOL=poolid } [ PARTIAL ]
{ VOL=volser } [ PURGE ]
DELETE FILELBL=dtfname
Required Parameter
Operands are mutually exclusive:
'file-id' Specifies the 44-character file identification of the file to be deleted. You can
omit trailing blanks.
'file-id*' Represents the files whose VTOC entries are to be deleted. All file IDs
beginning with the characters specified here are deleted.
FILELBL=dtfname Specifies that the file is to be accessed using the label information found on
the DLBL of the indicated dtfname. Do NOT include any other parameters
when specifying FILELBL=dtfname.

If you use FILELBL with DLBL and EXTENT statements, you must include the
DYNAM TRIGGER value in the EXTENT statement.
Note: Error messages CADD566 and CADD567 are produced when file-id* is
specified and a file is found that is a permanent or data-secured file. The
operator can respond with IGNORE, CANCEL, or BYPASS to these messages.
For more information, see the Message Guide.
Optional Parameter
Operands are mutually exclusive:
CATALOG Causes the Catalog to be searched to locate the data set. This greatly
improves efficiency because only the volume recorded in the Catalog as
containing the file will be searched. If the file is not found in the volume
indicated by the Catalog, it will not be deleted.
POOL=poolid Identifies the six-character serial number of the disk pool to be searched to
locate the desired file. The poolid specified must be defined as a virtual volume
using the COMPOOL option record
VOL=volser Defines the six-character volume serial number of the disk volume containing
the file to be deleted. It can be specified as a generic volume serial number
when suffixed by asterisks.
EXPIRE Optional parameter. Deletes all expired files on the indicated volume.
PARTIAL Optional parameter for SD files only. Controls the deletion of disk files that
have multiple extents existing on multiple volumes or files that have never
been closed. If either VOL= or POOL= is specified for a file residing on multiple
volumes, the DELETE will not complete without the PARTIAL parameter.
PARTIAL allows DELETE to complete even if only a portion of the file resides on
the specified volumes. If you omit PARTIAL, only complete files will be deleted
(unless PARTIAL(NO) is set in the DYNAM/D option record).
PARTIAL has no effect when used with the CATALOG parameter.
Disk File Without|DELETE With |DELETE

Description PARTIAL|(Y/N) PARTIAL|(Y/N)
---------------- -------+------- -------+-------
Single extent VOL= | Y VOL= | Y
| |
Multiple extents VOL= | Y VOL= | Y
| |
Multiple extents VOL= | N VOL= | Y
multiple volumes POOL= | N POOL= | Y
5–18 User Guide

Y DELETE executes.
N DELETE does not execute; message CADD595 is

displayed.
PURGE Optional parameter valid with CATALOG only. This causes the catalog version
records, associated with the files being deleted by the DYNUTIL DELETE
function, to also be deleted.
Note: Use DYNPRINT VTOC to determine whether a file is not closed or has
multiple extents on other volumes.
Examples:
Delete a file from the WORK02 pack.
DELETE 'OLD.FILE' VOL=WORK02
Delete all payroll files (file-IDs that begin with PAY) that are contained in the
pool PAPOOL.
DELETE 'PAY*' POOL=PAPOOL
Delete all work files from all work packs.
DELETE 'WORK*' VOL=WORK**
DISPLAY Command
The DISPLAY command selectively displays records or an entire file in

hexadecimal or character format.
DISPLAY VOL=volser { EXTENT=(cc1,hh1,cc2,hh2) } [Option List]

{ PBN=(pbn1,pbn2,cisize) }
{ VTOC }
or
DISPLAY 'file-id' { CATALOG } [Option List]
{ POOL=poolid }
{ VOL=volid }
Required Positional Parameter
'file-id' Identifies the file to be displayed. Supply the 44-character file identification
code; you can omit trailing blanks.

VOL=volser Identifies the six-character volume serial number of the disk volume on which
the file resides. You can specify a generic volume serial number.
Required parameter for a file-id display
CATALOG Specifies that only the Catalog is to be searched for the file.
POOL=poolid Specifies a virtual serial number that has been defined as a CA Dynam/D disk
pool using the COMPOOL option record.
VOL=volid Identifies the six-character volume serial number of the disk volume on which
the file resides. This can be specified as a generic volume serial number when
suffixed with asterisks.
Required parameter for a VOL=display
All of the following operands are mutually exclusive:
EXTENT=(cc1,hh1,cc cc1,hh1 specifies the cylinder and head address at which to begin the
2,hh2) display.
cc2,hh2 specifies the ending disk address. If you do not supply the ending
address, cc2,hh2 is set to cc1,hh1, displaying only one track.
PBN=(pbn1,pbn2, cisize)
pbn1 specifies the physical block number at which to begin the display.
pbn2 specifies the ending pbn. If you do not supply the ending address, pbn2
is set to pbn1, displaying only one CI.
cisize specifies the control interval size. If you omit it, 512 is used.
If you supply a cisize, the pbn2 operand is required (can be equal to pbn1 if
you want to display only one CI).
Note: PBN can also be used for CKD devices and is then interpreted as a
relative track number.
VTOC Specifies that the entire VTOC is to be displayed.
The Option List shown that follows applies to both file-id and VOL=. You can
specify any or all operands in this list.
ALL Indicates that the operands CHAR, HA, COUNT, and HEX are all to be used.
CHAR Specifies that each record is to be displayed in character format.
5–20 User Guide

CHARSET= {48|60| Defines the printer character set to be used for the display.
ALL }
COUNT Specifies that the count portion of each record is to be displayed.
HA Specifies that the home address and record zero are to be displayed from each
track.
HEX Specifies that each record is to be displayed in hexadecimal format.
LRECL=nnnnn Defines the number of bytes in each logical record of a blocked file.
NORECS=nnnnnnnn Defines the number of records to be displayed.
SKIP Specifies that the SYSLST output is to be suppressed can be used to read the
home addresses for disk validity checking.
START=nnnnnnnn Specifies the first relative record number to be displayed.
TERM Specifies that the output is to be displayed on the operator console.
Notes on the DISPLAY command:

The first format of the display command (using Option List A) can only be
used when you know the exact location of the records to be displayed.
It is not necessary to supply leading zeros for the parameters START=,

NORECS=, and LRECL=.
Both HEX and CHAR can be specified to produce both a hexadecimal and
translated character format display (DEFAULT).
When displaying a specific file ID, all forms of partition, CPU

independence, or both, that are acceptable to CA Dynam/D can be used in
control statements. For more information, see Defining Independent Files.
Example
To display the first two records of the file, in hexadecimal format:
DISPLAY 'DISK.FILE' NORECS=2 HEX
DUMP Command
The DUMP command copies a disk file to tape. (For more information about
copying it back to disk, see the RESTORE command.)
Formats:
DUMP VOL=volser [ EXPIRE=[yy/ddd|yyyy/ddd] ]

[ EXCLUDE= ['file-id'|' file-id*']]

[ PERM ]
[ RETAIN ]
[ UNEXPIRED ]
DUMP { 'file-id' } { POOL=poolid } [ EXPIRE=[yy/ddd|yyyy/ddd] ]
{ 'file-id*' } { VOL=volid } [ EXCLUDE= [' file-id'|' file-id*']]
[ PERM ]
[ RETAIN ]
[ UNEXPIRED ]
DUMP { 'file-id' }CATALOG
{ 'file-id*'}CATALOG [ EXCLUDE= [' file-id'|' file-id*']]
Required parameter
These operands are mutually exclusive.
'file-id' Identifies the specific file ID for transfer to tape. You can select a specific
generation by identifying the relative generation number or absolute
generation number in parentheses, respectively (G-nn) or (G#nn). If a specific
generation is not specified, then the most current generation is accessed.
'file-id*' Identifies the group of file IDs for transfer to tape.
Note: If you specify file-id or file-id*, you must also specify a VOL=volid or
POOL=poolid.
VOL=volser Indicates the disk volume from which all files are selected for transfer to tape.
The volser must be specified as a six-character real volume serial number (a
pool or generic volume serial number is not allowed here). This is a full volume
dump.
CATALOG Specifies to DYNUTIL that only files with existing catalog versions should be
dumped. Specifying CATALOG on the dump action dumps all files with a
matching file-ID if they are found in the CATALOG only. DYNUTIL supports the
catalog option when used with the DUMP command.
Required Parameter for a file-id or file-id* Dump
Specify either VOL=volid or POOL=poolid.
POOL=poolid Specifies the six-character serial number that identifies a pool of disk volumes
from which to dump the indicated files. The pool is defined in the COMPOOL
option record.
VOL=volid Specifies the six-character serial number of the disk volume, such as SYSWK4,
or collection of disk volumes, such as SYS***, from which to dump the
indicated files.
5–22 User Guide

Optional Parameter
The optional parameters below are valid only if the CATALOG option is not
used.
If UNEXPIRED is combined with PERM, RETAIN, or EXPIRE, then UNEXPIRED

takes precedence. When PERM, RETAIN, and EXPIRE are specified together,
only those files satisfying all three conditions will be dumped. If none of these
operands (EXPIRE, PERM, RETAIN, UNEXPIRED) are specified, DYNUTIL selects
all files for transfer to tape.
EXPIRE=yy/ddd|yyyy/ddd
Dumps only files whose expiration date equals or exceeds the specified
expiration date (yy or yyyy is the year, and ddd is a day of that year).
PERM Dumps only files with an expiration date equal to the date specified by the
AUTODTE parameter of the DYNAM/D option record.
RETAIN Dumps only files with an expiration date equal to the date specified by the
MANDTE parameter of the DYNAM/D option record.
UNEXPIRED Dumps only those files whose expiration date equals or exceeds today's date.
Note on the DUMP command:
When dumping a specific file ID, all forms of partition, CPU independence, or
both, that are acceptable to CA Dynam/D can be used in control statements.
For more information, see Defining Independent Files.
EXCLUDE Specifies a file ID or group of file IDs to be excluded.
‘file-id’ Specific file ID to be excluded.
Note: If a specific generation other than the most current is to be excluded,

then the full 44 character file ID must be specified.
‘file-id*’ Generic group of file IDs to be excluded.
Examples
Dump a disk file to tape:
DUMP 'MASTER' VOL=PERM02
Dump the father generation of the file to tape:
DUMP 'MASTER(G-1)' VOL=WORK**

Dump a partition-independent, CPU-independent file and search all disk

volumes for the file:
DUMP 'MASTER==CPU--' VOL=******
Dump an entire volume to tape:
DUMP VOL=CKD019
Dump a file defined in the CA Dynam/D pool CKDVOL:
DUMP 'PAYROLL*' POOL=CKDVOL
Dump all files on a volume with an expiration date of January 1, 1993 or

greater to tape:
DUMP VOL=PERM02 EXPIRE=1993/001
Dump all unexpired files on a volume to tape:
DUMP VOL=CKD001 UNEXPIRED
Given a DYNAM/D option record with AUTODTE(2099360), dump all files with
an expiration date of 2099/360:
DUMP VOL=CKD002 PERM
Dump all files with an expiration date equal to or greater than January 23,
2000.
DUMP VOL=CKD019 EXPIRE=00/023
LISTTAPE Command
The LISTTAPE command lists the data set names of all files found on tapes
created by DYNUTIL.
LISTTAPE (has no associated operands.)
Example
// JOB LISTTAPE
// ASSGN SYS006,281
// TLBL RESTORE,'file-id'
// EXEC DYNUTIL,SIZE=128K
LISTTAPE
/*
/&
5–24 User Guide

OPEN Command
The OPEN command selects options for the tape file to be dumped/restored.
This command is only necessary to override default options for processing the
tape. Otherwise, the open will take place on the first DUMP, RESTORE, REORG,
or LISTTAPE command encountered, using the default file name and logical
unit. For more information, see Overview Of DYNUTIL.
OPEN dtfname ([REW|NORWD] [SYSnnn] [HDRINFO] [INPUT|OUTPUT])
dtfname Identifies the file name or DTFname of the tape file to be opened. A TLBL
statement must be included in the job stream for this file name.
Optional Parameters
The following parameters are optional. REW and NORWD are mutually
exclusive.
REW Rewinds the tape to load point (the default option).
NORWD Indicates that the tape is not to be rewound.
SYSnnn Specifies the logical unit to be used in assigning the tape. If omitted, the
default is SYS005 for dtfname DUMP and SYS006 for all other dtfnames.
HDRINFO Prints information related to the standard labeled tape on SYSLOG. If this is
desired, you must specify HDRINFO, because it is not the default.
INPUT Opens the tape file for input prior to the RESTORE, REORG, or LISTTAPE
function. It is the default.
OUTPUT Opens the tape file for output prior to the DUMP function. Overrides the
default, INPUT.
Notes on the OPEN command:

The options defined within parentheses can be specified in any order and
must be separated by one or more blanks.
The OPEN and CLOSE commands are provided to allow user control of tape
data sets. This allows usage of any number of tape files during a single
execution of DYNUTIL.
If you issue an OPEN immediately following a CLOSE (rewind), you can get
message CADT004 requesting a volume mount. This occurs because OPEN
AVR processing starts while the REWIND is still in progress. Wait until the
rewind is complete and then reply END/ENTER.

Note: For more information about a way to circumvent this problem globally,
see the STOP option of the DYNAM/T option record.
Examples
Dump all files to tape and selectively restore files as follows:
X Restores all files whose expiration date is January 1, 1998, or greater.
Y Restores files beginning with the characters PAY from a different tape volume.
// JOB DUMPREST
// TLBL TAPE1
// ASSGN SYS009,281 TAPE ASSIGNMENT
// TLBL TAPE2
// ASSGN SYS019,283
// EXEC DYNUTIL
OPEN TAPE1 (OUTPUT REW SYS009)
DUMP VOL=WORK01
CLOSE TAPE1
OPEN TAPE1 (SYS009 REW INPUT)
RESTORE VOL=WORK01 EXPIRE=98/001 X
CLOSE TAPE1 (RUN)
OPEN TAPE2 (REW SYS019)
RESTORE 'PAY*' Y
CLOSE TAPE2
/*
/&
REORG Command
The REORG command restores files (specifically or generically) from a tape

created by a DYNUTIL DUMP command. CA Dynam/D automatically determines
placement of the files. Only SD-type files can be processed; others are
bypassed with a diagnostic message. Generation data sets (GDSs) are fully
supported. By default they are restored in the original sequence, but options
make it possible to restore them as new versions or replacing old versions out
of the original sequence.
File renaming is supported by the FILELBL/NONAMECH mechanism familiar to

experienced users. A new, easier renaming method using the NEWDSN=
parameter has been added. Migration to new disk volumes, which can be of a
different device type, is also supported. In the case of catalog-controlled files,
the CONVERT option lets you automatically update the Catalog entry for the
migrated files so that new versions will always be created on the new
volume/device type.
5–26 User Guide

You can perform six distinctive types of REORGs, each having a different
purpose and format. They are listed in the following table:
To Use
Method
Do a basic REORG 1
Migrate files to another volume or device type 2
Restrict a basic REORG to GDS files only 3
REORG as a new version of an existing GDS 4
Replace an existing version of an existing GDS 5
Base the REORG on production-JCL applications 6
Methods and Command Formats
Following are descriptions of the various methods and their associated

command formats.
Method 1: This is the basic REORG. Files are restored to the original volume regardless of
whether they are GDS files. In this format, the required file-id parameter and
the CATALOG/NONCATAL options let you select files from the tape to be
processed. The NEWDSN= option is permitted and allows files to be restored
under a new or modified name using the REORG command
REORG { 'file-id' } [ CATALOG|NONCATAL ]

{ 'file-id*' } [ NEWDSN= {'dsn'|'dsn*'|'*' } ]
{ '*' }
Method 2 Use this method to migrate files to another volume or device type. Required
for this method are the file-id and VOL= and/or POOL= parameters;
CONVERT/NONCATAL and NEWDSN= are optional. The file-id allows selection,
as does the NONCATAL option. The VOL=/POOL= parameter identifies the
target volumes for the REORG. CONVERT also causes the file allocation
information in the Catalog to be modified as appropriate for the new device
type. NEWDSN= allows renaming.
REORG { 'file-id' } { VOL=volser } [ CONVERT|NONCATAL ]

{ 'file-id*' } { POOL=pool-id } [ NEWDSN= {'dsn'|'dsn*'|'*' } ]
{ '*' }

Method 3 Essentially, the same as Method 1, but this method restricts processing to
generation-type files only. All of these parameters are required for this
method. Renaming is not supported.
REORG { 'file-id' } GDS=ORIGINAL CATALOG

{ 'file-id*' }
{ '*' }
Method 4 Use this method when the target file is to be a new version of an existing GDS.
The selected input file does not have to be a GDS version. Each of these
parameters is required here except NEWDSN=, the option that allows
renaming.
REORG 'file-id' GDS=NEW CATALOG [ NEWDSN= {'dsn'|'dsn*'|'*' } ]
Method 5 When the target file is to replace an existing version of an existing GDS, use
this method. The selected input file does not have to be a GDS version. Each
of these parameters, including NEWDSN=, is required for this format.
NEWDSN= identifies the version to replace, and can also be used to support
renaming.
REORG 'file-id' GDS=REPLACE CATALOG NEWDSN= { 'dsn' }

{ 'dsn*' }
{ '*' }
{ '*(G-nn)' }
{ '*(G#nn)' }
{ 'dsn(G-nn)' }
{ 'dsn(G#nn)' }
{ 'dsn*(G-nn)' }
{ 'dsn*(G#nn)' }
Method 6 This method is provided for convenience in certain production-JCL applications.

The only optional parameter is NONAMECH, which lets you change the name of
the REORG file.
REORG 'file-id' FILELBL=dtfname [ NONAMECH ]
Required Parameters
One of the parameters - file-id, file-id*, or ‘*’ - must be specified on the

REORG command to indicate which files on the input tape are to be processed.
CATALOG and NONCATAL are mutually exclusive:
'file-id' Identifies a specific file to be processed. It can include a relative or absolute

generation specification as:
file-id(G-nn) or file-id(G#nn).
If file-id belongs to a generation-type file and no generation is specified, the

current (most recent) generation is selected.
5–28 User Guide

Note that the following forms are not valid together with GDS=NEW or
GDS=REPLACE.
'file-id*' Identifies a group of files to be processed, all with file-id as the initial
characters. If any generation-type file is encompassed in the specification, all
generations on the tape are selected.
'*' All files on the tape are selected for processing.
CATALOG Only those selected files that are in the Catalog at the time the REORG
command is invoked are processed. This option applies to Method 1. If neither
CATALOG nor NONCATAL is specified in Method 1, all files selected by the file-
id, file-id* or '*' parameter are processed.
CONCATEX When specified will force DYNUTIL to create just one extent when a multi-
extent file is being restored using the REORG command. The number of tracks
specified on the single extent will be calculated by adding up all the tracks
specified for all the extents.
CONVERT Specifies that the allocation control information in the Catalog (for selected,
catalog-controlled files) is to be converted to reflect the new specific or generic
volid or pool-id. If the new location reflects a change in device type, the
amounts of space to be allocated are recalculated accordingly.
For generation-type files, CONVERT processing takes place only once, when
the current (most recent) version of the file is restored using the REORG
command.
CONVERT does not prevent non-catalog-controlled files from being processed,

but no catalog processing is done for them.
This option applies to Method 2.

FILELBL= Specifies the dtfname of a DLBL(/EXTENT) statement in the DYNUTIL (or a

previous) job step. The allocation information on that DLBL/EXTENT is used to
place the file being restored using the REORG command. Depending on the
format of the DLBL(/EXTENT) the resulting file will be catalog-controlled, CA
Dynam/D-controlled, or completely user-controlled.

By default, the file-id on the DLBL is ignored and the file-id from the tape is
used. If the DLBL implies Catalog control but the selected file-id is not catalog-
controlled, the REORG will not take place.
Note that FILELBL= is not permitted with file-id* or '*'.
GDS= Used to manipulate version sequencing in generation-type files (GDSs). Only

valid, and only applicable, when the target file of the REORG is a (version of a)
GDS. The CATALOG parameter is always required with GDS=.
ORIGINAL Specifies that any GDS version selected will be restored

in its original sequence. This is the same as what
happens if GDS= is omitted, except that if you specify
GDS=ORIGINAL, DYNUTIL requires that you specify
CATALOG as well, and only GDS versions are processed.
NEWDSN= is not permitted with GDS=ORIGINAL.
NEW Indicates that the target file for processing is to be a new

version. The REORG will take place only if the target file
(either the selected file or some other file specified using
NEWDSN=) has been defined in the Catalog as a GDS.
REPLACE Specifies that the target file for processing is a specific

existing version of the target GDS. You must include
NEWDSN= when specifying GDS=REPLACE to identify the
version you want, and the file-id (if different from the
selected file).
Note that GDS=NEW and GDS=REPLACE are not permitted together with file-
id* or '*'.
NEWDSN= Specifies a different file-id (other than the one by which the file is selected
from the input tape) created by the REORG. Additionally, when used with
GDS=REPLACE, specifies the target version.
'dsn' The selected file is restored under the name dsn using
the REORG command If GDS=NEW is specified, the
selected file is restored as the newest version of dsn, and
the oldest version is deleted. If GDS=REPLACE is
specified, the selected file is restored to replace the
current version of dsn.
'dsn*' The selected files are restored using the REORG

command under names created by concatenating dsn
with the file-id on the tape. For example, if
NEWDSN=BACKUP.* and a file PAYROLL is selected from
the tape, the file-id of the target file becomes
BACKUP.PAYROLL.
5–30 User Guide

'*' The selected file is restored using the REORG command,

replacing the current (most recent) version of itself.
The following forms are valid only with GDS=REPLACE.
'*(G-nn)' The selected file uses the REORG command to replace the
nnth relative version of itself.
'*(G#nn)' The selected file uses the REORG command to replace the
version of itself having absolute generation number nn.
'dsn(G-nn)' The selected file uses the REORG command to replace the
nnth relative version of the GDS called dsn.
'dsn(G#nn)' The selected file uses the REORG command to replace the
version of the GDS called dsn that has absolute version
number nn.
'dsn*(G-nn)'
'dsn*(G#nn)' The selected file uses the REORG command under a

modified file-id as described above for dsn*; the part
after the asterisk specifies the target version to be
replaced as described above for *(G-nn) and *(G#nn).
NONAMECH Specifies that the file uses the REORG command using the file-id on the DLBL,
to rename the file from the input tape.
This parameter is only permitted in conjunction with FILELBL=. No other

parameters are permitted with FILELBL=.
To restore a file to a specific volume within a pool, using the REORG

command, both VOL= and POOL= can be specified.
NONCATAL Only those selected files that are NOT in the Catalog at the time of the REORG
will be processed. This option applies to Method 1 and Method 2. If neither
CATALOG nor NONCATAL is specified in Method 1, all files selected by the
file-id, file-id* or '*' parameter are processed.
POOL=pool-id Specifies a CA Dynam/D pool-id to which the selected files are restored using
the REORG command.
VOL=volser Specifies the disk or disks to which the selected files are restored using the
REORG command. Can be a specific volid (six alphanumeric characters) or a
generic one (less than six alphanumeric characters padded out to six with
trailing asterisks).

Notes on REORG Command
Label Records, Message Routing, and Tapes
DYNUTIL dynamically constructs label records (DLBL/EXTENT) for each

extent selected from the input tape (except when Method 6 is used), and
invokes CA Dynam/D by performing an open.
The CATALOG option causes the label records to be constructed without

EXTENT information, thereby placing the files being processed under
Catalog control. The target files must first be defined in the Catalog; if
they are not, no REORG occurs.
If REORG is run from SYSIPT, many of the messages it issues appear only
on SYSLST. When it is run from the console, all messages appear on both
SYSLST and SYSLOG. All CA Dynam/D messages resulting from REORG
activity are issued in accordance with the options specified in the
DYNAM/D option record.
You can use the DYNUTIL LISTTAPE command to produce a formatted

listing of the tape’s contents to verify the order of the files on the tape.
REORG Processing
When using any of the options CATALOG, NEWDSN=, FILELBL or

CONVERT, only complete files are processed. Incomplete files are
bypassed with a diagnostic message.
When files dumped from an FBA device are restored to a non-FBA device
using the REORG command, they must have the CISIZE in the original
Format-1 label. The files without the CISIZE are bypassed with a
diagnostic message.
When an existing catalog-controlled file is restored using the REORG

command, the Catalog entry giving its location is updated to reflect the
new situation. This can only be relied upon, however, if the REORG
completes successfully and without error messages.
Whenever a catalog-controlled file (or an extent of one) is restored using

the REORG command, the original file or extent is automatically deleted
from the volume where it resided. Where the file is being renamed by use
of NEWDSN= or NONAMECH, the original file is not deleted but the target
file is, if it is catalog-controlled. Noncatalog-controlled files (or extents) are
deleted only if they are restored to the original volume using the REORG
command.
DYNUTIL searches the input tape in the forward direction only. If you issue
multiple REORG commands in one job, be sure the files you request in the
REORG command selection criteria are in the same order as they appear
on the tape. Otherwise, you must close and reopen the tape between
REORG commands.
5–32 User Guide

While the CATALOG|NONCATAL option applies to Method 1,

CONVERT|NONCATAL applies to Method 2.
If neither CATALOG nor NONCATAL is specified in Method 1, all files

selected by the file-id, file-id* or '*' parameter are processed.
Examples
Restore all sequential files on the input tape using the REORG command. All
files will be written back to the volume they were backed up from:
REORG '*'
Using the REORG command, restore files whose names begin with SALARY
moving them to volume ADMIN1:
REORG 'SALARY*' VOL=ADMIN1
Using the REORG command, restore a file using its Catalog definition:
REORG 'CATS.AND.DOGS' CATALOG
Using the REORG command, restore a file moving it into the PAYROL pool:
REORG 'TIME.IS.MONEY' POOL=PAYROL
Select a file PAYROLL.MASTER from a backup tape and restore it to the CA

Dynam/D pool POOL01 using the REORG command, and change its name to
OLD.PAYROLL.MASTER:
// JOB RENAME
// TLBL RESTORE,'dsn'
// ASSGN SYS006,tape
// DLBL NEWFILE,'OLD.PAYROLL.MASTER'
// EXTENT ,POOL01,1,0,1,40
REORG 'PAYROLL.MASTER' FILELBL=NEWFILE NONAMECH
/*
/&
Select a file PAYROLL.MASTER from a backup tape and use the REORG
command to restore it to disk, change its name to OLD.PAYROLL.MASTER, and
use CA Dynam Catalog control to locate and create the target file:
// JOB RENAME
// TLBL RESTORE,'dsn'
// ASSGN SYS006,tape
// DLBL NEWFILE,'OLD.PAYROLL.MASTER'
REORG 'PAYROLL.MASTER' FILELBL=NEWFILE NONAMECH
/*
/&

Examples
Assume the Catalog contains a GDS called STOCK with NGEN=3. Assume
further that there is a GDS called ALT.STOCK with NGEN=3, and two non-GDS
files called NOT.A.GDS and ALSO.NOT.A.GDS. The contents of the backup tape
are as follows:
STOCK(G#13) STOCK(G#11) NOT.A.GDS STOCK(G#12)
Using the REORG command, restore the current version from the tape as a
new current version:
REORG 'STOCK' CATALOG GDS=NEW CA Dynam Catalog
Before: STOCK - NGEN=3 - G#13 -> G#12 -> G#11

After: STOCK - NGEN=3 - G#14 -> G#13 -> G#12
|
+------------------ G#13 from backup
Note that if (G#14) had already been created, DYNUTIL would issue a
message that the requested file was not on the tape, and no processing would
take place.
Using the REORG command, restore the (G-2) version from the tape as the
new current version; in this example (G#14) has already been created, so (G-
2) is (G#12):
REORG 'STOCK(G-2)' CATALOG GDS=NEW CA Dynam Catalog

|
+------------------ G#12 from backup
Using the REORG command, restore the (G#11) version from the tape as the
new current version:
REORG 'STOCK(G#11)' CATALOG GDS=NEW CA Dynam Catalog

|
+------------------ G#11 from backup
5–34 User Guide

Using the REORG command, restore the (G#11) version from the tape in its
original sequence:
REORG 'STOCK(G#11)' CATALOG GDS=ORIGINAL (GDS=ORIGINAL optional) CA

Dynam Catalog

|
+-- G#11 from backup
Note that if G#14 had already been created, DYNUTIL would issue a message
that the requested target file was no longer current, and no processing would
take place.
Using the REORG command, restore all versions from the tape in their original
sequence:
REORG 'STOCK*' CATALOG GDS=ORIGINAL (GDS=ORIGINAL optional) CA

Dynam Catalog

| |
| |
| +-- G#12 from backup
+---------- G#13 from backup
Note that G#14 is not processed because it is not found on the tape, and
G#11 is bypassed because it is no longer current.
Using the REORG command, restore the (G#12) and (G#13) versions in
reversed sequence:
REORG 'STOCK(G-1)' CATALOG GDS=REPLACE NEWDSN='*(G-2)'

REORG 'STOCK(G-2)' CATALOG GDS=REPLACE NEWDSN='*(G-1)' CA Dynam Catalog

| |
| |
| +-- G#13 from backup
+---------- G#12 from backup
Note that the REORG commands could not be given in the reverse order unless
the tape were closed and reopened between them; DYNUTIL only searches the
tape in the forward direction.

Using the REORG command, restore the (G#12) version as the (G-1) version
of ALT.STOCK:
REORG 'STOCK(G#12)' CATALOG GDS=REPLACE NEWDSN='ALT.*(G-1)' CA Dynam Catalog

ALT.STOCK - NGEN=3 - G#76 -> G#75 -> G#74
ALT.STOCK - NGEN=3 - G#76 -> G#75 -> G#74
|
+------ G#12 from backup
Note that the result would be the same for NEWDSN=ALT.STOCK(G-1).
Using the REORG command, restore the file NOT.A.GDS as the current version
of STOCK:
REORG 'NOT.A.GDS' CATALOG GDS=NEW NEWDSN='STOCK' CA Dynam Catalog

|
+------------- NOT.A.GDS from backup
Note that GDS= is required in the command because the target file is a GDS,
even though the file selected from the tape is not.
Using the REORG command, restore version (G#13) of STOCK as file

NOT.A.GDS:
REORG 'STOCK(G-1)' CATALOG NEWDSN='NOT.A.GDS' CA Dynam Catalog

NOT.A.GDS - file
|
+----------- STOCK(G#13) from backup
Note that GDS= is omitted from the command because the target file is not a
GDS even though the file selected from the tape is.
Using the REORG command, restore the file NOT.A.GDS as file

ALSO.NOT.A.GDS:
REORG 'NOT.A.GDS' NEWDSN='ALSO.*' CATALOG (CATALOG is optional)
5–36 User Guide

STOCK(G#14) has been created but you find it contains corrupted data and
you want to restore the situation at the time of the backup so you can rerun
the production job:
REORG 'STOCK(G#13)' CATALOG GDS=REPLACE NEWDSN='*'

REORG 'STOCK(G#11)' CATALOG GDS=REPLACE NEWDSN='*(G-2)'
REORG 'STOCK(G#12)' CATALOG GDS=REPLACE NEWDSN='*(G-1)' CA Dynam Catalog

| | |
| | +-- G#11 from backup
| +---------- G#12 from backup
+------------------ G#13 from backup
Note:
The absolute generation numbers have now all slipped forward by one. But
to the production job JCL, which uses relative generation numbers, the
situation is indistinguishable from what applied when the DUMP tape was
created.
Again, the REORG commands are issued in an order corresponding to the

order of the files on the backup tape.
This reconstruction could be done using more than one backup tape if that
were necessary. For more information, see the OPEN and CLOSE
commands.
RESTORE Command
The RESTORE command copies back to disk those files that were previously
dumped to tape with DYNUTIL's DUMP command.
This command has the following formats:
RESTORE VOL=volser [ OLDVOL=xxxxxx ]

[ EXCLUDE= [' file-id'|' file-id*']]
[ EXPIRE=[yy/ddd|yyyy/dd] ]
[ PERM ]
[ RETAIN ]
[ UNEXPIRED ]
[ REPLACE ]
RESTORE { 'file-id' } [ EXPIRE=[yy/ddd|yyyy/ddd]]
{ 'file-id*' } [ EXCLUDE= [' file-id'|' file-id*']]
[ PERM ]
[ RETAIN ]
[ UNEXPIRED ]
[ REPLACE ]

These operands are mutually exclusive:
'file-id' file-id* Identifies the specific file ID or group of file IDs to be selected from the
tape volume and restored. Each file is restored to its original extents.
For generation data sets, you must specify the desired generation by
indicating its absolute generation number in parentheses, such as (G#nn).
VOL=volser Restores all files from the tape to the specified disk volume. The volser must
be specified as a six-character real volume serial number. A pool or generic
volume serial number is not allowed. This is a full volume RESTORE command.
Optional Parameters
These operands are optional and mutually exclusive except OLDVOL and
REPLACE, which are also optional but can be used with any one of the others.
If the UNEXPIRED command is combined with PERM, RETAIN, or EXPIRE, then
the UNEXPIRED command takes precedence. When PERM, RETAIN, and
EXPIRE are specified together, only those files satisfying all three conditions
are restored. If none of these operands (EXPIRE, PERM, RETAIN, UNEXPIRED)
are specified, DYNUTIL selects all files for transfer to tape.
EXPIRE=yy/ddd|yyyy/ddd
Restores only those files whose expiration date equals or exceeds the specified
expiration date (yy or yyyy is the year, and ddd is a day of that year).
PERM Restores only files with an expiration date equal to the date specified in the
AUTODTE parameter of the DYNAM/D option record.
RETAIN Restores only files with an expiration date equal to the date specified in the
MANDTE parameter of the DYNAM/D option record.
UNEXPIRED Restores only those files whose expiration date is the same as or exceeds the
current date.
OLDVOL=xxxxxx Restores files to the same physical location that they occupied on the old
volume. The original volume serial number from which the disk files were
dumped is indicated by xxxxxx. It is used only when the DUMP disk volume
serial number differs from the RESTORE disk volume serial number. It can only
be used for a full volume RESTORE; the input tape must be a full volume
DUMP tape. And, the old and new DASD devices must be of the same type.
REPLACE Causes each file on the tape to automatically overwrite the disk file of an equal
file ID. If you omit this parameter and an equal file ID exists on the VTOC, the
following message is issued and the file is not changed:
CADD548E DUPLICATE FILE-ID ON VOLUME=xxxxxx
5–38 User Guide


Notes on the RESTORE command:

When restoring a specific file ID, all forms of partition, CPU independence,
or both, that are acceptable to CA Dynam/D can be used in control
statements. For more information, see Defining Independent Files.
The RESTORE function can be used to retrieve individual file IDs or to

retrieve a group of file IDs from a full volume DUMP tape. An asterisk (*)
can be included as part of the file ID to restore a generic group of file IDs
from tape. For example, the file ID MAST* restores all files from the tape
whose first four characters are MAST.
If the file ID to be restored overlaps an existing file, the error message

CADD550 appears and the file is not restored.
On a full volume RESTORE, a new disk volume can be specified; however,

the device type must not change.
Restoring a single file ID, file-id, or group of file IDs, file-id*, to a different
disk volume is not supported by the RESTORE command. In these cases,
use the REORG command.
If the file ID to be restored already exists on the volume and the REPLACE
command has been omitted, then the error message CADD548 is issued
and the file is not restored.
Examples
Restore a specific disk file:
RESTORE 'MASTER'
Restore a group of disk files:
RESTORE 'DAILY.*'
Restore all files to the original disk volume:
RESTORE VOL=CAIDSK
Restore a generation disk file:
RESTORE 'MASTER.FILE(G#02)' REPLACE

Restore all files to a different disk volume of the same device type:
DUMP VOL=T3380A
RESTORE VOL=T3380G OLDVOL=T3380A
TAPE Command
The TAPE command rewinds, rewinds and unloads, backspaces and forward
spaces a tape.
TAPE SYSnnn { BSF }

{ (BSF n) }
{ FSF }
{ (FSF n) }
{ REW }
{ RUN }
SYSnnn Specifies the logical unit you want assigned to the tape drive. If omitted, the
default is SYS005 for a DUMP function and SYS006 for a RESTORE function.
BSF Backspaces the tape past one tapemark.
(BSF n) Backspaces the tape past n tapemarks.
FSF Forward spaces the tape past one tapemark.
(FSF n) Forward spaces the tape past n tapemarks.
REW Rewinds a tape.
RUN Rewinds and unloads the tape.
Note:
You should issue the TAPE command only while the target logical unit is
closed (prior to the first OPEN or after a CLOSE and before the next
OPEN).
The DUMP command creates standard-labeled files, so for each set of

OPEN|DUMP|CLOSE commands, three physical files are written to the
tape.
After a CLOSE command for OUTPUT (DUMP command), the tape is

positioned following the tapemark that closes the trailer label of the last
file written.
5–40 User Guide

After a CLOSE command for INPUT (RESTORE, REORG, LISTTAPE

commands), the tape is positioned to read the trailer label of the last file
read.
To position the tape correctly when backspacing, it is necessary to BSF for

the desired number of files plus one (+1), and then FSF once to pass over
the last tapemark found.
When creating or reading multifile DYNUTIL tapes, you can simplify

operation considerably if you avoid CA Dynam/T intervention either by
disabling CA Dynam/T, or by using a form of TLBL that bypasses CA
Dynam/T processing.
Examples
Write more than one DUMP to a single tape file.
DUMP 'TEST*' VOL=SYSWK1

DUMP 'UTIL*' VOL=PROD01
Write more than one DUMP to successive separate tape files.
DUMP 'TEST*' VOL=SYSWK1

CLOSE DUMP (SYS005 NORWD)
OPEN DUMP (SYS005 NORWD OUTPUT)
DUMP 'UTIL*' VOL=PROD01
LISTTAPE from the second DUMP file on a tape.
TAPE SYS006 (FSF 3)

OPEN RESTORE (SYS006 NORWD)
LISTTAPE from the first two DUMP files on a tape.
LISTTAPE
CLOSE RESTORE (SYS006 NORWD)
TAPE SYS006 FSF
OPEN RESTORE (SYS006 NORWD INPUT)
LISTTAPE
LISTTAPE from the fourth and then the second DUMP files.
TAPE SYS006 (FSF 9)

LISTTAPE
CLOSE RESTORE (SYS006 NORWD)
TAPE SYS006 (BSF 9)
TAPE SYS006 FSF

Reporting on Disk Files
LISTTAPE Write a DUMP as the third file on an existing DUMP tape.
TAPE SYS005 (FSF 6)

OPEN DUMP (SYS005 NORWD OUTPUT)
DUMP 'PAYROLL*' CATALOG
TRACE Command
The TRACE command prints a snap dump in trace fashion after certain
operations within DYNUTIL. The DATA operand produces large quantities of
output and should be used only at the request of CA Technical Support
personnel.
TRACE { CATLIO } [DATA]
{ DISKIO }
{ TAPEIO }
{ VTOCIO }
{ ALL }
{ OFF }
CATLIO, DISKIO, TAPEIO, VTOCIO

Defines the specific event to be traced: Catalog input/output, disk
input/output, tape input/output, or VTOC input/output, respectively. These
operands are mutually exclusive.
ALL Requests all events to be traced.
OFF Turns the trace off.
DATA Provides SNAP dumps of the data buffers for each I/O.

CA Dynam supplies the following standard, precompiled reports to assist you
in the management of disk files:
Disk Space Usage Analysis—SPACEUSE
Volume Table Of Contents—VTOCS
The SPACEUSE report informs you of the relative efficiency with which disk
space is being used. It helps optimize space utilization and system
performance by identifying badly blocked or allocated files. Data is retrieved
from system VTOCs in VTOC sequence by volume.
5–42 User Guide

The VTOCS report provides information about disk occupancy. Data can relate
to all mounted volumes, to all volumes in a pool, to generic volumes, or to a
specific real volume. One scan of all selected VTOCs can produce multiple
reports. Data is retrieved from system VTOCs in VTOC sequence by volume.
To enhance their capabilities, several options are available for each of these
reports. Complete descriptions are provided on the following pages.
Disk Space Usage Analysis—SPACEUSE
The SPACEUSE report is a standard, VTOC-based DYNPRINT report supplied

with CA Dynam. It helps you improve disk space utilization and disk file
performance by identifying files that are inefficiently blocked or inaccurately
allocated. Reports are restricted to disk files only.
Print in five different sort orders, including those that highlight files that
were badly blocked or badly allocated.
Report on both over-allocation and under-allocation analysis.
Determine actual maximum potential gain from reblocking files.
Establish a common unit of measurement for sorted output, to compare

space usage of different device types (including FBA).
Limit the report to an arbitrary number of files, to include only the worst
offenders.
Restrict the report to a generic group of volumes or to the space in a CA

Dynam/D disk pool.
SPACEUSE supersedes the older DYNSPACE report. It takes full advantage of

the most recent CA Dynam/D VTOC management features. Information is
presented in an easily interpreted form.
Invoking the Report
Use the following DYNPRINT command sequence to invoke SPACEUSE:
ACCESS VTOC
REPORT SPACEUSE [ BANNER ]
[ EROPT ]
[ MAXLINES ]
[ MAXRETR ]
[ SELECT= {option[,option..] } ]
[ VOL ]

SPACEUSE options and their application, see the chapter "General Reporting—
DYNPRINT."
SELECT Options The SELECT options for SPACEUSE are all sort-order options. Any or all of
them can be used to produce up to five reports from one command. They are:
FIDEXT Files are reported by file-id. Within each file-id, files are reported in order of
the first extent sequence number of an extent in, or overlapping, each real
volid or defined pool space. This is the default option if the SELECT option is
omitted.
REALLOC Files are reported by descending absolute percentage error in the original
allocation request.
REBLOCK Files are reported by descending number of bytes to be gained by changing to

optimum blocking.
VOLFID Files are reported by real volid and, within each volume, by file-id. If a file
spans more than one defined pool space on a volume, a line is reported for
each space summarizing the extents in, or overlapping, that space.
VTOCSEQ Files are reported on in order of VTOC retrieval.
SELECT=ALL prints all of the first four reports, omitting the VTOCSEQ report.
By invoking SPACEUSE with the following command, you can create a report
that you can compare with a DYNSPACE report:
REPORT SPACEUSE SELECT=FIDEXT
Source Code for SPACEUSE Report
The CA Earl source for the SPACEUSE report is the CA Dynam library member
DYNSP.0.
Report Headings The report headings are generally self-explanatory, but note the following:
If VOL= is given specifying a generic volid, one output detail line is

generated for each real volume on which a file has extents. On each line,
the computed items are based on the extents of the file residing on the
volume in question.
5–44 User Guide

If VOL= is given specifying a pool-id, one output detail line is generated

for each pool space that is on a real volume on which a file has extents. If
there is more than one pool space defined on one real volume, a detail line
will appear for each of them, causing some items to be repeated. The
contribution added into the total space used in the pool, however, is
adjusted to result in correct totals for each pool space and for the pool as
a whole. Files having no extents that overlap the pool space being
processed, are not reported for that pool space.
ALLOCATION INFO The computations for this group are only attempted for files that are complete
on the real volume in question and which have had the original allocation
request information recorded in the format-1 record. (This is true for files
created under CA Dynam/D control.)
BLOCKSIZE OPT. This is computed by calculating the largest blocksize that will fit on a track or
control interval for the device in question and is consistent with the file's
record length.
EXTENTS: 1ST SQ# This is the extent sequence number for the first extent on the real volume
being reported on.
EXTENTS: # on VOL This is the number of extents that are on the real volume for the file being
reported on.
FILE IDENTIFICATION, PREFIX FLAGS

The first flag (#) is displayed for any file that has one or more extents that
overlap the pool space in question. Where there are multiple pool spaces
defined on a single volume, this flag should not be trusted, because it can be
raised by extents that are entirely contained in the other pool spaces on the
volume.
The second flag can have the following values:
- if the format-1 record doesn't contain the CA Dynam/D system ID.

Continuations of files beyond the first real volume cannot have this ID set
even though they were created under CA Dynam/D control, and so can
have the - prefix set.
< if the extent sequence number of the first extent for this volume or pool
space is not 0. This can occur if the first extent was created with an
EXTENT statement containing a nonzero sequence number (allowed by
VSE). Otherwise it is a correct indication that the file has prior extents on
another real volume.
> if the format-1 record complete on this volume flag is not set. This can
occur if the file was never closed, and also for certain system utility or
PIOCS files. Otherwise it is a correct indication that the file has subsequent
extents on another real volume.
* if the conditions for both > and < are satisfied.

FT This is a decoded value derived from the file type indicator bytes in the VTOC
format-1 record. Generally, the codes are the same as those used on a DLBL,
but VSAM is abbreviated as VS; -- is displayed if the bits as set do not
correspond to one of the known file types (VS, SD, IS, or DA), which can occur
with initialized but never-opened utility files or in general for PIOCS files.
GAINED SPACE Reported in units appropriate to the device in question (tracks for CKD devices
and blocks for FBA). First, the number of logical records for that file is
ascertained, and then the number of optimal blocks required. From that, the
number of units is computed and subtracted from the actual number of units
used, to arrive at the number that can be gained.
This figure is correct for a file whose extents are partly outside the pool space
being reported on, but the potential gain shown applies to the whole amount
of space reported as TRACKS/BLOCKS ACTUAL (see below) even if that is not
all in the pool space.
Note that for sorting on the REBLOCK report the savings are converted into
bytes to make figures for different device types comparable. This can result in
some unexpected figures in this column, but the sort order is nonetheless
correct.
PERCENT HI/LO This figure can be computed in the following ways:
For under-allocated files it is shown as the percentage of the original

request by which the actual amount used exceeds the original request, and
has a minus sign (-) appended.
For over-allocated files it is shown as the percentage of the actual amount

used by which the original request exceeds the actual amount, and has a
plus sign (+) appended.
On the REALLOC report the sort variable is the absolute value of whichever of
the percentages mentioned above has been calculated, so that over- and
under-allocated files are presented together in the output.
REBLOCKING GAIN INFO

The fields in this section are filled only if the file is type SD with record format
F or FB, for which the record length and blocksize have been recorded in the
format-1 record. For all other files these fields are left blank.
RF This is a decoded value derived from the record format byte in the VTOC
format-1 record. The formats F, FB, V, VB, S, SB, and UN are decoded. If the
bits as set do not correspond to one of these codes then -- is shown. This
often occurs with PIOCS files and also with continuations of files beyond the
first real volume.
TRACKS/BLOCKS This is reported for all files or portions of a file, It shows the total amount of
ACTUAL space used on the real volume in question, regardless of whether it is in the
defined pool space.
5–46 User Guide

On the VOLFID report, a summary line is printed for each volume, showing the
total space used in the pool spaces on that volume. In that total, the nonpool
space used by overlapping extents has been deducted, so that the total is
correct for the pool.
Report Samples For more information about disk space usage analysis reports, see the chapter
"CA Dynam Report Examples."
Volume Table of Contents—VTOCS
The VTOCS report is a standard, VTOC-based DYNPRINT report supplied with

CA Dynam. It provides information about disk occupancy in a flexible and
easy-to-use form. Each extent of each file is reported on individually. Reports
are restricted to only disk files.
Print the report in five different sort orders, corresponding to the variables
most commonly of interest.
Report on free extents, either together with the allocated extents or

exclusively.
Limit the report to an arbitrary number of files.
Restrict reporting to a generic group of volumes, or to the space in a

DYNAM/D disk pool.
VTOCS supersedes the older DYNVTOC report. Using the DYNPRINT report
control language, up to five VTOCS reports can be produced from a single scan
of the VTOCs, enhancing performance. VTOCS does not support the extra info
and double-spacing options.
Invoking the Report
Use the following DYNPRINT command sequence to invoke VTOCS:
ACCESS VTOC
REPORT VTOCS [ BANNER ]
[ EROPT ]
[ MAXLINES ]
[ MAXRETR ]
[ SELECT={option[,option..]} ]
[ VOL ]
VTOCS options and their application, see the chapter "General Reporting—
DYNPRINT."

SELECT Options The SELECT options for VTOCS are grouped into sort-order options and report-
formatting options. Any or all of them can be used in one command, to
produce up to five reports with the desired choice of reported information.
Sort-order options:
FIDEXT Extents are reported by file-id and, within each file-id, in order of extent
sequence number. This is the default option if SELECT is omitted.
CREATE Extents are reported by ascending creation date of the file they belong to.
EXPIRE Extents are reported by ascending expiration date of the file they belong to.
VOLLOC Extents are reported by real volid and, within each volume, by physical
address. Extents having no overlap with any pool space on a volume, are not
reported (except for the VTOC extent).
VTOCSEQ Extents are reported on in order of VTOC retrieval.
Report-formatting options:
FREEXT Causes free extents to be reported. Affects the VOLLOC report only.
NODSNS Causes only free extents to be reported. Affects the VOLLOC report only, and
is ignored unless FREEXT is also given.
SELECT=ALL invokes the first four sort-order options, omitting the VTOCSEQ
report, and without either FREEXT or NODSNS. These last two options can be
used together with the ALL option, as in:
SELECT ALL,FREEXT
Most of the DYNVTOC reporting options can be simulated with the correct
combination of VTOCS SELECT options, and many additional combinations are
allowed. The most basic DYNVTOC report (on a single volume) can be
approximated with:
REPORT VTOCS SELECT=VOLLOC VOL=vvvvvv
Source Code for The CA Earl source for the VTOCS report is the CA Dynam library member
VTOCS Report DYNVT.0.
If VOL= is given specifying a generic volid, one output detail line is

generated for each extent on each real volume encompassed in the
generic volid.
5–48 User Guide

If VOL= is given specifying a pool-id, one output detail line is generated

for each extent entirely or partly in each pool space defined for the pool. If
more than one pool space is defined on one real volume, and an extent
overlaps more than one of them, it will be reported once for each pool
space it overlaps. The true starting and ending locations are always
reported, but the number of tracks or blocks reported reflects what is
actually in the pool space being reported on.
CREATE Reports the creation date as found in the file's format-1 record. If the date
there is uninitialized (zero), this item contains --/--/--.
EXPIRE Displays the expiration date as found in the file's format-1 record.
If the date there is uninitialized (zero), this item contains —/—/—.
If the date is equal to or later than 2099/366, this item contains —PERM—.
If the date is equal to 2099/365, this item contains -RETAIN-.
EXTENT SEQ Indicates that the report is unchanged from the extent segment in the format-
1, format-3, or format-4 record. If the complete on this volume flag is not set
for the file, a plus (+) appears next to this item. This means that the file has
continuation extents on another volume, that it was never closed, or that it
was created by PIOCS and the flag was not set by the access module.
EXTENT TYPE Indicates that the type is decoded from the corresponding binary field in the
format-1, format-3, or format-4 record. Values include the following:
Type Seq# Description
1 any PRIM Primary data extent
2 any OFLO ISAM overflow extent
4 0 MNDX ISAM master index extent
4 not 0 CNDX ISAM cylinder index extent
Other values of the extent type cause that are to be reported.
FILE TYPE Specifies a decoded value derived from the file type indicator bytes in the
VTOC format-1 record. --- is reported if the bits as set do not correspond to
one of the known file types (VSAM, SAM, ISAM or DAM), which can occur with
initialized but never-opened utility files or in general for PIOCS files.
LOW/HIGH EXTENT Specifies the physical position at which the extent starts and ends. For CKD
devices it is in CCC-HH format and for FBA, in BBBBB format.

REL TRK/BLK: NUMBER Reflects only the space within a pool if a pool space is being reported on. If the
number reported is less than the true number belonging to the extent, the
pool-overflow flag # is shown next to the reported figure.
STAT This column can contain one or both of the following codes:
E The file is expired.
DSF The file is data-secured.
VOL SEQ Indicates that the report is unchanged and remains as it was in the file's
format-1 record. If the field is uninitialized (zero), this field is blank on the
report.
5–50 User Guide

Chapter 6: Controlling File
Independence
Introducing CA Dynam/FI
CA Dynam/FI provides a comprehensive file independence facility for VSE
users. It is an integral part of the CA Dynam file management system, and
shares many common components with CA Dynam/T and CA Dynam/D.
"File independence" offers the VSE user the facility to define a sequential
access file in a program and then redefine this file at execution time (changing
device types, block sizes, and so on) without having to make any changes to
the program.
Because CA Dynam/FI dynamically defines the file at execution time, you do

not need to worry about the physical file type.
The facilities of the CA Dynam/FI system include the following:
Unit record simulation
Job exit facility
Catalog management
Audit trail facility
Dynamic file sorting through CA SRAM

Input file concatenation
Unit record simulation allows any unit record device (card reader, printer, card
punch) to be simulated as a tape, sequential disk or VSAM file.
The job exit facility is used to activate CA Dynam/FI options. It lets you
optimize block size, change record format, change unlabeled tape files to
labeled tape files, and specify double buffering.
Catalog management permits you to define CA Dynam/FI options in the

Catalog file. You can define and store file attributes such as block size, record
format, tape options and buffering techniques for cataloged data sets.
The audit trail facility records functions performed by CA Dynam/FI and can be
used to prepare reports on these functions.
Chapter 6: Controlling File Independence 6–1

Supported Program DTF Types
Dynamic file sorting sets up information to be sent to CA SRAM for sorting

files.
When a file's attributes are being modified, CA Dynam/FI replaces the user
program's DTF at OPEN with a new DTF in the partition GETVIS area. This file
type is compatible with the new file parameters defined at execution time. All
logical input/output requests are trapped and routed to the new DTF by CA
Dynam/FI.
Input file concatenation allows multiple input files to be read using one
OPEN/CLOSE.
Supported Program DTF Types
This DTF Defines the File For And Is Supported For
DTFCD Card I/O devices Reader and punch files
DTFCN Console I/O devices SYSLOG only For more information, see
ASSGN Statement.
DTFCP Compiler I/O Compiler files
DTFDA Direct access (DAM) Specific requests for FBA devices For
processing more information, see VCKD.
DTFDI Device independent Unit record I/O processing
DTFMT Magnetic tape I/O Data files only
DTFPH Physical access I/O FBA DTFDA only For more information,
see VCKD.
DTFPR Printer output Unit record I/O processing
DTFSD Sequential disk I/O Data files only
ACB/RPL VSAM I/O Keyed sequence for input and entry

sequence for output (Addressed mode
is used so index is ignored; only the
data component is addressed.)
6–2 User Guide

Physical Files
Physical Files
The following physical files are supported by CA Dynam/FI:
Disk (DTFSD and DTFDA)
Tape (DTFMT)
VSAM (ACB/RPL)
VSAM files may not be changed to disk or tape using FI. Disk or tape files,
however, may be changed to VSAM files by FI.
Restrictions on DTF Types
Special Considerations
DTFSD DTFs that specify the following:
UPDATE=YES (which includes COBOL files opened as I/O) may not be

converted to tape files using CA Dynam/FI.
BLKSIZE=MAX can only be used for fixed blocked records. When used with
other record formats, it causes all CA Dynam/FI functions to be
suppressed.
Supported DTFDA files are converted to DTFPH files and imperative macros are
converted to Physical IOCS channel program sequences.
Control characters for DTFCN (console) files (SYSLOG support) are always
removed.
Unsupported DTFs
The following DTF types are not supported by CA Dynam/FI:
DTFCD DTFs that specify a device type of 2560 or 5425 are not supported
by CA Dynam/FI.
ASCII tape DTFs are not supported.
Spanned record format is not supported.
Diskette DTFs (DTFDU) are not supported.

Hierarchy of File Information
Hierarchy of File Information

Initially, CA Dynam/FI uses the program DTF information. If the Catalog is
present, values defined there override the program DTF information.
Finally, CA Dynam/FI values defined on the DLBL or TLBL statement override

both the program DTF and the Catalog information. For input files, the device
type is determined either by the type of label (DLBL or TLBL) or by the device
type indicated in the Catalog record created for the file, if there is one.
Unit Record Simulation

Unit record simulation allows you the flexibility of routing any unit record
device (card reader, printer, card punch) as a tape, sequential disk or VSAM
file.
Unit record simulation lets you temporarily assign a system file to disk. This
eliminates potential errors caused when a job abends and permanently
assigned system files are not released. Furthermore, blocksize can be
optimized, reducing I/O.
The degree of support for unit record simulation is controlled by parameters in

the DYNAM/FI option record. For more information about setting DYNAM/FI
parameters, see the Programming Guide. Alternatively, you can set or change
support for unit record simulation with the SET statement.
Since DTFCD and DTFPR contain no file name (DTF name), CA Dynam/FI
generates a file name based on the logical unit name specified. The file name
'FISYSxx' is used, where 'xx' is derived from the logical unit specification in the
user program DTF. This logical unit may be overridden using JCL or the CA
Dynam Catalog, but the original logical unit specification is used when deriving
the file name.
For example, if a user program specifies SYS004 as the logical unit for printed
output, the following JCL would change that printer DTF to a disk DTF.
// DLBL FISYS04,'PRINT.OUTPUT.DISK.DATA',7,SD
// EXTENT SYS004,3350WK,1,0,19,50
// ASSGN SYS004,DISK,VOL=3350WK,SHR
Notice that the logical unit (SYS004) is appended to the special name FISYS in
order to derive a DTF name that matches with the label information.
Of course CA Dynam/FI parameters may be used to change the SYS number,

set a more efficient block size or make any other desired changes as required.
6–4 User Guide

Example
// DLBL FISYS04,'PRINT.OUTPUT.DISK.DATA',7,SD,BLKSZ=OPT,FIOPT=(DB),SYS008
// EXTENT SYS008,3350WK,1,0,19,50
DTFDI is the type of DTF normally used by IBM utilities, compilers, other utility
software, and sometimes by user-written Assembler programs, to process unit
record I/O. It always specifies a system logical unit (SYSIPT,SYSLST, and so
on). CA Dynam/FI can normally process the unit record I/O of these programs.
For DTFDI, and for DTFCP that use a system logical unit, the unit record
file names are always as follows:
FISYSIN For SYSIPT
FISYSLS For SYSLST
FISYSPH For SYSPCH
Always use an overriding programmer logical unit with SYSIPT, SYSLST and
SYSPCH files; choose one that is unused by the program which will utilize the
converted JCL. This prevents the problems associated with the opening and
closing of system logical units when these logical units are assigned to disk.
Example
JCL before CA Dynam/FI:
// DLBL IJSYSLS,'PRINTED.LIST.OUTPUT',2,SD
// EXTENT SYSLST,SCRTCH,1,0,256,10
ASSGN SYSLST,DISK,VOL=SCRTCH,SHR (opens SYSLST)
// EXEC FCOBOL,SIZE=256K
.
.
CLOSE SYSLST,D (required to close SYSLST) JCL to
utilize CA Dynam/FI:
// DLBL FISYSLS,'PRINTED.LIST.OUTPUT',2,SD,BLKSZ=OPT,SYS008
// EXTENT SYS008,SCRTCH,1,0,256,10
// ASSGN SYS008,DISK,VOL=SCRTCH,SHR
// EXEC FCOBOL,SIZE=256K
.
.

CICS Command Level Preprocessor Support
CA Dynam/FI fully supports the CICS command level preprocessor, despite the
inconsistent way in which the preprocessor performs I/O. BLKSZ=OPT support
provides major performance improvement and improved I/O utilization.
Sample JCL for COBOL:
// DLBL FISYSPH,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008
// EXEC DFHECP1$
.
.
COBOL PROGRAM
/*
// DLBL FISYSIN,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008
// EXEC FCOBOL
/* Sample JCL for ASSEMBLER:
// DLBL FISYSPH,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008
// EXEC DFHFA1$
.
.
ASSEMBLER PROGRAM
/*
// DLBL FISYSIN,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008,LRECL=80
// EXEC ASSEMBLY
/*
Note: For Assembler, the LRECL=80 parameter must be specified.
For other programs the LRECL=80 parameter may be specified, but it is not
required.
The file 'SYSPCH.FILE' can be CA Dynam/D-controlled, then the EXTENT and

ASSGN may be omitted.
6–6 User Guide

CICS Macro Level Preprocessor Support
CA Dynam/FI fully supports the CICS macro level preprocessor, despite the
inconsistent way in which the preprocessor performs I/O. BLKSZ=OPT support
provides major performance improvement and improved I/O utilization.
Sample JCL for COBOL:
// DLBL DFHPR30,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008
// EXEC DFHPRPR
.
.
COBOL PROGRAM
/*
// DLBL FISYSIN,'SYSPCH.FILE',2,SD,BLKSZ=OPT,SYS008,LRECL=80
// DLBL FISYSPH,'SYSPCH.FILE.2',2,SD,BLKSZ=OPT,SYS008
// EXEC ASSEMBLY
/*
// DLBL FISYSIN,'SYSPCH.FILE.2',2,SD,BLKSZ=OPT,SYS008
// EXEC FCOBOL
/*
Note: IBM requires a second DFHPRPR step with a UPSI of 10001000 to copy
the file and strip the first character. However, this step must be removed when
using CA Dynam/FI.
Derived file name For supported logical unit
FISYSIN SYSIPT DTFs
FISYSPH SYSPCH DTFs
FISYSLS SYSLST DTFs
FISYSnn SYS0nn DTFs (COBOL unit record DTFs are this type.)
SYSRDR files are not supported because VSE Job Control does not use LIOCS
to process its SYSRDR files. (Note that RPG II uses SYSRDR to process card
files.)

Dynamic File Sorting
Control characters for DTFPR (printer) files are inserted if not present, and
control characters for DTFCD (punch) files are removed if present. CA
Dynam/FI only supports printer files using ASA or machine control characters.
When the simulation is invoked for files not conforming to this rule,
unpredictable results occur.
The LIOCS functions provided by the CNTRL and PRTOV macros are not
supported. Therefore, programs which depend upon CNTRL and PRTOV
support cannot use this simulation. (This includes the COBOL 'EOP' condition.)
DTFCPs that use system logical units, and process unit record I/O, can
normally be processed by CA Dynam/FI; DTFCPs that use programmer logical
units, such as SYS001, cannot. This means that compiler and Assembler work
files may not be processed by CA Dynam/FI.

Dynamic file sorting lets you sort records on input or output while
manipulating/processing them in a user program written in Assembler, COBOL,
and so on. CA Dynam/FI does this by interfacing with CA SRAM (Sort
Reentrant Access Method). The procedure is transparent to the user program
since all CA SRAM specifications are made on the DLBL or TLBL rather than
within the program. CA Dynam/FI sends information to CA SRAM to define how
files are to be sorted, and intercepts the records at GETs and PUTs for CA
SRAM calls.
For this facility to work, both CA Dynam/FI and CA SRAM must be active and
supported. The Programming Guide explains how this is done. For more
information, see the DYNAM/FI installation option record.
On the DLBL or TLBL statement, indicate whether you are sorting on input
(SORTIN) or on output (SORTOUT) and what sort key fields are to be used.
The sort key field(s) may be defined on the xLBL statement or may reside in
the Catalog as a sort key name (SKNAME). A cataloged sort key name
provides greater flexibility:
Different files may use the same sort key.
A larger number of CA SRAM options may be defined.
A sort key is only defined once and easily maintained with DYNCAT.
For more information about defining and maintaining SKNAMEs, see the
DYNCAT utility.
On the DLBL or TLBL statement you may also indicate the file name and logical
unit for the sort work file (SORTWRK). If you omit the SORTWRK parameter,
the file name WORK01 on SYS001 is assumed.
6–8 User Guide

CA SRAM normally uses the upper unused portion of the partition to allocate
storage for each task and its own overhead. If this procedure conflicts with the
user program (for example, PL/I and RPG II also dynamically use partition
storage), a CA SRAM SRTCORE call must be issued. CA Dynam/FI obtains the
necessary storage from the partition GETVIS area and issues the SRTCORE call
based on the size you have indicated for the specific sorting task (using
SRTCORE on the xLBL statement) and/or what you have requested as a total
amount of storage (using SORTCORE on the SET statement).
Note that the SET SORTCORE statement indicates the total amount of storage
you want CA Dynam/FI to request for all sorting tasks. The SRTCORE
parameter on the xLBL statement indicates the amount of storage requested
for a particular task.
For more information on the CA Dynam/FI SET statement, see Controlling

System Actions. The CA SRAM documentation set provides instructions for
calculating storage sizes.
Examples
Sort the file TAPEOUT on output. The sort key record shows that the sorted
field starts at the first position, has a length of 20, is character data, and will
be sorted in descending order. The file name of the work file is WORK1 and is
on logical unit SYS040. 40000 bytes of GETVIS storage have been requested
for the sort and its overhead.
// TLBL TAPEOUT,'OUTPUT.FILE',,SORTOUT=(1,20,C,D), X
SORTWRK=(WORK1,SYS040),SRTCORE=40000
If a cataloged sort key name (KEY1) and sort work file defaults (WORK1 on
SYS001) were used, and no SRTCORE call were needed, the above example
could be rewritten as:
// TLBL TAPEOUT,'OUTPUT.FILE',,SORTOUT=KEY1
Sort the file FILEOUT on output. Since PL1001 is a user-written PL/I program,
a SET SORTCORE statement precedes execution of the program. 50000 bytes
of storage have been requested for all sorting tasks in this job and 30000
bytes have been requested for the task for FILEOUT.

Changing File Characteristics
/*
SET SORTCORE=50000
// DLBL WORK1,'WORK.FILE'
// EXTENT SYS040,3380WK,1,0,1,150
// DLBL FILEIN,'FILE.IN'
// EXTENT SYS012,3350WK,1,0,1,10
// DLBL FILEOUT,'FILE.OUT',,,SORTOUT=(1,50,CH,A),SRTCORE=30000, X
SORTWRK=(WORK1,SYS040)
// EXTENT SYS013,3350WK,1,0,1,10
// EXEC PL1001
/*
TLBL/DLBL Extensions and Format
CA Dynam provides a Job Control exit which enhances the existing VSE TLBL
and DLBL statements.
Operands are either keywords and values (BLKSZ=1210) or positional

operands (NODISK). A distinction is made between keywords and operands for
IBM and those for CA Dynam/FI. Note that all CA Dynam/FI positional and
keyword operands are optional. However, if not specified there may be a
system default.
CA Dynam/FI operands must follow all standard VSE Job Control operands. For
example, the following is invalid since the CA Dynam/FI operand BLKSZ=160
precedes the VSE Job Control retention period operand 2099/365:
// TLBL TEST01,'TAPE LABEL',BLKSZ=160,2099/365 The correct statement is:
// TLBL TEST01,'TAPE LABEL',2099/365,BLKSZ=160
CA Dynam/FI keyword operands (keyword=value) and optional operands may

appear in any order. Each of the following is correct.
// DLBL FILE01,'TEST FILE ONE',0,SD,BLKSZ=OPT

// DLBL FILE01,'TEST FILE ONE',0,SD,FIOPT=(DB),BLKSZ=OPT
// DLBL FILE01,'TEST FILE ONE',0,SD,BLKSZ=OPT,FIOPT=(SB,VERIFY)
6–10 User Guide

TLBL Statement
// TLBL filename,'dataset-name', [ retention ]
[ ,IBM TLBL options ]
[ ,BLKSZ= {nnnnn|OPTimize } ]
[ ,CONCAT ]
[ ,CONCAT= {ALL|nn } ]
[ ,FIOPT=(options) ]
[ ,IGNORE ]
[ ,LRECL=nnnnn ]
[ ,NODISK ]
[ ,NOFI ]
[ ,RECFM=xx ]
[ ,SRTCORE=nnnnnn ]
[ ,SORTIN= {(keys)|keyname } ]
[ ,SORTOUT= {(keys)|keyname } ]
[ ,SORTWRK=(filename,SYSnnn) ]
[ ,SYSxxx ]
IBM TLBL Parameters
The IBM TLBL parameters are as follows:
filename Indicates the standard IBM DTF file name.
'dataset-name' Indicates the standard IBM data set name (enclosed in single quotation
marks).
retention Indicates the standard IBM retention period specification. If the retention
period is omitted, the comma following this field must be supplied. This is
because CA Dynam/FI does not begin searching for its operands until the
fourth positional parameter.
Valid (notice commas): // TLBL TEST,'DSN',,NODISK

Invalid (comma missing): // TLBL TEST,'DSN',NODISK
If you use a keyword directly after this field, the second comma may be
omitted when you omit retention. The following is correct:
// TLBL TEST,'DSN',BLKSZ=OPT,NODISK
IBM TLBL Options Indicates the IBM TLBL optional parameters. (See the previous description of
"retention.")

CA Dynam/FI Operands
The remaining operands are as follows:
BLKSZ= Specifies the block size for the file. It is either a decimal number between 1
and 65535, or the keyword OPTIMIZE (or OPT). If you use OPTIMIZE, CA
Dynam/FI recalculates the block size for the physical unit on which the data
set resides.
When BLKSZ=OPT is specified, CA Dynam/FI uses the OPTBLKS value defined

in the DYNAM/FI option record for tape files during the installation procedure.
Before a file can be used as input with this specification, it must first be
created with the BLKSZ=OPT option. Indeed, if a file is created with CA
Dynam/FI OPT blocking, then when the file is processed for input, either OPT
or the correct numeric block size must be used. If you specify neither,
unpredictable results will occur.
Default: Block size defined in the Catalog or else block size in the user's
program.
CONCAT Specifies that this file is to be concatenated with another file.
When CONCAT is specified, a single open can be used to read two (or more)
input files. Specify CONCAT on the label of each file to be concatenated,
except for the last one to be read.
CONCAT=ALL, CONCAT=nn
CONTACT=ALL may be specified to concatenate all versions of a data set. Use
CONCAT=nn to concatenate the first nn versions of a data set.
FIOPT=(options) Specifies CA Dynam/FI options. Options may be listed in any order, separated
by commas and enclosed in parentheses.
AUDIT Instructs CA Dynam/FI to monitor processing of this file

even though nothing is to be changed (for information
about the processing of the file.)
NOCNTRL Ignores CNTRL requests for this file. For more information
about CNTRL macro, see the IBM Supervisor And I/O
Macro manual.
NORELSE Ignores RELSE requests for this file. For more information
about RELSE macro, see the IBM Supervisor And I/O
Macro manual.
NOTM Does not write tape mark at close. Default: Tape mark
written at close
6–12 User Guide

NOTRUNC Ignores TRUNC requests for this file. For more

information about TRUNC macro, see the IBM Supervisor
And I/O Macro manual.
RELEASE Releases the logical assignment for the file at close (only
for temporary programmer logical units). Default: No
release of the assignment
RUN|NORWD Specifies whether to rewind and unload tape at close.

Default: Tape rewound at close
SB|DB Single or double buffering for this file. Default: Buffering

technique specified by the user program
SKR Skips tape rewind at open. Default: Tape rewound at

open
SL|UL Forces standard label (SL) or unlabeled (UL) tape

processing. Default: Processing specified in program
IGNore Signals that ignore processing is in effect. The file is not opened. For input, an
EOF (end-of-file record) will be returned at the first GET/READ. For output, all
PUTs/WRITEs will be discarded.
CA Dynam/FI IGNORE processing is an alternative to the IBM 'ASSGN IGN'

facility. If, in normal processing, the logical unit derived by DYNAM/FI is
assigned 'IGN', but the TLBL has the CA Dynam/FI 'IGN' option, CA Dynam/FI
processing will prevail; i.e, the IBM facility will be ignored.
This option is not supported for CA SORT input/output files.
LRECL=nnnnn Defines the logical record length for the file.
Default: Record length defined in the Catalog or else record length in the
user's program
NODISK Prevents the operator from switching to DISK for this generation of the tape
file. Overrides the Catalog specification of FI for this data set.
NOFI Ignores CA Dynam/FI processing for this file (used with programs such as
DITTO, which modifies its DTF after OPEN processing is complete).
RECFM=xx Specifies the record format for the file. Record formats supported follow:
F Fixed
FB Fixed-blocked
V Variable

VB Variable-blocked
U Undefined
Default: Record format in the Catalog or else format remains unmodified
SRTCORE=nnnnnn Specifies the amount of storage, in bytes, which CA SRAM is to use for this
particular task. (Multiple tasks are permitted.) System performance may be
enhanced by providing a specific storage size.
Default: Twice the calculated minimum
SORTIN=, SORTOUT= Requests CA SRAM for dynamic file sorting, and defines both when the file is
to be sorted (input, output, or both) and the sort key fields to be used for
each. The sort fields may be specified in the normal CA SRAM key definition
vector format, or as the name of a predefined Catalog sort key entry.
The use of the "keyname" format is recommended since it provides maximum

flexibility. With this format, the file may be sorted using many different sort
keys without complex job control using continuation statements. It also
permits changing sort key fields without job control modification, and it allows
many files to share the sort key definitions. For more information about
maintaining sort key names, see the DYNCAT ALTER and DEFINE commands.
=(keys) Specifies each key field/vector, composed of four

parameters, (s1,l1,t1,m1,s2,l2,t2,m2,...).
s relative field start position in the data record
l key field length in bytes
t sort key type:
C/CH alphanumeric characters
B/BI positive binary data
P/PD packed decimal data
m collating sequence required:
A ascending sequence
D descending sequence
=keyname Identifies a CA Dynam Catalog Sort Key Record

(SKNAME) containing the sort key vector to be used for
sorting the file.
6–14 User Guide

SORTWRK= Specifies the file name (maximum of 5 characters) of the label information to
be used as the CA SRAM work file. The file name value is limited to a
maximum of 5 characters. SYSnnn is the logical unit to be used in accessing
the file. If more than one dynamically sorted file is processed in a single
program, this parameter must be used to define the CA SRAM work files.
Naturally, more than one task cannot use the same DASD work space at the
same time.
Default: (WORK1,SYS001)
SYSxxx Specifies an explicit logical unit. Use this option if you're using unit record
simulation when the program DTF is DTFDI.
Default: Program-defined logical unit
Examples
Changes the block size to 8000 bytes (BLKSZ=8000) and the tape labeling to
standard label processing (SL).
// TLBL FILEA,'FILE-ID',0,BLKSZ=8000,FIOPT=(SL)
Changes the block size to "optimal" blocking (BLKSZ=OPT), rewinds and

unloads the tape at close (RUN), and forces double buffering I/O (DB).
// TLBL FILEB,'FILE-ID',0,BLKSZ=OPT,FIOPT=(RUN,DB)
Forces the use of logical unit SYS018 (SYS018), changes the record format to
fixed-blocked (FB) and the record length to 80 bytes (LRECL=80).
// TLBL FILEC,'FILE-ID',,SYS018,RECFM=FB,LRECL=80
DLBL Statement
// DLBL filename,'dataset-name' [ ,retention ]
[ ,type ]
[ ,IBM DLBL options ]
[ ,BLKSZ= {nnnnn|OPTimize } ]
[ ,CONCAT ]
[ ,CONCAT= {ALL|nn } ]
[ ,FIOPT=(options) ]
[ ,FIVSAM|,NOFIVSAM ]
[ ,IGNORE ]
[ ,LRECL=nnnnn ]
[ ,MAXCI=nnnnn ]
[ ,NOFI ]
[ ,NOTAPE ]
[ ,RECFM=xx ]
[ ,SRTCORE=nnnnnn ]

[ ,SORTIN= {(keys)|keyname } ]
[ ,SORTOUT= {(keys)|keyname } ]
[ ,SORTWRK=(filename,SYSnnn) ]
[ ,SYSxxx ]
IBM DLBL Parameters
The IBM DLBL parameters are as follows:
filename Indicates the standard IBM DTF file name.
'dataset-name' Indicates the standard IBM data set name.
retention Indicates the standard IBM retention period specification.
type Indicates the standard IBM access method type specification. If the DLBL type
and/or retention are omitted, the commas following those fields must be
supplied. CA Dynam/FI does not begin searching for its options until the fifth
positional parameter.
Valid (notice commas): // DLBL FILE,'TEST',NOTAPE

Invalid (commas missing): // DLBL FILE,'TEST',NOTAPE
But, if the first CA Dynam/FI operand is a keyword, you may omit commas
when you omit retention and/or type, as shown:
// DLBL FILE,'TEST',BLKSZ=OPT,NOTAPE
IBM DLBL options Indicate the IBM DLBL optional parameters. (See previous note in relation to
"type.")
CA Dynam/FI Operands
The remaining operands are as follows:
BLKSZ= Specifies the block size for the file. It is either a decimal number between 1
and 65535, or the keyword OPTIMIZE (or OPT). If you specify OPTIMIZE, CA
Dynam/FI recalculates the block size for the physical unit on which the data
set resides. Note that this may not be the maximum block size for the device.
When BLKSZ=OPT is specified, CA Dynam/FI uses the OPTBLKS value defined

in the DYNAM/FI option record for disk files during the installation procedure.
If full-track blocking was indicated, then the block size value is set to the
approximate track size of the particular disk device type. For example, files on
3330 disks are given a block size value which is a multiple of the record length
and as close to 13,030 bytes as possible. If you specify BLKSZ=OPT and the
disk device type is FBA, the CISIZE, not the block size, is recalculated. With
FBA, the block size will not be changed.
6–16 User Guide

Before a file can be used as input with this specification, it must first be
created with the BLKSZ=OPT option. If a file is created with CA Dynam/FI OPT
blocking, then when the file is processed for input, either OPT or the correct
numeric block size must be used. If you specify neither, unpredictable results
can occur.
Default: Block size defined in the Catalog or else block size in the user's
program
CONCAT Specifies that this file is to be concatenated with another file.
When CONCAT is specified, a single open can be used to read two (or more)
input files. Specify CONCAT on the label of each file to be concatenated,
except for the last one to be read.
CONCAT=ALL Concatenates all versions of a data set.
CONCAT=nn Concatenates the first nn versions of a data set.
FIOPT=(options) Specifies CA Dynam/FI options. Options may be listed in any order, separated
by commas and enclosed in parentheses.
AUDIT Instructs CA Dynam/FI to control processing of this file,

even though nothing is to be changed, to get AUDIT
information about the processing of the file.
NOCNTRL Ignores CNTRL requests for this file. For more information
about the CNTRL macro, see the IBM Supervisor And I/O
Macro manual.
NORELSE Ignores RELSE requests for this file. For more information
about the RELSE macro, see the IBM Supervisor And I/O
Macro manual.
NOTRUNC Ignores TRUNC requests for this file. For more

information about the TRUNC macro, see the IBM
Supervisor And I/O Macro manual.
RELEASE Releases the logical assignment for the file at close

(applies only to temporary programmer logical units).
Default: No release of the assignment.
SB|DB Single or double buffering for this file. Default: The

buffering technique specified by the user program.
VERIFY Verifies output by reading the record just written. CA

Dynam/FI enables the VERIFY option in the program DTF.

FIVSAM, NOFIVSAM Specifies whether CA Dynam/FI is allowed to convert the file to a VSAM file if a
VSAM DLBL record is found. This parameter overrides the default set in the
DYNAM/FI option record. (Note that if FIVSAM is specified, CA Dynam/FI,
rather than VSAM/SAM, performs the modification from SD to VSAM by
creating ACB/RPL.)
IGNore Signals that ignore processing is in effect. The file is not opened. For input, an
EOF (end-of-file record) will be returned at the first GET/READ. For output, all
PUTs/WRITEs will be discarded.
CA Dynam/FI IGNORE processing is an alternative to the IBM 'ASSGN IGN'

facility. If, in normal processing, the logical unit derived by DYNAM/FI is
assigned 'IGN', but the DLBL has the CA Dynam/FI 'IGN' option, CA Dynam/FI
processing will prevail; i.e, the IBM facility will be ignored.
This option is not supported for DTFDA (VCKD) or for CA SORT input/output
files.
LRECL=nnnnn Defines the logical record length for the file.
Default: Record length defined in the Catalog or else record length in the
user's program.
MAXCI=nnnnn Specifies the maximum CI size to be used for FBA devices to calculate a new
CISIZE with BLKSZ=OPT. When BLKSZ=OPT and the device pointed to is FBA,
the block size is not changed but the DTF CISIZE field gets a computed value
based on MAXCI parameters. nnnnn must be a valid FBA CI size or zero. If this
operand is specified but the device pointed to is not FBA, it will be ignored.
Default: Control interval size specified at installation.
NOFI Ignores CA Dynam/FI processing for this file (used with programs such as
DITTO, which modifies its DTF after OPEN processing is complete).
NOTAPE Prevents the operator from switching to TAPE for this generation of the disk
file. Overrides the Catalog specification of FI for this data set.
RECFM=xx Specifies the record format for the file. Record formats supported are:
F Fixed
FB Fixed-blocked
V Variable
VB Variable-blocked
U Undefined
Default: Record format in the Catalog or else format remains unmodified.
6–18 User Guide

SRTCORE=nnnnnn Specifies the amount of storage, in bytes, which CA SRAM is to use for this
particular task. (Multiple tasks are permitted.) System performance may be
enhanced by providing a specific storage size.
Default: Twice calculated minimum.
SORTIN=, SORTOUT= Requests CA SRAM for dynamic file sorting, and defines both when the file is
to be sorted (input, output, or both) and the sort key fields to be used for
each. The sort fields may be specified in the normal CA SRAM key definition
vector format, or as the name of a predefined Catalog sort key entry.
The use of the cataloged keyname format is recommended since it provides

maximum flexibility. With this format, the file may be sorted using many
different sort keys without complex job control using continuation statements.
It also permits changing sort key fields without job control modification, and it
allows many files to share the sort key definitions. For more information about
maintaining sort key names, see the DYNCAT ALTER and DEFINE commands.
=(keys) Specifies each key field/vector, composed of four

parameters, (s1,l1,t1,m1,s2,l2,t2,m2,...)
s relative field start position in the data record
l key field length in bytes
t sort key type:
C/CH alphanumeric characters
B/BI positive binary data
P/PD packed decimal data
m collating sequence required:
A ascending sequence
D descending sequence
=keyname Identifies a Catalog Sort Key Record (SKNAME)

containing the sort key vector to be used for sorting the
file.
SORTWRK= Specifies the file name (maximum of 5 characters) of the label information
which is to be used as the CA SRAM work file. SYSnnn is the logical unit to be
used in accessing the file. If more than one dynamically sorted file is
processed in a single program, this parameter must be used to define the CA
SRAM work files. Naturally, more than one task cannot use the same work file
at the same time.

Default: (WORK1,SYS001)
SYSxxx Specifies an explicit logical unit. Use this option if using unit record simulation
when the program DTF is DTFDI.
Note that the logical unit specified in an EXTENT statement, if present, takes
precedence over the SYSxxx specified here. For CA Dynam/D users, the S
parameter on a DLBL statement will take precedence over any other logical
unit specification when Catalog management is invoked.
Default: The program defined logical unit, or the logical unit specified in the
EXTENT statements.
Examples
Recalculate the block size (BLKSZ=OPT).
// DLBL FILEA,'DISK-A',,SD,BLKSZ=OPT Release the assignment at close (RELEASE).
// DLBL FILEB,'DISK-B',,SD,FIOPT=(RELEASE)
// EXTENT SYS008,111111,1,0,1,100
Set the block size to 1210 bytes (BLKSZ=1210), verify the output (VERIFY),
and use SYS007 as the logical unit (SYS007).
// DLBL FISYSLS,'FILE-C',,SD,BLKSZ=1210,FIOPT=(VERIFY),SYS007
// EXTENT SYS007,111111,1,0,1,19
Cataloged Data Set Definitions
You may indicate sort key records and file independence options for data sets
in the CA Dynam Catalog. Use the DYNCAT ALTER and DEFINE commands. For
more information, see Maintaining the Catalog.
In order for CA Dynam/FI to use the cataloged data set information, you must
specify YES for these parameters:
CATALOG(YES) in the DYNAM/FI option record to indicate that catalog

support is available for CA Dynam/FI
DYNAMFI(YES) for the particular data set in the Catalog to indicate that CA
Dynam/FI may access the catalog information.
If either of these options is NO, the catalog information will neither be

accessed nor updated.
CA Dynam/FI overrides program DTF specifications with what it finds in the

Catalog. In turn, it overrides catalog definitions with FI options found on the
xLBL statement.
6–20 User Guide

Considerations for CA Dynam/FI Options
Record Format Changes

Changing a record format (RECFM=) from:
Fixed-length (F or FB) to variable-length (V or VB) or undefined records

(U) causes trailing blanks to be eliminated from each data record.
Variable-length (V or VB) or undefined (U) records to fixed-length (F or

FB) records causes the following. If the variable-length record is:
− greater than the LRECL specified, the record is truncated to the

specified length.
− smaller than the LRECL specified, the record is padded with blanks.
TRUNCS Support (DLBL)
DASD files processed by CA Dynam/FI use logic modules with TRUNCS=YES

support. If a file is created under CA Dynam/FI control for audit purposes only
(that is, no file characteristics are changed), be sure to process that file as
input with CA Dynam/FI or a logic module that includes TRUNCS support.
When you do not want short blocks written, use FIOPT=(NOTRUNC).
VSAM Support (DLBL) To change to VSAM DLBL files, CA Dynam/FI uses:

Entry-sequence/key-sequence on input
Entry-sequence on output
Address processing of files.
Physical locations of logical records in a key-sequenced VSAM file change as

other records are added/deleted. Address processing of such files will present
problems. Thus, users should reorganize their key-sequenced input files before
they request CA Dynam/FI to change them to VSAM files.
Commas Separating Operands

When DLBL and TLBL statements are logged by Job Control (either to SYSLOG
or SYSLST), the commas separating the CA Dynam/FI operands from the
remainder of the statement are replaced by blanks.
Example
Statement containing commas:
// TLBL INPUT,'TAPE FILE',,FIOPT=(SL),BLKSZ=1200
Will appear with blanks, as follows:
// TLBL INPUT,'TAPE FILE' FIOPT=(SL),BLKSZ=1200

Storage Requirements
Carefully consider storage requirements when using CA Dynam/FI to increase

the block size or buffers of a file -- single buffering to double buffering (DB). If
additional storage is needed for the blocks or buffers, it is taken from partition
GETVIS. This storage can be considerable depending on the new block size
and/or buffer size.
Also be aware that it is not always an efficient use of storage to specify

BLKSZ=OPTIMIZE for a file that originally wrote small records in small blocks.
This is true, for example, if the device type is a 3380 disk drive.
Block Sizes and Logical Record Lengths
The logical record length (LRECL) and the physical block size (BLKSZ) can
affect each other, depending on the record format specified. CA Dynam/FI will,
if necessary, alter either or both the LRECL and BLKSZ, depending on both the
old and new record format. The exact conditions and actions taken are
described below.
Note that if the user specifies an LRECL or BLKSZ value through Job Control or
the Catalog, then CA Dynam/FI uses these values just as they are. However, if
either the LRECL or BLKSZ value is not specified through Job Control or the
Catalog, then one or more of the following can occur:
If control characters for:
− DTFPR (printer)files are added to records, then record length is

increased one byte.
− DTFCD (punch) files are deleted from records, then record length is
decreased one byte.
If changing from:
− Fixed- or undefined- to variable-length records, then record length is

increased four bytes to include record descriptor word (RDW).
− Variable- to fixed- or undefined-length records, then record length is

decreased four bytes and RDWs are eliminated.
If record format is to be fixed-unblocked or undefined, then block size

equals record length.
If record format is to be fixed blocked and:
− Old format was fixed (blocked or unblocked), then block size equals
old blocking factor (old block size divided by old LRECL) multiplied by
record (current LRECL).
For example, if you specify RECFM=FB and LRECL=50 when:
old logical record length = 80
6–22 User Guide

old block size = 800
old record format = FB
CA Dynam/FI calculates the new block size as follows:
new block size = 800/80 X 50
new block size = 500
− Old format was not fixed, then block size is rounded down to nearest
multiple of record length. (If the block size is less than record length,
record length is used.)
For example, if you specify RECFM=FB and LRECL=80 when:
old record format = VB
(Record length does not apply for variable records.)

CA Dynam/FI calculates the new block size as follows:
The block size value of 850 is rounded down to the next even multiple
of the LRECL. Thus, new block size = 800.
If record format is to be:
− Variable-unblocked, then block size equals record length + 4 bytes for

the block descriptor word (BDW)
− Variable-blocked and old format (as defined in the program) is fixed or

undefined, then block size equals old blocking factor (old BLKSIZE
divided by old LRECL) multiplied by new record length + 4 bytes for
BDW.
For example, if you specify RECFM=VB when:
old logical record length = 80
old record format = FB
CA Dynam/FI calculates the new LRECL to be 84 (going from Fixed to

Variable, new LRECL = old LRECL + 4), and the block size is calculated
as follows:
new block size = 800/80 X 84 + 4
new block size = 10 X 84 + 4
new block size = 844

Concatenated Data Sets
CA Dynam/FI provides an input data set concatenation facility. This facility

allows multiple input data sets to be read as if they were a single data set, in
response to a single open issued by the application. Concatenation is invoked
by specifying the CONCat option on the label of each data set which is to be
concatenated.
Multiple concatenated input files may be processed concurrently; that is, an

application that issues opens for several different data sets may use
concatenation for one or all of them. In the case of tapes, the data sets to be
concatenated may be single file data sets or part of multifile data sets, and
may each consist of a single or multiple volumes. Input data sets to be
concatenated may have different attributes. Data sets may be concatenated
without regard to disk or tape residence, varying record formats, blocksizes, or
logical units, as these attributes are resolved as part of normal CA Dynam/FI
processing in a manner transparent to the application. The following sample
JCL demonstrates concatenation:
// JOB CONCATEX
/*
/* PROCESS MONTHLY A/P TRANSACTIONS
/*
/* INPUT: 1 CONCATENATED DATASET
/* CONSISTING OF 2 TAPE DATASETS
/* AND 2 DISK DATASETS
/*
// TLBL INPUT,'TRANS.TAPE.OLDEST',,CONCAT
// TLBL INPUT,'TRANS.TAPE.OLDER',,CONCAT
// DLBL INPUT,'TRANS.DISK.OLD',,,CONCAT
// DLBL INPUT,'TRANS.DISK'
// EXEC APMTHLY
/&
Where other CA Dynam products are installed, the concatenated data sets may
be either controlled, uncontrolled, or a mixture of the two. All processing
options supported by the other products in the CA Dynam family are supported
for use in conjunction with concatenation.
In addition, all versions of a particular data set may be read by using

CONCAT=ALL or the first nn versions may be concatenated by using
CONCAT=nn on the TLBL or DLBL.
Additional Examples
In this example, COBOL program COBTEST is originally written to read from a

card reader (DTFCD) and write the output to a line printer (DTFPR). However,
with CA Dynam/FI, the program will read from a tape file labeled 'CARD-
INPUT' and write to a tape file labeled 'PRINT-OUTPUT'.
6–24 User Guide

The input tape file is FISYSIN and the output tape file is FISYSLS. The output
file generated is a standard labeled tape. Logical unit SYS001 is used for the
SYSIN file and SYS002 for the SYSLST file.
// JOB TEST1
// TLBL FISYSIN,'CARD-INPUT',,SYS001
// TLBL FISYSLS,'PRINT-OUTPUT',,SYS002,FIOPT=(SL)
// ASSGN SYS001,TAPE
// ASSGN SYS002,TAPE
// EXEC COBTEST,SIZE=100K
The file name is derived from:
DTFname in Assembler programs
File SELECT in COBOL programs.
By default, the logical unit name is used.
Example
// DLBL SYS001, ...
Recalculate the block size of an output disk file. Note that the block size of the
disk file is calculated based upon the OPTBLKS value defined in the DYNAM/FI
option record at installation time. For fixed-length records, the block size value
is always a multiple of the record size value specified.
// DLBL OUTPUT,'DISK-FILE',,SD,BLKSZ=OPT
Reblock a tape file and set the options. The file below is reblocked on a tape to
8000 bytes, and double buffering is specified (DB). In addition, a rewind and
unload operation is performed on the tape when it is closed (RUN).
// TLBL OUTPUT,'TAPE-FILE',,BLKSZ=8000,FIOPT=(RUN,DB)
Create a tape file and change the logical unit. Logical unit SYS018 is used to
override the logical unit specified in the user's program.
// TLBL TAPDISK,'TAPE-DISK',,SYS018
Read a disk file created with reblocked size. Note that if the block size operand
were omitted, the block size value would default to the one in the user's
program. In many cases, however, this can cause a wrong-length record error
to occur.
// DLBL DISK,'MASTER',,SD,BLKSZ=OPT
Create a SYSLST disk file when SYSLST is program-defined as a printer. Note

that the SYSLST file is created on disk with a block size of 1210 bytes and the
file name FISYSLS is used. The SYS001 assignment overrides the use of
SYSLST.

Controlling System Actions
// DLBL FISYSLS,'LISTING DISK',,SD,BLKSZ=1210

// EXTENT SYS001,111111,1,0,1,100
// ASSGN SYS001,DISK,VOL=111111
Change from printer output (DTFDI or DTFPR) to disk output. Any one of the
DLBL/EXTENT pairs will produce the same result: output will be to disk.
// DLBL FISYSLS,'TEST.FILE1',2099/365,,SYS008
// EXTENT SYS008,335000,1,0,1,10
/*
// DLBL FISYSLS,'TEST.FILE2',2099/365,,
// EXTENT SYS008,335000,1,0,1,10
/*
// DLBL FISYSLS,'TEST.FILE3',2099/365,,SYS008
// EXTENT ,335000,1,0,1,10
Setting System Controls - SET Statement
CA Dynam/FI gets certain unique SET statements from either SYSLOG or

SYSRDR in order to temporarily or permanently (until next IPL) alter system
actions. For more information about the standard syntax notation used, see
the chapter "Introduction."
SET Format The format for SET is shown below.
[//] SET CPCMD='command'
[//] SET DYNAMFI= {ON|OFF }
[//] SET $JOBEXIT= {AFTER|BEFORE }
[//] SET [PARTID= {xx|* }] [,AUDIT= {ON|OFF } ]

[,EXECSIZE= {nnn|(nnn,AUTO)|(nnn,MAX) } ]
[,FIPROG= {ON|OFF } ]
[,SEARCH=(NOUR|UR,NODI|DI,NOCP|CP) ]
[,SORTCORE=nnnnnn ]
The defaults for the preceding operands are specified in the DYNAM/FI option
record.
CPCMD= Lets you pass a command to CP while running under VM.
6–26 User Guide

DYNAMFI= Enables or disables CA Dynam/FI processing in the partition in which the SET
command is issued.
ON Enables CA Dynam/FI to process in that partition.
OFF Disables CA Dynam/FI processing in that partition.
DYNAMFI command is issued in the same partition or until the VSE machine is
IPLed.
In dynamic partitions, CA Dynam/FI intercepts can be disabled only until the

$JOBEXIT= Specifies whether the standard job exit ($JOBEXIT) will be processed BEFORE
or AFTER the CA Dynam common Job Exit.
If you have specified processing in the standard $JOBEXIT that affects CA

Dynam processing, (that is, CA Dynam option substitution for TLBL|DLBLs)
code the SET $JOBEXIT=BEFORE command.
PARTID= Positional parameter. Specifies the partition for this statement. If used, it must
be the first operand specified. The asterisk (*) or any valid two-character
partition ID may be specified.
PARTID=xx Indicates that the SET statement applies to a particular

partition; this specification is effective immediately.
PARTID=* Indicates that the SET statement refers to all partitions;

it becomes effective with the next job in partition.
The presence of the PARTID parameter indicates that the SET command is
permanent; that is, it remains in effect until another SET command overrides
it or an IPL is performed. For dynamic partitions, permanent options are reset
when the class (POWER/VSE job) terminates.
All actions for a partition are either permanent or temporary based upon this
operand. If omitted, any action previously set as permanent will lose that
status and will be reset at end-of-job. The SET statement, also, will remain in
effect only until end-of-job.
AUDIT= Turns off AUDIT recording or turns it back on provided audit support was
specified in the DYNAM/FI option record. The occurrence of this command will
be recorded in the Audit File and reported on by the Audit system.
EXECSIZE= Changes the default size parameter that the CA Dynam/FI job exit puts on
EXEC statements. (Note that the format of this operand in the SET statement
is different from that in the DYNAM/FI option record.)

Because CA Dynam/FI appends the SIZE parameter to the end of the EXEC
statement, any of the VSE EXEC statement options that normally follow SIZE
(for example, GO) may not be used if CA Dynam/FI determines EXEC size.
FIPROG= Turns on or off CA Dynam/FI processing of files at OPEN/CLOSE. No DTF

modification will occur when set to OFF.
SEARCH= Determines the degree of support for DTFCD/DTFPR (UR), DTFDI (DI) and
DTFCP (CP). The operands UR, DI and CP, when specified, allow full support
for the corresponding file class while the operands NOUR, NODI and NOCP
suppress support. This parameter overrides the installation option defined for
the DI, CP, and UR parameters in the DYNAM/FI option record.
SORTCORE= Requests dynamic file sorting facility (CA SRAM) of CA Dynam/FI to reserve a
block of storage from the partition GETVIS area for CA SRAM use instead of
letting CA SRAM use the upper portion of the partition for its work area. The
value of nnnnnn should be large enough to include storage requirements for all
CA SRAM tasks concurrently active in the partition plus a reserve for CA SRAM
overhead. For more information, see the CA SRAM documentation set.
This operand will result in a SRTCORE call to CA SRAM by CA Dynam/FI. The

default is no SRTCORE call resulting in CA SRAM using partition work space.
Note that the value of nnnnnn will be rounded up to the next even multiple of
1K bytes when the SRTCORE call is issued.
SYSLOG Support - ASSGN Statement
CA Dynam/FI SYSLOG support for unit record devices is controlled by a

variation of the ASSGN statement. With a particular ASSGN in effect, records
will be transferred to or from SYSLOG instead of the original unit record, or
tape, or disk device. The DTFCN record format (RECFM) is undefined (UNDEF).
Therefore, all CA Dynam/FI rules about padding and truncation when record
format changes apply to SYSLOG support.
ASSGN Format The format for ASSGN is shown below.
[//] ASSGN SYSxxx,SYSLOG
SYSxxx Indicates the standard logical unit name for the file(s) to be intercepted by
DYNAM/FI at I/O, and rerouted to or from SYSLOG. If more than one file has
this particular logical unit in its DTF, each one will receive SYSLOG routing.
SYSLOG support is available only for the following unit record devices:
SYSIPT Input files
SYSPCH Files routed to the punch queue
SYSLST Files routed to the print queue
6–28 User Guide

Note that the SYSxxx:
Physical assignment is not changed within the system; a replacement

DTFCN is generated to control the SYSLOG I/O.
I/O intercepts remain in effect for the duration of the VSE job unless reset
by another ASSGN for SYSxxx to a device other than SYSLOG. For
example:
// ASSGN SYSIPT,SYSIPT or // ASSGN SYSIPT,x'00E'
If you want SYSLOG support in subsequent jobs, you must reissue the
following:
// ASSGN SYSxxx,SYSLOG
SYSLOG Indicates that all DTFs with the logical unit specified for SYSxxx will have their
I/O operations rerouted to or from SYSLOG. For this action to be effective, you
must formally OPEN the file and initiate all I/O with logical IOCS imperative
macros. You should also use a CLOSE macro.
Input Data All SYSIPT read requests are preceded by a prompting message with the
following format:
CADF099D dtfname SYSIPT:
SYSIPT input data is converted to uppercase before being passed to the

requesting program. You can signal end-of-data for SYSIPT files by either
entering the EOD characters /* or by entering null data (simply pressing the
ENTER key without typing any characters). By entering null data, the running
program will react as if /* had been entered.
Output Data All SYSPCH and SYSLST writes to SYSLOG have the data line prefixed by:
D/FI-SYSLST: or,
D/FI-SYSPCH:
If the combined length of this prefix (13 characters) plus the length of the
data is greater than 256 characters, the data portion of the line will be
truncated to this maximum. If the combined length exceeds the length of one
console/screen line, wraparound will occur.
You can route the output of a DTFMT or DTFSD to the console (if the output is
in displayable characters). The following example shows how to do this.
// DLBL FILEOUT,,,,SYSPCH
ASSGN SYSPCH,SYSLOG
CA Dynam/FI first overrides the DTFSD logical unit with SYSPCH. The second
line reroutes SYSPCH output to SYSLOG.

You should be very careful when routing SYSPCH or SYSLST output to the
console. This is because a program can go into an "output loop" or produce a
great volume of output. It can be frustrating trying to stop a program from a
console that is constantly busy.
Example
This is an example of CA Dynam/FI SYSLOG support. The operator wants to

execute and display output from DFHCSDUP on the console.
Uppercase lines are printed by the system; lowercase lines are entered by the
operator. Explanatory comments are shown to the right, enclosed in
parentheses.
r rdr,pause
AR 0015 1C39I COMMAND PASSED TO VSE/POWER
F1 0001 1R88I OK : 1 ENTRY PROCESSED BY R RDR,PAUSE
BG 0001 1Q47I BG PAUSE 02219 FROM VSECQA8,
TIME=14:52:30
BG 0000 // JOB PAUSE
DATE 10/26/2007, CLOCK 14/52/30
BG-0000 // PAUSE
0 assgn sysipt,syslog (route SYSIPT reads to SYSLOG)
BG-0000
0 assgn syslst,syslog (route SYSLST writes to SYSLOG)
BG-0000
0 // exec dfhcsdup
BG 0000 1S54I PHASE DFHCSDUP IS TO BE FETCHED FROM PRD1.BASE
BG 0000 CADF-SYSLST:
BG 0000 CADF099D FISYSIN SYSIPT: (SYSIPT prompting message)

BG-0000
0 list list(vselist)
BG 0000 CADF099D FISYSIN SYSIPT:

BG-0000
0 /* (end-of-data entered)
BG 0000 CADF-SYSLST: LIST LIST(VSELIST)
6–30 User Guide

BG 0000 CADF-SYSLST: DFHCA5120 I PRIMARY CSD OPENED; FILENAME: DFHCSD

BG 0000 CADF-SYSLST: CICS RDO OFF-LINE UTILITY PROGRAM
TIME 14:53 DATE 07:299 PAGE 0001
BG 0000 CADF-SYSLST: DFHCSDUP: CICS OFF-LINE UTILITY (LIST)
CURRENT RELEASE: 4.1.1
BG 0000 CADF-SYSLST: CONTENTS OF

CICS SYSTEM DEFINITION FILE (CSD)
-------------------------------------------------
BG 0000 CADF-SYSLST: CSD CREATED BY RELEASE: 4.1.1

DATE CREATED: 07.184 11:58
LAST UPDATED: 07.186 11:49
BG 0000 CADF-SYSLST: *********************************************************

***************************************************************
BG 0000 CADF-SYSLST: SUMMARY OF LISTS

UTILITY COMMAND: LIST LIST(VSELIST )
BG 0000 CADF-SYSLST: *********************************************************

***************************************************************
BG 0000 CADF-SYSLST: LIST NAME: VSELIST
BG 0000 CADF-SYSLST: ----------
BG 0000 CADF-SYSLST: ELEMENT NAME DATE ADDED
BG 0000 CADF-SYSLST: ------- ---- ----------
BG 0000 CADF-SYSLST: GROUP DFHAKP 07.184 11:59 (IBM PROTECTED)

BG 0000 CADF-SYSLST: GROUP DFHBACK 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHBMS 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHCONS 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHEDF 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHFE 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHHARDC 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHINQUI 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHINTER 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHISC 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHJRNL 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHMISC 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHMSWIT 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHOPCLS 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHOPER 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHPGAIP 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHRMI 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHRSEND 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHRSPLG 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHSIGN 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHSPI 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHSTAND 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHVTAM 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHVTAMP 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHTYPE 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHTERM 07.184 11:59 (IBM PROTECTED)
6–32 User Guide

BG 0000 CADF-SYSLST: GROUP DFHFEPI 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHTCL 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHCLNT 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHIPECI 07.184 11:59
BG 0000 CADF-SYSLST: GROUP DFHWEB 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFHDOC 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP CICREXX 07.184 11:59
BG 0000 CADF-SYSLST: GROUP DFHRCF 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP VSETYPE 07.184 11:59
BG 0000 CADF-SYSLST: GROUP VSEAI62 07.184 11:59

TIME 14:53 DATE 07:299 PAGE 0002
BG 0000 CADF-SYSLST: GROUP VSETERM 07.184 11:59
BG 0000 CADF-SYSLST: GROUP VSETERM1 07.184 11:59
BG 0000 CADF-SYSLST: GROUP VSESPG 07.184 11:59
BG 0000 CADF-SYSLST: GROUP FCTSP 07.184 11:59
BG 0000 CADF-SYSLST: GROUP EZA 07.184 11:59
BG 0000 CADF-SYSLST: GROUP DFH$WBSN 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP DFH$STAT 07.184 11:59 (IBM PROTECTED)
BG 0000 CADF-SYSLST: GROUP CEE 07.184 12:00
BG 0000 CADF-SYSLST: GROUP TCPIP 07.184 12:00
BG 0000 CADF-SYSLST: GROUP CAICUI 07.184 13:29
BG 0000 CADF-SYSLST: GROUP FAQSPCS 07.184 13:34
BG 0000 CADF-SYSLST: GROUP DYNAM 07.184 13:35
BG 0000 CADF-SYSLST: GROUP CAVL 07.184 13:36
BG 0000 CADF-SYSLST: GROUP EVSE 07.184 13:37

Operator Device Switching Facility
BG 0000 CADF-SYSLST: GROUP EXPCTS 07.184 13:41
BG 0000 CADF-SYSLST: GROUP MCAT 07.184 13:45
BG 0000 CADF-SYSLST: GROUP VAID 07.184 14:06
BG 0000 CADF-SYSLST: GROUP EXPCQA 07.186 11:47
BG 0000 CADF-SYSLST: GROUP GSS 07.186 11:49
BG 0000 CADF-SYSLST: *********************************************************

***************************************************************
TIME 14:53 DATE 07:299 PAGE 0003
BG 0000 CADF-SYSLST: DFHCA5101 I LIST COMMAND EXECUTED SUCCESSFULLY.

BG 0000 CADF-SYSLST: DFHCA5123 I PRIMARY CSD CLOSED; FILENAME: DFHCSD
BG 0000 CADF-SYSLST: DFHCA5107 I COMMANDS EXECUTED SUCCESSFULLY: 1
COMMANDS GIVING WARNING(S): 0 COMMANDS IN ERROR: 0
BG 0000 CADF-SYSLST: DFHCA5108 I COMMANDS NOT EXECUTED AFTER ERROR(S): 0
BG 0000 CADF-SYSLST: DFHCA5109 I END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN
CODE WAS: 0
BG 0000 1S55I LAST RETURN CODE WAS 0000
BG-0000 1I00D READY FOR COMMUNICATIONS.
0
BG 0000 EOJ PAUSE MAX.RETURN CODE=0000
DATE 10/26/2007, CLOCK 14/56/20, DURATION 00/03/50

Many times, in scheduling a day's work, certain jobs are given a lower priority
than is really desirable, due to the lack of available tape drives. There are also
cases when a job must be put in a Wait State for a long period of time or even
canceled when available DASD space becomes saturated. The Operator Device
Switching Facility allows the operator to switch device types from TAPE to
DASD or from DASD to TAPE when presented with output tape mount
messages or DASD space recovery options.
6–34 User Guide

Requirements
For operator switching to be active:
The FISWTCH option of the DYNAM/FI option record must be specified at

installation time. For more information, see the DYNAM/FI option record in
There must be full Catalog support (CATALOG(YES) in the DYNAM/FI

option record).
Each file for which switching is to be permissible must be defined in the

Catalog with DYNAMFI(YES) and with a device type of FI instead of either
TAPE or DISK. (See the description of DYNCAT.)
The Catalog entry must contain all information to create either a tape or
disk file. This includes all options that affect CA Dynam/D, CA Dynam/T,
and CA Dynam/FI.
Operation
The device type selected by CA Dynam/FI is, as always, determined by the

label type (TLBL or DLBL). If, when presented with a tape mount message or
DASD space recovery options, the operator specifies a switch to the other
device type by responding DISK or TAPE, respectively. CA Dynam/FI will do
the following:
Replace the existing TLBL or DLBL with a label record of the opposite type.
Reinitiate the OPEN request.
Since the replacement label record has only the minimal required information,
the Catalog record must have all disk allocation values as well as all tape
options. In effect, all files eligible for switching must be completely catalog-
driven. DEFALLOC may be used in the absence of disk allocation values.
When switched files are processed as input, CA Dynam/FI recognizes that

switching has been done and, if necessary, overrides the TLBL or DLBL
statement in the job stream so the file may be accessed properly. In this case,
all data needed to process the file is recorded in the Catalog when the file is
created.
If a data file is defined as a generation data set, it is permissible for different

generations to reside on different device types. Again, the Catalog has all the
information needed for proper processing of any specified generation.

Using Other Software with CA Dynam/FI
Restrictions
As with any processing procedure that enhances system operation, there are
certain restrictions. In addition to the requirements specified above, the
following conditions must be met:
All CA Dynam products (CA Dynam/D, CA Dynam/T and CA Dynam/FI)

must be installed and active on the system for the duration of the job.
The program DTF type must be one that is supported by CA Dynam/FI.
The file may not be the SORTOUT file of CA SORT.
The NOFI operand must not be specified on the TLBL or DLBL statement.
If operator switching is requested and all of the above conditions are not met,
an appropriate message will be issued to the operator.
There are additional restrictions imposed by CA Dynam/D and CA Dynam/T.

For more information, see the chapters "Maintaining Tape Files" and "Disk File
Management."
With CA Dynam/D and CA Dynam/T
If you use CA Dynam/D and CA Dynam/T products, you should be aware that
the Catalog file you currently access will be also be used by CA Dynam/FI. The
entire CA Dynam family uses the same Catalog file. The CUI File Management
transaction and DYNCAT utility programs are used to control and maintain the
CA Dynam/FI characteristics relating to tape and disk data sets; DYNACC, and
DYNPRINT can be used to access the FI information in the Catalog.
Defining Data Set Types
For control and allocation by CA Dynam/D and CA Dynam/T, data sets are
defined to the Catalog as the following:
Tape data sets
Disk data sets
FI data sets
6–36 User Guide

CA Dynam/FI options may be associated with each, and a data set may be
switched from one device type to the other (as a default) by using the DYNCAT
ALTER command (or the CUI File Management transaction) to change its file
type characteristic. This means that disk allocation information and tape
density information may be associated with the same data set. To create the
following, ensure that you adhere to the specifications described here:
Data set on tape – supply a TLBL and specify that it is a TAPE data set in
the Catalog. CA Dynam/FI assures that the DTF type is changed to tape,
and CA Dynam/T controls it.
Same data set on disk – supply a DLBL statement and specify that the
data set is a DISK data set in the Catalog.
If you define the data set as FI in the Catalog, you must also define attributes
to permit both CA Dynam/D and CA Dynam/T control in the Catalog. In this
case, the resulting DTF type will be determined by the label type (TLBL or
DLBL). In addition, when presented with a scratch tape mount message or
while in DASD space recovery, the operator may direct that the file be written
on the other device type.
Data Set Names
Since the entire CA Dynam family uses the same Catalog file, duplicate data
set names with different file attributes may not exist in the Catalog. Any data
set defined in the Catalog as disk will be processed as an uncontrolled file by
CA Dynam/T. Tape options which are defined by CA Dynam/T users on the
TLBL (such as rewinding and unloading a tape at close) take precedence over
any conflicting CA Dynam/FI-defined options.
The following CPU- and partition-independent substitutions are supported by

CA Dynam/FI:
Substitution Example Resolved DSN
=== ===WORK BGAWORK
==@ ==@WORK BGAWORK
== ==WORK BGWORK
CPU-- CPU--WORK CPU-AWORK
Searching the Catalog
If you use CA Dynam/D, note that CA Dynam/FI searches the Catalog even
when you provide DLBL statements with EXTENT statements.

Job Control (JCL) Options
Users of CA Dynam/FI, CA Dynam/D and CA Dynam/T may define Job Control

options. CA Dynam/FI always receives control at OPEN/CLOSE time before
either CA Dynam/D or CA Dynam/T. Therefore, Job Control options which are
defined by CA Dynam/FI in the file DTF will be overridden by either CA
Dynam/D or CA Dynam/T.
For example, if both the CA Dynam/FI option REW and the CA Dynam/T option
RUN are specified for the same file, the RUN option (rewind and unload tape at
close) will prevail. The only exception to this rule is the CA Dynam/FI option
RELEASE (release a logical assignment at close) which is performed after the
CLOSE processing has completed. This overrides any conflicting CA Dynam/T
or CA Dynam/D options.
CA Dynam/FI replaces variables in the data set name such as '==' and 'CPU--'
(for partition- and CPU-independence) before attempting to access the Catalog
for an entry. Therefore, the Catalog entry must exist in its resolved form.
Since different partitions or systems may be using these data set names for
differing file structures, this is necessary for CA Dynam/FI to return the
attributes of each file.
With System Utilities
System utilities (either IBM or original equipment) generally have problems

with CA Dynam/FI. This is because most utility-style programs either do not
use LIOCS or inspect and modify their DTFs. In the latter case, since CA
Dynam/FI has substituted a new DTF in partition GETVIS, results can be very
unpredictable. Types of programs that fall into this category include the
following:
DASD or library backup programs

File manipulation programs
Report writers
VSAM utilities
Preprocessors (including those used by COBOL compilers).
You should use the DFEXCL option record to prevent programs of this nature
from interfacing with CA Dynam/FI.
6–38 User Guide

With Sort Packages
CA Dynam/FI relies upon the use of logical IOCS for file processing. By
trapping and modifying LIOCS requests, CA Dynam/FI is able to function. As a
rule, sort packages do not use LIOCS for processing and generally use
skeleton DTFs or a DTFPH. This incompatibility between methods of operation
makes it impossible for CA Dynam/FI to override the parameters specified for
the sort.
The record format and file structure information in the sort parameter
statements is used by the sort product internally for handling the data and
sorting the records. As a result, the label information and parameter values
specified for the sort product must reflect the true characteristics of the files to
be used (i.e., the file characteristics after modification by CA Dynam/FI).
The CA SORT system, however, contains an interface to CA Dynam/FI.
CA SORT
CA SORT, contains an interface to CA Dynam/FI. This interface allows CA

Dynam/FI to pass the necessary information about the true structure and
attributes of the applicable files to CA SORT. The block size, record length, and
record format as specified in the sort parameter statements are overridden by
the CA SORT interface using internal communications.
Limited support for concatenation of input files read by CA SORT is provided

by the CA Dynam/FI - CA SORT interface. CA Dynam/FI will pass the number
of input files to be concatenated to CA SORT, and subsequently perform label
and OPEN/CLOSE processing for the concatenated files. As CA SORT uses
physical IOCs, all concatenated input files must have the same physical and
logical characteristics.
When you use CA SORT with CA Dynam/FI, be sure that CA SORT rules and
conventions are followed. These include such things as:
All input files must have the same record format.

All input files must have the same record length and block length.
The record format may not change during the SORT from input to output
(unless by user exit).
The logical record lengths must be the same for all SORTIN and SORTOUT
files when fixed-length records are used.

Version attributes (record length, block size, and so on) for cataloged data
sets are updated by CA Dynam/FI when requested to do so by CA SORT,
normally after the sort output file has been closed. This is necessary because
the file table used by CA SORT (DTFPH) does not have provisions for record
format, block size or record length. As a result, the version attributes would be
incomplete unless a facility such as CA Dynam/FI was available to update
them. The cataloged data set must have DYNAM/FI=YES for the update
processing to be effective.
Note: In order for the Catalog to be properly updated by CA Dynam/FI, do not

use the CA Dynam/T DROP option for SORTOUT tape files.
CA SRAM
CA SRAM modules are normally loaded into the upper unused portion of the
partition. This may conflict with the user's program. For example, PL/I also
uses this upper portion of the partition. If there is a chance that a conflict may
occur, use the CA Dynam/FI SET SORTCORE statement. It reserves a block of
storage from the partition GETVIS for working space and overhead for SRAM.
For more information about calculating the storage requirement, see the CA
SRAM documentation set.
With Existing Programs
This section lists miscellaneous items of special interest if you are planning to
use CA Dynam/FI to modify the attributes of files processed by existing
programs or are designing new programs.
Files Assigned to IGNORE
Some user programs open files that are only occasionally or never used. These
files are often assigned to IGNORE to prevent a tape volume or disk space
from being dedicated to the unused file. Since normal OPEN/CLOSE processing
does not require label information to be present for files assigned to IGN, the
DLBL or TLBL statements for the file may no longer be in the job stream.
When this condition exists, and CA Dynam/FI locates a label record on the
partition or system standard label area for the same DTFNAME, unpredictable
results may occur.
For example, if a program opened an output tape file with the DTFNAME
'MASTER,' the logical unit assigned to IGN and no TLBL included in the job
stream, CA Dynam/FI might find DLBL and EXTENT information for a disk file
with the same DTFNAME on the system standard labels. In this condition, a
disk DTF would be constructed by CA Dynam/FI using the logical unit specified
in the EXTENT statement. This OPEN would then fail due to 'INVALID LOGICAL
UNIT' if, for example, the logical unit was assigned to the card reader.
6–40 User Guide

To correct the situation, simply include the proper label information in the job
stream. CA Dynam/FI determines that no DTF modifications are necessary,
and the file is ignored.
Logical Unit Number
If the only CA Dynam/FI option specified for a file is an overriding logical unit
number on a DLBL statement, the new logical unit should be different from the
one specified on the file's EXTENT statement. If the units are the same, FI may
not create a virtual DTF for the file. CA Dynam/FI will appear "not to work" for
the file.
To correct this situation, change the logical unit.
TRUNCS Support
All output files under the control of CA Dynam/FI are created with TRUNCS
support. This may, under some conditions, cause the end-of-file record to be
written on the last track of a file where it normally would not have been
placed. If the file is then read using a program which does not require any CA
Dynam/FI file changes and the logic module used to read the file does not
specify 'TRUNCS=YES', the last block of data and the end-of-file record may
not be read.
Therefore, if CA Dynam/FI is used to create a disk file, it should also be used

to read the file. This will ensure that both input and output logic modules
always contain compatible options.
Physical I/O
Programs and products that use physical I/O (PIOCS) are incompatible with CA
Dynam/FI.
Checkpointing
Tape files for which checkpointing is done cannot be modified by CA

Dynam/FI.
Wrong Length Record Error (WLRERR) Routines
CA Dynam/FI always replaces any existing WLRERR routines in the program

with its own. This may cause unusual results in programs that "expect" wrong
length records to exist in a file and perform special processing when they do
occur.

Using One IOAREA and IOREG
CA Dynam/FI will always set up the I/O register (IOREG) if one is specified in
the program DTF. Programs that indicate an IOREG but ignore the information
passed in it will have unexpected results.
CA Dynam/FI does not support PL/1 programs that have a DTF with one
IOAREA and unblocked record format. The PL/1 compiler establishes DTFs with
IOREG specified. If the DTF has one IOAREA and unblocked record format,
however, the IOREG values are ignored. In order to force usage of the IOREG
values, the PL/1 option 'BUFFERS=2' must be specified.
Limiting File-independence Processing
Due to the nature of changes made to control blocks during file independence,
it may be advantageous at times not to have DYNAM/FI processing active. The
following chart reviews the ways that you may "turn off" DYNAM/FI. Each of
the commands is explained in detail elsewhere in this manual.
To Cause CA Dynam/FI To Specify Statement/Parameter
Bypass processing for the EXCPPGM=(phase1,phase2,...phasen) (in

particular phases (programs) DFEXCL option record)
Be deactivated. FI will not be DISABLE DYNAM/FI (with CASAUTIL)

invoked by the System Adapter
at intercepts (SVC 2 and 4)
and AR commands.
Ignore cataloged information DYNAMFI=NO (defined for cataloged file

for a particular file using DYNCAT)
Ignore processing for a NOFI (on TLBL/DLBL)

particular file. No DTF changes
will be made for the file
Not access cataloged CATALOG(NO) (in DYNAM/FI option record)

information for any files in the
DYNAM Catalog
Turn off all CA Dynam/FI [//] SET DYNAM/FI OFF

processing in a specific partition
until specifically reset (SET
DYNAM/FI ON) or, in the case of
dynamic partitions, until end of
the POWER/VSE job
Turn off processing of files at [//] SET FIPROG OFF

OPEN/CLOSE. No DTF changes
will be made.
6–42 User Guide

Direct Access File Independence Facility (VCKD)

Direct Access File Independence, which we will refer to as VCKD (Virtual-
Count Key Data), is a system that provides support for IBM's Direct Access
Method on Fixed Block Architecture (FBA) devices.
VCKD allows programs that utilize Direct Access Method, at the logical IOCS
level, to execute on FBA devices without conversion to another access method.
With VCKD, it is not necessary to make any program modifications in order to
process direct access (DA) file-dependent programs using FBA devices. After
installation, VCKD is completely transparent to the user. In addition, all
programming languages and teleprocessing monitors are supported.
For more information about the standard syntax notation used, see the
chapter "Introduction."
Utility Programs
VCKD contains the following utility programs:
Clear Disk utility to format a Direct Access file that resides on an FBA disk
device
Backup/Restore utility to convert current DA files on a CKD device to an

FBA device
CKD DA disk file analyzer to assist in the allocation of the new FBA DA file
Record Formats
VCKD supports each of the following record formats:

Fixed unblocked
Records created by sequential disk work and nonwork files
Data Records
Data records may be accessed by any of the following:
Relative record in the format of TTTR or TTTTTTTTRR
Physical track addressing in the form of (MBBCCHHR)
Key reference

System Restrictions
VCKD has been designed to be transparent and flexible from the user's point
of view. Nevertheless, the system's design does impose a few restrictions.
The following are not supported:
Spanned unblocked records
Trailer labels
Physical IOCS (EXCP level)
If a user program utilizes extent processing, then the program must process
every extent.
For VCKD support to be active for a file, the programmer logical unit (SYS
number) must be assigned to an FBA disk before the file is opened.
Each partition that runs programs using VCKD must contain enough GETVIS
area to contain all input/output buffers and VCKD control blocks.
Activating VCKD
The activation procedure for VCKD is relatively simple and straightforward. All
required processing phases and supporting utilities are installed automatically
with the installation of CA Dynam/FI. Just follow these steps to activate the
Direct Access File Independence Facility for a particular file.
1. Specify VCKD(YES) in the DYNAM/FI option record. For more information,

see DYNAM/FI in the Programming Guide.
2. Allocate the new FBA DA file and create the required JCL. For more
information, see Allocating FBA Disk Files.
3. Create the new FBA file. For more information, see Creating FBA Disk
Files.
4. Ensure that each partition has enough GETVIS area to contain all VCKD
I/O buffers and file control blocks.
VCKD File Parameters
VCKD file parameters define the characteristics of the direct access file now
residing on the FBA disk. Each parameter is defined within the data set name
portion of the DLBL statement of the file. The specified parameters actually
become part of the data set name and must be specified at file creation.
6–44 User Guide

MAP={T|R} Defines track-mapping or record-mapping access to the file. For more

information, see Mapping FBA disk files.
Default: Track mapping
CYL=xxx Defines the file's cylinder offset to be used by VCKD. ("xxx" is the cylinder
number of the original CKD file.) Programs that access the file using the old
CKD extents (for example, programs that have hard-coded the cylinder/head
address) can continue to function without program modification. VCKD
internally converts the address and maintains address compatibility.
Default: Offset is not used. File starts at cylinder 00, head 0
KL=xxx Provides support for programs accessing DA files containing keys when the
following parameters have been omitted from the Assembler DTF or COBOL
select statements:
KEYLEN= for Assembler
ACTUAL KEY IS for COBOL
The parameter tells VCKD that the file was created with keys and that VCKD
should allow any program omitting the above parameters to receive only the
data portion of each record.
Default: Key length is taken from the user program DTF
Examples
Indicates record mapping.
// DLBL FBAFILE,'NEW.FBA.FILE.MAP=R',,DA
Indicates cylinder offset to start at cylinder 210.
// DLBL FBAFILE,'NEW.FBA.FILE.CYL=210',,DA
Indicates a file that contains a key length of 4 characters.
// DLBL FBAFILE,'NEW.FBA.FILE.KL=4',,DA

FBA Disk Files
Mapping FBA Disk Files
VCKD provides two data-mapping techniques for Direct Access files: full-track
mapping and record mapping.
Full-track mapping combines all the key and data records from the original
CKD track into one control interval. All I/O to the file is then performed at
the track level. If the file contains physical keys, track mapping must be
specified.
Record mapping creates a separate control interval for each data record on
the original CKD track. I/O for the file is then performed at the record
level. Record mapping provides faster access to records and reduced
storage requirements. However, it is supported only for fixed-length
records.
Specify the mapping technique as a parameter within the file name of a DLBL
JCL statement. This parameter has the following format:
MAP=T - for track mapping
MAP=R - record mapping
If MAP= is not specified, the default is full-track mapping. A file that has been
created for record mapping cannot be accessed as track-mapped.
Examples
Indicates record mapping.
// DLBL FBAFILE,'NEW.FBA.FILE.MAP=R',,DA Indicates track mapping, by default.
// DLBL FBAFILE,'NEW.FBA.FILE',,DA
Allocating FBA Disk Files
There are two methods of determining the number of FBA blocks to allocate
for the new FBA DA file: direct calculation, and VCKD Disk Analyzer Program
(VCKDANAL) use.
Direct Calculation
VCKD emulates each CKD track as "n" FBA blocks. The actual number of
FBA blocks that make up each CKD track is based upon the CKD device
type, key and data lengths, and the number of records per track.
6–46 User Guide

In general, the number of FBA blocks to allocate for each CKD track can be
calculated using the following formula:
(NRPT * KDL) + 4 + (3 * NRPT)

FBABLKS = ----------------------------- rounded high
512
KDL = key length + data length
NRPT = number of records per track for the disk type and
specified KDL
FBABLKS = number of FBA blocks to allocate per CKD track
Note that the number of allocated FBA blocks on the EXTENT statement
must be an even multiple of the number of FBA blocks that define an
emulated CKD track. Therefore, 1500 FBA blocks will define 100 CKD
tracks.
For example, on a 3340 device, a record size of 2552 bytes produces three
blocks per track totaling a maximum of 7656 bytes. Therefore, VCKD will
allocate 15 FBA blocks for each CKD track. The allocation is calculated as
follows:
(3 * 2552) + 4 + (3 * 3) 7656 + 4 + 9 7669

------------------------ = ------------ = ---- = 15 (when rounded up)
512 512 512
Using VCKDANAL
Another method to obtain the number of blocks to allocate for each CKD
track is to run the VCKD disk file analyzer program VCKDANAL. This
program will read the first track of your CKD DA file and compute the
required number of FBA blocks to allocate for each track. For more
information, see VCKDANAL.
Creating FBA Disk Files
You can use any of the following methods to create the new Direct Access file
on the FBA disk:
Format the FBA disk extent using the VCKD Clear Disk Program
(VCKDCLDK). Then restore the file with a user-written backup/restore
program that utilizes DTFDA LIOCS.
Restore the file with a user-written program that performs WRITE RZERO
and WRITE AFTER formatting writes.
Use the VCKD backup/restore program (VCKDBKRS) to copy the CKD file
to tape. Then restore the tape to the FBA disk.

VCKD Utility Programs
Backup/Restore Utility (VCKDBKRS)
The VCKD Backup/Restore program (VCKDBKRS) provides a convenient

method to convert Direct Access files from CKD to FBA devices. Each Direct
Access file on the original CKD disk is copied to tape using the BACKUP=xxxx
option. The RESTORE option reads the backup tape and constructs the new file
on the FBA disk.
CA Dynam does not have to be enabled to convert the original CKD files to
tape or from tape to FBA files, but the VCKDBKRS program must be available.
Control Statement Format
Note that keywords are executed in the order specified on the statement.
BACKUP=xxxx [,MAP= {T|R } ]

[,CLEAR= {C'c'|X'xx' }]
[,MAXSIZE=nnnnn ]
[,EOF=Y ]
RESTORE [,CLEAR={C'c'|X'xx'} ]
BACKUP= Specifies the device type of the file to be copied to tape. Valid entries are
2311, 2314, 3330, 3340, and 3350.
RESTORE Restores the backup tape to the FBA disk.
MAP= Indicates track- or record-mapping. For more information, see Mapping FBA
Disk Files.
Default: Track mapping
CLEAR= Identifies fill character enclosed in single quotation marks (C'c' for EBCDIC,
X'xx' for hexadecimal). If specified during backup, any unused space between
the last record and the end of the control interval will be filled with the
indicated character. If specified during restore, all assigned FBA blocks will be
cleared with the indicated character before restoring the backup tape. CLEAR
should always be specified during a restore run. The clear character does not
have to be the same for the backup and restore of the same file.
MAXSIZE= Specifies the maximum record size for variable-length records within the file.
EOF=Y Causes an EOF record to be placed after the last control interval when the
backup file is restored.
File Names
CKDDISK - DLBL name for the DA file on the CKD disk.
6–48 User Guide

DATAPE - TLBL name for the backup tape.
FBADISK - DLBL name for the DA file on the FBA disk.
Device Assignments
SYS002 must be assigned to the tape.
The EXTENT statement can reflect any SYS number for the CKDDISK and
FBADISK files.
Examples
Backs up a CKD disk file to tape and restores it to an FBA disk using various
options.
// JOB VCKDBK BACKUP CKD DISK TO TAPE AND RESTORE ON AN FBA DISK
// TLBL DATAPE,'CKD.DA.TAPE'
// DLBL CKDDISK,'CKD.FILE',2099/365,DA
// EXTENT SYS003,CKDDSK,1,0,19,10
// ASSGN SYS003,DISK,VOL=CKDDSK,SHR
// ASSGN SYS002,X'281'
// EXEC VCKDBKRS
BACKUP=3330,CLEAR=X'FF',MAP=T,EOF=Y,RESTORE,MAXSIZE=650
/*
/&
Backs up a variable-length CKD disk file and restores it on an FBA disk.
// JOB VCKDBKRS BACKUP CKD DISK TO TAPE/RESTORE FBA DISK

// DLBL FBADISK,'FBA.FILE',2099/365,DA
// EXTENT SYS001,FBA300,1,0,100,200
// ASSGN SYS001,DISK,VOL=FBA300,SHR
// EXEC VCKDBKRS
BACKUP=3330,MAXSIZE=122,RESTORE
/*
/&
Restores the backup tape to an FBA disk.
// JOB VCKDBKRS RESTORE TAPE TO FBA DISK

// DLBL FBADISK,'FBA.FILE',2099/365,DA
// EXTENT SYS001,FBA300,1,0,100,200
// ASSGN SYS001,DISK,VOL=FBA300,SHR

// EXEC VCKDBKRS
RESTORE
/*
/&
Clear Disk Utility (VCKDCLDK)
The VCKD Clear Disk Utility (VCKDCLDK) program allows the user to format a
Direct Access file that will reside on an FBA disk device. If a user program does
not perform at a DA file using a WRITE RZERO or WRITE AFTER formatting
write, then VCKDCLDK must be executed. The utility control statements are
compatible with the IBM CLRDK program.
VCKDCLDK Control Statement Syntax
This program uses two different control statements: // UCL and // END. Apply
the following rules:
Separate all operands with commas.
Include an END statement.
// UCL B=(K=k,D=d) [,C'c'|X'xx'][,OY|ON] [,E=(eeee)|RECORD]

// END
UCL Specifies entry to clear disk utility.
B=(K=k,D=d) Specifies key and data block length.
k the length (in bytes) of the key (default is 0)
d the length (in bytes) of the data block (default is 100)
C'c'|X'xx' Identifies EBCDIC (C) or hexadecimal (X) fill character enclosed in single
quotation marks (default is x'00').
OY|ON Identifies output option.
OY Write disk check. (OY is the default.)
ON Do not write disk check.
E=(eeee)|RECORD Specifies emulated CKD device type. Valid entries are: 2311, 2314, 3330,
3340, and 3350, enclosed in parentheses. RECORD indicates record-mapping
support. If this operand is omitted, the default is 2311.
6–50 User Guide

END Specifies utility end statement.
Example
Formats an emulated 3340 track.
// JOB VCKDCLDK CLEAR DISK

// ASSGN SYS012,300 FBA DISK DRIVE
// DLBL UOUT,'FBA.DA.FILE',2099/365,DA
// EXTENT SYS012,FBA300,1,0,200,1500 ALLOCATE 1500 FBA BLOCKS
// EXEC VCKDCLDK
// UCL B=(K=0,D=2552),X'00',ON,E=(3340)
// END
/*
/&
Disk File Analyzer (VCKDANAL)
The VCKD disk analyzer program (VCKDANAL) reads the first track of a file
and determines the required number of FBA blocks to allocate for each track.
In addition, all extents are read to calculate the total number of FBA blocks
required for the complete file. VCKD does not have to be enabled in order for
VCKDANAL to analyze the CKD file. However, if the CKD disks are connected to
another CPU, then VCKDANAL must be installed on that system.
If you include MAXSIZE=, precede it with a comma.
ANAL=xxxx[,MAXSIZE=nnnnn]
ANAL=xxxx Specifies the device type (xxxx) to be analyzed. Valid entries are 2311, 2314,
3330, 3340 and 3350.
MAXSIZE=nnnnn Optional operand. Specifies the maximum record size (nnnnn) for variable-
length and undefined records within the file.
JCL Requirements
File name CKDDISK is the DLBL name for the DA file on the CKD disk.
Device The EXTENT statement can reflect any SYS number for CKDDISK.

Catalog Support for CA Dynam/FI
Example
Analyzes a CKD disk file.
// JOB VCKDANAL ANALYZE A CKD DISK FILE

// EXEC VCKDANAL
ANAL=3330
/*
/&
Catalog File
The CA Dynam Catalog management facility lets you control the attributes of
tape and disk files. The Catalog file contains information about data set
attributes (block size, record length, and so on). This information is either
automatically or manually cataloged using the DYNCAT utility program or the
CUI FILE Management online screens. By using the utilities, you can define file
attributes separate from job control.
The same Catalog is shared by CA Dynam/D, /T, and /FI. The Catalog need
only be created once. The locations of the Catalog and Audit files are saved
when they are accessed for the first time following IPL. Only one file of each
type may be used in a particular system, and it must not be moved except
through the appropriate DYNCAT and AUDTUTIL functions, which cause the
saved location to be updated.
File attributes defined in the Catalog are used in addition to the options
defined in job control. CA Dynam/FI overrides the Catalog information with
definitions found on TLBL and DLBL statements.
Setting Catalog Support
There are two stages of catalog support for CA Dynam/FI:
CATALOG(YES|NO) (set in the DYNAM/FI option record, for all data sets),
and
DYNAMFI=YES|NO (set in the DYNCAT/CUI File Management utilities, for a

particular cataloged data set).
6–52 User Guide

The DYNAM/FI installation option CATALOG(YES) instructs CA Dynam/FI to

access the Catalog to obtain information; CATALOG(NO) indicates that no
catalog calls will be made by CA Dynam/FI.
The DYNCAT DEFINE/ALTER operand DYNAMFI=YES allows CA Dynam/FI to

access a particular data set's attributes. Therefore, if you want to exclude a
cataloged data set from CA Dynam/FI processing, use DYNAMFI=NO. If you
want CA Dynam/FI to access catalog information, be sure that both
CATALOG(YES) and DYNAMFI=YES are set.
Maintaining Catalog Information
CA Dynam/FI uses the data set attributes to ensure that new versions of a
data set are created with the desired block size, record format, and so on. The
version attributes are used to properly process existing versions of a data set.
CA Dynam/FI will always access the most current version (version 1) of a data
set unless a CA Dynam/T or /D generation option is specified on the
TLBL/DLBL. In other words, if you want to access catalog information for a
version other than version 1, you must use a CA Dynam/T or /D generation
option on the TLBL/DLBL. For example, the following JCL accesses generation
information for versions 2 of DISK.FILE and TAPE.FILE.
// DLBL DISKIN,'DISK.FILE(G-1)'
// TLBL TAPEIN,'TAPE.FILE.(-1)'
// TLBL TAPEIN,'TAPE.FILE',,,,,2
Version attributes are updated by CA Dynam/FI at output only when requested

by CA SORT.

Chapter 7: Using Online Panels−CAICUI
Introduction to the File Management System

The CA Dynam VSE online transaction lets you display and update information
stored in the CA Dynam Catalog. It has been rewritten to comply with the
Common User Interface (CAICUI) VSE component and is now called File
Management. CAICUI provides a set of standards for the CA VSE product line.
All VSE products running under the Common User Interface follow these
standards, creating a common look as well as a common method of use for all
CA VSE products.
All CA Dynam panels that have been modified to meet the new VSE standards
are referred to as File Management panels; however, they perform the same
basic functions as the previously used CA Dynam VSE panels (with some
exceptions as noted).
Note: The CUI transaction is the main component of CAICUI. It controls other
CA product transactions and maintains product resource definitions. For more
information about using and customizing your CAICUI session, see the CA CIS
PF Keys
You can use the following PF keys to move around File Management panels.
They are supplied with File Management and take effect upon initialization:
PF Command Function Executed

Key
1/13 HELP Request help for the current panel
3/15 QUIT Quit the current panel and return to the previous
panel level
5/17 SWItch Return to the previous panel in a series of panels

BACkward
6/18 SWItch Switch forward to the next panel in a series of panels

FORward
7/19 BACkward Scroll the current panel backward one full panel length
Chapter 7: Using Online Panels−CAICUI 7–1

PF Command Function Executed

Key
8/20 FORward Scroll the current panel forward one full panel length
12/24 EXIT Exit the transaction
These default PF keys are panel-specific; that is, they are specifically assigned
to every panel to correspond to that panel's particular functionality. For
example, some panels contain only one panel of information and do not scroll
backward and forward. Therefore, they are not supplied with PF keys [PF7] /
[PF19] (Backward) and [PF8] / [PF20] (Forward). Other panels belong to a
"series" of related panels that are all on the same "level." These panels,
therefore, are supplied with PF keys [PF5] / [PF17] (Switch Backward) and
[PF6] / [PF20] (Switch Forward) to scroll through the series. Panels that do
not belong to a series are not assigned these PF keys.
Every panel, however, is assigned PF keys [PF1] / [PF13] (Help), [PF3] /

[PF15] (Quit) and [PF12] / [PF24] (Exit).
Although these PF key settings are hard-coded as defaults, they can be

changed by the user or the System Administrator at any time during the
session, either for the entire CUI transaction or for a specific panel. Setting PF
keys is discussed in the "Common User Interface" chapter of the CA CIS
Administration Guide.
Available Command Types
When using File Management, there are three types of commands that are
available: long, short or special.
Long Commands
Long commands further subdivide into three categories: global, immediate,

and local:
Global commands are issued from any panel running under the CUI
transaction. Control is transferred to a different panel.
You can use global commands to move around File Management panels or
to customize your CUI transaction. For example, you can use the DYNAM
MENU global command to transfer to the File Management main menu
panel (CAYD-0000) from anywhere within the CUI transaction, or you can
use the CUI QUERY STATUS global command to transfer to the CAICUI
Session Status Selection Panel (CUI-S000).
7–2 User Guide

Each global command that can be used to immediately transfer to File

Management panels is included in each panel description. For more
information about global CAICUI commands, see the CA CIS
Administration Guide.
Immediate commands are issued from any panel running under the CUI
transaction Control remains with the current panel.
Immediate commands set control information or affect some component of

the system. For example, you can issue the SET PF command to change
the PF key settings within your CUI transaction. DYNCAT is an immediate
command that is available for File Management specifically. For more
information about the DYNCAT command, see DYNCAT Command.
Local commands are available only on specific panels and affect only the
panel from which they are issued.
Local commands can be used to scroll through a panel display or a series

of panels (for example, scrolling commands such as TOP, BOTTOM,
SWITCH FORWARD and SWITCH BACKWARD are local commands). Local
commands also have special functions when made available on certain
panels. When available, all local commands are included in each panel
description.
Short Commands
Short commands are available on directory panels to be used in the short

command field (Cmd). They are used to perform a variety of functions on
directory panels (for example, the DSP command displays a specific directory
entry in detail, or the AUX command transfers you to the Auxiliary Record
Panel). When available, all short commands are included in each panel
description.
Special Commands
Special commands are also available within the File Management system,
including fastpath command processing. Using fastpath is equivalent to
entering global long commands to call certain panels for display. For more
information about using special commands, see the CA CIS Administration
Guide.

Global Display Command Summary

Once you become more familiar with the File Management system and the CUI
transaction, you can use the following global display commands to move
around File Management panels. This summary includes panel IDs, a brief
description of the panels that are displayed, and the commands that can be
used to get you there.
Panel ID Description Command
CAYD-0000 File Management main menu DYNAM MENU
CAYD-1000 File Management system options DYNAM OPTION Menu

menu
CAYD-1100 CA Dynam/D System Options DYNAM Display

Selection DOPTIONS Menu
CAYD-1111 CA Dynam/D processing options DYNAM Display

D1OPTions
CAYD-1112 CA Dynam/D processing options DYNAM Display

D2OPTions
CAYD-1113 CA Dynam/D option codes DYNAM Display

D3OPTions
CAYD-1114 CA Dynam/D DLBL Option Codes DYNAM Display

D4OPTions
CAYD-1115 CA Dynam/D ECFLAG Display DYNAM Display

D5OPTions
CAYD-1120 CA Dynam/D LUB Exclusions DYNAM Display

DDLUBEX
CAYD-1130 CA Dynam/D DTF Exclusions DYNAM Display

DDDTFEX
CAYD-1200 CA Dynam/T System Options DYNAM Display

Selection TOPTIONS Menu
CAYD-12A0 CA Dynam/T Virtual Tape Information DYNAM Display

DTVIRT
CAYD-1211 CA Dynam/T processing options DYNAM Display

T1OPTions

T2OPTions

T3OPTions
7–4 User Guide


T4OPTions
CAYD-1215 CA Dynam/T TLBL Option Codes DYNAM Display

T5OPTions
CAYD-1216 CA Dynam/T ECFLAG Display DYNAM Display

T6OPTions
CAYD-1220 CA Dynam/T tape drive pool DYNAM Display

information DTPOOL
CAYD-1230 CA Dynam/T tape drive lock name DYNAM Display

definition DTLOCK
CAYD-1240 CA Dynam/T VM dedicated tape drive DYNAM Display

information DTNODET
CAYD-1250 CA Dynam/T DTF exclusion panel DYNAM Display

DTDTFEX
CAYD-1260 CA Dynam/T LUB exclusion panel DYNAM Display

DTLUBEX
CAYD-1270 CA Dynam/T cross system node DYNAM Display

information DTNODE
CAYD-1280 CA Dynam/T DTPATH information DYNAM Display

DTPATH
CAYD-1290 CA Dynam/T tape library information DYNAM Display DTLIB
CAYD1300 CA Dynam/FI System Options DYNAM Display

Selection FOPTIONS Menu
CAYD-1311 CA Dynam/FI processing options DYNAM Display

F1OPTions
CAYD-1312 CA Dynam/FI processing options DYNAM Display

F2OPTions
CAYD-1313 CA Dynam/FI ECFLAG Display DYNAM Display

F3OPTions
CAYD-1320 CA Dynam/FI exceptional program DYNAM Display

information DFPROG
CAYD-1330 CA Dynam/FI program exclusion DYNAM Display

information DFEXCL
CAYD-1400 CA Dynam/COMMON System Option DYNAM Display

Selection COMOPTIONS Menu
CAYD-1410 CA Dynam/COMMON system DYNAM Display

processing options COMOPTIons

DYNCAT Command
CAYD-1420 CA Dynam/COMMON DASD AVR DYNAM Display

information COMAVR
CAYD-1430 CA Dynam/COMMON LUB information DYNAM Display

COMLUB
CAYD-1440 CA Dynam/COMMON DASD pool DYNAM Display

information COMPOOL
CAYD-1500 CA Dynam/D, CA Dynam/T, DYNAM Query STATus

CA Dynam/FI system status
information
CAYD-1600 CA Dynam Copy or Delete Option DYNAM Display

Records COPYSCR
DYNCAT Command
DYNCAT is an immediate command that executes the CA Dynam DYNCAT
command from the File Management online environment. Simply prefix all CA
Dynam DYNCAT commands with the keyword DYNCAT. It can be issued by
System Administrators only.
The File Management DYNCAT command can be issued from the command line
of any panel running under the CUI transaction; however, because of the
length of many CA Dynam DYNCAT commands, it may have to be issued from
the CAICUI Command Mode Panel (CUI-S600). This panel features an
extended command line to facilitate the processing of lengthy commands, and
requires no continuation characters.
Certain CA Dynam DYNCAT commands are restricted from use in File

Management. These include ACTION, BACKUP, MACC, RESTORE, SCRATCH,
INITIAL, and INT.
Local Command Summary

The following local commands are available with most File Management
panels. Like PF keys they are panel-specific; that is, they are specifically
assigned to every panel to correspond to that panel's particular functionality.
For example, only those panels that belong to a series of panels are assigned
SWITCH FORWARD and SWITCH BACKWARD command functionality.
7–6 User Guide

Accessing the File Management System
BACkward nnn Scroll backward nnn panels. The default is 1.
BOTtom Scroll to the bottom of the panel display.
DOwn nnn Scroll down nnn lines. The default is 1.
FORward nnn Scroll forward nnn panels. The default is 1.
SWI/BAC Switch backward to the previous panel level.
SWI/FOR Switch forward to the next panel level.
TOP Scroll to the top of the panel display.
UP nnn Scroll up nnn lines. The default is 1.

When you sign on to the CUI transaction, the CAICUI Primary Selection Panel
(CUI-MENU) is displayed, listing all of the functions available to you. To access
the File Management option from this panel, the File Management main menu
panel ID (CAYD-0000) must already be defined to your CAICUI main menu by
a Systems Administrator. If it has not been defined, the File Management
option will not appear on this panel and will not be accessible.
Note: Panel IDs can only be defined to your CAICUI main menu by a System
Administrator on the CAICUI Menu Selection/Security Panel (CUI-2300). The
panel IDs defined on this panel determine what products, or portions of
products, your CAICUI user ID can access. They also determine what is
displayed on your CAICUI Primary Selection Panel. If a product's main menu
panel ID is not defined to your CAICUI user ID, it will not be displayed on your
CAICUI Primary Selection Panel, and you will not be able to access that
product. For more information about defining CAICUI menus, see the CA CIS

An example of what might appear on your CAICUI main menu follows:
CUI-MENU Primary Selection Panel CAICUI

====>
Enter desired option number or any valid command and press the ENTER key.
1. CUI Session Status Selection

2. CUI Maintenance
3. Event Notification Selection
4. Event Notification Maintenance
5. File Management
1=Help 2= 3=Quit 4= 5= 6=
7=Backward 8=Forward 9= 10= 11= 12=Exit
To select the File Management option from this panel, enter its menu number
(in this case, 5) and press Enter, or tab down and press Enter. After you
become more familiar with the CUI transaction, you can optionally use CAICUI
global or special commands to immediately transfer to the panels of your
choice. For example, enter DYNAM MENU on the command line to
immediately transfer to the File Management Panel (CAYD-0000), or enter
DYNAM QUERY STATUS to immediately transfer to the System Status
Information Panel (CAYD-1400). You can also use fastpath command
processing (For more information, see the CA CIS Administration Guide.)
Local Commands
The following commands are available with the CAICUI Primary Selection Panel
(CUI-MENU). Type any of the following commands on the command line and
press Enter to execute these functions:
7–8 User Guide

File Management Panel (CAYD-0000)
File Management Panel (CAYD-0000)

When you select the File Management option from the CAICUI Primary
Selection Panel (regardless of the method used), the following panel is
displayed, listing all of the options available within the File Management
system.
Display the panel by doing the following:
Selecting File Management from the CAICUI Primary Selection Panel (CUI-
MENU)
Entering DYNAM MENU from anywhere within the CUI transaction
CAYD-0000 File Management CA Dynam

====>
Enter desired option number or any valid command and press ENTER:
1. System Options
2. Data Set Maintenance
3. Tape Volume Maintenance
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
To select a menu option, enter the desired menu number and press Enter, or
tab down to the desired option and press Enter. You can optionally enter a
CAICUI command on the command line, and press Enter to select and display
the panel of your choice.
The following summarizes each File Management menu option:
Select Option To
1. System Options Display or modify the various processing

options, option codes, and system status
information defined for CA Dynam/D, CA
Dynam/T, CA Dynam/FI and the CA
Dynam/Common. Documentation for this
function can be found in the Programming
Guide.
2. Data Set Maintenance Display a directory of the CA Dynam/D, CA

Dynam/T and CA Dynam/FI data sets contained
in the CA Dynam Catalog. You can optionally
add, delete or display Catalog data sets, as well
as auxiliary comments and messages defined
for a particular data set. You can also display
and update a data set's attributes.

System Options
Select Option To
3. Tape Volume Maintenance Display a directory of the tape volumes

contained in the CA Dynam Catalog. You can
display and update a tape volume's attributes,
as well as a directory of the data sets contained
in a particular tape volume.
Local Commands
Type any of the following commands on the command line and press Enter to
execute these functions:
System Options
For more information about System Options, see the Programming Guide.
Data Set Maintenance

The Data Set Maintenance branch of the File Management system displays a
directory of the CA Dynam/D, CA Dynam/T and CA Dynam/FI data sets (DISK,
TAPE and FI) contained in the CA Dynam Catalog. It lets you do the following:
Display a specific or generic data set directory list
Add data sets to the Catalog
Delete data sets from the Catalog
Display and update a data set's attributes
Display the comments and auxiliary messages currently defined for a

specific data set
7–10 User Guide

Display a directory of active data set versions
Display data set versions in detail
For more information about field parameters, defaults and limitations, while
updating data set attributes, see the DEFINE and ALTER command descriptions
in the chapter "Maintaining The Catalog - DYNCAT Program."
A basic understanding of how to use the CUI transaction, including directory

panels, short commands and changing selection/relation criteria, is assumed.
For more information about using the CUI transaction, see the chapter
"Common User Interface" in the CA CIS Administration Guide.
Data Set Selection Panel (CAYD-2000)
This panel lets you select data sets from the CA Dynam Catalog for display. Do
the following to display this panel:
Select Data Set Maintenance from the File Management Panel

(CAYD-2000)
Enter DYNAM SELect DSN from anywhere within the CUI transaction
CAYD-2000 Data Set Selection CA Dynam

====>
Enter desired selection criteria or any valid command and press the ENTER key.
Relation Selection
Data Set: __ ____________________________________________
Type: __ ____ Data set type (Disk,Tape,FI)
Disk Type: __ __ Disk filetype (SD, DA, IS)
User ID: __ __ (character A-Z,0-9)
Owner ID: __ __ (character A-Z,0-9)
System ID: __ __ (character A-Z,0-9)
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
You can use this panel to do the following:
Display a specific data set.
Enter data specific to the desired data set in the selection and relation
fields. When you press Enter, a browse is initiated to search the CA Dynam
Catalog for a data set that matches the selection/relation criteria you
specified. If found, the data set is displayed on a directory panel; if no
matching data set is found, a blank directory panel is displayed.
Display a generic group of data sets.

Enter data specific to the generic group of data sets in the selection and
relation fields. Generic criteria is specified by entering an asterisk (*) as a
suffix to a root word (for example, enter ACC* in the Data Set selection
field to display all data sets in the Catalog whose names begin with ACC).
When you press Enter, a browse is initiated to search the CA Dynam
Catalog for any data sets that match the specified selection/relation
criteria. If found, any and all data sets that match are alphabetically
displayed on a directory panel. If no matching data sets are found, a blank
directory panel is displayed.
You can also select a group of generic data sets that end in a specific
character or combination of characters that have a specific character or
combination of characters imbedded within the data set name ('wild
cards'). To select all data sets ending in the characters PROD, enter
*PROD in the Data Set selection field. To select all data sets that have
PROD anywhere in the data set name, enter *PROD* in the Data Set
selection field.
Display all the data sets in the CA Dynam Catalog.
Press Enter on this panel without specifying any selection or relation

criteria. All data sets in the CA Dynam Catalog are displayed.
Selection Field Descriptions
Data Set Specifies the specific or generic name of the desired data set(s).
Type Specifies the type of the data set.
Disk Type Specifies the disk file type. SD, DA, and IS are valid entries.
User ID Specifies the user ID associated with the data set.
Owner ID Specifies the ownership code associated with the data set.
System ID Specifies the system ID associated with the data set.
Relations
Enter either the relation's abbreviation or equivalent symbol:
Abbreviation Symbol Relation
EQ = Equal to the selection criteria.
NE ^= Not equal to the selection criteria.
LT < Less than the selection criteria.
GT > Greater than the selection criteria.
7–12 User Guide

LE <= Less than or equal to the selection criteria.
GE >= Greater than or equal to the selection criteria.
Note: Only EQ/= or NE/^= can be entered in the Type relation field.
Data Set Directory Panel (CAYD-2100)
This panel displays an alphabetical list of data sets as selected on the Data Set
Selection Panel (CAYD-2000). It can contain a specific data set, a specific
group of data sets, or all of the data sets contained in the CA Dynam Catalog,
depending upon what selection/relation criteria were specified on the Data Set
Selection Panel. This panel is displayed by doing the following:
Pressing Enter on the Data Set Selection Panel (CAYD-2000), whether any
selection/relation criteria was specified
Entering DYNAM DISplay DSNDIRectory from anywhere within the CUI

transaction
CAYD-2100 Data Set Directory CA Dynam

====>
Cmd -------------- Data Set Name --------------- Type Disk User Owner System
___ ACC.PAYABLE.BACKUP TAPE AP AP
___ ACCOUNT.PAYABLE.FILE DISK AP AP
___ PAYROLL.BACKUP TAPE PD PD
___ PAYROLL.MASTER.FILE DISK PD PD
___ WORK.FILE.DATASET FI
___ EMP.FILE DISK SD
___ TAX.DEDUCTIONS DISK DA
___ DEPT.EXPENSE.FILE DISK IS
===> __ = = = =
____________________________________________ ____ __ __ __
1=Help 2= 3=Quit 4= 5= 6=
Change selection criteria
Issue local commands
Issue short commands
Cmd Use this area to enter short commands.
Data Set Name Displays the names of the data sets that meet the specified criteria. Also a
selection field.
Type Displays the data set type. Also a selection field.

Disk Displays the data set disk type.
User Displays the user ID associated with the data set. Also a selection field.
Owner Displays the ownership code associated with the data set. Also a selection
field.
System Displays the system ID associated with the data set. Also a selection field.
Local Commands
Type any of the following commands on the command line in the upper left-
hand corner of the panel and press Enter to execute these functions:
ADD Transfer to the Data Set Detail Panel (CAYD-2110) and add a new data set to
the Catalog.
Short Commands
Enter any of the following commands in the short command area (Cmd) on the
same line as the desired data set to execute these functions:
AUX Transfer to the Auxiliary Record Panel (CAYD-2140), which displays the
comments and auxiliary messages defined for the selected data set.
DEL Delete the selected data set from the Catalog.
Important! When maintaining multifile-volume data sets, if you perform the

DELete command on one file, CA Dynam/T applies it to all subsequent files of
the multifile set.
DSP Transfer to the Data Set Detail Panel (CAYD-2110), which displays in detail all
the attributes of the selected data set. If no other short commands have been
entered, you can display the same information by positioning the cursor
anywhere on the same line of the desired data set and pressing Enter.
7–14 User Guide

LST Transfer to the Disk, Tape or FI Version List panel, which displays a list of the
active versions for the selected disk, tape or FI data set.
DLP Delete with Purge option. Deletes the DATASET record from the catalog and
then deletes (purges) the associated disk files from the disk volumes that they
reside on. If the disk file no longer exists on the disk volume pointed to in the
catalog, a message is issued but the version record will have already been
deleted.
Changing Selection Criteria
You can overtype or enter any selection and/or relation criteria in the
unlabeled selection and relation fields at the bottom of the panel to redisplay a
directory list that matches the new criteria. Use these relational abbreviations
and symbols:
Note: Only EQ/= or NE/^= can be entered in the Type relation field.
Data Set Detail Panel (CAYD-2110)
This panel displays in detail the attributes of a selected data set. It is the first
in a series of 9 panels and is displayed by doing the following:
Executing the DSP short command on the Data Set Directory Panel
(CAYD-2100)
Switching forward or backward from the other panels in this series

Entering DYNAM DISplay DSNDETail from anywhere within the CUI

transaction
CAYD-2110 Data Set Detail CA Dynam

====>
Data Set: BGAWORK Password:

Type: FI Disk Filetype:
Ngens: 0 Retention: 2 Owner ID: Lock: NO

Density: Exp Date: 00/00/0000 User ID: AMF: NO
Block Size: 0 PED Date: System ID: Catalog OPEN: NO
Record Length: 0 PED Cycle: 0 Volume ID: Work Data Set: NO
Record Format: No Access: 0 Def Vault: A DYNAM/FI: NO
Tape Length: Opens: 0 File No: 1 Robot: YES
Sysno Override: Next Disk: 1 Virtape: NO Long GDG: NO
Previous File:
Next File:
DASD Primary Allocations:

Volume: Alloc Unit: Logical Unit:
Primary: Secondary: Number of Sec:
Vault Locations(001-025):
1=Help 2= 3=Quit 4= 5=Switch Bwd 6=Switch Fwd

Update the displayed data set
Display another data set (see the Data Set field description)
Define a new data set (see the Data Set field description)
Additional attributes of this data set are displayed on the other panels in this
series. You can update all of the fields on this panel (except Opens, File No.
and Next File) by tabbing to the desired field and overtyping the information
contained there. When you press Enter, the changes are recorded by the
Catalog update facility.
Data Set The name of the currently displayed data set, up to 44 characters.
You can use this field to select an existing data set for display, or to define a
new data set using the displayed data set as a model.
1. To select an existing data set for display, type its name in this field and
press Enter. The CA Dynam Catalog is browsed for the specified data set.
If found, it is displayed. If not found, a copy of the displayed data set is
created, using the specified name as the new data set name.
2. To define a new data set using the displayed data set as a model, type the
name of the data set to be created in this field and press Enter. A copy of
the currently displayed data set is created under the new name. You can
then modify its fields (except Opens, File No. and Next File) as desired.
Password The 1- to 8-character password required to update the data set.
7–16 User Guide

Type The type of the data set. Choose either DISK, TAPE or FI. If FI is specified, the
data set may be either a disk or tape that is available for dynamic device
switching.
If you select DISK, you will be transferred to the Data Set Disk Option
Panel (CAYD-2120) when you switch forward to the next panel in the
series.
If you select TAPE, you will be transferred to the Data Set Option Panel
(CAYD-2130) when you switch forward to the next panel in the series.
If you select FI, you will be transferred to either of the two panels
mentioned above.
Disk Filetype Displays the file type if disk is selected as the type of data set. SD, DA, or IS
(for ISAM) is displayed if disk was selected as the type of data set.
Ngens The number of disk data set generations to be saved. This may be a value
from 0 to 999
Retention The retention period (number of days) from 0 to 9999, or NO to clear.
Owner ID The 1 or 2 character ownership code for the data set, or NO to clear.
Lock YES prevents access to this data set, NO allows access.
Density The recording density of this data set (TAPE only) or NO to clear. Valid entries
are:
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI
CART for tape cartridge
00 for tape cartridge with buffered write mode
00E for tape cartridge with buffered write mode (3490E)
00M for tape cartridge with buffered write mode (3590)
00ME for tape cartridge with buffered write mode (3590E)
00MH for tape cartridge with buffered write mode (3590H)
00W for tape cartridge with buffered write mode (3592)
00WE for tape cartridge with buffered write mode (3592E)

03WE for tape cartridge with encrypted buffered write mode

(3592E)
08 for tape cartridge with data compaction and buffered

write
08E for tape cartridge with data compaction and buffered

write (3490E)
08M for tape cartridge with data compaction and buffered

write (3590)
08ME for tape cartridge with data compaction and buffered

write (3590E)
08MH for tape cartridge with data compaction and buffered

write (3590H)
08W for tape cartridge with data compaction and buffered

write (3592)
08WE for tape cartridge with data compaction and buffered

write (3592E)
0BWE for tape cartridge with encrypted data compaction and

20 for tape cartridge with unbuffered write mode
20E for tape cartridge with unbuffered write mode (3490E)
20M for tape cartridge with unbuffered write mode (3590)
20ME for tape cartridge with unbuffered write mode (3590E)
20MH for tape cartridge with unbuffered write mode (3590H)
20W for tape cartridge with unbuffered write mode (3592)
20WE for tape cartridge with unbuffered write mode (3592E)
23WE for tape cartridge with encrypted unbuffered write mode

(3592E)
28 for tape cartridge with data compaction and unbuffered

write
28E for tape cartridge with data compaction and unbuffered

write (3490E)
7–18 User Guide

28M for tape cartridge with data compaction and unbuffered

write (3590)
28ME for tape cartridge with data compaction and unbuffered

write (3590E)
28MH for tape cartridge with data compaction and unbuffered

write (3590H)
28W for tape cartridge with data compaction and unbuffered

write (3592)
28WE for tape cartridge with data compaction and unbuffered

write (3592E)

42 for 1600 BPI (9348 buffered write mode)
62 for 1600 BPI (9348 unbuffered write mode)
C2 for 6250 BPI (9348 buffered write mode)
E2 for 6250 BPI (9348 unbuffered write mode)
Exp Date The expiration date of this data set, or NO to clear.
User ID The 1- or 2-character user ID that will appear in each version record for
reporting purposes, or NO to clear.
AMF Indicates whether this automatic multifile tape data set is to be on a new
volume (NEW) or reset to a specific number (nnn). NO specifies that multifile
support is not used.
Block Size The block size, from 0 to 65535, of this data set (DISK & FI only).
PED Date The period-ending date of this data set, or NO to clear.
System ID The 1- or 2-character system ID of this data set for reporting purposes, or NO
to clear.
Catalog OPEN Indicates whether newly opened output versions of this tape data set will be
considered valid versions when opened. YES catalogs the data set at OPEN, NO
catalogs at CLOSE.
Record Length The logical record length of the file, from 0 to 65535.
PED Cycle The number of versions, from 0 to 999, being retained by the period-ending
date.

Volume ID: Indicates the 2-character volid, or NO to clear.
Work Data Set Indicate whether this is a tape work data set, either YES or NO.
Record Format The record format of the data set. Valid entries are:
F fixed length records
FB fixed block records
V variable length records
VB variable block records
U undefined records
NO removes specification
No Access The number of days, after last access, to retain a version of this data set
before it is eligible for scratch. A value from 0 to 9999.
Def Vault The default vault location for any version of the data set that does not
explicitly specify a vault location.
DYNAM/FI Indicate whether this data set is eligible for modification by CA Dynam/FI.
Specify YES or NO. NO will not allow CA Dynam/FI to access Catalog
information for this data set.
Tape Length The tape length of the data set volume. Specify:
XS extra short
S short
MS medium short
M medium
ML medium long
L long
NO removes specification
Opens The number of opens for this data set (display only).
File No The sequence number of this file if it is part of a chained or predefined multifile
data set (display only).
Robot: Indicates whether a robotic type tape device is allowed.
7–20 User Guide

Sysno Override Specifies whether a logical unit override is defined for a data set in the
catalog. Valid entries are:
001 to 255 Specifies a SYS number for the data set.
000 or NO Deactivates this parameter.
Next Disk The next disk generation ID number for CA Dynam/D-controlled disk
generation data sets.
Virtape Specifies whether a data set is a virtual file.
NO The file is not a virtual file.
VTAPE The file is a Virtual Tape.
FTAPE The file is a Fake Tape.
Previous File The data set name of the previous file if this is a chained or predefined
multifile tape data set.
Long GDG Specifies whether .G#nnnnnn will be placed in the last 9 bytes of the data set
name for a generation data set. nnnnnn can be any value from 000001 to
065535. NO means the old format of G#nn is used.
Next File The data set name of the next file if this is a chained or predefined multifile
tape data set (display only).
Volume The volume serial number, from 1 to 6 characters, where the extent will
reside.
Alloc Unit The unit of allocation to be made for the extent. Specify:
TRK for tracks
CYL for cylinders
BLK for FBA blocks
RCD for the number of records
Logical Unit The default logical unit for the extent.
Primary The number of units, from 0 to 999999, to be used for primary allocation of
this data set. This value is required.
Secondary The number of units, from 0 to 999999, to be used for secondary allocation of
this data set.

Number of Sec The number of secondary allocations to be made for this data set, from 0 to
255.
Vault Locations The vault location scheme for versions of this data set (TAPE only). Any
number of vault locations up to 999 can be specified. Separate the locations
by commas. Use the PF7 and PF8 keys to scroll through the list. Specify NO to
clear.
Local Commands
SWI/BAC Switch backward to the previous panel level.
SWI/FOR Switch forward to the next panel level.
Data Set Disk Option Panel (CAYD-2120)
This panel displays in detail the attributes of a selected DISK or FI data set. It
is the second in a series of 9 panels and is displayed by doing the following:
Entering DYNAM DISplay DSNDOPTions from anywhere within the CUI

transaction
CAYD-2120 Data Set Disk Option CA Dynam

====>
Data Set: ACCOUNT.PAYABLE.FILE

Align on cylinder boundary: YES Lock File Read Only: NO
Bypass AVR: NO Message to SYSLOG: YES
Truncate at CLOSE: NO
Delete INPUT File at CLOSE: NO No Auto Secondary Allocation: NO
Fragmentation allocation: NO Prohibit Dynamic LUB Allocation: NO
Enqueue file: NO Same Extents SORTIN/SORTOUT: NO
Messages to SYSLST: YES Truncate ISAM/Workfile: NO
Old file: NO Delete SORT Work Files: NO
Keep SD Work File: NO Delete file at CLOSE: NO

7= 8= 9= 10= 11= 12=Exit
7–22 User Guide

series. You can update all of the fields on this panel by tabbing to the desired
field and overtyping the information contained there. When you press Enter,
the changes are recorded by the Catalog update facility.
Field Descriptions
Fields are described in the following list.
Data Set The name of the currently displayed data set.
You can use this field to select an existing data set for display. Type the name
of the desired data set in this field and press Enter. The CA Dynam Catalog is
then browsed for that data set. If found, it is displayed. If not, an error
message is issued. You cannot create a new data set from this panel.
Align on cylinder Indicates whether to align files on a cylinder boundary.

boundary
Bypass AVR Indicates whether to bypass AVR.
Delete INPUT File at Indicates whether the VTOC entry should be deleted when closing an INPUT
CLOSE SD.
Fragmentation Indicates whether to force CA Dynam/D to fragment space allocation for the
allocation file.
Enqueue file Indicates whether to enqueue files opened for input, update or output.
Messages to SYSLST Indicates whether messages produced by CA Dynam/D will be directed to the
printer, SYSLST.
Old file Indicates whether you can access an existing SD file and open it without
having to reallocate it.
Keep SD Work File Indicates whether to keep the SD work file after closing the file.
Lock File Read Only Indicates whether the data set is locked for read-only usage.
Message to SYSLOG Indicates whether messages produced by CA Dynam/D will be directed to the
console, SYSLOG.
No Truncate at CLOSE Indicates whether to inhibit truncation of SD files at CLOSE.
No Auto Secondary Indicates whether to automatically provide for secondary allocations.

Allocation
Prohibit Dynamic Indicates whether to prohibit dynamic LUB allocation.

LUB Alloc.

Same Ext. Indicates whether SORTIN and SORTOUT space can be assigned to the same
SORTIN/SORTOUT area.
Truncate ISAM/Workfile
Indicates whether the ISAM work files will be truncated.
Delete SORT Work Files

Indicates whether to delete SORT work files at CLOSE.
Delete file at CLOSE Indicates whether to delete files from VTOC at CLOSE.
Local Commands
SWItch BACkward Switch backward to the previous panel level.
SWItch FORward Switch forward to the next panel level.
Data Set Option Panel (CAYD-2130)
This panel displays in detail the attributes of a selected TAPE or FI data set. It
is the third in a series of 9 panels and is displayed by doing the following:
Entering DYNAM DISplay DSNTOPTions from anywhere within the CUI

transaction
CAYD-2130 Data Set Option CA Dynam

====>
Data Set: ACC.PAYABLE.BAKUP
Tape Options:
Automatic Scratch: NO Unlabeled Tape Support: NO

Drop Label at CLOSE: NO Release Work Data Set: NO
Hold Assign at CLOSE: NO Volume Rotation: NO
Modify DTFNAME at OPEN: NO OPEN Disposition: RWD
CLOSE Disposition
FI options:
Record to Journal: NO Buffering Technique:

Ignore CNTRL Request: NO Label Processing:
No Tape Mark at CLOSE: NO Verification of OUTPUT: NO
Ignore TRUNC Request: NO
Release Assign at CLOSE: NO
7= 8= 9= 10= 11= 12=Exit
7–24 User Guide

series. You can update all of the fields on this panel by tabbing to the desired
Field Descriptions
Fields are described below.
You can use this field to select an existing data set for display. Type the name
of the desired data set in this field and press Enter. You cannot create a new
data set from this panel.
TAPE Data Set Fields
The following group of fields is specific to TAPE data sets:
Automatic Scratch Indicates whether this data set will be automatically scratched at CLOSE.
Drop Label at CLOSE Indicates whether the TLBL will be erased at CLOSE.
Hold Assign at CLOSE Indicates whether the ASSGN statement will be held at CLOSE.
Modify DTFNAME at Indicates whether the DTF name will be modified at OPEN.
OPEN
OPEN Disposition Indicates whether tapes are rewound (RWD) at OPEN or not rewound
(NORWD).
CLOSE Disposition Indicates whether tapes are rewound (RWD), not rewound (NORWD), or
rewound and unloaded (UNL) at CLOSE.
Unlabeled Tape Support

Indicates whether tapes will be processed as unlabeled.
Release Work Data Set Indicates whether work data sets will be scratched at CLOSE.
Volume Rotation Indicates whether volume rotation is supported.

FI Data Set Fields
The following group of fields is specific to FI data sets:
Record to Journal Indicates whether audit recording will be performed for this data set.
Ignore CNTRL Request

Indicates whether CNTRL requests will be ignored.
No Tape Mark at CLOSE

Indicates whether a tape mark will be written at CLOSE.
Ignore TRUNC Request

Indicates whether TRUNC requests will be ignored.
Release Assign at CLOSE

Indicates whether the logical assignments will be released at CLOSE.
Buffering Technique Displays the type of buffering supported. SB indicates single buffering, and DB
indicates double buffering.
Label Processing Displays the type of label processing supported. SL indicates standard label
processing, and UL indicates unlabeled processing.
Verification of OUTPUT Indicates whether output verification is supported. YES enables the VERIFY
option in the DTF.
Local Commands
Auxiliary Record Panel (CAYD-2140)
This panel displays the comments and auxiliary messages currently defined for
the selected data set. It is the fourth in a series of 9 panels and is displayed by
doing the following:
Executing the AUX short command from the Data Set Directory Panel
(CAYD-2100)
7–26 User Guide

Entering DYNAM DISplay AUXiliary from anywhere within the CUI

transaction
CAYD-2140 Auxiliary Record CA DYNAM

====>
Data Set: PAYROLL.FILE
Comment: THIS IS THE 2007 PAYROLL FILE
Open Input Destination: BOTH (Both, Console, Printer) Alarm: Y (Y/N)

Message: PAYROLL FILE HAS BEEN OPENED FOR INPUT
Open Output Destination: BOTH (Both, Console, Printer) Alarm: Y (Y/N)

Message: PAYROLL HAS BEEN OPENED FOR OUTPUT
Close Input Destination: PRINTER (Both, Console, Printer) Alarm: N (Y/N)

Message: PAYROLL FILE HAS BEEN CLOSED SUCCESSFULLY ON INPUT
Close Output Destination: PRINTER (Both, Console, Printer) Alarm: N (Y/N)

Message: PAYROLL FILE HAS BEEN CLOSED SUCCESSFULLY ON OUTPUT
KEKL1: L/H
KEKL2: L/H

7= 8= 9= 10= 11= 12=Exit
Update, add or delete comments and/or messages defined for the

displayed data set
Select another data set (see the Data Set field description)
Update, add, or delete the KEKL information defined for the displayed data
set
series. You can update or add any of the information contained in the fields on
this panel by tabbing to the desired field and overtyping the information
contained there. When you press Enter, the changes are recorded by the
Catalog update facility.
You can delete information by simply overtyping the entire field with spaces
and pressing Enter.
You can use this field to select another data set for display. Type the name of
the desired data set in this field and press Enter. You cannot create a new data
set from this panel.
Comment The 100-character comment field to be used for reporting purposes only.

OPEN Input Destination

Indicate whether the message issued at OPEN input is to be sent to the
CONSOLE, the PRINTER or BOTH.
Alarm Indicate whether the console above is to sound when this message is issued.
Message The message, up to 70 characters, to be issued at OPEN input.
OPEN Output Indicate whether the message issued at OPEN output is to be sent to the
Destination CONSOLE, the PRINTER or BOTH.
Message The message, up to 70 characters, to be issued at OPEN output.
CLOSE Input Destination

Indicate whether the message issued at CLOSE input is to be sent to the
CONSOLE, the PRINTER or BOTH.
Message The message, up to 70 characters, to be issued at CLOSE input.
CLOSE Output Indicate whether the message issued at CLOSE output is to be sent to the
Destination CONSOLE, the PRINTER or BOTH.
Message The message, up to 70 characters, to be issued at CLOSE output.
KEKL1 KEKL1 value, up to 64 characters.
L/H Key Encryption Method for KEKL1:

L—Encode the Key label as the label is specified.
H—Encode the Key label as a hash of the public key.
KEKL2 KEKL2 value, up to 64 characters.
L/H Key Encryption Method for KEKL2:

L—Encode the Key label as the label is specified.
H—Encode the Key label as a hash of the public key.
Local Commands
7–28 User Guide

Disk Version List Panel (CAYD-2150)
This panel displays a list of the active data set versions for DISK data sets
only. It is the fifth in a series of nine panels and is displayed by doing the
following:
Executing the LST short command from the Data Set Directory Panel
(CAYD-2100) for a DISK data set
Entering DYNAM DISplay DISKlist 'dsname' from anywhere within the

CUI transaction
CAYD-2150 Disk Version List CA Dynam

====>
Data Set: STEVE2

GDG Number Initial Create Create Date
Cmd Number Extents Volser Date Time Job Name Expires
___ N/A 0002 WORK01 07/16/2000 07:56 CREATE PERM

This is a display-only panel. You cannot update any of the displayed attribute
information. You may, however, change the data set name to view the
attributes of another data set. Additional attributes of the data set being
displayed, are also displayed on other panels in this series.
Data Set Displays the name of the currently displayed disk data set.
GDG Number Displays the disk generation ID of the version.
Note: This value is set to N/A if it is not a GDG version.
Number Extents Displays the number of extents contained in the version.
Initial Volser Displays the initial volume serial number of the version.
Create Date Displays the date the version was created.
Create Time Displays the time the version was created.

Job Name Displays the name of the job that created the version.
Date Expires Displays the date the version expires.
Local Commands
Short Commands
Enter the following command in the short command area (Cmd) on the same
line as the desired version to execute this function:
DSP Transfer to the DISK Version Detail Panel (CAYD-2180), which displays the
attributes of the selected version in detail. If no other short commands have
been entered, you can display the same information by positioning the cursor
anywhere on the same line of the desired version and pressing Enter.
DEL Deletes the version record from the catalog.
DLP Delete with Purge option. Deletes the version record from the catalog and then
deletes (purges) the associated disk file from the disk volume where it resides.
If the disk file no longer exists on the disk volume pointed to in the catalog, a
message will be issued but the version record will have already been deleted.
7–30 User Guide

Tape Version List Panel (CAYD-2160)
This panel displays a list of the active data set versions for TAPE data sets
only. It is the sixth in a series of 9 panels and is displayed by doing the
following:
(CAYD-2100) for a TAPE data set
Entering DYNAM DISplay TAPEList 'dsname' from anywhere within the

CUI transaction
CAYD-2160 Tape Version List CA Dynam

====>
Data Set: MULTI.FILE1

Version Vol Initial Create Create Date
Cmd Number Seq Volser Date Time Job Name Expires Vlt
___ 00001 0001 MULTI2 07/05/2000 10:27 CREATE 07/05/2000 A
___ 00002 0001 MULTI1 07/03/2000 14:21 CREATE 07/03/2000 A

displayed are also displayed on other panels in this series.
Data Set Displays the name of the currently displayed tape data set.
Version Number Displays the number assigned to the version.
Vol Seq Displays the volume sequence number assigned to the version.
Initial Volser Displays the initial volume serial number of the version. VTAPE-created
volumes are indicated by a (V).
Vlt Displays the vault location of the version.

Local Commands
Short Commands
DSP Transfer to the TAPE Version Detail Panel (CAYD-2190), which displays the
FI Version List Panel (CAYD-2170)
This panel displays a list of the active data set versions for FI data sets only. It
is the seventh in a series of 9 panels and is displayed by the following:
(CAYD-2100) for an FI data set
7–32 User Guide

Entering DYNAM DISplay FIList 'dsname' from anywhere within the CUI
transaction
CAYD-2170 FI Version List CA DYNAM

====>
Data Set: TEST.BACKUP.FILE1
Version Initial Create Create Date

Cmd Number Type Trk/Blk Volser Date Time Job Name Expires Vlt
___ 00001 TAPE 0 335500 12/12/2000 13:46 BACKUP 12/12/2000 A
___ 00002 TAPE 0 121400 12/11/2000 10:12 BACKUP 12/11/2000 A
___ 00003 TAPE 0 121200 12/11/2000 09:54 BACKUP 12/11/2000 A
___ 00004 TAPE 0 121100 12/10/2000 12:52 BACKUP 12/10/2000 A
___ 00005 TAPE 0 121000 12/10/2000 12:43 BACKUP 12/10/2000 A
___ 00006 TAPE 0 293900 11/28/2000 16:29 ICCF17X 12/31/2001 A
___ 00007 TAPE 0 112700 11/27/2000 11:29 ICCF17X 12/31/2000 A
___ 00008 TAPE 0 112700 11/27/2000 11:15 ICCF17X 12/31/1999 A
___ 00009 TAPE 0 112700 11/27/2000 11:14 ICCF17X 12/31/1999 A
___ 00010 TAPE 0 112700 11/27/2000 11:13 ICCF17X PERM A
___ 00011 TAPE 0 112700 11/27/2000 11:13 ICCF17X RETAIN A
___ 00012 TAPE 0 112700 11/27/2000 11:13 ICCF17X 12/31/2000 A

7= 8= 9= 10= 11= 12=Exit
displayed are also displayed on other panels in this series.
Data Set Displays the name of the currently displayed FI data set.
Version Number Displays the number assigned to the version.
Type Displays the version type.
Trk/Blk Displays the number of tracks or blocks occupied by the version.
Initial Volser Displays the initial volume serial number of the version. VTAPE-created
volumes are indicated by a (V).
Vlt Displays the vault location of the version.

Local Commands
Short Commands
DSP Transfer to the DISK or TAPE Version Detail Panel, which displays the
DLP Delete with Purge option. Deletes the version record from the catalog and then
deletes (purges) the associated disk file (if the version is a disk version) from
the disk volume where it resides. If the disk file no longer exists on the disk
volume pointed to in the catalog, a message will be issued but the version
record will have already been deleted.
DISK Version Detail Panel (CAYD-2180)
This panel displays a selected version of a DISK or an FI data set in detail. It is

the eighth in a series of 9 panels and is displayed by doing the following:
Executing the DSP short command for a DISK or an FI data set on the Disk
Version List Panel (CAYD-2150) or the FI Version List Panel (CAYD-2170)
7–34 User Guide

Entering DYNAM DISplay DISKVersion 'dsname' from anywhere within

the CUI transaction
CAYD-2180 Disk Version Detail CA DYNAM

====>
Data Set: PAYROLL.FILE Version: 00001

Generation: #00001
Format: Block Size: 00000
LRECL: 00100 Tracks/Blocks: 00000002
Expires: 08/16/2000
PED: 08/09/2000 Abs Version: 00003
Date Time Job Name Job Step CPU Part

Created: 08/09/2000 07:56 PAUSE DYNCAT A BG
Access: 08/09/2000 07:56 PAUSE DYNCAT A BG
Extent Volser
000 POOL01

Select another data set or version
Data Set Displays the name of the data set.
the desired data set in this field and press Enter. You cannot create a new data
set from this panel.
Version The number assigned to the displayed version.
You can use this field to select another version for display. Type the number of
the desired version in this field and press Enter. You cannot create a new
version from this panel.
Generation Displays the disk generation ID of the version (DISK only).
Format Displays the record format of the version.
LRECL Displays the logical record length of the version
Expires Displays the date the version expires.
PED Displays the period-ending date of the version.
Abs Version Displays the absolute version number of the version.
Block Size Displays the block size of the version.

Tracks/Blocks The number of tracks or blocks occupied by the version.
Created The information assigned to the version when it was created.
Access The information assigned to the version when it was last accessed.
Date The date the version was created or last accessed.
Time The time the version was created or last accessed.
Job Name The name of the job that created the version or was running when the version
was last accessed.
Job Step The name of job step performed when the version was created or last
accessed.
CPU The ID of the CPU used when the version was created or last accessed.
Part The ID of the partition used when the version was created or last accessed.
Extent The sequence number assigned to the volume when it was created or last
accessed.
Volser The volume serial number assigned to the version when it was created or last
accessed.
Local Commands
Type any of the following commands on the command line, and press Enter to
7–36 User Guide

TAPE Version Detail Panel (CAYD-2190)
This panel displays a selected version of a TAPE or an FI data set in detail. It is

the ninth in a series of 9 panels and is displayed by doing the following:
Executing the DSP short command for a TAPE or FI data set on the Tape
Version List Panel (CAYD-2160) or the FI Version List Panel (CAYD-2170)
Entering DYNAM DISplay TAPEVersion 'dsname' from anywhere within

the CUI transaction
CAYD-2190 Tape Version Detail CA DYNAM

====>
CADC611I END OF FILE
Data Set: PAYROLL.FILE Version: 00003
Format: Block Size: 00000 Virtual Tape: NO

LRECL: 00000 Blocks: 00000000
Expires: 08/19/2000 Total Errors: 00000
PED: 08/09/2000 Abs Version 00002
Created: 08/09/2000 10:27 PAUSE DYNCAT A BG
Access: 08/09/2000 10:27 PAUSE DYNCAT A BG
Vol Volser Date Time CUU Mode Fils O/Err I/Err Cleaned Opens Vlt
001 234234 08/09/2000 10:27 0000 1 0 0 00/00/00 0 A

Select another data set or version
the desired data set in this field and press Enter. The CA Dynam Catalog is
then browsed for that data set. If found, it is displayed. If not, an error
message is issued. You cannot create a new data set from this panel.
Version The number assigned to the version.
You can use this field to select another version for display. Type the number of
the desired version in this field and press Enter. The CA Dynam Catalog is then
browsed for that version. If found, it is displayed. If not, an error message is
issued. You cannot create a new data set from this panel.
Format The record format of the version.

LRECL The logical record length of the version.
Expires The date on which the version expires.
PED The period-ending date of the version.
Block Size The block size of the version.
Blocks The number of blocks occupied by the version.
Total Errors The number of input/output errors for the volume.
Abs Version The absolute version number of the version.
Virtual Tape Indicates whether the version exists on VTAPE (VTP), Faketape (FTP) or does
not exist on a virtual tape (NO).
Created The information assigned to the version when it was created.
Access The information assigned to the version when it was last accessed.
Date The date the version was created or last accessed.
Time The time the version was created or last accessed.
Job Name The name of the job that created the version or was running when the version
last accessed.
Job Step The name of job step performed when the version was created or last
accessed.
CPU The ID of the CPU where the version was created or last accessed.
Part The ID of the partition where the version was created or last accessed.
Vol The sequence number assigned to the volume when it was created.
Volser The volume serial number assigned when the volume was created.
Date The date the volume was created.
Time The time the volume was created.
CUU The device address upon which the volume was created.
Mode The recording density of the volume when it was created.
Fils The number of files on the volume.
O/Err The number of output errors that have occurred on the volume.
7–38 User Guide

Tape Volume Maintenance
I/Err The number of input errors that have occurred on the volume.
Cleaned The date the volume was last cleaned.
Opens The number of times the volume has been opened.
Vlt The vault location of the volume.
Local Commands
Type any of the following commands on the command line, and press Enter to

The Tape Volume Maintenance branch of the File Management system displays
a directory of the tape volumes contained in the CA Dynam Catalog. It lets you
do the following:
Display a specific or generic tape volume directory list
Display and update a tape volume's attributes
Display a directory of all data sets contained in a specific tape volume
A basic understanding of how to use the CUI transaction, including directory

panels, short commands and changing selection/relation criteria, is assumed.
For more information about using the CUI transaction, see the chapter
"Common User Interface" in the CA CIS Administration Guide.

Tape Selection Panel (CAYD-3000)
This panel lets you select tape volumes from the CA Dynam Catalog for
display. It is displayed by doing the following:
Selecting Tape Volume Maintenance from the File Management Panel

(CAYD-0000)
Entering DYNAM SELect TAPE from anywhere within the CUI transaction
CAYD-3000 Tape Selection CA DYNAM

====>
Enter desired selection criteria or any valid command and press the ENTER key.
Relation Selection
Volser: __ ______ Volume Serial Number

Length: __ __ Length Specification (XS,S,MS,M,ML,L)
Owner: __ __ Owner ID
Density: __ ____ Tape Density
Status: __ _______ Tape Status
Initialized: __ ________ Date Of Initialization (MMDDYYYY)
Last Cleaned: __ ________ Date Last Cleaned (MMDDYYYY)
1=Help 2= 3=Quit 4= 5= 6=
7= 8 9= 10= 11= 12=Exit
You can use this panel to:
Display a specific tape volume.
Enter data specific to the desired tape volume in the selection and relation
fields. When you press Enter, a browse is initiated to search the CA Dynam
Catalog for a tape volume that matches the selection/relation criteria you
specified. If found, the tape volume is displayed on a directory panel; if no
matching tape volume is found, a blank directory panel is displayed.
Display a generic group of tape volumes.
Enter data specific to the generic group of tape volumes in the selection
and relation fields. Generic criteria is specified by entering an asterisk (*)
as a suffix to a root word (for example, enter MULTI* in the Volser
selection field to display all the volsers in the Catalog whose names begin
with MULTI). When you press Enter, a browse is initiated to search the CA
Dynam Catalog for any tape volumes that match the specified
selection/relation criteria. If found, any and all tape volumes that match
are alphabetically displayed on a directory panel. If no matching tape
volumes are found, a blank directory panel is displayed.
7–40 User Guide

You can also select generically, volsers that end in a specific character or
combination of characters or volsers that have a specific character or
combination of characters imbedded with the volume serial number ('wild
cards'). To select all volsers ending in the characters A00, enter *A00 in
the Volser selection field. To select all volsers that have A00 anywhere in
the volser, enter *A00* in the Volser selection field.
Display all the tape volumes in the CA Dynam Catalog.
Press Enter on this panel without specifying any selection or relation

criteria. All tape volumes in the CA Dynam Catalog are displayed.
Selection Field
Descriptions The following section describes selection fields.
Volser Specify a specific or generic volume serial number.
Length Specify a tape volume length. Choose XS, S, MS, M, ML or L.
Owner Specify a 1 or 2 character ownership code.
Density Specify a tape volume density. Valid entries are:
800 for 800 bpi
1600 for 1600 bpi
6250 for 6250 bpi
00 for tape cartridge with buffered write mode
00E for tape cartridge with buffered write mode (3490E)
00M for tape cartridge with buffered write mode (3590)
00ME for tape cartridge with buffered write mode (3590E)
00MH for tape cartridge with buffered write mode (3590H)
00W for tape cartridge with buffered write mode (3592)
00WE for tape cartridge with buffered write mode (3592E)
03WE for tape cartridge with encrypted buffered write mode

(3592E)
08 for tape cartridge with data compaction and buffered

write

08E for tape cartridge with data compaction and buffered

write (3490E)
08M for tape cartridge with data compaction and buffered

write (3590)
08ME for tape cartridge with data compaction and buffered

write (3590E)
08MH for tape cartridge with data compaction and buffered

write (3590H)
08W for tape cartridge with data compaction and buffered

write (3592)
08WE for tape cartridge with data compaction and buffered

write (3592E)

20 for tape cartridge with unbuffered write mode
20E for tape cartridge with unbuffered write mode (3490E)
20M for tape cartridge with unbuffered write mode (3590)
20ME for tape cartridge with unbuffered write mode (3590E)
20MH for tape cartridge with unbuffered write mode (3590H)
20W for tape cartridge with unbuffered write mode (3592)
20WE for tape cartridge with unbuffered write mode (3592E)
23WE for tape cartridge with encrypted unbuffered write mode

(3592E)
28 for tape cartridge with data compaction and unbuffered

write
28E for tape cartridge with data compaction and unbuffered

write (3490E)
28M for tape cartridge with data compaction and unbuffered

write (3590)
28ME for tape cartridge with data compaction and unbuffered

write (3590E)
7–42 User Guide

28MH for tape cartridge with data compaction and unbuffered

write (3590H)
28W for tape cartridge with data compaction and unbuffered

write (3592)
28WE for tape cartridge with data compaction and unbuffered

write (3592E)

Status Specify a tape volume status. Choose SCRATCH, ACT-MAN, C-$TEST, C-LOCK,
NO-CLSD, DELETED, LOCKED, or ACTIVE.
Initialized Specify an initialization date.
Last Cleaned Specify the date on which the desired tape volume or group of tape volumes
was last cleaned.
Relations Enter either the relation's abbreviation or equivalent symbol:
Note: Only EQ/= or NE/^= can be entered in the Length, Density and Status
relation fields.

Tape Directory Panel (CAYD-3100)
This panel displays an alphabetical list of tape volumes as specified on the

Tape Selection Panel (CAYD-3000). It can contain a specific tape volume, a
specific group of tape volumes, or all of the tape volumes contained in the CA
Dynam Catalog, depending upon what selection/relation criteria was specified
on the Tape Selection Panel. This panel is displayed by doing the following:
Pressing Enter on the Tape Selection Panel (CAYD-3000), whether any

selection/relation criteria was specified
Entering DYNAM Display TAPEDirectory from anywhere within the CUI

transaction
CAYD-3100 Tape Directory CA DYNAM

====>
Cmd Volser Len Own Density Initial Cleaned Opens Errors Status
___ MULTI1 1600 07/03/2000 00/00/0000 00004 000000 ACTIVE

___ MULTI2 1600 07/05/2000 00/00/0000 00016 000000 ACTIVE
___ MULTI3 1600 07/05/2000 00/00/0000 00002 000000 ACTIVE
___ SM0001 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0002 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0003 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0004 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0005 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0006 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0007 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ SM0008 1600 07/03/2000 00/00/0000 00001 000000 SCRATCH
___ 900711 1600 07/11/2000 00/00/0000 00001 000000 ACTIVE
===> = = = = = = = = =
______ __ __ ____ ________ ________ _____ ______ _______
1=Help 2= 3=Quit 4= 5= 6=
Issue short commands
Volser The volume serial number of the tape volume. Also a selection field. VTAPE
created volumes are indicated by a (V). FakeTape created volumes are
indicated by (F).
Len The length of the tape volume. Also a selection field.
Own The ownership code of the tape volume owner. Also a selection field.
Density The recording density of the tape volume. Also a selection field.
7–44 User Guide

Initial The date the tape volume was initialized. Also a selection field.
Cleaned The date the tape volume was last cleaned. Also a selection field.
Opens The number of opens that occurred. Also a selection field.
Errors The number of open errors that occurred. Also a selection field.
Status The status of the tape volume. Also a selection field.
Local Commands
Short Commands
Enter any of the following commands in the short command area (Cmd) on the
same line as the desired tape volume to execute these functions:
DAT Transfer to the Data Sets on Volume Panel (CAYD-3120), which displays a list
of all the data sets residing on the selected tape volume.
DSP Transfer to the Tape Volume Detail Panel (CAYD-3110), which displays the
attributes of the selected tape volume in detail. If no other short commands
have been entered, you can display the same information by positioning the
cursor anywhere on the same line of the desired tape volume and pressing
Enter.

Changing Selection Criteria
You can overtype or enter any selection and/or relation criteria in the
unlabeled selection and relation fields at the bottom of the panel to redisplay a
directory list that matches the new criteria. Use the following relational
abbreviations and symbols:
GE >= Greater than or equal to the selection

criteria.
Note: Only EQ/= or NE/^= can be entered in the Length, Density and Status
relation fields.
Tape Volume Detail Panel (CAYD-3110)
This panel displays in detail the attributes of a selected tape volume. It is the
first in a series of two panels and is displayed by doing the following:
Executing the DSP short command on the Tape Directory Panel (CAYD-
3100)
Switching forward or backward from the other panel in this series
7–46 User Guide

Entering DYNAM Display VOLume 'volser' from anywhere within the

CUI transaction
CAYD-3110 Tape Volume Detail CA DYNAM

====>
Volser: 001234 Volseq: 1 Version: Output Opens: 0
Files: 0 Vault: A Slot: Input Opens: 0
Owner: LN Density: 1600 Length: ML I/O Errors: 0
Clean: 555 TLMS Serv: TLMS Scr: (Y/N) External ID:
Status: SCRATCH Ext. Status: Last Cleaned Date: 11/22/1991
Expiration Date: Last Scratched Date: 04/16/1999
Initialized Date: 03/05/2000 Re-Initialized Date: 06/24/1991

Created:
Access: 04/07/1999 09:30 CICSINIT CACCSERV A F2
Comment: VOLUME MUST BE COPIED AND SENT OFFSITE
VTAPE Location: Virtape:

VTAPE File:

7= 8= 9= 10= 11= 12=Exit
View the current tape volume
Display another tape volume (see the Volser field description)
Additional attributes of this volume are displayed on the other panel in this
series. You can update certain fields on this panel by tabbing to the desired
Volser The volume serial number of the currently displayed tape volume.
You can use this field to select another tape volume for display. Type the
name of the desired tape volume in this field and press Enter. The
CA Dynam Catalog is then browsed for that tape volume. If found, it is
displayed. If not, an error message is issued. You cannot create a new tape
volume from this panel.
Files The number of files on the tape volume.
Owner The ownership code of the tape volume.
Clean The maximum number of tape errors to be allowed before the volume is
flagged to be cleaned.
Status The status of the tape volume.
Expiration Date The date on which the tape volume expires.

Initialized Date The date on which the tape volume was initialized.
Volseq The sequence number assigned to the volume.
Vault The vault in which the tape volume is located.
Density The density of the tape volume.
TLMS Serv TLMS ONLY. The status of the volume's service indicator. Service=in is normal
and, therefore, displayed as blank. Only=out will be displayed if the tape is not
in service.
Ext. Status The extended status information of the tape volume, if any.
UNCNTRL Last used for uncontrolled processing.
TLMSCON TLMS II conversion tape.
AC-TLMS Active TLMS volume.
OUTSERV Out of service.
UNLABEL Unlabeled data set.
DYNAM/B DYNAM/B CMS tape.
EXTERN Owned by another tape system.
Version The version number of the tape volume.
Slot The slot location of the tape volume.
Length The length of the tape volume.
TLMS Scr TLMS ONLY. The status of the scratch indicator for the volume. A status of
scratch=n will be displayed, indicating an active TLMS volume; otherwise, it is
blank.
Last Cleaned Date The date on which the tape volume was last cleaned.
Last Scratched Date The date on which the tape volume was last scratched.
Re-Initialized Date The date on which the tape volume was reinitialized.
Output Opens The number of output opens for this tape volume.
Input Opens The number of input opens for this tape volume.
I/O Errors The number of INPUT/OUTPUT errors for this tape volume.
7–48 User Guide

External ID The external owner ID of the tape volume.
Created The information assigned to the tape volume when it was created.
Access The information assigned to the tape volume when it was last accessed.
Date The date the tape volume was created or last accessed.
Time The time the tape volume was created or last accessed.
Job Name The name of the job that created the tape volume or was running when the
tape volume was last accessed.
Job Step The name of job step performed when the tape volume was created or last
accessed.
CPU The ID of the CPU where the volume was created or last accessed.
Part The ID of the partition used when the tape volume was created or last
accessed.
Comment The comment associated with this volser.
VTAPE Location The location of the virtual volume. This field will be blank if the volume is not a
virtual tape.
Virtape The type of virtual volume. The following values are displayed:
NO The volume is not a virtual tape.
VTAPE The volume is a VTAPE virtual volume.
FTAPE The volume is a FakeTape virtual volume.
VTAPE File The virtual file name of the volume. This field will be blank if the volume is not
a virtual tape.
Local Commands

Data Sets on Volume Panel (CAYD-3120)
This panel displays one line of information for each data set residing on a
particular tape volume. It is the second in a series of 2 panels and is displayed
by doing the following:
Executing the DAT short command on the Tape Directory Panel (CAYD-
3100)
Switching forward or backward from the other panel in this series
Entering DYNAM Display DSNVOLume 'volid' from anywhere within the

CUI transaction
CAYD-3120 Data Sets on Volume CA DYNAM

====>
Volume: MULTI1
File Seq --------------- Data Set Name --------------
00001 MULTI.FILE1
00002 MULTI.FILE2
00003 MULTI.FILE3
00004 MULTI.FILE4

This is a display-only panel. You cannot update any information on this panel
except for the Volume field. Additional attributes of this tape volume are
displayed on the other panel in this series. You can use this panel to do the
following:
Display another tape volume (see the Volume field description)
Volume The volume serial number of the currently displayed tape volume.
You can use this field to select another tape volume for display. Type the
name of the desired tape volume in this field and press Enter. The CA Dynam
Catalog is then browsed for that tape volume. If found, it is displayed. If not,
an error message is issued. You cannot create a new tape volume from this
panel.
File Seq The file sequence number assigned to the volume.
Data Set Name The names of the resident data sets.
7–50 User Guide

Local Commands

Chapter 8: Maintaining the
Catalog−DYNCAT Program
The DYNCAT utility program is used to create, maintain, and report upon the
Catalogs used by the CA Dynam system. These include the CA Dynam dataset
Catalog (CAICATL) and the VTOC index Catalogs, if indexed VTOC support is
being used. DYNCAT is provided with the combined CA Dynam system and
with any of its subset systems.
You request DYNCAT functions by submitting DYNCAT control statements. For

VSE users, these will be accepted from the SYSLOG device if the program is
executed from the console; or, if the program is executed from a job stream,
the control statements will be read from the SYSIPT device.
SYSIPT may be assigned to a card reader, magnetic tape unit, or DASD, and
must consist of 80-byte records. (For MVS users, the control statements will
be accepted from the operator console if the program is executed with
SYSPARM=CONSOLE, or they may be submitted from either SYSIN or any
sequential or partitioned dataset.)
Output is usually directed to the printer. However, you can use CA Dynam/FI
unit record simulation to direct the output file to disk, as in the example
below.
// DLBL FISYSLS,'OUTPUT.FILE',7,SD,,SYS008
.
.
Output to disk is not available without CA Dynam/FI because CA Dynam's

reporting format allows 133 characters, while IBM's DTFDI supports only 121
characters.
For more information, see the chapter “Controlling File Independence.”
Chapter 8: Maintaining the Catalog−DYNCAT Program 8–1

DYNCAT Control Statement Format
DYNCAT Control Statement Format

All DYNCAT control statements have the same general format:
Positions:
1 71 72 73 80
+-------------------------------------------------+ +--------+
< operation operands > cc
<*comments >
DYNCAT Control Statement Syntax
The following rules apply to DYNCAT statement syntax:

Control statements are free-form. Commands and operands may appear
anywhere within positions 1 and 71.
You can continue a control statement by placing a nonblank character in

position 72 and continue the information on the next statement between
positions 1 and 71. Up to 10 continuations can be supplied.
A blank must separate any complete operand and the continuation mark in
column 72.
If an operand enclosed in single quotation marks or parentheses must be

continued, the operand must go up to and include position 71 of the
control statement, and continue in position 1 of the next statement.
Comment statements must contain an asterisk (*) in position 1. Do not

insert any comment statements between continued control statements.
You may abbreviate certain DYNCAT commands and operands by

truncating their codes. They are shown as mixed case characters in the
manual to help you identify them. The uppercase letters are the minimum
abbreviation you may use to specify the command or operand; lower case
letters are optional.
For example, for the DEFINE command, DEFine shows that the minimum
specification allowed is DEF, but DEFI, DEFIN, and DEFINE are also
permitted.
Command field must be the first field in a control statement and cannot be
continued. It describes the type of statement.
8–2 User Guide

DYNCAT Functions
Operand field must be separated from the command field by at least one
blank character. The operand field consists of one or more parameters
(operands), separated by commas. This field may continue into
subsequent statements, if necessary. Each operand consists of a keyword
(name that identifies the operand type--may be more than one word) and,
optionally, values associated with the operand as follows:
− keyword
− keyword=value
− keyword='literal string'
− keyword=(value, value, ... )
Dates are processed by DYNCAT in the following forms, as indicated by the

operating system in which DYNCAT is run.
mm/dd/yy
mm/dd/yyyy
dd/mm/yy
dd/mm/yyyy
yyddd
yyyyddd
All dates in this section are shown in American format (mm/dd/yy), but
will be accepted in European format (dd/mm/yy) if the operating system is
so generated and if DATE(DDMM) is specified in the DYNAM/COMMON
option record.
DYNCAT Functions
DYNCAT performs the functions summarized in the following table:
To Use Command
Add a version manually to an existing dataset in ADD

the Catalog or to define externally owned tape
volumes
Add a new data set name or sort key record to DEFINE

the Catalog
Change an entry in the Catalog ALTER
Change an existing data set name to a new RENAME

name or to move a version of a dataset to a new
dataset

DYNCAT Functions
To Use Command
Define a pool of scratch tapes or modify the SCRPOOL

characteristics of a scratch tape
Delete an entry from the Catalog or to delete any DELETE

active generation from a dataset, immediately
returning its associated volume to SCRATCH
status
Display the Catalog utilization statistics STATUS
End DYNCAT processing END
Establish or change the Catalog identification OWN
Vault description for any vault location to be VAULT

used
Format the Catalog INITIAL
Create or delete a VTOC index on a DASD VTOC

volume if CA Dynam indexed VTOC support is to
be used
Initialize a tape for use by CA Dynam/T and INT

unload the initialized tape
Initialize a tape without unloading it INTR
Dequeue the CA TLMS or other external system MACC

Multiple Access (M:ACC) file
List the contents of the Catalog LISTCAT
Release the physical enqueue from a Catalog in a DEQUEUE

multi-CPU environment
Request DYNCAT processing options ACTION
Retrieve a saved copy of the Catalog from a tape RESTORE

or to reorganize the Catalog
Return eligible tape volumes to the scratch pool SCRATCH

and produce tape dataset reports
Save the Catalog on tape BACKUP
8–4 User Guide

Summary of Control Statement Syntax

ACTION Statement Required to change processing options.
ACTION CANCEL|NOCANCEL
ERR|NOERR
LOG|NOLOG
ADD Statement Required to manually add a dataset version to the Catalog or to define an
externally owned tape volume.
ADD 'data set name'

VOLser=(xxxxxx,...)
APPEND= {YES|NO }
CREate=date
DISK
EXPdate= {date|RETAIN|PERM }
EXTOwner=c
FILE=nn
GDSid=nn
JOBname='jobname'
PED=date
PERM= {YES|NO }
VERsion=nnn
VLTloc=c
VTAPLOC=’location’
VTAPFILE=’filename_first’
VTAPFILC=’filename_last’
ALTER Statement Required to change the characteristics of a dataset or version of a dataset.
ALTer 'data set name'

ALLoc=(volser,unit,q1,q2,q3,SYSnnn)
BLKSZ= {nnnnn|OPTimize|'OPT,nnnnn' }
CATOPEN= {YES|NO }
CIMSG= {'text,r'|NO }
CLOSE= {NORWD|RWD|UNL|NO }
COMment= {'text'|NO }
COMSG= {'text,r'|NO }
CREate=date
DEFvlt=c
DENsity= {cccc|NO }
{[A] [,B] [,D] [,E] [,F] }
DISKOPT=( {[,I] [,K] [,L] [,M] [,N] } )|NO
{[,O] [,P] [,S] [,T] [,W] }
{[,X] [,NA] }
DYNAMFI= {YES|NO }
EXPdate= {date|RETAIN|PERM|RT+nnn|CD+nnn|NO }
FILETYPE= {SD|IS|DA }

[AUDIT ]
[,NOCNTRL ]
[,NOTM ]
FIopt=( [,NOTRUNC ] )|NO
[,RELEASE|NORELSE]
[,SB|DB ]
[,SL|UL ]
[,VERIFY ]
GDGLONG= {YES|NO }
[ KEKL1='kekl1,[L|H]' ]
INDex=(volser,unit,q1,q2,SYSnnn)
JOBname='jobname'
LENgth= {XS|S|MS|M|ML|L|NO }
LOCK|UNLOCK
LRECL=nnnnn
MF= {NEW|nnn|NO }
MINDEX=(volser,unit,q1,q2,SYSnnn)
NEWPSWD='password'|"
NEXTGEN=nn
NGEN=nnn
NOACC=nnnn
OIMSG= {'text,r'|NO }
OOMSG= {'text,r'|NO }
OPEN= {NORWD|RWD|NO }
OVRfl=(volser,unit,q1,q2,SYSnnn)
OWner= {cc|NO }
PASSword='password'
PED=date
PEDCYC=nnn
PERM= {YES|NO }
PRIme=(sequence,volser,unit,q1,q2,SYSnnn)
RECFM= {F|FB|V|VB|U|NO }
RETain= {nnnn|NO }
SYsid= {cc|NO }
SYSNO={nnn|NO}
TAPE|DISK|FI
[AUTOSCR|NOAUTOSC]
[,DROP|NODROP ]
[,HOLD|NOHOLD ]
TAPEopt=( [,LABEL|NOLABEL ] )|NO
[,MODIFY|NOMODIFY]
[,RELEASE|NORELSE]
[,ROTATE|NOROTATE]
USerid= {cc|NO }
VERsion=nnn|VOLser=(xxxxxx)|GDSid=nn
VLTloc=(A,B,C,...,Z) [VLTSEQ=nnn]
VOLID=cc
WORK= {YES|NO }
8–6 User Guide

Required to change the characteristics of the sort key name record.
ALTer SKNAME='skname' FIELDS=(nnnn,nnnn,

format, {A|D }....)
FORMAT= {CH|BI|ZD|PD|FI|FL|CSL
|CTO|CST|CLO|AQ}
LRECL=nnnnn
RECFM= {F|V }
Required to change the characteristics of a tape volume.
ALTer volser
CLean= {nnn|YES }
DENsity= {cccc|NO }
LENgth= {cc|NO }
OWner= {cc|NO }
SCRatch= {YES|NO }
SERvice= {IN|OUT }
Required to unchain the files in a multifile dataset.
ALTer 'data set name' UNCHAIN
BACKUP Statement Required to create a tape backup of the Catalog.
BACKUP RECOVER
DEFINE Statement Required to define a dataset to the Catalog.
DEFine 'data set name'

ALLoc=(volser,unit,q1,q2,q3,SYSnnn)
BLKSZ= {nnnnn|OPTimize|'OPT,nnnnn' }
CATOPEN= {YES|NO }
CIMSG=('text,r')
CLOSE= {NORWD|RWD|UNL }
COMment='text'
COMSG=('text,r')
DEFvlt=c
DENsity= {cccc|NO }
DISKOPT=( [A] [,B] [,D] [,E] [,F] [,I]
[,K] [,L] [,M] [,N] [,O] [,P]
[,S] [,T] [,W] [,X] [,NA] )
DYNAMFI= {NO|YES }
EXPdate= {date|RETAIN|PERM }
FILETYPE= {SD|IS|DA }
[AUDIT ]
[,NOCNTRL ]
[,NOTM ]
FIopt=( [,NOTRUNC ] )
[,RELEASE|NORELSE]
[,SB|DB ]

[,SL|UL ]
[,VERIFY ]
GDGLONG= {YES|NO }
INDex=(volser,unit,q1,q2,SYSnnn)
LRECL=nnnnn
MF=AUTO
MINDEX=(volser,unit,q1,q2,SYSnnn)
MODEL='data set name'
NGEN=nnn
NOACC=nnnn
OIMSG=('text,r')
OOMSG=('text,r')
OPEN= {NORWD|RWD }
OVRfl=(volser,unit,q1,q2,SYSnnn)
OWner={cc|NO}
PASSWORD='password'
PED=date
PEDCYC=nnn
PrevFile='data set name'
PRIme=(sequence,volser,unit,q1,q2,SYSnnn)
RECFM= {F|FB|V|VB|U }
RETain=nnnn
SYsid=cc
SYSNO={nnn|NO}
TAPE|DISK|FI
[AUTOSCR ]
[,DROP ]
[,HOLD ]
TAPEopt=( [,MODIFY ] )
[,NOLABEL]
[,RELEASE]
[,ROTATE ]
USerid=cc
VLTloc=(A,B,C,...,Z)
VOLID=cc
WORK= {YES|NO }
Required to define the characteristics of the sort key name record.
DEFine SKNAME='skname'
FIELDS=(nnnn,nnnn,format, {A|D }...)
FORMAT= {CH|BI|ZD|PD|FI|FL|CSL
|CTO|CST|CLO|AQ}
LRECL=nnnnn
RECFM= {F|V }
8–8 User Guide

DELETE Statement Required to delete one or all versions of a dataset from the Catalog.
DELete 'data set name'

ALL|GDSid=nn|VERsion=nnn|VOLser=xxxxxx
PASSword='password'
PERmvlt= {YES|NO }
Required to delete a sort key name from the Catalog.
DELete SKNAME='skname'
Required to delete a volume from the Catalog.
DELete VOLser=xxxxxx
EXTERNAL= {YES|NO }
DEQUEUE Statement Statement has no operands. Required to dequeue the Catalog if it was left
enqueued by an abended job.
DEQueue
END Statement Statement has no operands. Required statement; must be the last statement.
END
INITIAL Statement Required to initialize the Catalog.
INITIAL DATAsets=nnnnnn
CISIZE=nnnn
id='text'
PASSword='password'
SHARE= {YES|NO|VSELOCK }
SORTkeys=nnnnnn
VOLumes=nnnnnn
Required to initialize and catalog scratch tapes.
INT|INTR unitnumber
CLean=nnn
CUU=cuu1,…
DENsity=cccc
FIRSTVOL=aaannn
LASTVOL=aaannn
LENgth= {XS|S|MS|M|ML|L }
NEW
OWner={cc|NO}
VOLser=(xxxxxx)

LISTCAT Statement Required to list only selected portions of the Catalog.
LISTcat {'data set name'}

{TAPE['data set name']}
{DISK['data set name']}
{ALL }
LISTcat SKR=['skname'|ALL]
LISTcat VCR|CCR
LISTcat VOL=[volser|ALL]
MACC Statement Required in order to dequeue or to format the CA TLMS and CA Dynam
XSYSTEM M/ACC files.
MACC DEQUEUE [DDNAME=ddname]

INITIAL [DDNAME=ddname]
OWN Statement Required to establish the Catalog ownership code.
OWN id='ownership code'
RENAME Statement Required to rename a dataset, or its versions, in the Catalog.
RENAME OLDNAME='old data set name'

NEWNAME='new data set name'
ALL
MF=RESET
NEWVERS=nnn
OLDVERS=nnn
VOLser=(xxxxxx)
RESTORE Statement Required to restore the Catalog from a backup tape. Can be issued without
operands.
RESTORE
RESTORE REORG [DATASETS=nnnnnn ]
[ID='text' ]
[MERGE ]
[PASSword='password' ]
[SHARE= {YES|NO|VSELOCK }]
[SORTKEYS=nnnnnn ]
[VOLUMES=nnnnnn ]
SCRATCH Statement Required to scratch active tape versions in the Catalog.
SCRatch NODEQ
NOLIST
VAULT= {YES|NO }
8–10 User Guide

DYNCAT Commands
SCRPOOL Statement Required to define a pool of scratch tapes or to modify the characteristics of a
scratch tape.
SCRPOOL VOLser=(xxxxxx,xxxxxx,...,xxxxxx)
CLean= {nnn|YES }
DENsity= {cccc|NO }
FIRSTVOL=nnnnnn
LASTVOL=nnnnnn
OWner=cc
STATUS Statement Statement has no operands. Required to display Catalog utilization statistics.
STATUS
VAULT Statement Required to define a remote-site tape vault location.
VAULT VLTloc=c
DESC='description'
SLOTS=(x1,y1)|DELETE=(x1,y1)
VTOC Statement Required to format or delete a VTOC index Catalog.
VTOC INITIAL|DELETE
VOLser=xxxxxx
DYNCAT Commands
ACTION Command
Use the ACTION command to describe the processing options that are to be in
effect during this run of DYNCAT. More than one ACTION statement may
appear in the input stream. Only the option(s) specified will be modified. The
rest will remain unchanged. This command does not update the Catalog.
The default processing options are: NOCANCEL, ERR, and NOLOG.
Format
The format of the command is shown below
ACTION [ CANCEL|NOCANCEL ]
[ ERR|NOERR ]
[ LOG|NOLOG ]

DYNCAT Commands
CANCEL|NOCANCEL Optional parameter. Indicates whether the job will be canceled if an error is
encountered in the input stream.
ERR|NOERR Optional parameter. Requests or suppresses the display of message

CADC801E on the console if an error is encountered in the input stream.
CADC801E will be written only once per execution.
LOG|NOLOG Optional parameter. Specifies whether each control statement will be logged
on the console as it is processed.
The following example sets the LOG and CANCEL options for the first part of
the run, then changes to NOCANCEL for the remainder of the run. Note that
the ERR option was not affected by either ACTION statement. Also the LOG
option set by the first ACTION statement was not affected by the second
ACTION statement.
// JOB CHANGE OPTIONS

ACTION LOG CANCEL
.
.
.
ACTION NOCANCEL
.
.
.
/*
/&
ADD Command
Use the ADD command to place tape files under control of CA Dynam/T after
they have been created. You can use the ADD command to add versions to
datasets or volumes to versions that are already in the Catalog file or to define
externally owned tape volumes. You can also use this command to add VTAPE
versions to the Catalog file.
The format of the command is shown below.
To add versions or volumes:
ADD 'data set name' VOLser=(xxxxxx,...)

[ APPEND= {YES|NO } ]
[ CREate=date ]
[ DISK ]
[ EXPdate= {date|RETAIN|PERM } ]
[ FILE=nn ]
[ GDSid=nn ]
[ JOBname='jobname' ]
8–12 User Guide

DYNCAT Commands
[ PED=date ]
[ PERM= {YES|NO } ]
[ VERsion=nnn ]
[ VLTloc=c ]
[ VTAPLOC=’location’ ]
[ VTAPFILE=’filename_first’ ]
[ VTAPFILC=’filename_last’ ]
To define externally owned tape volumes:
ADD 'data set name' VOLser=(xxxxxx,...) EXTOwner=c
'data set name' Required positional parameter. Specifies the dataset to which volumes are to
be added. Valid entries are:
1 to 44 characters enclosed in apostrophes.
VOLser= Required operand. Specifies the volume serial number(s) to be added to this
dataset. Valid entries are:
1 to 6 characters enclosed in parentheses. If multiple volume serial numbers

are coded, they must be separated by commas. A maximum of fifty may be
added on one ADD statement. If more are needed, use multiple ADDs with
APPEND=YES.
APPEND= Optional parameter. Indicates whether the volume(s) will be added to an

existing version. A new version is not defined.
YES The volume(s) specified will be appended to the existing

version indicated.
NO The volume(s) specified will be defined for the new

version being added.
NO is the default.
If using APPEND=YES, you may only use the following optional parameters:
DISK, VERSION.
CREate= Optional parameter. Specifies the date on which this file was created. Valid
entry is:
date Acceptable date forms are:
mm/dd/yy
mm/dd/yyyy
dd/mm/yy

DYNCAT Commands
dd/mm/yyyy
yyddd
yyyyddd
For European date format (dd/mm/yy) be sure to update the DYNAM/COMMON

option record with DATE(DDMM).
DISK Optional parameter. Specifies the version added is to be a disk version. If you
are appending volumes (APPEND=YES) to an existing disk version, you must
specify DISK.
EXPdate= Optional parameter. Specifies the date on which this version is to expire. Valid
entries are:
mm/dd/yy
mm/dd/yyyy
dd/mm/yy
dd/mm/yyyy
yyddd
yyyyddd

RETAIN To set the expiration date to 2099365.
PERM To set the expiration date to 2099366.
EXTOwner= Optional parameter. Indicates the owner ID of volumes. Also indicates that
volume(s) being added is externally owned. No other optional parameters may
be used with EXTOwner. The dsn specified will be considered the "last dsn on
volume." A dataset record will not be created for the dataset. Valid entry is:
a 1-character CPUID as defined in DTNODE option record.
Specify this parameter when you want to catalog tape volumes "owned" by
another system. CA Dynam/T will consider these volumes uncontrolled.
Information that an external volume is being defined is not passed to the
external system. It is the responsibility of the owning system to maintain its
own volumes. However, information about CA Dynam/VSE-owned volumes is
passed to the other system.
8–14 User Guide

DYNCAT Commands
FILE=nn Optional parameter. Specifies the file sequence from the beginning of the
current tape. FILE=nn must be specified for unchained, multifile datasets. If
FILE=nn is specified for a predefined multifile dataset, the file sequence
number must be from the beginning of the multifile set, not from the
beginning of the current tape. FILE=nn is not required when ADDing
predefined multifile dataset versions.
GDSid=nnnnn Optional parameter. Specifies the generation data set ID to be added. Valid
entry is:
a 1- to 5-digit numeric generation ID, 1-65535.
If the file is a GDS dataset, you must specify GDSID if adding a new DISK
version.
JOBname= Optional parameter. Specifies the name of the job that created this tape. Valid
entry is:
a 1- to 8-character job name enclosed in apostrophes.
PED= Optional parameter. Specifies the period-ending or as-of-date for this version
of the dataset. Valid entry is:
date - Acceptable date forms are mm/dd/yy or dd/mm/yy
If the variable as-of-date facility is to be used, code two asterisks for any or all
of the date fields. DYNCAT will replace the asterisks with the corresponding
fields from the date in the partition COMREG.
For example: If PED=**/31/** was coded on the ADD statement, the date
placed in the Catalog would be 05/31/07 if this job was run during May of
2007. If the job was run during June of 2006, the date placed in the Catalog
would be 06/31/06.
Note that the dates placed in this field are not validated.
PERM= Optional parameter. Indicates whether this version of the dataset is to remain
in the vault specified by the VLTloc parameter.
YES This version is to be permanently retained in the vault

specified by VLTloc.
NO This version is to be rotated to the vaults specified when

the dataset was defined in the Catalog.
VERsion= Optional parameter. Specifies the version to be added. Valid entry is:
a 1- to 3-digit number in range 1-999.
If omitted, version 1 is assumed.

DYNCAT Commands
VLTloc= Optional parameter. Specifies the vault location where this version of the
dataset resides. Valid entry is:
1 alphabetic character
If this parameter is omitted, the vault location defaults to 'A' or to the value
set when the dataset was defined.
VTAPLOC= Optional parameter. Specifies the VTAPE location for the volume being added.
VTAPLOC and VTAPFILE must be specified together. Only one volume may be
specified on the ADD command if the VTAPLOC parameter is specified. Valid
entry is:
VTAPFILE= Optional parameter. Specifies up to the first 200 characters of the VTAPE
file name of the volume being added. VTAPLOC and VTAPFILE must be
specified together. Only one volume may be specified on the ADD command if
the VTAPFILE parameter is specified. Valid entry is:
VTAPFILC= Optional parameter. Specifies the remaining portion of the VTAPE file name if
the name is greater than 200 characters. VTAPFILE must be specified in order
to use this parameter. Valid entry is:
Example
An example is shown below.
// JOB ADD VERSIONS TO CA Dynam DATA SETS

ADD 'PAYROLL BACKUP' VOLSER=(386) VER=3 X
ADD 'PATRANS' VOLSER=(7337,844) EXPDATE=06/13/09 Y
ADD 'SALES INPUT' VOLSER=(4667) PED=**/31/** Z
ADD 'SALES INPUT' VOLSER=(4668) APPEND=YES [
ADD 'CA1.FILE' VOLSER=(7218) EXTOWNER=B \
/*
/&
1. This adds volume 386 as version 3 of PAYROLL BACKUP.
2. This adds the two volumes 7337 and 844 as version 1 of PATRANS with an
expiration date of 6/13/09.
3. This adds volume 4667 as version 1 of SALES INPUT with the variable as-
of-date.
8–16 User Guide

DYNCAT Commands
4. This appends volume 4668 to version 1 of SALES INPUT.
5. This defines tape volume 7218 as externally owned by B.
ALTER Command
Use the ALTER command to modify the characteristics of entities defined in the
Catalog. There are three different types of information you can change,
depending on the positional operand you supply.
To Modify Command Required Operand
characteristics of tape and disk files ALTER 'data set name'
characteristics of sort key entries ALTER SKNAME='skname'
the status of tape volumes ALTER volser
file sequence in a multifile dataset ALTER ‘data set name’ UNCHAIN
Modifying Tape and Disk Characteristics
To modify the characteristics of tape and disk files, use the following
information. If you include a parameter (VERSION, VOLSER, or GDSID) that
uniquely identifies an existing version, only that version of the specified
dataset will be altered. Otherwise, the default characteristics of the dataset
will be altered. (With VERSION, VOLSER, and GDSID, only the following
operands may be included: BLKSZ, CREATE, EXPDATE, JOBNAME,
LOCK/UNLOCK, LRECL, OWNER, PED, PERM, RECFM, SYSID, USERID,
VLTLOC.)
ALTER 'data set name'
[ ALLoc=(volser,unit,q1,q2,q3,SYSnnn) ]
[ BLKSZ= {nnnnn|OPTimize|'OPT,nnnnn' } ]
[ CATOPEN= {YES|NO } ]
[ CIMSG= {'text,r'|NO } ]
[ CLOSE= {NORWD|RWD|UNL|NO } ]
[ COMment= {'text'|NO } ]
[ COMSG= {'text,r'|NO } ]
[ CREate=date ]
[ DEFvlt=c ]
[ DENsity= {cccc|NO } ]
[ {[A] [,B] [,D] [,E] [,F] [,I] } ]
[ DISKOPT=( {[,K] [,L] [,M] [,N] [,O] [,P] } ) ]
[ {[,S] [,T] [,W] [,X] [,NA] } ]

DYNCAT Commands
[ DYNAMFI= {YES|NO } ]
[ EXPdate= {date|RETAIN|PERM|RT+nnn|CD+nnn|NO } ]
[ FILETYPE= {SD|IS|DA } ]
[ [AUDIT ] ]
[ [,NOCNTRL ] ]
[ [,NOTM ] ]
[ FIopt=( [,NOTRUNC ] )|NO ]
[ [,RELEASE|NORELSE] ]
[ [,SB|DB ] ]
[ [,SL|UL ] ]
[ [,VERIFY ] ]
[ GDGLONG= {YES|NO } ]
[ INDex=(volser,unit,q1,q2,SYSnnn) ]
[ JOBname='jobname' ]
[ LENgth= {XS|S|MS|M|ML|L|NO } ]
[ LOCK|UNLOCK ]
[ LRECL=nnnnn ]
[ MF= {NEW|nnn|NO } ]
[ MINDEX=(volser,unit,q1,q2,SYSnnn) ]
[ NEWPSWD='password'|" ]
[ NEXTGEN=nn ]
[ NGEN=nnn ]
[ NOACC=nnnn ]
[ OIMSG= {'text,r'|NO } ]
[ OOMSG= {'text,r'|NO } ]
[ OPEN= {NORWD|RWD|NO } ]
[ OVRfl=(volser,unit,q1,q2,SYSnnn) ]
[ OWner= {cc|NO } ]
[ PASSword='password' ]
[ PED=date ]
[ PEDCYC=nnn ]
[ PERM= {YES|NO } ]
[ PRIme=(sequence,volser,unit,q1,q2,SYSnnn) ]
[ RECFM= {F|FB|V|VB|U|NO } ]
[ RETain= {nnnn|NO } ]
[ SYsid= {cc|NO } ]
[ SYSNO={nnn|NO} ]
[ TAPE|DISK|FI ]
[ [AUTOSCR|NOAUTOSC] ]
[ [,DROP|NODROP ] ]
[ [,HOLD|NOHOLD ] ]
[ TAPEopt=( [,LABEL|NOLABEL ] )|NO ]
[ [,MODIFY|NOMODIFY] ]
[ [,ROTATE|NOROTATE] ]
[ USerid= {cc|NO } ]
[ VERsion=nnn|VOLser=(xxxxxx)|GDSid=nn ]
8–18 User Guide

DYNCAT Commands
[ VIRTape={NO|VTAPE|FTAPE} ]
[ VLTloc=(A,B,C,...,Z) [VLTSEQ=nnn] ]
[ VOLID=cc ]
[ WORK= {YES|NO } ]
'data set name' Required positional parameter. Specifies the data set name to be altered. Valid
entry is: a 1- to 44-character data set name enclosed in apostrophes.
ALLoc= ALLoc=(volser,unit,q1,q2,q3,SYSnnn).
Optional parameter. Defines the new allocation characteristics of a disk

dataset to be allocated by the CA Dynam/D component. Specify valid entries
within parentheses:
volser volume serial number upon which the extent is to reside.

May be either a real, virtual (pool), or generic volser.
Default is '******', which indicates that any VOLSER may
be used for file allocation.
unit unit of allocation for the extent: TRK (tracks), CYL

(cylinders), BLK (FBA blocks), or RCD (number of
records). TRK is the default.
q1 number of units to allocate for primary allocation, 0-

999999. This is a required operand.
q2 number of units to allocate for each secondary allocation,

0-999999. Default is 0.
q3 number of secondary allocations to perform, 0-255.

Default is 0.
To establish catalog-controlled secondary allocation, q2 and q3 must be

numbers other than zero.
To establish automatic secondary allocation, q2 and q3 must both be zero,

and ASAMAX and ASAAMT parameters of the DYNAM/D option record must be
other than zero. To prohibit automatic secondary allocation, specify NA
either as a file ID option code or in the DISKOPT= parameter of DYNCAT
DEFINE command.
If ASAMAX, ASAAMT, q2 and q3 are all zero, no secondary allocation is

provided.
SYSnnn logical unit to use for the extent(s) generated if none was
specified in the DTF. None is included if not specified.

DYNCAT Commands
Enter complete ALLOC information. When ALTER is processed, all the

allocation characteristics are processed. Do not use ALLOC for ISAM files.
Instead, use the PRIME, INDEX, MINDEX, and OVRFL operands. The
parameters provided within the parentheses for ALLOC, PRIME, MINDEX,
INDEX, and OVRFL are positional; substitute a comma for an omitted
parameter unless the comma immediately precedes the closing parenthesis.
BLKSZ= Optional parameter. Specifies the block size for the file to the CA Dynam/FI
component. The DTF for the file will be modified to the value specified. Valid
entries are:
Maximum blocksize for tape: 65535
Maximum blocksize for disk: 65535, or
OPTimize, or
'OPT,nnnnn' (include single quotes)
When optimal blocking is specified, CA Dynam/FI will recalculate the block size
for the physical device on which the file is being created. For FBA devices, the
CISIZE is recalculated.
The Catalog is updated when the file is closed for output to record the actual
block size used for the file. When the file is opened for input, CA Dynam/FI
must use this value to build the input DTF correctly.
CATOPEN= Optional parameter. Specifies whether newly opened output versions of this
dataset are to be marked as valid versions so they may be cataloged at OPEN.
This will ensure that the version being created will always be considered a
good version even if it is never closed.
YES This dataset may be cataloged at OPEN.
NO This dataset should be cataloged at CLOSE.
CIMSG= Optional parameter. It changes user-specified messages for the dataset. These
messages will be issued Open Input (OIMSG=), Open Output (OOMSG=),
Close Input (CIMSG=), and/or Close Output (COMSG=) for the dataset, as
specified, and will be directed to the operator console and/or SYSLST as
indicated by the routing code. Routing codes are as follows:
C - Console (default)
P - Printer
B - Both
8–20 User Guide

DYNCAT Commands
Valid input is:
1 to 70 alphanumeric characters of message text, followed by a comma,

followed by single-character routing code, following optionally by a , A if
message should ring the console. All are enclosed by apostrophes. NO
removes the user message.
Example
OIMSG='MY MESSAGE,C'
OOMSG='MY MESSAGE FOR OUTPUT, C,A'
CLOSE= Optional parameter. Changes the DTF rewind option set by CA Dynam/T or
CA Dynam/FI for CLOSE.
NORWD not to rewind the tape
RWD to force rewind
UNL to force rewind and unload
NO removes CLOSE options.
COMment= Optional parameter. Changes the comment field associated with this dataset.
Valid entries are:
a comment of 1-100 alphanumeric characters enclosed in apostrophes.
NO removes the comment.
Note that on some reports the comment from this field will be truncated to
fewer than 100 characters.
COMSG= See CIMSG operand description.
CREate= Optional parameter that changes the version creation date in the Catalog.
Valid entry is:
mm/dd/yy
mm/dd/yyyy
dd/mm/yy
dd/mm/yyyy
yyddd
yyyyddd

DYNCAT Commands

VERSION or VOLSER or GDSID must be specified for this function.
DEFvlt= Optional parameter. Changes default vault location for any version of dataset
not specified by the VLTLOC parameter. Valid entry is:
one alphabetic character in the range A-Z.
If omitted, vault A, the main tape vault, is assumed.
DENsity= Optional parameter. Changes the default recording density for this dataset.
Valid entries are:
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI
00 for tape cartridge (buffered write mode)
00E for tape cartridge (3490E buffered write mode)
00M for tape cartridge (3590 buffered write mode)
00ME for tape cartridge (3590E buffered write mode)
00MH for tape cartridge (3590H buffered write mode)
00W for tape cartridge (3592 buffered write mode)
00WE for tape cartridge (3592E buffered write mode)
03WE for tape cartridge (3592E encrypted buffered write mode)
08 for tape cartridge (data compaction with buffered write)
08E for tape cartridge (3490E data compaction with buffered

write)
08M for tape cartridge (3590 data compaction with buffered

write)
08ME for tape cartridge (3590E data compaction with buffered

write)
8–22 User Guide

DYNCAT Commands
08MH for tape cartridge (3590H data compaction with buffered

write)
08W for tape cartridge (3592 data compaction with buffered

write)
08WE for tape cartridge (3592E data compaction with buffered

write)
0BWE for tape cartridge (3592E encrypted data compaction with

buffered write)
20 for tape cartridge (unbuffered write mode)
20E for tape cartridge (3490E unbuffered write mode)
20M for tape cartridge (3590 unbuffered write mode)
20ME for tape cartridge (3590E unbuffered write mode)
20MH for tape cartridge (3590H unbuffered write mode)
20W for tape cartridge (3592 unbuffered write mode)
20WE for tape cartridge (3592E unbuffered write mode)
23WE for tape cartridge (3592E encrypted unbuffered write

mode)
28 for tape cartridge (data compaction with unbuffered

write)
28E for tape cartridge (3490E data compaction with

unbuffered write)
28M for tape cartridge (3590 data compaction with unbuffered

write)
28ME for tape cartridge (3590E data compaction with

unbuffered write)
28MH for tape cartridge (3590H data compaction with

unbuffered write)
28W for tape cartridge (3592 data compaction with unbuffered

write)
28WE for tape cartridge (3592E data compaction with

unbuffered write)

DYNCAT Commands

unbuffered write)
NO removes density value
DISKOPT= Optional parameter. May be used to modify one or more of the processing
options specified for the disk dataset when it is processed under the control of
the CA Dynam/D component. For more information about the effect of each of
the various options, see Defining File ID Option Codes in the chapter "Disk File
Management."
Valid entries are one or more of the following options:
A, B, D, E, F, I, K, L, M, N, O,
P, S, T, W, X, NA NO
DISKOPT=NO removes all options
Enclose options in parentheses, separated with commas or blanks.
DYNAMFI= Optional parameter. Specifies whether CA Dynam/FI is to use and update

information from the Catalog. If you want CA Dynam/FI to do so, you must
specify YES. Otherwise, it will not access the Catalog regardless of other
parameters defined for this dataset.
YES ensures Catalog access for this dataset.
NO not to allow CA Dynam/FI to access the Catalog

information for this dataset. This is the default.
EXPdate= Optional parameter. Changes the expiration date for this dataset. Valid entries
are:
mm/dd/yy
mm/dd/yyyy
dd/mm/yy
8–24 User Guide

DYNCAT Commands
dd/mm/yyyy
yyddd
yyyyddd

RT+nnnn A 1- to 4-digit number to be added to the expiration date,

producing a new expiration date. Valid when modifying a
version only.
CD+nnnn A 1- to 4-digit number to be added to the creation date,

producing a new expiration date. Valid when modifying a
version only.
NO To clear expiration date.
FILETYPE= Optional parameter. Specifies the type of label record to be built by CA

Dynam/D when the disk file is opened. Valid entries are:
IS for ISAM
DA for direct access
SD for sequential disk (the default)
FIopt= Optional parameter. Specifies processing options to CA Dynam/FI. Enclose the

options in parentheses, separated with commas or blanks.
SB Requests single buffering. Applies to tape or disk files.
DB Requests double buffering. Applies to tape or disk files.
RELEASE Releases the logical assignment when the disk or tape file
is closed.
NORELSE Requests not to release the logical assignment when the

disk or tape file is closed.
VERIFY Verifies output by reading the disk record just written.

Enables the verify option in the user's DTF.
NOTM Modifies the DTF so as not to write a tape mark at close.

DYNCAT Commands
SL Modifies the DTF to provide for standard label processing

for tapes.
UL Modifies the DTF to provide unlabeled processing for

tapes.
NOTRUNC Ignores TRUNC requests for this file. (For more

information about the TRUNC macro, see the IBM VSE/AF
Application Programming Macro Reference.)
NOCNTRL Ignores CNTRL requests for this file. (For more

information about the CNTRL macro, see the IBM VSE/AF
Application Programming Macro Reference .)
AUDIT Performs CA Dynam/FI AUDIT recording for this file, even

though no other characteristics of the file have been
modified. This function may be used, either from the
Catalog or as a CA Dynam/FI DLBL/TLBL option, to cause
audit information to be recorded about selective files.
NO Removes all options.
GDGLONG= Optional parameter. Specifies whether a suffix of .G#nnnnnn will be added to

a generation dataset. nnnnnn can be any number from 000001 to 065535. Up
to 999 versions can be active at one time. Specifying GDGLONG=NO causes
the previous format, G#nn, be used.
INDex= INDex=(volser,unit,q1,q2,SYSnnn)
Optional parameter. Defines the allocation characteristics of the index extent

to be generated for the (ISAM) disk dataset if it is to be allocated by the CA
Dynam/D component. Valid entries are the same as for the PRIME data
allocation (except for the sequence option).
JOBname= Optional parameter. Changes the creation jobname in the Catalog. Valid entry
is:
a 1- to 8-character jobname enclosed in apostrophes.
VERSION, VOLSER, or GDSID must be specified for this function.
KEKL1= Optional parameter. Defines the KEKL1 specification for the dataset. Valid
input is a 1 to 64 character KEKL specification followed by a comma, followed
by a single–character Key Encryption Method. All is enclosed by apostrophes.
Valid Key Encryption Methods are as follows:
L Encode the Key label as the label is specified
H Encode the Key label as a hash of the public key
8–26 User Guide

DYNCAT Commands
Note: You must specify KEKL1 if you want to specify KEKL2. If you don’t
specify KEKL2, then the value of KEKL1 is used for KEKL2.
Note: You can specify KEKL2 only if you have specified KEKL1. If you don’t
LENgth= Optional parameter. Changes the tape length specification for this dataset.
Valid entries are:
XS extra short
S short
MS medium short
M medium
ML medium long
L long
NO removes the length specification.
LOCK|UNLOCK Optional parameter that prevents or allows access to a specific version of a

dataset or to the entire dataset.
LOCK If the LOCK function is used for a specific version, only

that version will be locked for input. New versions may
still be created.
If the LOCK function is used to LOCK the entire dataset, no new versions will
be cataloged, but existing versions will be available to be used as input. If the
entire dataset has been locked and the dataset is used for output, the output
will not be cataloged and the output tape is changed from SCRATCH to LOCK
status. The next scratch function will return this tape to SCRATCH status.
No batch maintenance may be performed on a dataset that is LOCKed, except

to UNLOCK it.
UNLOCK Reverses the effect of the LOCK parameter.

DYNCAT Commands
To unlock a specific version for input, specify the VERSION or VOLSER

parameters that were supplied when the dataset was locked.
To unlock the entire dataset for output, specify only the data set name.
LRECL= Optional parameter which specifies the logical record length for the file to the
CA Dynam/FI component. The DTF for the file will be modified to the value
specified. For more information about the effect of this parameter, see the
chapter "Controlling File Independence." Valid entries are:
1-5 numeric digits in the range 0-65535.
MF= Optional parameter. Tells CA Dynam/T that the next automatic multifile (AMF)
dataset is to be on a new volume, or is to be reset to a specific number. Valid
entries are:
NEW indicates a new volume is required for this AMF dataset.

The next AMF dataset created will be file 1 on a new
volume, using the next incremental AMF number in the
data set name.
nnn indicates the 3-digit number to be used for replacement

in the '***' field in the AMF data set name when the
dataset is created next. That is, the next AMF dataset
created for this file is to use the number specified in the
data set name. This number must be less than the
current file sequence number.
NO indicates that automatic multifile support is to be dropped

for this dataset.
For more information, see Using Automatic Multifile Datasets in the chapter
"Maintaining Tape Files."
MINDEX= MINDEX=(volser,unit,q1,q2,SYSnnn)
Optional parameter. Defines the allocation characteristics of the master index

extent to be generated for the (ISAM) disk dataset if it is to be allocated by
the CA Dynam/D component. Valid entries are the same as for the PRIME data
allocation (except for the sequence option).
NEWPSWD= Optional parameter. Specifies the new password to be used when accessing
this dataset. Valid entries are:
1-8 alphabetic characters enclosed in apostrophes.
To remove password protection, code two consecutive apostrophes.
If this dataset is already password protected, then the PASSWORD operand

must be supplied in order to use this function.
8–28 User Guide

DYNCAT Commands
NEXTGEN= Optional parameter. Modifies the next disk generation ID number that is to be
used for CA Dynam/D-controlled disk generation datasets. Valid entry is:
a 1- to 2-digit number in the range 1-99.
CA Dynam/D creates a disk GDG by appending G#nn as the last 4 characters

of the 44-byte file ID. Normally, each successive generation receives the next
sequential number, from 1 through 99.
If it is necessary to reset this number to a lower value, the VTOC entries for
the already existing files above this number should be removed from the
DASD devices upon which they reside (with DYNUTIL DELETE). In addition,
remove their associated version records from the Catalog (with DYNCAT
DELETE) before the generation ID is updated with NEXTGEN.
NGEN= Optional parameter. Changes the number of generations to be saved for this
dataset. Valid entries are a 1- to 3-digit number in range 0-999, for TAPE
datasets or DISK datasets.
See the DEFINE command for further discussion of the implications of NGEN
for TAPE and DISK datasets.
NOACC= Optional parameter. Specifies the number of days this dataset version is to be
retained after last access, before it becomes eligible for scratch.
1- to 4-digit number in the range 0-9999.
OIMSG= See CIMSG operand description.
OOMSG= See CIMSG operand description.
OPEN= Optional parameter that changes the DTF rewind option set by CA Dynam/T or
CA Dynam/FI for OPEN.
NORWD not to rewind the tape.
RWD forces the rewind.
NO removes the OPEN options.
OVRfl= OVRfl=(volser,unit,q1,q2,SYSnnn)
Optional parameter which defines the allocation characteristics of the

independent overflow to be generated for the (ISAM) disk dataset if it is to be
allocated by the CA Dynam/D component. Valid entries are the same as for the
PRIME data allocation (except for the sequence option).

DYNCAT Commands
OWner= Optional parameter. Changes the ownership code for this dataset. Valid entries
are:
a 1- to 2-character code
NO removes owner value.
PASSword= Required if a password has been defined for this dataset. Specifies the
password required to perform maintenance to this dataset. Valid entries are:
1-8 alphabetic characters enclosed in apostrophes.
PED= Optional parameter. Changes the as-of-date for this dataset or version. Valid
entries are:
date acceptable date forms are mm/dd/yy, dd/mm/yy,

mm/dd/yyyy or dd/mm/yyyy
NO to remove the as-of-date.
Two asterisks may be substituted for any or all of the data fields. When CA
Dynam/T encounters the asterisks, it will replace them with that field from the
job date (temporary COMREG date for VSE user). For example: **/31/**
would be changed to 05/31/00 for each version of the dataset created in May
of 2000.
No validation is done on the eight bytes specified for period ending date. Dates
are normally used, but this field may also be used to store eight bytes of user
information about the version, if desired. If a period ending date field contains
nonblank characters, or a date different from the creation date, the contents
of the field will be printed on applicable reports.
When used for a dataset with PEDCYC=0, the PED field becomes simply a user
comment field associated with each version.
PEDCYC= Optional parameter. Changes the number of versions of this dataset being
retained by period ending date. Valid entry is:
nnn an integer value in the range 0-999.
0 default, indicates that PED field is a comment.
PERM= Optional parameter. Indicates whether the dataset's current vault location is to
be permanent; that is, to be no longer rotated. Valid entries are:
YES The current vault location is to be permanent.
NO The current vault location is not to be permanent.
Either VERSION, VOLSER, or GDSID must be specified for this function.
8–30 User Guide

DYNCAT Commands
PRIme= PRIme=(sequence,volser,unit,q1,q2,SYSnnn)
Optional parameter. Modifies the characteristics of a particular prime data

extent to be generated for a disk dataset if it is to be allocated by the CA
Dynam/D component. Valid entries are specified within parentheses and
require:
sequence Extent sequence number to be modified by ALTER. Must

be numeric 0-255. This is a required operand.
volser Volume serial number upon which the extent resides. May
be either a real, virtual (pool), or generic volser.
unit Unit of allocation for the extent, one of TRK (tracks), CYL
(cylinders), BLK (FBA blocks), RCD (number of records),
or ABS (absolute quantity, indicating fixed extent file).
Applies to sequential files only.
For nonsequential files (DA, ISAM), the unit will always

be treated as tracks.
q1 Number of units to allocate for primary allocation, 0-

999999. If unit was specified as ABS, specifies the
beginning location of extent.
q2 If unit was specified as ABS, specifies the number of

tracks or blocks for the extent. Not valid unless ABS was
specified.
SYSnnn Logical unit to use for the extent(s) generated if none

was specified in the DTF.
RECFM= Optional parameter. Specifies the record format for the file to the CA
Dynam/FI component. The DTF for the file will be modified to the value
specified.
F Fixed length
FB Fixed Blocked
V Variable length
VB Variable Blocked
U Undefined records
NO Removes the RECFM specification.

DYNCAT Commands
RETain= Optional parameter. Changes the number of days retention used to calculate
the expiration date for this dataset. Valid entries are:
NO removes retention value.
ROBOT= Optional parameter. Specifies whether DYNAM/CMS will search robotic-type

tape devices when a DYNOPEN command is issued by VSE.
YES Allows robotic-type devices.
NO Disallows robotic-type devices.
SYsid= Optional parameter. Changes the system ID field for reporting purposes. Valid
entries are:
a 2-character ID to be used for reporting.
NO removes SYSID value.
SYSNO= Optional Parameter. Specifies whether a SYS number override is defined for a
dataset in the catalog. Valid entries are:
001 to 255 Specifies a SYS number for the dataset.
000 or NO Deactivates this parameter.
TAPE|DISK|FI Optional parameter. Indicates the type of storage medium used for this
TAPE Restricts the dataset to tape use only, under the control
of CA Dynam/T. It is not eligible for dynamic device
switching.
DISK Restricts the dataset to disk use only, under the control
of CA Dynam/D. It is not eligible for dynamic device
switching.
FI Allows the dataset to be used either for tape or disk, and

is eligible for dynamic device switching. Datasets with
this specification may have both tape and disk
characteristics. For more information, see Operator
Device Switching Facility in the chapter "Controlling File
Independence."
8–32 User Guide

DYNCAT Commands
TAPEopt= Optional parameter. Changes the default processing options performed during
open and close by CA Dynam/T. Enclose options in parentheses, separated
with commas or blanks. Valid options are:
RELEASE or NORELSE
Indicates whether this WORK dataset will be scratched at
CLOSE. This parameter is only valid for datasets specified
as WORK=YES.
HOLD or NOHOLD Determines whether the CA Dynam/T HOLD option (to

hold assignment) will be in effect at CLOSE.
DROP or NODROP Specifies whether the CA Dynam/T DROP option (to erase
TLBL at file CLOSE) will be in effect.
MODIFY or NOMODIFY
Indicates whether CA Dynam/T will modify the DTF
file name at OPEN.
AUTOSCR or NOAUTOSC
Causes CA Dynam/T to analyze (or not to analyze) this
dataset for versions eligible to be scratched at every
close for output. Valid only for single file tape datasets,
the processing of this option is also dependent upon the
setting of the AUTOSCR parameter in the DYNAM/T
option record. If specified, the CADT064I message will
be issued whenever a version is scratched due to
AUTOSCR.
ROTATE or NOROTATE
Indicates whether CA Dynam/T will process tapes within
this dataset in a cyclical fashion, so that the newest
output version will be written over the oldest version of
the dataset, if the number of versions specified by the
NGEN parameter for the dataset is filled. All expiration
and retention criteria are ignored when rotating. That is,
even if EXPDATE=PERM, the oldest version will be
scratched.
When the first file of a multifile set is reused, all the

subsequent files are scratched. Therefore, if a multifile,
multivolume set is being rotated, all the volumes not
reused by the first file, are returned to the scratch pool
and will not be called when creating the subsequent files
of the multifile set.
LABEL or NOLABEL
Causes CA Dynam/T to process tapes within this dataset
as labeled or unlabeled.

DYNCAT Commands
NO Removes all options.
USerid= Optional parameter. Changes the user ID field. Valid entries are:
a 2-character ID to be used for reporting purposes.
NO removes user ID value.
VERsion|VOLser|GDSid
VERsion= Optional parameter. Specifies the generation to be

modified. The VERSION number, VOLSER number, or
GDSID operand must be present when altering a specific
generation. Valid entry is a 1- to 3-digit number in the
range 1-999.
VOLser= Optional parameter. Specifies the first or only volume of

a dataset generation to be modified. The VOLser number,
VERsion number, or GDSid operand must be present
when altering a specific generation. Valid entry is a 1- to
6-character volume serial number.
GDSid= Optional parameter. Specifies the Generation Data Set ID

of the disk dataset to be modified (CA Dynam/D
controlled only). The GDSid, VERsion number, or VOLser
number operand must be present when altering a specific
generation. Valid entry is a 1- to 2-digit numeric
generation ID (1 - 99).
VIRTape= Optional parameter. Specifies whether a dataset should be created as a virtual

file.
NO The file is not created as a virtual file.
VTAPE The file is created using VTAPE.
FTAPE The file is created using FakeTape.
VLTloc= Optional parameter used to change the vault location for each version of the
dataset. Valid entry is a 1- to 999-alphabetic characters enclosed in
parentheses and separated by commas. Each character represents a vault
location. Its relative position in the string represents the generation of the
dataset that is to be in that vault. Specify NO to clear.
For example: (A,A,B,A) specifies that versions 1 and 2 are to be in vault A.

Version 3 is to go to vault B and version 4 is to return to vault A. The first 999
versions of a dataset may have vault location control. All versions after 999
will be kept in vault A. If a version is specified, the version will be moved to
the vault specified.
8–34 User Guide

DYNCAT Commands
VLTSEQ= Optional parameter used to specify the starting version for the VLTLOC
parameter. VLTSEQ must be specified sequentially with no gaps in versions.
Valid entries are 1 through 999.
VOLID= Optional parameter. Defines a volume identifier that allows the tape volume to
receive output from the dataset. The volume identifier must match the first
two characters of the volume serial number.
WORK= Optional parameter. Indicates whether this dataset is to be processed as a

tape work dataset. Valid entries are:
YES This is a work dataset.
NO This is not a work dataset.
Examples
Examples are shown next.
// JOB ALTER THE CA Dynam CATALOG

ALTER 'SALESTRANS' NGEN=3 LENGTH=S CLOSE=UNL X
ALTER 'PAYMAST' VERS=1 LOCK Y
ALTER 'AR SUSPENSE' EXPDATE=RT+14 VOLSER=(486) Z
ALTER 'AP DAILY' WORK=NO PED=**/31/** PEDCYC=3 [
ALTER 'CUSTMAST' PASSWORD='CUSTOMER' NEWPSWD='' \
ALTER 'EOM.TRANS.FILE' ALLOC=(POOL01,TRK,39,19,3) ]
ALTER 'FIXED.FILE' PRIME=(0,SYSRES,ABS,1938,57) ^
ALTER 'VAULT.DSN' VLTLOC=(A,B,C,D,E) _
ALTER 'VAULT.DSN' VLTLOC=(F,G,A,B,C) VLTSEQ=6 `
ALTER 'VAULT.DSN' VLTLOC=(D,E,F,G) VLTSEQ=11 a
/*
/&
1. This sets the number of generations to be retained for SALESTRANS to 3.It

also sets the length code to short and forces the dataset to be rewound
and unloaded at close.
2. This locks Version 1 of PAYMAST so that it cannot be read.
3. This adds 14 days to the expiration date of AR SUSPENSE on volume 486.
4. This changes AP DAILY from a work file to one using automatic as-of-date
control and retaining 3 as-of-date versions.
5. This removes the password from CUSTMAST.
6. This changes the disk allocation specified for 'EOM.TRANS.FILE' to a

primary allocation of 39 tracks, on volser POOL01, and three secondary
allocations of 19 tracks each.

DYNCAT Commands
7. This informs the Catalog that the actual location of 'FIXED.FILE' has
changed and now begins on volser SYSRES at track 1938 for 57 tracks.
8, 9, 10. This sets the vault scheme for the first 14 versions of the dataset
VAULT.DSN.
Modifying Sort Key Records
The sort key records are used in conjunction with CA Dynam/FI. For more
information, see the chapter "Controlling File Independence." When modifying
the characteristics of sort key entries, the following operands apply to the
ALTER command.
ALTER SKNAME='skname' FIELDS=(nnnn,nnnn,format, {A|D }....)
[ FORMAT= {CH|BI|ZD|PD|FI|FL|CSL|CTO|CST|CLO|AQ } ]
[ RECFM= {F|V } ]
SKNAME='skname' Required positional parameter. Specifies the sort key record which is to be
altered. This parameter is mutually exclusive with the 'data set name' and
volser parameters. Valid entry is:
1- to 8-character sort key name enclosed in apostrophes.
FIELDS= FIELDS=(s1,l1,t1,m1,s2,l2,t2,m2,. . .)
Required parameter. Specifies the control field information for the sort key
record defined by the SKNAME parameter. Valid entries:
sn Control field position relative to the start of the record
ln Control field length
tn Control field data type (same as FORMAT operand)
mn A for ascending, or D for descending sequence mode
FORMAT= Optional parameter which specifies the format of the data in the sort key
field(s) defined by the SKNAME= parameter. These are the valid data types
acceptable to CA SRAM:
CH Character
BI Binary
ZD Zoned Decimal
8–36 User Guide

DYNCAT Commands
PD Packed Decimal
FI Fixed Point
FL Floating Point
CSL Numeric, Separate Leading Sign
CTO Numeric, Trailing Overpunch Sign
CST Numeric, Separate Trailing Sign
CLO Numeric, Leading Overpunch Sign
AQ Alternate Collating Sequence
RECFM= Optional parameter. Specifies the record format of the records to be sorted
using the sort key information defined by SKNAME. Valid entry is one of the
following:
F Fixed-length records
V Variable-length records
Modifying Tape Volume Information
When modifying information about tape volumes, use the following format:
ALTER volser
[ CLean= {nnn|YES } ]
[ LENgth= {cc|NO } ]
[ OWner= {cc|NO } ]
[ SCRatch= {YES|NO } ]
[ SERvice= {IN|OUT } ]
[ COMMENT= {'text', no }]
volser Required positional parameter. Identifies the volume serial number of the tape
whose status is to be changed. This parameter is mutually exclusive with the
'data set name' and SKNAME parameters. Valid entry is:
a 1- to 6-character volume serial number.

DYNCAT Commands
CLean= Optional parameter. Specifies the maximum number of tape errors to be

allowed for this volume before CA Dynam/T flags it to be cleaned. This is a
cumulative total that is retained in the Catalog until the tape is reinitialized.
Valid entries are:
YES indicates that the tape has been cleaned, and resets the error counters in
the volume record.
Specify CLEAN=YES if the volume has been cleaned, but not reinitialized.
Comment Optional parameter. Creates or alters a comment field associated with this
volser. Valid entries are:
A comment of 1-100 alphanumeric characters enclosed in apostrophes.
NO removes the comment.
DENsity= Optional parameter. Specifies the recording density for this tape.
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI

write)
8–38 User Guide

DYNCAT Commands

write)

write)

write)

write)

write)

buffered write)

mode)

write)

unbuffered write)

write)

unbuffered write)

unbuffered write)

DYNCAT Commands

write)

unbuffered write)

unbuffered write)
NO removes density specification.
LENgth= Optional parameter. Changes the length specification for this volume.
XS extra short
S short
MS medium short
M medium
ML medium long
L long
OWner= Optional parameter. Modifies the volume's ownership code.
A 1- to 2-character code.
NO removes the owner value.
SCRatch= Optional operand. Used only if the CA TLMS interface is active.
YES Changes the scratch indicator for a CA TLMS active tape

to scratch status.
NO Changes the indicator for a CA TLMS tape from scratch to

active status.
8–40 User Guide

DYNCAT Commands
SERvice= Optional parameter. Used only if the CA TLMS interface is active. Modifies the
status of the volume's service indicator.
IN Changes the service indicator to inservice.
OUT Changes the service indicator to out-of-service.
Note that an out-of-service tape is not allowed for output use. If an out-of-
service tape is read as input, the service indicator is automatically changed to
inservice status.
Modifying File Sequence
To unchain all the datasets in a predefined multifile set, use the following
format:
ALTER 'data set name' UNCHAIN
UNCHAIN All versions of all files in the multifile dataset will have their file sequence
updated to reflect the file sequence from the beginning of the tape the version
starts on.
UNCHAIN must be the only parameter specified on the ALTER command and it
must be specified for the first file in the predefined multifile dataset.
All datasets will no longer be predefined as multifile.
BACKUP Command
Use the BACKUP command to copy the contents of the CA Dynam Catalog to
tape or disk for security purposes. Use this command also to logically verify
the integrity of the Catalog so that, if an error has occurred, steps may be
taken immediately to correct it. You may run BACKUP with or without the
RECOVER operand.
BACKUP [RECOVER]
[NODEQ ]
To create a normal backup file by using the Catalog directory for optimum
performance, specify BACKUP without an operand.
To create a backup file by sequentially reading the Catalog without accessing

the directory, specify BACKUP with the RECOVER operand. This file may later
be used to recover the contents of the Catalog if the directory has been
damaged.

DYNCAT Commands
A File Created By May Be Used for Performing
BACKUP RESTORE (to physically restore)
RESTORE REORG (to logically reorganize and restore)
BACKUP RECOVER RESTORE REORG only, because it does not contain a

reliable index
A tape created using BACKUP and restored using RESTORE may be used by
the audit facility to recover the Catalog. For more information, see the chapter
"Maintaining and Reporting on the Audit Trail."
BACKUP Processing
When a BACKUP is performed, the CA Dynam Catalog is enqueued as soon as

the backup file has been opened, and is not dequeued until the BACKUP is
completed.
If the backup file is a controlled dataset, the most current version will not be a
part of the data dumped to the backup file because the file has not yet been
closed. You need to define the backup dataset with CATOPEN=YES so that the
current version will be backed up (because it will be marked as active at open
time).
Resolving Processing Errors
If errors are encountered during the BACKUP, messages will be issued

describing the nature of the error. Review the printed output from the BACKUP
daily to assure that the Catalog is intact. In the event an error has been noted,
run the BACKUP RECOVER function to assure that no datasets are lost due to
directory errors; then, run the RESTORE REORG function to rebuild the
Catalog, correcting the error. The BACKUP function uses file name 'IJSYSBK'
for the BACKUP file. The logical unit used is SYS006.
Perform a BACKUP at least once each day; immediately prior to the SCRATCH
function. It must be performed when all other partitions are idle or, at least,
not running any jobs that use files controlled by the CA Dynam Catalog.
If you suspect any error or problem with the Catalog, you should BACKUP the
Catalog first, before attempting any other recovery. In most cases, running a
BACKUP, RESTORE REORG, and SCRATCH will correct any errors that may
occur. If it is necessary to run BACKUP RECOVER, the file containing the
original BACKUP file that produced the error should be retained for analysis.
8–42 User Guide

DYNCAT Commands
Considerations for a Multi-CPU Environment
The NODEQ parameter allows the DYNCAT backup to be followed immediately

by a RESTORE/REORG without the catalog being dequeued until the end of the
RESTORE/REORG. This ensures that no updates to the catalog take place. The
CPU running the backup must have all the other partitions idle. To ensure that
the catalog is not automatically dequeued, DYNAM must be disabled for the
duration of the backup and restore/reorg in the partition where the backup is
performed. Since DYNAM is disabled, the backup file cannot be controlled.
Perform backup in a multi-CPU environment without quiescing all other CPUs.
SET DYNAMT=OFF
SET DYNAMD=OFF
SET DYNAMFI=OFF
// ASSGN SYS006,CUU
// TLBL IJSYSBK
// EXEX DYNCAT
BACKUP NODEQ
RESTORE REORG
/*
SET DYNAMT=ON
SET DYNAMD=ON
SET DYNAMFI=ON
Note: To change any extents of the catalog, you must IPL all CPUs.
DYNCAT BACKUP/RESTORE Reports
In order to provide more detailed and meaningful information about the

Catalog's internal status, BACKUP and RESTORE REORG will produce reports of
the number of records of each type in the Catalog whenever they are run.
These reports should be retained for the normal cycle of backup tapes so that,
if questions arise, they will be available.
Reports show the physical count, logical count, and difference between the two
for each record type, as well as the number of blocks of each type on the
backup file. There will always be a difference between the physical and logical
counts for most record types since only the data records (DBRs, VBRs, and so
on) are restored directly; most of the linkage and control records in the
Catalog (DIRs, VIRs, and so on) are rebuilt by RESTORE REORG.

DYNCAT Commands
Example
Backup the CA Dynam Catalog to tape.
// JOB BACKUP THE CA Dynam CATALOG

// ASSGN SYS006,280
// TLBL IJSYSBK,'CA Dynam BKUP',99/365
BACKUP
/*
/&
Backup the CA Dynam Catalog to disk.
// JOB BACKUP THE CA Dynam CATALOG

// DLBL IJSYSBK
// EXEC DYNCAT
BACKUP
/*
/&
Note: Secondary allocations are not supported for the Backup dataset.
DEFINE Command
Use the DEFINE command to define new entities of various types in the CA
Dynam Catalog. There are two different types of information you can define,
depending on the positional operand you supply:
To Define Command Required Operand
characteristics of tape and disk files DEFINE 'data set name'
characteristics of sort key entries DEFINE SKNAME='skname'
Defining Tape and Disk Characteristics
To define the characteristics of tape and disk files, use the following
information.
The format of the command is shown next.
DEFINE 'data set name'
[ ALLoc=(volser,unit,q1,q2,q3,SYSnnn) ]
[ BLKSZ= {nnnnn|OPTimize|'OPT,nnnnn' } ]
[ CATOPEN= {YES|NO } ]
[ CIMSG=('text,r') ]
8–44 User Guide

DYNCAT Commands
[ CLOSE= {NORWD|RWD|UNL } ]
[ COMment='text' ]
[ COMSG=('text,r') ]
[ DEFvlt=c ]
[ {[A] [,B] [,D] [,E] [,F] [,I] } ]
[ DISKOPT=( {[,K] [,L] [,M] [,N] [,O] [,P] } )]
[ {[,S] [,T] [,W] [,X] [,NA] } ]
[ DYNAMFI= {YES|NO } ]
[ EXPdate= {date|RETAIN|PERM } ]
[ FILETYPE= {SD|IS|DA } ]
[ [AUDIT ] ]
[ [,NOCNTRL ] ]
[ [,NOTM ] ]
[ FIopt=( [,NOTRUNC ] ) ]
[ [,SB|DB ] ]
[ [,SL|UL ] ]
[ [,VERIFY ] ]
[ GDGLONG={YES|NO } ]
[ INDex=(volser,unit,q1,q2,SYSnnn) ]
[ LRECL=nnnnn ]
[ MF=AUTO ]
[ MINDEX=(volser,unit,q1,q2,SYSnnn) ]
[ NGEN=nnn ]
[ NOACC=nnnn ]
[ OIMSG=('text,r') ]
[ OOMSG=('text,r') ]
[ OPEN= {NORWD|RWD } ]
[ OVRfl=(volser,unit,q1,q2,SYSnnn) ]
[ OWner={cc|NO} ]
[ PED=date ]
[ PEDCYC=nnn ]
[ PrevFile='data set name' ]
[ PRIme=(sequence,volser,unit,q1,q2,SYSnnn) ]
[ RECFM= {F|FB|V|VB|U } ]
[ RETain=nnnn ]
[ SYsid=cc ]
[ SYSNO={nnn|NO} ]
[ TAPE|DISK|FI ]
[ [AUTOSCR ] ]
[ [,DROP ] ]
[ [,HOLD ] ]
[ TAPEopt=( [,MODIFY ] ) ]
[ [,NOLABEL] ]
[ [,RELEASE] ]

DYNCAT Commands
[ [,ROTATE ] ]
[ USerid=cc ]
[ VLTloc=(A,B,C,...,Z) ]
[ VOLID=cc ]
[ WORK= {YES|NO } ]
[ MODEL='data set name' ]
'data set name' Required positional parameter. Specifies the dataset to be defined. Valid entry
is 1 to 44 characters enclosed in apostrophes for DISK, TAPE or FI.
ALLoc= ALLoc=(volser,unit,q1,q2,q3,SYSnnn)
Optional parameter. Defines the allocation characteristics of a disk dataset if it

is to be allocated by CA Dynam/D. Valid entries are specified within
parentheses and are separated by commas. (Do not omit commas unless they
immediately precede closing parenthesis.)
All of the characteristics of the allocation information are defined when an

ALLOC is processed. Complete ALLOC information must be entered on the
command. The ALLOC parameter may not be used for ISAM files. For ISAM,
the PRIME, INDEX, MINDEX and OVRFL parameters must be used.
volser Volume serial number upon which the extent is to reside.

May be either a real, virtual (pool) or generic volser. The
default is '******', which defines allocation on any
mounted pack.
unit Unit of allocation for the extent. Valid entries are:
TRK for tracks
CYL for cylinders
BLK for FBA blocks
RCD for number of records
The default is TRK. Nonsequential files (DA, ISAM) are

always treated as TRK.
q1 Number of units to allocate for primary allocation. Valid

entries are in the range 0-999999. This is a required
operand.
q2 Number of units to allocate for each secondary allocation.

Valid entries are in the range 0-999999. The default is 0.
q3 Number of secondary allocations to perform. Valid entries

are in the range 0-255. The default is 0.
8–46 User Guide

DYNCAT Commands
To establish catalog-controlled secondary allocation, q2 and q3 must be

numbers other than zero.
To establish automatic secondary allocation, q2 and q3 must both be zero,

and the ASAMAX and ASAAMT parameters of the DYNAM/D option record must
be defined with a number other than zero. To prohibit automatic secondary
allocation, specify NA, either as a file ID option code or in the DISKOPT=
parameter of DYNCAT DEFINE command.
If ASAMAX, ASAAMT, q2 and q3 are all zero, no secondary allocation is

provided.
SYSnnn logical unit to use for the extent(s) generated if none was
specified in the DTF. The default is none.
BLKSZ= Optional parameter. Applicable to both disk and tape. Specifies to CA

Dynam/FI the block size for the file. If specified and CA Dynam/FI is active,
the DTF for the file will be modified. Valid entries are:
Maximum blocksize for tape: 65535
Maximum blocksize for disk: 65535, or
OPT or OPTIMIZE for optimal block size, or
'OPT,nnnnn' (include single quotes)
When optimal blocking is specified, CA Dynam/FI recalculates the block size

for the physical device on which the file is being created. For FBA devices, the
CISIZE is recalculated. The Catalog is updated when the file is closed for
output to record the actual block size used for the file. When the file is opened
for input, CA Dynam/FI must use this value to build the input DTF correctly.
The last form of this parameter should only be used when the file being
defined in the Catalog does not contain the block size specified by the
programs that read the file. That is, use it when the block size of the file has
already been changed by CA Dynam/FI and the existing file will be used for
input before it is created using the catalog entry. It is intended to be used
when a catalog entry is deleted from the Catalog and redefined, and the file
already exists with optimal block sizes. The current block size should be
specified as the nnnnn value.
CATOPEN= Optional parameter. Specifies whether newly opened output versions of this
dataset are to be marked as valid versions so they may be cataloged at OPEN.
This will ensure that the version being created will always be considered a
good version even if it is never closed.
YES This dataset may be cataloged at OPEN.
NO This dataset should be cataloged at CLOSE.

DYNCAT Commands
CIMSG= Optional parameter. It defines user-specified messages for the dataset. These
messages will be issued Open Input (OIMSG=), Open Output (OOMSG=),
Close Input (CIMSG=), and/or Close Output (COMSG=) for the dataset, as
specified, and will be directed to the operator console and/or SYSLST as
indicated by the routing code. Routing codes are as follows:
C - Console (default)
P - Printer
B - Both
Valid input is 1 to 70 alphanumeric characters of message text, followed by a

comma, followed by single-character routing code, following optionally by a , A
if message should ring the console. All are enclosed by apostrophes.
Example
OIMSG='MY MESSAGE,C'
OOMSG='MY MESSAGE FOR OUTPUT, C,A'
CLOSE= Optional parameter that specifies the DTF rewind option set by CA Dynam/T or
CA Dynam/FI for CLOSE.
NORWD tape is not rewound
RWD force rewind
UNL force rewind and unload
COMment= Optional parameter. Specifies the comment field to be associated with this
dataset. Valid entries are 1 to 100 alphanumeric characters enclosed in
apostrophes.
Note that, even though up to 100 bytes of comment may be specified, the
comment shown on some reports may be truncated due to space limitations.
COMSG= See CIMSG operand description.
DEFvlt= Optional parameter. Defines the default vault location for all versions of the
dataset not specified by VLTLOC parameter. Normally, the default vault
location is A. Valid entry is:
One alphabetic character in the range A-Z.
If omitted, the main tape vault (A) is assumed.
8–48 User Guide

DYNCAT Commands
DENsity= Optional parameter. Specifies the recording density for this dataset. Valid
entries are:
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI

write)

write)

write)

write)

write)

write)

buffered write)

DYNCAT Commands

mode)

write)

unbuffered write)

write)

unbuffered write)

unbuffered write)

write)

unbuffered write)

unbuffered write)
NO No density is specified for this dataset.
8–50 User Guide

DYNCAT Commands
DISKOPT= Optional parameter. Specifies one or more of the processing options to be

used for the disk dataset when it is processed under CA Dynam/D control. For
more information about the effect of each of the various options, see Defining
File ID Option Codes in the chapter "Disk File Management." Valid entries are
one or more of the following options:
A, B, D, E, F, I, K, L, M, N, O,
P, S, T, W, X, NA
Enclose options in parentheses, separated with commas or blanks.
DYNAMFI= Optional parameter. Specifies whether CA Dynam/FI is to use and update

information from the Catalog. If you want CA Dynam/FI to do so, you must
specify YES. Otherwise, it will not access the Catalog regardless of other
parameters defined for this dataset. Valid input is:
YES Enable Catalog access for this dataset.
NO Disallow CA Dynam/FI to access Catalog information (the

default).
EXPdate= Optional parameter. Specifies the expiration date to be used when new
versions of this dataset are created. Valid entries are:
mm/dd/yy
mm/dd/yyyy
dd/mm/yyyy
dd/mm/yy
yyddd
yyyyddd


DYNCAT Commands
FILETYPE= Optional parameter. Specifies the type of label record that CA Dynam/D builds
when the disk file is opened. Valid entries are:
IS for ISAM
DA for direct access
SD for sequential disk
The default is SD.
FIopt= Optional parameter. Specifies processing options for CA Dynam/FI. Note that
some of these options are the same as those that may be specified to CA
Dynam/T. If both CA Dynam/T and CA Dynam/FI are in use, the tape
processing options should be specified to CA Dynam/T where possible. If
conflicting options are specified, unpredictable results may occur. Valid entries
are one or more of the following separated by commas or blanks and enclosed
in parentheses:
SB Single buffering for disk or tape files
DB Double buffering for disk or tape files
RELEASE Release of the logical assignment when the disk or tape

file is closed
NORELSE No release of the logical assignment when the disk or

tape file is closed
VERIFY Verification of output by reading the disk record just

written. Operates by enabling the VERIFY option in the
user's DTF.
NOTM No writing of a tape mark at close
SL Standard label processing for tapes
UL Unlabeled processing for tapes
NOTRUNC Ignoring 'TRUNC' requests for this file. (For more

information about the TRUNC macro, see the IBM VSE/AF
NOCNTRL Ignoring 'CNTRL' requests for this file. (For more

information about the CNTRL macro, see the IBM VSE/AF
8–52 User Guide

DYNCAT Commands
AUDIT Performing CA Dynam/FI audit recording for this file even

though no other characteristics of the file have been
modified. This function may be used either from the
Catalog or as a CA Dynam/FI DLBL/TLBL option to cause
audit information to be recorded about selective files.
GDGLONG= Optional parameter. Specifies whether a suffix of .G#nnnnnn will be added to

a generation dataset. nnnnnn can be any number from 000001 to 065535. Up
to 999 versions can be active at one time. Specifying GDGLONG=NO causes
the previous format, G#nn, be used.
INDex= INDex=(volser,unit,q1,q2,SYSnnn)
Optional parameter. Specifies the allocation characteristics of the index extent

to be generated for the (ISAM) disk dataset if it is to be allocated by
CA Dynam/D. Valid entries are the same as for the PRIME data allocation
(except for the sequence option).
Note: You must specify KEKL1 if you want to specify KEKL2. If you don’t
Note: You can specify KEKL2 only if you have specified KEKL1. If you don’t
LENgth= Optional parameter that specifies the size tape to be requested for this
dataset.
XS extra short
S short
MS medium short

DYNCAT Commands
M medium
ML medium long
L long
NO No length is indicated for this dataset
LRECL= Optional parameter. Specifies to CA Dynam/FI the logical record length for the
file. The DTF for the file will be modified. For more information about the effect
of this parameter, see the chapter "Controlling File Independence." Valid entry
is a 1- to 5-digit number in the range 1 to 65535.
MF= Optional parameter. Specifies that the dataset is to be an automatic multifile

dataset. The only valid input is:
AUTO Indicates that the dataset is an automatic multifile

dataset.
MINDEX= MINDEX=(volser,unit,q1,q2,SYSnnn)
Optional parameter. Specifies the allocation characteristics of the master index

extent to be generated for the (ISAM) disk dataset if it is to be allocated by CA
Dynam/D. Valid entries are the same as for the PRIME data allocation (except
for the sequence option).
MODEL= Optional parameter. Copies a dataset definition. The new dataset will be
defined with the same attributes as the specified model dataset. The only valid
entry is a 1- to 44-character data set name, enclosed in apostrophes.
Do not include any other operands when specifying MODEL with the DEFINE
command.
NGEN= Optional parameter. Specifies the number of generations to be saved for this
dataset. For tape files, the number is the minimum number of cycles to be
retained, i.e., the SCRATCH function will never scratch any tapes belonging to
a version less than or equal to this value.
For disk datasets, this number represents the maximum number of

generations to be retained, i.e., CA Dynam/D will delete a generation from the
VTOC when a new generation is created which results in one more generation
existing on disk than is specified by NGEN. It is recommended that disk
generations to be controlled in this fashion be created using an expiration date
of RETAIN, to assure that they will not be inadvertently deleted by the
operator during space recovery. Valid entries are:
a 1- to 3-digit number in the range 0-999 for tape or disk datasets.
NOACC= Optional parameter. Specifies the number of days a version is to be retained

after last access before it becomes eligible for scratch.
8–54 User Guide

DYNCAT Commands
OIMSG= See CIMSG operand description.
OOMSG= See CIMSG operand description.
OPEN= Optional parameter. Specifies the DTF rewind option set by CA Dynam/T or CA
Dynam/FI for OPEN.
NORWD Tape is not rewound
RWD Force rewind
OVRfl= OVRfl=(volser,unit,q1,q2,SYSnnn)
Optional parameter. Specifies the allocation characteristics of the independent

overflow to be generated for the (ISAM) disk dataset if it is to be allocated by
CA Dynam/D. Valid entries are the same as for the PRIME data allocation
(except for the sequence option).
OWner= Optional parameter. Specifies the ownership code for this dataset. Valid
entries are:
cc 1 or 2 alphanumeric characters.
NO No ownerid specified. Leaves blank spaces in this field.
1 to 2 alphanumeric characters.
PASSword= Optional parameter. Specifies the password to be associated with this dataset.
If specified, this password will be required by DYNCAT in order to perform
maintenance on this dataset.
For disk datasets, this password will also be required by CA Dynam/D before
allowing access to the dataset. Valid entry is:
1 to 8 alphabetic characters within apostrophes.
PED= Optional parameter that specifies the period-ending-date value (as-of-date

value) for this file. Valid entries are:
date Acceptable date forms are mm/dd/yy or dd/mm/yy.
You may substitute two asterisks for any or all date fields. When CA Dynam/T
encounters the asterisks, it will replace them with that field from the job date
(temporary COMREG date for VSE users).
For example: **/31/** would be changed to 05/31/00 for each version of the
dataset created in May of 2000.

DYNCAT Commands
No validation is done on the eight bytes specified for period ending date. Dates
are normally used, but this field may also be used to store eight bytes of user
information about the version, if desired. If a period ending date field contains
nonblank characters, or a date different from the creation date, the contents
of the field will be printed on applicable reports.
When used for a dataset with PEDCYC=0, the PED field becomes simply a user
comment field associated with each version.
PEDCYC= Optional parameter that specifies the number of versions of this dataset being
retained by period-ending-date control. Valid entry is:
nnn An integer value in the range 0-999.
Default is 0, which indicates that the PED field is a comment.
PrevFile= Optional parameter. Specifies the prior file name when defining a multifile tape
a 1- to 44-character data set name enclosed in apostrophes.
PRIme= PRIme=(sequence,volser,unit,q1,q2,SYSnnn)
Optional parameter. Specifies the characteristics of a particular prime data

extent to be generated for a disk dataset if it is to be allocated by CA
Dynam/D. Valid entries are specified within parentheses separated by commas
(even if omitted):
sequence Extent sequence number to be defined. Must be numeric

in the range 0 - 255. This is a required operand.
volser Volume serial number upon which the extent resides. May
be either a real, virtual (pool) or generic volser.
unit Unit of allocation for the extent. Valid entries are:
TRK for tracks
CYL for cylinders
BLK for FBA blocks
RCD for number of records
ABS for absolute quantity (indicating fixed extent file)
q1 Number of units to allocate for primary allocation. Valid

entries are in the range 0 - 999999. If unit was specified
as ABS, specifies the beginning location of extent.
8–56 User Guide

DYNCAT Commands
q2 If unit was specified as ABS, specifies the number of

tracks or blocks for the extent. (Not valid unless ABS was
specified.)
SYSnnn Logical unit to use for the extent(s) generated if none

was specified in the DTF.
RECFM= Optional parameter. Specifies to CA Dynam/FI the record format for the file.
The DTF for the file will be modified. Valid entries are:
F Fixed-length
FB Fixed-blocked
V Variable-length
VB Variable-blocked
U Undefined
RETain= Optional parameter. Specifies the number of days past the creation date to be
used to calculate the expiration date when new versions are added to this
ROBOT= Optional parameter. Specifies whether DYNAM/CMS will search robotic-type

tape devices when a DYNOPEN command is issued by VSE.
YES Allows robotic-type devices.
NO Disallows robotic-type devices.
SYsid= Optional parameter. Specifies the system-ID field that will appear in each
version record. Valid entry is a 2-character ID to be used for reporting
purposes.
SYSNO= Specifies whether a SYS number override is defined for a dataset in the
catalog. Valid entries are:
001 to 255 Specifies a SYS number for the dataset.
000 or NO Deactivates the override.
TAPE|DISK|FI Optional parameter. Identifies the type of data storage medium to be used for
this dataset.
TAPE Restricts the dataset to tape use only, under the control
of CA Dynam/T. It is not eligible for dynamic device
switching.

DYNCAT Commands
DISK Restricts the dataset to disk use only, under the control
of CA Dynam/D. It is not eligible for dynamic device
switching.
FI Allows the dataset to be used either for tape or disk, and

is eligible for dynamic device switching. A dataset with
this specification may have both tape and disk
characteristics.
Note that TAPE, DISK, and FI are mutually exclusive parameters. DYNCAT
ALTER may be used to switch among them for a file, if desired. If you don't
specify an operand for TAPE, DISK, or FI, DYNCAT defaults to the parameter
specified in the DYNAM/COMMON system option record set at installation.
For information about operator device switching, see the chapter "Controlling
File Independence."
TAPEopt= Optional parameter. Specifies the default processing options performed during
OPEN and CLOSE by CA Dynam/T. Enclose options in parentheses, separated
with commas or blanks. Valid options are:
AUTOSCR Causes CA Dynam/T to analyze this dataset for versions

eligible to be scratched at every CLOSE for output. Valid
only for single file tape datasets, the processing of this
option is also dependent upon the setting of the
AUTOSCR parameter in the DYNAM/T option record. If
specified, the CADT064I message will be issued whenever
a version is scratched due to AUTOSCR.
DROP Forces the CA Dynam/T 'DROP' option (to erase TLBL at

file CLOSE).
HOLD Forces the CA Dynam/T 'HOLD' option (to hold

assignment) at CLOSE.
MODIFY Forces the CA Dynam/T 'MODIFY' option (to alter DTF file
name) at OPEN.
Note: These CA Dynam/T options for OPEN and CLOSE are usually specified
on the TLBL, not in the Catalog as dataset attributes. For more information
about the effect of these options, see the chapter "Maintaining Tape Files."
NOLABEL Causes CA Dynam/T to process tapes within this dataset

as UNLABELED.
RELEASE Scratches a WORK dataset at CLOSE. This parameter is

only valid for datasets specified as WORK=YES.
8–58 User Guide

DYNCAT Commands
ROTATE Causes CA Dynam/T to process tapes within this dataset

in a cyclical fashion, so that the newest output version
will be written over the oldest version of the dataset, if
the number of versions specified by the NGEN parameter
for the dataset is filled. All expiration and retention
criteria are ignored when rotating. That is, even if
EXPDATE=PERM, the oldest version will be scratched.
When the first file of a multifile set is reused, all the subsequent files are
scratched. Thus, if a multifile, multivolume set is being rotated, all the
volumes not reused by the first file are returned to the scratch pool and will
not be called when creating the subsequent files of the multifile set.
USerid= Optional parameter that specifies the user ID field which will appear in each
version record. Valid entry is a 2-character ID to be used for reporting
purposes.
VIRTape= Optional parameter. Specifies whether a dataset should be created as a virtual

file.
NO The file is not created as a virtual file.
VTAPE The file is created using VTAPE.
FTAPE The file is created using FakeTape.
VLTloc= Optional parameter. Specifies the vault rotation scheme to be used for
versions of the dataset. Valid entries are 1- to 100-alphabetic characters
enclosed in parentheses and separated by commas. Each character represents
a vault location. Its relative position in the string represents the generation of
the dataset that is to be in that vault.
For example: (A,A,B,A) specifies that Versions 1 and 2 are to be in vault A.

Version 3 is to go to vault B and Version 4 is to return to vault A. The first 999
versions of a data set may have vault location control. All versions after 999
will be kept in the default vault (see DEFVLT parameter).
VOLID= Optional parameter. Defines a volume identifier that allows the tape volume to
receive output from the dataset. The volume identifier must match the first
two characters of the volume serial number.

DYNCAT Commands
WORK= Optional parameter. Specifies that this tape dataset is to be processed as a

tape work dataset.
YES This is a work dataset. The RELEASE option may be used.
NO This is not a work dataset. The RELEASE option will be

ignored if used. You may not specify retention
information for a work dataset. Do not use RETAIN,
PEDCYC, or NGEN with this parameter.
Examples
Examples are shown next.
// JOB DEFINE ENTRIES IN THE CA Dynam CATALOG

DEFINE 'MULTI-FILE1' NGEN=3 DENSITY=6250 X
DEFINE 'MULTI-FILE2' PREVFILE='MULTI-FILE1' Y
DEFINE 'MULTI-FILE3' PREVFILE='MULTI-FILE2' Z
DEFINE 'BACKUP' NGEN=5 VLTLOC=(A,C,C) DEFVLT=A [
DEFINE 'PRBACKUP' RETAIN=180 CLOSE=UNL + \
PASSWORD='PROTECT' SYSID=PR LENGTH=L ]
DEFINE 'EDIT BATCHES ***' MF=AUTO COMMENT='PROTOTYPE AMF DSN' ^
DEF 'BG.CPU-A.WORK1' ALLOC=(POOL01,TRK,57,19,3) DISK _
DEF 'F1.CPU-A.WORK' ALLOC=(POOL01,TRK,57,19,3) DISK `
DEF SKNAME='PAY220KY' FIELDS=(20,14,CH,A) RECFM=F LRECL=150 a
DEF 'FICHE.FILE' TAPE BLKSZ=12100 FIOPT=(SL,DB,NOCNTRL) +
NGEN=2 DYNAMFI=YES
DEF 'MASTER.PAYROLL' DISK PRIME=(0,PAY001,ABS,1900,1900,SYS099) +
PRIME=(1,PAY002,ABS,1900,1900,SYS098) +
PRIME=(2,PAY003,ABS,1900,1900,SYS097)
/*
/&
1, 2, 3 These define a three-data-set multifile set. The define statement for

MULTI-FILE1 establishes the characteristics for the entire set while MULTI-
FILE2 and MULTI-FILE3 are chained to it with the PREVFILE operand.
4 This defines a dataset BACKUP that is to have 5 generations. Version 1 is

to be in vault A; Versions 2 and 3 are to be in vault C; Versions 4 and 5
default back to vault A.
5 This defines PRBACKUP, which is to be retained for 180 days. Whenever

the file is closed, it is to be unloaded. The password PROTECT must be
supplied in order for maintenance to be performed on the dataset. It is to
have a system ID of PR and is to be written on a long tape.
6 Note the continuation of the DEFINE statement in example 5 onto this

example (6) by placing a nonblank character in position 72 and continuing
the operands on the next statement.
7 This defines EDIT BATCHES *** as an automatic multifile dataset.
8–60 User Guide

DYNCAT Commands
8, 9 These define the DASD work files for BG and F1 to be used in conjunction
with the partition- and CPU-independent data set name feature of CA
Dynam/D. The files are to be allocated in the POOL01 pool with a primary
allocation of 57 tracks and up to 3 secondary allocations of 19 tracks each.
10 This defines a sort key record in the Catalog, with a name PAY220KY. The
sort key to be used is as indicated. This information may be used by CA
Dynam/FI for automatic sorting through the CA SRAM interface.
11 This defines a Catalog entry with information to be used by CA Dynam

when processing 'FICHE.FILE'. CA Dynam/FI will modify the DTF to a tape
DTF, and reblock it as indicated; double buffering will be used, and CA
Dynam/T will control the tape, retaining 2 generations. Any CNTRL macros
issued by the original program will be ignored.
12 This defines to the Catalog an existing file 'MASTER.PAYROLL' which is a

fixed extent file consisting of 3 extents on three volumes as indicated.
Defining Sort Key Records
Sort key records are used in conjunction with CA Dynam/FI. For more
information, see the chapter "Controlling File Independence." To define the
characteristics of sort key entries, the following operands apply to the DEFINE
command:
DEFINE SKNAME='skname'
FIELDS=(nnnn,nnnn,format,A|D....)
[ FORMAT= {CH|BI|ZD|PD|FI|FL|CSL|CTO|CST|CLO|AQ } ]
[ RECFM= {F|V } ]
SKNAME='skname' Required positional parameter. Specifies the sort key name record to be
defined. This parameter is mutually exclusive with the 'data set name'
parameter. A valid entry is a 1- to 8-character sort key name.
FIELDS= FIELDS=(s1,l1,t1,m1,s2,l2,t2,m2,. . .)
Required parameter. Specifies the control field information for the sort key
record defined by the SKNAME parameter. Valid entries are:
sn Control field position relative to the start of the record
ln Control field length

DYNCAT Commands
tn Control field data type (same as FORMAT parameter)
mn A for ascending, or D for descending sequence mode. CA

SRAM restrictions apply to these fields. For more
information, see the CA SRAM User Guide.
FORMAT= Optional parameter. Specifies the format of the data in the sort key field(s)
defined by the SKNAME parameter. A valid entry is one of the data types
acceptable to CA SRAM:
CH Character
BI Binary
ZD Zoned Decimal
PD Packed Decimal
FI Fixed Point
FL Floating Point
CSL Numeric, Separate Leading Sign
CTO Numeric, Trailing Overpunch Sign
CST Numeric, Separate Trailing Sign
CLO Numeric, Leading Overpunch Sign
AQ Alternate Collating Sequence
RECFM= Optional parameter. Specifies to CA Dynam/FI the record format for the file.
Valid entries are:
F Fixed-length
V Variable-length
The default is F.
Example
An example is shown next.
DEF SKNAME='PAY220KY' FIELDS=(20,14,CH,A) RECFM=F
8–62 User Guide

DYNCAT Commands
DELETE Command
Use the DELETE command to remove records from the Catalog. The following
types of records may be removed, each type achieving different results:
entire datasets
one or more versions of a dataset
sort key records
volume serial numbers.
Deleting a version of a dataset will result in all of its associated tape volumes
being returned to SCRATCH status.
You can control the scope of record deletion by using one of the following
positional operands:
To Delete Entries For Use Command Required Operand
one or all versions of a dataset DELETE 'data set name'
A sort key name DELETE SKNAME='skname'
A volume DELETE VOLser=xxxxxx
Deleting Dataset Records
To delete dataset records, provide the following information:
DELETE 'data set name' {ALL|GDSid=nnnnn|VERsion=nnn|VOLser=xxxxxx }
[PASSword='password'] [PURGE]
[PERmvlt= {YES|NO } ]
'data set name' Required positional parameter. Specifies the data set name or dataset version
that is to be deleted. A valid entry is 1 to 44 characters enclosed in
apostrophes.
ALL, GDSid=, VERsion=, VOLser=

The following parameters are mutually exclusive.
Choose one. Each parameter is explained next.
ALL Used to delete an entire dataset from the Catalog and

return all associated tape volumes to SCRATCH status.
Existing disk generations will not be affected; that is, no
VTOC entries will be removed, but the dataset will no
longer exist in the CA Dynam Catalog.

DYNCAT Commands
GDSid Specifies the Generation Data Set ID of the disk dataset

to be deleted (CA Dynam/D controlled only). The GDSid,
serial number, or version number must be present when
deleting a specific generation. A valid entry is a 1- to 5-
digit numeric generation ID in the range 1-65535.
Note that, when a generation of a CA Dynam/D controlled disk dataset is

deleted, the generation record is removed from the Catalog, but the file
continues to exist on its disk volume until it is removed from the VTOC by
other means. Deleting a disk generation does not affect the next GDSid to be
used by CA Dynam/D when the file is opened for output. The ALTER function
may be used to modify this value.
VERsion Specifies the generation to be deleted. The version

number, volume serial number or GDSid operand must be
present when deleting a specific generation. When a
generation is deleted, its associated tape volumes
become SCRATCH tapes immediately. A valid entry is a
VOLser Specifies the first or only volume of a tape dataset

generation to be deleted. The volume serial number,
version number or GDSid must be present when deleting
a specific generation. A valid entry is a 1- to 6-character
PASSword= Required if dataset has a password. Specifies the password required to delete
this dataset or a version of the dataset. A valid entry is 1 to 8 alphabetic
characters enclosed in apostrophes.
This operand is only required if a password was defined to the dataset.
PERmvlt= Specify YES if the version to be deleted resides in a permanent vault (ALTERed
by PERM=YES).
PURGE Specify PURGE to delete a file or files from a DASD volume. The disk file or
files deleted will be those which are associated with the version records
selected for deletion by a
Delete 'dsn' {ALL|GDSid=nn|VERsion=nnn } command.
8–64 User Guide

DYNCAT Commands
Deleting Sort Key Records
To delete sort key records, provide the following information:
DELETE SKNAME='skname'
SKNAME= Optional parameter. Indicates that the named sort key record is to be deleted.
A valid entry is 1- to 8-character sort key name enclosed in apostrophes.
Deleting Volume Records
To delete volume records, provide the following information:
DELETE VOLser=xxxxxx [EXTERNAL= {NO|YES }]
VOLser= Required parameter, mutually exclusive with 'data set name'. Specifies the
volume serial number record to be completely deleted from the Catalog for a
tape volume currently in SCRATCH status. A valid entry is a 1- to 6-character
EXTERNAL= Optional parameter. Indicates whether volume is externally owned; that is,
whether it is owned by another system. If you want to delete an externally
owned volume, you must specify EXTERNAL=YES.
The default is EXTERNAL=NO.
Information that an external volume is being deleted is not passed to the

external system. It is the responsibility of the owning system to maintain its
own volumes. However, information about CA Dynam/VSE-owned volumes is
passed to the other system.
Example
An example follows:
// JOB DELETE FROM THE CA Dynam CATALOG

DELETE 'OLD TRANS' VER=3 X
DELETE 'SORTED AR' VOLSER=1766 Y
DELETE VOLSER=1766 Z
DELETE 'TEST FILE' ALL [
DELETE VOLSER=333333 EXTERNAL=YES \
/*
/&

DYNCAT Commands
1 This scratches the volume that contains Version 3 of dataset OLD TRANS.
The volume serial number is unknown.
2 This deletes the version of 'SORTED AR' on volume 1766, and returns
1766 to SCRATCH status. If the 'SORTED AR' version contains multiple
volumes, all will be scratched.
3 This deletes Volume 1766 from the Catalog.
4 This deletes the dataset TEST FILE from the Catalog and returns all of the
tapes associated to the scratch pool.
5 This deletes externally owned volume 333333.
Note: The DELETE function, whether to delete an entire dataset, a volume

serial number, or a version of a dataset, is effective immediately.
DEQUEUE Command
Use the DEQUEUE command in a multi-CPU environment to release a Catalog

lock-out condition. This condition can occur if the DYNCAT program is canceled
while updating the Catalog.
The format of the command is shown next.
DEQUEUE (no associated operands)
Example
An example follows:
// JOB UNLOCK THE CATALOG

DEQUEUE
/*
/&
The above job stream could be used to unlock the Catalog file.
Important! Before using the DEQUEUE function, ensure that no Catalog

update is actually in progress in any partition in any system. If the Catalog is
enqueued by a looping program, cancel the program before issuing the
DEQUEUE command.
8–66 User Guide

DYNCAT Commands
END Command
Use the END command to terminate DYNCAT processing. This command is

optional.
END (no associated operands)
Example
An example follows:
// JOB END EXAMPLE FOR DYNCAT

DEFINE 'DATA.1' DISK
END
/*
/&
INITIAL Command
Use the INITIAL command to format the CAICATL Catalog file.
INITIAL [ CISIZE=nnnn ]
[ DATAsets=nnnnnn ]
[ id='text' ]
[ SHARE= {YES|NO|VSELOCK } ]
[ SORTkeys=nnnnnn ]
[ VOLumes=nnnnnn ]
CISIZE= Optional parameter. Specifies the control interval size for the Catalog being
initialized. This value should be chosen to optimize track utilization on the
DASD device where the Catalog will reside. The value must be a whole number
multiple of 1024; valid entries are 1024, 2048, 3072, or 4096.
The default is 1024.
DATAsets= Optional parameter. Specifies the number of datasets that the Catalog will
contain. This value should be chosen carefully since it helps determine the
amount of space in the Catalog reserved for index area. A valid entry is a 1- to
6-digit number. The default is 250.

DYNCAT Commands
ID= Optional parameter. Establishes a Catalog owner ID for all tapes associated
with a particular CA Dynam Catalog. The owner ID is placed in the VOL1 label
of the tapes belonging to the Catalog. Any tape that does not have a matching
owner ID will not be recognized during AVR if catalog checking is specified in
the DYNAM/T option record. A valid entry is 1 to 16 characters enclosed in
apostrophes.
It is possible to establish a Catalog owner ID that will be written on all output

tapes but not checked by AVR. To do this, specify CATCHK(NO) in the
DYNAM/T option record, and code the ID operand when initializing the Catalog.
Once all tapes have the owner ID in the VOL1 label, the checking feature may
be turned on by specifying CATCHK(YES) in the DYNAM/T option record. If no
ID is specified, a default of CA Dynam/T will be used.
If you have used the Catalog ownership feature on earlier releases of CA

Dynam/T and want to continue using it, you must ensure that the first 10
characters of the ownership codes are the same between the two releases. If
they are not, AVR will not recognize the tapes.
PASSword= Optional parameter. Specifies the required password to display the passwords
for password-protected datasets. A valid entry is 1 to 8 characters enclosed in
apostrophes.
Important! The Catalog password does not appear on any report and cannot
be changed without reorganizing the Catalog; make sure to remember the
password.
SHARE= Optional parameter. Indicates whether the Catalog file will be shared by
multiple systems. Valid entries are:
YES The Catalog is shared.
NO The Catalogis not shared.
VSELOCK The Catalog is shared and enqueuing is done using the

VSE external lock file rather than internal CA methods.
The default is NO.
SORTkeys= Optional parameter. Specifies the number of sort key records that the Catalog
will contain. This value should be chosen carefully since it helps determine the
amount of space in the Catalog reserved for index area. A valid entry is a 1- to
6-digit number. The default is zero.
VOLumes= Optional parameter. Specifies the number of volume serial numbers that the
Catalog will contain. This value should be chosen carefully since it helps
determine the amount of space in the Catalog reserved for index area. A valid
entry is a 1- to 6-digit number. The default is 1000.
8–68 User Guide

DYNCAT Commands
Example
An example follows:
// JOB INITIAL CA Dynam CATALOG

INITIAL id='PRODUCTION CATLG' PASSWORD='SECURITY' DATA=200
/*
The above example will initialize the CA Dynam Catalog to be used on a single
CPU. Space for 200 datasets is to be reserved in the index area, and the
Catalog owner and password are specified.
Note: When initializing a Catalog, the initializing system and all sharing
systems should be in a quiesced state, otherwise unpredictable results may
occur.
To prevent the accidental destruction of the Catalog file, the following console
message is issued:
'CADC421D REALLY INITIALIZE THE CATALOG?'
If the response is YES, the Catalog file is formatted. When the job has
completed, the Catalog will be ready for use. If an existing Catalog is
reinitialized, any existing entries are destroyed.
INT and INTR Commands
Use the INT command to initialize (and unload) a tape as a CA Dynam/T tape.
These tapes will contain standard labels and are marked as CA Dynam/T
initialized tapes. The INTR command is identical to the INT function except
that the tape is not unloaded, but rewound after being initialized.
INT|INTR unitnumber
[ CLean=nnn ]
[ CUU=(cuu1,cuu2,...,cuu16) ]
[ DENsity=cccc ]
[ FIRSTvol=xxxnnn ]
[ LASTvol=xxxnnn ]
[ LENgth= {XS|S|MS|M|ML|L } ]
[ NEW ]
[ OWner={cc|NO} ]
[ VOLser=xxxxxx ]

DYNCAT Commands
unitnumber Required parameter. Specifies the logical or physical unit number of the device
where the tape to be initialized resides. Valid entries are:
SYSnnn Where nnn is the logical unit number (SYS number)

assigned to the tape drive.
cuu The tape drive address.

cumulative total that is retained in the Catalog until the tape is reinitialized. A
valid entry is:
CUU= Optional parameter. Allows the initialization of multiple tapes starting with
cuu1 up to cuu16. FIRST and LAST volumes must be specified with CUU=.
DENsity= Optional parameter. Specifies the recording density for this tape. Valid entries
are:
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI
08E for tape cartridge (3490 data compaction with buffered

write)
8–70 User Guide

DYNCAT Commands

write)

write)

write)

write)

write)

buffered write)
20E for tape cartridge (3490 unbuffered write mode)

mode)
28 for tape cartridge (data compaction unbuffered write)
28E for tape cartridge (3490E data compaction unbuffered

write)
28M for tape cartridge (3590 data compaction unbuffered

write)
28ME for tape cartridge (3590E data compaction unbuffered

write)
28MH for tape cartridge (3590H data compaction unbuffered

write)

DYNCAT Commands
28W for tape cartridge (3592 data compaction unbuffered

write)
28WE for tape cartridge (3592E data compaction unbuffered

write)
2BWE for tape cartridge (3592E encrypted data compaction

unbuffered write)
FIRSTvol= Specifies the first tape in a multi-tape initialization. The alpha-character

portion of the tape name must match that specified for the LAST volume. Both
must end in a numeric value.
LASTvol= Specifies the last tape in a multi-tape initialization. The alpha-character

portion of the tape name must match that specified for the FIRST volume.
Both must end in a numeric value. For example, FIRST=JVA001
LAST=JVA012.
LENgth= Optional parameter. Specifies the length of this tape. Valid entries are:
XS Extra short
S Short
MS Medium short
M Medium
ML Medium long
L Long
NEW Optional keyword parameter. Specifies that the tape to be initialized is a new
tape. Causes CA Dynam/T to immediately write a VOL1/HDR1 on the tape
without attempting to read the tape to determine if it contains valid data, since
to do so would result in an I/O error if the tape has never been initialized. Use
this parameter carefully.
8–72 User Guide

DYNCAT Commands
OWner= Optional parameter. Specifies the tape ownership code to be assigned to this
tape. If selected, this tape may only be used for datasets with matching
ownership codes. A valid entries are:
cc 1 to 2 alphanumeric characters.
NO No ownerid specified. This will leave blank spaces in this

field.
VOLser= Optional parameter. Specifies the volume serial number to be written on the
tape and placed in the Catalog. A valid entry is a 1- to 6-character volume
serial number (may be enclosed in parentheses), consisting of letters and
numbers ONLY no special characters allowed.
VOLSER numbers that are not acceptable are ACCEPT, CANCEL, all zeroes
(000000) and all blanks.
If this parameter is not specified, the tape is read to determine its volume
serial number, and the operator is prompted to verify the accuracy of the
VOLSER found.
// JOB INITIAL CA Dynam/T TAPES

// ASSGN SYS006,280
INT SYS006 VOLSER=(011256) CLEAN=100 DENSITY=1600 LENGTH=L X
INT 281 VOLSER=(718) Y
/*
/&
1 The tape on drive 280(SYS006) is initialized with the volume serial number
011256. It is flagged for cleaning after 100 tape errors. It is initialized at
1600 BPI and is a long tape.
2 This initializes the tape on 281 with the volume serial number 718. It will
not have a tape error threshold or a length code, and it will be initialized
with the recording density set in the VSE supervisor for this tape drive.
LISTCAT Command
Use the LISTCAT command to report upon each of the various entries in the
Catalog, either individually or as a whole. LISTCAT requires no external work
area and does not enqueue the Catalog while accessing it. A separate LISTCAT
command must be submitted for each type of record to be reported upon.
For more information about sample reports produced by using the LISTCAT
command, see the chapter "CA Dynam Report Example."

DYNCAT Commands
LISTcat {'data set name'}

{TAPE['data set name']]
{DISK['data set name']}
{ALL }
or
LISTcat SKR= {'skname'|ALL }
or
LISTcat {VCR|CCR }
or
LISTcat VOL= {volser|ALL }
'data set name' Optional parameter. Specifies the dataset to be reported on. Valid entries are:
1- to 44-character data set name enclosed in apostrophes

the first n characters of a group of data set names (for a generic report).
TAPE|DISK|ALL Optional qualifier. Identifies the generic group of datasets to be reported upon.
TAPE or DISK restricts report to either tape or disk datasets, respectively. If

no data set name is entered, all datasets will be displayed within the indicated
group. The listing is presented in alphabetic sequence.
SKR= Optional parameter. Specifies the sort key record to be reported upon, or if
used with the qualifier ALL, specifies that a generic group of sort key records is
to be reported upon. The listing will be presented in alphanumeric sequence.
Valid entries are:
a 1- to 8-character sort key name enclosed in apostrophes.
the first n characters of a group of sort key names (for generic report if
qualified by ALL).
ALL to display all sort key records.
VCR|CCR Optional parameter. Specifies what is to be displayed. Valid entries are:
VCR for Vault Control Records and slot ranges.
CCR for the Catalog Control Record.
VOL= Optional parameter. Specifies the volume serial number record(s) to be

reported upon. Volume serial numbers will be presented in alphanumeric
sequence. Valid entries are:
a 1- to 6-character volume serial number.
ALL to display information about all volume serial number

records in the Catalog.
8–74 User Guide

DYNCAT Commands
Example
An example follows:
// JOB LISTCAT DISPLAY VARIOUS COMPONENTS OF THE CATALOG

LISTCAT 'PAY' DISK X
LISTCAT 'TRAN' TAPE Y
LISTCAT CCR Z
LISTCAT VOL=ALL [
LISTCAT SKR='PAY220SK' \
/*
/&
1 This displays all Catalog-controlled disk datasets whose data set names
begin with 'PAY'.
2 This displays all Catalog-controlled tape datasets whose data set names
begin with 'TRAN'.
3 This displays the Catalog control record for the Catalog.
4 This displays all volume records in the Catalog.
5 This displays the sort key record named 'PAY220SK'.
MACC Command
Use the MACC command for CA Dynam/T to dequeue or initialize a Multiple

Access (MACC) file. This command is needed when either the CA TLMS
interface or other cross-system interface is active.
MACC {DEQUEUE[DDNAME=ddname]|INITIAL[DDNAME=ddname] }
Required parameter. The following operands are mutually exclusive:
DEQUEUE Dequeues the MACC file.
INITIAL Initializes the MACC file.
DDNAME= Optional parameter. Indicates the ddname for the MACC file. Valid entry is 1 to
7 alphanumeric characters, the first of which must be alphabetic.
The default is CAIMACC. You must use CAIMACC for the CA TLMS interface.
Use a ddname other than CAIMACC for cross-system MACC files.

DYNCAT Commands
Example
// JOB MACC INITIAL

MACC INITIAL
/*
/&
MCAT Command
Use the MCAT command to catalog an active version of a dataset as an active

version of one or more additional datasets. The volumes of a multi-cataloged
version are eligible for scratch only when all of the multi-cataloged versions
are scratched.
Note:
Only single file volumes may be cataloged in this fashion.
MCAT and MCATAL cannot be used with multifile datasets including AMF
and unchained datasets (STACK=).
The MCAT and MCATAL commands perform the same function, but MCAT is the
preferred command. The MCATAL command allows for easier conversion from
CA EPAT.
MCAT FROMDSN='dsn' TODSN='dsn' [FROMVERS=nnn ]

[TOVERS=nnn ]
[PASSWORD='password']
MCATAL FROMDSN=dsname {.(0)|.gen },TODSN=dsname {.(0)|.rgen }

[PASSWORD='password']
FROMDSN= Required, positional parameter. Specifies the dataset to which the original
version belongs. This dataset must currently exist in the catalog.
TODSN= Required, positional parameter. Specifies the name of the dataset into which
the version is to be cataloged. This dataset must currently exist in the catalog.
FROMVERS= Optional parameter. Indicates the version to be copied into the TODSN
dataset. The default is version 1.
TOVERS= Optional parameter. Indicates the version to be multi-cataloged. The default is

version 1.
PASSWORD Required if a password has been defined for the from DSN. Valid entries are 1-
8 alphabetic characters enclosed in apostrophes.
8–76 User Guide

DYNCAT Commands
.gen Optional parameter. Specifies the absolute or relative generation of the

version. If omitted, relative generation 0 is assumed.
.rgen Optional parameter. Indicates the position of the generation in TODSN. If

omitted, relative generation 0 is assumed.
Example
Assume that version 2 of dataset 'PAYROLL' contains volsers PAY001 and

PAY002.
// JOB MCAT
MCAT FROMDSN='PAYROLL' FROMVERS=2 TODSN='TEST.PAYROLL'
/*
/&
In the previous example, MCAT causes version 1 of 'TEST.PAYROLL' to be

added to the Catalog. This version will reside on volumes PAY001 and PAY002.
Following is an example of the MCATAL format:
// JOB MCATAL
MCATAL FROMDSN=ARJNDLY,TODSN=ARJNWKLY
MCATAL FROMDSN=ARJNWKLY.(-3),TODSN=ARJNMTH
MCATAL FROMDSN=KPS7063.G207,TODSN=KPSSAVE
/*
/&
OWN Command
Use the OWN command to establish or change the Catalog ownership code.
OWN id='ownership code'
ID= Required parameter. Specifies the ownership code to be associated with this
Catalog. Valid entry is a 1- to 16-character ownership code enclosed in
apostrophes.

DYNCAT Commands
Example
The following example establishes the ownership code TEST CATALOG.
// JOB CATALOG OWNERSHIP

OWN id='TEST CATALOG'
/*
/&
RENAME Command
Use the RENAME command to assign a new name to an entire dataset or to

assign a new name and version number to a specific version of a tape dataset.
Individual versions of disk datasets may not be modified with RENAME.
RENAME OLDNAME='old data set name' NEWNAME='new data set name'
[ ALL| {OLDVERS=nnn|VOLser=xxxxxx }NEWVERS=nnn ]

[ MF=RESET ]
[ PASSWORD='password' ]
OLDNAME= Required parameter. Specifies the dataset to be renamed. Valid entry is:
NEWNAME= Required parameter. Specifies the new data set name. Valid entry is:
Note:
When renaming all the versions of a dataset (ALL operand), the 'new data
set name' must not already exist in the Catalog.
When renaming just one version of a dataset (OLDVERS or VOLSER

operand), the new data set name must already exist in the Catalog.
PASSWORD= Required parameter if old name DSN was defined with a password. Valid
entries are:
1- to 8-alphabetic characters enclosed in apostrophes.
8–78 User Guide

DYNCAT Commands
ALL Optional parameter. Specifies that all versions of the old dataset be renamed.
NEWVERS, OLDVERS and VOLSER must not be present when ALL is specified.
The data set name specified by NEWNAME must not exist in the Catalog when
the ALL operand is used.
When ALL is specified, the name of the entire dataset is changed. If not, a
version is moved from one dataset to another.
MF=RESET Optional parameter. Automatically resets the prototype record of the AMF
dataset to indicate 001 as the next output data set name to be used as file one
of the tape to be created. Renames all existing members of the AMF group to a
new name, as specified by the NEWNAME parameter.
When MF=RESET is used, the data set names specified for both OLDNAME and
NEWNAME must contain three asterisks (***) identifying the position for the
numeric AMF numbers in the old and new data set names.
NEWVERS, OLDVERS and VOLSER must not be present when MF=RESET is

specified.
NEWVERS= Optional parameter. Specifies the new version number to be assigned to the
renamed version. Valid entry is:
a 1- to 3-digit number in the range 0 - 999.
OLDVERS= Optional parameter. Specifies the version of the dataset to be renamed.

OLDVERS and VOLSER are mutually exclusive. Valid entry is:
a 1- to 3-digit number in the range 0 - 999.
VOLser= Optional parameter. Specifies the volume serial number of the first or only
volume of the dataset to be renamed. VOLSER and OLDVERS are mutually
exclusive. Valid entry is a 1- to 6-character volume serial number. (May be
enclosed in parentheses.)
Examples
Examples follow:
// JOB RENAME CA Dynam DATA SETS

RENAME OLDNAME='DSN1' NEWNAME='DSN2' ALL X
RENAME OLDNAME='DSN3' NEWNAME='DSN4' OLDVERS=3 NEWVERS=13 Y
RENAME OLDNAME='DSN5' NEWNAME='DSN6' VOLSER=7528 NEWVERS=7 Z
RENAME OLDNAME='PAY***' MF=RESET NEWNAME='PAYDEC***' [
/*
/&

DYNCAT Commands
1 This renames dataset DSN1to DSN2. The relative generations remain the
same under the new name.
2 This renames Version 3 of DSN3 to Version 13 of DSN4.
3 This specifies that the version of DSN5, of which volume 7528is the first or
only volume, is to be renamed to DSN6 Version 7.
4. This renames the multifile dataset "PAY***" to "PAYDEC***"and resets

next multifile dataset to "PAYDEC001."
RESTORE Command
Use the RESTORE command to recover the CA Dynam Catalog from the
backup file created by the BACKUP function. This may be done in two different
ways:
To Restore Specify And Operand
A mirror-image of the Catalog RESTORE (none)
Logically reorganize the Catalog RESTORE REORG
There are two formats for the RESTORE command:
RESTORE (no options)
RESTORE REORG [ CISIZE=nnnn ]

[ DATASETS=nnnnnn ]
[ id='text' ]
[ MERGE ]
[ SHARE= {YES|NO|VSELOCK } ]
[ SORTKEYS=nnnnnn ]
[ VOLUMES=nnnnnn ]
The RESTORE function reads the file using the file name IJSYSBK. The logical
unit used is SYS005.
A RESTORE REORG must be scheduled periodically to assure optimum

performance and maintain the integrity of the catalog. It is recommended that
this be performed once a week.
8–80 User Guide

DYNCAT Commands
Using RESTORE without Operands
If you do not specify any operands for the RESTORE command, the restored
Catalog will be physically identical to the backup copy created through the
BACKUP command. This function may be used to move the Catalog from one
device type to another, or from one extent to another. If the Catalog is
destroyed due to disk I/O failure, this physical restore may be used in
conjunction with the Audit Trail facility Catalog recovery feature to
automatically bring the Catalog up-to-date.
The physical RESTORE function runs very quickly since no analysis of the file
need be done. The Catalog need not be initialized before the physical restore is
performed since the records are restored exactly as they previously had
existed.
Note: The physical RESTORE function may be used to enlarge the Catalog,
change the extents of the Catalog, move the Catalog to a different device
type, or restore the Catalog to its previous location. It may not be used to
change Catalog characteristics as specified when the Catalog was initialized.
Using RESTORE with Operands
If you specify the RESTORE command and the REORG operand, DYNCAT both
restores and logically reorganizes the Catalog from the tape copy produced by
the BACKUP function. This tape contains sufficient information to perform
either function.
The Catalog produced by RESTORE REORG will be logically identical to the

Catalog as it was backed up, but will be physically quite different. Index blocks
will be rebuilt, free space will be concatenated, and disk utilization will be
optimized. In addition, if any logical errors are encountered during the
reorganization, they will be corrected and error messages issued to the
SYSLST device to document the actions taken.
Unlike the physical RESTORE function, the RESTORE REORG function allows
the user to modify the characteristics of the Catalog as originally established
through the INITIAL command and to MERGE one Catalog into another.
Ordinarily, the DATASETS, VOLUMES, and SORTKEYS operands would not be

submitted for a RESTORE REORG, since this information is present on the
BACKUP tape and RESTORE REORG will use it to optimize performance
dynamically. However, they are supported as overrides, if desired. Any that
are submitted will override those already in effect in the Catalog. Any that are
omitted will be taken from the BACKUP tape.
If you inadvertently specify options with RESTORE, but do not specify REORG,
the options are ignored and a RESTORE is done as if no operands were
supplied.

DYNCAT Commands
CISIZE= Optional parameter. Specifies the control interval size for the Catalog being
initialized. This value should be chosen to optimize track utilization on the
DASD device where the Catalog will reside. The value must be a whole number
multiple of 1024; valid entries are 1024, 2048, 3072, or 4096.
The default is 1024.
DATASETS=, VOLUMES=, SORTKEYS=

These three operands may be used to override the values found on the
BACKUP tape if it is necessary to reserve additional space for a larger Catalog
than that being restored. As a general rule, however, they should not be
specified since RESTORE REORG was written to be self-optimizing. Valid entry
is a 1- to 6-digit numeric value indicating the number of records of the
specified type expected to be in the Catalog.
ID= Optional parameter. Establishes a Catalog owner. A valid entry is a 1- to 16-

character literal enclosed in apostrophes.
Only in very exceptional circumstances should this specification be

changed after once having been provided.
The default is the specification from the Catalog as backed up.
MERGE Optional operand. Causes RESTORE REORG to skip the Catalog initialization
phase and simply merge the contents of the input tape into the existing
Catalog as found. May be used to merge two existing CA Dynam Catalogs.
If a MERGE operation is to be done, first a RESTORE REORG of one Catalog

should be done to build the Catalog with its desired characteristics (including
specification of additional index area to accommodate the merged Catalog).
Then the second Catalog should be added to the first through a second
RESTORE REORG using the MERGE operand.
Note: Duplicate data set name entries are not resolved during a MERGE
function. If a data set name on the MERGE tape already exists in the Catalog,
its versions will just be added as the first ones to the dataset in the Catalog.
PASSword= Optional parameter. Specifies the Catalog password. A valid entry is a 1- to 8-

character literal enclosed in apostrophes.
REORG Optional parameter. Indicates that a reorganizing restore is desired.
SHARE= Optional parameter. Indicates whether the Catalog is to be shared between

two real or virtual systems. Valid entries are:
YES Indicates that the Catalog is to be shared.
8–82 User Guide

DYNCAT Commands
VSELOCK Indicates that the Catalog file is shared, and enqueuing is

done using the VSE external lock file rather than internal
CA methods.
NO Indicates that the Catalog is not to be shared.
Example
In the following example, the Catalog will be restored and reorganized, and
the password will be changed to 'SECURITY'.
// JOB INITIAL AND REORG CA Dynam CATALOG

// TLBL IJSYSBK,'CA Dynam BKUP'
RESTORE REORG PASSWORD='SECURITY'
/*
/&
Note: You may use RESTORE REORG to increase or decrease the size of the
Catalog to a different extent, device, or device type, modify Catalog
characteristics, improve access performance, and correct any Catalog errors
which may have been noted on the BACKUP function.
In most cases where a problem with the Catalog is indicated, recovery from
audit is not necessary. The RESTORE REORG function was designed in part to
diagnose and correct Catalog errors. If an error is suspected, you should run a
BACKUP and RESTORE REORG, followed by a SCRATCH function. If the
sequence completes successfully, the integrity of the Catalog can be assured.
If you attempt a RESTORE REORG which would result in changing the SHARE
option of the Catalog from SHARE=YES or SHARE=VSELOCK, to SHARE=NO, a
message will be issued warning you that this is being done.
SCRATCH Command
Use the SCRATCH command to return eligible tapes to the scratch pool and
perform internal housekeeping in the Catalog. It should be run at least once
per day. Remember to always perform a BACKUP immediately prior to
performing the SCRATCH.
If you specify the SCRATCH command without any operands, DYNCAT will
produce a group of dataset reports as a by-product. It will also periodically
dequeue the Catalog and wait for a short interval to allow concurrent
processing in other partitions and CPUs to continue. SCRATCH needs a work
file to perform its functions.

DYNCAT Commands
For more information about sample reports produced using the SCRATCH
command, see the chapter "CA Dynam Report Examples."
SCRATCH [ NODEQ ]
[ NOLIST ]
[ VAULT= {YES|NO } ]
NODEQ Optional operand. Eliminates periodic dequeues during the SCRATCH run.
Catalog buffers need not be refreshed, thereby shortening the run time.
Note, however, that if NODEQ is specified, almost all other tasks that share
the Catalog or Audit files can be expected to wait until SCRATCH is complete.
NOLIST Optional operand. Creates only SCRATCH tape listings -- not regular dataset
reports.
VAULT= Optional operand.
YES Specifies that a volume residing in a vault other than the

main tape vault will be eligible for scratch. Once an entire
volume becomes eligible for scratch, a Vault Movement
Exit Report will show the volume moving to the main tape
vault.
NO This is the default. Specifies that a volume must reside in

the main tape vault to be considered eligible for scratch.
Note: The main tape vault is always vault 'A'.
The following tapes will be made available as scratch tapes:
Tapes that have exceeded all retention criteria -- that is, tapes whose
cycle retention and/or date retention and/or as-of-date cycle retention has
passed.
All tapes created under data set names locked for output.
All tapes created under $TEST job processing.
All tapes opened for output, but never closed, which have been open
longer than the number of hours specified in the DYNAM/T option record.
The default is 8 hours.
All work tapes not released by TLBL or Catalog option that have exceeded
the standard work tape retention.
All tapes scratched by RERUN option.
8–84 User Guide

DYNCAT Commands
The following reports are produced by the SCRATCH function:
Tapes scratched by this function, listed in volume serial number sequence.
Exceptions encountered.
All tape datasets with their associated versions in alphabetic sequence. An

asterisk (*) marks versions eligible for scratching but which are not
scratched because of restrictions (locked, permanent vault, not DOS
version, not in Vault A).
All active tape volumes in alphanumeric sequence.
All tapes in SCRATCH status.
Status Report for the Catalog.
Vault Movement Exit list (if VAULT=YES is specified).
For more information about the report format and report fields, see Utility
Reporting Program - TDYNUTL in the chapter "Supporting Tape File
Management."
Example
An example follows:
// JOB SCRATCH TAPES

// ASSGN SYS006,280
// TLBL IJSYSBK,'CA Dynam BKUP'
// ASSGN SYS001,150
// DLBL WORK1,'WORKAREA',O,SD DISK WORK FILE FOR SCRATCH
BACKUP FIRST BACKUP THE CATALOG
SCRATCH THEN RUN SCRATCH
/*
/&

DYNCAT Commands
SCRPOOL Command
Use the SCRPOOL command to define scratch tapes in the CA Dynam Catalog
without initializing the tapes. Characteristics of existing SCRATCH volumes
may also be modified by the SCRPOOL command.
SCRPOOL VOLser=(xxxxxx,xxxxxx,...,xxxxxx)
[ CLean= {nnn|YES } ]
[ FIRSTVOL=nnnnn ]
[ LASTVOL=nnnnn ]
[ OWner=cc ]
[ VTAPFILE='location' ]
[ VTAPLOC='filename' ]
VOLser= Required parameter. Specifies the volume serial numbers to be added to the
Catalog or modified. Valid entries are 1- to 6-character volume serial numbers
enclosed in parentheses and separated by commas.
A maximum of 10 volumes may be added/modified per SCRPOOL statement.

cumulative total that is retained in the Catalog until the tape is reinitialized.
Valid entries are:
YES - indicates that the tape has been cleaned and resets the error counters in
the volume record. The CLEAN threshold is not modified.
CLEAN=YES should be specified if the volume has been cleaned without having
been reinitialized.
DENsity= Optional parameter. Specifies the recording density for this tape. Valid entries
are:
800 for 800 BPI
1600 for 1600 BPI
6250 for 6250 BPI
8–86 User Guide

DYNCAT Commands
08E for tape cartridge (3490E data compaction buffered write)
08M for tape cartridge (3590 data compaction buffered write)
08ME for tape cartridge (3590E data compaction buffered write)
08MH for tape cartridge (3590H data compaction buffered

write)
08W for tape cartridge (3592 data compaction buffered write)
08WE for tape cartridge (3592E data compaction buffered write)

buffered write)

mode)

write)

DYNCAT Commands
28E for tape cartridge (3490E data compaction unbuffered

write)
28M for tape cartridge (3590 data compaction unbuffered

write)
28ME for tape cartridge (3590E data compaction unbuffered

write)
28MH for tape cartridge (3590H data compaction unbuffered

write)
28W for tape cartridge (3592 data compaction unbuffered

write)
28WE for tape cartridge (3592E data compaction unbuffered

write)

unbuffered write)
NO removes the recording density specification.
FIRSTVOL=nnnnnn Optional parameter. Specifies the first volume in a range of volumes to be

defined as scratch tapes.
LASTVOL=nnnnnn Optional parameter. Specifies the last volume in a range of volumes to be

defined as scratch tapes.
LENgth= Optional parameter. Specifies the length of this tape. Valid entries are:
XS Extra short
S Short
MS Medium short
M Medium
8–88 User Guide

DYNCAT Commands
ML Medium long
L Long
OWner= Optional parameter. Specifies the tape ownership code to be assigned to this
tape. If selected, this tape may only be used for datasets with matching
ownership codes. Valid entry is a 1- or 2-character ownership code.
VIRTape= Optional parameter. Specifies whether the tape will be defined as a virtual
scratch tape. This parameter is mutually exclusive with the VTAPLOC and
VTAPFILE parameters. If this parameter is specified and the tape currently has
associated virtual tape information, that information will be removed from the
catalog.
NO The tape will not be defined as a virtual scratch tape.
VTAPE The tape will be defined as a VTAPE scratch tape.

CA Dynam/T will use the default VTAPE file name and
location defined in the DTVIRT system option record at
open time.
FTAPE The tape will be defined as a FakeTape scratch tape.

CA Dynam/T will use the default FakeTape file name
defined in the DTVIRT system option record at open time.
VTAPFILE= Optional parameter. Specifies the virtual file name. This parameter is mutually
exclusive with the VIRTAPE parameter. The virtual file name must be enclosed
in apostrophes and contain the literal 'VOLSER', which will be automatically
replaced with the volser of the virtual tape being opened. If this parameter is
specified, VTAPLOC must also be specified.
The maximum length of a VSAM VTAPE file name is 7 characters. For an

external VTAPE file, the specified virtual file name can contain up to 200
characters and must contain the the fully qualified location and name of the
virtual file. For FakeTape, the specified virtual file name can contain up to 127
characters.
For example,
For a VSAM VTAPE file:
VTAPFILE='VOLSER'
For an external VTAPE file:
VTAPFILE='C:\VTAPE\VOLSER.AWS'

DYNCAT Commands
For a FakeTape file:
VTAPFILE='FAKETAPE.FILE.VOLSER'
VTAPLOC= Optional parameter. Specifies that the tape will be defined as a virtual scratch
tape. This parameter is mutually exclusive with the VIRTAPE parameter. If this
parameter is specified, VTAPFILE must also be specified. The following
operands must be enclosed in apostrophes.
FTAPE The virtual file is a FakeTape file.
VSAM The virtual file is a VTAPE file in VSAM. The LOC=

parameter on the VTAPE START command issued by
CA Dynam/T will be set to VSAM .
Ipaddr:port The virtual file is an external VTAPE file. The LOC=

parameter on the VTAPE START command issued by
CA Dynam/T will be set to the specified IP address and
port number.
Example
The following example places three volume serial numbers in the Catalog.
Each one is to be flagged for cleaning after 50 tape errors. They are long tapes
and are to be written at 6250 BPI.
// JOB ADD TAPES TO SCRATCH POOL

SCRPOOL VOLSER=(601,602,603) CLEAN=50 LEN=L DENSITY=6250
/*
/&
STATUS Command
Use the STATUS command to display the current Catalog file utilization
statistics on SYSLST.
STATUS (no associated operands)
The display contains the following information:
Number of:
− Tape volumes in the Catalog
− Tape volumes containing active datasets
− Active versions of datasets recorded in the Catalog
8–90 User Guide

DYNCAT Commands
− Tape volumes available for use as SCRATCH tapes
− Datasets recorded in the Catalog
Percentage of:
− Available space in the Catalog
− Reserved index area in the Catalog used
− All space in the Catalog used
− All space in the Catalog used when Catalog was most full
Example
An example follows:
// JOB DISPLAY CATALOG STATUS

STATUS
/*
/&
VAULT Command
Use the VAULT command to establish or delete vault descriptions for any or all
vaults to be used. You may also assign or delete storage slots to be used for a
particular vault location. These descriptions are used for reporting purposes
only.
VAULT VLTloc=c [ DESC='description' ]

[ SLOTS=(x1,y1)|DELETE=(x1,y1) ]
VLTloc= Required parameter. Identifies a vault location. Valid entry is:
a 1-alphabetic-character vault ID (A to Z).
DESC= Optional parameter. Provides or deletes the description of the vault location
identified in VLTloc. Valid entries are:
'description' 100 characters enclosed in apostrophes which describe

the vault.
' 'one space enclosed in apostrophes to delete the vault description.
SLOTS=(x1,y1), DELETE=(x1,y1)
Optional parameters. Assigns or deletes ranges of slot numbers for the
identified vault.

DYNCAT Commands
x Identifies the range's starting number.
y Identifies the range's ending number.
x1,y1 Specifies the range of slot numbers.
Valid entries are:
1 to 5 numerics - for the start and end number of a range.
Up to ten ranges of slot numbers may be defined or deleted, accounting for a

maximum of 65,535 slots. Each slot range defined or deleted requires a
unique VAULT VLTLOC= statement.
You may not define slot numbers for vault A.
If slot ranges are added/deleted/changed, this will signal to TDYNVLT to run a

VERIFY automatically at its next execution. However, the automatic VERIFY
cannot be run if a TDYNVLT conversion function was requested.
Example
An example follows:
// JOB DESCRIBE VAULTS

VAULT VLTLOC=A DESC='TAPE LIBRARY' X
VAULT VLTLOC=B DESC='TAPE VAULT AT BANK' SLOTS=(1001,1250) Y
VAULT VLTLOC=B DESC='TAPE VAULT AT BANK' SLOTS=(2001,2250)
VAULT VLTLOC=B DESC='TAPE VAULT AT BANK' SLOTS=(3001,3250)
VAULT VLTLOC=B DELETE=(1001,1250) Z
VAULT VLTLOC=B DELETE=(2001,2250)
VAULT VLTLOC=B DELETE=(3001,3250)
VAULT VLTLOC=B DESC=' ' [
/*
/&
1 This establishes a description for the tape library itself. Note that vault A is
always the tape library.
2 This establishes a description for vault B, which is "TAPE VAULT AT BANK".

Vault B has three cabinets, each containing 250 slots.
3 This deletes the slot numbers defined in example 2.
4 This deletes vault B's description of 'TAPE VAULT AT BANK' as defined in

example 2.
8–92 User Guide

DYNCAT Commands
VTOC Command
Use the VTOC command to create and delete the VTOC indexes used by the
CA Dynam/D VTOC Management. Each VTOC index is a small disk file
containing an index to the entries in the unmodified VTOC for the device.
These files have a standard name of 'DYNAM.VTOC.INDEX'.
VTOC {INITIAL|DELETE } VOLser=xxxxxx
INITIAL Creates the VTOC indexes used by CA Dynam/D VTOC Management.
DELETE Deletes the VTOC indexes used by CA Dynam/D VTOC Management.
Note: INITIAL and DELETE are mutually exclusive; one is required.
VOLser= Required parameter. Indicates the DASD device upon which the VTOC index is
to built or from which the VTOC index is to be removed. Valid entry is a 1- to
6-character volume serial number.
BLDIX Builds the VTOC index used by CA Dynam/D VTOC management.
Using the VTOC INITIAL Function
For performance reasons, we recommend that the VTOC index be located as

near to the VTOC of the volume as possible, ideally on the same cylinder with
the VTOC, immediately preceding it. As a general guideline, the VTOC index
file should be the same size (number of tracks) as the VTOC on CKD devices,
and twice the size (twice the number of blocks) as the VTOC on FBA devices.
The minimum size for the VTOC index is two tracks on CKD and 80 blocks on
FBA. The minimum size for the VTOC index is four tracks if the CKD device has
more than 32K cylinders.
Using the VTOC DELETE Function
The DELETE function disables CA Dynam-indexed VTOC support for the volume
and removes the index file.
Using the VTOC BLDIX Function
The BLDIX function will rebuild a VTOC index on a particular volume. This
function can only be run if a VTOC index exists on the volume prior to running
the BLDIX function. BLDIX is useful because expired files are deleted. This
function is not mandatory because indexes are automatically rebuilt. For more
information, see Deleting Expired Files in the chapter “Disk File Management.”

DYNCAT Commands
Index File Label Information
The INITIAL, DELETE, and BLDIX functions require that the label information
for the index files be available. We recommend that these labels be placed in
standard labels for ease of reference. CA Dynam/D may not be used to
allocate the VTOC index files. When the INITIAL function creates the files, they
are created with the standard file ID as shown, and with an expiration date of
2099/366.
We recommend that they be made data-secured files also. These files must
never be deleted except with the DYNCAT VTOC DELETE function, or the
results will be unpredictable.
Example
The following jobstream builds CA Dynam VTOC indexes on each of the three
DASD volumes: SYSWK1, 335001, and 337501. Note that the file ID and
expiration date are included in the DLBLs for the three files for documentation
purposes. These labels should be included in standard labels for the same
reason.
// JOB CREATE VTOC INDEX FILES

// DLBL SYSWK1,'DYNAM.VTOC.INDEX',2099/366,SD,DSF
// EXTENT SYS001,SYSWK1,1,0,01,9 * CYL 0 TRKS 1 THROUGH 9 *
// ASSGN SYS001,DISK,3330,VOL=SYSWK1,SHR
// DLBL V335001,'DYNAM.VTOC.INDEX',2099/366,SD,DSF
// EXTENT SYS002,335001,1,0,19,9 * CYL 1 TRKS 0 THROUGH 8 *
// ASSGN SYS002,DISK,3330,VOL=335001,SHR
// DLBL V337501,'DYNAM.VTOC.INDEX',2099/366,SD,DSF
// EXTENT SYS003,337501,1,0,7657,9 * CYL 403 TRKS 0 THROUGH 8 *
// ASSGN SYS003,DISK,3330,VOL=337501,SHR
VTOC INITIAL VOLSER=335001
VTOC INITIAL VOLSER=337501
VTOC BLDIX VOLSER=335001
VTOC DELETE VOLSER=SYSWK1
/*
/&
The standard name 'DYNAM.VTOC.INDEX' overrides whatever is specified by

the user. The selected logical units are used only to open the three files, not to
access them once built. These units must be properly assigned to the devices
described by the DLBL and EXTENT only for the duration of the DYNCAT job,
and may be subsequently assigned elsewhere.
8–94 User Guide

DYNCAT Commands
When initializing a VTOC index with the DYNCAT VTOC function, a label must
be supplied to specify the extent to be used for the VTOC index. The dtfname
used is the same as the volser on which the VTOC index is to be built. If the
first character of the volser is numeric, the dtfname is not valid. The character
'V' may be inserted prior to the volser as the dtfname for the VTOC index
label. For example, for volser = "335000", use "// DLBL V335000,'...". Six-
character dtfnames with a nonnumeric first character are valid.
Once initialized, the VTOC index will be rebuilt at each IPL, or at about 8:00
a.m. each morning automatically. The IXVOPTS macro may be used to change
the time at which the index is automatically rebuilt.
The VTOC INITIAL function results in the automatic deletion of all expired files
created using CA Dynam/D, which are found on the volume, in order to further
improve performance.
If you wish to retain expired files that currently exist, use the DYNUTIL ALTER
command to modify the expiration date of the file before running VTOC
INITIAL. Only expired files created using CA Dynam/D will be so deleted. Other
expired files will be retained until explicitly deleted by the user.

Chapter 9: CA Dynam Reporting Utilities
General Reporting−DYNPRINT
DYNPRINT is the CA Dynam family reporting utility supplied with r5.5 and
above. It lets you report on the CA Dynam Catalog and disk VTOCs. Through
its simple report control language, you can invoke standard reports as well as
compile and execute custom reports.
DYNPRINT is intended to be the basic means of satisfying CA Dynam reporting

needs. It is a replacement for DYNDART, offering substantial performance
improvements and functional advantages. Additionally, it replaces a subset of
certain current CA Dynam reporting utilities.
The DYNPRINT report control language has the following properties:
Supports a number of standard reports, some of which are similar to or

are replacements for utility reports available in previous releases. These
reports cover both disk and tape data sets and draw on data from the CA
Dynam Catalog and from disk VTOCs.
− Standard reports are supplied both as precompiled executable

programs and as source members.
− They may be customized or enhanced to meet individual site

requirements, either on an as-needed or permanent basis.
Allows predefined or inline reports to be compiled and/or invoked. Data

selection criteria may be specified for each selected report, allowing
anything from a single data instance to all occurrences of the data
available on the system to be reported.
All reports are generated using CA Earl, a powerful high-level nonprocedural

reporting language. A subset of CA Earl has been included with CA CIS. It has
all the features and capabilities of CA Earl, except that no access method
support is provided other than through DYNREAD.
DYNREAD is invoked by the CA Earl report programs and provides access to

information contained in the CA Dynam Catalog and system VTOCs and to
services provided by the System Adapter. DYNREAD tailors data requests
according to the selection criteria defined to DYNPRINT. No knowledge of CA
Earl or DYNREAD is required to execute the standard reports as supplied.
Chapter 9: CA Dynam Reporting Utilities 9–1

Note: CA Earl r6.0 added additional parameters to the EARLGEN macro.

AFPOUT, SYSEARL, and SYSPRIN specify a programmer logical unit to be used
for the creation of EARL reports. The default logical units are SYS107, SYS108,
and SYS109. These logical units should be unassigned. If they are not
unassigned, the following message will be issued:
CALR843E INVALID ASSIGNMENT FOR SYSLST OR SYSPRIN
For more information, see CA Earl Generation Macro in the CA Earl Systems
Programmer Guide for details.
Access Methods DYNACC, the Catalog access method used by DYNREAD, includes sequential
processing of the entire Catalog, generic key retrievals, get-next generation
and get-next file capabilities. For more information about DYNACC processing,
see the chapter "Accessing The Catalog."
VTOCAC, the VTOC access method used by DYNREAD, has been supplied to
support read-only shared access (through DYNREAD for CA Earl programs) to
information contained in the VTOCs of all volumes available on your system.
DYNPRINT Control Statements
There are three types of control statements: ACCESS, REPORT, and COMPILE.
To Use
select the data source for the report ACCESS
invoke a precompiled report program REPORT
create customized reports by invoking CA Earl COMPILE
DYNPRINT Statement Syntax
The DYNPRINT report control language is free-form. Statements may appear

anywhere between positions 1 and 71, inclusive. Statements may span
multiple lines; no continuation indicator is required. A single line may contain
multiple statements.
The following rules apply to DYNPRINT statement syntax:
A statement is made up of a command followed by its parameters.
Each optional parameter is made up of a keyword and associated value.

For example, CBUFN=nnnn where:
CBUFN is the keyword

nnnn is a value you supply
9–2 User Guide

Spaces, equal signs, and commas are interchangeable delimiters. A value

that contains any of these delimiters must be enclosed in single quotation
marks (').
Each keyword or value must be wholly contained on one line do not split
an individual keyword, or a value, between lines.
Syntax analysis is performed on all DYNPRINT statements before any

statements are processed. If no serious syntax errors are detected, each
statement is processed in the order in which it was submitted. If any serious
error is found, processing terminates.
ACCESS Command
The ACCESS command defines the data source for the report. It selects the
access method, such as DYNACC or VTOCAC.
ACCESS {CATALOG|VTOC }
Note: CATALOG and VTOC are mutually exclusive parameters.
CATALOG requests that DYNACC access the CA Dynam Catalog.
VTOC chooses VTOCAC for access to disk VTOCs.
By default, DYNPRINT accesses the Catalog. If a VTOC-based report is

required, insert an ACCESS VTOC statement prior to the first VTOC-based
REPORT statement. If subsequent CATALOG reports are required, insert an
ACCESS CATALOG statement following the last VTOC-based REPORT
statement.
REPORT and COMPILE Commands
Use the REPORT or COMPILE command to select the operation to be

performed:
REPORT invokes a precompiled report program. This may be a standard report

or a previously compiled and saved custom report.
COMPILE invokes the CA Earl compiler to process the CA Earl source

statements which immediately follow DYNPRINT control statements.
Depending on the CA Earl compilation options specified, if free from serious
errors, the output may be saved and cataloged or immediately executed. If
immediately executed, the effect of all options specified on the COMPILE
statement is the same as if they had been specified on a REPORT statement.

The only difference between the effect of a COMPILE statement and a REPORT
statement is that COMPILE calls an inline CA Earl compilation prior to
executing the report program.
{REPORT|COMPILE } report-name [ ,BANNER=OFF ]

[ ,CATNM=dtfname ]
[ ,CBUFN=nnnn ]
[ ,DSN=dsn ]
[ ,DVC= {DISK|TAPE|FI } ]
[ ,EROPT=D ]
[ ,FSQ=nnnn ]
[ ,GDG=xxxxxxxx ]
[ ,GEN=nnn ]
[ ,MAXFILES=nnn ]
[ ,MAXLINES=nnnnn ]
[ ,MAXVERS=nnn ]
[ ,MAXVOLS=nnn ]
[ ,MAXRETR=nnnnnnn ]
[ ,PSW=xxxxxxxx ]
[ ,REQ=xx ]
[ ,SELECT= {option[,option..] } ]
[ ,VER=nnn ]
[ ,VOL=xxxxxx ]
[ ,VSQ=nnnn ]
report-name Required parameter. Specifies the report to be invoked. This name is used by
DYNPRINT to derive the name of the report program to invoke and to establish
the default characteristics of the report.
For standard reports, refer to the report documentation for the name and
applicable options. For custom reports, either compiled inline or saved from a
previous compilation, the name is CUSTOMnn, where n is a number between
zero and 99. The associated program name is CUSnn.
By default, all CATALOG custom reports process all data sets in the Catalog in
DSN sequence and all VTOC custom reports process all extents for all data set
names defined in all available VTOCs on the execution system.
BANNER=OFF Optional parameter. Suppresses the DYNPRINT banner for this report.
CATNM=dtfname Optional parameter; valid only for CATALOG reports. Specifies the dtfname for
the Catalog. Defaults to CAICATL.
CBUFN=nnnn Optional parameter; valid only for CATALOG reports. Specifies the number of
Catalog buffers, in a range 3-9999 (defaults to 12).
9–4 User Guide

DSN=dsn Optional parameter; valid only for CATALOG reports. Specifies a specific data
set name to be reported on. May be specified as a generic key, with an '*'
immediately after the last significant character in the name.
DVC= {D|T|F } Optional parameter; valid only for CATALOG reports. Specifies a device class
filter to be placed on the data sets and generations to be reported in certain
reports. Defaults to all data sets.
DISK, or D for DISK data sets
TAPE, or T for TAPE data sets
FI, or F for FI data sets
EROPT=D Optional parameter. Causes the access method to generate snap dumps of
selected data areas for certain types of errors. Operation is access method
dependent. This option is intended for debugging.
FSQ=nnnn Optional parameter; valid only for CATALOG reports on multifile tapes. Selects
the file sequence number of the data set version to be retrieved.
GDG=xxxxxxxx Optional parameter; valid only for CATALOG reports. Specifies the generation
of the data set to be reported on, based upon the OS generation data group
identifier of the generation.
GEN=nnn Optional parameter; valid only for CATALOG reports. Specifies the version of
the data set to be reported on, based on the CA Dynam/D generation number.
MAXFILES=nnn Optional parameter - report dependent.
MAXLINES=nnnnn Optional parameter - report dependent. Usually the maximum lines to be

printed for each individual selected report.
MAXVERS=nnn Optional parameter - report dependent.
MAXVOLS=nnn Optional parameter - report dependent.
MAXRETR=nnnnnnn Optional parameter - report dependent. Usually the maximum number of

logical retrieves to be performed by the access method.
PSW=xxxxxxxx Optional parameter; valid only for CATALOG reports, is the Catalog or data set
password which enables reporting of password-protected data sets.
REQ=xx Optional parameter. Specifies the initial request code to be passed to the
access method. Overrides the default request code for the report. Access
method dependent. Usually only used for custom reports.
SELECT= Optional parameter - report dependent.
SELECT= {option[,option..] }

VER=nnn Optional parameter; valid only for CATALOG reports. Identifies the version
number of the data set to be reported on.
VOL=xxxxxx Optional parameter; for CATALOG reports, identifies the volser or generic
volser to be reported on. For VTOC reports, identifies the volser, generic volser
or CA Dynam/D pool to be reported on. For either type, a generic key value
may be specified by following the last significant character in the volser by an
asterisk.
VSQ=nnnn Optional parameter; valid only for CATALOG reporting on multivolume data
sets. Specifies the volume sequence number of the volume to be reported on.
Selection parameters are optional. If you supply any, each one must contain a
keyword followed by an appropriate numeric or alphanumeric value. If you
omit them, defaults are used to determine the data to be retrieved.
Parameters are dependent on the report specified.
Standard DYNPRINT Reports
Report Types
Basically, there are six different standard reports currently supplied with CA
Dynam. They are divided into catalog-based or VTOC-based report classes.
Catalog-based reports are further subdivided into DSN-entry reports and VOL-
entry reports.
DSN-entry reports access the Catalog sequentially by data set name, and can,
by extension, report on series of the following:
Versions for each data set

Tape volumes or disk extents for each version
VOL-entry reports access the Catalog sequentially by volser (only tape

volumes being supported) and can by extension report on series of files (or
versions of files) resident on each volume. It is the logic of these access paths
which causes some selection keywords to be excluded for each class of report.
To find out which options are supported by given reports, consult the
documentation for that report.
9–6 User Guide

Report Title Program

Name
ACTVFILE Active Catalog Files DYNAF
FILEDEFS Catalog File Definitions DYNFD
FREQUSE File Usage Frequency DYNFQ
SPACEUSE Disk Space Usage Analysis DYNSP
TAPES Tape Inventory Report DYNTA
VTOCS Volume Table Of Contents DYNVT
Report Descriptions
Standard reports are described briefly below. Detailed descriptions of

ACTVFILE, FILEDEFS and FREQUSE appear later in this chapter.
ACTVFILE Lists information about active generations and versions of disk and tape files.
Provides reports in volser, DSN, owner, user-id or system-id order. Data is
retrieved from the Catalog in DSN sequence.
FILEDEFS Reports information about data sets defined in the Catalog. The reports may
display retention data, messages, data set specifications, multifile organization
and others. Data is retrieved from the Catalog in DSN sequence.
FREQUSE Highlights the frequency of use of files on both disk and tape. Reports may be
produced in DSN, days-old, days-unused or average-opens-day sequence.
Data is retrieved from the Catalog in DSN sequence.
For more information about TAPES, see the chapter "Supporting Tape File
Management." For more information about SPACEUSE and VTOCS, see the
chapter "Supporting Disk File Management."
SPACEUSE Highlights the relative efficiency with which disk space is being used. Helps
optimize space utilization and system performance by identifying badly
blocked or allocated files. Data is retrieved from system VTOCs in VTOC
sequence by volume.
TAPES Lists information about data sets on tape. Provides reports of active tapes,
scratch tapes or all tapes. Data is retrieved from the Catalog in volser
sequence.
VTOCS Reports information about disk occupancy. Data may relate to all mounted
volumes, to all volumes in a pool, to generic volumes or to a specific real
volume. One scan of all selected VTOCs can produce multiple reports. Data is
retrieved from system VTOCs in VTOC sequence by volume.

Creating Customized Reports
With DYNPRINT you can modify existing reports, either permanently or as

needed. Additionally, you can create new, custom reports. These may be
saved in object form for repetitive use, or compiled and executed in one job
step for once-only use.
To compile and link a new or customized report program, you may either use
the CA Earl compiler directly or to go through the COMPILE feature of
DYNPRINT. To compile and execute in one step, you must use the COMPILE
feature. DYNPRINT invokes the CA Earl compiler and then executes the
resulting object program, assuming no serious errors are detected by the
compiler.
The CA Earl source programs used to generate the standard report programs
are supplied with DYNPRINT, and can be found on the DYNPRINT library with a
member type of '0' (zero). The source members have the same name as the
object members.
To customize a report, you must update the source book, either with the
existing or a new name. The updated source member could then be compiled
with the CA Earl compiler, linkage edited and cataloged into the execution
library. The program in the execution library must have a name that is known
to DYNPRINT (such as CUS01 or DYNAF) and correspond to an existing report
name keyword (such as CUSTOM01 or ACTVFILE).
For more information about instructions and examples of compiling and

linkage editing CA Earl programs, see the CA Earl documentation.
Once a phase named CUSnn has been cataloged into a library in the DYNPRINT
phase search chain, that report program may be invoked by the REPORT
command using the CUSTOMnn report-name keyword.
You can make use of the SELECT option in any custom report. The SELECT
keyword values defined for all custom reports are:
Value EACSELOP Bit EACSELOP Value
REPORT1 15 1
REPORT2 14 2
REPORT3 13 4
REPORT4 12 8
9–8 User Guide

Value EACSELOP Bit EACSELOP Value
REPORT5 11 16
REPORT6 10 32
REPORT7 9 64
REPORT8 8 128
In addition, SELECT=ALL used with a custom report turns on all EACSELOP

bits. To see how to take account of EACSELOP in your custom report, look at
any of the standard report source books.
To compile and execute the updated program under the control of DYNPRINT,
replace the REPORT command with COMPILE. In all other respects the
DYNPRINT syntax is identical. The source program must then be included or
copied into the job stream immediately following the /* that terminates the
DYNPRINT control statement stream. The DYNPRINT library must be in the
source search list when DYNPRINT is executed and the COMPILE facility is used
and the CA Earl source deck contains a COPY statement.
Example
Compile and execute a simple custom report.
// EXEC DYNPRINT,SIZE=256K
COMPILE CUSTOM01 REQ=SV
/*
USER 'CA INTERNATIONAL, INC' !Top Report Heading
CAICATL: FILE DYNREAD 300 RECORD=3232 !Identifies the Catalog
DEFINE INFOREC 1-3232 X !Defines the function PLIST
COPY DYNINFOE USING INFOREC !Copies data definition
SET DYNRQLEN = DYNINFLN
GET CAICATL
GOTO EOJ CAICATL = 'E'
REPORT 'READ/WRITE ERRORS BY VOLUME' !Report # 1
SELECT DYNRTCOD = 0 AND ! Only successful retrieves
DYGCDVCL = 'TAPE ' ! Only want tapes, not disks
PRINT DYVVOL DYVSTAT DYGCCUU (DYVOOPNS) (DYVOERRS) (DYVIOPNS)
(DYVIERRS) DYVDRINT DYVTCLN DYVDCLN DYVADAT DYVREELS DYVMODE2
REPORT 'ERRORS BY CUU'
SELECT DYNRTCOD = 0 AND ! Only successful retrieves
DYGCDVCL = 'TAPE ' AND ! Only want tapes, not disks
(DYVOERRS > 0 OR DYVIERRS > 0) ! Volumes with errors
CONTROL DYGCCUU DYVOERRS DOWN DYVIERRS DOWN
PRINT DYGCCUU (DYVOOPNS) (DYVOERRS) (DYVIOPNS) (DYVIERRS) DYVDRINT
DYVTCLN DYVDCLN DYVADAT DYVREELS DYVMODE2 DYVVOL DYVSTAT
END
/*
/&

DYNPRINT VSE Operation
DYNPRINT requires a minimum VSE execution size of 256K and approximately

256K of partition GETVIS. It uses System Adapter services, so CA Dynam must
be active and enabled for the execution partition. All files required by CA Earl
must be assigned and have label information.
The library into which DYNPRINT is installed must be in the phase search chain
at execution time. To run reports that access the VTOCs, CA Dynam/D must
be active and enabled. If you want to compile CA Earl Catalog reporting
programs, the installation library must be in the source search chain also.
DYNPRINT reads input statements from SYSLOG if executed from the console,
or SYSIPT if executed from within a job stream. SYSIPT may be assigned to a
card reader, magnetic tape unit or DASD. Input must consist of fixed
unblocked 80 or 81 byte records. Printed output is sent to SYSLST. One or
more report control statements must be supplied. Input is terminated by
either a null line or /* from SYSLOG and a /* on SYSIPT.
Examples
Generate a standard report - no compilation needed.
// JOB DYNPRINT
// LIBDEF PHASE,SEARCH=LCL.DYNAM55
// DLBL SORTIN1,'CA EARL HIT WORK FILE',0
// EXTENT SYS002,SYSWK1,1,0,1,30
// DLBL SORTWK1,'SORT WORK FILE',0
// DLBL WORK1,'SRAM.WORK.FILE',0
// DLBL SORTOUT,'CA EARL SORTED HIT FILE',0
// ASSGN SYS001,DISK,VOL=SYSWK1,SHR
// ASSGN SYS007,UA
// ASSGN SYS008,UA
// ASSGN SYS009,UA
REPORT ACTVFILE
/*
/&
9–10 User Guide

Compile and execute a custom report.
// JOB DYNPRINT
// LIBDEF SOURCE,SEARCH=(LCL.USERLIB,LCL.DYNAM55)
// DLBL EARLOBJ,'CA EARL OBJECT WORK FILE',0
// DLBL IJSYS01,'CPU--.==.SYS001.WORK',,SD
// DLBL SORTIN1,'CA EARL HIT WORK FILE',0
// DLBL SORTWK1,'SORT WORK FILE',0
// DLBL WORK1,'SRAM.WORK.FILE',0
// DLBL SORTOUT,'CA EARL SORTED HIT FILE',0
COMPILE CUSTOM01
/*
...
... CA EARL source program
...
/*
/&

Compile and catalog custom report - no execution.
// JOB DYNPRINT
// LIBDEF PHASE,CATALOG=LCL.USERLIB
// DLBL IJSYSLN,'CPU--.==.SYSLNK.WORK',,SD
// EXTENT SYSLNK,SYSWK1,1,0,1,30
// ASSGN SYSLNK,DISK,VOL=SYSWK1,SHR
// OPTION CATAL
COMPILE CUSTOM01
/*
OPTION SAVE=CUS01
...
... CA EARL source program
...
/*
// EXEC LNKEDT
/&
9–12 User Guide

Compile and catalog standard report - no execution.
// JOB DYNPRINT
// LIBDEF PHASE,CATALOG=LCL.USERLIB
// DLBL IJSYSLN,'CPU--.==.SYSLNK.WORK',,SD
// EXTENT SYSLNK,SYSWK1,1,0,1,30
// ASSGN SYSLNK,DISK,VOL=SYSWK1,SHR
// OPTION CATAL
COMPILE ACTVFILE
/*
OPTION SAVE=DYNAF
COPY DYNAF
/*
// EXEC LNKEDT
/&
DYNREAD

The DYNREAD Interface
DYNREAD is the user module supplied with DYNPRINT. It is used by all

programs operating under DYNPRINT control to access data from the CA
Dynam Catalog, disk VTOCs and to obtain access to CA Dynam System
Adapter services. In order to create your own custom or as-needed reports,
you need to understand how to use it.
DYNREAD operates as a single interface between the CA Earl program and the
various service providers. The CA Earl program, CA Earl runtime routines and
DYNREAD communicate with each other through two data areas. These are the
first two parameters passed by CA Earl to a file module. They are the function
parameter list, also referred to by CA Earl as the record area, and the
communications area. The first eight bytes of the function parameter list
contain the function code and indicate the service required.
On entry, DYNREAD analyzes the function code and invokes the service
provider in the appropriate manner, passing the function parameter list
according to the conventions supported by the service provider.
Upon return, DYNREAD analyzes the function return code and sets indicators in
the form required by CA Earl to indicate whether the operation succeeded.
These indicators and other return information maintained by DYNREAD are all
contained in the CA Earl/DYNREAD communications area. While it isn't
required for CA Earl to analyze or process the CA Earl/DYNREAD
communications area, a CA Earl-language definition of this area is supplied
with DYNPRINT and is called EARLCOMM.
The version of CA Earl supplied with CA Dynam does not support the use of
any user modules other than DYNREAD. Nor does this version of CA Earl allow
access to, or creation of, any data files other than through DYNREAD. If you
have the fully functional version of CA Earl, then these restrictions do not
apply to you. In all other respects the functioning of the CA Earl version
supplied with DYNPRINT is identical to that of the fully functional version.
DYNREAD is invoked as a standard CA Earl file module in the following

manner:
filename: FILE DYNREAD 300 RECORD = plist-size

..
..
GET filename
When CA Earl is invoked under the control of DYNPRINT, and DYNREAD is

invoked by the CA Earl program with a function code equal to spaces,
DYNREAD checks to see whether a request has been generated by DYNPRINT
from report control statements. If so, DYNREAD copies the DYNPRINT request
into the function parameter list area and uses it for processing as if it had
been passed from the CA Earl program.
9–14 User Guide

When DYNREAD is invoked by a CA Earl program executing under the control

of DYNPRINT, DYNREAD checks for the existence of a DYNPRINT CA Earl report
control block and if present, moves it into the EARLCOMM area. For more
information about the fields involved, see the EARLCOMM copybook.
The first eight bytes of the function parameter list are the DYNREAD function
code and identify the function to be performed. This may be a call to a data
access module such as DYNACC or VTOCAC, or a CA Dynam System Adapter
function.
The DYNREAD functions supported are listed in the table below. Each function
has the following items:
A separate parameter list layout
A CA Earl source copybook
Functions of DYNREAD
Briefly, the purpose of each function is as follows:
Function Parameter List Description

Name Name
DASDCALC DASDCALE Device-specific DASD capacity calculation
DATEPROC DATEPROE Date conversion and calculation
DYNAM/D DDPARMSE CA Dynam/D profile and configuration

options
DYNINFO DYNINFOE Invoke DYNACC (For more information, see

the chapter "Accessing The Catalog.")
MESSAGE MESSAGEE Write system message
OBTAIN OBTAINE Obtain operating system information
VTOCINFO DYNVTOCE Invoke VTOCAC
Refer to the documentation imbedded in each copybook for a more detailed

description of the input required and information returned.

Reporting on the Catalog

CA Dynam supplies three standard, precompiled reports for reporting on tape
and disk files recorded in the CA Dynam Catalog. The three reports are:
"Active Catalog Files" - ACTVFILE
"Catalog File Definitions" - FILEDEFS
"File Usage Frequency" - FREQUSE
The ACTVFILE report lists information about active generations and versions of
disk and tape files. It prints reports in volser, DSN, owner, user-id or system-
id order. Data is retrieved from the Catalog in DSN sequence.
The FILEDEFS report provides information about data sets defined in the
Catalog. The reports may display retention data, messages, data set
specifications, multifile organization and others. Data is retrieved from the
Catalog in DSN sequence.
The FREQUSE report highlights the frequency of use of files on both disk and
tape. Reports may be produced in DSN, days-old, days-unused or average-
opens-day sequence. Data is retrieved from the Catalog in DSN sequence.
To enhance their capabilities, several options are available for each of these
reports. Complete descriptions are provided on the following pages.
Active Catalog Files−ACTVFILE
The ACTVFILE report is a standard, catalog-based, DSN-entry DYNPRINT

report supplied with CA Dynam. It focuses only on active files and versions
under Catalog control. ACTVFILE ignores inactive files and versions on the
requested device class. How the files are defined in the Catalog is irrelevant.
Specific features let you do the following tasks:
Print the report in five different sort orders, including various

administrative fields as well as file-id and volser.
Include tape files, disk files, or both.
For generation-type files, report on all, or a particular number of, versions.
Report on any CA Dynam Catalog.
ACTVFILE is based on the older TDYNUTL LIST DSN=ALL report. But, it is more
flexible and enables you to produce several reports from a single scan of the
Catalog.
9–16 User Guide

Report Samples For more information about samples of active catalog files, see the chapter
Invoking the Report
Use the following DYNPRINT command sequence to invoke ACTVFILE:
ACCESS CATALOG
REPORT ACTVFILE [ options ] or REPORT ACTIVEFILES [ options ]
Options for ACTVFILE or ACTIVEFILES:
[ BANNER ]
[ CATNM ]
[ CBUFN ]
[ DSN ]
[ DVC ]
[ EROPT ]
[ PSW ]
[ MAXLINES ]
[ MAXRETR ]
[ MAXVERS ]
The MAXVERS and SELECT options are described here. For more information
about all other ACTVFILE options and their application, see REPORT and
COMPILE Commands.
MAXVERS Option The MAXVERS option specifies the maximum number of versions to be
reported on for each (generation-type) file. If MAXVERS=1 is given, only the
most recent version of each file is reported.
SELECT Options The SELECT options for ACTVFILE are all sort-order options. Any or all of
them may be used, to produce up to five reports from one command. They
are:
FIDVER Files are sorted on file-id/version. This is the default option if the SELECT
keyword is omitted.
OWNERID Files are sorted on owner-id/file-id.
SYSTEMID Files are sorted on system-id/file-id.
USERID Files are sorted on user-id/file-id.
VOLSER Files are sorted on volser/file-seq/file-id. For disk files, the second sort
variable is set to 0, so that disk files are sorted on file-id only within each
volume.

SELECT=ALL Prints all five reports.
You can nearly duplicate the TDYNUTL LIST DSN=ALL report by invoking
ACTVFILE with:
REPORT ACTVFILE DVC=TAPE
Source Code for ACTVFILE Report
The CA Earl source for the ACTVFILE report is CA Dynam’s library member
DYNAF.0.
VLT Shows the vault where the file presently resides. This item is only meaningful,
and only reported, for tape files.
VOL For tape files this is the sequence number of the volume relative to the start of
the multivolume set (if any). It may not be the same as the volume's
sequence number relative to the start of the file being reported on.
For disk files it is the sequence number relative to the file.
FSQ/EXT For tape files this is the file sequence number, that is, the sequential position
of the file in the multifile set. It may differ from the sequential position of the
file relative to the tape volume being reported on.
For disk files it is the extent sequence number of the first of the file's extents
on the volume. This is found by counting the number of extents registered for
the file in the Catalog, starting from zero. For sequential files it is normally the
same as the true extent sequence number registered in the VTOC.
OW/SY/US These are administrative fields that you can define in the Catalog for each file.
They are blank by default. They must have been previously defined for the
associated sort orders to have any value.
MSG This field can contain one of three texts:
MF if the file is part of a multifile set
WRK if the file is defined with the "W" option (work file)
LCK if the file is defined with the "L" option (read-only)
These conditions are tested in the order shown above and the last one
satisfied is reported.
9–18 User Guide

Catalog File Definitions−FILEDEFS
The FILEDEFS report is a standard, catalog-based, DSN-entry DYNPRINT

report supplied with CA Dynam. It provides overviews of file definitions found
in the CA Dynam Catalog. Information is based strictly on the default settings
for each file, not on characteristics of specific versions of a file. FILEDEFS
prints one line of data per file.
Specific features let you do the following tasks:
Print in seven different formats, emphasizing the category of interest to

you.
Report on tape files, disk files, or both.
Reports are always sorted on file-id.
The FILEDEFS report has no equivalent among the older CA Dynam reporting
utilities. However, the information provided is similar to that reported by the
DYNCAT LISTCAT ALL command. For more information, see Data Set
Attributes. The advantage of FILEDEFS is that you can decide which
categories of information to report on. Each category is summarized on a
single line.
Invoking the Report
Use the following DYNPRINT command sequence to invoke FILEDEFS:
ACCESS CATALOG
REPORT FILEDEFS [ BANNER ]
[ CATNM ]
[ CBUFN ]
[ DSN ]
[ DVC ]
[ EROPT ]
[ PSW ]
[ MAXLINES ]
[ MAXRETR ]
FILEDEFS options and their application, see REPORT and COMPILE Commands.

SELECT Options The SELECT options for FILEDEFS are all report-formatting options. You may
use any or all of them, to produce up to seven reports from one command.
They are:
ALLOCS The disk allocation information for each file is reported.

Only those files defined with disk allocation specifications
in the Catalog are reported on.
CREATE Information is reported about the creation and most

recent changes in the Catalog definition for each file.
MESSAGES The comment and open/close input/output messages, if

any, are reported. Only files having at least one of these
fields filled are reported on.
MULTFILE or MULTIFILE
Items relating to multifile specifications are reported.
Only those files defined in the Catalog with multifile
specifications are reported on.
RETENT All default retention information for each file is reported.

This is the default option if the SELECT keyword is
omitted.
TECHSPEC Technical and administrative specifications are reported

for each file.
VAULTS The vault rotation scheme for each file is reported. Only
those files defined with a vault rotation scheme in the
Catalog are reported on.
SELECT=ALL Prints all seven reports.
FILEDEFS reports look unlike any previous reports. But they can contain nearly
the same information as DYNCAT LISTCAT ALL reports if you invoke FILEDEFS
with this command:
REPORT FILEDEFS SELECT ALL
9–20 User Guide

Source Code for FILEDEFS Report
The CA Earl source for the FILEDEFS report is CA Dynam's library member
DYNFD.0.
EXP. DATE Because files can be disk, tape or FI-type, and the PERM and RETAIN dates
can differ for these categories, no attempt is made to translate these dates to
the appropriate texts. The tape PERM date, 2099/366, appears on the report
as 01/13/2099.
Report Samples For more information about samples of catalog file definitions, see to the
chapter "CA Dynam Report Examples."
File Usage Frequency−FREQUSE
The FREQUSE report is a standard, catalog-based DYNPRINT report supplied

with CA Dynam. It helps you assess how effectively storage is being used. The
information focuses on the age and frequency of use of the files.
Print the report in four different sort orders, highlighting very old, long-
unused, or little-used files.
End the report at an arbitrary number of files, including only the "worst
offenders."
For generation-type files, report on all versions, or only a specified

number.
Include tape files, disk files, or both.

FREQUSE is based on the older DYNFREQ report, but offers extensive

functional advantages. In addition, the algorithms used to compute the data
and sort the files have been improved.

Invoking the Report
Use the following DYNPRINT command sequence to invoke FREQUSE:
ACCESS CATALOG
REPORT FREQUSE [ BANNER ]
[ CATNM ]
[ CBUFN ]
[ DSN ]
[ DVC ]
[ EROPT ]
[ MAXLINES ]
[ MAXRETR ]
[ MAXVERS ]
[ PSW ]
The MAXVERS and SELECT options are described here. For more information
about all other FREQUSE options and their application, see REPORT and
COMPILE Commands.
MAXVERS Option The MAXVERS option specifies the maximum number of versions to be
reported on for each (generation-type) file. If MAXVERS=1 is given, only the
most recent version of each file is reported.
SELECT Options The SELECT options for FREQUSE are all sort-order options. Any or all of them
may be used, to produce up to four reports from one command. They are:
AVOPDAY Files are reported by increasing average number of opens

per day since creation.
DAYSOLD Files are reported by descending days-since-created.
DAYSUNUS Files are reported by descending days-since-last-used.
FIDVER Files are reported on in order of file-id/version. This is the

default option if the SELECT keyword is omitted.
SELECT=ALL Prints all four reports.
By invoking FREQUSE with the following command, you can create a report
that you can compare with a DYNFREQ report:
REPORT FREQUSE MAXVERS=1 DVC=DISK
9–22 User Guide

Source Code for FREQUSE Report
The CA Earl source for the FREQUSE report is CA Dynam's library member
DYNFQ.0.
Report Samples For more information about samples of file usage frequency, see the chapter
VER The version number ascends from 1 (the current version) to steadily higher
numbers (for older versions). This count is relative and only encompasses
existing versions, so it does not show any gaps.
EXTS For disk files this field is the total number of extents on all volumes. For tape
files it is equal to the number of volumes.
VLS This shows the number of volumes on which the file resides.
CREATION DATE The creation date is blank if it was never recorded in the CA Dynam Catalog.
on the DAYSOLD report, files with blank creation dates are ranked at the top.
The age of a file starts at 1 day on the day it is created, and increases by 1
day every night at midnight. Times are not taken into account.
EXP. DATE If the file is considered "permanent", the text --PERM-- is shown. For disk files
this means any date equal to or later than the MANDTE value defined in the
DYNAM/D option record, the normal value being 2099/365. For tape files it is
any date equal to or later than 2099/366.
If the file is not "permanent" but has a value equal to or later than the
appropriate value, the text -RETAIN- is shown. For disk files this is the
AUTODTE value defined in the DYNAM/D option record (normally 2099/364)
and for tape files it is 2099/365.
LAST ACCESS DATE/TIME

If the last access date is blank, no access since creation has been recorded.
Such files show zeros for the last access time, which can be ignored.
DAYS W/O OPEN This is calculated the same way as the age of the file (see the CREATION DATE
description), but using the last access date. If there is no last access date, this
field is computed from the creation date.
TOTAL OPENS This figure always includes one open for the creation of the file.
AVERAGE OPENS This is calculated by dividing the "total opens" by the "days since created" as
PER DAY described above. Since neither of those figures is ever zero, this item tends
to be quite reliable, with values higher than 1 being very unusual.
Occasionally, for often-used files, this figure may be inaccurately low due to
"opens" counter wraparound. Presumably such files will be well-known to
you.

Displaying the VTOC−DYNVTOC

The DYNVTOC program provides a formatted display of the entries in the VTOC
for a specific disk volume or for a pool of disk volumes. The program also
includes the following summary statistics:
Total amount of free space
Total amount of expired space
Total number of VTOC entries
Number of cylinders on volume
Number of tracks per cylinder
Track length
Using DYNVTOC
With DYNVTOC, you control the level of detail for reporting on VTOC contents
to produce the following reports:
Basic VTOC listings assign SYS001 to the desired disk and execute
DYNVTOC.
Detailed VTOC report and for VTOC reporting on a pool of disk volumes or
multiple volumes currently mounted, submit an UPSI JCL statement for
DYNVTOC. DYNVTOC examines the options specified on the UPSI
statement to format these reports.
DYNVTOC should be executed with SIZE=128K specified on the EXEC

statement.
UPSI JCL Statement You may set the UPSI bits according to one of the operands shown below.
Syntax
// UPSI {00000000 }
{10000000 }
{01000000 }
{00100000 }
{00010000 }
{00001000 }
{00000100 }
// UPSI Setting Description
UPSI 00000000 Causes a basic report to be prepared.
UPSI 10000000 Causes all lines displayed in the basic report to be double spaced.
9–24 User Guide

UPSI 01000000 Specifies that a control statement will be input from SYSIPT or SYSLOG to
indicate the sorting sequence and the volume(s) or pool to be displayed.
{VOL=volser|POOL=poolid } [SORTSEQ= {DSN|LOC|CREATE|EXPIRE }]
You must submit a control statement identifying either a VOL=volser or

POOL=poolid.
The VOL, or POOL, parameter is required. It specifies the device(s) to be

included in the listing. The VOL parameter may specify either a real volser
(WORK01), or a generic volser (WORK** for all volsers beginning with
WORK). The POOL parameter causes all of the VOLSERs in the named pool
to be displayed.
Optionally, you may include an operand to indicate the sorting sequence

desired for the listing. Otherwise, DSN is the default sequence.
− DSN specifies data set sequence
− LOC specifies sorting by location
− CREATE or EXPIRE specify sorting by creation date or expiration date,

respectively
If executed from the console, input is from SYSLOG and is terminated by EOB.
Multiple control statements may be input to one DYNVTOC execution, though
the SORTSEQ and VOL= or POOL= parameter must be on the same command
line.
This option requires the use of a small disk work file for sorting. The file name
used to access this file is WORK1, on SYS001.
UPSI 00100000 Causes more detailed information to be provided for each file displayed. May
not be used with UPSI 01 because of format limitations.
UPSI 00010000 Produces a VTOC listing for each disk volume which is assigned by a logical
unit in the partition. This may not be used with UPSI 01.
UPSI 00001000 Causes all free-space lines to be eliminated from the VTOC display. This may
not be used with UPSI 01.
UPSI 00000100 This causes only free-space lines to appear without individual file information.
This may not be used with UPSI 01.
Example
// JOB DYNVTOC WITH DETAIL

// UPSI 00100000
// ASSGN SYS001,140
// EXEC DYNVTOC,SIZE=128K
/&

// JOB DYNVTOC BASIC

// ASSGN SYS001,150
/&
General Report Headings
The following headings appear on all reports created by DYNVTOC:
EXPIRE --PERM-- indicates a date of 2099/366
-RETAIN- means a date of 2099/365
STATUS *-DSF-* identifies a 'data-secured' file.
EXTENT TYPE PRM shows the prime extent
INDX indicates index extent (ISAM)
OVFL means overflow extent (ISAM)
VOL SEQ This position may contain a plus sign (+) to identify sequential files which
have one of the following attributes:
The file is opened but not closed.
Additional extents exist for this file on another disk volume.
Specific Report Headings
The report headings shown below only appear on reports created by DYNVTOC
using the following UPSI statement
// UPSI 01000000
F1=xxx-yy-zz Shows the disk location of the file's format-1 record where:
xxx cylinder address
yy track address
zz record number
BL= Indicates the data block length. Note that this value is valid for ISAM files
only.
RL= Shows the logical record length (ISAM only).
KL= Indicates the key length (ISAM only).
9–26 User Guide

RKP= Identifies the relative key position (ISAM only).
NXTNT= Specifies the number of extents defined for this file.
VOL= Shows the original volume serial number.
DYNVTOC Report Shown below is a sample report and the JCL that produced it.
Example
// JOB DYNVTOC VTOC LISTING

// UPSI 0000
// ASSGN SYS001,140
/*
/&
CA D Y N A M / D V T O C D I S P L A Y DYNVTOC PAGE 1
CA Dynam 7.1 0709YD001 VOLUME - DOSRES CUU - 140 DEVICE - 3380 23 JAN 2008 20:08:58
FILE IDENTIFICATION FILE LOW HIGH ----RELTRK---- VOL -EXTENT- CREATE EXPIRE STATUS
-------------------------------------------- TYPE CCCCC-HH CCCCC-HH START NTRKS SEQ TYPE SEQ -------- -------- --------
--- IPL AND VOL1 RECORDS --- 0 0 0 0 0 1

VSE.SYSRES.LIBRARY SAM 0 1 61 29 1 1859 + 1 PRM 0 12/22/07 -RETAIN-
DOS.LABEL.FILE.FF0161164341.AREA1 62 0 62 29 1860 30 1 PRM 0 12/30/07 -RETAIN-
VSE.POWER.QUEUE.FILE DAM 63 0 63 29 1890 30 1 PRM 0 12/22/07 -RETAIN-
Z9999996.VSAMDSPC.T9A38B8E.TF9CBF14 VSAM 64 0 66 29 1920 90 0 PRM 0 00/00/00 --PERM-- *-DSF-*
Z9999992.VSAMDSPC.T9A38B90.T8822066 VSAM 67 0 144 29 2010 2340 0 PRM 0 00/00/00 --PERM-- *-DSF-*
VSESP21.NCP.LIBRARY SAM 145 0 162 29 4350 540 + 1 PRM 0 06/24/07 -RETAIN-
VSE.PRD1.LIBRARY SAM 163 0 233 29 4890 2130 + 1 PRM 0 12/22/07 -RETAIN-
Z9999992.VSAMDSPC.T9A38B8F.T56EF35E VSAM 234 0 333 29 7020 3000 0 PRM 0 00/00/00 --PERM-- *-DSF-*
IBM.VSESP21.DBASE.LIBRARY SAM 334 0 369 29 10020 1080 + 1 PRM 0 06/04/07 -RETAIN-
CAI.VSESP21.PRODUCTS.LIBRARY SAM 370 0 552 29 11100 5490 + 1 PRM 0 06/05/07 -RETAIN-
--- VOLUME TABLE OF CONTENTS --- VTOC 553 0 553 29 16590 30 PRM
FORMAT-4 INFORMATION --------------------DEVICE CONSTANTS--------------------

LOCATION NXT-ALTTRK NUMBER VTOC TOTAL ACTIVE NUM TRKS TRACK LBLS DBLK
CCC-HH-RR CCC-HH ALTTRKS INDS. ENTRIES ENTRIES CYLS /CYL LENGTH /TRK /TRK I L K TOL FLAG
553-00-01 000-00 0 X'80' 1408 12 554 30 19254 47 36 1 11 82 512 X'00'
FREE EXPIRED ALLOCATED TOTAL

TRACKS TRACKS TRACKS FILES

Chapter 10: Accessing the Catalog
The DYNACC facility provides a general interface to the CA Dynam Catalog.
DYNACC accepts data requests, searches the Catalog, and returns data
suitably formatted for building reports. Conceptually, access may be obtained
to almost every data item in the Catalog apart from internal navigational
pointers.
DYNACC is also used by CA Dynam family reporting components such as

DYNPRINT. DYNACC is the means by which user programs and CA Dynam
reporting programs may obtain read-only access to the CA Dynam Catalog.
DYNACC may be used to access the Catalog and obtain information in either
data set or volume serial number sequence. Additionally, information about
the Catalog itself and about vaults may be retrieved.
DYNACC Version 2 is a major redevelopment in response to user requirements.

It is faster, more reliable, easier to use, and more functional than its
predecessor. On average, most programs using it will achieve runtime
reductions approximating 45 percent, and in some cases substantially more.
Complete compatibility has been maintained with the previous version.

Existing programs will execute unchanged in the CA Dynam r6.0 environment.
If an existing program that executes correctly using the earlier version of
DYNACC is relinked or recompiled, it will continue to function correctly, and no
changes are required unless you wish to benefit from the performance
advantages or functional enhancements realized in Version 2.
Supported Languages
Since DYNACC adheres to standard IBM linkage conventions, calling programs
may be written in any language that generates external program calls in a
manner that complies with these rules. This includes, among others, COBOL,
Assembler, and CA Earl. Copy text defining the DYNACC DYNINFO parameter
list is supplied for these three languages.
Using DYNACC
DYNACC is supplied as a relocatable program text file and is linked with the
calling program. It is designed to be CA Dynam release-independent. It runs in
both the CMS and VSE environments. DYNACC and all its called service
routines are self-relocating, reentrant, and operating system independent.
Chapter 10: Accessing the Catalog 10–1

Using DYNACC
DYNACC communicates with calling programs using a communications area or

parameter list called DYNINFO. Significant enhancements were made to
DYNACC Version 1, as shipped with CA Dynam r5.3 and additional fields have
been added to DYNINFO. However, changes have been made in a way which
should be compatible with existing programs. Because both Version 1 and
Version 2 formats are supported by DYNACC, there is no mandatory
requirement to change to the new format.
Testing DYNACC Programs
DYNATEST is a new feature in DYNACC Version 2. The DYNATEST macro has

been provided as an easy way of learning about DYNACC, the differences
between Version 1 and Version 2, and for prototyping strategies for retrieving
Catalog information. DYNATEST will generate a program to exercise any
DYNACC function and will print a report detailing the results. Programs can be
generated to use either Version 1 or Version 2 parameter lists and will execute
on any supported operating system. You may use the generated programs as
a guide when developing your own programs.
DYNINFO Parameter List Generation
The DYNINFO parameter list used to control DYNACC is generated by copying

a definition in the appropriate language from the library in which CA Dynam is
installed. Assembler programs should invoke the DYNINFOA macro directly.
For more information, see DYNINFO Parameter List or perform a test assembly
invoking the DYNINFOA macro with no parameters for a description.
Detailed documentation on DYNINFO and DYNACC function and return codes

has been built into DYNINFOA and is printed when that macro is invoked with
INFO=YES (the default) as a parameter.
Using DYNACC
DYNACC is supplied as a relocatable object module suitable for linking with a
calling program. DYNACC resides in the library in which CA Dynam was
installed. DYNACC Version 2 is a root module which dynamically invokes a
separate service module depending on the version of the parameter list.
DYNACC is approximately 1K bytes in length. It has one entry point. DYNACC

uses CA Dynam system functions and so will only execute if CA Dynam is
installed and available.
Under CMS, provided CA Dynam can be located, DYNACC will activate the
System Adapter automatically, if necessary. Under VSE, the System Adapter
must already be active when DYNACC is first invoked.
10–2 User Guide

Using DYNACC
The service module is loaded at runtime into dynamically acquired storage.

Under VSE, the service modules may be preloaded into the Shared Virtual
Area. Alternatively, they will be loaded at runtime into the partition GETVIS
area by DYNACC. The Version 2 service module, CACUDA20, is approximately
12K in size. It acquires a further 16K or more for catalog buffers and work
areas, depending on the options specified by the caller.
Linkage Conventions
DYNACC is called using standard IBM linkage conventions.
Linkage register usage on entry is as follows:
R1 points to the parameter list.
R13 points to a standard format save area (XL72).
R14 points to the return address in the calling program.
R15 points to the entry point in DYNACC
On return, R15 will contain a return code and the condition code is set to
facilitate error processing. The return code is also stored in a field in the
DYNINFO header (DYNRTCOD) for use by high-level languages.
Parameter List Contents
The parameter list is in IBM standard format as generated by the Assembler

CALL macro and equivalent higher level constructs. Assembler programmers
should use the CALL macro to ensure strict adherence to linkage conventions,
upon which DYNACC relies.
The parameter list contains one entry, as follows:
+0 A(DYNINFO) - address of DYNINFO
The high-order bit should be on to denote end-of-list. This ensures

compatibility should a future release support additional calling parameters.

DYNINFO Parameter List
Service Module Processing
On initial entry, DYNACC determines what version parameter list has been
passed by the caller. Depending on the version level of the caller's parameter
list, an appropriate service module is dynamically invoked. The service module
returns directly to the caller. If the caller uses a Version 1 format parameter
list, the service module invoked is CACUDA10. This module was created by
applying maintenance correcting all CA Dynam r5.3 known DYNACC problems
to the standard 5.3 DYNACC object module and linking it as a separately
loadable module.
This ensures that programs which yielded correct results using DYNACC
Version 1 will continue to execute correctly when relinked with DYNACC
Version 2.
DYNACC sets a return code and returns immediately to the caller if it is unable
to locate the System Adapter or the appropriate service module.

The DYNINFO parameter list may be generated in a number of ways.
Invoking DYNACC from COBOL and CA Earl Programs
High level language processors may use a source (copybook) description.

Copybooks are supplied for COBOL and CA Earl. The name of the copybook is
obtained by appending a language identifier character to the name DYNINFO.
For COBOL it is DYNINFOC and for CA Earl it is DYNINFOE. These reside in the
same library as DYNACC.
Invoking DYNACC from Assembler Programs
Assembler programmers should use the DYNINFOA macro. For compatibility

with Version 1, an Assembler copy unit called DYNINFO is also supplied. This
contains a DYNINFOA macro call with parameters set to generate a Version 1
format parameter list. This ensures that programs which were written to use
the earlier version will not be impacted unless you explicitly change the
version level of the parameter list.
The DYNINFOA macro generates a parameter list in the correct format for
either Version 1 or for Version 2.
10–4 User Guide

The macro has the following syntax:
name DYNINFOA [ TYPE= {DS|CSECT|DSECT }, ]

[ V=n, ]
[ INFO=YES|NO, ]
[ LEN=nnnnn ]
name Required parameter. This is the label used in the CALL to DYNACC.
INFO= Optional parameter. Determines whether explanatory material will be

generated.
YES or NO (defaults to YES)
LEN=nnnnn Optional parameter. Determines the value assigned to DYNRQLEN and the
amount of storage reserved for DYNINFO. (Determines how many records
DYNINFO can accommodate.) Choose a number greater than the value of
DYNCOMLN.
Defaults to a number sufficient to accommodate 20 sets of volume information

for a single multivolume data set version. To calculate this value, multiply the
number of volumes minus one by DYNVBRLN and add DYNCOMLN. One
volume is already included in DYNCOMLN.
TYPE= Optional parameter. Determines the type of label generated by DYNINFO.
DS, CSECT, and DSECT are mutually exclusive; choose only one value.
Defaults to DS.
V=n Optional parameter. Indicates which version of the parameter list is generated.
It corresponds to the Dynam release.
Example:
7 for Dynam r7.0 and 7.1

Defaults to current release.
DYNACC modifies the current program mask but restores
it before returning to the caller.
DYNINFO is the parameter list used to communicate between the calling

program and DYNACC. The address of DYNINFO must be passed in a standard
format parameter list as produced by the CALL macro.

Example:
.
.
LA R13,DYNASAVE ESTABLISH SAVE AREA
CALL DYNACC,(DYNINFO) INVOKE CATALOG ACCESS
LTR R15,R15 TEST RETURN CODE
.
.
DYNINFO DYNINFOA , GENERATE PARAMETER LIST
.
DYNINFO Layout
DYNREQST User requests
DYNRETRN DYNACC status and communication fields
DYNCCREC Catalog Control Information
DYNVCREC Vault Control Information
DYNDBREC Data set Information
DYNGBREC Version/Generation Information
DYNVBREC Volume/Extent Information
For more information about a list of the component fields and their contents,
see DYNACC Version 2 Parameter List Contents.
DYNACC Request Codes
To Request Use
Code
direct retrieve: by data set DD

by volser DV
generic retrieve: by data set GD

by volser GV
get control information CC
get next: file for volser NF

generation/version for data set NG
volumes/extents for version NX
10–6 User Guide

To Request Use
Code
get vault description VC

information
reset: catalog processing RC

sequential data set processing RD
sequential data set processing RV
sequential retrieve: by data set SD

by volser SV
set EARL flat file retrieval option OE
DYNACC Request Code Descriptions
CC Retrieves information describing the Catalog data set.
Required fields: None
Optional fields: None
Return codes: None
DD Initiates a direct retrieval of the data set whose DSN matches DYNRQDSN. If a
generation or version selection field is specified (DYNRQVER, DYNRQGEN,
DYNRQGDG, or DYNRQVOL) the appropriate generation will be returned.
Otherwise, the most current generation will be returned.
If DYNRQDVC is specified, only data sets and versions of the required device
class will be returned. If DYNRQVSQ is specified, volumes starting at the
volume sequence number specified are returned. Otherwise volumes starting
with the first volume for the version are returned. As many volumes as exist
and fit in DYNINFO are returned in one call.
If more volumes or extents exist than will fit, DYNRTCOD is set to 28.
DYGNVOL always contains the number actually returned. DYGVOLS always
contains the total number active for the version. DYNRTLEN contains the
DYNINFO length in bytes required to hold all volumes available, starting at the
specified volume sequence number.
Required fields: DYNRQDSN
Optional fields: DYNRQPSW, DYNRQDVC, DYNRQVER, DYNRQGEN,

DYNRQGDG, DYNRQVOL, DYNRQVSQ

The fields DYNRQVER, DYNRQGEN, DYNRQGDG, and DYNRQVOL are mutually

exclusive and are evaluated in the order given. The first nonblank field in this
sequence is used and all of the subsequent fields are ignored.
Return codes:
4 data set has no active versions
8 version or volume not found
12 specified data set not found
28 insufficient length for all volumes
32 syntax error (either invalid packed field on DYNRQVER, DYNRQGEN, or

DYNRQVSQ; or, DYNRQDVC is invalid - see DYNERCOD and DYNERLOC)
40 invalid password
DV Initiates a direct retrieval of the tape volume whose VOLSER matches

DYNRQVOL. If DYNRQFSQ is specified, the version and data set for that file
sequence number on the volume is returned. Otherwise the first data set
version on the tape is returned.
Required fields: DYNRQVOL
Optional fields: DYNRQPSW, DYNRQFSQ
Return codes:
6 volume is scratch - no active data sets
8 specified volser or filseq not found
16 password-protected data set
32 syntax error (invalid packed field - DYNRQFSQ)
GD Initiates or continues a scan of the Catalog in DSN sequence starting at the

first data set whose name matches the partial key supplied in DYNRQDSN up
to the first blank. If DYNRQDVC is specified, only data sets and versions of the
required device class will be returned.
Required fields: DYNRQDSN
Optional fields: DYNRQPSW, DYNRQDVC
Return codes:
4 no active versions
16 password protected data set
20 no more data sets
10–8 User Guide

32 syntax error (DYNRQDSN all spaces or DYNRQDVC invalid)
GV Initiates or continues a scan of the Catalog in volser sequence starting at the

first volume whose volser matches the partial key supplied in DYNRQVOL up to
the first blank.
Required fields: DYNRQVOL
Optional fields: DYNRQPSW
Return codes:
6 volume is scratch - no active data sets

24 no more volumes
32 syntax error (DYNRQVOL all spaces)
NF Is used after an SV, GV, DV, or NF call to return the next file on a multifile
tape volume without reaccessing the volume information. It is functionally
equivalent to a DV with the DYNRQFSQ value incremented by one, but is
significantly faster. DYGFILSQ indicates the actual file sequence number
returned.
Return codes:
16 password-protected data set
26 no more files for volume
32 syntax error (previous command was not SV, GV, DV, or NF)
NG Is used after a SD, GD, DD, NX, or NG call to return the next generation for
the data set without reaccessing the data set information. It is functionally
equivalent to a DD call with DYNRQVER incremented by 1, but is significantly
faster. If DYNRQDVC is specified, only data sets and versions of the specified
device class will be returned. If DYNRQVER is nonblank, it will be validated as
a packed field. A valid packed number is assumed to be the number of
versions retrieved for this data set so far, and is incremented by one. It is not
used in any other way. Scratched, test and invalid generations are ignored and
do not count in calculating the relative generation number.
Optional fields: DYNRQDVC, DYNRQVER

Return codes:
18 no more versions for data set
32 syntax error (previous command was not SD, GD, DD, NX, or NG; or
DYNRQDVC is invalid; or DYNRQVER is not spaces and is not a valid
packed field - see DYNERCOD and DYNERLOC)
NX Is used after an SD, GD, DD, NG, or NX call to return as many volumes or
extents as exist and will fit in DYNINFO, starting with the volume which follows
the last volume or extent retrieved. The data set and version information is
not rebuilt. This is functionally equivalent to a DD call for the same version
with the volume sequence number incremented by one, but is considerably
faster.
Return codes:
22 no more volumes for version
32 syntax error (previous command was not SD, GD, DD, NG, or NX)
OE Is used to set an option to ensure that no more than one volume or extent is
returned for a given data set version per call, regardless of how many will fit in
DYNINFO. This option, once set, only affects data set calls (SD, GD, DD, NG,
or NX). It is reset whenever the Catalog is reset explicitly by an RC call or
implicitly by logical end of file for a sequential or generic retrieve or by a
significant error (DYNRTCOD > 36).
If more than one volume or extent remains, DYNRTCOD will be set to 28.
DYGNVOL will always be equal to 1. DYNRTLEN always reflects the length in
bytes of DYNINFO necessary to accommodate all available volumes starting at
the relevant volume sequence number. DYGVOLS reflects the total number of
volumes or extents for the version.
Return codes: None
RC, RD, RV Resets catalog processing. A subsequent sequential or generic retrieve will
start again from the beginning. All dynamic work areas and catalog buffers are
released and will be reallocated on a subsequent call. Automatically invoked on
logical end-of-file for sequential and generic retrieves and on significant errors.
10–10 User Guide

Return codes: None
SD Initiates or continues a scan of all data sets in the Catalog in DSN order. The
most current valid version and its associated volumes are returned. If
DYNRQDVC is specified, only data sets and versions of the requested device
class will be returned.
Optional fields: DYNRQPSW, DYNRQDVC
Return codes:
4 data set has no active versions

20 no more data sets
32 syntax error (device type is invalid)
SV Initiates or continues a scan of all tape volumes in the Catalog in VOLSER

order. The first data set version on the tape is returned.
Optional fields: DYNRQPSW
Return codes:
6 no active data sets (volume is a scratch)
24 no more volumes
VC Is used to retrieve descriptions of vaults defined in the Catalog.
Return codes:
28 more vaults exist than fit in DYNINFO. The only way to retrieve these
descriptions is to enlarge DYNINFO. DYNRTLEN contains the length in
bytes to which DYNINFO must be enlarged to accommodate all vault
descriptions.

DYNINFO Request Fields
DYNSTAMP, DYNRQID, DYNRQLEN

These DYNINFO header fields containing the sentinel, release identifier and
parameter list length are required. If DYNINFO is generated with TYPE=CSECT
or TYPE=DS (the default), these fields will contain the correct values at
execution time. However, if generated as a DSECT (TYPE=DSECT), these
values must be initialized as shown by the caller before invoking DYNACC.
If DYNSTAMP is not equal to DYNINFO, DYNACC will set DYNRTCOD to 28.
DYNRQLEN, DYNNVBRS
For data set calls (SD, GD, DD, NG, and NX), for each data set (DYNDBREC)
and version (DYNGBREC) retrieved, DYNACC builds an array of volume/extent
(DYNVBREC) entries in DYNINFO. Usually this starts with volume sequence one
for the file version and continues for as many volumes or extents as exist and
will fit in DYNINFO. If the DD call is used, specifying the DYNRQVSQ
parameter, then the array will commence with the specified volume sequence
number. If the NX call is used, the array will commence with the next volume
in sequence after the last volume returned by the preceding SD, GD, DD, NG,
or NX call.
By default, enough space is reserved in DYNINFO to accommodate twelve tape

volumes for a given data set version. The actual number that may be
accommodated is indicated by the DYNNVBRS field. At assembly time, the
DYNINFOA macro calculates the DYNNVBRS value by dividing the length of
DYNINFO, minus the length of other segments, by the length of a tape
DYNVBREC (DYNVBRLN).
As DYNACC builds DYNINFO while processing each call, the length of each
segment is added to DYNRTLEN. The segment is not moved into DYNINFO if
there is insufficient space to accommodate it. This is determined by comparing
the value in DYNRTLEN with that specified by DYNRQLEN. When DYNRTLEN is
greater than DYNRQLEN, DYNACC sets DYNRTCOD to 28.
DYNRTLEN contains the length in bytes of DYNINFO required to accommodate

all volumes for the requested data set version, starting at the volume
sequence number specified in DYNRQVSQ. (DYNRQVSQ is only valid for DD
calls.) The DD function may be used to retrieve the additional volumes for the
version.
The LEN parameter of the DYNINFOA macro may be used to reserve a greater
or smaller number of bytes for DYNINFO in total. The LEN value specifies the
length reserved for DYNINFO and the value to be placed in DYNRQLEN.
Consequently, a greater or smaller number of VBRs may be accommodated.
The minimum length is equal to the value specified by DYNCOMLN. Calculate
the required value by adding the value specified by DYNCOMLN to the result of
the number of volumes desired, minus one, multiplied by the length of the
appropriate segment (DYNVBRLN for tapes or DYNEXTLN for disk extents).
10–12 User Guide

If the OE call is used to set the EARL flat file option, no more than one volume
or extent will be returned at a time by DYNACC. If the file version is spread
over more than one volume or extent, DYNRTCOD will be set to 28 regardless
of the amount of space reserved for DYNINFO. In this case DYGNVOLS will
never be greater than one.
DYNREQST Contains all input variables to DYNACC. If an optional field is to be omitted, it

must be cleared to spaces before calling DYNACC. Selection fields which
contain other values, for example, binary zeros, will be evaluated by DYNACC
as selection fields.
DYNRQDSN Required for DD and GD calls. Otherwise, it must be spaces.
For GD calls, all data sets which match all characters before the leading space
will be returned. On DD calls, if an exactly matching DSN is not found,
DYNRTCOD 12 is set. On GD calls, on the call after all matching data sets have
been returned (if any) DYNRTCOD 20 is set. For GD calls, DYNRQDSN must
contain at least one nonblank character, else DYNRTCOD 32 (SYNTAX ERROR)
and DYNERCOD 8 (GENERIC KEY ALL SPACES) is set.
DYNRQPSW For password-protected data sets, if no password is supplied, for any call
except a DD, DYNRTCOD 16 is set and only the DSN is returned. On a DD call
for a password-protected data set, if no password is supplied or doesn't
match, DYNRTCOD 40 is set and the call is terminated.
DYNRQVER Optional for DD calls. Otherwise must be spaces. It is the disk or tape data set
version number, relative to the most current version (version one) to be
retrieved. Test ($TEST job), scratch and invalid versions (such as, open not
closed) are ignored. If not found, DYNRTCOD 8 is set. May not be specified in
conjunction with DYNRQGEN, DYNRQGDG, or DYNRQVOL. If DYNRQVER,
DYNRQGEN, DYNRQGDG, and DYNRQVOL are all spaces, the most current
version (version one) is returned.
DYNRQGEN Optional for DD calls. Otherwise must be spaces. It is the CA Dynam/D disk
data set generation number to match against in the catalog. If not found,
DYNRTCOD 8 is set. May not be specified in conjunction with DYNRQVER,
DYNRQGDG or DYNRQVOL.
DYNRQGDG Optional for DD calls. Otherwise must be spaces. It is the OS or MVS

Generation Data Group identifier to match against in the Catalog. If not found,
DYNRTCOD 8 is set. May not be specified in conjunction with DYNRQVER,
DYNRQGEN, or DYNRQVOL.
DYNRQVOL Required for DV and GV calls. Optional for DD calls. Otherwise must be spaces.
For DV calls, it is used to specify the exact volser to retrieve. If not found,
DYNRTCOD is set to 8. If the volser contains no active files (is a scratch),
complete volume information (but no data set or version information except
for the most recently active data set name) is returned, and DYNRTCOD is set
to 6.

For GV calls, tape volumes which match the characters before the leading
space are returned. On the call after the last matching volser has been
returned, DYNRTCOD 24 is set. DYNRTCOD 6 is set for volumes with no active
files (scratches). A key of at least one nonblank character must be supplied,
otherwise DYNRTCOD 32 (SYNTAX ERROR) and DYNERCOD 16 (VOLSER
GENERIC KEY ALL SPACES) is set.
For DD calls, it is used to request that the version of the tape data set which
resides on a specific volume is returned. If the volume does not contain an
active version of the data set, DYNRTCOD 8 is set. May not be specified in
conjunction with DYNRQVER, DYNRQGEN or DYNRQGDG.
DYNRQVSQ Optional for DD calls. Otherwise must be spaces. It may be specified in

conjunction with version selectors (DYNRQVER, DYNRQGEN, DYNRQGDG, or
DYNRQVOL).
It is used to specify the starting volume sequence number for a multivolume

tape file (relative to 1) or the relative extent sequence number for multi-
extent disk files (relative to 1). DYNRQVSQ is useful where DYNINFO is not
large enough to hold all volumes or extents for a data set version. If a SD, GD,
DD, or NG call results in DYNRTCOD being set to 28, set up a DD call for the
data set with DYNRQVSQ set to one greater than the number of volumes
retrieved so far. The DYNVBREC array is filled with as many volumes as exist
and will fit, starting at this volume sequence number.
DYGNVOL always contains the number of tape or disk entries actually returned
for a specific call. DYGVOLS contains the total number of volumes or extents
that exist for a data set version. DYNNVBRS indicates the number of tape
volumes which will fit in DYNINFO. More than this number of disk entries will
fit, as disk entries are smaller. If more exist than will fit, as many as will fit are
returned, DYNRTCOD is set to 28, and DYNRTLEN is set to indicate the length
that would have been required to accommodate all that exist, starting at the
volume sequence number specified in DYNRQVSQ. (DYNRQVSQ is only valid
for DD calls.)
DYNRQFSQ Optional for DV calls. Otherwise must be spaces. It is used to indicate which
file on a multifile tape volume is to be returned, relative to 1. If this file
sequence does not exist, DYNRTCOD is set to 8. If this field is not set, the first
active file version on the tape volume is returned.
DYNRQDVC Optional for SD, GD, DD, and NG calls. Otherwise must be spaces. It is used to
select the device class of data sets and generations to be retrieved from the
Catalog. Selection values are as follows:
(blank) all data sets and generations
T TAPE and FI data sets and tape generations
10–14 User Guide

D DISK and FI data sets and disk generations
F FI data sets and all generations
Any other value will cause DYNRTCOD 32 (SYNTAX ERROR) and DYNERCOD 28
(INVALID DEVICE CLASS) to be set.
Note that a data set defined as FI will qualify as both disk and tape, and so FI
data sets will be returned for DYNRQDVC = T or D. However, for FI data sets,
only those versions actually created on tape will be returned for T and only
those versions actually created on disk will be returned for D. FI data sets
which have only versions of the excluded type will have the data set
information returned, no version or volume information, and DYNRTCOD will
be set to 4 (NO ACTIVE VERSIONS).
DYNCBUFN Specifies the number of Catalog buffers to be allocated by Catalog

Management. Minimum is two and default is twelve. Buffers are the same size
as the Catalog control interval size, usually 1K.
DYNCATNM Specifies the DD name or DTF name to be used to access the Catalog. May be
used to access a snapshot of the Catalog by restoring a backup tape and
referring to the restored file by a name other than the active system Catalog.
Defaults to CAICATL.
DYNEROPT DYNACC never intentionally aborts, but sets a return code and returns to the
caller. If this field is set to D, on any significant error (DYNRTCOD > 32),
DYNACC will produce snap dumps of areas of interest before returning. It is up
to the caller to terminate processing.
DYNINFO Return Fields
DYNINFO DYNRTCOD Return Codes

0 Requested info has been returned.
4 DSN exists but has no active generations.
6 VOLSER exists but has no active files.
8 Requested version or volser does not exist.
12 Requested dsn or volser does not exist.
14 Catalog information missing.
16 Data set is password protected.
18 No more versions for dsn - NG.
20 No more dsns - SD or GD.
22 No more volumes for version - NX.

24 No more volumes - SV or GV.
26 No more files for volume - NF.
28 More volumes exist for dsn than fit in DYNINFO.
32 Syntax error in call - reason code in DYNERCOD.
34 DYNINFO DYNRQLEN below minimum (DYNCOMLN).
36 DYNACC/DYNINFO version mismatch (DYNRQID).
38 DYNINFO sentinel not found (DYNSTAMP).
40 Password is incorrect (DYNRQPSW).
44 Physical I/O error during Catalog read.
46 Logical I/O error during Catalog read.

48 Catalog is inaccessible.
56 GETVIS denial for buffers.
64 Catalog saver memory management error.
68 DYNACC logical error - location in DYNERLOC.
92 GETVIS denial for dynamic storage.
96 Unable to locate CACUDAX0 phase.
DYNINFO DYNERCOD Error Codes
For DYNRTCOD 14 - Catalog Information Missing
04 Invalid GBRVPRPT pointer.
08 Missing DBR for volser.
12 Missing GBR for volser.
16 Invalid GBRLINK pointer.
20 Invalid VCRLINK pointer.
For DYNRTCOD 32 - SYNTAX ERROR IN CALL
04 Invalid function code.
08 DSN generic key is all spaces.
12 Invalid previous command for NG.
16 Volser generic key is all spaces.
20 Invalid previous command for NF.
24 Invalid packed field - DYNERLOC has location.
28 Invalid device class selection.
32 Invalid previous command for NX.
10–16 User Guide

DYNACC User Exits
DYNACC User Exits

DYNACC supports two types of user exit processing. The first type of exit
provided is an EXCP exit. Each time CA Dynam Catalog Management issues an
EXCP, if the exit is active, control will be passed to it. This is designed to allow
the exit to perform a WAIT operation on the event control block which is
passed as a parameter. This permits users who call DYNACC from within a
data communications environment or multitasking environment to perform
their own WAIT processing and to avoid an operating system level WAIT
operation which might be detrimental to performance.
The exit may also be used for other purposes, such as performance metrics.
DYNATEST programs use the exit to count EXCPs, for example.
The other type of exit supported is a logical error exit. This is supplied for
debugging purposes and for error analysis of Catalog errors. If the exit is
active, and the DYNACC catalog search routines encounter an unexpected
error condition, the exit will be invoked. DYNATEST, for example, can generate
code to dump areas of interest in such a situation.
DYNAEXIT EXCP Exit
This exit is activated by including a user exit module called DYNAEXIT with the
DYNACC root module when the user application program is link edited. The
routine will receive control immediately after an EXCP on the Catalog is issued.
Control must be returned to CA Dynam or results are unpredictable. After
control is returned from the user exit, Catalog Management will check to see
whether a WAIT is still necessary. If none was performed by the exit, CA
Dynam will issue one in the normal fashion. Upon entry to the users exit, the
following conditions will exist:
R0 points to the save area provided by the caller on entry to DYNACC. This is
assumed to be a standard format save area of 72 bytes. DYNACC stored the
caller's registers R14 through R12 starting at offset decimal 12 on entry from
the calling program. This save area may be used by the exit to obtain the
addresses of code and data in the caller's program.
R13 points to a standard format save area in which the exit must save its registers
on entry and restore them on exit. The first three words contain save area
chain pointers and should not be changed.
R14 will point to the return address in CA Dynam.
R15 will point to the user exit entry point and may be used to obtain addressability.

Test Program Generator - DYNATEST
DYNACC Version 2 differs in DYNAEXIT processing from Version 1 in the

following way: For Version 1, R0 on entry pointed to an area containing the
callers registers R2 through R15. It should be noted that R0 now points to the
save area containing all registers. The user needs to note the change to an
IBM standard save area format and the consequent change in offsets to
particular registers. This change will only impact callers using Version 2
parameter lists, as a Version 1 parameter list will cause the original service
module to be invoked, which will continue to store the registers in the old
manner.
DYNEEXIT Catalog Logical Error Exit
This exit is activated by including a user exit module called DYNEEXIT with the
DYNACC root module when the user application program is link edited. Upon
entry to the user's exit, the following conditions will exist:
R0 points to the save area provided by the caller on entry to DYNACC. This is
assumed to be a standard format save area of 72 bytes. DYNACC stores the
caller's registers R14 through R12, starting at offset decimal 12 on entry from
the calling program. This save area may be used by the exit to obtain
addressability to code and data in the caller's program.
R1 points to the Catalog Management parameter list.
R2 contains the Catalog Management function code.
R13 points to a standard format save area in which the exit must save its registers
on entry and restore them on exit. The first three words contain save area
chain pointers and should not be changed.
R14 will point to the return address in CA Dynam.
R15 will point to the user exit entry point and may be used to obtain addressability.
DYNATEST Functions
DYNATEST is a macro which generates an assembler program to access the CA

Dynam Catalog using either the Version 1 or Version 2 format parameter list.
The program is executable either on VM or VSE.
10–18 User Guide

While DYNACC operation is system independent, the program generated by

DYNATEST requests operating system services using standard interfaces;
therefore the program only executes on the operating system for which it was
generated.
DYNATEST is intended to demonstrate how to use DYNACC Version 2.0. It also

illustrates the differences between DYNACC Version 1, as shipped with CA
Dynam 5.3, and DYNACC Version 2, as shipped with CA Dynam 5.5, or higher.
DYNATEST can generate a program which calls either version of DYNACC

correctly. When a retrieval which executes correctly on Version 1 is repeated
using Version 2, identical results should be achieved, but the performance
advantages of Version 2 should be apparent.
DYNATEST can also be used to experiment with the effect of changing various
parameters such as the number of volumes which may be accommodated in
DYNINFO so that the effect on EXCP counts may be observed.
DYNATEST Syntax
The macro has the following syntax:
name DYNATEST [ AEXIT=YES|NO, ]

[ BUFN=nnnn, ]
[ CATN=dtfname, ]
[ DSN=dsn ]
[ DVC=D|T|F, ]
[ EEXIT=NO|YES, ]
[ EROPT=D ]
[ FLAT=NO|YES, ]
[ FSQ=nnnn, ]
[ GDG=xxxxxxxx, ]
[ GEN=nnn, ]
[ INFO=YES|NO, ]
[ NCALLS=nnnnnn, ]
[ NVBRS=nnnn, ]
[ PCOMM=NO|YES, ]
[ PSW=xxxxxxxx, ]
[ REQ=SD|GD|DD|SV|GV|DV|CC|VC, ]
[ SYSTEM=DOS|CMS, ]
[ V=2|1, ]
[ VER=nnn, ]
[ VOL=xxxxxx, ]
[ VSQ=nnnn, ]
The first value specified after the equals sign is the default.

name Required parameter. It is the name of the CSECT to be generated.
AEXIT= Optional parameter. Determines whether a DYNAEXIT routine is to be

generated. Choose either
BUFN=nnnn Optional parameter. Specifies the number of Catalog buffers to be allocated.

Each buffer is the size of the Catalog CI size, usually 1K.
a 1- to 4-digit number in the range 3-9999 (defaults to 12)
CATN=dtfname Optional parameter. Identifies the ddname of the Catalog. Specify
1-8 alphanumeric characters (defaults to CAICATL)
DSN= Optional parameter. Data set name provides the key for generic or direct data
set calls.
DVC= Optional parameter. Specifies a device class restriction to be placed on the

data sets and generations to be retrieved by data set type calls (SD, GD, DD,
and NG).
D for disk
T for tape
F for file independence (FI)
EEXIT= Optional parameter. Determines whether a DYNEEXIT routine is to be

generated.
NO or YES (defaults to NO)
EROPT= Optional parameter. Include it only if you want DYNACC to generate snap
dumps on error. Otherwise omit it.
D for snap dumps (defaults to spaces)
FLAT= Optional parameter. Determines whether the generated program is to issue a

request during initialization to DYNACC to set the EARL flat file option. This
option causes DYNACC to return only one extent or volume per call, regardless
of how many exist and can fit in DYNINFO.
10–20 User Guide

FSQ=nnnn Optional parameter. For a multifile tape volume, for a direct volume (DV) call,
specifies which data set version is to be retrieved.
GDG=xxxxxxxx Optional parameter. Identifies the generation to retrieve, based on the

operating system generation data set group you specify here.
GEN=nnn Optional parameter. Specifies the CA Dynam/D data set version to retrieve for
a direct data set call (DD).
a 1- to 3-digit number in the range 1-999
If omitted, the most current is assumed.
INFO= Optional parameter. Determines whether descriptive material is generated.
NCALLS=nnnnnn Optional parameter. Specifies the maximum number of calls to make to

DYNACC.
NVBRS=nnnn Optional parameter. Determines the maximum number of tape volumes for a
single version which may be accommodated in DYNINFO.
PCOMM= Optional parameter. Determines whether the generated program is to build

the request to DYNACC from an argument passed in a DYNPCOMM parameter
list from DYNPRINT, or from the selection arguments passed to this macro.
This is intended to assist in debugging user programs written to execute in the
DYNPRINT execution environment.
PSW=xxxxxxxx Optional parameter. Specifies the password to be supplied to DYNACC.

DYNACC only returns the data set name for password-protected data sets
unless you supply the appropriate password. Supply either the catalog or the
data set password.
1 to 8 alphanumeric characters

REQ= Optional parameter. Determines the basic type of retrieval to be performed by

the generated program. Choose only one of these values:
SD, GD, DD, SV, GV, DV, CC, or VC
If CC or VC is specified, a maximum of one call is made to DYNACC, after

which the program will terminate.
For other types, additional calls will be constructed and executed to ensure
that all volumes (for data set type calls) or files (for volume type calls) for
each data set or volume are retrieved.
For direct calls (Dx), the generated program terminates once the specified
data set or volume has been completely processed.
For sequential or generic calls (Sx or Gx), the program terminates when
DYNACC indicates an end condition exists.
In any case, the program terminates normally when the NCALLS counter
decrements to zero.
SYSTEM= Optional parameter. Determines which operating system environment to

generate support for.
DOS or CMS (defaults to DOS)
V= Optional parameter. Determines whether the generated program is to use

Version 2 or Version 1 format DYNINFO to call DYNACC. Choose either 2 or 1
(defaults to 2)
VER=nnn Optional parameter. Identifies the version number of the data set to retrieve
for a direct data set call (DD).
a 1- to 3-digit number in the range 1-255
If omitted, version one of the data set is assumed.
VOL=xxxxxx Optional parameter. Specifies the volume serial number to retrieve for a direct
(Dx) call.
VSQ=nnnn Optional parameter. For a multivolume file version, for a direct data set (DD)
call, specifies the volume sequence number of the first volume to retrieve. As
many subsequent volumes are retrieved as exist and can fit in DYNINFO (see
also the NVBRS parameter).
10–22 User Guide

DYNACC Version 2 Parameter List Contents

DYNINFO DYNINFOA INFO=NO
DYNINFO DC 0D'0' DYNACC PARAMETER LIST
***************************************************************
* 'DYNINFOA' MACRO V7.1 *
* COPYRIGHT (C) 2007 CA. ALL RIGHTS RESERVED. *
* CA Dynam CATALOG USER INTERFACE *
***************************************************************
DYNSTAMP DC CL8'DYNINFO ' SENTINEL
DYNRQID DC CL4'7.1' VERSION
DYNRQLEN DC PL4'6709' TOTAL LENGTH DYNINFO
***************************************************************
* DYNACC REQUEST AREA - INPUT VARIABLES *
***************************************************************
DYNREQST EQU * USER REQUEST AREA
DYNRQCD DC CL2' ' TYPE OF REQUEST
DYNRQDSN DC CL44' ' DATA SET NAME
DYNRQPSW DC CL8' ' CATALOG OR DATASET PASSWORD
DYNRQVER DC PL3'0' VERSION NUMBER
DYNRQGEN DC PL2'0' GENERATION NUMBER
DYNRQGDG DC CL8' ' GENERATION DATA GROUP ID
DYNRQVOL DC CL6' ' VOLUME SERIAL NUMBER
DYNRQVSQ DC PL2'0' VOLUME SEQUENCE NUMBER
DYNRQFSQ DC PL2'0' FILE SEQUENCE NUMBER
DYNRQDVC DC CL1' ' DEVICE CLASS
DYNCBUFN DC PL3'0' NO OF CATALOG BUFFERS
DYNCATNM DC CL8' ' CATALOG FILE NAME
DYNEROPT DC CL1' ' ERR OPT D = DUMP
DYNHDRLN EQU *-DYNREQST LENGTH REQUEST AREA
ORG DYNREQST
DC (DYNHDRLN)C' ' INITIALIZE TO SPACES
***************************************************************
* DYNACC RETURN AREA - OUTPUT VARIABLES *
***************************************************************
DYNRETRN EQU * DYNACC COMMUNICATION AREA
DYNRTCOD DC PL2'0' RETURN CODE
DYNERCOD DC PL2'0' ERROR CODE
DYNERLOC DC XL4'00' DISPLACEMENT OF ERROR FIELD
DYNRTLEN DC PL4'0' DYNINFO RETURN LENGTH
DYNRECCT DC PL4'0' INPUT RECORD COUNTER
DYNREQCT DC PL4'0' DYNACC REQUEST COUNTER
DYNRQRES DC CL26' ' RESERVED FOR DYNACC
DYNAEEXT DC AL4(0) RESERVED FOR DYNACC
DYNAAEXT DC AL4(0) RESERVED FOR DYNACC
DYNREQLN EQU *-DYNSTAMP LENGTH DYNINFO HEADER SEGMENT
***************************************************************
* DYNWRKA -- DYNACC WORK AREA *
***************************************************************

DYNWRKA DC (1024)XL1'00'
DYNWRKLN EQU *-DYNWRKA LENGTH OF DYNACC WORK AREA
***************************************************************
* DYNREC -- DYNINFO RECORD OUTPUT AREA *
***************************************************************
DYNREC EQU * DYNINFO OUTPUT AREA
***************************************************************
* DYNCCREC -- CATALOG CONTROL RECORD SEGMENT *
***************************************************************
ORG DYNREC
DYNCCREC EQU * CATALOG CONTROL INFORMATION
DYCOWNID DC CL16' ' CATALOG OWNER IDENT.
DYCVOL DC CL6' ' VOLUME SERIAL NUMBER
DYCCISZ DC PL3'0' CONTROL INTERVAL SIZE
DYCLOWER DC PL6'0' LOWER EXTENT LIMIT
DYCUPPER DC PL6'0' UPPER EXTENT LIMIT
DYCNBYTS DC PL6'0' NUMBER OF BYTES IN THE CAT.
DYCFSREM DC PL6'0' NUMBER OF FREE SPACE BYTES
DYCNDBRS DC PL6'0' NUMBER OF DATASET BASE RECS.
DYCNSKRS DC PL6'0' NUMBER OF SORT KEY RECORDS
DYCNVBRS DC PL6'0' NUMBER OF VOLUME BASE RECS.
DYCSTAT0 DC CL8' ' STATUS FLAGS BYTE 0
DYCSTAT1 DC CL8' ' STATUS FLAGS BYTE 1 - RESERVED
DYCLEVEL DC CL2' ' CATALOG VERSION AND LEVEL
DYCCJOB DC CL8' ' CREATION JOB NAME
DYCCSTEP DC CL8' ' CREATION STEP NAME
DYCCPROC DC CL8' ' CREATION PROCEDURE NAME
DYCCCPU DC CL16' ' CREATION CPU ID SERIAL NUMBER
DYCCTOD DC PL4'0' CREATION TIME (0HHMMSS)
DYCCDTE DC PL4'0' CREATION SYSTEM DATE (00YYDDD+)
DYCCDAT DC CL8' ' CREATION SYSTEM DATE GREGORIAN
DYCCPART DC CL3' ' CREATION PARTITION ID
DYCCVER DC CL2' ' CREATION ADAPTER VERSION
DYCCLVL DC CL2' ' CREATION ADAPTER LEVEL
DYCCCPUI DC CL1' ' CREATION CPU ID CHARACTER
DYCCSYS DC CL8' ' CREATION OPERATING SYSTEM
DYCCDVTP DC CL6' ' CREATION DEVICE TYPE
DYCCCUU DC CL3' ' CREATION DEVICE ADDRESS
DYCBJOB DC CL8' ' BACKUP JOB NAME
DYCBSTEP DC CL8' ' BACKUP STEP NAME
DYCBPROC DC CL8' ' BACKUP PROCEDURE NAME
DYCBCPU DC CL16' ' BACKUP CPU ID SERIAL NUMBER
DYCBTOD DC PL4'0' BACKUP TIME (0HHMMSS)
DYCBDTE DC PL4'0' BACKUP SYSTEM DATE (00YYDDD+)
DYCBDAT DC CL8' ' BACKUP SYSTEM DATE GREGORIAN
DYCBPART DC CL3' ' BACKUP PARTITION ID
DYCBVER DC CL2' ' BACKUP ADAPTER VERSION
DYCBLVL DC CL2' ' BACKUP ADAPTER LEVEL
DYCBCPUI DC CL1' ' BACKUP CPU ID CHARACTER
DYCBSYS DC CL8' ' BACKUP OPERATING SYSTEM
10–24 User Guide

DYNCCRLN EQU *-DYNCCREC LENGTH CATALOG CONTROL SEGMENT

***************************************************************
* DYNVCREC -- VAULT CONTROL RECORD SEGMENT *
***************************************************************
ORG DYNREC
DYNVCREC EQU * VAULT CONTROL INFORMATION
DVCENTS DC PL4'0' NUMBER OF VAULT ENTRIES IN ARRAY
DVCENTRY EQU * VAULT CONTROL ENTRY
DVCVAULT DC CL1' ' VAULT IDENTIFICATION
DVCDESC DC CL100' ' VAULT DESCRIPTION
DVCSTAT0 DC CL8' ' VAULT STATUS BYTE 0
DVCSTAT1 DC CL8' ' VAULT STATUS BYTE 1
DVCENTLN EQU *-DVCENTRY LENGTH VAULT CONTROL ENTRY
ORG DVCENTRY+(26*DVCENTLN) ROOM FOR MAXIMUM VCRS
DYNVCRLN EQU *-DYNVCREC LENGTH VAULT CONTROL SEGMENT
***************************************************************
* DYNDBREC -- DATASET BASE RECORD SEGMENT *
***************************************************************
ORG DYNREC
DYNDBREC EQU * DATA SET INFORMATION
DYNDSN DC CL44' ' DATA SET NAME
DYNDSORG DC CL4' ' DATASET ORGANIZATION
DYNRECFM DC CL3' ' RECORD FORMAT
DYNBLKSZ DC PL3'0' BLOCK SIZE
DYNLRECL DC PL3'0' LOGICAL RECORD LENGTH
DYNKEYLN DC PL3'0' KEY LENGTH
DYNRKP DC PL3'0' RELATIVE KEY POSITION
DYNBUFNO DC PL2'0' NUMBER OF BUFFERS
DYNBFTEK DC CL1' ' BUFFER TECHNIQUE
DYNBTFKS EQU C'S' SINGLE BUFFERED
DYNBTFKD EQU C'D' DOUBLE BUFFERED
DYNBTFKE EQU C'E' EXCHANGE BUFFERING
DYNBTFKA EQU C'A' VARIABLE SPANNED RECORDS
DYNBTFKR EQU C'R' BDAM VBS
DYNBFALN DC CL1' ' BUFFER ALIGNMENT
DYNBFALF EQU C'F' FULLWORD ALIGNMENT
DYNBFALD EQU C'D' DOUBLEWORD ALIGNMENT
DYNDEVCL DC CL5' ' DEVICE CLASS
DYN00000 DC XL7'00' RESERVED
DYNOPTS DS 0CL120 DEFAULT OPTIONS
DYNOPTT DC CL40' ' DEFAULT TAPE OPTIONS
DYNOPTTA EQU C'A' MODIFY DDNAME IN PROGRAM
DYNOPTTD EQU C'D' DROP LABEL AT CLOSE
DYNOPTTH EQU C'H' HOLD DEVICE ASSIGN
DYNOPTTR EQU C'R' RELEASE WORK TAPE
DYNOPTTU EQU C'U' UNLOAD AT CLOSE
DYNOPTTW EQU C'W' REWIND AT CLOSE
DYNOPTD DC CL40' ' DEFAULT DISK OPTIONS
DYNOPTDA EQU C'A' ALIGN on CYLINDER BOUNDARY
DYNOPTDB EQU C'B' BYPASS AVR

DYNOPTDC EQU C'C' CATALOG DATASET AT CLOSE

DYNOPTDD EQU C'D' DELETE AT CLOSE FOR INPUT
DYNOPTDE EQU C'E' ENQUEUE DATASET AT OPEN
DYNOPTDI EQU C'I' PRINT INFO MESSAGES on SYSLST
DYNOPTDK EQU C'K' KEEP FILE AT CLOSE
DYNOPTDL EQU C'L' LOCK DATASET - READ ONLY
DYNOPTDM EQU C'M' PRINT INFO MESSAGES on SYSLOG
DYNOPTDN EQU C'N' DO NOT TRUNCATE AT CLOSE
DYNOPTDO EQU C'O' USE OLD EXTENTS
DYNOPTDP EQU C'P' PROHIBIT DYNAMIC LUB ALLOCATION
DYNOPTDR EQU C'R' ALLOW RECOVERY DURING ALLOCATION
DYNOPTDS EQU C'S' SORTIN=SORTOUT
DYNOPTDT EQU C'T' TRUNCATE AT CLOSE
DYNOPTDW EQU C'W' DELETE SORTWORK FILES AT CLOSE
DYNOPTDX EQU C'X' UNCONDITIONAL DELETE AT CLOSE
DYNOPTFI DC CL40' ' DEFAULT FI OPTIONS
DYNPOPT0 DC CL8' ' PROCESSING OPTIONS BYTE 0
DYNDOPT0 DC CL8' ' DISK OPTIONS BYTE 0
DYNDOPT3 DC CL8' ' DISK OPTIONS BYTE 3 - RESERVED
DYNTOPT0 DC CL8' ' TAPE OPTIONS BYTE 0
DYNTOPT3 DC CL8' ' TAPE OPTIONS BYTE 3 - RESERVED
DYNEXDTE DC PL4'0' EXPIRY DATE (00YYDDD)
DYNVAULT DC CL1' ' VAULT IDENTIFICATION
DYNREELS DC CL2' ' SPECIFIED REEL SIZE
DYNMODE DC CL2' ' SPECIFIED MODE SET
DYNMODE2 DC CL4' ' SPECIFIED MODE SET
DYNRETN DC PL3'0' NUMBER OF DAYS RETENTION
DYNNOACC DC PL3'0' NUMBER OF NOACC DAYS
DYNCYC DC PL3'0' NUMBER OF CYCLES RETENTION
DYNACYC DC PL3'0' NUMBER OF PER-END-CYCLES RETENTION
DYNPED DC CL8' ' CURRENT PERIOD ENDING DATE FOR DSN
DYNAUTOS DC PL3'0' CURRENT MF=AUTO SEQUENCE COUNT
DYNGENID DC CL2' ' PRESENT GENERATION VALUE FOR DSN
DYNOWNID DC CL2' ' OWNER ID CODE FOR DSN
DYNSYSID DC CL2' ' SYSTEM ID CODE FOR DSN
DYNUSRID DC CL2' ' USER ID CODE FOR DSN
DYNNOPNS DC PL6'0' TOTAL NUMBER OF OPENS
DYNSTAT0 DC CL8' ' DATASET STATUS FLAG 1
10–26 User Guide

DYNPASSW DC CL8' ' DATASET PASSWORD

DYNFILSQ DC PL2'0' SPECIFIED FILSEQ NUMBER FOR DSN
DYNVLTS DC CL1' ' VAULT INDICATOR FOR THIS DATA SET
DYNVLTSV EQU C'V' VAULT SUPPORT
DYNVLTSN EQU C'N' NO VAULT SUPPORT
DYNWRKS DC CL1' ' WORK INDICATOR FOR THIS DATA SET
DYNWRKSW EQU C'W' WORK DATASET
DYNWRKSN EQU C'N' NOT A WORK DATASET
DYNLCKS DC CL1' ' LOCK INDICATOR
DYNLCKSL EQU C'L' LOCKED FOR OUTPUT
DYNLCKSN EQU C'N' DATASET NOT LOCKED
DYNPACRC EQU * PRIMARY ALLOCATION CONTROL SEGMENT
DYNSNO DC PL3'0' NUMBER OF ALLOCATION TRIES
DYNVOL DC CL6' ' SPECIFIED VOLSER
DYNBEG DC PL6'0' PRIMARY ALLOCATION START
DYNSIZ DC PL6'0' PRIMARY ALLOCATION AMOUNT
DYNALLOC DC CL3' ' UNIT OF ALLOCATION
COMLUB DC CL6' ' LOGICAL UNIT OVERRIDE IF SPECIFIED
DYNSACRC EQU * SECONDARY ALLOCATION CONTROL SEGMENT
DYNSVOL DC CL6' ' SPECIFIED VOLSER
DYNSBEG DC PL6'0' SECONDARY ALLOCATION START
DYNSEC DC PL6'0' SECONDARY ALLOCATION AMOUNT
DYNSALLC DC CL3' ' UNIT OF ALLOCATION
DYNSLUB DC CL6' ' LOGICAL UNIT OVERRIDE IF SPECIFIED
DYNACRLN EQU *-DYNPACRC LENGTH ACR SEGMENT
DYNDDTE DC PL4'0' DEFINITION DATE (JULIAN)
DYNDDAT DC CL8' ' DEFINITION DATE (GREGORIAN)
DYNDTOD DC PL4'0' DEFINITION TIME (0HHMMSS)
DYNDJOB DC CL8' ' DEFINITION JOB NAME
DYNDPROC DC CL8' ' DEFINITION PROC NAME
DYNDCPUD DC CL16' ' DEFINITION CPU-ID
DYNDSYS DC CL8' ' DEFINITION OPERATING SYSTEM
DYNDSTP DC CL8' ' DEFINITION STEP NAME
DYNDPART DC CL2' ' DEFINITION PARTITION
DYNDCPU DC CL8' ' DEFINITION CPU ID
DYNDCPUA DC CL1' ' DEFINITION CPU ID (FROM CPUPROF)
DYNMDTE DC PL4'0' MANUAL UPD DATE (JULIAN)
DYNMDAT DC CL8' ' MANUAL UPD DATE (GREGORIAN)
DYNMTOD DC PL4'0' MANUAL UPD TIME (0HHMMSS)
DYNMJOB DC CL8' ' MANUAL UPD JOB NAME
DYNMSTP DC CL8' ' MANUAL UPD STEP NAME
DYNMPROC DC CL8' ' MANUAL UPD PROC NAME
DYNMCPUD DC CL16' ' MANUAL UPD CPU-ID
DYNMSYS DC CL8' ' MANUAL UPD OPERATING SYSTEM
DYNMPART DC CL2' ' MANUAL UPD PARTITION
DYNMCPU DC CL8' ' MANUAL UPD CPU ID
DYNMCPUA DC CL1' ' MANUAL UPD CPU ID (FROM CPUPROF)
DYNMCDE DC CL1' ' MANUAL UPD FUNCTION CODE
DYNCOM DC CL100' ' COMMENT ASSOCIATED WITH THIS DATASET
DYNOIMSG DC CL70' ' OPEN INPUT MESSAGE

DYNOIRTC DC CL1' ' OPEN INPUT ROUTING CODE

DYNOOMSG DC CL70' ' OPEN OUTPUT MESSAGE
DYNOORTC DC CL1' ' OPEN OUTPUT ROUTING CODE
DYNCIMSG DC CL70' ' CLOSE INPUT MESSAGE
DYNCIRTC DC CL1' ' CLOSE INPUT ROUTING CODE
DYNCOMSG DC CL70' ' CLOSE OUTPUT MESSAGE
DYNCORTC DC CL1' ' CLOSE OUTPUT ROUTING CODE
DYNPRIOR DC CL44' ' PRIOR FILE NAME
DYNFOLOW DC CL44' ' SUBSEQUENT FILE NAME
DYNFIRST DC CL44' ' NAME OF 1ST FILE IN MULTI-FILE SET
DYNSYSNO DC CL6' ' OVERRIDING LOGICAL UNIT
DYNVOLID DC CL2' ' VOLID
DYNLGEN DC CL6' ' CURRENT LONG GENERATION ID
DYNVROT DC CL100' ' SPECIFIED VAULT ROTATION
DYNDBRLN EQU *-DYNDBREC LENGTH DATASET BASE RECORD SEGMENT
***************************************************************
* DYNGBREC -- GENERATION / VERSION BASE RECORD SEGMENT *
***************************************************************
DYNGBREC EQU * VERSION INFORMATION
DYGDSORG DC CL4' ' DATASET ORGANIZATION THIS VERSION
DYGRECFM DC CL3' ' RECORD FORMAT THIS VERSION
DYGBLKSZ DC PL3'0' BLOCKSIZE FOR THIS VERSION
DYGLRECL DC PL3'0' LOGICAL RECORD LENGTH THIS VERSION
DYGKEYLN DC PL3'0' KEY LENGTH THIS VERSION
DYGRKP DC PL3'0' RELATIVE KEY POSITION THIS VERSION
DYGBUFNO DC PL2'0' NUMBER OF BUFFERS
DYGBFTEK DC CL1' ' BUFFER TECHNIQUE
DYGBFALN DC CL1' ' BUFFER ALIGNMENT
DYGPOPT0 DC CL8' ' PROCESSING OPTIONS BYTE 0
DYGDOPT0 DC CL8' ' DISK OPTIONS BYTE 0
DYGDOPT3 DC CL8' ' DISK OPTIONS BYTE 3 - RESERVED
DYGTOPT0 DC CL8' ' TAPE OPTIONS BYTE 0
DYGTOPT3 DC CL8' ' TAPE OPTIONS BYTE 3 - RESERVED
DYGREELS DC CL2' ' SPECIFIED REEL SIZE
DYGEXDTE DC PL4'0' EXPIRATION DATE (JULIAN)
DYGEDATE DC CL8' ' EXPIRATION DATE (GREGORIAN)
DYGRETN DC PL3'0' NUMBER OF DAYS RETENTION
DYGVAULT DC CL1' ' VAULT LOCATION THIS VERSION
DYGPED DC CL8' ' PERIOD ENDING DATE THIS VERSION
DYGGENID DC CL2' ' GENERATION ID FOR THIS VERSION
DYGGDGID DC CL8' ' OS GDG ID FOR THIS VERSION
10–28 User Guide

DYGOWNID DC CL2' ' OWNER ID CODE FOR DSN

DYGSYSID DC CL2' ' SYSTEM ID CODE FOR DSN
DYGUSRID DC CL2' ' USER ID CODE FOR DSN
DYGSTAT0 DC CL8' ' DATASET STATUS FLAG 1
DYGVOLS DC PL2'0' NUMBER OF VOLUMES THIS VERSION
DYGEXTS EQU DYGVOLS NUMBER OF EXTENTS THIS VERSION
DYGFILSQ DC PL2'0' ACTUAL FILSEQ NUMBER THIS VERSION
DYGCONV DC XL2'00' USED FOR CONVERSIONS
DYGIOPNS DC PL5'0' NUMBER OF INPUT OPENS THIS VERSION
DYGOERRS DC PL5'0' NUMBER OF WRITE ERRORS
DYGIERRS DC PL5'0' NUMBER OF READ ERRORS
DYGBLKS DC PL5'0' NUMBER OF BLOCKS THIS VERSION (TAPE)
DYGNTRKS EQU DYGBLKS NUMBER OF TRACKS THIS VERSION (DISK)
DYGMODE DC CL2' ' MODE SET
DYGMODE2 DC CL4' ' MODE SET
DYGCDTE DC PL4'0' CREATION DATE (JULIAN)
DYGCDAT DC CL8' ' CREATION DATE (GREGORIAN)
DYGCTIM DC PL4'0' CREATION TIME (0HHMMSS)
DYGCJOB DC CL8' ' CREATION JOB NAME
DYGCPROC DC CL8' ' CREATION PROCEDURE NAME
DYGCCPUD DC CL16' ' CREATION CPU-ID
DYGCSYS DC CL8' ' CREATION OPERATING SYSTEM
DYGCSTP DC CL8' ' CREATION STEP NAME
DYGCPART DC CL2' ' CREATION PARTITION
DYGCCPU DC CL8' ' CREATION CPU-ID
DYGCCPUA DC CL1' ' CREATION CPU ID (FROM CPUPROF)
DYGCDVCL DC CL5' ' CREATION DEVICE CLASS
DYGCCUU DC CL3' ' CREATION DEVICE ADDRESS
DYGADTE DC PL4'0' LAST ACCESS DATE (JULIAN)
DYGADAT DC CL8' ' LAST ACCESS DATE (GREGORIAN)
DYGATIM DC PL4'0' LAST ACCESS TIME (0HHMMSS)
DYGAJOB DC CL8' ' LAST ACCESS JOB NAME
DYGAPROC DC CL8' ' LAST ACCESS PROCEDURE NAME
DYGACPUD DC CL16' ' LAST ACCESS CPU-ID
DYGASYS DC CL8' ' LAST ACCESS OPERATING SYSTEM
DYGACUU DC CL3' ' LAST ACCESS DEVICE ADDRESS
DYGASTP DC CL8' ' LAST ACCESS STEP NAME
DYGAPART DC CL2' ' LAST ACCESS PARTITION
DYGACPU DC CL8' ' LAST ACCESS CPU-ID
DYGACPUA DC CL1' ' LAST ACCESS CPU ID (FROM CPUPROF)
DYGMDTE DC PL4'0' LAST MANUAL UPD DATE (JULIAN)
DYGMDAT DC CL8' ' LAST MANUAL UPD DATE (GREGORIAN)
DYGMTIM DC PL4'0' LAST MANUAL UPD TIME (0HHMMSS)
DYGMJOB DC CL8' ' LAST MANUAL UPD JOB NAME
DYGMPROC DC CL8' ' LAST MANUAL UPD PROCEDURE NAME
DYGMCPUD DC CL16' ' LAST MANUAL UPD CPU-ID
DYGMSYS DC CL8' ' LAST MANUAL UPD OPERATING SYSTEM

DYGMCDE DC CL1' ' LAST MANUAL UPDATE FUNCTION CODE

DYGMSTP DC CL8' ' LAST MANUAL UPDATE STEP NAME
DYGMPART DC CL2' ' LAST MANUAL UPDATE PARTITION
DYGMCPU DC CL8' ' LAST MANUAL UPDATE CPU-ID
DYGMCPUA DC CL1' ' LAST MANUAL UPDATE CPU ID (CPUPROF)
DYGBLKID DC CL8' ' BLOCK ID - CARTRIDGE TAPE POSITION
DYGBLKPR DC PL2'0' CARTRIDGE PHYSICAL REFERENCE
DYGBLKLR DC PL5'0' CARTRIDGE LOGICAL REFERENCE
DYGABSID DC PL5'0' ABSOLUTE VERSION ID
DYGLGEN DC CL6' ' LONG GEN ID FOR THIS VERSION
DYGNVOL DC PL2'0' NUMBER VOLUMES/EXTENTS RETURNED
DYNGBRLN EQU *-DYNGBREC LENGTH GENERATION RECORD SEGMENT
***************************************************************
* DYNVBREC -- VOLUME / EXTENT BASE RECORD SEGMENT *
***************************************************************
DYNVBREC EQU * EXTENT/VOLUME INFORMATION
DYVCDVTP DC CL6' ' DEVICE TYPE
DYVVOL DC CL6' ' VOLUME SERIAL OF THIS EXTENT/VOLUME
DYVEINFO EQU * SPECIFIC DISK INFO
DYVSEQ DC PL2'0' EXTENT SEQUENCE NUMBER (DISK)
DC XL4'00' RESERVED
DYNEXTLN EQU *-DYNVBREC LENGTH DISK ENTRY SEGMENT
ORG DYVEINFO
DYVTINFO EQU * SPECIFIC TAPE INFO
DYVOWNID DC CL2' ' OWNER OF THIS VOLUME
DYVVAULT DC CL1' ' VAULT LOCATION OF THIS VOLUME
DYVSLOT DC PL3'0' VAULT SLOT OF THIS VOLUME
DYVREELS DC CL2' ' REEL SIZE OF THIS VOLUME
DYVMODE DC CL2' ' MODESET OF THIS VOLUME
DYVMODE2 DC CL4' ' MODESET OF THIS VOLUME
DYVSTAT DC CL1' ' CURRENT STATUS OF VOLUME
DYVSTATC EQU C'C' ACTIVE VERSION
DYVSTATD EQU C'D' MANUALLY DELETED
DYVSTATL EQU C'L' CREATED WHEN LOCKED
DYVSTATM EQU C'M' MANUALLY CATALOGGED
DYVSTATO EQU C'O' OPENED NOT CLOSED
DYVSTATS EQU C'S' SCRATCH
DYVSTATT EQU C'T' CREATED BY $TEST JOB
DYVSTAT0 DC CL8' ' VOLUME STATUS BYTE 0
DYVVOLSQ DC PL3'0' VOLUME SEQUENCE NUMBER
DYVNFILE DC PL2'0' NUMBER OF ACTIVE FILES on VOLUME
DYVOOPNS DC PL5'0' NUMBER OF OUTPUT OPENS on VOLUME
DYVIOPNS DC PL5'0' NUMBER OF INPUT OPENS on VOLUME
DYVOERRS DC PL5'0' NUMBER OF WRITE ERRORS on VOLUME
DYVIERRS DC PL5'0' NUMBER OF READ ERRORS on VOLUME
DYVDINIT DC PL4'0' DATE VOL FIRST INITIALIZED (JULIAN)
DYVDRINT DC PL4'0' DATE VOL LAST INITIALIZED (JULIAN)
DYVDTSCR DC CL8' ' DATE VOL LAST SCRATCHED (GREGORIAN)
DYVDSCR DC PL4'0' DATE VOL LAST SCRATCHED (JULIAN)
10–30 User Guide

DYVDCLN DC PL4'0' DATE VOL LAST CLEANED (JULIAN)

DYVRSCR DC CL1' ' REASON CODE FOR LAST SCRATCH
DYVRSCRB EQU C' ' SCRATCHED ONLINE
DYVRSCRD EQU C'D' DATASET DELETED
DYVRSCRM EQU C'M' MANUALLY SCRATCHED
DYVRSCRO EQU C'O' OPENED BUT NOT CLOSED
DYVRSCRS EQU C'S' DYNCAT SCRATCH FUNCTION
DYVRSCRT EQU C'T' CREATED BY $TEST JOB
DYVRSCRW EQU C'W' WORK TAPE RELEASED
DYVADTE DC PL4'0' LAST ACCESS DATE (JULIAN)
DYVADAT DC CL8' ' LAST ACCESS DATE (GREGORIAN)
DYVATIM DC PL4'0' LAST ACCESS TIME (0HHMMSS)
DYVAJOB DC CL8' ' LAST ACCESS JOB NAME
DYVASTP DC CL8' ' LAST ACCESS STEP NAME
DYVAPART DC CL2' ' LAST ACCESS PARTITION
DYVACPU DC CL8' ' LAST ACCESS CPU-ID
DYVACPUA DC CL1' ' LAST ACCESS CPU ID (FROM CPUPROF)
DYVAPROC DC CL8' ' LAST ACCESS PROCEDURE NAME
DYVACPUD DC CL16' ' LAST ACCESS CPU-ID (PRINTABLE)
DYVASYS DC CL8' ' LAST ACCESS OPERATING SYSTEM
DYVACUU DC CL3' ' LAST ACCESS DEVICE ADDRESS
DYVTCLN DC PL3'0' THRESHOLD COUNT FOR CLEAN
DYVEXOWN DC CL1' ' ID OF OTHER TAPE MGR
DYVBLKID DC CL8' ' BLOCK ID - CARTRIDGE TAPE POSITION
DYVBLKPR DC PL2'0' CARTRIDGE PHYSICAL REFERENCE
DYVBLKLR DC PL5'0' CARTRIDGE LOGICAL REFERENCE
DYVCOM DC CL100' ' COMMENT FOR THIS VOLUME
DYNVBRLN EQU *-DYNVBREC LENGTH TAPE ENTRY SEGMENT
DYNCOMLN EQU *-DYNSTAMP LENGTH BASIC DYNINFO
DC (6709-DYNCOMLN)X'00' ROOM FOR MORE VBRS
DYNINFLN EQU *-DYNSTAMP TOTAL LENGTH OF DYNINFO
DYNNVBRS EQU (6709-DYNCOMLN)/DYNVBRLN+1 NUMBER VBRS FIT
***************************************************************
* END OF DYNINFO DSECT *

Chapter 11: CAIAUDIT in Prompt Mode
CAIAUDIT is a comprehensive logging and reporting facility for a variety of CA
products. The AUDIT run-time system performs the actual logging of data to
the CAIAUDIT data sets. All CAIAUDIT records can be viewed on directory or
detail panels.
This chapter explains how to use CAIAUDIT in prompt mode and shows you
how to display the following:
A directory of all records logged to the CAIAUDIT data sets
A directory of specific records

A record in detail
Primary Selection Panel (CUI-MENU)

This panel lists all of the options available to a particular user within the CUI
transaction. System Administrators are responsible for defining this panel for
each user.
CUI-MENU Primary Selection Panel CAICUI

====>
Enter desired option number or any valid command and press ENTER:
1. CUI Session Status Selection
2. CUI Maintenance
3. Event Notification Selection
4. Event Notification Maintenance
1=Help 2= 3=Quit 4= 5= 6=
To select a menu option, enter the desired menu number and press ENTER, or
tab down to the desired option and press ENTER.
Chapter 11: CAIAUDIT in Prompt Mode 11–1

AUDIT Data Set Browse Selection Panel (AUDT-1000)

This panel lets you specify what CAUDPCn records you want to display. You
can select a record or group of records by entering data specific to the
desired record or group of records in these selection and relation fields.
CAICUI uses this information to browse the specified CAUDPCn data set from
the first to last record and redisplays a directory of all entries that match the
specified information.
If no criterion is entered, all records in the current CAUDPCn data set are
displayed on the AUDIT Data Set Directory Panel - All Products (AUDT-1100).
AUDT-1000 AUDIT Data Set Browse Selection CA AUDIT

====>
Enter the desired selection criteria and press the ENTER key.
Relation Selection
CAUDPCn: _ Specify Data Set to Browse (1,2)
Product: ____ Product code
Event: __ ____ Event code
Date: __ ______ Date of event (MMDDYY)
Time: __ ______ Time of event (HHMMSS)
Userid: __ ________ User identification
Facility: __ ________ Facility identification
Severity: __ _ Severity code
Name: __ ________ Name identification
Misc: __ ____________________ Miscellaneous
CPU: __ __ Relative CPU number
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
For example, enter a valid CAIAUDIT-assigned product code on this panel to

display a product-specific AUDIT data set directory panel. For more
information about a list of valid product codes, see the appendix, “CA Dynam
Report Examples.”
Selection Field Descriptions
CAUDPCn Specify a data set. The default is the current CAUDPCn data set.
Product Specify a product code. For more information about a list of valid product
codes, see the Installation Guide.
Event Specify an event code. For more information about a list of valid event codes,
see the Message Guide.
Date Specify a date.
Time Specify a time.
Userid Specify a user ID.
11–2 User Guide

Facility Specify a facility ID. Depending upon the product, it can be a terminal ID,
partition ID or VTAM application ID.
Severity Specify a severity code. Valid severity codes are:
A Abend
E Error
I Informational
W Warning
Name Specify a Job name.
Misc Specify any miscellaneous event information.
CPU Specify a CPU ID.

AUDIT Data Set Directory Panel—All Products (AUDT-1100)

This panel displays one line of information for each record contained in the
CAUDPCn data set currently being browsed. It is displayed if no product code
is specified on the AUDIT Data Set Browse Selection Panel (AUDT-1000).
AUDT-1100 AUDIT Data Set Directory - All Products CA AUDIT

====>
Cmd Date Time Prod Evnt User Fac ID Sev Name CPU
Miscellaneous
___ 06/06/00 11:11:36 DYNT UTIL CA Dynam F3 I PAWS 01

___ 06/06/00 11:12:28 DYNT OPEN CA Dynam BG I CART 01
___ 06/06/00 11:12:38 DYNT CLOS CA Dynam BG I CART 01
___ 06/06/00 12:37:35 DYND OPEN CA Dynam BG I DISKOUT 01
___ 06/06/00 12:37:44 DYND CLOS CA Dynam BG I DISKOUT 01
__ __ = __ __ __ __ __ __ __
==> ______ ______ ____ ____ ________ ________ _ ________ __
_____________
1=Help 2= 3=Quit 4= 5= 6=
Select a record for detail display
Use local commands
Date The date the event occurred. Also a selection field.
Time The time the event occurred. Also a selection field.
Prod The CAIAUDIT-assigned product code of the product that logged the event.
Also a selection field. For more information about a list of valid product codes,
see the Installation Guide.
Evnt The event code of the event that occurred. Also a selection field. For more
information about a list of valid event codes, see the Message Guide.
User The user ID associated with the event that occurred. Also a selection field.
11–4 User Guide

Fac ID The facility ID of the event that occurred. Depending upon the product, the
facility ID is a terminal ID, partition ID, or VTAM application ID. Also a
selection field.
Sev The severity code of the event that occurred. Also a selection field. Valid
severity codes are:
A Abend
E Error
I Informational
W Warning
Name The name associated with the event that occurred. Also a selection field.
CPU The relative ID of the CPU where the event occurred. Also a selection field.
Misc Any miscellaneous event information. Also a selection field.
Local Commands
Short Commands
DSP Display in detail all available information contained in a specific record. Enter
DSP in the short command area on the same line as the desired record or if no
other short commands have been entered, position the cursor anywhere on
the line of the desired record and press ENTER.

AUDIT Data Set Directory Panel—CA Dynam/T (AUDT-1900)

This panel displays one line of information for each DYNAM/T record logged to
the CAUDPCn data set currently being browsed when DYNT is specified as the
product code on the AUDIT Data Set Browse Selection Panel (AUDT-1000).
AUDT-1900 AUDIT Data Set Directory - CA Dynam/T CA AUDIT

====>
CMD EVENT DATE TIME PID JOBNAME PHASENAME DATASET NAME

CODE
___ UTIL 06/06/00 10:31:50 BG UTIL DYNCAT TAPEUTIL

___ OPEN 06/06/00 10:31:54 BG TEST1 DTTEST TAPE.FILE
___ CLOS 06/06/00 10:32:11 BG TEST1 DTTEST TAPE.FILE
___ UTIL 06/06/00 10:34:41 BG UTILTST DYNCAT TAPEUTIL
___ OPEN 06/06/00 10:34:46 BG EOVTEST DTTEST TAPE
___ EOV 06/06/00 10:35:13 BG EOVTEST DTTEST TAPE
___ OPEN 06/06/00 10:35:23 BG EOVTEST DTTEST TAPE
___ CLOS 06/06/00 10:35:32 BG EOVTEST DTTEST TAPE
___ OPEN 06/06/00 10:49:45 BG TEST3 DTTEST TAPE
__ __ __ __ __ __ __
==> ____ ______ ______ __ ________ ________ _________________
1=Help 2= 3=Quit 4= 5= 6=
Use local commands
Cmd Use this area to enter short commands
11–6 User Guide

Event Code The event code of the event that occurred. Also a selection field. For more
Time The Time the event occurred. Also a selection field.
PID The Partition (Syslog ID) that the event occurred in. Also a selection field.
Jobname The Jobname of the job that the event occurred in. Also a selection field.
Phasename The name of the Phase that was executing when the event occurred. Also a
selection field.
Dataset Name The name of the data set that was being processed when the event occurred.
Also a selection field. This field may appear as blanks if the label has not been
processed at the time the audit entry has been logged or in the case of some
job control opens, and so on.
Local Commands

AUDIT Data Set Detail Panel—DYNAM/T (AUDT-1910)
Short Commands
DSP in the short command area on the same line as the desired record or if no
other short commands have been entered, position the cursor anywhere on
the line of the desired record and press ENTER.
AUDIT Data Set Detail Panel—DYNAM/T (AUDT-1910)

This panel is displayed when a CA Dynam/T event is selected for detail display
for all event codes except UTIL.
AUDT-1910 AUDIT Data Set Detail - CA Dynam/T CA AUDIT

====>
Event code: OPEN Description: Tape file open

Date: 06/06/00 Time: 10:31:54
Dataset name: TAPE

Jobname: EOV Phasename: DTTEST
Dtfname: UOUT Partition: BG CPUid: FF00005530900000
Assigned via: AVR Typefle: OUTPUT CPU: A
Logical unit: SYS011 Device addr: 0181 Ctrld: YES
Create date: 06/06/00 Expire date: Vault: A
VOLUME INFORMATION:
Volser: 000026 Volume seq: 1 Filseq: 1
Owner id: Reel size: Mode:
Block size 20000 Record size: 2000 Recfm: FB
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
11–8 User Guide

AUDIT Data Set Detail Panel—CA Dynam/T (AUDT-1920)
AUDIT Data Set Detail Panel—CA Dynam/T (AUDT-1920)

This panel is displayed when a CA Dynam/T event with an event code of UTIL
is selected for detail display.
AUDT-1920 AUDIT Data Set Detail - CA Dynam/T CA AUDIT

====>
Event code: UTIL Description: Dynam/T utility command audit entry

Date: 06/06/00 Time: 10:31:50
Dataset name: TAPE

Jobname: EOV Phasename: DYNCAT CPU: A
Volume: 000026 Partition: BG CPUid: FF00005530900000
Volume seq:
Dyncat control statement:
DEL 'TAPE' ALL
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
AUDIT Data Set Directory Panel—CA Dynam/D (AUDT-1A00)

This panel displays one line of information for each Dynam/D record logged to
the CAUDPCn data set currently being browsed when DYND is specified as the
product code on the AUDIT Data Set Browse Selection Panel (AUDT-1000)
AUDT-1A00 AUDIT Data Set Directory - CA Dynam/D CA AUDIT

====>

CODE
___ OPEN 06/06/00 10:50:24 BG CAAU $JOBACCT CPU-A.BG.SYSLNK.W

___ CLOS 06/06/00 10:50:27 BG CAAU $JOBACCT
___ OPEN 06/06/00 10:50:28 BG CAAU LNKEDT CPU-A.BG.SYSLNK.W
___ CLOS 06/06/00 10:50:31 BG CAAU LNKEDT CPU-A.BG.SYSLNK.W
___ OPEN 06/06/00 12:37:35 BG DISKOUT DDTEST DISK.5XTNTS
___ CLOS 06/06/00 12:37:44 BG DISKOUT DDTEST DISK.5XTNTS
___ OPEN 06/06/00 12:38:22 BG DISKOUT DDTEST DISK.4450
__ __ __ __ __ __ __
==> ____ ______ ______ __ ________ ________ _________________
1=Help 2= 3=Quit 4= 5= 6=

AUDIT Data Set Directory Panel—CA Dynam/D (AUDT-1A00)
Use local commands
selection field.
processed at the time the audit entry has been logged or in the case of some
job control opens.
Local Commands
Short Commands
DSP in the short command area on the same line as the desired record or, if
no other short commands have been entered, position the cursor anywhere
on the line of the desired record and press |ENTER|.
11–10 User Guide

AUDIT Data Set Detail Panel—CA Dynam/D (AUDT-1A10)
AUDIT Data Set Detail Panel—CA Dynam/D (AUDT-1A10)

This panel is displayed when a CA Dynam/D event is selected for detail
display.
AUDT-1A10 AUDIT Data Set Detail - CA Dynam/D CA AUDIT

====>
Event code: OPEN Description: Disk file open

Date: 06/06/00 Time: 10:50:24
Dataset name: CPU-A.BG.SYSLNK.WORK

Jobname: CAAU Phasename: $JOBACCT
Dtfname: IJSYSLN Partition: BG CPUid: FF00005530900000
DTF type: DTFCP(32) Typefle: OUTPUT CPU: A
DTF log unit: SYSLNK Device addr: 0140 Ctrld: YES
Orig Alloc: 60 Actual: 60
Processing Completion Information: open/close successful

EXTENT INFORMATION - Rel Number
Volser Type Seq trk/blk trk/blks Lub
Original - 338000 DATA 0 1 60 SYSLNK
Updated - 338000 DATA 0 2 60 SYSLNK
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit

AUDIT Data Set Directory Panel—CA Dynam/FI (AUDT-1B00)

This panel displays one line of information for each Dynam/FI record logged to
the CAUDPCn data set currently being browsed when DYNF is specified as the
product code on the AUDIT Data Set Browse Selection Panel (AUDT-1000)
AUDT-1B00 AUDIT Data Set Directory - CA Dynam/FI CA AUDIT

====>

CODE
___ GENL 06/07/00 14:16:45 BG FITAPE DDTEST FI

___ GENL 06/07/00 14:18:21 BG FITAPE DDTEST FITEST
___ GENL 06/10/00 12:18:43 BG FITAPE DTTEST FI.AUD.TEST
___ GENL 06/10/00 12:40:24 BG FITAPE DTTEST FI.AUD.TEST
___ GENL 06/10/00 12:47:27 BG FITAPE DDTEST FI2
___ GENL 06/10/00 16:01:12 BG FITAPE DDTEST FI2
__ __ __ __ __ __ __
==> ____ ______ ______ __ ________ ________ _________________
1=Help 2= 3=Quit 4= 5= 6=
Use local commands
selection field.
11–12 User Guide

processed at the time the audit entry has been logged, in the event of some
job control opens, and so on.
Local Commands
Short Commands
DSP in the short command area on the same line as the desired record or, if
no other short commands have been entered, position the cursor anywhere
on the line of the desired record and press |ENTER|.

AUDIT Data Set Detail Panel—CA Dynam/FI (AUDT-1B10)
AUDIT Data Set Detail Panel—CA Dynam/FI (AUDT-1B10)

This panel is displayed when a CA Dynam/FI event is selected for detail
display:
AUDT-1B10 AUDIT Data Set Detail - CA Dynam/FI CA AUDIT

====>
Event code: GENL Description: Dynam/Fi accepted for processing

Date: 06/07/00 Time: 14:16:45
Dataset name: FI
Jobname: FITAPE Phasename: DDTEST CPU: A
Dtfname: UOUT Partition: BG CPUid: FF00005530900000
Device asgnd: 3380 Typefle: OUTPUT Lub: SYS130
Volser: 338000
DTF information: Varbld

DTF Block Buffer /Recsz
type Recfm Size Lrecl Tech. Ioreg Worka Reg
Original: SD-20 FB 500 100 DOUBLE NO YES NO
Generated: SD-20 FB 500 100 DOUBLE NO YES NO
1=Help 2= 3=Quit 4= 5= 6=
7= 8= 9= 10= 11= 12=Exit
CAIAUDIT in Command Mode

This section explains how to use CAIAUDIT in command mode. There are
essentially two commands that can be used to display CAIAUDT panels. Both
contain the optional prefix AUDIT: it may sometimes be required to specify
with which product or component the command is associated (that is, to
distinguish it from similar product or component commands). Consult the
System Administrator for details.
SELECT AUDITRECORDS
SELECT AUDITRECORDS displays the CAIAUDIT Data Set Browse Selection

Panel (AUDT-1000), from which you can select specific CAIAUDIT records.
Type Global
AUDIT SELect AUDITRECORDS
The AUDIT prefix is optional on this command. It is sometimes necessary to

specify with which product the command is associated. The command
executes with or without the AUDIT prefix.
11–14 User Guide

Example
The following command displays the CAIAUDIT Data Set Browse Selection
Panel (AUDT-1000):
SEL AUDIT RECORDS
DISPLAY AUDIT
DISPLAY AUDIT selects specific CAIAUDIT records for display on a directory

panel.
Type
Global
AUDIT Display AUDIT [PRODUCT=ALL|product]

[DSN=1|2]
[CPU=nn]
[DATE=mmddyy|ddmmyy]
[EVENT=eventcode]
[FACILITY=facility]
[MISC=miscellaneous]
[SEVERITY=A|E|I|W]
[TIME=hhmmss]
[USERID=userid]
The AUDIT prefix is optional on this command. It is sometimes necessary to

specify with which product the command is associated. The command
executes with or without the AUDIT prefix.
Required Operand
The following operand is required.
AUDIT Specify that CAIAUDIT records are to be displayed.
Optional Operands
The following operands are optional.
PRODUCT=ALL|product Specify the product code of the record(s) to be displayed. Only one product
can be specified at a time. Fore more information about a list of valid product
codes, see the Installation Guide. The default is ALL.

DSN=1|2 Specify the data set to be browsed. The default is the data set currently being
logged. Choose one of the following:
1 CAUDPC1
2 CAUDPC2
CPU=nn Specify the relative CPU number of the record(s) to be displayed. It can be
any number from 1 to 32.
DATE=mmddyy|ddm Specify the date of the record(s) to be displayed, using the format specified
myy in the AUDIT Control Options Panel (AUDM-1000).
EVENT=eventcode Specify the event code of the record(s) to be displayed. For more information
about a list of valid event codes, see the Message Guide.
FACILITY=facility Specify the facility ID of the record(s) to be displayed.
MISC=miscellaneous Specify any informational text.
SEVERITY=A|E|I|W Specify the severity code of the record(s) to be displayed. Valid severity codes
are:
A Abend
E Error
I Informational
W Warning
TIME=hhmmss Specify the time of the record(s) to be displayed.
USERID=userid Specify the user ID associated with the record(s) to be displayed.
Example
The following command displays all CA Dynam/D records with the event code
OPEN:
D AUDIT,PRODUCT=DYND,EVENT=OPEN
11–16 User Guide

Batch Reporting for CAJAUDIT
Batch Reporting for CAJAUDIT

CAIAUDIT’s extensive reporting capabilities are facilitated by CA EARL, a utility
that generates reports for all CA products using CAIAUDIT. In addition to the
standard reports provided with CAIAUDIT, customized reports can also be
created using CA EARL.
The copybook needed to generate a specific product’s CAIAUDIT EARL Report

was cataloged to the library defined as a 0 (zero) book during installation. The
copybooks for all CA products using CAJAUDIT can be found in this library with
the prefix CAAU.
Printable Fields
The following tables list the printable fields that can be used for:
CAIAUDIT
CA DYNAM/T
CA DYNAM/D
CA DYNAM/FI
CA DYNAM/T Header Fields
Name Length Description
CADTE 8 Header date (part of

CAIAUDIT key)
CATME 8 Header time (part of

CAIAUDIT key)
CAPRD 4 Header product code
CAPEC 4 Header event code
CAUID 8 Header user ID
CACPR 2 Header CPU ID
CASID 2 Header system ID
CAFID 8 Header facility ID
CASVC 1 Header severity code
CANAM 8 Header job name

Printable Fields
CAINF 20 Header miscellaneous

information
CASVCP 13 Header severity code

(additional detail)
CACFL1 20 Header control flag

(alphabetic)

(numeric)
CAPRDP 19 Header product code

(additional detail)

CAIAUDIT key)

CAIAUDIT key)

information

(additional detail)

(alphabetic)

(numeric)

(additional detail)
11–18 User Guide

Printable Fields
CA DYNAM/FI Header Fields

CAIAUDIT key)

CATAUDIT key)

information

(additional detail)
CACFLI 20 Header control flag

(alphabetic)

(numeric)

(additional detail)

Chapter 12: Maintaining and Reporting
on the Audit Trail
The CA Dynam Audit Trail facility, AUDTUTIL, gives you a permanent record of
CA Dynam file management activity. Each time CA Dynam processes a file, or
whenever any batch or online update is made to the Catalog, an Audit record
is logged (added) to the Audit Trail disk file. An Audit Trail reporting program
is also supplied; it lets you produce both predefined and customized reports.
The Audit Trail facility records the following details about file OPEN/CLOSE
processing:
Data set name
File name
Job and phase name
File and volume sequence number
Version number
System date
Time of processing
Exceptional occurrences, such as operator responses of ACCEPT, RERUN,

or CANCEL
All maintenance performed on the CA Dynam Catalog
This is a complete auditing facility, designed to increase security and efficiency

for your installation. For instance, you can generate reports to track various
conditions regarding file use and track unauthorized access to data files, or
locate and correct bottlenecks.
The Audit Trail facility also records internal Catalog recovery information.
Therefore, you can use this facility to recreate or recover the CA Dynam
Catalog if it is destroyed or corrupted; no information relating to file
management activity is lost.
Chapter 12: Maintaining and Reporting on the Audit Trail 12–1

Maintaining the Audit Trail File
The Audit Trail report generator lets you design your own reports by specifying
the following criteria:
Page and heading titles
Selecting records and fields to be reported upon with easy-to-use

keywords and selection logic
Several predefined reports are also provided. For more information about
predefined reports, see the appendix, “Audit Trail Report Examples.”
The Audit Trail Facility - AUDTUTIL
You can run the Audit Trail facility in either basic or extended mode.
BASIC mode only performs logging of Catalog recovery information. You

may use the Catalog recovery facility with this mode, but none of the
reporting facilities will be available. The logmode is set when the Audit
data set is initialized and may be modified at any time by the AUDTUTIL
DATASET command.
Run the Audit system in LOGMODE=EXTENDED if you require audit reports

concerning file management activity.
Audit Trail Logging
The system option records for DYNAM, DYNAM/D, DYNAM/T, and DYNAM/FI
provide several options through which you can control the level and amount of
logging performed by the Audit subsystem in each CA Dynam subset. This
control gives you maximum flexibility with minimum overhead. For more
information about option records, see the Programming Guide.
Creating Audit Trail Records
Audit records will be created under a wide variety of conditions, depending

upon the option record settings. If you specify the most extensive auditing,
the following conditions will produce reportable audit records:
A tape or disk file (controlled or uncontrolled) is opened or closed.
An end-of-volume condition occurs on tape (controlled or uncontrolled).
12–2 User Guide

An exceptional condition occurs for a file:
− ACCEPT of a tape file
− ALTER of the specified tape file
− RERUN of the current tape file
− use of a 'locked' file
− unlabeled tape processing
− uncontrolled tape processing
− CANCEL response to a CA Dynam message
− V= response
− recovery delete response

− automatic GDG deletion
− operator allocation change
− password violation
A DYNCAT utility command is entered, causing the Catalog to be modified

(including the SCRATCH function).
CA Dynam/FI is used to modify the characteristics of a DTF for processing

or the FI 'AUDIT' option is used on a file which is not modified.
The Audit Trail facility can report all of these conditions through the AUDTUTIL
report generator. It also logs special Catalog recovery entries whenever the
Catalog is modified. However, these are processed only during Catalog
recovery.
Whenever an Audit Trail record is created, the following information is noted:
Catalog record entry (new entries)
System date and time of processing
Job name, phase name
Partition ID
Tape or disk drive address
File name (DTFname)
Tape recording mode
Before logged file activity can be directed to the Audit Trail file, you must
initialize the file with the AUDTUTIL program's DATASET command.

Note:
A software enqueue/dequeue technique prevents multiple access of the

Audit Trail at any given time.
The Audit Trail file must be a single extent file. Messages are written to
SYSLOG as each ten-percent-full mark is reached. If the file fills up,
logging stops and audit entries are lost until a BACKUP of the file is
performed. CA Dynam records the number of entries lost.
Using the Catalog Recovery Facility
The CA Dynam Catalog Recovery facility enables you to recreate the Catalog
file in the event of disaster. Using a previous BACKUP tape of the file in
conjunction with the Audit Trail file, you can recover the Catalog without
concern for system integrity and reliability. CA Dynam uses an enqueue
technique that protects the Catalog during recovery from being updated by
any other jobs running on the system and programs running on other CPUs.
By default, only audit records created after the last BACKUP of the Catalog file
are considered during Catalog recovery. However, you can process multiple
backup tapes of the Audit Trail file. You may override the starting date and
time from which Audit Trail records are selected for processing.
Catalog recovery is a two-step process:
1. Issue the DYNCAT RESTORE command to restore the latest backup of the
Catalog file to disk. Be careful not to issue a RESTORE REORG; this resets
pointers required by the recovery function and should only be used if
recovery is not possible after a RESTORE.
2. Issue the AUDTUTIL CATALOG RECOVERY command. This permits you to

load selected Audit Trail records from a backup tape of the Audit Trail file,
the Audit Trail file itself, or both. You can also write the Audit Trail disk file
to tape by issuing the AUDTUTIL BACKUP command. For more information
about CATALOG RECOVERY and BACKUP commands, see Maintenance
Commands.
Note: The Audit facility is designed for Catalog recovery from a catastrophic
loss. If you suspect a noncritical or logical Catalog error, execute the DYNCAT
BACKUP, RESTORE REORG, and SCRATCH functions to correct the Catalog
error instead. Audit recovery is unnecessary under these circumstances;
RESTORE REORG resolves noncritical problems.
12–4 User Guide

AUDTUTIL Control Statement Syntax
AUDTUTIL Control Statement Syntax

The following rules apply to AUDTUTIL statement syntax:
Commands can begin in any position of the statement.
All operands are separated by one or more blanks.
Commands can continue onto a maximum of six continuation statements.

The first nonblank character on the next statement begins the next
operand.
Only positions 1-72 are examined by the AUDTUTIL program.
You can enter any number of Audit Trail commands, in any sequence, in a
single execution of the AUDTUTIL program.
All output is written to SYSLST except for some initial messages which are
displayed at the operator's console.
Continuation requires a nonblank character in position 72 of the statement

to be continued.
Commands may be issued from the console to dynamically generate audit

reports.
Maintenance Commands
AUDTUTIL enables you to perform various maintenance functions on the
accumulated Audit Trail data. The chart below lists each maintenance
command and briefly describes its functions.
This Command Performs These Functions
BACKUP Backs up the Audit Trail file, merging the data to a

history tape, then clearing the disk data set of all
active entries.
CATALOG RECOVERY Updates an existing Catalog file with information from

the Audit Trail data set.
DATASET Initializes, reports on, unlocks, locks, and sets logging

support for the Audit Trail data set.

BACKUP Command
The BACKUP command writes the Audit Trail file to the tape mounted on the
drive assigned to logical unit SYSnnn.
BACKUP [ ADD [INPUT=SYSnnn] [TAPE=SYSnnn] ]

[ ]
[ INITIALIZE [DISP=KEEP] [TAPE=SYSnnn] ]
ADD Required if using other optional parameters. Copies the period-to-date audit
information from the input (previous period-to-date tape) to the output tape
and adds new information.
ADD is the default if only BACKUP is specified.
INITIALIZE Required if using other optional parameters. Initializes tape for output. The
Audit Trail data is written at the beginning of the tape.
INPUT=SYSnnn Optional parameter. If ADD is used, the input tape is assigned by logical unit
SYSnnn (default is SYS005.)
Note: ADD and INITIALIZE are mutually exclusive.
TAPE=SYSnnn Optional parameter. Assigns the output tape by logical unit SYSnnn (default is
SYS006).
DISP=KEEP Optional parameter. Ensures that the Audit Trail file is not cleared after the
BACKUP function is run. This operand is only valid on a BACKUP INITIALIZE
command. Use DISP=KEEP only for generating tapes for reporting and testing.
This reduces the possibility of creating multiple copies of the same data.
Examples
BACKUP INITIALIZE DISP=KEEP
BACKUP INITIALIZE TAPE=SYS008
BACKUP ADD INPUT=SYS010 TAPE=SYS011
Example Job Stream:
// JOB BACKUP
// ASSGN SYS006,181
// TLBL DYNHIST,'CA Dynam AUDIT'
// EXEC AUDTUTIL,SIZE=128K
BACKUP INITIALIZE TAPE=SYS006
/*
/&
12–6 User Guide

Note:
The Audit Trail file is reinitialized when the BACKUP is complete unless
DISP=KEEP is specified.
A TLBL for DYNHIST is required for the history tape.
A TLBL for DYNOLD is required for the ADD function for the input period-
to-date tape.
If the Audit Trail data set becomes full, perform a BACKUP immediately
records cannot be logged until the BACKUP is executed.
If the AUDTUTIL job cancels during a BACKUP, and the Audit data set has
been specified as SHARE=YES, execute the DATASET UNLOCK command.
The BACKUP function locks the Audit Trail file while it is writing the data
records to tape. The file is not unlocked until the BACKUP completes
successfully.
CATALOG RECOVERY Command
The CATALOG command recovers tape activity information lost from the
Catalog files. This command uses the information on the Audit Trail tape(s)
and Audit Trail disk file in order to update the existing Catalog file.
CATALOG RECOVERY [ TAPE=SYSnnn ]

[ MULTITAPE=n ]
[ NODISK ]
[ NOTAPE ]
[ LIST ]
[ DATE= {mm/dd/yy|dd/mm/yy } [TIME=hh.mm.ss] ]
TAPE=SYSnnn Optional parameter. Assigns the input Audit Trail tape by logical unit SYSnnn
(default is SYS005).
MULTITAPE=n Optional parameter. Specifies the number of logical Audit Trail backup files to
use in the recovery. The Catalog recovery reads the specified number of files.
This operand is not required for a single file which spans multiple volumes.
Catalog recovery supports end-of-volume conditions.
NODISK Optional parameter. Instructs CA Dynam not to process the Audit Trail disk file
after all Audit tapes are read. Use this operand with caution: entries contained
in the Audit disk file indicate the most recent CA Dynam activity.
NOTAPE Optional parameter. Instructs CA Dynam not to process any Audit Trail backup
tapes. Audit Trail information is read only from the Audit disk file.

LIST Optional parameter. Prints a listing of Catalog recovery operations as each

Catalog entry is recovered. A printed message indicates the Catalog function
performed, the data set name, volume serial number, version, volume
sequence when applicable.
DATE=mm/dd/yy or dd/mm/yy
Optional parameter. Indicates the starting date from which Audit Trail records
will be processed. All Audit records with an older date are ignored. Use this
operand with caution: the date you supply overrides the last 'backup' date,
which is contained in the Catalog time-stamp record (CCR).
Default: date and time of the last backup as indicated in the CCR for the
existing Catalog.
TIME=hh.mm.ss Optional parameter. Indicates the time of day (using a 24-hour clock) for the
first audit entry to be used in the Catalog recovery. You can include this
operand only if you also specify the DATE= operand. If you specify DATE=
without the TIME= operand, the default is 00.00.00.
Examples
CATALOG RECOVERY command examples are as follows:
(1) CATALOG RECOVERY TAPE=SYS005
(2) CATALOG RECOVERY MULTITAPE=3 DATE=01/01/00
Example 1 shows the following:
The Audit Trail tape is assigned to logical unit SYS005.
After the Audit backup tape file is processed, the Audit disk file is to be
processed.
Example 2 shows the following:
The Audit Trail tape is assigned to logical unit SYS005 by default.
Three Audit Trail history tapes are to be processed.
Only audit records with a date after January 1, 2000 are to be processed.
Example Job Stream
// JOB RECOVERY
// ASSGN SYS005,181
// TLBL DYNHIST
CATALOG RECOVERY NODISK LIST TAPE=SYS005
/*
/&
12–8 User Guide

Backing up the CA Dynam Catalog, and backing up and clearing the Audit data
set:
// JOB AUDTUTIL BACKUP AND CLEAR AUDIT DATA SET

// TLBL DYNHIST,'CA Dynam AUDT',,,,,,2
BACKUP INITIALIZE
/*
/&
// JOB DYNCAT BACKUP
// TLBL IJSYSBK,'CA Dynam BKUP',,,,,,2
BACKUP
/*
/&
This job stream creates a backup of the Catalog and Audit files and clears the
Audit data set. Run this job in the order shown at least once daily. This
ensures that current backups are always available.
Back up and clear the Audit data set first to ensure the following is done:
All records on the Audit data set reflect activity since the most recent
backup
The most recent backup is logged
Example
The following example details the recovery procedure.
Recovering the Catalog from a backup tape and Audit file:
// JOB DYNCAT RESTORE CA Dynam CATALOG FILES

// TLBL IJSYSBK
RESTORE
/*
/&
// JOB AUDTUTIL RECOVER CA Dynam CATALOGS FROM DISASTER
CATALOG RECOVERY NOTAPE LIST
/*
/&
This job stream recovers the Catalog using the current backup tape and the
Audit data set. No file ID is specified for IJSYSBK, the backup tape to be
restored. Since the Catalog has been destroyed, it would serve no purpose to
try to input the tape as a controlled data set.

Note:
The Audit Trail records to be processed are retrieved first from the Audit
Trail history tape(s), if any exist, then from the Audit Trail disk file.
If you omit the DATE= operand, the CATALOG RECOVERY command

processes only those Audit Trail records logged after the last BACKUP of
the existing Catalog file. All other Audit Trail records are ignored.
The Catalog recovery operation does not clear the Audit disk file. Only the
BACKUP function clears the Audit disk.
During the recovery operation, CA Dynam always processes the Audit trail
history tapes used as input during the recovery as uncontrolled data sets -
- even if the tape file's data set name is in the CA Dynam Catalog. During
the recovery operation, the data contained in the Catalog may be
unreliable.
Use the LIST option during Catalog recovery to log each operation.
DATASET Command
The DATASET command performs various general purpose functions on the

Audit Trail data set. The operands indicate the functions.
DATASET {INITIALIZE [LOGMODE=BASIC|EXTENDED] [SHARE=VSELOCK|YES|NO] }

{STATUS }
{UNLOCK }
The following parameters are mutually exclusive.
INITIALIZE Initializes the Audit Trail data set so that it can be used by AUDTUTIL.
STATUS Reports on the status of the data set.
UNLOCK Unlocks the data set when a lock-out condition occurs. This may happen when
SHARE=YES is in effect, and a job is canceled while the Audit Trail data set is
being updated.
Optional parameters
The following parameters are optional but not mutually exclusive. Each
parameter can be used only in combination with the INITIALIZE parameter.
LOGMODE= This includes the following:
BASIC Only logs information necessary for Catalog recovery to

the Audit Trail file.
12–10 User Guide

Reporting Commands
EXTENDED Default. Logs all file activity, including uncontrolled file

activity, to the Audit Trail file. This option supports Audit
logging of reportable records.
SHARE= This includes the following:
VSELOCK Enqueues the Audit file through the VSE External Lock file
rather than internal CA methods.
YES Provides multi-CPU users with Audit data set

enqueue/dequeue. Indicates the Audit data set is shared.
NO Default. Single-CPU users should specify SHARE=NO.
Examples
DATASET INITIALIZE LOGMODE=EXTENDED SHARE=YES
DATASET STATUS Notes:
Data set status information is automatically printed after the INITIALIZE or

UNLOCK functions are executed.
If the Audit Trail file is locked, any program attempting to log (update) the
Audit file from another partition is kept waiting until the Audit file is
unlocked. Within a single system, this is accomplished through the VSE
Lock Facility. Cross-system serialization is performed using an exclusive
CA technique (SHARE=YES), which does not employ SENSE RESERVE.
If SHARE=VSELOCK is specified, the IBM LOCK macro is used with the

EXTERNAL operand. If you select this option, all systems accessing the
Audit file must be sharing the VSE Lock file.
Reporting Commands
AUDTUTIL enables you to report on information logged to the Audit trail file.
This table lists each of the reporting commands and briefly describes their
functions.
Command Function
FIELDS Required and valid only for user-defined reports. Specifies the
fields to be included in a user-defined report and the order in
which they will appear.
GENERATE Required for both predefined and user-defined reporting.

Generates the report based on commands issued since the
previous REPORT command.

Reporting Commands
INPUT Optional for both predefined and user-defined reporting.

Indicates which Audit Trail file -- disk or history tapes(s) --
will be used for input for the reports.
PROGRAM Required for both predefined and user-defined reporting.

Specifies which product's (CA Dynam/T's, /D's, or /FI's) audit
records will be used in the reports.
REPORT Required for both predefined and user-defined reporting.

Specifies which predefined reports will be prepared or that a
user report will be defined in subsequent statements.
SELECT Optional parameter valid only for user-defined reports.

Indicates the conditions under which an audit record is
included in a user-defined report.
TITLE Optional parameter valid for predefined and user-defined

reports. Defines the page and field titles for user-defined
reports or for overriding titles for predefined reports.
All reports are defined by the following lists:
A selection list
A report definition list
A page title list
A field title list
Predefined Reports
Predefined reports set these lists up for you. You only have to tell the Audit
utility which reports you want. The following commands are valid for
predefined reports:
GENERATE
INPUT
PROGRAM
REPORT
TITLE
12–12 User Guide

Reporting Commands
The following job stream will produce two reports: one on catalog maintenance
and one on CA Dynam/T uncontrolled tape processing.
// JOB REPORT on TAPE PROCESSING AND MAINTENANCE

PROGRAM DYNAM/T (CA Dynam/T audit records)
REPORT MAINT UNCNTRLD (2 reports requested)
TITLE (PARTID 2) 'PT' (change in field title)
INPUT DATASET (disk audit file used)
GENERATE
/*
/&
Note the following ordering-of-statement rules:
The PROGRAM statement must precede the REPORT statement.

GENERATE must be the last statement before processing the report.
TITLE and INPUT must follow REPORT.
Several reports may be indicated on one REPORT statement. See the

description of the REPORT command for charts of the available predefined
reports.
If the predefined report field title were not changed, the above example could
be rewritten as follows:
// JOB REPORT on TAPE PROCESSING AND MAINTENANCE

PROGRAM DYNAM/T
REPORT MAINT UNCNTRLD
GENERATE
/*
/&
The INPUT statement is not needed since the default is the audit disk file.

Reporting Commands
User-defined Reports
If you'd rather customize a report, prepare the selection and title lists yourself.
This JCL produces a customized report on two particular data sets.
// JOB REPORT on PROCESSING OF TWO DATA SETS

PROGRAM DYNAM/T
REPORT
INPUT TAPE=SYS005
FIELDS DSNAME VOLSER VERSION VOLSEQ JOB FUNCTION I/O CONTROL
TITLE 'SPECIAL AUDIT REPORT'
TITLE (DSNAME 2) 'NAME'
TITLE (VOLSER 2) 'VOLUME'
TITLE (VOLSEQ 2) 'SEQ'
TITLE (CONTROL 2) 'CONT'
SELECT (DSNAME TEST.FILE1)
GENERATE
/*
/&
One report that traces the audit records for the two data sets will be
generated. Note that some of the default titles are being overridden.
As in the predefined reports, the following must be adhered to:
The PROGRAM statement must precede the REPORT statement
GENERATE must be the last statement before processing the report
FIELDS, INPUT, SELECT and TITLE must follow REPORT
For a customized report, you must at least supply FIELDS and GENERATE
statements.
Multiple Reports in One Execution
Several reports may be defined in one job stream. Each one is processed when
a GENERATE statement is encountered. Note that report definitions are cleared
after each GENERATE statement is executed so each GENERATE statement
must be paired with a REPORT statement. See the REPORT command for
examples.
12–14 User Guide

Reporting Commands
FIELDS Command
The FIELDS command specifies the fields to be included in the report and the
order in which they are to appear.
FIELDS {field-name [$SPn]...|$SP }
Examples
// JOB AUDIT REPORT CUSTOMIZED

PROGRAM DYNAM/D
REPORT (first report)
TITLE DSNAME 'DSN VOLUME UNIT'
FIELDS DSNAME
FIELDS VOLSER $SP5 UNIT
FIELDS $SP
FIELDS $SP
GENERATE
REPORT (second report)
TITLE DSNAME 'NAME'
TITLE VOLSER 'VOLUME'
TITLE UNIT 'UNIT'
FIELDS DSNAME VOLSER $SP5 UNIT
FIELDS $SP
FIELDS $SP
GENERATE
REPORT (third report)
FIELDS DSNAME VOLSER UNIT
GENERATE
/*
/&
The first report puts the data set name field on one line, volser and unit on the
second. These two lines are followed by two blank lines. Volser and unit are
separated by 5 spaces. The report will look like this:
DSN VOLUME UNIT (title line)
TEST.FILE1 (data set name line)

SYSWK1 0160 (volser and unit line)
(blank line)
(blank line)
TEST.FILE1 (next record)
SYSWK2 0167

Reporting Commands
Note that if you separate the fields onto individual lines, you are limited to
defining the title for the first FIELDS statement.
The second report puts data set name, volser and unit on one line; volser and
unit are separated by 5 spaces. This line is followed by two blank lines. The
report will look like this:
NAME VOLUME UNIT (title)
TEST.FILE1 SYSWK1 0160 (record 1)

(blank line)
(blank line)
The third report puts data set name, volser and unit on one line. Fields are
separated by 1 space by default. The report will look like this:
VOLUME
----- D A T A S E T N A M E ------ SERIAL UNIT (default title)

Note:
You cannot issue the FIELDS command for predefined reports.
Fields are printed in the order in which you specify them in the FIELDS
command.
The length of each field differs and is listed along with the field definitions
in the section "Report Fields."
Indicate spaces between fields with $SPn, where n is the number of spaces
to insert.
If two fields are specified with no intervening $SPn, spaces are inserted
between the fields.
To insert a blank line into the report, issue a FIELDS command with the
single field name '$SP'. For example,
FIELDS DSNAME VOLSER

FIELDS $SP
This prints the data set name and volser on one line. This is followed by
one blank line.
If all or part of any field falls outside position 120, the field will be
completely omitted.
Each FIELDS command defines a separate report line. If you issue more
than one FIELDS command, each audit entry will have more than one
output line on the report.
12–16 User Guide

Reporting Commands
GENERATE Command
The GENERATE command executes the report generation function using all
commands issued since the previous REPORT command. No operands are
required with this command.
Note: GENERATE is required to print a report. It must be the last command

entered for a given report.
Example
// JOB REPORTS
PROGRAM DYNAM/T
REPORT DATASET MAINT
GENERATE (2 predefined reports printed)
PROGRAM DYNAM/D
REPORT
TITLE 'VOLUME AUDIT REPORT'
TITLE DSNAME 'NAME'
GENERATE (a customized report printed)
/*
/&
INPUT Command
The INPUT command specifies which Audit Trail data file is to be used for
generating a report. If you omit all operands, the default is INPUT DATASET.
INPUT [ DATASET ]
[ ]
[ TAPE=[SYSnnn] [MULTITAPE=nn] ]
DATASET Optional parameter. Uses the Audit Trail file on disk for generating a report.
DATASET is the default if no parameters are specified, or if the entire INPUT

statement is omitted.
Note: DATASET and TAPE are mutually exclusive.

Reporting Commands
TAPE=[SYSnnn] Optional parameter. Uses the Audit Trail history tape assigned by logical unit
SYSnnn.
Default: SYS005
If a logical unit is not specified, you may omit the equal sign (=) too.
MULTITAPE=nn Optional parameter. Specifies the number of input files to be processed Not
required for one file spanning several volumes. End-of-volume switching is
handled normally.
Default: MULTITAPE=1
Examples
// JOB AUDIT EXAMPLE 1

// ASSGN SYS005,181
// TLBL DYNHIST
PROGRAM DYNAM/T
INPUT TAPE
GENERATE
/*
/&

PROGRAM DYNAM/T
GENERATE
/*
/&

* 1 FILE FOR EACH REPORT USING DEFAULT OF MULTITAPE=1
* AUDIT DATA SET IS on MULTIFILE VOLUME
*
* TLBL FOR 1ST REPORT - MAINT
// TLBL DYNHIST,'CA Dynam AUDT.1',,,,,,17
* TLBL FOR 2ND REPORT - DATASET
* TLBL FOR 3RD REPORT - SYSTEM
// ASSGN SYS008,181
PROGRAM DYNAM/T
REPORT MAINT DATASET SYSTEM
12–18 User Guide

Reporting Commands
INPUT TAPE=SYS008
GENERATE
/*
/&

* AUDIT DATA SET IS on MULTIFILE VOLUME
* MULTITAPE=3 -- 2 REPORTS - EACH READS 3 FILES
*
* TLBLS FOR FIRST REPORT - MAINT
* TLBLS FOR SECOND REPORT - DATASET
// ASSGN SYS005,181
PROGRAM DYNAM/T
REPORT MAINT DATASET
INPUT TAPE=SYS005 MULTITAPE=3
GENERATE
/*
/&
Examples 1, 3 and 4 use history tape files for input. Example 2 defaults to
using the disk audit trail file as input.
Note: If you are using the history tape for generating a report, you must
include a TLBL statement with the file name 'DYNHIST'; otherwise, the
function will fail and the job will be canceled.
PROGRAM Command
The PROGRAM command indicates whether a CA Dynam/T, CA Dynam/D or CA

Dynam/FI report is to be generated. (The records logged by each subset
contain different information.)
PROGRAM {DYNAM/T|DYNAM/FI|DYNAM/D }
DYNAM/T Generates a CA Dynam/T report.
DYNAM/FI Generates a CA Dynam/FI report.
DYNAM/D Generates a CA Dynam/D report.

Reporting Commands
Example
// JOB AUDIT REPORT

PROGRAM DYNAM/T
REPORT MAINT
GENERATE
/*
/&
Note:
Issue the PROGRAM command only if you have more than one CA Dynam
product installed.
If needed, the PROGRAM command must precede the REPORT command.
REPORT Command
The REPORT command indicates that a customized report is to be defined, or

lists the predefined reports to be generated.
REPORT [name1] [name2 ... name7]
Example
// JOB REPORTS
PROGRAM DYNAM/T
REPORT DATASET MAINT (2 predefined reports requested)
GENERATE
PROGRAM DYNAM/D
REPORT (a customized report defined)
TITLE 'VOLUME AUDIT REPORT'
TITLE DSNAME 'NAME'
GENERATE
/*
/&
The above job stream will produce three reports: two predefined reports for
CA Dynam/T (one on CA Dynam/T-controlled tape processing by data set
name and one on catalog maintenance) and one user-defined report.
12–20 User Guide

Reporting Commands
Note:
The REPORT command follows the PROGRAM command.
FIELDS, INPUT, SELECT and TITLE (when used) follow the REPORT
command.
More than one REPORT may be defined in one execution of AUDTUTIL.
Up to seven predefined reports may be specified on one REPORT

statement.
The available predefined reports are explained in the following section.
CA Dynam/T Auditing
These are the available predefined reports on information logged by CA

Dynam/T:
CANCEL All jobs canceled because of an operator response to a CA Dynam/T message.
CREATION All tape file creations.
DATASET All CA Dynam/T controlled tape processing by data set name.
DEVICES Tape device activity.
MAINT All Catalog management maintenance performed by the CA Dynam utility

programs.
OPERATOR Operator responses relating to tape file processing.
SYSTEM OPEN/CLOSE/EOV processing by data set name.
UNCNTRLD All CA Dynam/T uncontrolled tape processing by data set name.
UNLABELD All unlabeled tape files.
CA Dynam/D Auditing

Dynam/D:
CANCEL All jobs which canceled because of an operator response to a CA Dynam/D

message.
DATASET All CA Dynam/D-controlled disk processing by data set name.
DEVICES Disk device activity

Reporting Commands
MAINT All Catalog management maintenance performed by the CA Dynam utility

programs.
OPERATOR Operator responses relating to disk file processing.
PASSWORD All password violations relating to disk files.
PERMDEL All deleted permanent disk files.
SYSTEM OPEN, CLOSE, and exception processing by data set name.
UNCNTRLD All CA Dynam/D uncontrolled disk processing by data set name.
CA Dynam/FI Auditing

Dynam/FI:
DATASETS Creation or access of CA Dynam/FI-modified files.
TIMES Which files have been used at what times.
SELECT Command
The SELECT command specifies the conditions under which a record is selected
from the Audit Trail data set.
You can specify as many SELECT statements as you like, and include as many
conditions as you like in a single SELECT statement.
A record is selected only if it satisfies all the conditions in a SELECT statement.

The conditions in any one SELECT statement are considered to be connected
by logical ANDs while distinct SELECT statements are considered to be
connected by logical ORs.
SELECT (condition1) (condition2) ...
The chart below details the conditions you can specify in a SELECT statement:
(generic-class) a class of records, for example, (OPEN)
(field-name value) all records whose indicated field has the specified value, for example, (OWNER
DA)
12–22 User Guide

Reporting Commands
(field-name low- all records whose indicated field has a value within the specified range, for
value high-value) example, (UNIT 160 167)
Generic class names are described in the following pages. For more
information about lists of the field names, see Report Fields.
Examples
// JOB AUDIT REPORT SELECTIONS 1

PROGRAM DYNAM/D
REPORT
SELECT (OUTPUT)
SELECT (DATE 02/08/07 02/09/07)
GENERATE
/*
/&
// JOB AUDIT REPORT SELECTIONS 2

PROGRAM DYNAM/D
REPORT
SELECT (DSNAME TEST.FILE1) (OUTPUT) (DATE 02/08/07 02/09/07)
SELECT (DSNAME TEST.FILE3) (OUTPUT) (DATE 02/08/07 02/09/07)
GENERATE
/*
/&
The first example chooses records that meet any one of the following criteria:
The records are output files
The records have a data set name of TEST.FILE1 or TEST.FILE3
The records have a date between February 8, 2007 and February 9, 2007
The second example chooses records that meet any one of the following
criteria:
The records have a data set name of TEST.FILE1 and are output files and
have a date between February 8, 2007 and February 9, 2007
The records have a data set name of TEST.FILE3 and are output files and
have a date between February 8, 2007 and February 9, 2007

Reporting Commands
Note:
If you do not issue a SELECT statement, all records in the Audit file are
selected.
You cannot issue the SELECT command for predefined reports.
Field Values for SELECT Command
The following chart details the permitted field values for SELECT:
Value Example Notes
Numeric NCYCLE 5 Numeric values are right-justified within their

fields.
Alphanumeric JOB CATEST8 Alphanumeric values are left-justified within

their fields. If the string contains embedded
blanks, commas, or parentheses, enclose it in
apostrophes. If the string includes
apostrophes around it, use double
apostrophes.
Date DATE At system generation time, decide whether to

11/27/00 express DATE in mm/dd/yy or dd/mm/yy
format. Use this format for AUDTUTIL.
TIME TIME 07 17 The TIME format is HH.MM.SS. This example

selects entries logged between 7 A.M. and 5
P.M.(17:00:00)
When you are comparing alphanumeric field values, only the number of
characters supplied on the SELECT statement is used, regardless of the actual
length of the field. For example, to select all job names beginning with the
characters 'EL', issue the command:
SELECT (JOB EL)
Generic Classes for SELECT Statement
Records are logically grouped into generic classes based upon the contents of
one or more fields. Include a class name to reference these records in your
SELECT statement; this eliminates the need to specify the field values.
CA Dynam/D Generic Classes:
CLOSE CLOSE activity
INPUT input files
12–24 User Guide

Reporting Commands
MANUAL logged DYNCAT commands
OPEN OPEN activity
OUTPUT output files
CA Dynam/FI Generic Classes:
ACCEPT files accepted for processing by CA Dynam/FI
INPUT input files
OUTPUT output files
REJECT files rejected for processing by CA Dynam/FI
CA Dynam/T Generic Classes:
INPUT input files
OUTPUT output files
OPEN OPEN activity
CLOSE CLOSE activity
EOV EOV activity
ACCEPT instances of ACCEPT
ALTER instances of ALTER
RERUN instances of RERUN
PREV instances of PREV
EXCEPTION exceptional occurrences
MANUAL DYNCAT commands which were logged
Field Names for SELECT Command
Field names and their contents are described in the "Report Fields" section of
this chapter.

Reporting Commands
TITLE Command
The TITLE command overrides CA Dynam defaults for the titles used on the
report (page titles and field titles).
Format for page title:
TITLE ('page-title' [LEFT|RIGHT])

or
TITLE 'page-title1' 'page-title2' ...
Format for field title:
TITLE (field-name [line-number [position]]) 'field-title'
Page Title The page title format prints a user-defined title at the top of each report page.
LEFT and RIGHT are optional parameters indicating left or right justification of
the page title. If you specify neither, you may omit the parentheses and the
title is centered across the page. If all titles are to be centered, you can use
the same format to string the page titles on one statement.
You can issue several TITLE commands. They are printed on separate lines in
the order in which they are issued. The first character of each page title should
be an ANSI control character (blank, '0', '+', or '-'). If the first character is not
a valid ANSI control character, CA Dynam forces single-line spacing.
Field Title This specifies a user-defined title as the heading for the identified field.
Line-number is the title line on which this field title is to be printed: 1 for the
first field title line, 2 for the second field title line, and so on. Default: 1.
Position is the print position at which the field title is to begin, relative to the
beginning of the field on the report line. Default: 0.
A negative position (-nn) indicates that the title is to begin 'nn' spaces before
the start of the field.
If you omit both the line number and position, you can also omit the
parentheses that would have surrounded them.
You can specify as many user-defined field titles as needed. They replace the
default field titles. For more information about the default titles, see Report
Fields.
12–26 User Guide

Reporting Commands
Examples
// JOB AUDIT REPORT CUSTOMIZED

PROGRAM DYNAM/D
REPORT (first report)
TITLE 'REPORT 1'
TITLE 'REPORT on DISK DATA SET'
TITLE 'AND VOLUME USAGE'
GENERATE
REPORT (second report)
TITLE '0REPORT 2' 'REPORT on DISK DATA SET' 'AND VOLUME USAGE'
GENERATE
REPORT (third report)
TITLE ('YY/MM/DD' LEFT)
TITLE ('REPORT on DISK DATA SET AND VOLUME USAGE' LEFT)
TITLE DSNAME 'DATA SET NAME'
TITLE (VOLSER 2) 'SERIAL'
TITLE (VOLSER 3 -1) 'NUMBERS'
GENERATE
/*
/&
The first report defines a 3-line page title centered on the page. Default field
titles are used.
AUDIT TRAIL UTILITY PROGRAM

REPORT 1
REPORT on DISK DATA SET
AND VOLUME USAGE
VOLUME
--- D A T A S E T N A M E --- SERIAL
VBWORK SYSWK1
VSFILE SYSWK2

Reporting Commands
The second report is the same as the first, except that there is a blank line
before the page title starts. The blank line is caused by the ANSI control
character (0) in the first title ('0REPORT2').
REPORT 2
REPORT on DISK DATA SET
AND VOLUME USAGE
VOLUME
--- D A T A S E T N A M E --- SERIAL
VBWORK SYSWK1
VSFILE SYSWK2
The third report prints the date the report was generated and a page title.
Both lines are left-justified on the page. The field title for volume serial
number is printed on three lines. Note that the third line (NUMBERS) is shifted
one character to the left.

88/12/02
REPORT on DISK DATA SET AND VOLUME USAGE
DATA SET NAME VOLUME

SERIAL
NUMBERS
VBWORK SYSWK1
VSFILE SYSWK2 Notes:
You may include the strings YY/MM/DD or HH.MM.SS. The Audit Trail
facility will replace these with the current date and time, respectively.
Make sure that you code these strings as shown.
If the TITLE text (within apostrophes) exceeds position 72, you can
continue it starting in position 1 on the next statement.
The maximum length of a page title is 120 characters (excluding the ANSI
control character). If you specify a title larger than 120 characters, only
the leftmost 120 characters are printed.
The maximum length of a field title is 120 characters. The titles are moved
into the output line in the order in which you specified them. If any overlap
occurs, only the last specified title is printed correctly.
There is a maximum of seven titles (page and field). All other titles are
ignored.
Insert two consecutive apostrophes to specify an apostrophe as part of the

title text.
12–28 User Guide

Report Fields
The total number of lines per page is the value defined during the VSE
supervisor generation or specified on the Job Control command 'SET
LINECT=nnn'.
The position operand, +nn, may have any value. However, if the
specification causes part of the title to be positioned outside the report
line, truncation occurs and only the contents of the report line are printed.
If all or part of any field title falls outside positions 1 to 120 inclusive, the
field title is completely omitted.
Report Fields
This section identifies the field names for each CA Dynam product. Use these
field names on the FIELDS, SELECT, and TITLE statements. The charts show
the field name that AUDTUTIL recognizes, the length and description of the
field, and the default field title that appears on reports.
Note:
Numeric values are right-justified within their fields; all other values are
left-justified.
The default field title for DSNAME is a character string with the words
'DATASET NAME' double-spaced and padded with hyphens to a length of
44 characters.
CA Dynam/T Fields
CA Dynam/T fields are shown in the following table.
Field Name Length Description And Possible Values Default Field

Title
BLKCOUNT 8 Number of blocks on tape BLOCK
SCRATCH or COUNT
if a scratch tape
OUTSIDE
if tape not defined in the CA Dynam Catalog file
COMMAND 40 DYNCAT command. If DYNCAT DELETE, the slot and --UTILITY

vault (other than A) are also displayed COMMAND LINE--
COMMENTS 18 Descriptive comments --COMMENTS--

Report Fields

Title
COND 8 Condition code - possible values: CONDITION

CODE
OPERATOR
Operator response occurred
LOCKED
Job canceled: file was locked
PROTECT
Tried to write on protected tape
BADLUB
Invalid logical unit used
BADFILE
Invalid file number requested
LBLTFULL
User label track full
CTFULL
File is full
BADVERS
Invalid version number supplied
CONTROL 4 CTRL
Indicates whether the tape and/or file is controlled or
uncontrolled (not in the Catalog). Possible values:
YES controlled tape

NO uncontrolled tape
NODN not in Catalog file
NOSN not in Catalog file
CPUID 3 CPU ID character CPU ID
CREATE 8 Creation date (Gregorian) CREATION DATE
DATE 8 Date, as MM/DD/YY or DD/MM/YY (whichever was DATE

specified at supervisor generation time)
DATES 5 Date as MM/DD or DD/MM DATE
DEVICE 6 Device type values DEVICE TYPE
DSNAME 17 Data set name (file ID) DATASET NAME
DSN44 44 Data set name (file ID) DATASET NAME
EXPIRE 8 Expiration date EXPIRATN DATE
12–30 User Guide

Report Fields

Title
FILENAME 8 DTF file name FILENAME
FILESEQ 4 File sequence number FILE SEQ.
FUNCTION 8 Function performed: FUNCTION CODE
OPEN, CLOSE, EOV, ALTER, RERUN, ACCEPT, CANCEL,

RELEASE, ASSIGN, DYNCAT, PREV
I/O 3 Input or Output I/O
JOB 8 Jobname JOB NAME
MODE 4 Recording mode used MODE
NCYCLE 6 Number of cycles NUMBER CYCLES
NUMFILES 5 Number of files on tape NUMB.
FILES
OWNER 5 Ownership code OWNER ID
PARTID 4 Partition ID ID
PHASE 8 Phase name PRGRM NAME
SID 4 System ID SYST ID
TAPELBL 4 Tape label type: LBLS
SL (standard label) or UL (unlabeled)
TIME 8 Time of day, as HH.MM.SS TIME
TIMES 5 Time of day, as HH.MM TIME
UID 4 User ID USER ID
UNIT 4 Tape drive address UNIT
VAULT 5 Vault ID VAULT LOC
VERSION 4 Version number VERS NUMB
VOLSEQ 4 Volume sequence number VOL.
SEQ.
VOLSER 6 Volume serial number VOLUME SERIAL

Report Fields
CA Dynam/FI Fields
CA Dynam/FI fields are shown in the following table.

Title
BLKSIZE 5 New block size BLKSI
BUFRMODE 5 Buffering mode. BM
SB (single) or DB (double)
DATE 8 Date, as MM/DD/YY or DD/MM/YY (whichever was DATE

specified at supervisor generation time)
DEVICE 6 Device type examples: DEVICE TYPE
2311, 2314, 2400, 3330, 3340, 3350, 3375, 3380,

3410, 3420, 8809, FBA
DSNAME 44 Data set name (file ID) -DATASET NAME-
DTFTYPE 8 Old DTF type. Possible values: OLD DTF TYPE
READER, PUNCH, PRINTER, DISK TAPE, DI
FILENAME 8 DTF file name DTF NAME
I/O 5 Input or Output IN/OUT DISP
INPUT or OUTPUT
JOB 8 Jobname JOB NAME
LBLTYPE 4 Label type found: TAPE, SD, VSAM, ISC, ISE, DA LABEL FOUND
LRECL 5 New record length LRECL
MISCFLAG 8 Miscellaneous flags MISC FLAGS
RELEASE or VERIFY
OLDBLKSZ 5 Old block size OLD BLKSZ
OLDLRECL 5 Old record length OLD LRECL
OLDRECFM 5 Old record format: OLD RECFM
F, FB, V, VB, U
PARTID 2 Partition ID ID
PHASE 8 Phase name PHASE NAME
RECFM 5 New record format: RECFM
F, FB, V, VB, U
12–32 User Guide

Report Fields

Title
REJECT 8 Rejection code. Possible values: REJECT REASON
BLKSIZE
inconsistent block size value
LBLTYPE
unsupported label type
DEVICE
unsupported DTF device type
DTFFEAT
unsupported DTF feature
RECFORM
unsupported record format
IGNORED
NOFI option used
TAPELBL 2 Tape label type. TL
SL (standard label) or UL (unlabeled)
TAPEPOS 10 Tape position indicators: TAPE POSITION
REW, RUN, NORWD, SKR, NOTM, POSITION
CA Dynam/D Fields
CA Dynam/D fields are shown in the following table.

Title
ACTALLOC 6 Actual allocation ACTUAL ALLOC
ACTDEV 4 Actual device type examples: DVC
3330, 3340, 3344, 3350, 3375
3380, 2311, 2314, 2319, 3310, 3370
AEXTSEQ0 6 Actual extent sequence EXTSEQ AEXT00

Report Fields

Title
AEXTYPE0 6 Actual extent type: TYPE AEXT00
PRIME, OVRFL or INDEX
ANUMTRK0 6 Actual extend number of TRKS NUMTRK AEXT00
ARELTRK0 6 Actual extent relative TRK RELTRK AEXT00
AVOLSER0 6 Actual extent VOLSER VOLSER AEXT00
COMPCODE 18 Completion reasons COMPLETION

CODE
CONTROL 4 Indicates whether the file is processed as controlled, CTRL

or uncontrolled (YES|NO)
CPUID 1 CPU ID CPU ID
DATE 8 Date, as MM/DD/YY or DD/MM/YY DATE
DATES 5 Date, as MM/DD or DD/MM DATE
DDNAME 8 DTF file name DDNAME
DSNAME 44 Data set name -DATASET NAME-
DTFTYPE 5 DTF type: DTF TYPE
DTFSD, DTFPH, DTFDA, DTFIS, ACB, DTFCP, DTFDI
FUNCTION 8 Function being performed: FUNCTION CODE
(OPEN, CLOSE, CANCEL, V=, REC-DEL, GDG-DEL,

CHG-ALLC, BAD-PSWD, PERM-DEL)
GDSVERID 2 GDS VERSION ID GDS ID
I/O 3 Input or Output (IN|OUT) I/O
JOB 8 Job name JOB NAME
LASTMSG 4 Last CA Dynam/D message issued LAST MSG
NUMEXTS 4 Number of extents used by DSN NUM EXTS
OEXTSEQ0 6 Original extent sequence EXTSEQ OEXT00
OEXTYPE0 6 Original extent type: TYPE OEXT00
ONUMTRK0 6 Original extent number of TRKS NUMTRK OEXT00
OPERVOL 6 Operator responded VOLSER OPER VOLSER
ORELTRK0 6 Original extent relative TRK RELTRK OEXT00
ORIGALLC 6 Original ALLOC quantity (OPEN) ORIG ALLOC
12–34 User Guide

Report Fields

Title
ORIGDEV 6 Original device type examples: ORIG DEVICE
3330, 3340, 3344, 3350, 3375
3380, 2311, 2314, 2319, 3310, 3370
OVERRIDE 8 Operator override allocation OVERRIDE ALLOC
OVOLSER0 6 Original extent VOLSER VOLSER OEXT00
PARTID 3 Partition ID PART ID
PASSWORD 8 Incorrect password entered (BAD-PSWD) INVALID

PASSWORD
PHASE 8 Phase name PHASE NAME
PROCIND 8 Processing Indicators: PROCESSING

INDICATORS
SDWORK
DTFSD work file
INPUT
Input data set
DDCNTRL
CA Dynam/D-controlled
CATCNTRL
Catalog controlled
DASDDI
DASD DI required
DSNDEL
Data set was deleted
EQFILDEL
Equal file-ID deleted
POOL
Pool volser used
SECSD
Not 1st extent open SD
TIMES 5 Time of day, as HH.MM TIME
TRKTRUNC 6 TRKS/BLKS truncated (CLOSE) TRACKS TRUNC

Report Fields

Title
UNIT 4 Disk drive address UNIT
The following fields are valid only for NON-SD data sets. A total of 15
additional extents is possible.

Title
AEXTSEQ1 6 Actual extent 1 sequence EXTSEQ

AEXT01
AEXTYPE1 6 Actual extent 1 type: PRIME, OVRFL or INDEX TYPE AEXT01
ANUMTRK1 6 Actual extent 1 number of TRKS NUMTRK

AEXT01
ARELTRK1 6 Actual extent 1 relative TRK RELTRK

AEXT01
AVOLSER1 6 Actual extent 1 volser VOLSER

AEXT01
OEXTSEQ1 6 Original extent 1 sequence EXTSEQ

OEXT01
OEXTYPE1 6 Original extent 1 type: TYPE OEXT01
ONUMTRK1 6 Original extent 1 number of TRKS NUMTRK

OEXT01
ORELTRK1 6 Original extent 1 relative TRK RELTRK

OEXT01
OVOLSER1 6 Original extent 1 volser VOLSER

OEXT01
12–36 User Guide

Chapter 13: DYNCOPY−CA Dynam File
Utility Program
The CA Dynam file-copy facility, DYNCOPY, gives you a simple way to copy
files within CA Dynam. The program will copy any tape file or sequential disk
file to another tape or disk: tape-to-tape, tape-to-disk, disk-to-tape, or
disk-to-disk. The program also lets you specify reblocking of the output file
and provides facilities for selective copying of specified records from a file.
DYNCOPY uses standard LIOCS access methods so that input and output data
sets can be completely controlled by CA Dynam.
The second main function of DYNCOPY is to simplify file-dumping. All or

selected records of a file can be displayed in either hex-and-character format
or character-only format.
Input and output tapes may be labeled or unlabeled, and may contain
undefined, spanned, fixed-length, or variable-length records. Records may be
blocked or unblocked.
Parameters are supplied to support both CA System/Manager's SPUTIL

program and the CA EPIC TSIDDTD and TSIDDMP programs. All corresponding
parameters are interchangeable except where noted.
Operation
The following criteria must be met for the successful operation of DYNCOPY:
DYNCOPY requires 64K + 8 bytes of partition GETVIS storage for the input
file buffer. When the COPY function is used, an additional 64K bytes of
partition GETVIS storage is required.
The maximum block size supported is 64K.
Tapes will be rewound at OPEN and at CLOSE, unless this positioning is

overridden by the use of the RUN, NOREW, RUNIN, or NOREWOUT
parameters on the DYNCOPY control statements or equivalent CA Dynam/T
TLBL options.
The following file names (DTFnames) are required on DLBLs and TLBLs:
INPUT Input disk or tape files
TAPEIN Standard-labeled input tapes
DISKIN Input disk file
OUTPUT Output disk or tape files
Chapter 13: DYNCOPY−CA Dynam File Utility Program 13–1

Parameter Statements
TAPEOUT Output tape (always standard-labeled)
DISKOUT Output disk file
To specify a DTFname of your choosing for the input tape or disk file, specify
FILEIN= or INNAME= on a DYNCOPY control statement. To specify your own
DTFname for the output tape or disk file, specify FILEOUT= or OUTNAME= on
a DYNCOPY control statement.
Parameter Statements
If DYNCOPY is executed from the console, it will read its parameters from the
console. After the last parameter has been entered, pressing (END/ENTER)
with no data will cause DYNCOPY to begin executing the required functions. If
DYNCOPY is executed from SYSRDR, it will read its parameter statements from
SYSIPT, and at least one statement must be input to specify the type of copy
or dump wanted.
Parameters may be specified in any order, on any number of statements, but

the first parameter on each statement must begin in column 1, and no
parameter may be continued onto another statement. Parameters on the
same statement must be separated from each other by a single comma or
blank, and may extend into column 80. Comments may be placed on the
statement if at least two blank columns are left between the end of the last
parameter and the beginning of the comment.
Parameters
DUMP Produces a dump of the file with no deblocking of records when the records
are printed. The COPY, MAX=, SKIP=, and CHARONLY parameters may be
used with DUMP, but the SEL= parameter may not be used. All other
parameters used with DUMP will be ignored.
COPY Causes the input file to be copied to tape or disk. If a full copy of the file is
wanted, with no reblocking, no other parameters are needed. If a selective
copy is to be made, the SEL=, LRECL=, BLKSIZE=, and RECFM= parameters
are required. If COPY is used without SEL=, RECFM=, and LRECL= all being
specified, DYNCOPY uses a DTF with undefined records for the output file. The
copy will be correct, but the record size and block size saved on the CA Dynam
Catalog will be missing or incorrect. COPY is the default parameter if no
command is specified.
SEL=ALL All records will be selected for copying and/or printing.
13–2 User Guide

Parameters
Startingposition, Specifies a condition upon which input records are to be selected for copying
Length, Condition, and/or printing, and forces deblocking of printed records. If any SEL=
Type, Argument parameters are used, a valid LRECL= parameter must also be specified. The
total number of SEL= parameters may not exceed 20 per run. The SEL=
parameter may be specified on the same statement as other parameters, but
the SEL= parameter must be the last parameter on the statement.
Two SEL= parameters may not be specified on the same statement.
Startingposition A 1- to 4-digit number which indicates the starting

position of a field (relative to 1) in the logical record. The
number must be between 1 and 4095.
Length A 1- to 2-digit number which indicates the length of the

field to be compared. The number must be between 1
and 67.
Condition Must be one of the following:
EQ equal to
NE not equal to
GT greater than
LT less than
NG not greater than
NL not less than
GE greater than or equal to
LE less than or equal to
Type "C" if the argument is to be specified in character format,

or "X" if the argument is to be specified in hex notation.
Argument The hex or character string to be compared to the

specified field in the record. The argument is not
enclosed by apostrophes, and a character string may
contain embedded blanks, commas, and so on.
Note: Record selection for copying or printing occurs when any of the
specified SEL= tests is true (for example, SEL= tests are treated as a set of
"or" conditions); no "and" specification is possible. The tests are executed in
the order in which they are entered on the input statements.
EOJ= | FEOF= The EOJ= and FEOF= parameters can be used interchangeably. Both have
Startingpos, Length, the same format as the SEL= parameter and may be used to avoid reading
Condition, Type, an entire file by specifying the conditions upon which the program is to
Argument terminate. A valid LRECL= parameter and at least one valid SEL= parameter
are required with this parameter.

Parameters
The EOJ= or FEOF= parameter must be on a statement by itself, must begin in

column 1, and should precede the SEL parameter(s). The SEL= and EOJ=
tests are executed in the order in which these parameters are read. The total
number of EOJ= parameters may not exceed 20 per run.
PRINT Specifies that printing is wanted. PRINT is assumed and need not be specified
if either DUMP or CHARONLY is specified.
MAX=n | RECS=n Specifies that printing and/or copying is to halt and DYNCOPY is to terminate
when n records have been printed or copied. The value of n must be a 1 to 6
digit number between 1 and 999,999. If the LRECL= parameter is specified,
then n specifies the number of logical records; if LRECL= is not specified, then
n specifies the number of physical blocks.
SKIP=n Specifies the number of physical blocks or logical records at the beginning of
the file which are to be skipped before record selection, copying, or printing
begins. The value of n may be any number from zero to 999,999; inclusive.
If this parameter is omitted, no records will be skipped. If the LRECL=
parameter is specified, then n specifies the number of logical records; if
LRECL= is not specified, then n specifies the number of physical blocks.
CHARONLY Specifies that the printed output is not to contain the hex equivalent of the
character data. If this parameter is omitted, hex and character printing is the
default, with one exception: if a line to be printed consists entirely of printable
characters, that line will be printed as if CHARONLY had been specified.
RECFM=xx Specifies the record format. If a full copy of a file is wanted with no change in
block size, this parameter must be omitted. If a selective copy is wanted, this
parameter must specify one of the following:
F Fixed-length, unblocked.
FB Fixed-length, blocked.
V Variable-length, unblocked.
VB Variable-length, blocked.
S Spanned
SB Spanned, blocked
U Undefined
Note: The record type of the output file must be the same as the record type
of the input file (for example, a fixed-length output file requires fixed-length
input records), and a variable-length output file requires variable-length input
records. This parameter is required for selective copying and printing.
13–4 User Guide

Parameters
LRECL=n Specifies the logical record length in bytes. For variable-length records, specify
LRECL=V. This parameter is required for selective file copying and selective
printing.
BLKSIZE=n Specifies the block size of the input files, in bytes, and must be a valid size for
the output device type. For variable-length blocked files, specify the maximum
size for the largest block in the file. Block size must be a multiple of the value
specified in the LRECL= parameter.
If the block size of the output file is to be different from the block size of the
input file, then the BLKSIZE= parameter must specify the block size of the
input file and either the BLKSZ= parameter on the DLBL or TLBL, or the
DYNCOPY OBLKSIZE parameter must be used to specify the block size of the
output file.
OBLKSIZE=n Specifies the block size of the output file, in bytes, and must be a valid size for
the output device type. For variable length blocked files, specify the maximum
size for the largest block in the file. For disk output, do not add 8 to the
OBLKSIZE= value; simply specify the block size. Block size must be a multiple
of the value specified in the LRECL= parameter.
If the block size of the output file is to be different from the block size of the
input file, then the BLKSIZE= parameter must specify the block size of the
input file and either the DYNCOPY OBLKSIZE= or the BLKSZ= parameter on
the DLBL or TLBL must be used to specify the block size of the output file.
CISIZE=n Specifies the CISIZE, in bytes, to be used for output files on FBA devices, and
is only used when COPY is specified and reblocking is not to be performed.
This parameter is ignored if the input is on a CKD device. In this case, the
CISIZE for the output file is based on the track capacity of the input CKD
device. If the input file is on tape or on FBA and this parameter is not
specified, a CISIZE of 512 will be used. Do not specify this parameter if the
DYNCOPY BLKSIZE= parameter is also specified.
FILES= | INPUT= Specifies the number of input tape or disk files to be concatenated. If
concatenating disk files the DLBL for the first file must be DISKIN, and the
DLBLs for the second and subsequent files must be DISKINn, where n is a
number from 1 to 9. If concatenating tape files, the TLBL for the first file must
be TAPEIN and the TLBLs for the second and subsequent files must be
TAPEINn, where n is a number from 1 to 9. However, if the CA Dynam/T DROP
option is used on TLBLs, the same DTF name may be used for each file.
RUN | RUNIN Specifies that all input and output tapes are to be rewound at open and
rewound and unloaded at close. If this parameter is not specified and the
NOREW or NOREWIN parameter is also not specified, the tape file(s) will be
rewound at open and close.

Sample JCL
NOREW | NOREWIN | NOREWOUT

Specifies that all input and output tapes are not to be rewound at open or at
close. If this parameter is not specified and the RUN or RUNIN parameter is
also not specified, the tape file(s) will be rewound at open and at close.
NOREWIN only applies to input files and NOREWOUT only applies to output
files, NOREW can be used with both input and output files.
NOPLINE | NOSCALE Specifies that no "positioning" line is to be printed beneath the records
printed. If this parameter is not specified, a positioning line will be printed
under each record printed.
{LABEL=YES|NO} | UNLBLIN
Specifies whether the input tape file contains standard labels. LABEL=YES
indicates that the input tape contains standard labels. LABEL=NO or UNLBLIN
indicates that the input tape(s) are unlabeled.
UNLBLOUT Defines the output as an unlabeled tape.
FILEIN= | INNAME= Specifies the input DTFname to override the default name of TAPEIN, DISKIN,
or INPUT.
FILEOUT= | OUTNAME=
Specifies the output DTFname to override the default name of TAPEOUT,
DISKOUT, or OUTPUT.
HDRINFO Causes VSE to display the tape header information on the operator console
when opening the input data sets.
NOTPMK Suppresses the leading tape marks normally written before the data on
unlabeled output tapes.
Sample JCL
Example 1: Produce a hex and character dump of all records having a
customer code of 0211 or 0212. The record is 120 bytes long and the
customer code is in positions 47 of the record.
// TLBL TAPEIN,'ORDER.FILE'
// EXEC DYNCOPY,SIZE=22K
LRECL=120,RECFM=F,PRINT
SEL=47,4,EQ,C,0211
SEL=47,4,EQ,C,0212
/*
13–6 User Guide

Sample JCL
Example 2: Produce a character only dump of all records containing X'FFFF' in

positions 1213. Do not print more than 1,000 records, and stop the dump
when positions 56 are XY. The file is on disk and records are variable blocked.
// DLBL INPUT,'INVENTORY.FILE'
// EXEC DYNCOPY
PRINT,MAX=1000,CHARONLY,LRECL=V,RECFM=VB,BLKSIZE=6000
FEOF=56,2,EQ,C,XY
SEL=1213,2,EQ,X,FFFF
/*
Example 3: Create a test file on disk from the master payroll tape file by
copying record types 1 and 5. The record number is in card column 1. The
records on tape are 100 bytes blocked 20. The output disk file records are to
be blocked 40. Get a hex dump of all records copied to the new test file.
// JOB DYNCOPY
// TLBL TAPEIN,'PAYROLL.MASTER'
// DLBL DISKOUT,'PAYROLL.TEST'
// EXEC DYNCOPY
COPY,PRINT,LRECL=100,RECFM=FB,BLKSIZE=2000,OBLKSIZE=4000
SEL=1,1,EQ,C,1
SEL=1,1,EQ,C,5
/*
/&
Example 4: This is an example of stacking files on one output tape.
// JOB CREATE A MULTIFILE SET

// DLBL IN1,'FILEA' 1ST INPUT FILE
// TLBL OUT1,'BACKUP.FILEA',STACK=A 1ST OUTPUT FILE
COPY,FILEIN=IN1,FILEOUT=OUT1
/*
// DLBL IN2,'FILEB' 2ND INPUT FILE
// TLBL OUT2,'BACKUP.FILEB',STACK=A 2ND OUTPUT FILE
/*
// DLBL IN3,'FILEC' 3RD INPUT FILE
// TLBL OUT3,'BACKUP.FILEC',STACK=A 3RD OUTPUT FILE
/*
/&

Sample JCL
Example 5: Concatenate three disk files into one tape file
// JOB DYNCOPY
// DLBL DISKIN,'DISK.FILE.1' 1st input file
// DLBL DISKIN1,'DISK.FILE.2' 2nd input file
// DLBL DISKIN2,'DISK.FILE.3' 3rd input file
// TLBL OUT1,'TAPE.FILE' output
// EXEC DYNCOPY
COPY,FILES=3,FILEOUT=OUT1
/*
13–8 User Guide

Appendix A: CA Dynam Report
Examples
The following reports are provided by CA Dynam. Examples appear following
the chart.
Title Report No. Program

Functions
TDYNUTL Reports
DATA SET NAME LISTING TDYNUTL-01 LIST DSN=ALL
ALL TAPES BY VOLUME SERIAL NUMBER TDYNUTL-02 LIST ALL
ALL ACTIVE TAPES BY VOLUME SERIAL TDYNUTL-03 LIST VOL=ALL

NUMBER:
EXCEPTION REPORT TDYNUTL-04 EXCEPTS
SELECTED DATA SET NAME LISTING TDYNUTL-05 LIST DSN=dsn
INVENTORY OF ALL SCRATCH TAPES TDYNUTL-06 LIST SCRATCH
CURRENT ACTIVITY BY DATA SET NAME TDYNUTL-07 LIST NEW
CURRENT ACTIVITY BY VOLUME SERIAL TDYNUTL-08 LIST NEW

NUMBER
LIST OF SELECTED VOLUME SERIAL TDYNUTL-09 LIST VOL=volser

NUMBERS
DYNCAT Reports
TAPES SCRATCHED IN THIS RUN TDYNUTL-05 SCRATCH
LISTCAT REPORT LISTCAT
TDYNVLT Reports
LOCATION MOVEMENT EXIT REPORT TDYNVLT-01 MOVEMENT
LOCATION MOVEMENT ENTRY REPORT TDYNVLT-02 MOVEMENT
LOCATION MOVEMENT SUMMARY REPORT TDYNVLT-03 MOVEMENT
LOCATION INVENTORY REPORT TDYNVLT-05 INVENTORY
TDYNLIST Reports
EMPLOYEE SYSTEM PULL LIST TDYNLIST-01 PULL LIST
DYNAM/T PULL LIST BY VOLUME SERIAL TDYNLIST-02 PULL LIST

NUMBER
Appendix A: CA Dynam Report Examples A–1

TDYNUTL Reports

Functions
TDYNSYNC Reports
CATALOG APPLY - APPLY
CATALOG EXTRACT - EXTRACT
CATALOG SYNCHRONIZATION - SYNC
ACTIVE CATALOG FILES ACTVFILE SELECT
FIDVER
OWNERID
SYSTEMID
USERID
VOLSER
CATALOG FILE DEFINITIONS FILEDEFS SELECT
ALLOCS
CREATE
MESSAGES
MULTFILE
RETENT
TECHSPEC
VAULTS
DISK SPACE USAGE ANALYSIS SPACEUSE SELECT
FIDEXT
REALLOC
REBLOCK
VOLFID
FILE USAGE FREQUENCY FREQUSE SELECT
AVOPDAY
DAYSOLD
DAYSUNUS
FIDVER
A–2 User Guide

TDYNUTL Reports

Functions
TAPE INVENTORY REPORT TAPES SELECT
ACTIVE
ALLTAPES
SCRATCH
VOLUME TABLE OF CONTENTS VTOCS SELECT
CREATE
EXPIRE
FIDEXT
VOLLOC

TDYNUTL Reports
TDYNUTL Reports
This JCL produces reports TDYNUTL-01 through TDYNUTL-09.
// JOB TDYNUTL REPORTING UTILITY FOR CA Dynam/T

// DLBL WORK1,'WORK.FILE.1',0
// EXTENT SYS001...
// ASSGN SYS001,150
LIST DSN=ALL
LIST ALL
LIST VOL=ALL
EXCEPTS
LIST DSN='D.SAVE.IT'
LIST SCRATCH
LIST NEW
LIST VOL=001100
/*
/&
CA DATA SET NAME LISTING TDYNUTL-01 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 15.05.15
DSN VLT VOLSER VER VOL FIL OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION----- PED PED TAPE MSG
BKFILE.1
A 001546 1 1 2 2 10/31/99 10/29/99 14.37 A F5 381 6250 CPJ94B 214
A 001550 2 1 2 2 10/31/99 10/29/99 07.15 A F5 383 6250 CPJ94B 134
D.FILE
A 001333 1 1 3 10/29/99 10/29/99 02.24 A F5 380 6250 CPJLB 472
A 001534 2 1 3 10/22/99 10/22/99 06.04 A F5 383 6250 CPJLB 656
A 002067 3 1 3 10/15/99 10/15/99 14.30 A F5 380 6250 CPJLB 123
DYN.AUDIT.BKUP
NO TAPE 2
F.AGNT.FILE MF
A 001120 1 1 7 4 10/01/99 10/01/99 07.58 A F6 380 6250 FMJREPRO 917
A 001183 2 1 7 4 10/01/99 10/01/99 06.56 A F6 380 6250 FMJREPRO 291
A 001231 3 1 7 4 10/01/99 10/01/99 05.58 A F6 383 6250 FMJREPRO 567
A–4 User Guide

TDYNUTL Reports
CA ALL TAPES BY VOLUME SERIAL NUMBER TDYNUTL-02 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 17.37.44
VOLSER VLT ----------------DATA-SET-NAME--------------- VER VOL FIL OW SY US ------------CREATION-INFORMATION-------- TAPE

ID ID ID DATE TIME CPU PT CUU MODE LEN JOB-NAME ERRS
NUM001 B NUM.1 1 1 1 01/11/00 16.38 A BG REPORT

NUM002 A NUM.1 2 1 1 01/11/00 16.38 A BG REPORT
NUM021 A NUMBER.2 1 1 1 01/11/00 16.39 A BG REPORT
NUM031 C NUMBR.3 1 1 1 01/11/00 16.39 A BG REPORT
NUM032 A NUMBR.3 2 1 1 01/11/00 16.39 A BG REPORT
001100 A NU.LOAN 5 3 1 10/27/99 04.04 A F5 381 6250 CPJSAVE1 466
NU.COLL 5 3 2 10/27/99 04.21 A F5 381 6250 CPJSAVE1 466
NU.EXC 5 3 3 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NU.TX 5 3 4 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NUS.RV 5 3 5 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NUS.SGN 5 3 6 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
001101 A ICCF.WEEKLY 1 1 1 10/28/99 16.57 A F5 383 6250 SYJ006W 569
001104 NUSV.LOAN SCRATCHED ON 12/02/99
CA ALL ACTIVE TAPES BY VOLUME SERIAL NUMBER TDYNUTL-03 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 18.10.34

NUM001 B NUM.1 1 1 1 01/11/00 16.38 A BG REPORT

NUM002 A NUM.1 2 1 1 01/11/00 16.38 A BG REPORT
NUM031 C NUMBR.3 1 1 1 01/11/00 16.39 A BG REPORT
NU.EXC 5 3 3 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NU.TX 5 3 4 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NUS.RV 5 3 5 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
001101 A ICCF.WEEKLY 1 1 1 10/28/99 16.57 A F5 383 6250 SYJ006W 569
CA EXCEPTION REPORT TDYNUTL-04 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 18.18.56
---------------DATA-SET-NAME---------------- VOLSER VERSION VOLUME EXCEPTION-DESCRIPTION
NUM.1 NUM001 1 1 DATA SET MANUALLY CATALOGUED

NUM002 2 1 DATA SET MANUALLY CATALOGUED
NUMBER.2 NUM021 1 1 DATA SET MANUALLY CATALOGUED
NUMBR.3 NUM031 1 1 DATA SET MANUALLY CATALOGUED

TDYNUTL Reports
CA SELECTED DATA SET NAME LISTING TDYNUTL-05 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 18.19.33
DSN VLT VOLSER VER VOL FIL OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION----- PED PED TAPE MSG
D.SAVE.IT
A 001333 1 1 3 10/29/99 10/29/99 02.24 A F5 380 6250 CPJOB 472
A 001534 2 1 3 10/22/99 10/22/99 06.04 A F5 383 6250 CPJOB 656
A 002067 3 1 3 10/15/99 10/15/99 14.30 A F5 380 6250 CPJOB 123
CA INVENTORY OF ALL SCRATCH TAPES TDYNUTL-06 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 15.51.37
VOLSER OWNER -------------LAST-DATA-SET-NAME------------- SCRATCHED LENGTH MODE TAPE-ERRS
NUM001 NUM.1 01/11/00 NOT INITIALIZED

NUM002 NUM.1 01/11/00 NOT INITIALIZED
NUM021 NUMBER.2 01/11/00 NOT INITIALIZED
NUM031 NUMBR.3 01/11/00 NOT INITIALIZED
001104 NU.LOAN 12/02/99 MS 6250 380 * CLEAN *
001107 NU.S.LOAN 12/02/99 6250 783 * CLEAN *
001109 F.SORT 09/18/00 6250
001117 NU.CLAIM 10/24/99 6250 333 * CLEAN *
001119 NU.COMP 12/02/99 6250 437 * CLEAN *
001121 NU.POLICY.MSTR 12/02/99 6250 495 * CLEAN *
001123 NU.TRANS 12/02/99 6250 310 * CLEAN *
A–6 User Guide

TDYNUTL Reports
CA CURRENT ACTIVITY BY DATA SET NAME TDYNUTL-07 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 19.21.33
DSN VLT VOLSER VER VOL FIL OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION------ PED PED TAPE MSG
AP.MASTER.BKUP
A/P MASTER FILE BACKUP TAPE
A 000770 1 2 0 4 A BG CARP2050 01/23/86
A 002447 2 1 0 4 12/23/85 12/23/85 18.02 A BG CARP2050 01/23/86
A 000921 2 2 0 4 A BG CARP2050 01/23/86
A 001879 3 1 0 4 12/20/85 12/20/85 18.03 A BG CARP2050 01/23/86
A 002271 4 1 0 4 12/19/85 12/19/85 18.03 A BG CARP2050 01/23/86
AP.VNDR.MSTR
A/P VENDOR MASTER
A 000894 2 1 0 3 12/08/85 12/08/85 18.03 A BG CAAP0301 01/23/86
A 000083 3 1 0 3 12/13/85 12/13/85 18.03 A BG CAAP0301 01/23/86
AR.BACKUP
A/R MASTER BACKUP
A 100423 1 2 AR CM MC 0 2 A BG AR 01/23/86
A 100483 2 1 AR CM MC 0 2 12/13/83 12/13/83 18.03 A BG NNCCM 01/23/86
A 000659 3* 1 AR CM MC 0 2 06/13/83 06/13/83 18.03 A BG BAAR0605 01/23/86
AR.DESC.1
ACCNTS RECEIVABLE DESCRIPTION - FILE 1
A 100723 2 1 1 2 05/10/85 05/09/85 18.03 A BG ARDESCUP 01/23/86
A 009876 3* 1 1 2 04/20/85 04/19/85 18.03 A BG DESCUPD 01/23/86
DYNAUDT.BACKUP
DYNAM AUDIT HISTORY FILE BACKUP
EMP.MASTER.BKUP
EMPLOYEE MASTER BACKUP TAPE
A 000505 1 2 TA 53 30 3 15 A BG EMP00901 NO
A 000679 1 3 TA 53 30 3 15 A BG EMP00901 NO
A 001794 2 1 TA 53 30 3 15 01/30/86 12/31/85 18.03 A BG EMP00901 NO
A 000926 2 2 TA 53 30 3 15 A BG EMP00901 NO
A 001283 3 1 TA 53 30 3 15 01/14/86 12/15/85 18.03 A BG EMP00901 NO
A 000428 3 2 TA 53 30 3 15 A BG EMP00901 NO
EMP.MASTER.FILE
EMPLOYEE MASTER FILE
A 000711 1 2 0 3 A BG EMP00801 01/23/86
A 000905 1 3 0 3 A BG EMP00801 01/23/86
EMP.TRAN.FILE
EMPLOYEE TRANSACTION FILE

TDYNUTL Reports
CURRENT ACTIVITY BY VOLUME SERIAL NUMBER
CA CURRENT ACTIVITY BY VOLUME SERIAL NUMBER TDYNUTL-08 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 19.21.33
VOLSER VLT ----------------DATA-SET-NAME--------------- VER VOL FIL OW SY US ------------CREATION-INFORMATION--------- TAPE

000083 A AP.VNDR.MSTR 3 1 1 12/13/85 18.03 A BG CAAP0301

000427 A DYNAUDT.BACKUP 1 1 1 01/23/86 18.39 A BG 182 6250 GK53AUBK
000428 A EMP.MASTER.BKUP 3 2 1 TA 53 12/15/85 18.03 A BG EMP00901
000610 A EMP.TRAN.FILE 1 1 1 11/01/85 18.02 A BG EMP00801
000615 A EMP.MASTER.FILE 1 1 1 11/01/85 18.02 A BG EMP00801
000659 A AR.BACKUP 3 1 1 AR CM MC 06/13/83 18.03 A BG BAAR0605
000770 A AP.MASTER.BKUP 1 2 1 12/24/85 18.02 A BG CARP2050
009876 A AR.DESC.1 3 1 1 04/19/85 18.03 A BG DESCUPD
100423 A AR.BACKUP 1 2 1 AR CM MC 06/15/84 18.03 A BG AR
100483 A AR.BACKUP 2 1 1 AR CM MC 12/13/83 18.03 A BG NNCCM
100486 A AR.BACKUP 1 1 1 AR CM MC 06/15/84 18.03 A BG AR
100723 A AR.DESC.1 2 1 1 05/09/85 18.03 A BG ARDESCUP
100744 A AR.DESC.1 1 1 1 06/04/85 18.03 A BG ARDESCUP
CA LIST OF SELECTED VOLUME SERIAL NUMBERS TDYNUTL-09 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 18.34.35


NU.EXC 5 3 3 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NU.TX 5 3 4 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
NUS.RV 5 3 5 10/27/99 04.24 A F5 381 6250 CPJSAVE1 466
A–8 User Guide

DYNCAT Reports
DYNCAT Reports
// JOB DYNCAT SCRATCH DYNAM/T TAPES
// EXTENT SYS001...
// ASSGN SYS001,150
SCRATCH NOLIST
/*
/&
TAPES SCRATCHED IN THIS RUN
CA TAPES SCRATCHED IN THIS RUN TDYNUTL-05 PAGE 1

CA Dynam 7.1 0709YD000 11 JAN 2007 18.17.40
VOLSER ----------------DATA-SET-NAME------------ VERSION VOLUME OWN SYS USR CREATION PED REMARKS
ID ID ID DATE
000659 AR.BACKUP 3 1 AR CM MC 06/13/83 01/23/86 TAPE NOT INITIALIZED BY DYNAM/T

009876 AR.DESC.1 3 1 04/19/85 01/23/86 TAPE NOT INITIALIZED BY DYNAM/T

DYNCAT Reports
// JOB DYNCAT DEFINE DSN

LISTCAT '70RH.GDG'
/*
/&
CA LISTCAT REPORT PAGE 1

CA Dynam 7.1 0709YD000 22 JUN 2007 20.26.42
DATA SET NAME - 70RH.GDG FILE TYPE - DISK
COMMENT - NONE DEFINED

OIMSG - NONE DEFINED
OOMSG - NONE DEFINED
CIMSG - NONE DEFINED
COMSG - NONE DEFINED
KEKL1 - NONE DEFINED
KEKL2 - NONE DEFINED
DATA SET ATTRIBUTES

---- --- ----------
NUMBER OF CYCLES - 5 EXPIRATION DATE - RETENTION DAYS - 11 NOACC DAYS - 0

PED - PED CYCLES - 0 SPECIFIED DENSITY - SPECIFIED LENGTH - ANY
OWNER ID - USER ID - SYSTEM ID - PASSWORD PROTECTED - NO
WORK DATA SET - NO LOCKED FOR OUTPUT - NO RECORD FORMAT - BLOCKSIZE -
LRECL - NUMBER OF BUFFERS - BUFFER TECHNIQUE - SIMPLE BUFFER ALIGNMENT - FULLWORD
NUMBER OF OPENS - 12 CATOPEN - NO DYNAMFI - NO ROBOT - YES
SYSNO OVERRIDE - VOLID - VIRTAPE - NO
TAPE OPTIONS -
DISK OPTIONS -
PROCESSING OPTIONS -
STATUS FLAGS -
AMF SEQUENCE COUNT - 0 MULTI-FILE - NO FILE SEQUENCE NUMBER - 1 DISK GENID - 05
PRIOR DSN - NEXT DSN -
DBR CREATE DATE - 20 JUN 2000 TIME - 15.29.04 CPUID - A ID - F4

JOB - CICSOLD1 STEP - CAYDSERV PROC -
DBR UPDATE DATE - TIME - CPUID - ID -

JOB - STEP - PROC -
DEFAULT VAULT - A
VAULT SEQUENCE -
DISK ALLOCATION
---- ----------
SEQ - 0 VOLSER - SYSWK1 UNITS - TRK SYSNO - TYPE - PRIME START - 1 EXTENT 5
A–10 User Guide

DYNCAT Reports

CA Dynam 7.1 0709YD000 22 JUN 2007 20.26.42
DSN - 70RH.GDG G#02 VERSION ATTRIBUTES VERSION TYPE - DISK

------- ----------
VERSION NUMBER - 1 EXPIRATION DATE - PERM RETENTION DAYS - NUMBER OF OPENS - 0

PED - ABSOLUTE VERSION - 2 DENSITY - WRITE ERRORS - 0
OWNER ID - USER ID - SYSTEM ID - READ ERRORS - 0
NUMBER TRKS/BLKS - 1 LOCKED FOR INPUT - NO RECORD FORMAT - FB BLOCKSIZE - 300
LRECL - 100 STARTING BLOCK ID -
TAPE OPTIONS -
DISK OPTIONS -
STATUS FLAGS -
GBR CREATE DATE - 22 JUN 2000 TIME - 19.54.52 CPUID - A OPSYS - DOS/VSE ID - BG
JOB - SORT STEP - SORT PROC -
GBR UPDATE DATE - TIME - CPUID - OPSYS - ID -
JOB - STEP - PROC -
GBR ACCESS DATE - 22 JUN 2000 TIME - 19.54.52 CPUID - A OPSYS - DOS/VSE ID - BG
VAULT LOCATION - A
VOLUMES - SYSWK1
DSN - 70RH.GDG G#01 VERSION ATTRIBUTES VERSION TYPE - DISK

------- ----------
VERSION NUMBER - 2 EXPIRATION DATE - PERM RETENTION DAYS - NUMBER OF OPENS - 1
PED - ABSOLUTE VERSION - 1 DENSITY - WRITE ERRORS - 0
OWNER ID - USER ID - SYSTEM ID - READ ERRORS - 0
NUMBER TRKS/BLKS - 1 LOCKED FOR INPUT - NO RECORD FORMAT - FB BLOCKSIZE - 300
LRECL - 100 STARTING BLOCK ID -
TAPE OPTIONS -
DISK OPTIONS -
STATUS FLAGS -
GBR CREATE DATE - 22 JUN 2000 TIME - 19.53.45 CPUID - A OPSYS - DOS/VSE ID - BG
GBR UPDATE DATE - TIME - CPUID - OPSYS - ID -
JOB - STEP - PROC -
GBR ACCESS DATE - 22 JUN 2000 TIME - 19.54.52 CPUID - A OPSYS - DOS/VSE ID - BG
VAULT LOCATION - A
VOLUMES - SYSWK1

CA Dynam 7.1 0709YD000 11 JAN 2007 19.02.31
VOLSER - 000531 VOLUME ATTRIBUTES

------ ----------
OWNER ID - VAULT LOCATION - A REEL SIZE - ANY DENSITY -

VOLUME STATUS - ACTIVE
NUMBER OF FILES - 1 NUMBER ACTIVE FILES - 1 VOLUME SEQ - 1 CLEANING THRESHOLD - 100
NUMBER OPENS OUTPUT - 114 NUMBER OPENS INPUT - 56 OUTPUT ERRORS - 254 INPUT ERRORS - 0
DATE FIRST INIT - 18 APR 1988 DATE LAST INIT - DATE LAST SCRATCHED - 28 OCT 1988 DATE LAST CLEANED - 18 APR 1988
VBR ACCESS DATE - 29 OCT 1988 TIME - 04.37.39 CPUID - A OPSYS - DOS/VSE ID - F5
JOB - VLJ5 STEP - SORT PROC -
REASON LAST SCRATCH -
EXTERNAL OWNER - VIRTAPE - NO
DSNS ON VOLUME - NU.CLAIM VTAPE LOCATION - VSAM
VTAPE FILE – 1111

TDYNVLT Reports
TDYNVLT Reports
This JCL produces reports TDYNVLT-01 through TDYNVLT-05.
// JOB TDYNVLT VAULT MOVEMENT AND INVENTORY

// EXTENT SYS001...
// ASSGN SYS001,150
// EXTENT SYS002...
// ASSGN SYS002,151
MOVEMENT
INVENTORY SEQ=DSN
/*
/&
LOCATION MOVEMENT EXIT REPORT
CA L O C A T I O N M O V E M E N T E X I T R E P O R T TDYNVLT-01 PAGE 1
CA Dynam 7.1 0709YD000 11 JAN 2007 18.06.35
VAULT A TAPE LIBRARY
-----------------------------------------------------------------------------------------------------------------------------
FROM TO VOL.
V SLOT V SLOT VOLSER SEQ VRS DATA SET NAME COMMENT
-----------------------------------------------------------------------------------------------------------------------------
A D 000428 02 3 EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
A X 000926 02 2 EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
A D 001283 01 3 EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
A X 001794 01 2 EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
A B 100423 02 1 AR.BACKUP A/R MASTER BACKUP
A C 100483 01 2 AR.BACKUP A/R MASTER BACKUP
A B 100486 01 1 AR.BACKUP A/R MASTER BACKUP
*** TOTAL VOLUMES EXITING VAULT A 7
LOCATION MOVEMENT ENTRY REPORT
CA L O C A T I O N M O V E M E N T E N T R Y R E P O R T TDYNVLT-02 PAGE 1
CA Dynam 7.1 0709YD000 11 JAN 2007 18.06.35
VAULT B OFFSITE VAULT LOCATION 1
-----------------------------------------------------------------------------------------------------------------------------
TO FROM VOL.
V SLOT VOLSER V SLOT SEQ VRS DATA SET NAME COMMENT
-----------------------------------------------------------------------------------------------------------------------------
B 100423 A 02 1 AR.BACKUP A/R MASTER BACKUP
B 100486 A 01 1 AR.BACKUP A/R MASTER BACKUP
*** TOTAL VOLUMES ENTERING VAULT B 2
A–12 User Guide

TDYNVLT Reports
LOCATION MOVEMENT SUMMARY REPORT
CA L O C A T I O N M O V E M E N T S U M M A R Y R E P O R T TDYNVLT-03 PAGE 1
CA Dynam 7.1 0709YD000 11 JAN 2007 18.06.35
----------------------------------------------------------------------------------------------------------------------------
VOL. FROM TO
VOLSER SEQ VRS V SLOT V SLOT DATA SET NAME COMMENT
-----------------------------------------------------------------------------------------------------------------------------
000428 2 3 A D EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
000926 2 2 A X EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
001283 1 3 A D EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
001794 1 2 A X EMP.MASTER.BKUP EMPLOYEE MASTER BACKUP TAPE
100423 2 1 A B AR.BACKUP A/R MASTER BACKUP
100483 1 2 A C AR.BACKUP A/R MASTER BACKUP
100486 1 1 A B AR.BACKUP A/R MASTER BACKUP
*** TOTAL VOLUMES 7
LOCATION INVENTORY REPORT
CA L O C A T I O N I N V E N T O R Y R E P O R T TDYNVLT-05 PAGE 1
CA Dynam 7.1 0709YD000 11 JAN 2007 18.06.35
-----------------------------------------------------------------------------------------------------------------------------
VOL. LOC OW SY US
DATA SET NAME VRS VOLSER SEQ V SLOT ID ID ID COMMENT
-----------------------------------------------------------------------------------------------------------------------------
AP.MASTER.BKUP 1 002256 1 A A/P MASTER FILE BACKUP TAPE

AP.VNDR.MSTR 1 002926 1 A A/P VENDOR MASTER

AR.BACKUP 1 100486 1 A AR CM MC A/R MASTER BACKUP

AR.DESC.1 1 100744 1 A ACCTS RECEIVABLE DESCRIPTION - FILE 1

EMP.MASTER.BKUP 1 002525 1 A TA 53 EMPLOYEE MASTER BACKUP TAPE

EMP.MASTER.FILE 1 000615 1 A EMPLOYEE MASTER FILE

EMP.TRAN.FILE 1 000610 1 A EMPLOYEE TRANSACTION FILE

TDYNLIST Reports
TDYNLIST Reports
// JOB TDYNLIST
// DLBL WORK1,'DYNAM.WORK.FILE.1.CPU--.=='
// EXTENT SYS003,3350WK,1,1,1,400
// EXEC TDYNLIST,SIZE=128K
TITLE=TITLE ONE
STEP=STEP ONE
DN='NUM.1',VR=1,NOTE=UPDATE MASTER FILE
DN='NUM.1',VR=2
DN='NUMBER.2',VR=3
DN='NUMBER.2',VR=2
DN='NUMBR.3',VR=1
DN='NUMBR.3',VR=2
DN='NUMBR.3',SCRATCH
DN='NUMBR.3',VR=3
NOTE=RUN THIS JOB ON THE FIRST AND 16TH OF THE MONTH
TITLE=TITLE TWO
STEP=STEP TWO
DN='NUM.1',VR=2,NOTE=PREPARE REPORTS
DN='NUMBER.2',VR=1
DN='NUMBER.2',VR=2
DN='NUMBER.2',VR=3
DN='NUMBR.3',NEW
ROUTE
/*
/&
DATE 01/11/07 TIME 16.40 TITLE ONE

*CA Dynam/T 7.1 0012YD700* TDYNLIST-01 PAGE 1
DATA SET NAME VER VOLUMES DEN VLT COMMENTS

******************************************** *** ****** ****** ****** *** *** ********************************************
STEP ONE STEP # 1

NUM.1 1 NUM001 B UPDATE MASTER FILE
NUM.1 2 NUM002 B
NUMBER.2 3 NUM023 A
NUMBER.2 2 NUM022 A
NUMBR.3 1 NUM031 C
NUMBR.3 2 NUM032 C
NUMBR.3 SCRATCH TAPES NEEDED 01
NUMBR.3 3 NUM033 C
RUN THIS JOB ON THE FIRST AND 16TH OF THE MONTH
A–14 User Guide

TDYNLIST Reports
DATE 01/11/07 TIME 16.40 TITLE TWO

DATA SET NAME VER VOLUMES DEN VLT COMMENTS

******************************************** *** ****** ****** ****** *** *** ********************************************
STEP TWO STEP # 2

NUM.1 2 NUM002 B PREPARE REPORTS
NUMBER.2 1 NUM021 A
NUMBER.2 2 NUM022 A
NUMBER.2 3 NUM023 A
NUMBR.3 CREATED IN PREV. STEP# 1
****************************************************************************************************************************
* * USER *DATA CONTROL* TAPE * COMPUTER *FORMS CONTRL* USER *DATA CONTROL* * *
* * DEPARTMENT * CLERK * LIBRARIAN * OPERATOR * CLERK * DEPARTMENT * CLERK * * *
****************************************************************************************************************************
* * * * * * * * * * *
* * * * * * * * * * *
****************************************************************************************************************************
DATE 01/11/07 TIME 16.40 DYNAM/T PULL LIST BY VOLUME SERIAL NUMBER
DATA SET NAME VOLUMES VERSION VOLSEQ DENSITY VLT
NUM.1 NUM001 1 1 B
NUM.1 NUM002 2 1 B
NUMBER.2 NUM021 1 1 A
NUMBR.3 NUM031 1 1 C
APPROXIMATE NUMBER SCRATCH TAPES NEEDED 1

TDYNSYNC Reports
TDYNSYNC Reports
APPLY
CATNAME=CAICATL
APPLY
CA CATALOG APPLY TDYNSYNC PAGE 1
CA Dynam . 22 MAY 2000 TIME 14.27.44
DATASET NAME EXT VOLSER VER VOL FIL VLT SLOT MESSAGE
OWN SEQ SEQ
JNB002 1 A ** VOLUME ADDED
B JN4281 1 A ** VOLUME ADDED
B 000027 1 A ** VOLUME ADDED
APPLY TRANSACTIONS
SCRATCH 0
ADD 25
CATALOG
ACTIVE VOLUMES SCRATCHED
VOLUMES ADDED (ACTIVE EXTERNAL OWNER) 23
VOLUMES ADDED (SCRATCH) 2
A–16 User Guide

TDYNSYNC Reports
EXTRACT
CATNAME=CAICATL
EXTRACT
CA CATALOG EXTRACT TDYNSYNC PAGE 1
CA Dynam . 22 MAY 2000 TIME 14.07.55
DATASET NAME EXT VOLSER VER VOL FIL VLT SLOT MESSAGE
OWN SEQ SEQ
JOETEST1 000001 1 A ** ACTIVE VOLUME
JOETEST1 000002 2 A ** ACTIVE VOLUME
DYN21.CATALOG 000003 1 A ** ACTIVE VOLUME
DYNAM.CMS.WEEKLY 000004 1 A ** ACTIVE VOLUME
DYNAM.CMS.DAILY 000007 1 A ** ACTIVE VOLUME
DYN21.CATALOG 000008 1 A ** ACTIVE VOLUME
DYNAM.DDR.MONTHLY 000009 1 A ** ACTIVE VOLUME
UPLEX.DDR.MONTHLY 000010 1 A ** ACTIVE VOLUME
DYNAM.DDR.MONTHLY 000011 1 A ** ACTIVE VOLUME
UPLEX.DDR.MONTHLY 000012 1 A ** ACTIVE VOLUME
TST21.DDR.MONTHLY 000013 1 A ** ACTIVE VOLUME
000020 A ** SCRATCH VOLUME
ACCT.MF1 000501 1 A ** ACTIVE VOLUME
EXTRACT TRANSACTIONS CREATED

SCRATCH 20
ACTIVE 25

TDYNSYNC Reports
SYNC
SYNC
CA CATALOG SYNCHRONIZATION TDYNSYNC PAGE 1
CA Dynam . 22 MAY 2000 TIME 14.07.55
CA Dynam/T CA 1 MVS
VOLSER DATA SET NAME STAT CREATED SYSTEM DATA SET NAME STAT CREATED SYSTEM DEST MESSAGE
JNB002 SCR 89109 1455 SYS1 VOLSER NOT ON SYS1 EXTRACT
JN4281 JOETEST ACT 89118 1421 VM-CPU1 SYS1 VOLSER NOT ON SYS1 EXTRACT
000001 JOETEST1 ACT 89129 1503 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000002 JOETEST1 ACT 89129 1531 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000003 DYN21.CATALOG ACT 89129 1634 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000004 DYNAM.CMS.WEEKLY ACT 89129 1658 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000007 DYNAM.CMS.DAILY ACT 89130 1446 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000008 DYN21.CATALOG ACT 89130 1532 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000009 DYNAM.DDR.MONTHLY ACT 89142 1114 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000010 UPLEX.DDR.MONTHLY ACT 89142 1114 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000011 DYNAM.DDR.MONTHLY ACT 89142 1132 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000012 UPLEX.DDR.MONTHLY ACT 89142 1133 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000013 TST21.DDR.MONTHLY ACT 89142 1210 VM-CPU1 SYS2 VOLSER NOT ON SYS2 EXTRACT
000020 SCR 89142 1403 SYS2 VOLSER NOT ON SYS2 EXTRACT
000027 SCR 89142 1403 DYN21C.IJSYSBK ACT 89135 1717 VM-CPU1 SYS1 VOLUME STATUS DOES NOT MATCH
000032 SCR 89142 1403 DYNB21C.DYNBBKUP ACT 89135 1717 VM-CPU1 SYS1 VOLUME STATUS DOES NOT MATCH
000501 ACCT.MF1 ACT 89142 1352VSE-CPU1 DYN21.CMS.DAILY ACT 89135 1716 VM-CPU1 SYS2 EACH SYSTEM CLAIMS OWNERSHIP
000510 DYN21.CMS.DAILY ACT 89135 1716 VM-CPU1 SYS1 VOLSER NOT ON SYS1 EXTRACT
000517 DYN21.CMS.WEEKLY ACT 89135 1716 VM-CPU1 SYS1 VOLSER NOT ON SYS1 EXTRACT
SYS1 SYS2
TOTAL RECORDS READ 45 34
TOTAL RECORDS WRITTEN 25 32
TOTAL RECORDS INVALID 0 0
A–18 User Guide


ACTVFILE
CA A C T I V E C A T A L O G F I L E S ACTVFILE PAGE 1
CA Dynam 7.1 0709YD000 23/01/07 15.06.37
== SORTED BY FILE-ID/VERSION (DEFAULT) == SELECT: FID
DSN VLT VOLSER VER VOL FSQ OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION------------ PED PED TAPE MSG
TYPE /EXT DAY NGEN NOAC EXP-DATE DATE TIME CPU PT CUU MODE LEN JOB-NAME CYC ERRS
YDPRASAM.01.AP.MASTER
THIS FILE UPDATED DAILY
DISK T33500 1 1 0 DS TS CA 1 6 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
YDPRASAM.02.OPTICAL.DATA
DISK T33800 1 1 0 DS VS WD 1 -RETAIN- 12/23/99 15:05 A BG 181 YDPRASAM
YDPRASAM.03.AP.VENDOR
DISK T33800 1 1 0 LT TS CA 183 06/24/00 12/23/99 15:06 A BG 181 YDPRASAM
YDPRASAM.04.EMP.MASTER
DISK T33802 1 1 0 LT TS WD 1 90 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
YDPRASAM.12.FIXED.ASSETS
DISK T33800 1 1 0 1 3 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
YDPRASAM.13.AP.DESCR1
CA Dynam 7.1 0709YD000 23/01/07 15.06.37
== SORTED BY OWNER-ID/FILE-ID/VERSION == SELECT: OWNE
DISK T33800 1 1 0 DS VS WD 1 -RETAIN- 12/23/99 15:05 A BG 181 YDPRASAM

CA Dynam 7.1 0709YD000 23/01/07 15.06.37
== SORTED BY SYSTEM-ID/FILE-ID/VERSION == SELECT: SYSTE
YDPRASAM.04.EMP.MASTER
DISK T33802 1 1 0 LT TS WD 1 90 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
CA Dynam 7.1 0709YD000 23/01/07 15.06.37
== SORTED BY USER-ID/FILE-ID/VERSION == SELECT: USE
CA Dynam 7.1 0709YD000 23/01/07 15.06.37
== SORTED BY VOLSER/FILESEQ/FILE-ID == SELECT: VOL
TYPE VLT VOLSER VER VOL FSQ OW SY US ----RETENTION-INFO---- -----------CREATION-INFORMATION------------ PED PED TAPE MSG
DSN /EXT DAY NGEN NOAC EXP-DATE DATE TIME CPU PT CUU MODE LEN JOB-NAME CYC ERRS
YDPRASAM.14.EMP.BIOG.DATA
PASSWORD PROTECTED DSN
DISK T33500
1 1 0 DS TS CA 1 6 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
1 1 0 1 7 02/28/99 12/23/99 15:06 A BG 181 YDPRASAM
2 1 0 1 7 02/28/99 12/23/99 15:06 A BG 181 YDPRASAM
3 1 0 1 7 02/28/99 12/23/99 15:06 A BG 181 YDPRASAM
DISK T33800
1 1 0 DS VS WD 1 -RETAIN- 12/23/99 15:05 A BG 181 YDPRASAM
1 1 0 LT TS CA 183 06/24/00 12/23/99 15:06 A BG 181 YDPRASAM
YDPRASAM.12.FIXED.ASSETS
1 1 0 1 3 12/30/99 12/23/99 15:06 A BG 181 YDPRASAM
A–20 User Guide

FILEDEFS
CA C A T A L O G F I L E D E F I N I T I O N S FILEDEFS PAGE 1
CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: DISK ALLOCATION SPECIFICATIONS == SELECT:
TYPE VERS -------------- DATA SET NAME--------------- ------ PRIMARY EXTENT ------ ------- SECONDARY EXTENTS ------- LOGICAL
VOLSER -START- --SIZE- UNITS TRIES VOLSER -START- --SIZE- UNITS UNIT
DISK 4 YDPRFSAM.01.AP.MASTER T3350* 1 2 TRK 4 T3350* 1 3 TRK SYSOMP

DISK 1 YDPRFSAM.02.OPTICAL.DATA T3380* 1 5 TRK
FI 1 YDPRFSAM.03.AP.VENDOR T33800 1 2 TRK 5 T33800 1 1 TRK SYS255
FI 1 YDPRFSAM.04.EMP.MASTER T33802 1 4 TRK 2 T33802 1 3 TRK SYS255
FI 1 YDPRFSAM.12.FIXED.ASSETS T3380* 1 1 CYL
FI 3 YDPRFSAM.13.AP.DESCR1 T3350* 1 1 TRK 4 T3350* 1 2 TRK SYS255
YDPRFSAM.14.EMP.BIOG.DATA === PASSWORD PROTECTED DATASET ===
CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: CATALOG MAINTENANCE INFORMATION == SELECT:
TYPE VERS -------------- DATA SET NAME--------------- --DATE-- --TIME-- CPU PART JOBNAME PROCNAME STEPNAME SYSNAME
DISK 4 YDPRFSAM.01.AP.MASTER 12/23/99 14:59:58 A BG YDPRFSAM DYNCAT DOS/VSE

DISK 1 YDPRFSAM.02.OPTICAL.DATA 12/23/99 14:59:58 A BG YDPRFSAM DYNCAT DOS/VSE
FI 1 YDPRFSAM.03.AP.VENDOR 12/23/99 14:59:59 A BG YDPRFSAM DYNCAT DOS/VSE
FI 1 YDPRFSAM.04.EMP.MASTER 12/23/99 14:59:59 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.05.PAYROLL.MASTER 12/23/99 15:00:00 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.06.PAYROLL.TRANS 12/23/99 15:00:00 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.07.PAYROLL.CURR 12/23/99 15:00:00 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.08.PAYROLL.PREV 12/23/99 15:00:01 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.09.PAYROLL.TOTALS 12/23/99 15:00:01 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.10.OPT.DESCRIPT 12/23/99 15:00:01 A BG YDPRFSAM DYNCAT DOS/VSE
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA 12/23/99 15:00:02 A BG YDPRFSAM DYNCAT DOS/VSE
FI 1 YDPRFSAM.12.FIXED.ASSETS 12/23/99 15:00:02 A BG YDPRFSAM DYNCAT DOS/VSE
FI 3 YDPRFSAM.13.AP.DESCR1 12/23/99 15:00:03 A BG YDPRFSAM DYNCAT DOS/VSE
LAST MANUAL UPDATE: 12/23/99 15:00:05 A BG YDPRFSAM DYNCAT DOS/VSE
CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: COMMENT AND MESSAGES == SELECT:
TYPE VERS -------------- DATA SET NAME---------------
DISK 4 YDPRFSAM.01.AP.MASTER
COMMENT: THIS FILE UPDATED DAILY
DISK 1 YDPRFSAM.02.OPTICAL.DATA
TO: PROGRAMMER OPEN INPUT MESSAGE: RETURN OUTPUT OPT ICAL DEPT.
FI 1 YDPRFSAM.03.AP.VENDOR
TO: OPERATOR OPEN OUTPUT MESSAGE: USE RESERVED SPACE 32
FI 1 YDPRFSAM.04.EMP.MASTER
TO: OPER & PROG CLOSE INPUT MESSAGE: FILE TERMINATED
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA
COMMENT: INFO FIELD TESTS
FI 1 YDPRFSAM.12.FIXED.ASSETS
TO: OPERATOR OPEN INPUT MESSAGE: FILE CONTENTS NEVER CHANGE
TO: OPERATOR CLOSE INPUT MESSAGE: CONTENTS SAME

CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: MULTIFILE SET INFORMATION == SELECT:
TYPE VERS -------------- DATA SET NAME--------------- MULTI-FILE AUTO-MULTI-FILE -------

SEQ. SEQ NO. NEW TAPE
TAPE 0 YDPRFSAM.05.PAYROLL.MASTER YES 1 NO

PRIOR DSN: NEXT DSN: YDPRFSAM.06.PAYROLL.TRANS
TAPE 0 YDPRFSAM.06.PAYROLL.TRANS YES 2 NO
PRIOR DSN: YDPRFSAM.05.PAYROLL.MASTER NEXT DSN: YDPRFSAM.07.PAYROLL.CURR
TAPE 0 YDPRFSAM.07.PAYROLL.CURR YES 3 NO
PRIOR DSN: YDPRFSAM.06.PAYROLL.TRANS NEXT DSN: YDPRFSAM.08.PAYROLL.PREV
TAPE 0 YDPRFSAM.08.PAYROLL.PREV YES 4 NO
PRIOR DSN: YDPRFSAM.07.PAYROLL.CURR NEXT DSN: YDPRFSAM.09.PAYROLL.TOTALS
TAPE 0 YDPRFSAM.09.PAYROLL.TOTALS YES 5 NO
PRIOR DSN: YDPRFSAM.08.PAYROLL.PREV NEXT DSN:
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA NO 1 YES 1 NO
CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: DEFAULT RETENTION SPECIFICATIONS == SELECT:
TYPE VERS -------------- DATA SET NAME--------------- EXPDATE RETN DAYS VERSIONS NOACC DAYS DISK PERIOD-ENDING DATE/CYCLES
GEN
DISK 4 YDPRFSAM.01.AP.MASTER 1 6 4
DISK 1 YDPRFSAM.02.OPTICAL.DATA -RETAIN- 1
FI 1 YDPRFSAM.03.AP.VENDOR 183
FI 1 YDPRFSAM.04.EMP.MASTER 1 90
TAPE 0 YDPRFSAM.05.PAYROLL.MASTER 1 9 12/31/** 2
TAPE 0 YDPRFSAM.06.PAYROLL.TRANS 1 9 12/31/** 2
TAPE 0 YDPRFSAM.07.PAYROLL.CURR 1 9 12/31/** 2
TAPE 0 YDPRFSAM.08.PAYROLL.PREV 1 9 12/31/** 2
TAPE 0 YDPRFSAM.09.PAYROLL.TOTALS 1 9 12/31/** 2
TAPE 0 YDPRFSAM.10.OPT.DESCRIPT 1 20 **/01/** 12
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA 1
FI 1 YDPRFSAM.12.FIXED.ASSETS 1 3 1
FI 3 YDPRFSAM.13.AP.DESCR1 02/28/99 1 7 3
A–22 User Guide

CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: ADMIN. AND TECH. SPECS. == SELECT:
TYPE VERS -------------- DATA SET NAME--------------- OW SY US AUTO OPENS TYPE FMT LRECL BLKSZ KEYLN KEY BUFFERS TAPE VWL
SQNO OFFSET NO. T A SZ MODE
DISK 4 YDPRFSAM.01.AP.MASTER DS TS CA 4 DA S F NNN

DYNAM/D OPTIONS: E,R,K
DISK 1 YDPRFSAM.02.OPTICAL.DATA DS VS WD 1 FB 100 S F NNN
DYNAM/D OPTIONS: N,R,M
FI 1 YDPRFSAM.03.AP.VENDOR LT TS CA 1 FB 100 1800 S F S 6250 NNN
DYNAM/T OPTIONS: U,A
DYNAM/D OPTIONS: D,I,R
FI 1 YDPRFSAM.04.EMP.MASTER LT TS WD 1 S F 1600 NNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.05.PAYROLL.MASTER DS VS WD S F VNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.06.PAYROLL.TRANS DS VS WD S F NNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.07.PAYROLL.CURR DS VS WD S F NNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.08.PAYROLL.PREV DS VS WD S F NNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.09.PAYROLL.TOTALS DS VS WD S F NNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.10.OPT.DESCRIPT LT TS WD S F VNN
DYNAM/D OPTIONS: R
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA 1 S F VNN
DYNAM/D OPTIONS: R
FI 1 YDPRFSAM.12.FIXED.ASSETS 1 S F NNN
DYNAM/D OPTIONS: R
CA Dynam 7.1 0709YD000 23/01/07 15.00.58
== SORTED BY FILE-ID: VAULT ROTATION INFORMATION == SELECT:
TYPE VERS -------------- DATA SET NAME---------------

5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100
|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|
TAPE 0 YDPRFSAM.05.PAYROLL.MASTER
AAADUSF
TAPE 0 YDPRFSAM.10.OPT.DESCRIPT
AAFFSUDDDSA
TAPE 0 YDPRFSAM.11.***.PRODUCT.DATA
AFSUUDSUUFF
|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|----+----|
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100

FREQUSE
CA F I L E U S A G E F R E Q U E N C Y FREQUSE PAGE 1
CA Dynam 7.1 0709YD000 23/01/07 15.53.26
== SORTED BY AVERAGE OPENS PER DAY == SELECT: AVOP
DAYS AVERAGE
EXTS FIRST CREATION EXP. LAST ACCESS JOBNAME W/O TOTAL OPENS
VER FILE IDENTIFICATION VLS VOLUME DATE DATE DATE TIME CREATOR LAST OPEN OPENS PER DAY
1 TEST.FILE.P33501.PERM 1 1 P33501 12/21/99 --PERM-- 12/21/99 14.29 DDMNARP DDMNARP 3 1 0.333

1 TEST.FILE.P33501.RETAIN 3 1 P33501 12/21/99 -RETAIN- 12/21/99 14.19 DDMNIIF DDMNIIF 3 1 0.333
1 TEST.FILE.P33502.MISSING 1 1 P33502 12/21/99 12/28/99 12/21/99 14.28 DDMNARMF DDMNARMF 3 1 0.333
1 TEST.FILE.P33801.EXPIRE 1 1 P33801 12/21/99 01/01/00 12/21/99 14.30 DDMNARSX DDMNARSX 3 1 0.333
4 TEST.GDG.P3350B.POOL.MWF 1 1 P33501 12/21/99 --PERM-- 12/21/99 14.20 DDMNIIG DDMNIIG 3 1 0.333
5 TEST.GDG.P33NNN.GENERIC 1 1 P33501 12/21/99 --PERM-- 12/21/99 14.31 DDMNIIG DDMND01 3 2 0.666
3 TEST.GDG.P3350B.POOL.MWF 1 1 P33502 12/21/99 --PERM-- 12/21/99 14.22 DDMNIIG DDMNPMWF 3 2 0.666
2 TEST.GDG.P3350B.POOL.MWF 1 1 P33501 12/21/99 --PERM-- 12/23/99 12.46 DDMNPMWF DDMNPMWF 1 2 0.666
5 TEST.GDG.P33800.POOL 1 1 P33801 12/21/99 --PERM-- 12/21/99 14.31 DDMNIIG DDMND01 3 2 0.666
1 TEST.FILE.P3350T.POOL 1 1 P33502 12/23/99 12/30/99 12/23/99 12.45 DDMNARDX DDMNARDX 1 1 1.000
1 TEST.FILE.P33802.RETPER 1 1 P33802 12/23/99 12/27/99 12/23/99 12.45 DDMNARRP DDMNARRP 1 1 1.000
3 TEST.GDG.P33NNN.GENERIC 1 1 P33501 12/21/99 --PERM-- 12/23/99 12.46 DDMND01 DDMND01 1 3 1.000
3 TEST.GDG.P33800.POOL 1 1 P33801 12/21/99 --PERM-- 12/23/99 12.46 DDMND01 DDMND01 1 3 1.000
1 TEST.GDG.P33802.REAL.MWF 1 1 P33802 12/23/99 --PERM-- 12/23/99 12.47 DDMNPMWF DDMNPMWF 1 1 1.000
CA Dynam 7.1 0709YD000 23/01/07 15.53.26
== SORTED BY DESCENDING DAYS-SINCE-CREATION == SELECT: DAYS
DAYS AVERAGE

A–24 User Guide

CA Dynam 7.1 0709YD000 23/01/07 15.53.26
== SORTED BY DESCENDING DAYS NOT USED == SELECT: DAYSU
DAYS AVERAGE

CA Dynam 7.1 0709YD000 23/01/07 15.53.26
== SORTED BY FILE-ID/VERSION (DEFAULT) == SELECT: FID
DAYS AVERAGE


SPACEUSE
CA D I S K S P A C E U S A G E A N A L Y S I S SPACEUSE PAGE 1
CA Dynam 7.1 0709YD000 22/01/07 13.56.27
== SORTED ON FILE-ID/EXTENT (DEFAULT) == SELECT: FID
EXTENTS REBLOCKING GAIN INFO ALLOCATION INFO

--------- ------------------------- ----------------------
1ST # ON REC- BLOCKSIZE GAINED TRACKS/BLOCKS PERCENT
FILE IDENTIFICATION VOLUME DEVICE TYPE SQ# VOL. FT RF LEN NOW OPT. SPACE ACTUAL REQUEST HI/LO
DDPRTSAM.06.RINF T33500 3350 CKD 0 2 SD FB 100 500 19000 1 6 4 50-

DDPRTSAM.07.QINF T33500 3350 CKD 0 2 SD FB 100 500 19000 1 6 3 100-
DDPRTSAM.08.PDATA T33501 3350 CKD 0 1 SD FB 100 500 19000 2 10 15 50+
DDPRTSAM.09.EDFILE T33501 3350 CKD 0 1 SD FB 100 500 19000 3 14 20 42+
DDPRTSAM.10.KYS T33800 3380 CKD 0 1 SD FB 100 500 47400 4 9 15 66+
DDPRTSAM.11.PINF T33800 3380 CKD 0 1 SD FB 100 500 47400 2 6 15 150+
DDPRTSAM.12.RDATA.A T33500 3350 CKD 0 1 SD FB 100 500 19000 1 5 5 0
DDPRTSAM.13.SINF T33500 3350 CKD 0 1 SD FB 100 500 19000 1 6 6 0
DDPRTSAM.14.AJN T33500 3350 CKD 0 1 SD FB 100 500 19000 0 1 4 300+
>DDPRTSAM.17.MULTI.FILE T33500 3350 CKD 0 1 SD FB 100 500 19000 0 1
*DDPRTSAM.17.MULTI.FILE T33501 3350 CKD 1 1 SD FB 100 500 19000 0 1
<DDPRTSAM.17.MULTI.FILE T33502 3350 CKD 2 1 SD FB 100 500 19000 0 3
END OF REPORT
- ===> NOT DETERMINED IF FILE IS COMPLETE ON THIS VOLUME

< ===> FILE MAY HAVE PRIOR EXTENTS ON OTHER VOLUME(S)
> ===> FILE MAY HAVE FOLLOWING EXTENTS ON OTHER VOLUME(S)
* ===> FILE MAY HAVE PRIOR AND/OR FOLLOWING EXTENTS ON OTHER VOLUME(S)
# ===> FILE'S EXTENTS ON THIS VOLUME ARE PARTLY OUTSIDE POOL
CA Dynam 7.1 0709YD000 22/01/07 13.56.27
== SORTED ON DECREASING ALLOCATION ERROR PERCENTAGE == SELECT: REAL

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

END OF REPORT

A–26 User Guide

CA Dynam 7.1 0709YD000 22/01/07 13.56.27
== SORTED BY DECREASING GAIN WITH OPTIMUM BLOCKSIZE == SELECT: REBL

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

END OF REPORT

CA Dynam 7.1 0709YD000 22/01/07 13.56.27
== SORTED ON VOLID / FILE-ID == SELECT: VOL

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

>DDPRTSAM.17.MULTI.FILE T33500 3350 CKD 0 1 SD FB 100 500 19000 0 1
T33500
-----
TOTAL (POOL) SPACE USED ON VOLUME(S) = 25
-----
*DDPRTSAM.17.MULTI.FILE T33501 3350 CKD 1 1 SD FB 100 500 19000 0 1
T33501
-----
TOTAL (POOL) SPACE USED ON VOLUME(S) = 25
-----


TAPES
CA T A P E I N V E N T O R Y R E P O R T TAPES PAGE 1
CA Dynam 7.1 0709YD000 23/01/07 16.13.35
== SORTED BY VOLSER/FILESEQ - ACTIVE TAPES == SELECT: ACT
VOLSER VLT ----------------DATA-SET-NAME--------------- VOL FIL OW SY US ------------CREATION-INFORMATION------------ TAPE ERRS

ID ID ID DATE TIME CPU PT CUU MODE LEN JOB-NAME OUT IN
RAPS01 A RAPS.ARCHIVE.OUT 1 1 03/30/99 16:42 A BG 181 6250 ARCHIVE

RAPS02 A RAPS.ARCHIVE.OUT 1 1 03/30/99 16:49 A F4 181 6250 ARCHIVE
TONY01 A LOCK.TEST 1 1 05/10/99 16:50 A BG 180 6250 TONY
0TR987 A RFILE 1 1 12/21/00 12:03 A F2 000 ICCFCICS
00000D A GODRI01.TEST 1 1 09/09/99 10:59 A BG 181 6250 FCOPY1
005409 A HR.RESTORES 1 1 06/07/99 12:25 A F2 000 ICCFCICS
005555 A ZED1 1 1 07/12/99 10:03 A F2 000 ICCFCICS
ZED2 1 2 07/12/99 10:05 A F2 000 ICCFCICS
031888 A BACKUP CATALOG 1 1 03/18/99 15:52 A BG 280 6250 BACKUP
066666 A XINFO 1 1 08/19/00 11:22 A F2 000 ICCFCICS
1G4001 D TEST.VLT 1 1 03/25/99 12:14 A F2 000 ICCFCICS
1G4002 C TEST.VLT 1 1 03/25/99 12:14 A F2 000 ICCFCICS
1G4003 B TEST.VLT 1 1 03/25/99 12:15 A F2 000 ICCFCICS
1G4004 A TEST.VLT 1 1 03/25/99 12:15 A F2 000 ICCFCICS
221211 A TEST1.ASSGN 1 1 03/18/99 16:16 A BG 280 6250 IDCAMS2
CA Dynam 7.1 0709YD000 23/01/07 16.13.35
== SORTED BY VOLSER/FILESEQ -- ALL TAPES (DEFAULT) == SELECT: ALLTA
VOLSER VLT ----------------DATA-SET-NAME--------------- VOL FIL OW SY US ------------CREATION-INFORMATION------------ TAPE ERRS

ID ID ID DATE TIME CPU PT CUU MODE LEN JOB-NAME OUT IN
RAPS01 A RAPS.ARCHIVE.OUT 1 1 03/30/99 16:42 A BG 181 6250 ARCHIVE

RAPS02 A RAPS.ARCHIVE.OUT 1 1 03/30/99 16:49 A F4 181 6250 ARCHIVE
TONY01 A LOCK.TEST 1 1 05/10/99 16:50 A BG 180 6250 TONY
0TR987 A RFILE 1 1 12/21/00 12:03 A F2 000 ICCFCICS
00000D A GODRI01.TEST 1 1 09/09/99 10:59 A BG 181 6250 FCOPY1
005409 A HR.RESTORES 1 1 06/07/99 12:25 A F2 000 ICCFCICS
005555 A ZED1 1 1 07/12/99 10:03 A F2 000 ICCFCICS
ZED2 1 2 07/12/99 10:05 A F2 000 ICCFCICS
030988 DYNUTIL.DUMP 1 0 ****** 6250 1
030988 SCRATCHED ON 03/10/99
031888 A BACKUP CATALOG 1 1 03/18/99 15:52 A BG 280 6250 BACKUP
032188 OUTPUTS 1 0 ****** 6250
032188 SCRATCHED ON 04/14/99
1G4001 D TEST.VLT 1 1 03/25/99 12:14 A F2 000 ICCFCICS
1G4002 C TEST.VLT 1 1 03/25/99 12:14 A F2 000 ICCFCICS
1G4003 B TEST.VLT 1 1 03/25/99 12:15 A F2 000 ICCFCICS
1G4004 A TEST.VLT 1 1 03/25/99 12:15 A F2 000 ICCFCICS
191919 OUTPUTS 1 0 ****** 6250
191919 SCRATCHED ON 04/14/99
221211 A TEST1.ASSGN 1 1 03/18/99 16:16 A BG 280 6250 IDCAMS2
888889 OUTPUTS 1 0 ****** 6250
888889 SCRATCHED ON 04/14/99
A–28 User Guide

CA Dynam 7.1 0709YD000 23/01/07 16.20.49
== SORTED BY VOLSER/FILESEQ -- SCRATCH TAPES == SELECT: SCRA
TAPE ERRS
VOLSER OWNER -------------LAST DATA SET NAME------------- SCRATCHED LENGTH MODE OUT IN REASON FOR SCRATCH REMARKS
0030988 DYNUTIL.DUMP 6250 1 DATASET DELETED

032188 OUTPUTS 6250 DATASET DELETED
VTOCS
CA V O L U M E T A B L E O F C O N T E N T S VTOCS PAGE 1
CA Dynam 7.1 0709YD000 22/01/07 12.19.11
== SORTED ON CREATION DATE/FILE-ID/EXTENT SEQ NO. == SELECT: CRE
FILE IDENTIFICATION FILE LOW HIGH -REL TRK/BLK- DEVICE VOL -EXTENT- CREATE EXPIRE
-------------------------------------------- TYPE EXTENT EXTENT START NUMBER VOLSER TYPE SEQ TYPE SQ -------- -------- STAT
--- VOLUME TABLE OF CONTENTS --- VTOC 0-00 0-00 0 1 P33501 3350 1 PRIM 0
WARNING--YOU HAVE EXCEEDED MINI-DISK SIZE DAM 2-00 554-29 60 16590 P33501 3350 1 PRIM 0 11/18/99 --PERM--
DDSIXXXX.TEST.SORTIN.FILE SAM 1-20 1-27 50 8 P33502 3350 1 PRIM 0 12/21/99 --PERM--
TEST.FILE.P3350N.2VOLS SAM 0-01 0-01 1 1 P33501 3350 1 PRIM 0 + 12/21/99 -RETAIN-
SAM 0-02 0-02 2 1 P33502 3350 2 PRIM 1 12/21/99 -RETAIN-
TEST.FILE.P3350T.POOL SAM 0-08 0-08 8 1 P33501 3350 1 PRIM 0 12/21/99 12/28/99
TEST.FILE.P33501.PERM SAM 0-05 0-05 5 1 P33501 3350 1 PRIM 0 12/21/99 --PERM--
TEST.FILE.P33501.RETAIN SAM 0-02 0-02 2 1 P33501 3350 1 PRIM 0 12/21/99 -RETAIN-
SAM 0-03 0-03 3 1 P33501 3350 1 PRIM 1 12/21/99 -RETAIN-
SAM 0-04 0-04 4 1 P33501 3350 1 PRIM 2 12/21/99 -RETAIN-
TEST.GDG.P33NNN.GENERIC G#01 SAM 0-06 0-06 6 1 P33501 3350 1 PRIM 0 12/21/99 --PERM--
TEST.GDG.P3350B.POOL.MWF G#01 SAM 1-00 1-00 30 1 P33501 3350 1 PRIM 0 12/21/99 --PERM--

CA Dynam 7.1 0709YD000 22/01/07 12.19.11
== SORTED ON EXPIRATION DATE/FILE -ID/EXTENT SEQ NO. == SELECT: EXP

SAM 0-02 0-02 2 1 P33502 3350 2 PRIM 1 12/21/99 -RETAIN-
SAM 0-03 0-03 3 1 P33501 3350 1 PRIM 1 12/21/99 -RETAIN-
SAM 0-04 0-04 4 1 P33501 3350 1 PRIM 2 12/21/99 -RETAIN-
CA Dynam 7.1 0709YD000 22/12/07 12.19.11
== SORTED ON FILE-ID/EXTENT SEQ NO. (DEFAULT) == SELECT: FID
SAM 0-02 0-02 2 1 P33502 3350 2 PRIM 1 12/21/99 -RETAIN-
SAM 0-03 0-03 3 1 P33501 3350 1 PRIM 1 12/21/99 -RETAIN-
SAM 0-04 0-04 4 1 P33501 3350 1 PRIM 2 12/21/99 -RETAIN-
A–30 User Guide

CA Dynam 7.1 0709YD000 22/01/07 12.19.11
== SORTED ON VOLID/LOCATION == SELECT: VOL
VOLUME - P33501 CUU - 0355 DEVICE - 3350
* * * - FREE SPACE - * * * 0-11 0-29 11 19
* * * - FREE SPACE - * * * 1-02 1-29 32 28
P33501

Appendix B: Audit Trail Report Examples
Audit Trail Reports

The CA Dynam Audit Trail report generator lets you create any report using
the Audit records. Several predefined reports are also provided.
// JOB AUDTUTIL RUN DYNAMT AUDTUTIL REPORTS

// EXTENT SYS001...
// ASSGN SYS001,150
PROGRAM DYNAM/T
REPORT SYSTEM DATASET DEVICES CREATION MAINT
INPUT DATASET
GENERATE
/*
/&
AUDIT TRAIL UTILITY PROGRAM PAGE 1
CA CA Dynam 7.1 0709YD000 23 JAN 2007 18.19.03 AUDIT TRAIL UTILITY PROGRAM PAGE 1
PROGRAM DYNAM/T
REPORT SYSTEM DATASET DEVICES CREATION MAINT
INPUT DATASET
GENERATE
AUDIT TRAIL UTILITY PROGRAM -- PAGE 2 (SYSTEM ACTIVITY)
CA AUDIT TRAIL UTILITY PROGRAM PAGE 2

CA Dynam 7.1 0709YD000 CA Dynam/T SYSTEM ACTIVITY REPORT 23 JAN 2007 18.19.03
FUNCTION VOLUME VOL.

DATE TIME ID JOB NAME CODE FILENAME I/O -------- D A T A S E T N A M E -------- SERIAL SEQ. COMMENTS ----
01/23/86 18.16.57 BG GK53BKUP OPEN IJSYSBK OUT DYN53.BACKUP.RCVR 000910 1

01/23/86 18.17.16 BG GK53BKUP CLOSE IJSYSBK OUT DYN53.BACKUP.RCVR 000910 1
Appendix B: Audit Trail Report Examples B–1

Audit Trail Reports
AUDIT TRAIL UTILITY PROGRAM -- PAGE 3 (DATASET ACTIVITY)

CA Dynam 7.1 0709YD000 CA Dynam/T TAPE DATASET ACTIVITY REPORT 23 JAN 2007 18.19.03
FUNCTION VERS VOLUME VOL.

DATE TIME ID JOB NAME CODE I/O FILENAME -------- D A T A S E T N A M E -------- NUMB SERIAL SEQ. -COMMENTS --
01/23/86 18.16 BG GK53BKUP OPEN OUT IJSYSBK DYN53.BACKUP.RCVR 000910 1

01/23/86 18.17 BG GK53BKUP CLOSE OUT IJSYSBK DYN53.BACKUP.RCVR 000910 1
AUDIT TRAIL UTILITY PROGRAM -- PAGE 5 (DEVICES ACTIVITY)

CA Dynam 7.1 0709YD000 CA Dynam/T TAPE DEVICES ACTIVITY REPORT 23 JAN 2007 18.19.03
DEVICE PRGRM FUNCTION VOLUME

DATE TIME UNIT TYPE MODE ID JOB NAME NAME I/O CODE SERIAL FILENAME -------- D A T A S E T N A M E ----
01/23/86 18.16 0181 3420 BG GK53BKUP DYNCAT OUT OPEN 000910 IJSYSBK DYN53.BACKUP.RCVR
01/23/86 18.17 0181 3420 BG GK53BKUP DYNCAT OUT CLOSE 000910 IJSYSBK DYN53.BACKUP.RCVR
AUDIT TRAIL UTILITY PROGRAM -- PAGE 4 (TAPE CREATION)

CA Dynam 7.1 0709YD000 CA Dynam/T TAPE CREATION REPORT 23 JAN 2007 18.19.20
FUNCTION VOLUME VOL.

DATE TIME ID JOB NAME CODE I/O FILENAME -------- D A T A S E T N A M E -------- SERIAL SEQ. ---- COMMENTS --
01/23/86 18.16 BG GK53BKUP OPEN OUT IJSYSBK DYN53.BACKUP.RCVR 000910 1

01/23/86 18.17 BG GK53BKUP CLOSE OUT IJSYSBK DYN53.BACKUP.RCVR 000910 1
AUDIT TRAIL UTILITY PROGRAM -- PAGE 5 (CATALOG MAINTENANCE)

CA Dynam 7.1 0709YD000 CA Dynam/T MANUAL CATALOG MAINTENANCE REPORT 23 JAN 2007 18.19.20
VERS VOLUME VOL.

DATE TIME ID JOB NAME -------- D A T A S E T N A M E -------- NUMB SERIAL SEQ. --------- UTILITY COMMAND LINE --
01/23/86 18.05 BG GK53DEF STATUS

01/23/86 18.16 BG GK53BKUP BACKUP RECOVER
01/23/86 18.17 BG GK53BKUP SCRATCH
B–2 User Guide

Glossary
abend CA Dynam/FI
Abnormal ending. An early termination of a CA file independence software package.
program due to an error. Provides flexibility and independence for device
types and files.
access method
A technique for moving data between main CA Dynam/T
storage and input/output devices. CA tape management software package.
Manages tape processing, security and control.
ACB
Access method control block which contains CA SORT
control information necessary for linking to CA SORT/MERGE utility system. Can arrange
VSAM. files into a single data stream with logical
record selection and manipulation.
AMF data set
Automatic multifile data set. Automatic CA Earl
generation of multifile data set names. CA report writing facility for creating standard
and user-customized reports.
ASA
Automatic secondary allocation for disk files. CA SRAM
Provides control of secondary allocation CA sort facility capable of executing from
automatically from JCL or the Catalog. within a program.
ASI PROC CI
Automated system initialization procedure. Control interval. Unit of data (group of records)
Operating system startup commands read from transmitted to or from storage.
a procedure library.
CKD
AVR Count-key-data. Disk storage device that
Automatic volume recognition. Provides for stores data in three fields:
automatic assignment of a mounted disk by count field (address - by cylinder, head and
searching for the volume serial number of the record number - and length of record)
EXTENT statement. The ASSGN statement is key field (for searching), and
not needed and the user does not have to actual data of record
know the physical device address.
cuu
CA Dynam Catalog Channel and unit address. Tape or disk device
Disk file which stores file attributes and address.
information necessary for processing those
files. DA
Direct access. A method of locating a record
CA Dynam/D directly rather than by searching through all
CA disk management software package. previous records.
Provides catalog, disk pool and enhanced VTOC
management.
Glossary–1
DASD FBA
Direct access storage device. Any storage Fixed block architecture. A DASD architecture
device that can immediately read or write where data is stored in fixed-size blocks that
anywhere on its recording surface. are addressed by a block number relative to
the start of the file.
DSCB
Data set control block. A record in the DASD GETVIS
VTOC containing control and descriptive A dynamically managed storage area.
information about a data set.
home address
DTF Address of track relative to start of volume.
Define the file. A control block used for
sequential or unit record access methods. For IOCS
example, DTFMT is sequential tape. Input/output control system. Used to transfer
data between main storage and auxiliary
DVCDN status storage devices.
Device down status. Device is not available.
IPL
DVCUP status Initial program load. Starting up of a computer
Device up status. Device is available. system.
DYNACC keyword
CA general interface to the CA Dynam Catalog. A predefined word that identifies an operand
It accepts data requests, searches the Catalog and is part of that operand. For example, the
and returns data suitably formatted for keyword in BLKSZ=1210 is BLKSZ. The
building reports. keyword is the whole operand in the CA
Dynam/FI option RUN.
DYNCAT
A CA utility program used to create, maintain LIOCS
and report on the CA Dynam Catalog. Logical input/output control system. Group of
macro instructions which create, retrieve and
DYNDART change data files.
A CA utility program used to generate reports
for CA Dynam Catalog. LTA
Logical transient area. Temporary storage area
DYNPRINT used by system routines.
A CA common reporting component used by
the CA Dynam VSE family. Through CA Earl, it LUB
can generate both standard and user- Logical unit block. Programmer logical unit or
customized reports on CA Dynam tape, disk, SYSnumber. Used instead of actual device
and Catalog activity. address.
EXTENT statement operand

JCL statement which defines each area of a A variable that specifies a value or an
DASD file. operation to be performed. Used
interchangeably with 'parameter.'
Glossary–2 User Guide

work file (work data set)
parameter SD file
A variable that specifies a value or an Sequential disk file. File that is located by first
operation to be performed. Used reading previous files.
interchangeably with 'operand.'
SVA
PIOCS Shared virtual area. Storage area for system
Physical input/output control system. Controls support and use.
the actual transfer of records between main
storage and auxiliary storage devices. track mapping
Combining all key and data records from
PUB original CKD track into one control interval.
Physical unit block. Table which describes the
input/output devices defined to the system. TDYNSYNC
A CA utility program that provides tape volume
record mapping synchronization between two catalogs that
Creating separate control intervals for each share tape volume status information.
data record on original CKD track.
truncation
recovery Release of unused disk space allocated for a
Retrieving, securing and protecting data by file.
restoring a backup tape and then updating it.
unit record simulation
restore utility Specifying a unit record device (card reader,
A program used to secure and protect data by printer, card punch) to be simulated as a tape,
retrieving, reading and loading the most recent sequential disk or VSAM file (as used in CA
backup tape. Dynam/FI).
RPS UPSI statement

Rotational position sensing. Method of locating User program switch indicator statement to set
data on disk devices. program switches that can be tested.
RPL VCKD
Request parameter list. A control block with Virtual count-key-data. (See CKD.)
information needed to process an I/O request.
work file (work data set)
sequential access File (data set) used temporarily when extra or
Locating a record by going through all previous intermediate storage is needed for the
records one after the other, starting at record processing of a job.
1.
scratch
Erase or overwrite data that is no longer
needed or that has expired.
scratch tape
Tape that is available for reuse.
Glossary–3
Index
Active tapes, 3-42
$ ACTVFILE report, 9-16
ADD command (DYNCAT), 8-12

$JOBEXIT parameter adding
CA Dynam/D, 4-48 VTAPE versions to the catalog, 3-56, 8-12,
CA Dynam/FI, 6-26 8-16
$TEST jobname, 2-53 files to the Catalog, 2-37, 4-29
generation data sets, 4-20
multifile-volume data sets, 2-64
1 Adding versions to data sets, 8-12
Allocating
1400 Emulator tapes, 2-7 disk space
FBA disk files, 6-46, 6-51
minimum percentage, 4-35
LUBs, 2-14
3
scratch tapes, 2-2, 2-53
ALTER
3494 tape libraries, 3-52
command (DYNUTIL), 5-13
response to MOUNT message, 2-15, 2-21
A ALTER command (DYNCAT), 8-17
Altering
data set
Absolute generation number, 4-22
ownership, 2-57
ACCEPT response to MOUNT message, 2-16, password, 2-57
2-21 retention characteristics, 2-48
to drop a TLBL, 2-56
Accepting control statements from SYSIPT, 3-9
Altering data set characteristics, 8-17
ACCESS command (DYNPRINT), 9-3
AMF (Automatic Multifile), 2-69
Accessing
generation data sets, 4-22 APPLY
the Catalog file, 2-7 command (TDYNSYNC), 3-19
report, 3-23
Accessing the Catalog, 9-2, 9-14
AR commands
ACTION command (DYNCAT), 8-11
answering mount messages, 2-17
Activating disk bypass status/control, 4-32
automatic cataloging, 2-60 DTPATH query/control of XSYSTEM, 2-25
AVR, 2-12 tape drive status/control, 2-24
VCKD, 6-44
ASA, 4-17
Active cataloged files, 9-16
Index–1
ASCII tape Auxiliary messages, 7-26
DTF restriction, 6-3
AVR
support, 2-73
activating, 2-12
AS-OF-DATE, 8-55 defining disk volumes, 4-32
disk files, 4-24
AS-OF-DATE retention, 2-9
finding scratch tapes during, 2-52
ASSGN function (TDYNASN), 2-7, 3-2, 3-3 functioning of, 2-29, 2-64
implementing, 2-73
Assigning
input tape selection, 2-53
logical unit, 3-3
invoking with OPEN, 3-5
mode in TLBL, 2-46
length checking during, 2-41
scratch tapes, 2-16
output tape selection, 2-17
tape files to physical devices, 2-12, 2-13
overriding, 2-84
volume serial numbers, 2-6
positioning multifile data sets, 2-14
Asterisks in AMF DSN, 2-69 purpose of, 2-12
searching in desired order, 2-84
Audit data set
tape files, 2-12
also see AUDTUTIL, 12-1
verifying tape ownership, 2-58
backup tapes, 12-4, 12-6
with
logging, 12-2
CA Dynam/D, 4-24
recovering the Catalog, 12-4
utility programs, 3-1
reporting commands, 12-11
Audit data set, purpose of, 2-1
Auditing program (AUDTUTIL), 12-1 B

AUDTUTIL utility program
Catalog recovery steps, 12-4 Backing up
commands Catalog, 2-54
maintenance, 12-5 DA files, 6-47
reporting, 12-11 BACKUP command
control statement syntax, 12-5 AUDTUTIL, 12-4, 12-6
overview, 12-1 DYNCAT, 8-41, 8-43
reporting
commands, 12-11, 12-15 BACKUP command (VCKDBKRS), 6-48
predefined reports, 12-12 Basic mode, 12-2
report fields, 12-29
user-defined reports, 12-14 BLDINDEX recovery, 4-36
Automatic BLKSIZE= parameter

cataloging, 2-60 DYNCOPY program, 13-5
multifile data sets Block size
as input, 2-71 calculating, 6-22
defining, 2-69 FI operands, 6-22
renaming, 2-72 TDYNCOPY, 3-8
reporting TAPE ERRS, 3-43
scratching names, 2-71 Blocking factor, 3-9
volume switching, 2-70 BSF response to MOUNT message, 2-16
Retry Facility, 2-29
Secondary Allocation (ASA), 4-5, 4-17
volume assignment/recognition, 4-24
Index–2 User Guide

BSR response to MOUNT message, 2-16 option considerations, 6-21
partition independence, 6-37
Buffers, increasing, 6-22
RESET statement, 1-15
SET statement, 6-26, 6-42
SYSLOG support, 6-30
C system restrictions, 6-44
TLBL options, 6-11, 6-42
CA Dynam unit record DTFs, 6-4
Audit data set, 2-1 with
Catalog file, 2-2, 4-6, 6-4, 6-20, 6-39 CA Dynam/D, 6-36
subsets CA Dynam/T, 6-36
CA Dynam/FI, 6-1 CA SORT, 6-39
CA Dynam/T, 2-1 CA Dynam/T
common features, 1-2 and AVR, 2-12
CA Dynam/D catalog synchronization, 3-16
automatic CHKPT/RSTRT support program, 3-14
secondary allocation, 4-5, 4-17 CPU independence, 2-50
volume assignment/recognition, 4-15, extended operational facilities, 2-48
4-24, 4-32 implementation, 2-6
basic components of, 4-2 mount messages, 2-15, 2-16, 2-17, 2-18,
checkpointed files, 4-52 2-19, 2-20, 2-21, 2-22, 2-23
controlling option record, 2-60
allocation and access, 4-30 partition independence, 2-49
generation data sets, 4-20 restrictions, 2-8, 2-73
converting to trigger value, 5-3 retention characteristics, 2-8
CPU independence, 4-38 SET command, 2-82
defining disk volumes for AVR, 4-32 system messages, file-dependent, 2-61
disk pool volumes, 4-30 tape
DLBL options, 4-14 assignment, 3-1
partition independence, 4-38 copy utility, 3-8
restarting programs, 4-52 TLBL options, 2-30
restrictions, 4-5 with
SET command, 4-48 CA Dynam/FI, 6-36
sort interfaces, 4-46 CA SORT, 2-73, 3-1, 3-4
system messages, file-dependent, 4-45 CA 1, 3-16
with CA Dynam/FI, 6-36 LIBR, 2-75
work data sets, 2-48
CA Dynam/FI
accessing generation data sets, 6-53 CA EARL
ASSGN statement, 6-28 and DYNREAD communication, 9-14
calculating compiler, 9-8
block size, 6-22 generating reports, 9-1
logical record length, 6-22 source programs, 9-8
CPU independence, 6-37 CA EPAT, 8-76
DLBL options, 6-15
DTF types supported, 6-2 CA SORT interface
file information override, 6-4 logical unit checking, 2-73
introduction, 6-1 with
limiting processing, 6-42 CA Dynam/D, 4-42, 4-46
CA Dynam/FI, 6-53
Index–3
CA Dynam/T, 2-73, 3-1, 3-2, 3-4 DYNAM DISplay VOLume, 7-46
CADynam/D, 4-18 DYNAM MENU, 7-9
DYNAM SELect DATaset, 7-11
CA SRAM with CA Dynam/FI, 6-8, 6-14, 6-19
DYNAM SELect TAPE, 7-40
CA 1 interface summary, 7-4
catalog synchronization, 3-16 local commands, 7-6
DYNCOMM task, 3-22 overview, 7-1, 7-4
message paths, 2-25, 3-16 panel summary, 7-4
PATH command, 2-25 PF keys, 7-1
Primary Selection Panel (CUI-MENU), 7-8
CAIAUDIT
Tape
data sets
Directory panel (CAYD-3100), 7-44
all products directory, 11-4
Selection panel (CAYD-3000), 7-40
displaying a product-specific directory,
Version Detail panel (CAYD-2190),
11-2
7-37
displaying records, 11-4
Version List panel (CAYD-2160), 7-31
selecting records, 11-2
Volume Detail panel (CAYD-3110),
viewing records, 11-4
7-47
in command mode, 11-14
in prompt mode, 11-1 CAIMACC queue file, 3-17
CAICATL Catalog file, 2-2 CAINTDK utility program, 5-1
CAICUI (common user interface) CAISPI, CAICUI panels Primary Selection Panel
accessing, 7-7 (CUI-MENU), 7-8
Auxiliary Record panel (CAYD-2140), 7-27
Catalog
Data Set
Access Facility, 9-2, 9-14
Directory panel (CAYD-2100), 7-13
accessing, 2-7, 6-42
Disk Option panel (CAYD-2120), 7-22
adding
on Volume panel (CAYD-3120), 7-50
disk data sets, 4-29
Option panel (CAYD-2130), 7-24
tape data sets, 2-37
Selection panel (CAYD-2000), 7-11
VTAPE versions, 3-56
Disk
backing up, 2-54
Version Detail panel (CAYD-2180),
destroying, 8-69
7-35
management
Version List panel (CAYD-2150), 7-29
disk files, 4-7
FI Version List panel (CAYD-2170), 7-33
tape files, 2-2, 2-60
File Management Panel (CAYD-0000), 7-9
global commands
overriding cataloged mode, 2-46
DYNAM DISplay AUXiliary, 7-26
ownership, 2-56
DYNAM DISplay DISKlist, 7-29
protecting, 2-56, 8-67
DYNAM DISplay DISKVersion, 7-34
purpose of, 2-2
DYNAM DISplay DSNDETail, 7-15
recovery, 12-2, 12-4
DYNAM DISplay DSNDIRectory, 7-13
reporting, customized, DYNPRINT program,
DYNAM DISplay DSNDOPTions, 7-22
9-16
DYNAM DISplay DSNTOPTions, 7-24
reporting, standard
DYNAM DISplay DSNVOLume, 7-50
on active files, 9-16
DYNAM DISplay FIlist, 7-32
on file definitions, 9-19
DYNAM DISplay TAPEDirectory, 7-44
on file usage, 9-21
DYNAM DISplay TAPElist, 7-31
synchronization, 3-16
DYNAM DISplay TAPEVersion, 7-37
updating, 2-8, 2-53, 3-6, 3-14

CATALOG RECOVERY command (AUDTUTIL), Console
12-4, 12-7 commands, 2-17, 2-24, 2-25, 4-32
output, 6-29
CATNAME command (TDYNSYNC), 3-20
Control statements for
Changing data set characteristics, 8-17
ACTVFILE, 9-17
CHARONLY parameter, DYNCOPY program, AUDTUTIL, 12-5
13-4 DYNCAT, 8-2
DYNPRINT, 9-2
Checkpointing, 3-14, 4-52, 5-8, 6-41
FILEDEFS, 9-19
CHKPT/RSTRT Support Program, 3-14 FREQUSE, 9-22
TDYNASN, 3-2
CICS preprocessor
TDYNCOPY, 3-10
command level, 6-6
TDYNLBL, 3-13
macro level, 6-7
TDYNPULL, 3-33
CISIZE= parameter TDYNRST, 3-15
DYNCOPY program, 13-5 TDYNSYNC, 3-18
Clear Disk Utility (VCKDCLDK), 6-50 Control Statements for

CAINTDK, 5-1
CLOSE command
TDYNLIST, 3-31
DYNUTIL, 5-16
TDYNUTL, 3-38
TDYNASN, 3-6
Control statements, DYNCAT command, 8-5
Closing
output data sets, 2-53 CONVERSION command (TDYNVLT), 3-49
work data sets, 2-49
CONVERT command (DYNCONV), 5-3
Coding TLBL/DLBL statements, 6-21
Converting EXTENT Statements, 5-3
COMAVR processing, 4-32
COPY
COMLUB processing, 4-28 parameter,
DYNCOPYprogram, 13-2
Command mode, using CAIAUDIT, 11-14
Copybooks for DYNPRINT, 9-8, 9-15
Commands
DISPLAY AUDIT, 11-15 CP commands, 4-48, 6-26
global display
CPU
MENU, 7-7
IDs, 2-50
summary, 7-4
independence
local, summary, 7-6
CA Dynam/D, 4-38
SELECT AUDITRECORDS, 11-14
CA Dynam/FI, 6-37
Comments for data sets, 8-14, 8-21, 8-29, CA Dynam/T, 2-50
8-55
CPUID option record, 2-50
Common subset features, 1-2
Cross-volume allocation, 4-33
Common User Interface (CAICUI), 7-1
Current generation number, 4-21
COMPILE command (DYNPRINT), 9-3
Customizing reports
Compiler work files, 4-38 AUDTUTIL, 12-1
DYNPRINT, 9-8
COMPOOL processing, 4-30
cuu response to MOUNT message, 2-15
Index–5
D protection, 2-7
retention, 2-8, 8-44
scratching versions, 2-10
DA files selecting a CAUDPCn record, 11-2
assigning logical units, 4-9 selection, 7-11
deleting, 4-42 specifying for input processing of VTAPE
Data sets files, 3-55
accessing tape, 7-24
disk pools, 4-30 temporary, 2-51, 2-61, 4-8
generation, 4-22 versions, 7-29, 7-31, 7-32, 7-34, 7-37
tape, 2-57 viewing a CAUDPCn record, 11-4
active versions, 7-29, 7-31, 7-32, 7-34, work, 2-49
7-37 Data Sets
altering characteristics, 8-17 partition independent, 2-49
automatic multifile
defining, 2-69, 2-70 DATASET command (AUDTUTIL), 12-10
renaming, 2-72 Date
report fields and comments, 3-43 processing, 4-43
scratching, 2-71 retention, 2-9, 2-10
volume switching, 2-70
cataloging Default allocation, 4-10
tape, 2-55, 2-60 DEFINE command (DYNCAT), 8-44
control, 2-7
CPU-independent, 2-50 Defining
creating, 2-2 automatic multifile data sets, 2-69, 2-70
defining, 7-15 Catalog ownership, 2-56
defining multifile-volume, 2-62, 2-65 data sets, 7-15
directory, 7-13 disk pool volumes, 4-30, 4-32
Disk Option Panel (CAYD-2120), 7-22 DLBL options, 4-14, 6-10, 6-15
FI, 7-22, 7-24 dynamic LUB allocation, 4-27
forcing input, 2-55 FBA disk files, 6-47
generation generation data sets, 4-20
deleting, 4-22 independent files, 2-49, 4-38
retention, 2-9 LUB ranges, 4-27
list, 2-54 message paths, 3-16
MACC queue files, 3-16 multifile-volume data sets, 2-62, 2-65
maintenance, 7-10 partition-independent files, 4-38
multiple disk versions, 4-20 SYSPCH tape, 3-6
naming tape
file, 2-2 data sets, 2-3
in the Catalog, 6-37 drive pools, 2-13
multifile-volumes, 2-63 tape volumes, 7-46
tape, 2-2 TLBL options, 2-30, 6-10
temporary, 4-8 DELETE command (DYNCAT), 8-63
naming via DYNCAT, 8-54, 8-56, 8-57
output, 2-53 DELETE command (DYNUTIL), 5-17
overriding mode of, 2-46 Deleting
ownership of, 2-57 DA files, 4-42
positioning multifile-volume tapes, 2-14 expired files, 4-13

generation data sets, 4-22 DISPLAY command (DYNUTIL), 5-19
option code D, 4-14
Displaying
SORTWK files, 4-19
CAIAUDIT records, 11-4
DEQUEUE command (DYNCAT), 8-66 tape volumes, 7-50
Destroying the Catalog, 8-69 DLBL

coding, 6-21
DETACH command (TDYNASN), 3-7
options, 4-14, 4-16, 6-10, 6-15
Detaching SYSPCH tape, 3-7 order of operands, 6-10
statement, 6-15, 6-21
Device switching
SYS number on, 4-25
example, 2-23
with EXTENT, 4-8
operation, 6-36
requirements, 6-34 DN option (TDYNLIST), 3-32
DIGITS option (TDYNLBL), 3-13 DSN parameter

VTAPE command, 3-55
Direct Access File Independence (VCKD), 6-43
DTF types
Disk
supported by CA Dynam/FI, 6-2
File Analyzer (VCKDANAL), 6-51
files DTLOCK option record
defining volumes for AVR, 4-32 usage, 2-84
deleting, 4-14, 4-42 with AVR, 2-13
displaying, 7-22
DTPATH option record and DT PATH command,
file type, 4-9
2-25
multiple-version, 4-20
versions, 7-29, 7-34 DTPOOL option record
maintenance utilities usage, 2-84
CAINTDK, 5-1 with AVR, 2-13
DYNCONV, 5-3
Dummy
DYNOPEN, 5-8
ASSGN, 3-2
DYNUTIL, 5-11
tape drives, 3-2
pool volumes, 4-30
pre-open file processing, 5-8 DUMP command (DYNUTIL), 5-21
processing
DUMP parameter, DYNCOPY program, 13-2
status, 4-32
reporting DVCUP, 2-13
SPACEUSE, 5-43
DYNACC interface
VTOCS, 5-47
calling parameter list, 10-3
reporting, DYNVTOC, 9-24
copybooks, 10-4
space
DYNINFO area, 10-2
across generic volumes, 4-33
invoking, 10-4
minimum percentage, 4-35
linkage conventions, 10-3
recovery from insufficient allocation,
parameter list content, 10-23
4-36
request fields, 10-6
releasing unused space, 4-40
testing, 10-18
secondary allocation, 4-5
user exits, 10-17
DISK response to MOUNT message, 2-17, 2-23
DYNAEXIT user exit, 10-17
DISPLAY AUDIT command, 11-15
DYNAM/D option record, 4-10
Index–7
DYNAM/T option record parameters, 13-2
MULTCPU parameter, 2-50 requirements, 13-1
processing
DYNEEXIT user exit, 10-18
common LOCK name, 2-84
FLT option, 2-73 DYNINFO
VOLSER= option, 2-82 area (DYNACC), 10-2
record layout, 10-6
Dynamic LUB allocation, 2-14, 4-27
request fields, 10-12
DYNATEST program return codes, 10-15
functions, 10-18
DYNOPEN utility program
parameters, 10-19
DITTO, 5-8
syntax, 10-19
IDCAMS, 5-8
DYNCAT command (CAICUI), 7-6 pre-open processing, 5-8
restarting checkpointed files, 4-52
DYNCAT utility program, 3-17, 7-6
commands DYNPRINT standard reports
ACTION, 8-11 SPACEUSE, 5-43
ADD, 8-12 TAPES, 3-28
ALTER, 8-17 VTOCS, 5-47
BACKUP, 8-41
DYNPRINT utility program
DEFINE, 8-44
commands, 9-2
DELETE, 8-63
control statements, 9-2
DEQUEUE, 8-66
customized reports, 9-8
END, 8-67
requirements for, 9-3, 9-10
INITIAL, 8-67
standard reports
INT and INTR, 8-69
ACTVFILE, 9-16
LISTCAT, 8-73
FILEDEFS, 9-19
MACC, 8-75
FREQUSE, 9-21
MCAT, 8-76
overview, 9-6
OWN, 8-77
RENAME, 8-78 DYNREAD interface, 9-2, 9-14
RESTORE, 8-80
DYNUTIL utility program
RESTORE REORG, 8-41
commands
SCRATCH, 8-83
ALTER, 5-13
SCRPOOL, 8-86
CLOSE, 5-16
STATUS, 8-90
DELETE, 5-17
VAULT, 8-91
DISPLAY, 5-19
VTOC, 8-93
DUMP, 5-21
control statement format, 8-2
LISTTAPE, 5-24
functions, 8-3
OPEN, 5-25
processing options, 8-11
REORG, 5-26
summary of control statements, 8-5, 8-6,
RESTORE, 5-37
8-7, 8-8, 8-10, 8-11
summary, 5-12
DYNCOMM task, 3-22 TAPE, 5-40
TRACE, 5-42
DYNCONV utility program, 5-3
DYNVTOC utility program
DYNCOPY, File Utility program
report headings, 9-26
examples, 13-6
UPSI settings, 9-24
general, 13-1

E F
Early Drive Release facility, 2-14 FakeTape, 3-57
EJECT command (TDYNVLT), 3-49, 3-54 FBA disk files

allocating, 6-46, 6-51
END command (DYNCAT), 8-67
defining, 6-47
END option (TDYNLBL), 3-13 mapping, 6-44, 6-45, 6-46, 6-48
Enqueue, 4-15 FEOF= parameter, DYNCOPY statement, 13-3
EOB response to MOUNT message, 2-15 FIELDS command (AUDTUTIL), 12-15
EOJ= parameter, DYNCOPY statement, 13-3 File

IDs
Equal filenames
CA Dynam/D, 4-14
disk file IDs, 4-45
CA Dynam/T, 2-37
tape, 2-38, 2-67
independence, 2-49, 4-38
ERRORS option (TDYNCLEN), 3-30 names
derived, 6-4
Establishing
in TLBL, 2-6
data set ownership, 2-57
override hierarchy for FI, 6-4
dummy tape drive in PUB table, 3-2
stacking, tape cartridges, 2-47
retention characteristics, 2-8
type, 4-9
tape drive pooling, 2-84
vault locations, 3-46 File management
work files in CA Dynam/T, 2-48 activity, 12-2
panel, 7-9
Event notification selection panels, 11-2
system, 7-7
Exception list, 2-55
File Utility program, DYNCOPY, 13-1
EXCEPTS command (TDYNUTL), 3-40
FILEDEFS report, 9-19
Expiration date override, 4-8
File-dependent system messages
Expired disk files CA Dynam/D, 4-45
deleting, 4-13 CA Dynam/T, 2-61
processing, 4-43
FILEIN= parameter, DYNCOPY program, 13-6
Extended mode, 12-2
FILEOUT= parameter, DYNCOPY program, 13-6
Extended Operator Communication facility, 1-4
FILES=parameter,
EXTENT statement DYNCOPY program, 13-5
blank, 4-8
Fixed length record files, 3-8
converting, 5-3
omitting, 4-9 FLT, 2-72
External Tape System, 3-16 Forced standard labels, 2-72, 2-79
EXTRACT FORMAT command (TDYNUTL), 3-41

command (TDYNSYNC), 3-20
FORTRAN, 2-74, 4-5
report, 3-23, 3-24
Fragment, 4-15
FREE response to MOUNT message, 2-15
Index–9
Frequency of file usage, 9-19 I
FREQUSE report, 9-21
FSF response to MOUNT message, 2-16 IBM

Sort/Merge, 4-46
FSR response to MOUNT message, 2-16 SORT/MERGE, 6-39
IBM 3494 Tape Library, 3-52

G IBM Virtual Tape Support
adding versions to the catalog, 3-56, 8-12,
8-16
G#nn, 4-16
CA Dynam/T enhanced, 3-57
GENERATE command, 12-17 command format, 3-55
CUU assignment, 3-56
Generating
DSN= parameter, 3-55
AMF file numbers, 2-69
overview, 3-55
DSNs for multifile-volume data sets, 2-69
IDCAMS
Generation
DYNOPEN utility program, 5-8
data sets
support, 4-8
accessing, 4-22, 5-22, 5-38, 6-53
controlling, 4-20 IGNOREd files, 6-40
deleting, 4-22
INCREMENT option (TDYNLBL), 3-13
migrating, 5-26
option, 2-32, 4-16, 4-22 Independent files, defining
renaming, 5-27, 5-28 disk files, 4-38
restoring, 5-26 tape files, 2-49
number
Indexed VTOC processing, 4-13
absolute, 4-22
current, 2-32, 4-16, 4-21 Indexed VTOC support, 8-93
identifying, 4-21
INITIAL command (DYNCAT), 8-67
relative, 2-32, 4-16, 4-22
retention, 2-8 Initializing
message paths, 3-17
Generic
Multi
cross-volume allocation, 4-33
,ACCESS queue files, 3-17
volume serial numbers, 4-33
scratch tapes, 2-3
GETVIS Support volumes, 2-40
for DYNCOPY, 13-1
Initializing VTOC indexes, 8-93
G-nn, 4-16
INNAME= parameter, DYNCOPY program, 13-6
INPUT command (AUDTUTIL), 12-17

H Input tapes, selecting, 2-2
INPUT=parameter,
HDR1 information, 2-38 DYNCOPY program, 13-5
HDRINFO= parameter, DYNCOPY program, Inputting automatic multifile data sets, 2-71
13-6
Holding assignments, 2-38, 2-64

Installation options LABELMSG parameter
COMAVR option record, 4-32 CA Dynam/D, 4-48
COMLUB option record, 4-28 CA Dynam/T, 2-83
COMPOOL option record, 4-30
LIBR with CA Dynam/T, 2-75
CPUID option record, 2-50
DTLOCK option record, 2-13, 2-84 Limiting tape allocation, 2-58
DTPATH option record, 2-25
LIST command (TDYNUTL), 3-41
DTPOOL option record, 2-13, 2-84
DYNAM/D option record, 4-10 LISTCAT command (DYNCAT), 8-73
DYNAM/T option record, 2-50, 2-73, 2-82,
Listing
2-84
active data sets, 2-55
XSYSTEM option record, 3-16
scratch tapes, 2-16
Insufficient space
LISTTAPE command (DYNUTIL), 5-24
operator actions, 4-36
recovery allocation, 4-36 Lock
data sets, 2-57
INT command (DYNCAT), 8-69
tape drives, 2-84
Interfaces
LOCK option record, 2-85
CA SORT, 4-46
XSYSTEM, 3-16 Logging
Audit data set, 12-2
INTR command (DYNCAT), 8-69
catalog recovery information, 12-2
INVENTORY command (TDYNVLT), 3-49 on, 7-7
ISAM files Logical
deleting, 4-42 record
extending, 4-16 length calculation, 6-22
size, 3-9
unit assignments
J DA files, 4-9
disk, 4-24, 4-25
tape, 2-5, 2-12, 3-2
JCL
modifying, 2-5 LRECL= parameter
testing, 2-53 DYNCOPY program, 13-5
Job LUB
control, conversion, 5-3 allocation
exit facility (FI), 6-11, 6-42 defining, 4-27
dynamic, 2-14
prohibiting, 4-18
recommended, 4-9
L processing, 4-25
ranges, 4-27
Label
prefix, 3-13
processing area, 2-72
with TDYNASN, 3-7
LABEL= parameter, DYNCOPY program, 13-6
Index–11
M MOVEMENT command (TDYNVLT), 3-49, 3-51
MTC, 3-6
MACC command (DYNCAT), 8-75 Multi
MACC queue files ACCESS queue files
creating, 3-16 creating, 3-16
formatting, 3-17 formatting, 3-17
Maintaining multifile-volume data sets, 2-64 Multi-CPU environment, 2-84
Mapping FBA disk files, 6-44, 6-45, 6-46, 6-48 Multifile-volume data sets
adding versions, 2-64
MAX= parameter, DYNCOPY program, 13-4 cataloging, 2-63
Maximizing tape resources, 2-12 defining, 2-62, 2-65
generating DSNs for, 2-69
MCAT command (DYNCAT), 8-76 identical dtfnames, 2-67
MENU command (CAICUI), 7-8 input and output, 2-66
maintaining, 2-64
Messages naming, 2-63
answering, 2-17, 2-18, 2-19, 2-20, 2-21, processing, 2-65
2-22, 2-23, 2-29 reporting TAPE ERRS, 3-43
auxiliary, 7-26 restrictions, 2-64
for data sets, 8-20, 8-47 retention characteristics, 2-63
operator recovery actions, 4-36 STACK option, 2-67
paths, initializing, 3-17 support for, 2-62
responses, mounting tapes, 2-15, 2-16 tape positioning, 2-64
support, 2-61, 4-45 unchaining tapes, 2-67
Migrating generation data sets, 5-26 Multiple
Mode catalogs, 2-58
assigning in TLBL, 2-46 installations, 2-58
control, 2-42, 2-44
example, 2-59
overriding, 2-46 N
setting, 2-42, 2-44
uncontrolled tape files, 2-46
Naming
unspecified, 2-46
disk data sets, 4-5, 6-37, 8-54, 8-56, 8-57
MODE multifile-volume data sets, 2-63
specifying, 2-42 sort key records, 8-61
tape data sets, 2-2, 8-54, 8-56, 8-57
Modification Aid (CAINTDK), 5-1
temporary disk data sets, 4-8
Modifying test jobs, 2-53
JCL, 2-5
NEWTAP response to MOUNT message, 2-16
retention characteristics, 2-10
NOLABEL option, 2-76
MOUNT message
examples, 2-17, 2-18, 2-19, 2-20, 2-21, 2- Non-standard files, tape cartridges, 2-46
22, 2-23
NOPLINE parameter, DYNCOPY program, 13-6
responses, 2-15, 2-16
NOREW parameter
Mounting tapes, 2-15
DYNCOPY program, 13-6

NOREWIN parameter Macros COMPOOL, 4-30
DYNCOPY program, 13-6 multi-CPU environment, 2-50
XSYSTEM, 3-16
NOREWOUT parameter
DYNCOPY program, 13-6 Option Record
PULLTAB, 3-36
NOSCALE parameter, DYNCOPY program, 13-6
Options
NOTE option (TDYNLIST), 3-32
all DLBL/TLBL, 1-6
NOTPMK= parameter, DYNCOPY program, 13-6 DLBL
CA Dynam/D, 4-14
CA Dynam/FI, 6-15
O TLBL
CA Dynam/FI, 6-11
CA Dynam/T, 2-30
OBLKSIZE= parameter
DYNCOPY program, 13-5 OUTNAME= parameter, DYNCOPY program,
13-6
Online panels, CAICUI, 7-8
Output
OPEN command console dialogue, 2-17
DYNOPEN, 5-8 tapes, 2-8, 2-17, 2-53
DYNUTIL, 5-25 unlabeled files, 3-9
TDYNASN, 3-5
Overriding
Open requests, 2-7, 2-12, 2-13, 2-15, 2-16 AVR, 2-84
OPENS option (TDYNCLEN), 3-30 cataloged SYS numbers, 4-25
catalog-specified mode, 2-46
Operator expiration date, 4-8
cancellation, 1-5 logical units, 6-5, 6-15
device switching requested recording density, 2-46
example, 2-23
facility, 6-34 OWN command (DYNCAT), 8-77
operation, 6-36, 6-37 Owner ID, 8-55, 8-67
recovery actions, 4-36
Ownership, tape data sets, 2-57
Option codes
defining, 4-14, 4-15, 4-16, 4-17
examples, 4-19 P
using option S, 4-48
Option record
Panels
COMLUB, 4-28
AUDIT Data Set Browse Selection (AUDT-
CPUID, 2-50
1000), 11-2
DTLOCK, 2-13, 2-84
AUDIT Data Set Detail - DYNAM/T (AUDT-
DTPATH, 2-25
1910), 11-8
DTPOOL, 2-13, 2-84
DYNAM/D, 4-10
1920), 11-9
DYNAM/T, 2-50, 2-73, 2-82, 2-84
LOCK, 2-85
1A10), 11-11
Macros COMAVR, 4-32
AUDIT Data Set Directory - All Products
(AUDT-1100), 11-4
Index–13
AUDIT Data Set Directory – CA Dynam/T PF keys, system defaults, 7-1
(AUDT-1900), 11-6
Placing partition in WAIT state, 2-52
AUDIT Data Set Directory - DYNAM/T
(AUDT-1A00), 11-9 POFFLOAD tapes, controlling, 2-80
AUDIT Data Set Directory - DYNAM/T
Pools
(AUDT-1B00), 11-12
disk, 4-30
AUDIT Dataset Detail Panel- CA Dynam/FI
tape, 2-84
(AUDT-1B10), 11-14
Auxiliary Record Panel (CAYD-2140), 7-26 POWER Offload tapes, controlling, 2-80
Data Set Detail Panel (CAYD-2110), 7-15
Predefined reports (AUDTUTIL), 12-20
Data Set Directory Panel (CAYD-2100),
7-13 PREFIX option (TDYNLBL), 3-13
Data Set Disk Option Panel (CAYD-2120),
Pre-open file processing
7-22
for CA Dynam/D, 5-8
Data Set Option Panel (CAYD-2130), 7-24
for CA Dynam/T, 2-73
Data Set Selection Panel (CAYD-2000),
7-11 Preparing to use CA Dynam/T, 2-1
Data Sets on Volume Panel (CAYD-3120),
PREV response to MOUNT message, 2-16
7-50
DISK Version Detail Panel (CAYD-2180), Preventing early drive release, 2-38
7-34
PRINT parameter, DYNCOPY program, 13-4
Disk Version List Panel (CAYD-2150), 7-29
FI Version List Panel (CAYD-2170), 7-32 Printing tape labels, 3-12
File Management Panel (CAYD-0000), 7-9
Processing
Primary Selection (CUI-MENU), 11-1
equal file IDs, 4-45
Tape Directory Panel (CAYD-3100), 7-44
expired files (CA Dynam/D), 4-43
Tape Selection Panel (CAYD-3000), 7-40
FORTRAN tape files, 2-74
TAPE Version Detail Panel (CAYD-2190),
7-37
retention and expiration date, 4-43
Tape Version List Panel (CAYD-2160), 7-31
the TLBL, 2-49
Tape Volume Detail Panel (CAYD-3110),
7-46 Production JCL, 2-53
Partitions PROGRAM command (AUDTUTIL), 12-19

communications region date, 2-9
Programmer Test option, 2-53
independence
(D) substitutions, 4-38 Programs
(FI) substitutions, 6-37 restarting, 3-14, 4-52, 5-8
(T) substitutions, 2-49 terminating, 3-14
defining, 2-49, 4-38, 6-37
Prompt mode, using CAIAUDIT, 11-1
with SORT and compiler work files,
4-38 Protecting
placing in WAIT state, 2-52 areas of disk pools, 4-30
stopped status, 2-15 data sets, 2-7, 2-57
shared tapes, 2-84
Password protection, 2-57, 8-44
the Catalog, 2-56
PATH command (AR command), 2-25
Protecting the Catalog, 8-67
PATHID, 3-16
PUB, 2-13, 2-46, 3-2
Performance considerations, 1-5

Pull lists REPORT command
TDYNLIST, 3-31 AUDTUTIL, 12-20
TDYNPULL, 3-33 DYNPRINT, 9-3
PULLTAB option record, 3-36 Reports

on catalog-controlled tapes, 3-28, 3-41
on disk files, 5-42
R on exceptional occurrences, 2-55
on scratch tapes, 3-42
on tape files
Read Backwards, support, 2-73 controlled tapes, 3-28
Reblocking, 3-8 tapes to be pulled, 3-31, 3-33
volume synchronization, 3-23
RECFM= parameter, DYNCOPY program, 13-4 on tapes to be pulled
Record TDYNLIST, 3-31
formats, 6-21 TDYNPULL, 3-33
length, 6-22 on the Audit Trail
size, 3-8 customized, 12-14
predefined, 12-12
Recording density on the Catalog
overriding, 2-46 active files (ACTVFILE), 9-16
specifying, 2-42, 2-59 file definitions (FILEDEFS), 9-19
uncontrolled tape files, 2-46 file usage (FREQUSE), 9-21
unspecified, 2-46 standard DYNPRINTs overview, 9-6
Recovering the Catalog, 12-4, 12-7 on vaults/slots, 3-49
on VTOC display (DYNVTOC), 9-24
Recovery from insufficient disk space, 4-36 samples
RECS= parameter, DYNCOPY program, 13-4 DYNVTOC, 9-27
Samples
Reel length, 2-39 ACTVFILE, A-19
REL response to MOUNT message, 2-16, 2-22 DYNCAT, A-9
FILEDEFS, A-21
Relative generation number, 4-22 FREQUSE, A-24
Releasing SPACEUSE, A-26
disk space, 4-40 TAPES, A-28
logical assignment, 6-38 TDYNLIST, A-14
tape drive lock, 2-84 TDYNSYNC, A-16
work data sets, 2-49 TDYNUTL, A-4
TDYNVLT, A-12
REMOVE command (TDYNSYNC), 3-21 VTOCS, A-29
Removing ASSGN from JCL, 2-7 RERUN response to MOUNT message, 2-15, 2-
RENAME command (DYNCAT), 8-78 20
Renaming RESET statement (FI), 1-15

automatic multifile data sets, 2-72 Resetting automatic multifile data sets, 2-72
generation data sets, 5-26
Resetting the generation ID, 8-28
Renaming, data sets/versions, 8-78
Restarting
REORG command (DYNUTIL), 5-26 programs, 3-14, 4-52, 5-8
tape files, 3-14
Index–15
RESTORE command (DYNCAT), 8-43, 8-80, setting mode on, 2-46
12-4 using as output, 2-55
with established owner, 2-58
RESTORE command (DYNUTIL), 5-37
SCRATCH command (DYNCAT), 8-83, 12-4
RESTORE REORG command (DYNCAT), 8-41,
8-83, 12-4 Scratching
automatic multifile data set names, 2-71
Restore/Backup utility, VCKDBKRS, 6-48
data set versions, 2-10
Retention
SCRPOOL command (DYNCAT), 8-86
and expiration date processing, 4-43
characteristics SCRPOOL usage, 2-41
altering, 2-48
SCRTCH response to MOUNT message, 2-16,
data sets, 2-3
2-21
establishing, 2-8
modifying, 2-10 SD files
multifile-volume data sets, 2-63 deleting, 4-42
specifying, 2-32 releasing unused space, 4-40
work data sets, 2-48 truncating, 4-40
data set ownership, 2-58
Secondary disk space
options, 2-9
cross-volume allocation, 4-33
REW response to MOUNT message, 2-16, 2-19
SEL= parameter, DYNCOPY program, 13-3
Rewinding tapes, 2-16, 2-37
SELECT AUDITRECORDS command, 11-14
ROUTE option (TDYNLIST), 3-32
SELECT command (AUDTUTIL), 12-22
Routing output to console, 6-29
Selecting
RUN parameter input tapes, 2-2
DYNCOPY program, 13-5 logical units, 4-25
RUN response to MOUNT message, 2-16 Sequential disk files

releasing unused space, 4-40
RUNIN parameter
truncating, 4-40
DYNCOPY program, 13-5
Serial Number File, 2-2
Running tests with production JCL, 2-53
SET command
CA Dynam/D, 4-48
S CA Dynam/FI, 6-26
CA Dynam/T, 2-82
Scratch Setting the mode

pool, 2-55 for uncontrolled tapes, 2-46
status, 2-53, 2-61 in the Catalog, 2-44
tapes in TLBL statements, 2-42, 2-46
allocating, 2-2 on scratch tapes, 2-46
assigning, 2-16 Shared tape drives, 2-84
changing length of, 2-41
initializing, 2-3 Signing on, 7-7
listing, 2-16, 2-55, 3-33 SKIP option (TDYNLBL), 3-13
reinitializing, 2-58
reporting, 3-28, 3-42 SKIP= parameter, DYNCOPY program, 13-4

Slot numbers, 3-46 SYNC
command (TDYNSYNC), 3-21
Sort key records
defining, 8-61 SYNC command (TDYNVLT), 3-49, 3-54
Sort work files, 4-19 Synchronizing

checklist, 3-22
SORTIN/SORTOUT and
message paths, 3-16
disk files, 4-18
tape
FI, 6-14
catalogs, 3-16
file independence, 6-19
volume information, 3-16
tape files, 3-4
SYSIPT
Sorting
accepting control statements, 3-9
and
and TDYNASN OPEN, 3-6
CA Dynam/FI, 6-8, 6-14, 6-17, 6-19,
6-28, 6-39 SYSLOG message support, 4-17, 6-28
DYNOPEN, 5-8
SYSPCH tapes, 3-6
disk files, 4-18, 4-42, 4-46
packages, 6-39 System Adapter, usage, 1-5
tape files, 3-4
work files, 4-38, 4-42, 4-46
Source books, DYNPRINT, 9-8 T

Space allocation (minimum percentage), 4-35
Tables
SPACEUSE report, 5-43 DTPOOL, 2-13
STACK option on TLBL, 2-67 PUB, 2-13
Stacking files, tape cartridges, 2-47 Tape

activity, 12-7
Standard DYNPRINT reports, 9-6 as intermediate storage, 2-48
Standard labels assignment to physical devices, 2-12
implementing CA Dynam/T, 2-6 cartridges, 2-46
support, 2-72 Cleaning and Error Report, 3-29
command (DYNUTIL), 5-40
Starting new volumes, 2-70 control commands, 2-16
Status Copy utility, 3-8
display, tape cartridges, 2-47 data set ownership, 2-58
Scratch, 2-53 directory, 7-44
TEST, 2-53 drive
availability, 2-12
STATUS locking/unlocking, 2-84
option (TDYNCLEN), 3-30 pool definition, 2-13
response to MOUNT message, 2-15 pooling/sharing, 2-84
STATUS command (DYNCAT), 8-90 status, 2-13, 2-24, 2-47
File Management (CA Dynam/T), 2-1
STEP option (TDYNLIST), 3-32 files
STOP response to MOUNT message, 2-15 displaying, 7-24
limiting allocation, 2-58
Storage requirements, 6-8, 6-22 restarting, 3-14
Index–17
scratch, 2-58 TDYNCOPY utility program
versions, 7-31, 7-37 JCL examples, 3-11
Label Generator (TDYNLBL), 3-12 options, 3-9, 3-10
listings
TDYNLBL utility program, 3-12
TDYNLIST, 3-31
TDYNPULL, 3-33 TDYNLIST utility program, 3-31
maintenance utilities
TDYNPULL utility program, 3-33
TDYNASN, 3-1
TDYNCLEN, 3-29 TDYNRST utility program, 3-14, 3-15
TDYNCOPY, 3-8
TDYNSYNC utility program
TDYNLBL, 3-12
commands, 3-18
TDYNLIST, 3-31
control statements, 3-18
TDYNPULL, 3-33
creating message paths, 3-16
TDYNRST, 3-14
initializing MACC queue files, 3-17
TDYNSYNC, 3-16
overview, 3-16
TDYNUTL, 3-38
reports, 3-23
TDYNVLT, 3-45
management, 2-1 TDYNUTL utility program
options, 2-34 commands, 3-39
positioning, multifile data sets, 2-64 functions, 3-38
POWER offload, 2-80 report fields, 3-43
recording density, 2-13, 2-42, 2-59 reports, 3-40
reel length, 2-39
TDYNVLT utility program
resources, 2-12
and DYNCAT, 3-47
return to SCRATCH status, 2-55
commands, 3-49
selection, 7-40
defining slots, 3-48
standard-labeled, 2-6
execution phases, 3-47
status
reports, 3-45, 3-51
display, 2-47
slots, 3-48
from TDYNCLEN, 3-31
updating the Catalog, 3-45
of unit, 2-15
volume Temporary data sets, 2-51, 4-8
defining, 7-46
TEST
displaying, 7-50
$TEST jobname, 2-53
information extract, 3-20
option (TDYNLBL), 3-13
ownership initialization, 2-58
status, 2-53
synchronization among catalogs, 3-16
updating, 3-19 Test program (DYNATEST), 10-18
Tape drive Test versions for production runs, 2-54

free status, 2-15
Testing
TAPEOPT option, 2-76 JCL, 2-53
jobs, 2-53
TAPES report, 3-28
temporary data sets, 2-61
TDYNASN utility program
Testing DYNACC Version 2, 10-18
functions, 3-1, 3-2
UPSI settings, 3-7 TITLE command (AUDTUTIL), 12-26
with LIBR, 2-76
TDYNCLEN utility program, 3-29

TLBL Updating
alternate, 2-56 tape volumes, 3-19
assigning mode, 2-46 the Catalog, 2-8, 2-53, 3-6, 3-14
coding, 6-21
UPSI
dropping, 2-37, 2-56
statement (DYNVTOC), 9-24
file names in, 2-6
identical dtfnames, 2-67 UPSI settings
matching data set name, 2-5 TDYNASN, 3-7
options, 2-30, 2-33, 6-11 TDYNCOPY, 3-9
order of operands, 6-10
User labels, 3-7
processing, 2-49
RELEASE option, 2-49 Utilities
specifying multiple options, 2-37 for disk files
STACK option, 2-67 CAINTDK, 5-1
statement, 6-21 DYNCONV, 5-3
DYNOPEN, 4-52, 5-1, 5-8
TRACE command (DYNUTIL), 5-42
DYNUTIL, 5-11
Trigger value for CA Dynam/D, 4-3 SPACEUSE, 5-43
VTOCS, 5-47
Trigger value for CA Dynam/D, 5-3
for disk files, DYNVTOC, 9-24
Truncating for file independence
ISAM files, 4-18 VCKDANAL, 6-46, 6-51
SD files, 4-18 VCKDBKRS, 6-47, 6-48
VCKDCLDK, 6-47, 6-50
TRUNCS support, 6-21, 6-41
for tape files
TAPES, 3-28
TDYNASN, 3-1
U TDYNCLEN, 3-29
TDYNCOPY, 3-8
UA, 2-16 TDYNLBL, 3-12
TDYNLIST, 3-31
Unchaining multifile tapes, 2-67 TDYNPULL, 3-33
Unconditional delete, 4-19 TDYNRST, 3-14
TDYNSYNC, 3-16
Uncontrolled tape files, 2-46, 2-55 TDYNUTL, 3-38
Unit record TDYNVLT, 3-45
devices, 6-28 for the Audit Trail, AUDTUTIL, 12-1, 12-5
simulation, 6-4, 6-15, 6-28 for the Catalog
ACTVFILE, 9-16
Unlabeled files, 3-9 FILEDEFS, 9-19
UNLBLIN= parameter, DYNCOPY program, FREQUSE, 9-21
13-6 with AVR, 3-1
UNLBLOUT= parameter, DYNCOPY program, Utilities, DYNCOPY, 13-1

13-6 Utility package support, 2-73
Unloading tapes, 2-16, 2-37
Unlocking tape drive, 2-85
Unspecified mode, 2-46
Index–19
V automatic assignment, 4-24
enforcing standards, 2-82
for OPEN requests, 2-7
Vault generic, 4-33
Location Control program (TDYNVLT), 3-45 on tape labels, 3-12
locations, 3-46 specifying in TLBL, 2-33
movement, 3-45 switching with automatic multifile data
reporting, 3-45, 3-49 sets, 2-70
VAULT command (DYNCAT), 8-91 VSAM support for FI, 6-21
vault sequencing with VLTSEQ, 3-46 VTAPE support, 3-57, see IBM Virtual Tape
VCKD Support
activating, 6-44 VTAPFILC parameter
backup/restore, 6-48 DYNCAT ADD command, 8-16
clear disk utility, 6-50
disk file analyzer, 6-51 VTAPFILE parameter
FBA disk files DYNCAT ADD command, 8-16
allocating, 6-46, 6-51 VTAPLOC parameter
creating, 6-47 DYNCAT ADD command, 8-16
mapping, 6-44, 6-46
file parameters, 6-44 VTOC
record formats, 6-43 access to, 9-2
system restrictions, 6-44 command (DYNCAT), 8-93
display, 9-24
VCKDANAL utility program, 6-46, 6-51 index, 4-11
VCKDBKRS utility program, 6-47, 6-48 modification, 5-1
Modification program (CAINTDK), 5-1
VCKDCLDK utility program, 6-47, 6-50 report, 5-47
VERIFY command (TDYNVLT), 3-49, 3-51 VTOCAC, 9-2
Verifying tape ownership during AVR, 2-58 VTOCS report, 5-47
Version specification
in DLBL, 4-16
in TLBL, 2-32 W
versions, data set
specifying for VTAPE files, 3-56 Work files
and CA Dynam/T, 2-48
versions, VTAPE
example, 2-51
adding to the catalog, 3-56
restrictions, 4-5
Viewing CAIAUDIT records, 11-4 SORT, 4-46
VOL1/HDR1 labels, 2-13
Volser, 2-82 X
VOLSER, 3-12
Volume XSYSTEM option record interface, with

sequence number, 2-33 TDYNSYNC, 3-16
serial numbers
assigning, 2-6

CA Dynam For VSE User Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CA Dynam For VSE User Guide

Încărcat de

Drepturi de autor:

Formate disponibile

CA Dynam for VSE

The manufacturer of this Documentation is CA.

Copyright © 2008 CA. All rights reserved.

 CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)

 CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)

 CA Dynam®/FI File Independence (CA Dynam/FI)

 CA TLMS Tape Management (CA TLMS)

 CA Common Infrastructure Services for z/VSE (CA CIS)

 CA Sort® for z/VSE (CA Sort)

If you have comments or questions about CA product documentation, you can

If you would like to provide feedback about CA product documentation, please

Chapter 2: Maintaining Tape Files

Chapter 3: Supporting Tape File Management

viii User Guide

Chapter 5: Supporting Disk File Management

Chapter 7: Using Online Panels−CAICUI

Chapter 8: Maintaining the Catalog−DYNCAT Program

Chapter 9: CA Dynam Reporting Utilities

xii User Guide

Chapter 11: CAIAUDIT in Prompt Mode

Chapter 12: Maintaining and Reporting on the Audit Trail

Chapter 13: DYNCOPY−CA Dynam File Utility Program

xiv User Guide

Appendix B: Audit Trail Report Examples

The following table summarizes the functions of the three products of CA

Subset System Purpose

CA Dynam/T Tape Management Tape data set management

CA Dynam/D Disk Management Disk data set management

CA Dynam/FI File Independence File independence between data and

CA Dynam for VSE Products

CA Dynam/T Tape Management

 Automatically controls tape data set usage and retention

 Prevents active tape data sets from being scratched

 Controls remote site tape movement and retention

CA Dynam/D Disk Management

CA Dynam/D manages your disk data sets in the following ways:

 Allocates primary and secondary disk space

 Permits automatic space release

Chapter 1: Introduction 1–1

 Provides device independence for automatic conversion to new DASD

CA Dynam/FI File Independence

CA Dynam/FI allows files to be switched from most sequential media to either

 Dynamically reblocks files for specified devices.

 Dynamically changes record formats.

 Simulates unit-record to multi-record device types, such as card reader to

Common Subset Features

 Data set control using the CA Dynam Catalog File

 Disaster recovery using the CA Dynam Audit Trail File

 Interfacing with your data center's operating system

 Reporting on CA Dynam and your operating system data

Creation of the CA Dynam Catalog is a requirement of CA Dynam/T, the tape

CA Dynam Catalog and Audit Trail Files

1–2 User Guide

Data Set Control

 Volume serial number

 Data set name and characteristics

 Retention and location information

To ensure that this information is always current and accurate, CA Dynam is

Backup, Restore, and Recover

Report on the Catalog

A common reporting facility, DYNPRINT, enables you to report on the CA

Chapter 1: Introduction 1–3

Start and Deactivate CA Dynam

CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)

CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)

CA Dynam®/FI File Independence (CA Dynam/FI)

CA TLMS Tape Management (CA TLMS)

CA Common Infrastructure Services for z/VSE (CA CIS)

CA Sort® for z/VSE (CA Sort)

Automatically controls tape data set usage and retention

Prevents active tape data sets from being scratched

Controls remote site tape movement and retention

Allocates primary and secondary disk space

Permits automatic space release

Provides device independence for automatic conversion to new DASD

Dynamically reblocks files for specified devices.

Dynamically changes record formats.

Simulates unit-record to multi-record device types, such as card reader to

Data set control using the CA Dynam Catalog File

Disaster recovery using the CA Dynam Audit Trail File

Interfacing with your data center's operating system

Reporting on CA Dynam and your operating system data

Volume serial number

Data set name and characteristics

Retention and location information

AR 0015 CADS330I ---- CA - CA - CA - CA - CA - CA - CA - CA ----

CA Dynam/T tape processing option codes at end of file-id, separated by