BIM-EPIC DISK / TAPE MANAGEMENT SYSTEM USER REFERENCE Release 6.3 (COPYRIGHT © 2001, B I MOYLE ASSOCIATES, INC.) BIM-EPIC is a proprietary product of B I Moyle Associates, Inc. It cannot be reproduced, changed, copied, or stored in any form (including, but not limited to, copies on magnetic media) without the express prior written permission of B I Moyle Associates, Inc.
This documentation applies to Release 6.3 of the program product BIM-EPIC. Original Printing ................ 01/08/2001 Last Revised.......................
Contents Trademark Information................................................................................................. x Preface .........................................................................................................................xi Related Publications .................................................................................................. xiv Chapter 1 Introduction.......................................................................................................
Online Catalog Management Commands...................................................................2-5 Using the Online Manager..............................................................................................2-7 Configuring Online Security ......................................................................................2-7 Maintaining User Profiles ........................................................................................2-12 Customizing the EDD Display.....................
CATALOG ..............................................................................................................3-12 CLEAN....................................................................................................................3-18 CLOSE.....................................................................................................................3-19 CYCLE ....................................................................................................................3-20 DELETE ..
LABEL Parameter ...................................................................................................6-25 OPTION Parameter .................................................................................................6-26 SPACE Parameter....................................................................................................6-30 UNIT Parameter.......................................................................................................6-33 VOLUME Parameter ..............
VSE/ICCF and Interactive Partition GETVIS Requirements with BIM-EPIC ............7-52 Processing with COBOL II ..........................................................................................7-53 Using BIM-EPIC's JCL Features .................................................................................7-54 Restarting Programs from a Checkpoint ..................................................................7-54 Choosing the Device Type.........................................................
Using the Subroutines ............................................................................................10-11 Return Codes..........................................................................................................10-12 Processing Requirements .......................................................................................10-14 Creating Job Setup/Run Sheets (TSIDFAV) ..............................................................10-15 Chapter 11 Job Activity Reports ...........
TSIDONL Control Statements...............................................................................13-29 Differences Between TSIDONL Onload and TSIDONL Restore .........................13-32 Consolidating Offload Versions (TSIDOFC) ........................................................13-34 Appendix A BIM-EPIC Report Fields and Examples ....................................................A-1 Customized Reports...........................................................................................
Trademark Information This manual refers to the following brand or product names, registered trademarks, and trademarks which are listed according to their respective owners. Software Diversified Systems, Inc. DUSP™ MAXBACK/VSE Automatic Tape Library (ATL) Library Management Software (LMS) Storage Technology Corporation (Storage Tek®) Host Software Component (HSC) Computer Associates International, Inc.
Preface Most BIM-EPIC features operate only in conjunction with controlled datasets (datasets that BIM-EPIC catalogs and maintains), and controlled datasets are assumed in the discussion of each feature. Activity involving uncontrolled datasets is noted explicitly. BIM-EPIC configuration options govern how BIM-EPIC operates and what you can expect BIM-EPIC to do. Default options are assumed in the main body of this manual.
Braces ({ NOFUNCTION }) also indicate required items. They surround lists of values or parameters where only one must be supplied. Specify only one of the choices. Do not code the braces ({}) themselves. The vertical bar symbol (YES|NO) separates choices that are mutually exclusive. Enter only one of the choices. An underlined item (YES) indicates a default value that is used if the parameter is not specified. Unless otherwise noted, parameters must be specified in the order shown.
Procedure Step Action 1 Gain as thorough an understanding of the situation as you can, and classify your call using one of the following categories: 1. MALFUNCTION IN A USER PROGRAM: A user program behaves differently with BIM-EPIC turned on than with BIM-EPIC turned off. 2. MALFUNCTION IN VSE: VSE malfunctions when BIM-EPIC is turned on. For example, you receive non-interruptible wait states, system loops, and so on. 3. BIM-EPIC FAILURE: An overall BIM-EPIC failure (abend). 4.
Related Publications The documents described below contain important BIM-EPIC technical information. Familiarity with the relevant IBM operating system is assumed. • • • • • • xiv User Reference BIM-EPIC Installation and System Guide contains detailed procedures for BIM-EPIC system installation, configuration, and maintenance. It assumes that you have access to the User Reference. BIM-EPIC User Reference Guid serves as both user guide and reference to BIM-EPIC operating features.
1 Introduction This chapter contains an overview of features and functions provided by BIM-EPIC®. This manual is written to include the novice mainframe programmer. If you have more experience in the field, you already are familiar with some of the subjects discussed and you may want to skim those sections. However, most of the chapter presents information unique to BIM-EPIC, so we encourage everyone to read the chapter for a full introduction. Chapter Contents BIM-EPIC Fundamentals.......................
Configuration Options BIM-EPIC Fundamentals BIM-EPIC Fundamentals Configuration Options Description BIM-EPIC provides configuration options which allow you to customize many aspects of your processing. Many configuration options are discussed in this manual. Please consult your systems programmer or the BIM-EPIC Installation and System Guide if you have a question about a specific configuration option.
BIM-EPIC Fundamentals Controlled Datasets Controlled Datasets Description BIM-EPIC controls datasets best when they are known to its Dataset Name (DSN) Catalog. The information contained in the records that make up a DSN Catalog entry determines how a dataset is processed.
Start Track 1 Datasets BIM-EPIC Fundamentals Start Track 1 Datasets Description A Start Track 1 dataset is a disk dataset that is defined by the use of the number “1” in the relative track field of the VSE EXTENT statement. For example: // DLBL MYFILE,’ANY.FILE’ // EXTENT SYS005,SYSWK3,1,0,1,20 The use of the number “1” in the relative track field above indicates that BIM-EPIC will allocate the dataset. The use of any other number in this field indicates that BIM-EPIC does not handle the allocation.
BIM-EPIC Fundamentals Controlling Different Types of Datasets Controlling Different Types of Datasets Description BIM-EPIC can control SAM, ISAM, and DA datasets. If the VSAM configuration option is set to YES, BIM-EPIC logs VSAM extent information in the DSN Catalog. Logging occurs each time a VSAM dataset is opened. BIM-EPIC always reflects the currently used extents, even if the dataset contains multiple secondary allocations. BIM-EPIC can only control TYPEFLE=WORK files on disk.
DSN Catalog Entries BIM-EPIC Fundamentals DSN Catalog Entries Description BIM-EPIC’s control of datasets is based on information contained in the DSN Catalog. All information pertaining to one cataloged dataset name is called a DSN Catalog entry. The format and contents of an entry are described below. DSN Catalog information is divided into two levels: the BIM-EPIC dataset definition (EDD) level and the version level. Each EDD contains all the attributes associated with a unique dataset name.
BIM-EPIC Fundamentals DSN Catalog Management DSN Catalog Management Description Most updates to the DSN Catalog are made automatically as datasets are processed. However, sometimes you want to add a special dataset or change the defaults you have supplied for an existing EDD. This manual cataloging can be done using either the Online Manager or the TSIDMNT utility. The BIM-EPIC Online Manager (EOM) is a panel-driven catalog management program.
DSN Catalog Maintenance BIM-EPIC Fundamentals DSN Catalog Maintenance Description The DSN Catalog must be maintained regularly. Maintenance includes regular backups and scratch runs, as well as periodic re-indexing. Catalog maintenance is done using the DSN Catalog maintenance utility (TSIDUTL). See the BIM-EPIC Installation and System Guide for information about required maintenance.
BIM-EPIC Dataset Definitions (EDDs) Introduction BIM-EPIC Dataset Definitions (EDDs) Introduction Dataset Name BIM-EPIC uses the dataset name in the DSN Catalog to identify a dataset as controlled. Each time a controlled dataset is opened, BIM-EPIC participates in processing. The rules for dataset naming are: • Dataset names can be up to 44 characters long, except for generation datasets (see below), whose names are limited to 35 characters.
Introduction BIM-EPIC Dataset Definitions (EDDs) is no difference in function between them. You can use both together to group datasets at two levels. Either one or both can be used for any dataset. SYS Number You can cause a specific SYS number to be used for a dataset by entering that SYS number in the EDD. This inhibits LUB allocation (described in Chapter 7) for the dataset each time it is processed. We recommend that you avoid assigning a SYS number here unless it is absolutely necessary.
BIM-EPIC Dataset Definitions (EDDs) Introduction You can use the retention days field to specify permanent retention (PERM). When a disk version is created with permanent retention, an expiration date of 2099366 is recorded in the VTOC entry. When BIM-EPIC sees the 2099366 expiration date, it does not allow the operator to display or delete the dataset in response to an INSUFFICIENT SPACE condition.
EDD Tape Information BIM-EPIC Dataset Definitions (EDDs) EDD Tape Information Standard Label The label field specifies whether an output tape dataset is to be created on a labeled or unlabeled tape. Tape Density The tape density specifies which density to use when creating a tape dataset. When a density is specified, BIM-EPIC only scans drives that support the specified density when it looks for a valid scratch tape. For example, you can use this field to assign a dataset to cartridge tapes only.
BIM-EPIC Dataset Definitions (EDDs) EDD Tape Information Tape Size If you specify Tape Size as SMALL, BIM-EPIC requests a small scratch tape when the dataset is created. If a tape volume serial number ends in ‘S’, BIM-EPIC considers the tape small. Large tapes are the default, and they have no restriction on their volume serial numbers. Vault Method Number A vault method establishes a pattern of movement through tape vaults for each tape volume in the dataset.
EDD Disk Information BIM-EPIC Dataset Definitions (EDDs) EDD Disk Information CISIZE The CISIZE field specifies a CISIZE for FBA devices and forces the dataset to be written to maximize the number of records written to a control interval. Use CISIZE instead of block size for datasets to be written on FBA devices. Block size and CISIZE are mutually exclusive; you can only specify one of these in a BIMEPIC dataset definition.
BIM-EPIC Dataset Definitions (EDDs) • • • EDD Disk Information estimated number of records block size track/block capacity of the selected volume. ALR allows you to migrate from one device type to another without changing the allocation size. ALR is valid only for sequential disk datasets created with a DTFSD. Chapter 1.
Introduction Version Information Version Information Introduction Description As each version of a dataset is created, BIM-EPIC automatically records attributes specific to that version in the DSN Catalog. The attributes recorded at this level are described in this section. Version Number The current (most recently created) version is always version 1. Whenever a new version of a dataset is created, previous versions are incremented automatically.
Version Information Introduction Scratch (S) denotes a tape version in scratch status. The tape can be overwritten at any time. Disk version records are deleted, not marked as scratch. Lock (L) denotes a version in locked status. It cannot be accessed as input until it is unlocked or released using Online Manager or the TSIDMNT utility. Subdataset (N) denotes a dataset in a multi-dataset group with file sequence number 2 or greater. Work (W) indicates a non-generation dataset.
Introduction Version Information Creation Date/Time BIM-EPIC records the date and time the version was written. Creating Job/Device Address BIM-EPIC records the name of the job that created the version, the partition in which it was created, and the address (cuu) of the device on which it was created. Last Access: Job and Date At each open, BIM-EPIC records the date the version was accessed and the name of the job that accessed it.
Version Information Automatic Cataloging Automatic Cataloging Description Each new dataset and version must have an entry in the DSN Catalog to be controlled. These entries can be created automatically for uncontrolled datasets using the AUTOCAT and AUTOLOG features or the parameter DISP=(x,CATLG) parameter on a DD statement. AUTOCAT and AUTOLOG are configuration options described in the BIM-EPIC Installation and System Guide. AUTOCAT and AUTOLOG operate globally on all qualifying datasets.
Automatic Cataloging Configuration Options Version Information Automatic cataloging is affected by the AUTOCAT, AUTOLOG, CATRT1, NCATDSK, CYCL, RETEN, DEFPOL, and DEFEXT configuration options. AUTOCAT functions can be specified differently for tape and disk. There are three choices for automatic cataloging functions: Global, SYSPARM, and None. Global AUTOCAT Global automatic cataloging catalogs all datasets. SYSPARM AUTOCAT Only selected datasets are cataloged under SYSPARM automatic cataloging.
Version Information Retention and Scratching Retention and Scratching Description All catalog-controlled datasets must be scratched before tapes and disk space can be reused. However, BIM-EPIC does not scratch any datasets unless specifically told to do so. This can be done in four ways.
Rules for Dataset Retention Version Information Rules for Dataset Retention Cataloged Datasets BIM-EPIC’s retention rules for cataloged datasets are: Tapes are not made available for reuse and disk space is not released until dataset versions are scratched. Non-temporary versions are not scratched until the SCRATCH function of the TSIDUTL utility is executed. TSIDUTL does not scratch any versions until they are eligible. A version is not eligible until ALL the retention criteria have been satisfied.
Version Information Examples Examples Description This section contains examples of retention under multiple criteria. Retain x Versions for y Days You need to retain each version of an inventory dataset for 100 days. You also need to retain the last 10 versions, regardless of when they were created. The dataset definition specifies: Generation Dataset......YES Retention Days.......100 Retention Cycles.....10 Retention DLA........
Retention for Start Track 1 Datasets Version Information Retention for Start Track 1 Datasets Description By default, BIM-EPIC’s retains Start Track 1 datasets with period retention only. Expiration is determined by the JCL or by the default retention for Start Track 1 datasets specified in the DSKRET configuration option. The existing version is deleted as a new version is created. The space occupied by a Start Track 1 dataset becomes available when the expiration date in the VTOC has been reached.
Version Information Overriding Standard Retention Overriding Standard Retention Description Since the default retention criteria may not be suitable for every version of every dataset, you may want to modify retention criteria occasionally. You can change retention for new versions, for existing versions, or for the dataset as a whole. Retention days or an expiration date specified on a TLBL, DLBL, or DD statement for an output dataset overrides the catalog default.
Automatic Generation Purge Version Information Automatic Generation Purge Description When Automatic Generation Purge (AGP) is enabled, BIM-EPIC automatically deletes DSN Catalog information about any disk dataset whose version number exceeds the cycles retention in the BIM-EPIC dataset definition (EDD). AGP is enabled by setting the AGP configuration option to YES when creating or updating an EDD in the DSN Catalog.
The Recorder File The Recorder File Description The Recorder logs controlled dataset activity. This includes: • • • all DSN Catalog maintenance transactions, excluding TSIDVLT (vaulting) maintenance all opens and closes of controlled datasets machine use and job accounting statistics The Recorder File is vital to emergency recovery of the DSN Catalog. It contains a record of all changes made to the DSN Catalog since the last catalog backup.
LUB Allocation Additional BIM-EPIC Features and Functions Additional BIM-EPIC Features and Functions LUB Allocation Description VSE’s Logical Unit Block (LUB) connects the logical unit (SYS number) in a program’s file definition (DTF) with the physical device (cuu) that controls the dataset. The LUB allocation feature of BIM-EPIC assigns logical units for tape and disk devices if they are opened when the SYS number specified in the program is already in use.
Additional BIM-EPIC Features and Functions Managing Tape Devices Managing Tape Devices Drive Assignments BIM-EPIC makes and releases drive assignments automatically with the Automatic Volume Recognition (AVR), Autoattach, and Early Drive Release features. With these functions, tape drives are assigned to a partition or virtual machine only between open and close. They aren’t tied up between job start and open time or between close time and EOJ, so tape drive availability is increased.
Managing Tape Devices Additional BIM-EPIC Features and Functions BIM-EPIC issues these commands during AVR to search for the desired tape on a drive that is owned by VM. These commands differ from their IBM counterparts in the following ways: • • Early Drive Release VDETACH detaches the tape drive without unloading the tape. This leaves the tape accessible for another AVR search. Both the VATTACH and VDETACH commands operate in “silent” mode. That is, they do not issue messages.
Additional BIM-EPIC Features and Functions Managing Disk Devices Managing Disk Devices Disk Pooling BIM-EPIC uses disk pooling to make disk allocation more flexible and more efficient. The systems programmer defines disk pools for use in your installation. Disk pools can include one or more disk volumes. Part of a volume can also be allocated to a pool. Each disk dataset must be assigned to a disk pool before allocation. Each time the dataset is written, its allocation is made in that pool.
Starting and Stopping Partitions Additional BIM-EPIC Features and Functions Starting and Stopping Partitions Description You can stop a partition by responding STOP to most BIM-EPIC messages. To restart, submit the following command to the attention routine (AR): MSG xx where xx specifies the partition identifier (for example, BG, F1, F2). Partitions can be stopped and restarted at any time using the VSE STOP and START commands.
Additional BIM-EPIC Features and Functions Creating Reports Creating Reports Description BIM-EPIC programs provide a variety of reports about tape and disk datasets, storage use, and even job accounting. For report examples and an explanation of report fields, see “Report Fields and Examples”. You can create your own reports containing BIM-EPIC data from the DSN Catalog and the Recorder File. For more information, see “Customized Reports”. Chapter 1.
When is BIM-EPIC On? The BIM-EPIC Environment The BIM-EPIC Environment When is BIM-EPIC On? Description BIM-EPIC is activated by partition. If you have just IPLed your system, or you have deactivated and reactivated BIM-EPIC, BIM-EPIC becomes functional when the first OPEN is issued in the partition. BIM-EPIC does no processing until it is activated. This means that JCL enhancements (such as DD statements) cannot be processed until then.
The BIM-EPIC Environment What Happens When BIM-EPIC Scratches or Deletes a Dataset? What Happens When BIM-EPIC Scratches or Deletes a Dataset? Description BIM-EPIC provides several methods for scratching datasets. Datasets can be scratched at your request using JCL, Online Manager, the TSIDMNT catalog management utility, or the TSIDUTL catalog maintenance utility. Regardless of which method is used, BIM-EPIC scratch processing is the same.
BIM-EPIC JCL The BIM-EPIC Environment BIM-EPIC JCL Description 1-36 User Reference BIM-EPIC changes the way you use JCL. It offers many enhancements to standard VSE job control. It also requires some changes to function properly.
The BIM-EPIC Environment Physical Input/Output Control System and Pre-Open Checking Physical Input/Output Control System and Pre-Open Checking Description Programs that use physical IOCS cause conflicts with tape and disk management programs. As the following sections describe, BIM-EPIC doesn’t get control until your program issues a request to the VSE supervisor for open, end-of-volume/extent, or close.
What happens if the job cancels? The BIM-EPIC Environment What happens if the job cancels? Description At open time, versions are entered into the DSN Catalog with an open status. When close processing is requested, BIM-EPIC updates the version record and indicates that the version has been closed and is now active. If the job cancels before a version is closed, the version remains in open status.
BIM-EPIC Job Control Introduction BIM-EPIC Job Control Introduction JCL Enhancements Because BIM-EPIC offers JCL enhancements which VSE cannot process, BIM-EPIC processes JCL options before VSE so that no error is generated. BIM-EPIC checks dataset status and generates the required VSE label information. Chapter 1.
Tape Processing BIM-EPIC Job Control Tape Processing Open Processing Open, end-of-volume, and close processing are the most significant processing periods for BIM-EPIC, and open processing is the most important of the three. In each case, processing is different for tape and disk. Each is discussed separately. When a tape dataset is opened, BIM-EPIC carries out the following tasks: BIM-EPIC determines whether a dataset is tape or disk by checking the JCL and the DSN Catalog.
BIM-EPIC Job Control Tape Processing It passes final control to VSE. Closing Tape Datasets In close processing for tape, BIM-EPIC gains control from and passes control to VSE more than once. BIM-EPIC tells VSE how to position the tape, whether to unload it, rewind it, or leave it in place. It releases the drive’s assignments and detaches the drive from the VSE machine is Autoattach is active. On output, it writes to the DSN Catalog, placing all volumes in closed status.
Disk Processing BIM-EPIC Job Control Disk Processing Open and End-ofExtent Processing The tasks required for disk open and end-of-extent processing are similar to those for tape. BIM-EPIC reads the DSN Catalog, issues messages, makes an assignment, and so on. For disk, however, BIM-EPIC must make the allocation, which is more complicated than finding the correct tape volume. Quick Disk Allocation (QDAS) At every open, VSE reads the VTOC sequentially, which can require thousands of I/O operations.
BIM-EPIC Job Control On Input Disk Processing 1. BIM-EPIC locates the dataset. For cataloged datasets, it finds the dataset’s location in the DSN Catalog. For Start Track 1 datasets, it has to read each VTOC in the pool until it finds the first extent of the dataset. 2. It updates the VSE Label Area, creating an extent and assigning the disk volume. Cataloged dataset processing requires a great deal less overhead than Start Track 1 processing.
Disk Processing BIM-EPIC Job Control BIM-EPIC determines whether a precautionary extent is required. If so, it writes the space holder record, updates the VSE Label Area with the new extent information, and writes the extent record in the DSN Catalog. It places the version in closed status in the DSN Catalog. BIM-EPIC passes control to VSE.
2 BIM-EPIC Online Manager This chapter describes the BIM-EPIC Online Manager. Chapter Contents Introduction to Manual Cataloging ................................................................................2-2 Introduction to Online Manager .....................................................................................2-3 Using the Online Manager .............................................................................................2-7 Managing BIM-EPIC Dataset Definitions (EDDs) ..........
Introduction to Manual Cataloging Introduction to Manual Cataloging Description There are several reasons for doing manual cataloging and catalog management. Automatic cataloging is global in scope, so it will not match the exact requirements of all datasets.
Introduction to Online Manager Overview Introduction to Online Manager Overview Description This chapter gets you started with online management, including: • • • • accessing Online Manager using panels and menus getting help exiting Online Manager Online Access Using CICS Online Manager can be accessed as a CICS transaction. See the BIM-EPIC Installation and System Guide for information on installing the CICS EPIC transaction.
Overview Primary Option Menu Introduction to Online Manager When the Online Manager is accessed, the Primary Option Menu is displayed first. TSIO0001.
Introduction to Online Manager Online Catalog Management Commands Online Catalog Management Commands Description Even while using Online Manager panels for your catalog management, you can still execute TSIDMNT functions in command mode. To do this, place the cursor in a panel’s command area, and type EPIC, followed by a space and the normal TSIDMNT syntax. See Chapter 3, “DSN Catalog Management Utility”, for more information.
Online Catalog Management Commands Disk Volume Control (BIM-EPIC only) 2-6 User Reference Introduction to Online Manager Using TSIDMNT commands, you can temporarily remove disk packs from BIM-EPIC processing. Use QUIESCE to prevent writing controlled output datasets on a disk volume, while still allowing datasets to be read from it. Use OFFLINE to remove the volume from both input and output processing. ONLINE returns the volume to full processing.
Using the Online Manager Configuring Online Security Using the Online Manager Configuring Online Security Controlling Access to BIM-EPIC Online Manager Online Manager has its own panel–driven security system. This system allows online catalog management functions and some BIM-EPIC system functions to be restricted selectively to individual users, and for multiple users to inherit (model) an individual set of security attributes.
Configuring Online Security Using the Online Manager Accessing the Online Security System To access the security system from the Primary Option Menu, type SECURITY at the command line and press ENTER, or select the SYSTEM option to display the System Configuration Menu. To access the security system from the System Configuration Menu, select the SECURITY option. Secured Users Panel The Secured Users panel displays the names of security profiles that are defined to Online Manager.
Using the Online Manager Configuring Online Security Example Enter SECURITY at an Online Manager command line to display the Secured Users panel. Place M (for Model) in front of the $DEFSEC profile, and press ENTER. When prompted for a new profile name, enter USER99. The list displays USER99 and shows that it is modeled on $DEFSEC. USER99 now possess the security attributes of $DEFSEC.
Configuring Online Security Using the Online Manager Changing Security Settings for One User Enter SECURITY at an Online Manager command line to display the Secured Users panel. Place U (for Update) in front of the selected user’s security profile, and press ENTER. When the User Security panel is displayed, make the necessary changes. Press PF6 to accept the changes.
Using the Online Manager Security Administration Example Configuring Online Security Step Action 1 Use your security administrator’s user ID as the name for a new security profile modeled on $EPIC. 2 Update the new administrator profile with password protection and enable password prompting by setting Bypass the BIM-EPIC Sign–On Panel to ‘N’.
Maintaining User Profiles Using the Online Manager Maintaining User Profiles Description Online Manager allows users to customize the way dataset definition and version information is displayed. BIM supplies two default profiles containing display layouts and confirmation options. The $DEFPROF default profile provides a modifiable layout that applies to all users who are not specifically defined to Online Manager. The $EPIC default profile provides a fixed standard layout.
Using the Online Manager Customizing the EDD Display Customizing the EDD Display Description Use the Modify EDD Display panel to change the screen display format for BIM-EPIC dataset definitions. The Current Display Order area provides functions to Move (M) a field to a new location Following (F) or Preceding (P) another field, or to Remove (R) a field from the display. Press PF1 for more information. TSIO0301.
Customizing the Version Display Using the Online Manager Customizing the Version Display Description Use the Modify Version Display panel to change the screen display format for dataset version information. The Current Display Order area provides functions to Move (M) a field to a new location Following (F) or Preceding (P) another field, or to Remove (R) a field from the display. Press PF1 for more information. TSIO0302.
Using the Online Manager Customizing the Confirmation Options Customizing the Confirmation Options Description Use the Modify Profile Defaults panel to enable or disable confirmation prompts to a variety of BIM-EPIC functions, and to change the default level for a catalog search. The $EPIC default profile always requests confirmation. TSIO0303.
Using Online Manager Help Using the Online Manager Using Online Manager Help Description The Online Manager provides a number of types of online help for the user. These include: • • • • Panel help Input field help Command help Panel navigation help Help for Help The H (Help) option of the Primary Option Menu provides a description of the Help system. Panel Help Press PF1 in the command line of any panel to display help for that panel.
Using the Online Manager Panel IDs Display (I) Using Online Manager Help TSIO0901.
Managing BIM-EPIC Dataset Definitions (EDDs) Managing BIM-EPIC Dataset Definitions (EDDs) Description 2-18 User Reference BIM-EPIC maintains a dataset–level description for each unique dataset name it controls, regardless of the number of versions of it that exist. This BIM-EPIC dataset definition (EDD) can be created automatically during processing, or it can be defined manually.
Managing BIM-EPIC Dataset Definitions (EDDs) Displaying BIM-EPIC Dataset Definitions Displaying BIM-EPIC Dataset Definitions Introduction Use the Search Catalog panel to search for dataset definitions in the DSN Catalog. You can search for EDDs using the following criteria: • • • Two–character user–defined User ID (not your system USERID) Two–character user–defined System ID (not the SMFID) Tape pool ID Using the Manage EDDs panel, you can view, modify, and update dataset definitions.
Displaying BIM-EPIC Dataset Definitions Procedure 2-20 User Reference Step Managing BIM-EPIC Dataset Definitions (EDDs) Action 1 Type a fully or partially qualified dataset name in the Name field. If you specify a partial dataset name, all EDDs that meet the name criteria are displayed. An asterisk (*) can be substituted for dataset levels. A question mark (?) can be substituted for any individual character. 2 Enter an 'E' in the Level field to view selected EDDs.
Managing BIM-EPIC Dataset Definitions (EDDs) Managing EDDs Managing EDDs Introduction The Manage EDDs panel lists dataset definitions matching the dataset name or expression you entered in the Search Catalog panel. From this panel, you can select a dataset definition to display or update. You can add, delete, lock, purge, release or unlock a dataset definition. You can also request a list of its versions. Access From the Primary Option Menu, press M (for MANAGE).
Displaying a Dataset Definition Managing BIM-EPIC Dataset Definitions (EDDs) Displaying a Dataset Definition Introduction The EDD Information panel displays the dataset definition attributes. You can update those attributes or create a new definition based on the one displayed. Access From the Manage EDDs panel, place an I (Information) in front of a dataset definition entry and press ENTER to display the EDD Information panel. EDD Information Panel TSIO0102.
Managing BIM-EPIC Dataset Definitions (EDDs) Creating a Dataset Definition Creating a Dataset Definition Introduction Use the Define an EDD panel to create new dataset definitions. The attributes on this panel are those of the dataset being modeled if you typed M in the input field of the EDD Information panel. Access You can access the Define an EDD panel by entering D (for DEFINE) on the Primary Option Menu.
Creating a Dataset Definition Using TSIDMNT CATALOG 2-24 User Reference Managing BIM-EPIC Dataset Definitions (EDDs) BIM-EPIC also provides the CATALOG command of the TSIDMNT catalog management utility to create a BIM-EPIC dataset definition (EDD). See Chapter 3, “DSN Catalog Management Utility”, for information on using the CATALOG command.
Managing BIM-EPIC Dataset Definitions (EDDs) Updating a Dataset Definition Updating a Dataset Definition Introduction Online Manager provides the Update an EDD panel to update your BIM-EPIC dataset definitions (EDDs) in the DSN Catalog. The attributes displayed on this panel are the defaults for all output datasets using this dataset name. Any modifications affect subsequent versions only.
Locking a Dataset Definition Managing BIM-EPIC Dataset Definitions (EDDs) Locking a Dataset Definition Introduction Locking a BIM-EPIC dataset definition prevents its use for output (creating a new version with the same dataset name). You can lock a dataset definition from the Manage EDDs panel. Access From the Primary Option Menu, press M (for MANAGE). Complete the Search Catalog panel and press Enter. Manage EDDs Panel TSIO0101.
Managing BIM-EPIC Dataset Definitions (EDDs) Releasing a Locked Dataset Definition Releasing a Locked Dataset Definition Introduction Releasing a locked BIM-EPIC dataset definition permits one use of the EDD for output (creating one new version with the EDD name and attributes). You can release a dataset definition from the Manage EDDs panel. To permanently release an EDD, use the UNLOCK procedure. Access From the Primary Option Menu, press M (for MANAGE).
Unlocking a Dataset Definition Managing BIM-EPIC Dataset Definitions (EDDs) Unlocking a Dataset Definition Introduction Unlocking a BIM-EPIC dataset definition allows its unrestricted use for output (creating new versions with the EDD name and attributes). You can lock a dataset definition from the Manage EDDs panel. Access From the Primary Option Menu, press M for MANAGE. Complete the Search Catalog panel and press ENTER. Manage EDDs Panel TSIO0101.
Managing BIM-EPIC Dataset Definitions (EDDs) Deleting a Dataset Definition Deleting a Dataset Definition Introduction When you delete a BIM-EPIC dataset definition, all version information is removed from the DSN Catalog, but tape volume information is kept under the dataset name ‘** DSN DELETED **’ until the volume serial number is reused or purged. You can remove an EDD from the DSN Catalog using the Manage EDDs panel. Access From the Primary Option Menu, press M (for MANAGE).
Displaying Version Information Managing Dataset Versions Managing Dataset Versions Displaying Version Information Introduction In order to view or maintain a dataset version online, you must first find its entry in the DSN Catalog. Online Manager provides the Search Catalog panel to request a list of dataset versions according to specified criteria.
Managing Dataset Versions Procedure Using TSIDMNT DISPLAY Displaying Version Information Step Action 1 Type a fully or partially qualified dataset name in the Name field. If you specify a partial dataset name, all versions that meet the name criteria are displayed. An asterisk (*) can be substituted for dataset levels. A question mark (?) can be substituted for any individual character. 2 Enter an V in the Level field to view selected versions.
Selecting a Version from a List Managing Dataset Versions Selecting a Version from a List Introduction The Manage Versions panel lists dataset versions based on the search criteria specified on the Search Catalog panel. From Manage Versions, you can select a specific version for display. You can also close, lock, unlock, release, scratch, retain or cycle the version. From Manage Versions, you can also display and maintain tape volume information.
Managing Dataset Versions Displaying Version Attributes Displaying Version Attributes Introduction The Version Information panel lists information on a specific dataset version. From this panel you can add a new version or display information on associated volumes. Access From the Manage Versions panel, place an I (Information) next to the dataset name and press ENTER. Version Information Panel TSIO0201.G -------- BIM-EPIC - Version Information ------------COMMAND ===> ( _ ) Dataset: BILL.REPRINT.
Adding Version Information Managing Dataset Versions Adding Version Information Introduction Using the Add a Tape Version panel, you can add a new version to an existing dataset definition or you can add new volume serial numbers to an existing dataset version. Access To add a new tape version to a controlled dataset definition, access the Manage EDDs panel and enter A (for Add) to display the Add a Tape Dataset panel.
Managing Dataset Versions Locking a Version Locking a Version Introduction Locking a version prevents its use as input. You can lock a version from any panel that allows general version management. Access Enter the dataset name and Level V on the Search Catalog panel, and press ENTER to display the Manage Versions panel. Manage Versions Panel TSIO0200.
Releasing a Locked Version Managing Dataset Versions Releasing a Locked Version Introduction Releasing a version permits one use of a locked version as input. You can release a locked version from any panel that allows general version management. Access Enter the dataset name and Level V on the Search Catalog panel, and press ENTER to display the Manage Versions panel. Manage Versions Panel TSIO0200.
Managing Dataset Versions Unlocking a Version Unlocking a Version Introduction Unlocking a version allows its unrestricted use as input. You can unlock a version from any panel that allows general version management. Access Enter the dataset name and Level V on the Search Catalog panel, and press ENTER to display the Manage Versions panel. Manage Versions Panel TSIO0200.
Closing a Version Managing Dataset Versions Closing a Version Introduction It may be necessary to manually close a dataset version when it is in open status or conditionally cataloged by the abnormal termination of a job. You can close a version from the Manage Versions panel. Access Once you have used the Search Catalog panel to enter your search criteria, the Manage Versions panel is displayed, listing all dataset versions that meet the name criteria specified. Manage Versions Panel TSIO0200.
Managing Dataset Versions Removing Version Information from the DSN Catalog Removing Version Information from the DSN Catalog Introduction A dataset’s version information can be removed from the DSN Catalog by deleting its dataset definition or by purging its tape volume serial number. Procedure See “Deleting a Dataset Definition” or “Purging a Tape Volume” for information on actions which delete version information.
Managing Tapes Managing Tapes Tapes in the DSN Catalog Every tape used for a BIM-EPIC-controlled dataset is recorded in the DSN Catalog. Tapes are identified in the DSN Catalog by volume serial number. New tapes are added to the DSN Catalog automatically when BIM-EPIC-controlled datasets residing on those tapes are processed. You can also enter tape information into the DSN Catalog by using the Online Manager or the TSIDMNT ADD command. Volumes entered into an ACL are added to the dataset name ‘***.
Managing Tapes How BIM-EPIC Selects Tapes for Mounting How BIM-EPIC Selects Tapes for Mounting Introduction BIM-EPIC controls which tapes can be used for output. It checks the volume serial number of every tape processed. If the mounted volume is controlled, its serial number is compared with its corresponding DSN Catalog entry for scratch status before it can be used as output. If the tape is uncontrolled, BIM-EPIC checks to see if the volume serial number is unique within the DSN Catalog.
Displaying Tape Volume Information Managing Tapes Displaying Tape Volume Information Introduction Online Manager provides the Tape Volume Information panel to display information on any controlled tape volume. You can also execute tape functions from the Tape Volume Information panel. Access Choose M (for MANAGE) on the Primary Option Menu to display the Search Catalog panel. Type the desired volume serial number in the Volume Serial Number field.
Managing Tapes Maintaining Tape Volume Information Maintaining Tape Volume Information Introduction Use the Manage Tape Volumes panel to manage tape volume information. Access Choose M (for MANAGE) on the Primary Option Menu to display the Search Catalog panel. Enter the name of the dataset that owns the tape volume you want to manage, enter a 'V' in Level and press ENTER to display the Manage Versions panel.
Purging a Tape Volume Managing Tapes Purging a Tape Volume Introduction You can purge a tape volume from the DSN Catalog by using the Manage Tape Volumes panel. Access Choose M (for MANAGE) on the Primary Option Menu to display the Search Catalog panel. Enter the name of the dataset that owns the tape volume you want to manage, enter a 'V' in Level and press ENTER to display the Manage Versions panel.
Managing Tapes Recording Tape Cleaning Recording Tape Cleaning Introduction You can record tape cleaning using either the Tape Volume Information or Manage Tape Volumes panels. Access Choose M (for MANAGE) on the Primary Option Menu to display the Search Catalog panel. Enter the name of the dataset that owns the tape volume you want to manage, enter a 'V' in Level and press ENTER to display the Manage Versions panel.
Understanding Retention Concepts Retention and Scratching Retention and Scratching Understanding Retention Concepts Introduction Retention is how long a dataset is kept before it can be discarded. Retention is one of the most critical areas of information control. Scratching, or making a tape available for reuse, is the physical storage consequence of the expiration of a tape dataset’s retention.
Retention and Scratching Setting Dataset Definition Retention Setting Dataset Definition Retention Introduction When a dataset definition is created manually using the Define an EDD panel, a new set of retention criteria is defined which will apply to all future versions of that dataset. Access Select D (for DEFINE) from the Primary Option Menu to display the Define an EDD panel. Define an EDD Panel TSIO0103.
Modifying Dataset Definition Retention Retention and Scratching Modifying Dataset Definition Retention Introduction When an existing dataset definition is modified using the Update an EDD panel, the existing retention criteria can be changed. The changes will apply to all subsequent versions of that dataset. Access Select M (for MANAGE) from the Primary Option Menu to display the Search Catalog panel. After you have entered your search criteria, press ENTER to display the Manage EDDs panel.
Retention and Scratching Setting or Modifying Dataset Version Retention Setting or Modifying Dataset Version Retention Introduction Use the Retain a Version panel to set or modify the expiration date, creation date, and creation job name of a version. If the version is not in active status, it is put in active status automatically. Access From the Manage Versions panel, place an H (for Retain) next to a dataset name and press ENTER.
Cycling a Dataset Version Retention and Scratching Cycling a Dataset Version Introduction Cycling is a special purpose function for overriding the number of versions (cycles) retained for a dataset. Use it to take one version out of the normal retention cycle and reserve it for special retention.
Retention and Scratching Cycle a Version Panel Cycling a Dataset Version TSIO0211.
Scratching a Dataset Version Retention and Scratching Scratching a Dataset Version Introduction There are several different status types that affect when a dataset version becomes eligible for scratch. Datasets in open status are eligible for scratch only after they have been closed with the Online Manager. All other versions are eligible for scratch only after all of the retention criteria specified for the dataset version has been satisfied.
3 DSN Catalog Management Utility BIM-EPIC provides the TSIDMNT utility program for managing the DSN Catalog. The same functions can also be performed using the BIM-EPIC Online Manager. Chapter Contents Command Summary.......................................................................................................3-3 BIM-EPIC System Requirements...................................................................................3-4 BIM-EPIC Requirements..................................................
SCRATCH ...............................................................................................................3-39 TRANSFER .............................................................................................................3-41 UNLOCK.................................................................................................................3-42 UPDATE .................................................................................................................
Command Summary Command Summary Command Function ADD Add a version of a controlled dataset to the DSN Catalog CAPACITY Display DSN Catalog utilization statistics CATALOG Define a new EDD in the DSN Catalog (in Online Manager, use the DEFINE command) CLEAN Reset tape usage, error counts, and clean date CLOSE Change a version’s status from “open” or “conditionally cataloged” to “active” CYCLE Override the cycle control of a dataset DELETE Remove a dataset and all of its versions from the DSN C
BIM-EPIC Requirements BIM-EPIC System Requirements BIM-EPIC System Requirements BIM-EPIC Requirements JCL Requirements TSIDMNT is designed for use within production job streams, to scratch datasets as necessary and perform other periodic catalog management such as MCATALOG or CYCLE. TSIDMNT functions are submitted as shown below: [// OPTION LOG] // EXEC TSIDMNT control-statements . . /* Print Options 3-4 User Reference Print output is controlled using the JCL LOG option.
BIM-EPIC System Requirements CA-EPIC for CMS Requirements CA-EPIC for CMS Requirements In order to use TSICMNT commands in CA-EPIC for CMS, link to the minidisk containing CA-EPIC for CMS user programs (for example, TSICSERV 191), and issue the following command: GLOBAL TXTLIB TSICTXT Chapter 3.
Command Syntax TSIDMNT Commands TSIDMNT Commands Command Syntax Description TSIDMNT functions follow this syntax: command [ 'dataset-name' ] [ parameter-expressions ] The command must always be first. It can be specified in full or abbreviated to its first three letters. For example, you can use either DISPLAY or DIS for the DISPLAY command. dataset-name is positional. When used, it must always follow the command and be enclosed in apostrophes.
TSIDMNT Commands PASSWORD PASSWORD Description If your installation has used the PASSWD configuration option to invoke DSN Catalog update protection, you must use the PASSWORD command to enter the required password. The DSN Catalog password is required for all commands except the following: • • • • CAPACITY DISPLAY HELP PASSWORD Submit the PASSWORD statement before any protected operation. The password is not printed on SYSLST if the command name (PASSWORD or PAS) begins in column 1.
ADD TSIDMNT Commands ADD Description Use the ADD command to add a new version to a controlled dataset. To create a new BIMEPIC dataset definition (EDD) for a previously uncontrolled dataset, use the CATALOG command. ADD can be used to add a new version that was created outside BIM-EPIC control or to recatalog a deleted version. Once a dataset is controlled, all new versions created under BIMEPIC are added to the DSN Catalog automatically. BIM-EPIC resequences version numbers as you add new versions.
TSIDMNT Commands ADD Parameters ADD Parameter Valid Entry Default 1 to 44 characters None SER (or ESER) 1 to 6 characters None VOL (or EVOL) 1 to 6 characters None VER 1 to 999 1 GEN 1 to 999999 None dataset-name Required? Yes Specify only one of the following two (required): Specify only one of the following two (optional): Descriptions FIL No 2 to 255 None BLK No 1 to 65535|MAX|OPT None OFL No 1 None dataset-name specifies the name of the dataset to which the new versi
ADD TSIDMNT Commands example, if the highest current generation number (usually version 1) is 000120, specify a new generation number of 000122 or greater. The new version is always version 1. FIL specifies the file sequence number if this version of a tape dataset is not the first dataset in a multi–dataset group. BLK specifies the block size of this version of the dataset, if you wish. MAX sets the block size to track capacity for disk datasets and for tape datasets - 64K for VSE/ESA 2.
TSIDMNT Commands CAPACITY CAPACITY Description Use the CAPACITY control statement to display DSN Catalog usage. This is displayed as both the number of active/free records, and as a percentage. Syntax CAPACITY Results The following is an example of the CAPACITY display. (no parameters) EP119 TOTAL EP119 CAPACITY EP119 4560 CATALOG UTILIZATION ACTIVE FREE PCT 959 3601 21 INDEX UTILIZATION ACTIVE FREE PCT 560 4000 12 Chapter 3.
CATALOG TSIDMNT Commands CATALOG Description Use the CATALOG command to create a new BIM-EPIC dataset definition (EDD) in the DSN Catalog, and to define the attributes to be associated with that dataset name. After the EDD has been created, you can catalog versions of the dataset with the ADD command.
TSIDMNT Commands General Parameters Descriptions CATALOG Parameter Required? Valid Entry Default dataset-name Yes 1 to 44 characters None BLK No NO|1 to 65535|MAX|OPT NO COM No 1 to 30 characters None COP No 1 to 44 characters None CYC No 0 to 999 None DLA No 1 to 9999 None PWD No 1 to 8 characters NO RET No 1 to 9999|PERM None SID No NO|2 characters NO SYSnnn No 000 to 253 000 UID No NO|2 characters NO WRK No YES|NO NO dataset-name is used to locate a
CATALOG TSIDMNT Commands RET specifies the number of days to retain the dataset after its creation date. CYC specifies the number of cycles (versions) to retain. DLA specifies the number of days to retain the dataset after its last access date. WRK specifies whether this is a generation dataset (WRK=NO) or a non–generation dataset (WRK=YES). SID and UID (VSE Only) can be used to group your dataset with other datasets for catalog functions. If you specify NO, the ID is inactive.
TSIDMNT Commands CATALOG The following densities are supported for 3424/9348 devices: 42 62 C2 E2 Buffered write mode 1600 bpi Unbuffered write mode 1600 bpi Buffered write mode 6250 bpi Unbuffered write mode 6250 bpi The following densities are supported for 3410/3420/3422/3430 devices: D0 6250 bpi C0 1600 bpi C8 800 bpi The following densities are supported for 3490E devices: F0 Buffered write mode (3490E) F8 Buffered write mode with IDRC (3490E) Modes F0 and F8 are used internally by BIM-EPIC to dist
CATALOG Disk Parameters TSIDMNT Commands Disk information is only meaningful to BIM-EPIC, but it can be updated from CA-EPIC for CMS. Parameter Required? Valid Entry Default AGP No Yes or NO NO ALR No 1 to 99999 None CIZ No NO|512 to 32768 None EXT No 1 to 999999 DEFEXT EX2 No 0 to 999999 50% of primary POL No 1 to 6 characters None SEC No 0 to 255 255 AGP specifies whether dataset retention is controlled by the Automatic Generation Purge feature.
TSIDMNT Commands CATALOG The following example catalogs the BALANCE.BUDGET dataset, with day retention of 3 and days last accessed retention of 3. Disk datasets are written in disk pool POOLA1 with a primary extent size of 20 and a maximum of 3 secondary extents. CAT 'BALANCE.BUDGET',RET=3,DLA=3,POL=POOLA1,EXT=20,SEC=3 The following example results in BIM-EPIC retaining three versions of the BALANCE.BUDGET dataset at all times.
CLEAN TSIDMNT Commands CLEAN Description Use the CLEAN command to record tape cleaning. CLEAN sets the use and error counts for cleaned tapes to zero. Syntax CLEAN Parameters SER=volser1,volser2,... Parameter volsern Required? Yes Valid Entry Default 1 to 6 characters None SER specifies the volume serial numbers of the cleaned tapes.
TSIDMNT Commands CLOSE CLOSE Description BIM-EPIC only accesses active versions of a dataset. Datasets that are in “open” or “conditionally cataloged” status cannot be processed, and they become eligible for scratch differently from active versions. To access or save an open or conditionally cataloged dataset, you must close it with the CLOSE command. CLOSE only changes the DSN Catalog status of a version. It does not perform close processing, such as writing tape or disk labels.
CYCLE TSIDMNT Commands CYCLE Description The CYCLE command is a special purpose command for overriding the normal Cycles Retention (CYC) of a dataset. The CYCLE command causes one version to be removed from the Cycles Retention and reserved for special retention. For example, you might use it to isolate the correct balance sheet from a series of trial balance runs. CYCLE looks very similar to the RETAIN command. However, its effect is quite different. Using RETAIN only affects the version you modify.
TSIDMNT Commands Parameters CYCLE Parameter dataset-name Required? Yes Valid Entry Default 1 to 44 characters None Specify only one of the following three (required): VER 1 to 999 None SER 1 to 6 characters None GEN 1 to 999999 None Specify at least one of the following parameters (required): EXD 1900001 to 2099366 None DAY 1 to 999 None CDT 1900001 to 2099366 None JOB 1 to 8 characters None dataset-name specifies the dataset name.
DELETE TSIDMNT Commands DELETE Description Use the DELETE command to remove a dataset and all its versions from the DSN Catalog and from BIM-EPIC control. The BIM-EPIC dataset definition (EDD) is deleted. All tapes associated with the dataset become scratch tapes and are listed under the dataset name ‘** DSN DELETED **’ on BIM-EPIC reports and in Online Manager displays. Disk space allocated to the dataset is freed.
TSIDMNT Commands DEQ DEQ Description Use DEQ to dequeue the BIM-EPIC DSN Catalog after it has been enqueued with the ENQ command. In CA-EPIC for CMS, this command is only meaningful when sharing a BIM-EPIC DSN Catalog. Syntax DEQ (no parameters) Chapter 3.
DISPLAY TSIDMNT Commands DISPLAY Description Use the DISPLAY command to display entries in the DSN Catalog. The display lists all cataloged information about the dataset and each of its versions. The summary display contains one line of data for each version of each dataset. If a version resides on multiple volumes, each volume has its own line in the display. Scratched tape versions continue to be displayed until their tapes are used to write other datasets.
TSIDMNT Commands Parameters DISPLAY Parameter Required? Valid Entry Default Specify one of the following four (required): dataset-name 1 to 44 characters None SER 1 to 6 characters None ALL ALL None string.
DISPLAY Secondary Parameters TSIDMNT Commands The following parameters are valid with the ALL and string.ALL parameters. ACTIVE displays only active versions. DSK displays only disk versions. DSN displays dataset names only (omits dataset summaries). JOB displays the latest version of all datasets that were created by the specified jobname. It also displays any OPEN or conditionally cataloged datasets created by that job since the latest version was created.
TSIDMNT Commands ENQ ENQ Description Use ENQ to enqueue the BIM-EPIC DSN Catalog and prevent access to it by jobs running in other partitions or CPUs. To enqueue a DSN Catalog that is shared by two or more CPUs, MULTCPU=YES must be specified as a configuration option. In CA-EPIC for CMS, this command is only meaningful when sharing a BIM-EPIC DSN Catalog. Syntax ENQ (no parameters) Chapter 3.
LOCK TSIDMNT Commands LOCK Description Use the LOCK command to lock a dataset or version. If you do not specify a version, volume serial number, or generation number, the EDD is locked for output, which means that BIM-EPIC does not permit additional versions to be created until you release or unlock it. If you do specify a version, volume serial number, or generation number, only that version of the dataset is locked for input, which means that it cannot be read until you release or unlock it.
TSIDMNT Commands MCATALOG MCATALOG Description Use the MCATALOG command to specify that a tape dataset can be accessed by more than one dataset name. The new dataset names are known as MCAT aliases. After a version has been MCATALOGed, it is accessible by both its original dataset name and its MCAT alias(es). The dataset is retained until all retention criteria from all associated BIM-EPIC dataset definitions (EDDs) have been satisfied.
MOVE TSIDMNT Commands MOVE Description Use the MOVE command to change the vault and slot location of a tape volume. If an Automated Cartridge Library (ACL) is supported and the tape is moved from the main vault (Vault 0), the volume is ejected from the ACL at the time the MOVE statement is processed. WARNING! Vaulting reports do not reflect changes specified by MOVE commands.
TSIDMNT Commands OFFLINE (VSE Only) OFFLINE (VSE Only) Description Use the OFFLINE command to prevent a disk volume from being accessed by BIM-EPIC if you must dismount the volume or “device down” the drive. Once a volume is in OFFLINE status, BIM-EPIC will not use it to allocate either output or input datasets. OFFLINE cannot disable volume access across machines, so you must issue the OFFLINE command from all machines that have access to the device.
ONLINE (VSE Only) TSIDMNT Commands ONLINE (VSE Only) Description Use the ONLINE command to enable BIM-EPIC to access a disk volume for both input and output datasets. If a disk volume has been placed in OFFLINE or QUIESCE status, use ONLINE to restore access to the volume. ONLINE cannot enable a volume across machines, so you must use the ONLINE command in all machines in which the OFFLINE command was used for the volume. See OFFLINE and QUIESCE.
TSIDMNT Commands PURGE PURGE Description Use the PURGE command to remove BIM-EPIC dataset definitions (EDDs), versions, and tape volume serial numbers from the DSN Catalog. With PURGE, you can delete an entire dataset and all its versions (tape and disk) or simply remove a tape volume and the versions it contains. Datasets which are part of a multi–dataset group cannot be purged until all other datasets in the group are scratched or deleted.
QUIESCE (VSE Only) TSIDMNT Commands QUIESCE (VSE Only) Description QUIESCE makes disk volumes ineligible for the creation of controlled datasets. BIM-EPIC will not allocate output datasets on a volume that has been quiesced. Quiesced volumes are still eligible for BIM-EPIC input processing and for uncontrolled processing. QUIESCE cannot disable a volume across machines, so you must use QUIESCE on all machines that have access to the volume. Use the ONLINE command to remove a volume from quiesced status.
TSIDMNT Commands RELEASE RELEASE Description Use the RELEASE command to unlock, for one use only, EDDs or versions that have been placed in LOCK status (the UNLOCK command allows unlimited access). If you do not indicate a specific version, the EDD is released for one use as output, so that you can create one more version of the dataset. The new version is placed in locked status automatically.
RENAME TSIDMNT Commands RENAME Description The RENAME command allows you to change the name of a cataloged dataset. All existing versions of the original dataset are referenced by the new dataset name, and all dataset characteristics remain the same. If the dataset is a disk dataset, its VTOC entries are also renamed. WARNING! Do not rename prime datasets or offload datasets. Results are unpredictable.
TSIDMNT Commands RETAIN RETAIN Description Use the RETAIN command to alter a version's expiration date, creation date, or creation job name. If the version is not in active status, it is put in active status automatically. If an Automated Cartridge Library (ACL) is supported, RETAIN sets the tape volume to “non–scratch” status in the ACL inventory. RETAIN also changes the status of a version from scratch, open or conditional catalog to active status.
RETAIN Examples TSIDMNT Commands The following example retains version 3 of the AGED.TRIAL.BALANCE dataset. Version 3 is closed and is retained for seven days from today, and its creating job name is changed to TRIALBAL. RETAIN 'AGED.TRIAL.BALANCE',VER=3,DAY=7,JOB=TRIALBAL The following example retains the version of PAYROLL.UNEDITED.TRANSACTIONS which starts on volume PR5867. The version is closed and expires on November 23, 1997. RET 'PAYROLL.UNEDITED.
TSIDMNT Commands SCRATCH SCRATCH Description Use the SCRATCH command to scratch a version of a dataset. The version must be in active status to be scratched. If it is in open or conditionally cataloged status, you must first use the CLOSE command to make it active. If an Automated Cartridge Library (ACL) is supported, SCRATCH sets the tape volume to “scratch” status in the ACL inventory.
SCRATCH TSIDMNT Commands FOR specifies that the disk volume on which a dataset resides is no longer available and the entry is to be removed from the catalog . Scratching by volume serial number is not valid for NSU subdatasets or MCAT aliases. Examples The following example scratches version 1 of the INVENTRY.SANDIEGO.3847 dataset. SCRATCH 'INVENTRY.SANDIEGO.3847',VER=1 The following example scratches the version of the INVENTRY.SANDIEGO.3847 dataset which starts on volume IN4658. SCR 'INVENTRY.
TSIDMNT Commands TRANSFER TRANSFER Description Use the TRANSFER command to move a version from one dataset to another. The version transferred is no longer associated with its original dataset name. A transferred version retains all of its original characteristics, except for version number. VSE Only: If the version is a disk dataset, the associated VTOC entry is also renamed.
UNLOCK TSIDMNT Commands UNLOCK Description Use the UNLOCK command to permanently unlock a locked dataset or version. To unlock a dataset or version for one use only, use the RELEASE command instead. Use of UNLOCK requires prior use of the LOCK command. To permit unlimited access to a specific version, use UNLOCK with a version qualifier. To permit creation of an unlimited number of new versions, use UNLOCK without a version qualifier.
TSIDMNT Commands UPDATE UPDATE Description Use UPDATE to change the characteristics associated with an EDD in the DSN Catalog. The updated characteristics will only affect versions created after the update. To update previously created versions, use CLOSE, CYCLE, or RETAIN. The parameters available on the UPDATE command are nearly identical to the CATALOG command parameters. However, the prime dataset name and encryption password parameters cannot be updated once the dataset is cataloged.
UPDATE 3-44 User Reference TSIDMNT Commands
4 Accessing the DSN Catalog This chapter discusses several ways to access the DSN Catalog. Chapter Contents Displaying DSN Catalog Entries (TSIDUTL DSPLY) ..................................................4-2 Accessing DSN Catalog Records (TSIDAC2) ...............................................................4-5 ADDRESS EPIC..........................................................................................................
Displaying DSN Catalog Entries (TSIDUTL DSPLY) Displaying DSN Catalog Entries (TSIDUTL DSPLY) Description The DSPLY command creates reports from the data maintained in the DSN Catalog. Reports can be created displaying data associated with all the datasets, all the version entries, specific datasets, or specific versions which match specified criteria. These reports can also be produced in different sort sequences. DSPLY produces reports listing all datasets or groups of datasets in the DSN Catalog.
Displaying DSN Catalog Entries (TSIDUTL DSPLY) NEW reports dataset versions created since the last time the DSPLY NEW report was run. NEW can be used to track the datasets created within a given time frame. NEW updates the catalog so that at the next run it can distinguish the new datasets. If you do not want the update, execute TSIDUTL with UPSI xxx1x. PULL reports the latest version of all datasets. PULL,DSN=‘dataset-name’ reports the latest version of the named dataset. SCRATCH reports scratch tapes.
Displaying DSN Catalog Entries (TSIDUTL DSPLY) Examples The following job produces a report listing all datasets belonging to the System ID TS and the User ID MR. They are listed in the order they are found in the catalog's index. // JOB DISPLAY DSN CATALOG // EXEC TSIDUTL DSPLY ALL,SYSID=TS,USERID=MR /* /& The following job produce a report listing all vaulted tapes. Tapes are listed in dataset name sequence within the vault. // JOB DISPLAY DSN CATALOG // ASSGN SYS001,150 // DLBL SORTWK1,'===.
Accessing DSN Catalog Records (TSIDAC2) Accessing DSN Catalog Records (TSIDAC2) Description You may want to access DSN Catalog information with your own programs to produce your own reports or for other reasons. The TSIDAC2 subroutine is provided for this purpose and is located in the BIM-EPIC installation library as member name TSIDAC2.OBJ.. A sample COBOL program (TSIDACC2) is located in the BIM-EPIC installation library as member name TSIDACC2.C.
TSIDAC2 Calling Procedure Accessing DSN Catalog Records (TSIDAC2) TSIDAC2 Calling Procedure Description TSIDAC2 returns DSN Catalog information for any program language or report writer. TSIDAC2 is a relocatable module in the BIM-EPIC installation library. The library that contains TSIDAC2 must be available when you catalog your calling program. The procedure for using the TSIDAC2 subroutine is: Step 1 Define the storage area to be used for the parameter list during a TSIDAC2 call.
Accessing DSN Catalog Records (TSIDAC2) TSIDAC2 Calling Procedure Data is returned only if the return code is 0. Example This is an example of the COBOL coding that can be used to invoke the TSIDAC2 subroutine. WORKING-STORAGE SECTION. 01 ACC-RECORD COPY TSIDAC2. PROCEDURE DIVISION. MOVE (search argument) TO USR-KEY. CALL 'TSIDAC2' USING ACC-RECORD. IF USER-RETURN-OK GO TO PROCESS-THE-RECORD. IF USER-RETURN-EOF GO TO END-OF-FILE. IF USER-RETURN-NOT-ACTIVE GO TO SYSTEM-DOWN.
TSIDAC2 Search Arguments and Calls Accessing DSN Catalog Records (TSIDAC2) TSIDAC2 Search Arguments and Calls Description The following pages detail the specific procedures necessary to gain different types of access to the DSN Catalog using TSIDAC2. Implement these procedures as steps 2 and 3 of the procedure outlined in the previous section. For the sake of discussion, we use the COBOL copybook (TSIDAC2.C) to name the data fields described in this section, and all examples are coded in COBOL.
Accessing DSN Catalog Records (TSIDAC2) TSIDAC2 Search Arguments and Calls . . MOVE HEX02 TO USR-KEY-POS-1. MOVE 'EP3452' TO USR-KEY-SER. CALL 'TSIDAC2' USING ACC-RECORD. . . . Sequential Access To read the entire DSN Catalog sequentially: 1. 2. Example Move spaces to the USR-KEY field. Issue multiple calls to TSIDAC2. PROCEDURE DIVISION. . . . SEQUENTIAL-READ. MOVE SPACES TO USR-KEY. CALL 'TSIDAC2' USING ACC-RECORD. IF USER-RETURN_CODE = 1 GO TO END-OF-CATALOG.
TSIDAC2 Search Arguments and Calls Accessing DSN Catalog Records (TSIDAC2) Example PROCEDURE DIVISION. . . . MOVE HIGH-VALUES TO USR-KEY. CALL 'TSIDAC2' USING ACC-RECORD. . . . Releasing GETVIS The first time TSIDAC2 is called, it acquires partition GETVIS storage for various purposes. If you want to release this storage: 1. 2. Example 4-10 User Reference Move low-values (hex 00) to USR-KEY. Call TSIDAC2. PROCEDURE DIVISION. . . . MOVE LOW-VALUES TO USR-KEY. CALL 'TSIDAC2' USING DSN-RECORD. . . .
ADDRESS EPIC ADDRESS EPIC Description Return Codes Command Forms The ADDRESS EPIC command provides an interface to BIM-EPIC from BIM's Global Subsystem (BIM-GSS) product.
ADDRESS EPIC In the following examples, REXX coding rules apply, that is, if an argument is a literal, it is within quote marks; if it is a variable it is outside the quote marks. Two examples: ADDRESS EPIC ‘EXTRACT DSN ID’ ii ‘STEM n. COUNT’ c ‘SKIP’ s ADDRESS EPIC ‘EXTRACT DSN ID’ ii ‘STEM n. COUNT 5 SKIP 8’ The following form returns the master record for all datasets in the BIM-EPIC catalog. The stem n.0 indicates the total number of records returned as stem variables. If n.
5 BIM-EPIC TLBL and DLBL Statements This chapter describes BIM-EPIC’s TLBL and DLBL statements. BIM-EPIC TLBL statements are slightly different from VSE TLBLs and provide additional options. BIM-EPIC DLBL statements have the same format as VSE DLBLs and also provide additional options. BIM-EPIC provides an MVS-style DD statement for VSE. See 6-1 in this manual for further information. Each type of BIM-EPIC label statement provides its own benefits.
TLBL Statements TLBL Statements Introduction BIM-EPIC provides modifications to the standard VSE TLBL statement. Similarities and differences are shown in the table below. All TLBL fields are positional.
TLBL Statements dtfname dtfname specifies the symbolic name that the program uses for the dataset, for example TAPEIN and SORTIN. IBM calls this field the filename. Dataset Name Field The dataset name field consists of dataset-name and any desired alpha-opts. A beginning and ending apostrophe are required. This parameter is required for output. For input, the dataset name field can be omitted and a volume serial number supplied instead.
TLBL Statements C0 1600 bpi C8 800 bpi The following densities are supported for 3490E devices: F0 Buffered write mode (3490E) F8 Buffered write mode with IDRC (3490E) Modes F0 and F8 are used internally by BIM-EPIC to distinguish 3490E tape cartridge drives from 3480/3490. Because VSE/ESA does not support these modes directly, BIM-EPIC sends mode 00 or 08 to the 3490E hardware whenever modes F0 or F8 are specified. retention retention specifies the number of days to retain this version.
TLBL Statements Examples In the following example, BIM-EPIC selects the tape volume BACKUP.STR (version 1) from the DSN Catalog. // TLBL TAPEIN,'BACKUP.STR' In the following example, BIM-EPIC selects the BACKUP.STR (version 3) from the DSN Catalog. // TLBL TAPEIN,'BACKUP.STR,(-2)' In the following example, BIM-EPIC honors the request for volume EP6173. // TLBL TAPEIN,,,EP6173 In the following example, BIM-EPIC selects BACKUP.STR, and specifies "Rewind and unload at close" and mode '08'.
TLBL Options TLBL Statements TLBL Options Description TLBL option codes provide special BIM-EPIC processing that is unavailable with standard VSE TLBL parameters. See “TLBL Statements” above for instructions and restrictions on specifying parameters. Alphabetic option codes (called alpha options) are provided for compatibility with other tape management products. Alpha options can only be specified within the TLBL dataset name field.
TLBL Statements TLBL Options 2 or U (Unload) Rewinds and unloads the tape at close. 3 (Do not rewind) Prevents rewinding the tape at close. Use this option when you are creating multi-dataset tapes. 4 or R (Scratch at close) Scratches the dataset when it is closed as input. This option does not affect subdatasets. 8 or H (Hold the drive assignment at close) Prevents BIM-EPIC from releasing the tape drive at close. If Autoattach is on, it also prevents the drive from being detached.
DLBL Statements DLBL Statements Description The BIM-EPIC DLBL statement is identical to the VSE DLBL statement, with additional options provided for special BIM-EPIC processing. BIM-EPIC DLBL options are specified within the file-id (dataset-name) parameter, beginning after the dataset name itself and ending with the closing apostrophe ('). Options must be separated from the dataset name, and from each other, by a comma. The options(s) specified must be enclosed in parentheses.
DLBL Statements Option Codes Code A B=n Action Align allocation on cylinder boundaries Reblock (n=1 to 32767|MAX|OPT) C Conditionally catalog D Delete after closed as input E Concatenate datasets F Allow fragmentation G=n Access the specified generation (n=1 to 65535) H Prevent automatic fragmentation I Ignore this dataset L Inhibit LUB allocation M Issue messages open/close N Bypass truncation O Use extent size in EXTENT statement P Delete (Purge) at End of Job (non-generation fi
DLBL Options DLBL Statements DLBL Options A Aligns the disk allocation on cylinder boundaries. Valid for CKD devices only. Allocations for direct access (DA) and ISAM datasets are aligned automatically. B=xxx Changes the block size of your datasets without recompiling your programs. Valid for datasets with either fixed or variable record formats. Reblock with caution when running programs that use physical IOCS; such programs must be able to support reblocking.
DLBL Statements DLBL Options I Overrides BIM-EPIC's control of dataset. Valid ASSGN and EXTENT statements must be included to process the dataset. L Inhibits LUB allocation for the dataset. Inhibiting LUB allocation is often necessary when you are running programs that use physical IOCS. It is required with the BIM-EPIC TSIDASS utility. See "LUB allocation" for more information. M Overrides configuration options ALLMALL=NO (default) and ALLMSG=NO for this dataset.
DLBL Options DLBL Statements S The next version of the dataset is to be written in the same extent space the current version occupies. This option is useful when you want to create datasets under a fixed head for better performance. This option affects single extent non-generation datasets only. When you use this option, you must also inhibit truncation (option 'N') for the dataset. T Deletes the label information for this dataset from the label area (not from the VTOC) when the dataset is closed.
6 BIM-EPIC DD Statements The BIM-EPIC DD statement is an MVS-style dataset label for VSE installations. For many users, its primary benefit is compatibility with MVS, because it simplifies moving JCL between the two operating systems. The DD statement also offers several options which are unavailable with standard VSE labels, even when using BIM-EPIC TLBL and DLBL options. Chapter Contents Specifying the DD Statement .........................................................................................
Introduction Specifying the DD Statement Specifying the DD Statement Introduction DD Statement Identifier (* //) All DD statements follow the same format. The identifying characters are '* //', which must be specified in columns 1-4. These are followed immediately by the DD name. Format * //ddname DD Name ddname performs the same function as the DTF name (filename). It specifies the program's logical name for the dataset. It must begin in column 5.
Specifying the DD Statement DD Statement Syntax DD Statement Syntax Specifying Parentheses and Commas You can specify multiple parameters after the DD operation. Some parameters have multiple subparameters. Separate multiple parameters and subparameters with commas. Enclose multiple subparameters in parentheses. Many subparameters are positional. If you omit a subparameter, a comma must be specified in the omitted position for all but the last subparameter, just as in VSE and MVS.
DD Statement Syntax Specifying the DD Statement Example * //TAPEIN * //TAPEIN * //TAPEIN DD DD DD Concatenating Datasets BIM-EPIC concatenates all versions of a single input dataset automatically, as does MVS. If you do not specify a single version on input, all versions are read sequentially, beginning with the current version. Example * //TAPEIN DD DSN=INVENTRY.1QTR(0),DISP=(OLD,KEEP) DSN=INVENTRY.2QTR(0),DISP=(OLD,KEEP) DSN=INVENTRY.3QTR(0),DISP=(OLD,KEEP) DSN=INVENTRY.
Specifying the DD Statement Special DD Names Special DD Names Description Many ddnames have special purposes in MVS. This affects how the BIM-EPIC DD facility processes them. Unsupported DD Names Statements containing unsupported ddnames are ignored by the BIM-EPIC DD system and treated as comments by VSE. Use standard VSE JCL to define datasets processed with these names.
Special DD Names SYSABEND, SYSUDUMP, and SYSMDUMP Specifying the DD Statement SYSABEND, SYSUDUMP, and SYSMDUMP determine the kind of dump to be generated when a job cancels. They are similar to the DUMP and PARTDUMP parameters of the VSE OPTION statement. SYSABEND and SYSUDUMP specify a standard partition dump. SYSMDUMP specifies a full supervisor and partition dump. The SYSOUT parameter must be specified with the SYSABEND, SYSUDUMP, and SYSMDUMP ddnames. SYSOUT identifies a print class in MVS.
DD Statements for Tape and Disk Datasets Introduction to the Parameters DD Statements for Tape and Disk Datasets Introduction to the Parameters In this section, we present a brief guide to the parameters and their purposes. Following this section, each parameter is examined in detail in a section of its own. Those sections are arranged in alphabetical order for quick reference.
Introduction to the Parameters DD Statements for Tape and Disk Datasets You can also request CPU and partition independence or common work dataset support with the DSN parameter (these options are not available with MVS). FREE The FREE parameter specifies how tape drive assignments are to be handled when the dataset is closed. When doing multi-dataset processing, use FREE to hold the assignment until all datasets have been processed. FREE is only valid for tape datasets.
DD Statements for Tape and Disk Datasets What to do for Different Types of Datasets What to do for Different Types of Datasets This section describes the particular DD parameters to use when you are processing different kinds of datasets. Tape For tape processing, pay particular attention to the VOLUME, FREE, and DISP parameters. VOLUME has several uses for tape. FREE holds and releases tape drive assignments. DISP=(x,KEEP) unloads tapes at close. By default a tape is rewound at close, but left mounted.
What to do for Different Types of Datasets DD Statements for Tape and Disk Datasets The following example shows a new, uncataloged dataset. It is automatically cataloged, and the specified values for block size, period retention and density are entered in the dataset definition. * //TAPEOUT * // DD DSN=SARS.
DD Statements for Tape and Disk Datasets What to do for Different Types of Datasets VSAM You can use existing VSAM datasets using BIM-EPIC DD statements. To process an already existing VSAM dataset, include the AMP parameter in your statement. Define the VSAM catalog with a STEPCAT or JOBCAT DD statement. Example * //JOBCAT DD * //VSAMCLU DD DSN=CUSTOMER.CAT,DISP=SHR DSN=CUSTOMER.MASTER,DISP=SHR,AMP=AMORG Chapter 6.
AMP Parameter DD Statements for Tape and Disk Datasets AMP Parameter Description Use the AMP parameter to define a VSAM cluster or a VSAM/SAM dataset. Syntax AMP=(AMORG [ ,BUFSP=x ]) Subparameters Subparameter Required? Valid Default AMORG Yes None None BUFSP No 0 to 9999999 None AMORG specifies that this is a VSAM cluster or VSAM/SAM dataset. BUFSP specifies the number of bytes to be allocated as buffer space. If omitted, VSAM will determine the size of the buffer.
DD Statements for Tape and Disk Datasets DCB Parameter DCB Parameter Description Use the DCB parameter to define the characteristics of your dataset. It overrides the DSN Catalog entry on output, but not on input.
DCB Parameter DD Statements for Tape and Disk Datasets Specifies a recording density.
DD Statements for Tape and Disk Datasets DISP Parameter DISP Parameter Description DISP identifies how a dataset is to be opened and what is to be done to the dataset when it is closed. DISP subparameters define the usage, normal termination and abnormal termination disposition of a dataset. If more than one subparameter is used, the subparameter list must be enclosed in parentheses.
DISP Parameter DD Statements for Tape and Disk Datasets • • DELETE KEEP If abnormal-end-status is used without both usage-status and normal-end status, normal-end status will be used for abnormal-end-status.
DD Statements for Tape and Disk Datasets Normal Termination Subparameters Normal Termination Subparameters DELETE Causes datasets to be scratched automatically after they have been used. Based upon the dataset usage, the scratching may be done at close, end of step (EOS) or at end of job (EOJ). Several factors determine when and if the DELETE disposition will be effective or bypassed. The factors are: • • • work vs.
Deleting Datasets Using DDGEN and the DISP Parameter DD Statements for Tape and Disk Datasets Deleting Datasets Using DDGEN and the DISP Parameter Description The DDGEN configuration option controls when a dataset is to be deleted based upon its DISP DD parameter. The table belows shows when deletion occurs based upon the possible DDGEN and DISP combinations. Where there is no entry in the table, no deletion occurs. For simplicity, the table below descibes the basic DISP combinations.
DD Statements for Tape and Disk Datasets Deleting Datasets Using DDGEN and the DISP Parameter NOTE 1 DISP=(OLD,KEEP) and DISP=(OLD,KEEP,KEEP) will automatically reset any delete at end-of-step or delete at end-of-job action currently in effect for the the specified dataset NOTE 2 Normal deletion will occur at file close but, when used in conjunction with the automatic concatenation feature, deletion will occur at end-of-step. If usage is MOD, deletion will occur at end-of-job.
Deleting Datasets Using DDGEN and the DISP Parameter DD Statements for Tape and Disk Datasets disk dataset; in that case the disk dataset will be cataloged as a generation dataset. If the startup option DDGEN is set to YES, tape and disk datasets will both be automatically cataloged as non-generation datasets unless a plus sign (+) is found in the DSN parameter. See the DDGEN configuration option in the BIM-EPIC Installation and System Guide for more information.
DD Statements for Tape and Disk Datasets Abnormal Termination Subparameters Abnormal Termination Subparameters Description The default disposition for abnormal termination depends on both the normal termination subparameter and the PURBYP configuration option. KEEP and CATLG Retain the dataset if the job cancels. The abnormal termination disposition is KEEP unless both of the following are true: • • Normal termination disposition is DELETE PURBYP is set to NO Chapter 6.
DSN Parameter DD Statements for Tape and Disk Datasets DSN Parameter Description The DSN parameter specifies the name of the dataset being processed. It is required for all tape and disk datasets. It also determines which version or versions of the dataset will be used for input. The rules for dataset names with DD statements are slightly different from those with standard VSE JCL. Both tape and disk dataset names can be up to 44 characters long. Generation dataset names are limited to 35 characters.
DD Statements for Tape and Disk Datasets DSN Parameter For compatibility with MVS, the current version is indicated by a zero instead of a one as in the DSN Catalog. That means that when you enter a version number with a minus sign, it should be one less than the version number displayed in the DSN Catalog. For example, if the version number in the DSN Catalog is 3, specify DSN=dataset-name(-2). Also note that specifying '(+n)' is not necessary for output datasets.
FREE Parameter DD Statements for Tape and Disk Datasets FREE Parameter Specifies when a tape drive assignment is to be released. FREE is valid for tape datasets only. If FREE is not specified, the assignment is released when the dataset is closed. When you are processing multi-dataset tapes, you must specify FREE=END for every dataset except the last one processed in the job. Syntax CLOSE FREE={ END } Values CLOSE releases the assignment when the dataset is closed. This is the default.
DD Statements for Tape and Disk Datasets LABEL Parameter LABEL Parameter Description The LABEL parameter can be used to define the dataset's retention. You can specify an explicit expiration date or specify the number of days the dataset is to be retained. The LABEL parameter overrides the CYCL and RETEN configuration options. If a dataset is being autocataloged for the first time, the new EDD will take the LABEL value.
OPTION Parameter DD Statements for Tape and Disk Datasets OPTION Parameter Description The OPTION parameter can be used to invoke a BIM-EPIC feature applicable for which there is no equivalent MVS JCL parameter.
DD Statements for Tape and Disk Datasets OPTION Parameter ALLMSGS Overrides configuration options ALLMALL=NO (default) and ALLMSG=NO for this dataset in the current job step only. It enables all allocation messages for the disk dataset. This subparameter performs the same function as the BIM-EPIC DLBL option 'M'. The ALLMSGS subparameter is valid for disk datasets only and is ignored if specified for a tape dataset.
OPTION Parameter DD Statements for Tape and Disk Datasets RUN OPTION=RUN can be used to unload the tape at close. It overrides any rewind option defaulted to by the DISP or VOL parameters. SPACE= *.ddname[x] Specifies that the primary extent allocation is to be based on the amount of space used by a dataset that was defined previously in the same job step. Identify the dataset you are referring to by specifying its ddname in the SPACE parameter. RLSE is automatically invoked with SPACE refer-back.
DD Statements for Tape and Disk Datasets OPTION Parameter To allocate a new dataset five tracks smaller than the space the referenced dataset occupies, specify: * //FILEOUT DD DSN=dataset-name,DISP=(NEW,CATLG) * // UNIT=SYSDA,OPTION=SPACE=*.REFFILE-5 To allocate a new dataset half of the space occupied by the referenced dataset, specify: * //FILEOUT DD DSN=dataset-name,DISP=(NEW,CATLG) * // UNIT=SYSDA,OPTION=SPACE=*.REFFILE*.
SPACE Parameter DD Statements for Tape and Disk Datasets SPACE Parameter Description SPACE specifies the allocation of a disk dataset. Space is used to: • • • • specify allocation size permit or inhibit truncation at close for an output dataset invoke dataset fragmentation if contiguous space is unavailable align allocation on track or cylinder boundaries on CKD devices Parentheses are used to enclose the positional subparameters of the SPACE parameter.
DD Statements for Tape and Disk Datasets SPACE Parameter specified). However, if the SPACE parameter is not specified for cataloged datasets, they are truncated at close. frag-control is optional. If used, it must be one of the following: • • CONTIG specifies that each allocation must be made using consecutive tracks or blocks for the entire allocation amount. This is the same as the DLBL option 'H'. MXIG and ALX both specify fragmentation without operator intervention.
SPACE Parameter Example DD Statements for Tape and Disk Datasets The following example shows an uncontrolled dataset. BIM-EPIC creates a label indicating the extent begins at relative track 1680 and is 5 tracks long. It is on the SYSWK1 volume. * //DISKIN * // 6-32 User Reference DD DSN=INVENTRY.
DD Statements for Tape and Disk Datasets UNIT Parameter UNIT Parameter Description Specifies a device or device type for processing. It is usually specified for output, and it is required for disk output datasets. It is optional for input datasets that are controlled by the DSN Catalog. If UNIT is not specified, UNIT=TAPE is assumed unless the dataset name begins with “$$$.” (common work dataset) in which case UNIT=DISK is forced. You can also request a unit by a group name.
UNIT Parameter DD Statements for Tape and Disk Datasets • • • • • • • • 3420 specifies any tape device (does not override default MODE) 3424 specifies any tape device (does not override default MODE) 3430 specifies any tape device (does not override default MODE) 3480 specifies a 3480 non-IDRC drive 3490 specifies a 3490 IDRC drive 3590 specified a TPA device 8809 specifies any tape device (does not override default MODE) 9348 specifies any tape device (does not override default MODE) cuu specifies the
DD Statements for Tape and Disk Datasets VOLUME Parameter VOLUME Parameter Description For tape datasets, use VOLUME to specify tape rewind options and to select a tape volume to process. These options are especially important for multi-dataset processing. For disk datasets, use VOLUME to specify a disk pool for allocation and to specify a maximum number of secondary allocations. VOLUME is required for Start Track 1 datasets. VOLUME's first four subparameters are positional.
VOLUME Parameter DD Statements for Tape and Disk Datasets SER=volser selects a volume by volume serial number. You can use this subparameter to specify a disk volume for uncontrolled disk datasets. SER=poolname selects a disk pool. It is required for Start Track 1 datasets. Example In the following example, the VOL parameter indicates the pool where the Start Track 1 dataset is located. * //DISKIN * // DD DSN=INVENTRY.FILE,SPACE=(CYL,(5,5),RLSE), DISP=(NEW,KEEP),VOL=SER=SYSWK1 REF=*.
DD Statements for Tape and Disk Datasets VOLUME Parameter The VOL=REF=subparameter tells BIM-EPIC the name of the prime dataset. VOL=(RETAIN,,,REF=*.TAPEDUM) tells BIM-EPIC that both of the following are true: • • this dataset is a subdataset and part of a multi-dataset group the prime dataset associated with this subdataset is 'PRIME.DSN.1' See "Multi-Dataset Processing" for further explanation of prime datasets and subdatasets. Chapter 6.
VOLUME Parameter DD Statements For Printer and Punch Datasets DD Statements For Printer and Punch Datasets Description You can use DD statements to assign printer and punch datasets. Format * //ddname Parameters DD Parameter SYSOUT=x [ ,OPTION=SYSnnn ] Required? Valid Default x Yes A to Z or 0 to 9 None SYSnnn No SYS000 to SYS254 None SYSOUT pecifies the class to be used for printer and punch data. For punch data, specify B. For print data, specify any other character.
DD Statements for In-Stream Datasets VOLUME Parameter DD Statements for In-Stream Datasets Description When a job uses in-stream data, you can use a DD statement to assign a logical unit to the data stream. You must still place the in-stream data after the EXEC statement, as in VSE.
VOLUME Parameter Examples DD Statements for In-Stream Datasets In the following example, the AJS00987 statement is read as in-stream data using SYS005. Because the ddname is itself a logical unit specification, no OPTION statement is necessary. * //SYS005 DD // EXEC PGM AJS00987 /* * In the following example, LOG JE0987 and SP 9876 are read as in-stream data using logical unit SYS005.
DD Statements for Dummy Datasets VOLUME Parameter DD Statements for Dummy Datasets Description You can define dummy datasets with DD statements. Format * //ddname Parameters DD Parameter DUMMY [,OPTION=SYSnnn] Required? DUMMY Yes SYSnnn No Valid Default None SYS000 to SYS254 None DUMMY specifies that this is a dummy dataset. SYSnnn specifies the programmer logical unit and is required if the ddname itself is not a logical unit specification.
VOLUME Parameter 6-42 User Reference DD Statements for Dummy Datasets
7 Running Jobs With BIM-EPIC BIM-EPIC is designed to work with your existing JCL. However, JCL changes are sometimes necessary and sometimes helpful. Some situations require special entries in the BIM-EPIC dataset definition (EDD). This chapter discusses how to use BIM-EPIC and JCL with products from IBM and other third-party vendors. It describes new requirements and the use of BIM-EPIC label options. Recommendations for JCL and EDDs are presented for each topic when relevant.
Unsupported Datasets Introduction Introduction Unsupported Datasets Description BIM-EPIC does not control datasets that are defined in the JCL with the following DTF names: • • • IJSYSNR IJSYSPC IJSYSRS BIM-EPIC also does not control datasets processed with the following system utilities: • DITTO basic and control functions BIM-EPIC can control DITTO file functions.
Introduction JCL or DSN Catalog? JCL or DSN Catalog? Description For output datasets, JCL parameters always override corresponding DSN Catalog information. However, JCL period retention must be greater than zero to override a DSN Catalog value.
Input Dataset Selection Introduction Input Dataset Selection Description When you use TLBL and DLBL statements for input, BIM-EPIC selects the current version by default. When you use DD statements for input, the entire dataset is concatenated if you do not specify a version number. All versions of the dataset are read, beginning with the current version and ending with the oldest version. JCL can be used to override these defaults.
Introduction Defining Your Datasets With TLBL, DLBL, and DD Statements Defining Your Datasets With TLBL, DLBL, and DD Statements Description For every controlled dataset that it processes, BIM-EPIC uses the information in the DSN Catalog entry to update the VSE label area when the dataset is opened. Because this information is recorded automatically, JCL can be very concise.
Rules For Dataset Name Introduction Rules For Dataset Name Description Rules for dataset names are specified at 5-2, 5-8 and 6-22 in this manual. For generation datasets, specify the dataset name as it appears in the EDD. Do not specify the G=nnnnnn extension that appears in the VTOC.
Introduction LUB Allocation and the ASSGN Statement LUB Allocation and the ASSGN Statement When an ASSGN Statement is Not Required Using LUB allocation and AVR, BIM-EPIC does the work of an ASSGN statement. LUB allocation selects the SYS number, and AVR selects the drive. As long as LUB allocation is active, ASSGN statements are not necessary and should be removed from your JCL. When an ASSGN Statement is Required ASSGN statements must be used whenever LUB allocation is inhibited.
Controlled Datasets Disk Processing Disk Processing Controlled Datasets EXTENT Statements For most controlled datasets, the EXTENT statement is ignored. An EXTENT statement can be required when you process direct access (DA) datasets or any datasets with programs that use PIOCS processing. See "Physical IOCS Processing" in this chapter for details.
Disk Processing Start Track 1 Datasets Start Track 1 Datasets Description To define a Start Track 1 dataset, you must specify allocation information. DLBL Statements EXTENT statements are required for Start Track 1 datasets. The EXTENT statement for a Start Track 1 dataset differs only slightly from the standard VSE EXTENT statement. To use a Start Track 1 EXTENT, do the following: • • Example Specify a BIM-EPIC disk pool instead of a volume serial number.
Reusing the Same Space Disk Processing Reusing the Same Space DSN Catalog If you want to write a new version of a disk dataset in the same location (reusing the same space), catalog the dataset as work ("WRK" using Online Manager, or WRK=YES using TSIDMNT) and zero secondary allocations. JCL Requirements 1. Each time the dataset is created or modified, inhibit truncation. This leaves space in the extent for a larger dataset the next time it is processed.
Processing Tape Datasets Processing Internal Tape Labels Processing Tape Datasets Processing Internal Tape Labels Description BIM-EPIC supports both labeled and unlabeled tape processing. BIM-EPIC automatically changes the DTF for an unlabeled tape (FILABL=NO or "LABEL RECORDS OMITTED") to a DTF for a labeled tape (FILABL=STD or "LABEL RECORDS STANDARD") when you supply a TLBL with the DTF name. This allows you to convert to labeled processing without making program changes.
Rewind Options and MTC Statements Processing Tape Datasets Rewind Options and MTC Statements You do not need to use MTC statements to rewind your tapes. BIM-EPIC will position the tape automatically for input processing. You can also use BIM-EPIC's rewind options for output or input processing. These label options will override equivalent options in your program.
Processing Tape Datasets Multi-Volume Processing Multi-Volume Processing Description You can process up to 255 volumes per tape dataset version and up to 255 extents per disk dataset version. JCL Requirements None. Chapter 7.
Multi-Dataset Processing Processing Tape Datasets Multi-Dataset Processing Description This section explains the concept of multi-dataset groups and describes their processing requirements and options. A multi-dataset group consists of a prime dataset and up to 9,998 subdatasets. A multi-dataset group can reside on a single volume or on multiple volumes.
Processing Tape Datasets Subdatasets Multi-Dataset Processing Each subdataset has its own EDD, but some subdataset attributes cannot be specified because they are always inherited from the prime dataset. These attributes are: • • • • • • Density Tape labeling Tape size Tape pool Owner ID Vaulting method Scratching MultiDataset Tapes Multi-dataset tapes are scratched when all active datasets on the tape are scratched.
Multi-Dataset Processing Processing Tape Datasets If you are creating subdatasets with a single program that opens multiple DTFs with different logical units, you must inhibit LUB allocation through the DSN Catalog. To force BIM-EPIC to use the same logical unit for each dataset, specify the same SYS number in each EDD.
Processing Tape Datasets Multi-Dataset Processing Be sure the dataset is not already controlled before you attempt to catalog it using this option. If the prime dataset or any subdataset is already controlled, DISP=(x,CATLG) is ignored. Chapter 7.
Multi-Dataset Processing Examples Processing Tape Datasets Multi-Dataset Processing Examples Example 1 The first example is one of the simplest possible situations for creating a multi-dataset group. Your program creates datasets with different DTF names, but each DTF uses the same logical unit. The datasets are controlled in the first step. They are created in the second step. The second dataset on the tape is read in the third step. In the cataloging step, the prime dataset is defined first.
Processing Tape Datasets Example 2 Multi-Dataset Processing Examples This example creates multiple datasets with the same DTF name. This process requires dataset drop.
Multi-Dataset Processing Examples Example 3 Processing Tape Datasets This example creates multiple datasets with different DTF names. Because the different DTFs use different logical units, a logical unit must be supplied in the dataset definitions.
Processing Tape Datasets Example 4 Multi-Dataset Processing Examples This example is very similar to Example 2. It may seem more complicated than Example 2, but the BIM-EPIC DD facility offers greater flexibility than TLBLs.
Multi-Dataset Processing Examples Processing Tape Datasets In the example above, the options used in the creation step are: Option Action DSN='xxxx(+0)' The "+0" in parentheses indicates that this is a generation dataset (see the DDGEN configuration option in the BIM-EPIC Installation and System Guide). OPTION=(SYS010) Inhibits LUB allocation for this dataset. This is equivalent to TLBL option code 64. In addition, this forces the use of SYS010 (which has no TLBL equivalent).
Processing Tape Datasets Example 5 Multi-Dataset Processing Examples Whenever a subdataset such as VERY.LONG.NAME.FOR.NEWSUB.3 is accessed, the prime dataset name must be referenced in the JCL. The following example shows how VERY.LONG.NAME.FOR.NEWSUB.3 can be read as input: // JOB XYZ * * ---------------------------------------------------------------+ * READ VERY.LONG.NAME.FOR.NEWSUB.3 AS INPUT. THE PRIME DATASET + * NAME (VERY.LONG.NAME.FOR.PRIME.
Sequential Datasets Types of Datasets Types of Datasets Sequential Datasets For disk, allocation is on track boundaries for CKD devices. If you specify DLBL option "A" or the SPACE=(...,ROUND) parameter on a DD statement, BIM-EPIC makes the allocation on cylinder boundaries. Otherwise, there are no special requirements for sequential dataset processing.
Types of Datasets Direct Access Datasets Direct Access Datasets Description For direct access datasets: • • • LUB allocation is inhibited automatically Allocation is on cylinder boundaries and datasets are not truncated Secondary extents are not supported for controlled datasets Configuration Options For uncontrolled DA datasets, the following apply: DSN Catalog No special EDD requirements. JCL Requirements The VSE job control program requires you to use a DLBL and a complete EXTENT statement.
ISAM Datasets Types of Datasets ISAM Datasets Description BIM-EPIC can control ISAM datasets. The following VSE restrictions affect ISAM dataset processing with BIM-EPIC: • • • BIM-EPIC can control only one prime data area, one overflow area, and one index per ISAM dataset. ISAM datasets are automatically allocated on cylinder boundaries.
Types of Datasets Examples ISAM Datasets In the following example, each area is defined with its own set of parameters. Space and other information about the area follows the DSN parameter identifying the area. Because it is defined alone, index area space is defined with the primary-qty subparameter, SPACE=(TRK,1) and not the index-qty, SPACE=(TRK(,,1)). * * * * * * * * * * * * * * * * * * //DATA // // // // // // // // // // // // // // // // // DD DD DD DSN=CUSTOMER.
VSAM and VSAM-Managed SAM Datasets Types of Datasets VSAM and VSAM-Managed SAM Datasets Description BIM-EPIC does not control VSAM or VSAM-managed SAM datasets. Therefore no changes are required in your JCL. However, you can use DD statements to access an existing VSAM cluster or VSAM-managed SAM dataset. See the IBM documentation for further information. You can have VSAM dataset location and activity recorded in the DSN Catalog.
Types of Datasets Work Datasets Work Datasets Temporary Datasets BIM-EPIC can release disk space or tapes used for controlled datasets at close or at end-ofjob. You can find common work dataset (CWDS) support or CPU/partition independence helpful with work datasets. See "Common Work Datasets" and "CPU and Partition Independence" for details. DSN Catalog Catalog the EDD as work ("WRK" using Online Manager, or WRK=YES using TSIDMNT). JCL Requirements For TLBLs, specify option "4".
CPU and Partition Independence Types of Datasets CPU and Partition Independence Description CPU and partition independence are normally used with work datasets. They allow you to use a single set of JCL to run in any partition or CPU. Because BIM-EPIC inserts a partition and/or CPU ID into the dataset name to make the dataset name unique, there will be no duplication of the dataset names in different partitions or machines. For example, in your JCL you could specify ===.SORTWRK1 as the dataset name.
Types of Datasets Common Work Datasets (CWDS) Common Work Datasets (CWDS) Description The easiest way to control sort work, compiler work areas and any other disk only dataset that does not need to be kept after end-of-job is to use the common work dataset (CWDS) feature. When a dataset name begins with three dollar signs and a period ($$$., or £££. in the U.K.), BIM-EPIC recognizes it as a CWDS.
TYPEFLE=WORK DTFs Types of Datasets TYPEFLE=WORK DTFs Description Datasets that have TYPEFLE=WORK DTFs are processed differently from other sequential datasets. Common TYPEFLE=WORK DTFs include compiler work datasets and FORTRAN disk datasets. BIM-EPIC can process TYPEFLE=WORK DTFs on disk only (DTFSD). You can, of course, still use TYPEFLE=WORK DTFs with tape if the tape dataset is uncontrolled. TYPEFLE=WORK DTFs can be controlled as Start Track 1 or cataloged datasets.
Types of Datasets Compiler Work Datasets Compiler Work Datasets Description Compiler work datasets have the same requirements as TYPEFLE=WORK DTF datasets. Refer to "TYPEFLE=WORK DTF's" above, for those requirements. In addition, observe the following requirements described below. DSN Catalog Compiler work datasets should be controlled with a disk pool that contains volumes of the same device type as those to which SYS001, SYS002,SYS003, SYS004, and SYSLNK are permanently assigned.
Uncontrolled Datasets Types of Datasets Uncontrolled Datasets Description Any dataset that is not controlled using the DSN Catalog or the Start Track 1 features is called an uncontrolled dataset. With a few exceptions, uncontrolled datasets are not provided any additional features than are provided using standard VSE. For uncontrolled tape datasets, BIM-EPIC provides protection for all output tapes to ensure that any tape volume that is still in an active status is not used.
Types of Datasets Physical IOCS Processing Physical IOCS Processing Introduction VSE system utilities, sort programs, report writers, database utilities, and many other programs process datasets with physical IOCS (PIOCS). Many different issues can come into play when a program uses PIOCS to process datasets that are under BIM-EPIC control. If you familiarize yourself with those described below, you can make any PIOCS program work with BIM-EPIC-controlled datasets.
Physical IOCS Processing Types of Datasets 5. Generic device independence (GDI) cannot be used with PIOCS. 6. Some PIOCS programs do not provide the address of the last record written, so BIM-EPIC may not be able to truncate the dataset. Utility Programs BIM-EPIC provides the following utility programs to facilitate processing with PIOCS programs: Program Can be used for...
Sorting with BIM-EPIC Introduction Sorting with BIM-EPIC Introduction Description This section describes the considerations necessary to use BIM-EPIC controlled datasets with all sort programs in general and these three sort programs specifically: • • • SYNCSORT using BIM-EPIC Interface IBM SORT beginning with DFSORT 3.
BIM-EPIC Sort Interface (TSIDSRT) Sorting with BIM-EPIC BIM-EPIC Sort Interface (TSIDSRT) Description The BIM-EPIC sort interface program (TSIDSRT) addresses all the considerations described above, and usually requires no JCL changes except the phase name on the EXEC statement. TSIDSRT does the following: 1. Reads the sort control statements and modifies the input BLKSIZE to match the block size in the BIM-EPIC Catalog. 2.
Sorting with BIM-EPIC Sort Specifics Sort Specifics Description Many BIM-EPIC features rely upon DTF information that is automatically provided by the LIOCS (Logical Input Output Control Systems) access methods. BIM-EPIC also relies upon the standard open/close/end-of-extent/end-of-reel processing used by LIOCS.
Sort Specifics SYNCSORT using BIM-EPIC Interface Sorting with BIM-EPIC SYNCSORT offers options to improve compatibility with BIM-EPIC. See the SYNCSORT Installation Guide for details about these options. In addition, there are BIM-EPIC special options which must be activated when using SYNCSORT. See the BIM-EPIC Installation and System Guide, "Compatibility With Other Software" for details.
Sorting with BIM-EPIC SORTWK Datasets SORTWK Datasets Description To provide optimal utilization of disk work space, SORTWK datasets should be defined as temporary datasets and deleted as soon as they are no longer in use. DSN Catalog 1. Catalog SORTWK datasets as work ("WRK" using Online Manager, or WRK=YES using TSIDMNT). 2. Use the CWDS facility or partition/CPU-independent datasets so that the datasets can be processed in any partition without conflict.
SORTWK Datasets JCL Requirements Sorting with BIM-EPIC Pre-open assignments can be met by any of the following means: Media Method Disk 1. Permanent assignments (in partition start-up procedure) 2. Temporary assignments (in each job) Tape Execute TSIDASS with the ASSGN function. Tape or Disk 1. Use the DD OPTION=SYSnnn parameter. 2. Execute TSIDSRT.
IDCAMS BACKUP and RESTORE IDCAMS BACKUP and RESTORE Description You can use BIM-EPIC to control the IDCAMS backup dataset produced by the BACKUP function and used by the RESTORE function. IDCAMS provides for the backup dataset to reside on either tape or disk. DSN Catalog Only prime dataset definitions are allowed. Therefore, multi-dataset tape groups are specifically disallowed.
IDCAMS REPRO IDCAMS REPRO Description You can use BIM-EPIC to control non-VSAM sequential datasets for both input and output with the IDCAMS REPRO function. DSN Catalog No restrictions exist. For disk, both generation and non-generation datasets with single or multiple extents may be used. For tape, both single and multi-dataset groups residing and single or multiple tape volumes may be used. JCL Requirements for Tape Each controlled dataset must be defined with a TLBL or DD statement.
IDCAMS IMPORT/EXPORT IDCAMS IMPORT/EXPORT Description You can use BIM-EPIC to control the portable file produced by the EXPORT function and read by the IMPORT function. DSN Catalog No restrictions exist. For disk, both generation and non-generation datasets with single or multiple extents may be used. For tape, both single and multi-dataset groups residing and single or multiple tape volumes may be used. JCL Requirements for Tape Controlled portable files must be defined with a TLBL or DD statement.
LIBR BACKUP/RESTORE LIBR BACKUP/RESTORE Description You can use BIM-EPIC to control the tape datasets created by the BACKUP function and read by the RESTORE function. DSN Catalog Only prime dataset definitions are allowed. Therefore, multi-dataset tape groups are specifically disallowed. JCL Requirements Each controlled dataset must be defined with a TLBL or DD statement. LUB allocation must be inhibited since LIBR requires use of the SYS number specified in the BACKUP or RESTORE control statement.
DITTO DITTO Description You can use BIM-EPIC to control tape and sequential disk files logically accessed by DITTO. However, we do not recommend using DITTO due to the excessive JCL requirements. We recommend using TSIDDTD and TSIDDMP for equivalent functions each of which have minimal JCL requirements. When card-image processing is required, we recommend using your sort program (if that program supports card-image processing) or IDCAMS REPRO. DSN Catalog Only prime dataset definitions are allowed.
VSE/POWER ACCOUNT FILE VSE/POWER ACCOUNT FILE Description You can use BIM-EPIC to control account tape and sequential disk files created by the VSE/POWER PACCOUNT command. DSN Catalog No tape dataset restrictions exist. For disk, the pool must be comprised of the exact same DASD type as is used for the VSE/POWER account file (IJAFILE). Specify an adequate primary allocation value as not all versions of VSE/POWER will request secondary allocations even if needed.
VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling Description With the introduction of standard label support for tape spooling of either print or punch data and for POFFLOAD tapes, it is possible to utilize BIM-EPIC controlled tapes and dataset names for these functions even though some restrictions do apply.
VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling Since VSE/POWER still has the tape drive assigned, BIM-EPIC is unable to AVR other tape drives for the next volume in the version. The operator must mount the required volume on the indicated drive and respond 'NEWTAP'.
SQL/VSE Tape Output Functions SQL/VSE Tape Output Functions Description SQL/VSE is a long running task that manages database files for other tasks in the same VSE environment. The ability to archive database files (and their corresponding journal files) without having to terminate the SQL/VSE task is accomplished by invoking the operator communications facility for the partition-id in which the SQL/VSE task is running (MSG pp, where pp is the two character partition-id desired).
VSE/ICCF and Interactive Partition GETVIS Requirements with BIM-EPIC VSE/ICCF and Interactive Partition GETVIS Requirements with BIM-EPIC Problem An ICCF pseudo partition is allocated only 48K of GETVIS and there is currently no way to change that default. With BIM-EPIC active in the VSE system (it makes no difference if BIM-EPIC is turned off in the ICCF/CICS partition using OPTION EPICOFF=pp), more than 48K of GETVIS is generally needed just to initiate many programs.
Processing with COBOL II Processing with COBOL II Description BIM-EPIC requires that COBOL II programs are compiled with the Library Management Feature (the RES CBL option) in order to function properly. In some instances, you may have COBOL II software which was not compiled with the Library Management Feature active, and you have no access to the source code. To run these programs with BIM-EPIC, special JCL is required. DSN Catalog No special entries are required.
Restarting Programs from a Checkpoint Using BIM-EPIC's JCL Features Using BIM-EPIC's JCL Features Restarting Programs from a Checkpoint Description To prepare to restart programs from a checkpoint: • • Close all output datasets with the TSIDMNT CLOSE function. Use the console log to determine which input and output tape volumes have been used and which checkpoints have been taken. DSN Catalog All datasets must be cataloged. Start Track 1 datasets cannot be used with checkpoint/restart.
Using BIM-EPIC's JCL Features Example Restarting Programs from a Checkpoint In this example, TSIDASS restarts both input and output datasets at volume 2, using the same SYS numbers that were used when the checkpoint was taken. The TLBL option "64" inhibits LUB allocation. Because the checkpoints are embedded (being written to the same output tape as the output dataset using an assignment of SYS019), a VSE ASSGN statement is used to assign SYS019 to the checkpoint dataset.
Choosing the Device Type Using BIM-EPIC's JCL Features Choosing the Device Type Generic Device Independence Generic Device Independence (GDI) and Generic Device Independence for Unit Record Devices (GDIUR), sometimes called storage media independence, allows you to choose the type of media on which your dataset will be stored. You can process the dataset on either tape and disk, no matter how the dataset is defined in your program.
Using BIM-EPIC's JCL Features Eligibility Choosing the Device Type You can use GDI or GDIUR for uncontrolled and controlled datasets. A dataset normally processed as a Start Track 1 disk dataset would become uncontrolled if processed on tape with GDI. GDIUR does not support RPG-II SYSLST processing. GDIUR datasets cannot have secondary extents. GDI applies to tape and disk sequential datasets (DTFMT or DTFSD). VSAM, direct access, and ISAM datasets are not eligible.
Choosing the Device Type Example Using BIM-EPIC's JCL Features This example routes punch output to a disk dataset using GDIUR. * //IJSYSPH DD * // // EXEC PROGRAM /* * //IJSYSPH DD 7-58 User Reference DSN='CARD.
Using BIM-EPIC's JCL Features System Datasets and VSE Device Independence System Datasets and VSE Device Independence Description Although we recommend that you use GDIUR, you can also control a system dataset that is routed to disk or tape using VSE device independence. DSN Catalog No special entries are required. JCL Requirements The dataset cannot have secondary extents. The dataset must be permanently assigned, and label information must precede the assignment.
Dummy Datasets and ASSGN IGNORE Using BIM-EPIC's JCL Features Dummy Datasets and ASSGN IGNORE Description Dummy processing and ASSIGN IGNORE are only supported for LIOCS sequential access methods. DSN Catalog No special entries are required. JCL Requirements Assign the logical unit to IGNORE, so that BIM-EPIC ignores the dataset. Use an EXTENT statement for disk datasets defined with DLBLs. For DD statements, specify the DUMMY parameter instead of the DSN parameter.
Using BIM-EPIC's JCL Features Concatenating Datasets Concatenating Datasets Description Dataset concatenation reads multiple versions of a dataset or multiple datasets with one open. This allows you to process a number of datasets as if they were a single dataset. All versions of concatenated datasets must reside on the same device type. If the datasets have different block sizes, you must read the dataset with the largest block size first. DSN Catalog No special entries are required.
Concatenating Datasets Examples Using BIM-EPIC's JCL Features The following example processes versions 1 through 5 of the DAILY.TRANS dataset on disk with one open. It also processes WEEKLY.TRANS and WEEKLY.RERUN on tape with another single open. Although there are mixed device types in the job, they are not mixed within a single open, so they meet the requirements for concatenation. // // // // // // // // DLBL DLBL DLBL DLBL DLBL TLBL TLBL EXEC INPUT1,'DAILY.TRANS,(E,V=5)' INPUT1,'DAILY.
Using BIM-EPIC's JCL Features Processing Multiple Datasets with the Same DTF Name (Dataset Drop) Processing Multiple Datasets with the Same DTF Name (Dataset Drop) Description BIM-EPIC allows you to open multiple datasets with the same DTF name. Each dataset is opened and closed separately, in the order in which its label is submitted. DSN Catalog No special entries are required. JCL Requirements Specify the dataset drop option for all but the last dataset defined. Examples For... Use...
Running Test Jobs With Production Datasets Using BIM-EPIC's JCL Features Running Test Jobs With Production Datasets Description BIM-EPIC’s test job feature allows you to run test jobs with production datasets without affecting production processing. Test job names are defined by the TSTJOB configuration option. The TSTJOB configuration option can include wildcard characters to allow greater flexibility in creating test job names.
8 BIM-EPIC Utilities This chapter describes how to use BIM-EPIC JCL utilities that control files that are processed with physical IOCS (PIOCS) instead of logical IOCS (LIOCS). For more information about the recommended use of these utilities, see 7-1 in this manual. In addition, this chapter presents the dataset copy and dump utilities TSIDDTD and TSIDDMP and the VSE label access subroutines (TSIDGLB and TSIDPLB). Chapter Contents Pre-Open Processing (TSIDASS) .............................................
Pre-Open Processing (TSIDASS) Pre-Open Processing (TSIDASS) Description Use TSIDASS to process controlled files with programs that do not issue OPEN requests or that do pre-open checking of assignments. You can also use TSIDASS to make assignments to SYSRDR, SYSIPT, SYSLST, and SYSPCH.
Pre-Open Processing (TSIDASS) To make the assignment to a system logical unit, you must supply a dataset label for the dtfname IJSYSIN, IJSYSLS, or IJSYSPH. If a SYSPCH or SYSLST dataset is created on tape, you must place it in closed status before you can use it as input. Use the CLOSE function of TSIDMNT to close the dataset after it is created. To simplify the JCL necessary to process system files (SYSIPT, SYSLIST and SYSPCH), use the Generic Device Indepndence for Unit Record Devices (GDIUR) feature.
Pre-Open Processing (TSIDASS) INPUT specifies that the file is opened as input. OUTPUT specifies that the file is opened as output. Example // JOB OPEN TAPE DATASET // TLBL TAPEIN,'AP.DAILY.TRANS',,,,,,64 // EXEC TSIDASS OPEN TAPEIN,SYS020,OUTPUT /* // EXEC PROGRAM /& In this example, TSIDASS issues an open for the AP.DAILY.TRANS dataset. LUB allocation is inhibited for that dataset. RSTRT Statements Use TSIDASS RSTRT when you are restarting a job that has been checkpointed by VSE.
Pre-Open Processing (TSIDASS) OUTPUT specifies that the dataset was last opened as output. EXT specifies the sequence number of the extent to be re-opened. This is only necessary for disk datasets, and only if the dataset is to be opened at an extent other than the primary extent. This number will be equal to the number of BIM-EPIC EP053 messages that were issued for the dataset prior to the checkpoint from which the program will be restarted. Chapter 8.
Using the BIM-EPIC Sort Interface (TSIDSRT) Using the BIM-EPIC Sort Interface (TSIDSRT) Description TSIDSRT solves the problems that can occur at both open and close with some SORT utility programs. TSIDSRT is not a sort program. Instead, it is an interface program between BIMEPIC and your sort program. It calls your sort program to do the sort, but it allows BIM-EPIC to satisfy pre-open assignment checking, to truncate the SORTOUT file, and to close and delete SORTWK areas.
Deleting Datasets (TSIDDEL) Deleting Datasets (TSIDDEL) Description Some programs that use PIOCS do not close their work datasets. TSIDDEL can be used to delete disk work datasets that are not closed by the program that opens them. At any point in the job or job step, TSIDDEL can be used to free up their disk space for other processing. These datasets must be controlled, and they can be either Start Track 1 or cataloged datasets. TSIDDEL is available as a batch program and as a callable subroutine.
Deleting Datasets (TSIDDEL) Example The following job creates the SORTWK1 dataset in the first step. The 'D' option is included on the DLBL to qualify the dataset for deletion. In the second step, TSIDDEL deletes the SORTWK1 file and frees the space it occupied. . . . // DLBL SORTWK1,'$$$.SORTWK1,(D)' // EXTENT SYS003 // EXEC SORT [sort control statements] /* // EXEC TSIDDEL SORTWK1 /* . . .
Copying and Merging Datasets (TSIDDTD) Copying and Merging Datasets (TSIDDTD) Description TSIDDTD is a dataset-to-dataset copy/merge utility program. It can be used to copy a single dataset or to merge multiple input datasets into a single output dataset. TSIDDTD uses standard LIOCS access methods, so the input and output datasets can be completely controlled by BIM-EPIC. TSIDDTD supports any sequential dataset with a fixed, variable, spanned or undefined record format.
Copying and Merging Datasets (TSIDDTD) Tape Formats Supported Because TSIDDTD uses standard LIOCS access methods, it can only process tapes which follow standard LIOCS format conventions.
Copying and Merging Datasets (TSIDDTD) Syntax Control Statement Parameters [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ BLKSIZE=nnnnn ] FEOF=start,length,operand,type,value ] HDRINFO ] INNAME=dtfname ] INPUT=n ] LRECL=nnnnn ] NOREWIN ] NOREWOUT ] NOTPMK ] OBLKSIZE=nnnnn ] OUTNAME=dtfname ] RECFM=x ] RUNIN ] RUNOUT ] RECS=nnnnnn ] SEL=start,length,operand,type,value ] SKIP=nnnnnn ] UNLBLIN ] UNLBLOUT ] Parameter Required? Valid Default BLKSIZE No 1 to 32767 (or greater for disk) 32767 FEOF No See sub
Copying and Merging Datasets (TSIDDTD) RECS No 1 to 999999 All RUNIN/RUNOUT No None OFF SEL No See FEOF All SKIP No 1 to 999999 0 UNLBLIN/UNLBLOUT No None OFF BLKSIZE defines the block size for input datasets. If BLKSIZE is not specified, it will be set to one of the following: • • the value of LRECL undefined (if LRECL is not specified). In this case, the input dataset is treated as unblocked.
Copying and Merging Datasets (TSIDDTD) INNAME specifies an alternate input DTF name. INPUT specifies the number of input datasets to be merged into a single output. If specified as '?' (i.e., INPUT=?), the message EP712 will be issued requiring the operator to respond with the number of files to be copied. LRECL defines the dataset record size. For catalog-controlled datasets, the LRECL in the DSN Catalog is used instead if available.
Copying and Merging Datasets (TSIDDTD) UNLBLIN defines the input as an unlabeled uncontrolled tape dataset (not required if the dataset is controlled). UNLBLOUT defines the output as an unlabeled uncontrolled tape dataset (not required if the dataset is controlled). Example This job copies a controlled disk dataset to a controlled tape dataset. No TSIDDTD control statements are required. // // // // /* /& Example JOB TSIDDTD COPY DISK TO TAPE DLBL INPUT,'input.data.set' TLBL OUTPUT,'output.data.
Copying and Merging Datasets (TSIDDTD) Example This job copies a Start Track 1 disk dataset to an output dataset using alternate DTF names, selecting only those records with the constant "TAC" in positions 1-3 or any data except lowvalues in positions 4-6. The record format, record size and block size information is required for Start Track 1 datasets. // JOB TSIDDTD CREATE NEWFIL // DLBL OLDFIL,'input.data.set' // EXTENT SYS005,POOL01,1,0,1,300 // TLBL NEWFIL,'output.data.
Printing Datasets (TSIDDMP) Printing Datasets (TSIDDMP) Description TSIDDMP is a dataset dump and print utility program. It can be used to completely or selectively dump or print a dataset in hex or character format, and will also print report files that have been written to disk or tape. TSIDDMP uses standard LIOCS access methods, so the input dataset can easily controlled by BIM-EPIC. TSIDDMP supports any sequential dataset with a fixed, variable, spanned or undefined record format.
Printing Datasets (TSIDDMP) Control statement parameters can be used to limit total output, select specific records only and end processing before end-of-file (EOF) is reached on input. Various formating options are also provided. All control statements will be read and processed before TSIDDMP begins the dump operation. Parameters can be placed in columns 1 through 71. Separate parameters with commas.
Printing Datasets (TSIDDMP) Descriptions NOSCALE No None OFF RECFM No F|V|S|U U RECS No 0 or 1 to 999999 All RUN No None OFF SEL No See FEOF All SKIP No 1 to 999999 0 UNLBL No None OFF BLKSIZE defines the block size for the input dataset. If BLKSIZE is not specified, it will be set to one of the following: • • the value of LRECL undefined (if LRECL is not specified). In this case, the input dataset is treated as unblocked.
Printing Datasets (TSIDDMP) GT greater than value LT less than value GE greater than or equal to value LE less than or equal to value type specifies the type of data to be used in the test. C indicates that the value is in character format. X indicates that the value is in hexadecimal format. value specifies the constant to be used in the test. Specify the same number of characters as the length value for character comparisons, or two times that number for hexadecimal comparisons.
Printing Datasets (TSIDDMP) When SEL is specified, all SEL subparameters are required. SEL subparameters are identical to FEOF subparameters (see above). SKIP specifies the number of records to skip before beginning the copy operation. UNLBL defines the input as an unlabeled uncontrolled tape dataset (not required if the dataset is controlled). Examples The following job will dump the entire contents of a catalog-controlled disk dataset in hex format. No control statements are required.
Accessing the VSE Label Area (TSIDGLB and TSIDPLB) Accessing the VSE Label Area (TSIDGLB and TSIDPLB) Description TSIDGLB and TSIDPLB are subroutines that can be called by your program to read and write VSE labels. TSIDGLB is used to read system-standard, partition-standard, and partition user labels. TSIDPLB is used to modify a label that was acquired by TSIDGLB. TSIDPLB writes the label to an area maintained by BIM-EPIC.
Accessing the VSE Label Area (TSIDGLB and TSIDPLB) To Read a Label TSIDGLB Example To Write a Label Step Action 1 Move the DTF name of the label to be processed to FILENAME. 2 Call TSIDGLB, specifying FILENAME and LBLRETCD. ... MVC FILENAME,=CL7'INPFILE' CALL TSIDGLB,(FILENAME,LBLRETCD) ... COPY TSIDGLB ... Step Action 1 Read the label using the TSIDGLB procedure. 2 Modify the label information (see warning below). 3 Move the DTF name of the label to be processed to FILENAME.
9 Job Management Control Language BIM-EPIC's Job Management Control Language (JMCL) gives you greater control over the execution of your job. The JMCL facility is activated using the JCLLANG=YES configuration option as described in the BIM-EPIC Installation and System Guide. Chapter Contents JMCL Statements ...........................................................................................................9-2 JMCL Parameters...........................................................................
Introduction JMCL Statements JMCL Statements Introduction Description JMCL parameters are specified on VSE JCL statements. You can specify JMCL parameters on: • • • • EXEC statements JOB statements OPTION statements Comment statements Most JMCL parameters are valid on only one or two of the JCL statement types. Check the description of the particular parameter to see where it can be specified. JMCL parameters are in keyword format. You can specify more than one JMCL paramenter on a single statement.
JMCL Statements Using JOB, EXEC, and OPTION Statements Using JOB, EXEC, and OPTION Statements Description On JOB, EXEC, and OPTION statements, the JMCL parameters must: • • Syntax follow at least one VSE keyword (or a comma between two spaces) precede any comments // JOB jobname parameters comments // EXEC program parameters comments // OPTION option parameters comments Example In this example, the job name is PAYROLL. RESET is a JMCL parameter in its correct position. CHECKS is a comment.
Using Comment Statements JMCL Statements Using Comment Statements Description VSE comment statements can invoke JMCL by using special JMCL parameters.
JMCL Parameters JCL Syntax Checking JMCL Parameters JCL Syntax Checking Description With JMCL, you can retain datasets that have been flagged for purge (HOLD). You can cancel a job if it exceeds a specified time limit (TIME=n) or specify special processing for restarting canceled jobs (TYPRUN=RESTART). In addition, you can prevent some job cancellations by requesting DD statement syntax checking (TYPRUN=SCAN and TYPRUN=SCANS).
JCL Syntax Checking TYPRUN JMCL Parameters TYPRUN has two separate uses. It can be used to specify: • • syntax checking for DD statements special processing for job restarts TYPRUN is valid on JOB statements. Syntax SCAN TYPRUN=SCANS RESTART TYPRUN Parameters SCAN checks DD statement syntax and prints all JCL and any error messages. SCAN scans the JCL until the first /& statement, after which normal processing resumes. The job is not executed.
JMCL Parameters Condition Checking and Branching Condition Checking and Branching Description The GOTO facility allows you to bypass JCL statements without deleting them or changing them to comments before you submit the job. Condition checking, with the IF parameter, allows you to check whether certain conditions exist before you branch to a new part of the job. GOTO GOTO supports unconditional branching and conditional branching when used in conjunction with the JMCL IF parameter.
Condition Checking and Branching DATA JMCL Parameters Use DATA to bypass SYSIPT data during a GOTO branch. Because SYSIPT data is processed specially, BIM-EPIC cannot bypass it automatically. Place a DATA parameter on the EXEC statement of each program that is followed by SYSIPT data. DATA is valid only on EXEC statements.
JMCL Parameters Conditions and IF Conditions and IF Description Use IF to test for a condition. IF can test the current condition code, the highest condition code, the VSE cancel code, the date, time, CPU, partition, and a global constant you set. You can also set the current and highest condition codes. See 9-11 in this manual for more information. You can test multiple conditions using the IF parameter. Both "AND" and "OR" conditions are supported.
Conditions and IF JMCL Parameters DATE current date TIME current time Gnn global constant operand specifies the kind of test. Use... To test whether the input data is... EQ equal to value NE not equal to value GT greater than value LT less than value GE greater than or equal to value LE less than or equal to value value specifies the constant to be used in the comparison. Global constants are set with the SETG JMCL parameter.
JMCL Parameters Setting Values Setting Values Description You can establish a number of constants with JMCL parameters. These constants can be tested with the IF parameter. Use SETC to set the current condition code. Use SETG to set up to 15 global constants. SETC SETC sets the current condition code to the number you specify. This also updates the highest condition code, if appropriate.
Symbolic Replacements JMCL Parameters Symbolic Replacements Description Symbolic replacements "replace" a set of characters that are found in your JCL. Symbolic replacements are useful for JCL subparameters or comments. BIM-EPIC inserts the replacement value into the statement and shifts to the right any data following the replacement symbol. For example: * JMCL &1='INVENTRY.INPUT' // TLBL SORTOUT,'&1',,,,,,2 would result in: // TLBL SORTOUT,'INVENTRY.
JMCL Parameters RESET RESET Description RESET nullifies most JMCL parameters. You can use it to set the current or highest condition code to zero, nullify GOTO branches, and nullify TIME control over a job. We recommend that you use the global RESET parameter on the JOB statements and at the end of all jobs that do not have a logical dependency on previous jobs. RESET is valid on JOB, EXEC, JMCL, and OPTION statements.
JMCL Example JMCL Parameters JMCL Example Description The following example shows JMCL parameters working together. // JOB EXAMPLE TYPRUN=RESTART,RESET,TIME=240 * JMCL HOLD // OPTION LOG &1=PAYROLL * JMCL &2=PAYROLL * JMCL GOTO=STEP2 // ASSGN SYS001,DISK,VOL=VOLUME,SHR // DLBL SORTWK1,'==.SORTWK1(P)' // EXTENT SYS001 // DLBL SORTIN,'&1.INPUT' // DLBL SORTOUT,'&2.OUTPUT' // EXEC SORT DATA sort statements /* * JMCL NAME=STEP2 * JMCL IF=(DATE EQ **-**-01,TIME LT 19-00-00),GOTO=STEP3 // DLBL INPUT,'&1.
Using the JMCL Interface (TSIDJC2) Introduction Using the JMCL Interface (TSIDJC2) Introduction TSIDJC2 A batch program can interface with BIM-EPIC’s Job Management Control Language by calling the TSIDJC2 subroutine. TSIDJC2 can be used to retrieve the following information: • • • • • • • • • • DOS job name program name current date (MM/DD/YY) current time (HH.MM.
Retrieving JMCL Data (GET REQUEST) Using the JMCL Interface (TSIDJC2) Retrieving JMCL Data (GET REQUEST) GET REQUEST (G) Data can be retrieved from the JMCL system by passing a character ‘G’ to TSIDJC2 in the request byte of the parameter list (field JCSREQ in TSIDJC2.And JCS-REQ in TSIDJC2.C Control is returned to the next instruction following the CALL. COBOL Example WORKING-STORAGE SECTION. COPY TSIDJC2. . . . PROCEDURE DIVISION. MOVE 'G' TO JCS-REQ. CALL 'TSIDJC2' USING JCS-START.
Using the JMCL Interface (TSIDJC2) Updating JMCL Data (PUT REQUEST) Updating JMCL Data (PUT REQUEST) PUT REQUEST (P) JMCL data can updated by passing a character ‘P’ to TSIDJC2 in the request byte of the parameter. This byte is labeled JCSREQ in TSIDJC2.A and JCS-REQ in TSIDJC2.C. A Put request updates the current JMCL condition code, the highest JMCL condition code, all JMCL symbolics and all global constants.
Updating JMCL Data (PUT REQUEST) Assembler Example 9-18 User Reference MVI CALL MVC MVC XC MVI CALL JCSREQ,JCSREQG TSIDJC2,(JCSSTART) JCSCC,=XL2'00' JCSSYM2,=CL20'MONTHLY' JCSGBL10,JCSGBL10 JCSREQ,JCSREQP TSIDJC2,(JCSSTART) Using the JMCL Interface (TSIDJC2)
Using the JMCL Interface (TSIDJC2) TSIDJC2 Return Codes TSIDJC2 Return Codes Description Values TSIDJC2 returns a value in the return code byte of the parameter list. This byte is labeled JCSRC in TSIDJC2.A and JCS-RC in TSIDJC2.C. All return codes are one-byte character values. Code Explanation 0 Successful completion of the G(et) or P(ut) request. 1 Either BIM-EPIC or the JMCL system are not active. 2 A secondary routine (TSIDJCS) could not be loaded from the BIM-EPIC system library.
Executing CP Commands Executing CP Commands Description You can execute any VM/CP command in your VSE job stream by using JMCL's CP control statement. The CP control statement must begin in column 1. Configuration Options For CP commands to be valid, the VM configuration option must be set to YES. Syntax * CP command where command specifies which VM/CP command to execute. Example The following statement lists all tape drives on the operator console.
10 Job Scheduling BIM-EPIC's job scheduling system can be used to control execution across all partitions and VSE machines sharing the same DSN Catalog. Chapter Contents Event Posting ...............................................................................................................10-2 Introduction .............................................................................................................10-2 Scheduling Functions...............................................................
Introduction Event Posting Event Posting Introduction Description When a job, step, or process has completed, you can direct BIM-EPIC to post an event. BIM-EPIC writes the name of the event in the DSN Catalog as a version of the dataset *EPIC.EVENT.DSN*. You assign an event a name, 1 to 8 characters long. You then use this name to identify which event has completed.
Event Posting Scheduling Functions Scheduling Functions Description There are four job scheduling functions: • • • • Posting an event and releasing all matching jobs Posting an event only Checking for a posted event and releasing the requesting job Deleting a posted event For each job scheduling function, BIM-EPIC provides one batch utility, one standard processing subroutine, and one CICS subroutine. The batch utilities and subroutines share the same names. CICS subroutine names begin with TSIDC.
Posting an Event and Releasing Matching Jobs (TSIDREL and TSIDCREL) Posting an Event and Releasing Matching Jobs (TSIDREL and TSIDCREL) Description TSIDREL and TSIDCREL post events and automatically release jobs with matching job names from the POWER reader queue. To be released, a job must be in disposition "H" or "L" in the POWER reader queue, and its job name must match the event name posted.
Event Posting Posting an Event Only (TSIDLOC) Posting an Event Only (TSIDLOC) Description TSIDLOC and TSIDCLOC post events. They do not release jobs. When you use TSIDLOC or TSIDCLOC, dependent jobs must themselves issue a check for the posted event using TSIDCHK or TSIDCCHK. Chapter 10.
Checking for a Posted Event (TSIDCHK and TSIDCCHK) Event Posting Checking for a Posted Event (TSIDCHK and TSIDCCHK) Description TSIDCHK and TSIDCCHK are used within a job to check to see if an event has been posted before continuing with a dependent task. If the event is posted your job continues uninterrupted. If you check for the event with TSIDCHK (in either batch or subroutine) and the event is not posted, execution is interrupted.
Event Posting Deleting a Posted Event (TSIDUNL) Deleting a Posted Event (TSIDUNL) Description TSIDUNL and TSIDCUNL delete posted events. Use them to delete an event after all dependent tasks have completed. This is important if another processing cycle occurs before the event is scratched automatically. Remember that if you do not delete them, events become eligible for scratch as described under "About Posted Events". Chapter 10.
Executing in Batch Jobs Event Posting Executing in Batch Jobs Description TSIDREL, TSIDLOC, TSIDCHK, and TSIDUNL can be executed in batch jobs. JCL Requirements // OPTION SYSPARM='event-name' // EXEC TSIDxxx // OPTION SYSPARM=' ' Control Statements Two OPTION statements are required: one to specify the event name as a SYSPARM and one to clear the SYSPARM so it does not affect later processing. event-name specifies the name of the event to be posted (the name of the job to be released).
Executing Standard Processing Subroutines Processing Requirements for TSIDREL, TSIDLOC, and TSIDUNL Executing Standard Processing Subroutines TSIDREL, TSIDLOC, TSIDCHK, and TSIDUNL are callable subroutines for non-CICS programs. Standard linkage conventions apply to all four subroutines. Processing Requirements for TSIDREL, TSIDLOC, and TSIDUNL Procedure Example Step Action 1 Perform the “event” task. 2 Move the event name to the EVENT-NAME field.
Processing Requirements for TSIDCHK Executing Standard Processing Subroutines Processing Requirements for TSIDCHK Procedure Example Step Action 1 Move the event name to the EVENT-NAME field. See "Posted Events," for details about event-name limitations. 2 Issue a call to TSIDCHK. 3 Perform the dependent task. The following task calls TSIDCHK, with PAY as the EVENT-NAME. If that event is posted, the task performs PAYROLL-CHECKS. ... WORKING-STORAGE SECTION. 01 EVENT-NAME PIC X(8) VALUE SPACES.
Executing in CICS Using the Subroutines Executing in CICS Using the Subroutines Description TSIDCREL, TSIDCLOC, TSIDCCHK, and TSIDCUNL are CICS subroutines that can be called from a CICS command-level program.
Return Codes Executing in CICS Return Codes TSIDCREL Code Explanation A The event has already been posted. No jobs are released. F The DSN Catalog is full and the event cannot be posted. M The event name specified in EVENT–NAME is missing or invalid. P The event was posted, but there was an error in releasing jobs from the POWER reader queue. W The event was posted, but POWER is in a busy state and jobs were not released. X The event was posted, but the XECB supervisor table is full.
Executing in CICS TSIDCCHK TSIDCUNL Return Codes Code Explanation M The event name is missing or invalid. N The event is not posted. Y The event is posted. Code Explanation E The *EPIC.EVENT.DSN* dataset definition has been deleted from the DSN Catalog. F The DSN Catalog is full. M The event name is missing or invalid. N The event was not posted. Y The event was deleted successfully. Chapter 10.
Processing Requirements Executing in CICS Processing Requirements Procedure Example Step Action 1 Move the event name to the EVENT–NAME field. See "Posted Events," for details about event–name limitations. 2 Link to the subroutine. 3 Check the return code passed and process accordingly. WORKING-STORAGE SECTION. 01 EVENT. 02 EVENT-NAME PIC X(08). 02 EVENT-RETURN-CODE PIC X(01). 88 SUCCESS VALUE 'Y'. 88 FAILURE VALUE 'N'. 02 EVENT-POWER-MESSAGE PIC X(60) PROCEDURE DIVISION.
Creating Job Setup/Run Sheets (TSIDFAV) Processing Requirements Creating Job Setup/Run Sheets (TSIDFAV) UPSI Settings Modes of Execution // UPSI 1XXXX Print comment cards. // UPSI X1XXX Print user data cards. // UPSI XX1XX Scan all VSE jobs for creation of input files. // UPSI XXX1X Scan all POWER JOBS for creation of input files. // UPSI XXXX1 Input JCL submitted backwards (POWER MODE). TSIDFAV can be executed in VSE mode or in POWER mode.
Processing Requirements JCL Examples for VSE Mode Creating Job Setup/Run Sheets (TSIDFAV) // JOB TSIDFAV * INPUT INSTREAM DATA // ASSGN SYS004,SYSIPT // UPSI XXXX0 // EXEC TSIDFAV VSE JCL -/* /& // JOB TSIDFAV * DISK INPUT // DLBL DISKIN,'FAV.INPUT.JCL' // ASSGN SYS004,DISK,...
11 Job Activity Reports BIM-EPIC provides several job accounting programs. These programs produce job accounting statistics using data collected from the Recorder File. All job accounting is affected by the JOBACCT and RECORD configuration options. Chapter Contents Recorder History Dataset.........................................................................................11-2 Creating the Activity Log Report (TSIDARP) ........................................................
Recorder History Dataset Recorder History Dataset Description Recorder File backups can be used to create job activity reports. For example, you may want to combine daily backups into a single Recorder History dataset. You can create a new Recorder History dataset weekly, monthly, or for whatever time period you wish. Step 1 Create a new Recorder History dataset, using a tape-to-tape copying utility such as TSIDDTD.
Creating the Activity Log Report (TSIDARP) Creating the Activity Log Report (TSIDARP) Description TSIDARP produces the Activity Log report, which shows open and close activity for controlled datasets. Open and close activity is sorted by: • • • System ID Date and time Job name The Activity Log report can be limited to activity generated on any CPU or occurring during a specific time period. TSIDARP also produces the cross-reference dataset that is used as input to TSIDBRP.
EXCLUDE Control Statement EXCLUDE Control Statement Description The EXCLUDE control statement specifies a job to be excluded from the report. If used, it must come before the TSIDARP statement. You can use up to 20 EXCLUDE statements, each statement specifying one 1 to 8–character job name.
TSIDARP Control Statement TSIDARP Control Statement Description The TSIDARP control statement specifies what dates, CPUs, and partitions to include in the report. It is optional, and if it is omitted, the report contains all relevant data.
Creating the DSN/Job Cross-Reference Report (TSIDBRP) Creating the DSN/Job Cross-Reference Report (TSIDBRP) Description TSIDBRP generates two reports: the DSN/JOB Cross-Reference Report and the Accepted Tapes Report. The DSN/JOB Cross-Reference Report lists tape activity and is a cross-reference to the Activity Log report created by TSIDARP. The Accepted Tapes Report lists the controlled tapes that were accepted as input with the ACCEPT response to BIM-EPIC message EP009.
Creating the DSN/Job Cross-Reference Report (TSIDBRP) UPSI 100 creates only the Accepted Tapes report. It uses the Recorder Cross-Reference dataset as input. UPSI 101 creates only the Accepted Tapes report. It uses the Recorder Backup or History dataset as input. Dataset Requirements SYS002 identifies the Cross-Reference dataset created by TSIDARP. It is required with UPSI 000, 100, and 010. SYS005 identifies the Recorder Backup or History dataset when used with UPSI 101.
Job Accounting Reports by Job (TSIDJAC) Job Accounting Reports by Job (TSIDJAC) Description TSIDJAC produces the Job Time Activity report, which reports machine use statistics by job. Statistics are detailed by job step with totals for each job. In addition, a grand total is generated for all jobs. Use this report to find out when a particular job was run (did they really run payroll twice last night?) and what resources it used (my inventory program used 100% of my CPU?).
Job Accounting Reports by Partition (TSIDTAC) Job Accounting Reports by Partition (TSIDTAC) Description TSIDTAC produces the Date Time Activity report, which reports machine use statistics by partition and generates a grand total for machine use in all partitions. Use this report to find out what was running in a partition at a particular time. Statistics include start and end times, duration, partition ID, CPU time, overhead, and I/O activity.
Maintaining the Job Accounting Database (TSIDJLD) Maintaining the Job Accounting Database (TSIDJLD) Description TSIDJLD creates and maintains a job accounting database. You can access this database through CICS with the TOJA transaction. You can also develop your own reports and CICS transactions to access this data. To help you develop your own access to this data, a COBOL copy book (TSIDOJA.C) is provided. TSIDJLD uses a VSAM KSDS to store its data.
Maintaining the Job Accounting Database (TSIDJLD) The control statement is 28 bytes long and contains five fields: Bytes 1–3 ADD or DEL 4–11 Job name 12–21 Jobs started on or after this date 22 23–32 Syntax Parameters Contents ADD { DEL} Blank Jobs started on or before this date jobnamemm/dd/yyyy mm/dd/yyyy Parameter Required? Valid Default Specify one of the following two (required): ADD None OFF DEL None OFF jobname No 1 to 8 characters None mm/dd/yyyy No 10 characters None
Maintaining the Job Accounting Database (TSIDJLD) Examples The following job adds all information from the Recorder Backup dataset to the data base. // JOB TSIDJLD UPDATE THE JOB ACCTNG DATA BASE // ASSGN SYS003,SYSIPT // ASSGN SYS004,SYSLST // ASSGN SYS001,DISK,VOL=WORK01,SHR // TLBL SYS005,'DAILY.RCDR.BACKUP' // DLBL SORTWK1,'===.SORTWK1' // EXTENT SYS001 // DLBL TSIJADB,'TSIJADB.JOB.
Online Access to the Job Accounting Database (TOJA) Online Access to the Job Accounting Database (TOJA) Description TOJA, a CICS transaction, gives you online access to the job accounting database created by TSIDJLD. TOJA has four panels. The Job Selection panel is an entry panel. It allows you to select a job or a set of jobs for display. The rest of the panels display job accounting information at increasing levels of detail.
Online Access to the Job Accounting Database (TOJA) BIM-EPIC/VSE ONLINE JOB ACCOUNTING FACILITY .
Online Access to the Job Accounting Database (TOJA) Accessing TOJA Step Action 1 From CICS, enter the TOJA transaction. The Job Selection panel is displayed. 2 If you want to view all jobs, press ENTER. If you want to view several jobs beginning with the same character string, enter the string and press ENTER. If you want to view a single job, enter the job name and press ENTER. Navigating in TOJA To move forward in a panel, press PF8. To move backward in a panel, press PF7.
Online Access to the Job Accounting Database (TOJA) 11-16 User Reference
12 Managing Tape Volumes To protect controlled datasets effectively, BIM-EPIC controls the tape volumes they reside on. BIM-EPIC also protects the tape volumes it controls. Every tape that contains a BIM-EPICcontrolled dataset is recorded in the DSN Catalog. Tapes are identified by volume serial number and controlled at the version level under the name of the dataset they contain. Tape volumes are cataloged individually, as they are used for controlled datasets or initialized with TSIDINIT.
Introduction Introduction Tape Volume Serial Numbers Every tape volume used to write a BIM-EPIC-controlled dataset must have a unique volume serial number. Even unlabeled tapes must be identified with their own volume serial numbers. This strict identification is essential to tape volume control. Volume serial numbers can be any six-character combination of alphanumeric characters. Groups of volume serial numbers do not need to be consecutive; any unique volume serial number is valid.
Introduction Tape Pooling You can use tape pooling to group similar types of tapes into tape pools. For example, your high quality tapes could constitute one pool, short tapes another, long tapes a third, and so forth. You can also use pools to separate cartridge tapes from reel tapes. Datasets are assigned to tape pools through the DSN Catalog. When a pooled dataset is created, BIMEPIC automatically requests the operator to mount a scratch tape from the appropriate pool.
Introduction If the dataset is new or it does not own enough tapes, new tapes can be added with the ADD command and then scratched with the SCRATCH command (using Online Manager or the TSIDMNT program). Multi-Dataset/MultiVolume Processing BIM-EPIC supports multi-dataset, multi-volume, and multi-dataset/multi-volume processing. A tape volume that contains a dataset that is a member of a multi-dataset group cannot be scratched until all datasets in the group have been scratched.
Attention Routine Commands Attention Routine Commands Description Certain BIM-EPIC services can be invoked by commands that the operator issues to the VSE Attention Routine (AR). Command Summary The BIM-EPIC Attention Routine commands are: How to Enter the Commands Command Action EP ? (or EP HELP) Displays help information for BIM-EPIC AR commands. EP END STname Terminates a BIM-EPIC Dispatcher subtask. This command should be used only when directed by BIM-EPIC Technical Support.
FREE and STATUS Commands Attention Routine Commands FREE and STATUS Commands Description In addition to providing status information using the AR command facility, BIM-EPIC also allows the operator to respond FREE or STATUS to many BIM-EPIC messages. The FREE command lists all tape drives that are: • • • In READY status or with no tape mounted Not assigned to any partition Not attached to any other machine The STATUS command lists the current status of each tape drive.
Mounting Tapes Output Mounting Tapes Output Description BIM-EPIC controls which tapes can be used for output. It checks the volume serial number of every tape processed. If the tape mounted is controlled, its volume serial number is checked with its corresponding DSN Catalog entry to ensure that it is in scratch status before it can be used as output. If the tape is uncontrolled, BIM-EPIC checks to see if the tape's volume serial number exists in the DSN Catalog.
Input Mounting Tapes Input Requesting the Previous Version To request the previous version of a dataset, type RERUN in response to BIM-EPIC’s request for a tape mount. A new tape mount request will then be issued for the previous version. Example If a tape mount request is issued for version 1 and you reply RERUN, a new request is issued for version 2. You can reply RERUN as many times as there are versions for the dataset.
Mounting Tapes Initializing Tapes (TSIDINIT) Initializing Tapes (TSIDINIT) Description TSIDINIT initializes tapes with BIM-EPIC VOL1 labels and enters them in the DSN Catalog under the dataset name ‘***.VOLUME.DSN.**’. The tapes are then ready for use as controlled scratch tapes. Up to ten tape drives can be used in the initialization process. TSIDINIT can be executed from JCL or from the operator console. If it is executed from the console, the operator is queried for all processing information.
Initializing Tapes (TSIDINIT) Mounting Tapes Sequential initialization requires that the last four characters of the volume serial number be numeric (for example, EP1200 or A67019). Random initialization places no restrictions on the volume serial number. TSIDINIT normally checks each tape’s actual volume serial number before writing in the tape to ensure that an active tape is not initialized by mistake. It also protects against the creation of duplicate volume serial numbers.
Mounting Tapes PARM Values Initializing Tapes (TSIDINIT) PARM='CONSOLE' can be specified on the VSE EXEC statement to allow the operator to control initialization. This has exactly the same effect as entering EXEC TSIDINIT after a VSE ‘// PAUSE’ statement. PARM=’ACL=aclname[,COUNT=nnnnn]’ The parameters are positional – ACL= must preceed COUNT= aclname designates the ACL to use for initialization.
Initializing Tapes (TSIDINIT) Examples Mounting Tapes In this example, TSIDINIT performs sequential initialization of uncontrolled tapes that have labels or tape marks. It initializes the first tape with the volume serial number EP0001, the second tape with EP0002, the third tape with EP0003, and so on until the operator stops the process. It does label checking to ensure that the tape does not contain an active dataset.
Mounting Tapes Initializing Tapes (TSIDINIT) In this example, TSIDINIT uses an ACL to do random initialization of tapes not in the EPIC Catalog that do not have labels or tape marks, i.e. forced initialization. It initializes the first tape with volume serial number JCSR09, the second with WXY981, and so on until all volume serial number specifications have been read. // JOB INITTAPE // UPSI 01101 // EXEC TSIDINIT,PARM=’ACL=A2ATL’ CUU=480,481 JCSR09 WXY981 ….. ….. /* /& Chapter 12.
Printing External Volume Serial Labels (TSIDLBL) Mounting Tapes Printing External Volume Serial Labels (TSIDLBL) Description TSIDLBL creates external volume serial number labels in large block characters. These labels contain the volume serial number and a short optional comment. Standard spacing for each label is 1 line for the comment, 7 lines for the volume serial number, and two blank lines between labels.
Mounting Tapes Example Printing External Volume Serial Labels (TSIDLBL) In this example, EP0001-EP0100 DSN CONTROLLED indicates that one label is to be created for each volume serial number from EP0001 to EP0100, inclusive. Each label in this series will contain the comment ‘DSN CONTROLLED’. PR0001-PR0050 PAYROLL indicates that one label is to be created for each volume serial number from PR0001-PR0050, inclusive. Each label in this series will contain the comment ‘PAYROLL’.
Printing Dataset Labels (TSIDBPR and TSIDPRT) Mounting Tapes Printing Dataset Labels (TSIDBPR and TSIDPRT) Description With BIM-EPIC, you can create gummed dataset labels automatically when datasets are opened for output. You can create labels in a batch partition or through CICS. The TSIDBPR program creates labels in a batch partition. The TSIDPRT transaction creates labels through CICS. Automatic label creation requires you to write a subroutine.
Tape Vaulting Introduction Tape Vaulting Introduction Description BIM-EPIC's vaulting subsystem controls tape vaulting automatically. This section presents an overview of the programs and procedures involved in tape vaulting. Components Vault locations are established using the VAULTDEF macro, which defines the name and, if necessary, the size of each vault and the number of slots it contains. Vaults are identified by integers. The main library is always Vault 0 (zero).
Introduction Additional Reports 12-18 User Reference Tape Vaulting Reports listing current vault inventories can be created using TSIDUTL. TSIDPRV creates a report that cross references datasets with the vaulting methods assigned to them. See the BIMEPIC Installation and System Guide for more information on TSIDUTL.
Tape Vaulting Assigning Vaulting Methods to Datasets Assigning Vaulting Methods to Datasets Description After vaults and vaulting methods have been defined, they must be assigned to datasets before automatic vaulting can occur. This is done using the DSN Catalog. Vaulting methods are assigned to datasets using the CATALOG or UPDATE command (in Online Manager or TSIDMNT). In Online Manager, place the vault method number in the Vault Method field of the EDD.
Moving Volumes (TSIDVLT) Tape Vaulting Moving Volumes (TSIDVLT) Description TSIDVLT should be executed every day. TSIDVLT moves tapes from one vault to another and creates movement reports. TSIDVLT can be instructed to: • • Perform actual vaulting actions. Movement from one vault/slot to another occurs and a report describing the activity is produced. Perform projected vaulting actions. A report is produced describing what movements would take place, but no actual vault/slot movement occurs.
Tape Vaulting Reporting Current Locations of Vaulted Tapes Reporting Current Locations of Vaulted Tapes Description The DSPLY function of TSIDUTL creates reports which provide vault information for tape volumes. These reports can select and display tape datasets by vault. Parameter Action Example ALL Lists vault information for all tape datasets. DSPLY ALL,SEQ=DSN VAULT Lists the tapes contained in every vault except Vault 0 (main library).
Manually Controlled Vaults Tape Vaulting Manually Controlled Vaults Description A manually controlled vault is any vault whose number is greater than the value of the AVAULTS parameter in the VAULTDEF macro. Since manually controlled vaults are not known to BIM-EPIC, they must be tracked manually. Any version of any dataset can be moved to a manually controlled vault. Tapes are moved to or from manually controlled vaults using the MOVE function of Online Manager or TSIDMNT.
Tape Vaulting Vault To Dataset Cross-Reference Report (TSIDPRV) Vault To Dataset Cross-Reference Report (TSIDPRV) Description TSIDPRV produces the Vault Method Report. This report lists the vaulting method for each dataset, in dataset name sequence. For a dataset to appear on this report, it must have a vaulting method assigned to it in the DSN Catalog. JCL Requirements // DLBL SORTWK1... // EXTENT SYS001 // EXEC TSIDPRV UPSI Values None Dataset Requirements SORTWK1 is required.
Dataset to Tape Report (TSIDDIS) Tape Vaulting Dataset to Tape Report (TSIDDIS) Description TSIDDIS produces a summary report correlating dataset versions and tape volume serial numbers. It is listed in dataset name order. There is one entry for each dataset version. If a version spans more than one volume, there is an entry for each volume. See the Appendix for an example of this report. JCL Requirements // DLBL SORTWK1 // EXEC TSIDDIS UPSI Values None Dataset Requirements SORTWK1 is required.
Tape Vaulting Tape to Dataset Report (TSIDSDS) Tape to Dataset Report (TSIDSDS) Description TSIDSDS produces a summary report correlating dataset versions and tape volume serial numbers. It is listed in volume serial number order. There is at least one entry for each version of a dataset. If a version spans more than one volume, there is an entry for each volume. See the Appendix for an example of this report.
Tape to Dataset Report (TSIDSDS) 12-26 User Reference Tape Vaulting
13 Disk Space Management This chapter discusses how BIM-EPIC can help you to maximize and manage your disk space. Chapter Contents Introduction..................................................................................................................13-2 Dataset Fragmentation .............................................................................................13-2 Secondary Allocation...............................................................................................
Dataset Fragmentation Introduction Introduction Dataset Fragmentation Description When you create a dataset with a large primary allocation, there may not be a large enough free space in the pool to contain the entire primary extent. BIM-EPIC can respond to this condition by allocating the largest contiguous free space to the primary extent and allocating secondary extents when the primary extent becomes full. This process is called dataset fragmentation.
Introduction Secondary Allocation Secondary Allocation Description BIM-EPIC automatically allocates secondary extents to eligible datasets when the primary extent has been filled. Secondary allocation is not available for direct access or TYPEFLE=WORK datasets. Secondary allocation is available for SORTWK datasets only if the SORT program specifically allows it. For cataloged datasets, you can specify the size of the secondary extents and the maximum number of secondary extents (up to 255).
Truncation Introduction Truncation Description Any allocated extent that was not completely filled can be truncated so that the unused portion of the extent is freed. BIM-EPIC performs truncation for controlled datasets by altering both the VTOC and the DSN Catalog to show only the space actually used. Extents are always truncated on track or control interval boundaries. Truncation occurs only on output for sequential disk datasets.
Introduction Converting Uncontrolled Disk Datasets Converting Uncontrolled Disk Datasets Description To Convert to Catalog Control To Convert to Start Track 1 Example Existing uncontrolled disk datasets can be placed under BIM-EPIC control. Any existing dataset can be controlled, as long as all its extents reside in a single defined disk pool. You can convert a disk dataset to catalog control or Start Track 1 control.
Placing Datasets on Specific Volumes in a Pool Introduction Placing Datasets on Specific Volumes in a Pool Description Procedure 13-6 User Reference All disk datasets can be assigned to a BIM-EPIC pool. If your pool is made up of more than one volume, the dataset can be placed on any of those volumes. If you wish, you can place datasets on a specific volume. Step Action 1 Quiesce all other volumes in the pool. 2 Create the dataset and inhibit truncation.
VTOC Utilities Introduction VTOC Utilities Introduction Description WARNING! BIM-EPIC provides the following VTOC utilities: TSIDLVT, TVTO, and TSIDVUT. Utility Description TSIDLVT Displays VTOCs by BIM-EPIC pool or by volume, and in extent or dataset sequence. Can display both active and expired datasets, or active datasets only. TVTO Online utility. Displays VTOCs by volume only. TSIDVUT Allows modification of existing entries.
Printing VTOC Entries (TSIDLVT) VTOC Utilities Printing VTOC Entries (TSIDLVT) Description TSIDLVT produces printed reports of VTOC entries. It can display entries for an entire BIMEPIC pool or a specific volume. TSIDLVT prints expired datasets, unexpired datasets, and free space. Extents are shown in track/block format and dates in MM/DD/YYYY format. Control statements can be used to change the display format. At the end of each report, TSIDLVT prints the total free space in the pool or volume.
VTOC Utilities Printing VTOC Entries (TSIDLVT) [ [ [ [ [ [ [ Parameters ,EXP ] ,UNEXP ] ,FREE ] ,DSN ] ,INPOOL ] ,EURO ] ,CCHH ] Parameter Required? Valid Default volser 1 to 6 characters None poolname 1 to 6 characters None One of the following two is required: ALL No ON UNEXP No OFF EXP No OFF FREE No OFF DSN No OFF INPOOL No OFF EURO No OFF CHH No OFF You must specify either SER=volser or poolname. volser specifies the disk volume serial number to report.
Printing VTOC Entries (TSIDLVT) Examples VTOC Utilities The following job creates a report of the VTOC of volume SYSWK1. // // // // JOB VTOC DLBL SORTWK1,'===.SORTWK1,(X)' EXTENT SYS001 EXEC TSIDLVT SER=SYSWK1 /* /& The following job creates two reports. The first one, reporting POOL50, prints the standard report. The second, reporting POLFBA, lists only unexpired and expired datasets. They are listed in dataset name sequence. // // // // JOB VTOC DLBL SORTWK1,’===.
VTOC Utilities Online VTOC Displays (TVTO) Online VTOC Displays (TVTO) Description The TVTO CICS transaction displays information about entries found in the VTOC on a specific DASD volume. TVTO is a pseudo-conversational transaction, can only be utilized on an 80-character wide screen, will utilize 31-bit storage for the majority of its work areas (if available), and will automatically use the alternate screen size if larger than the default screen size.
Online VTOC Displays (TVTO) VTOC Utilities and upper limits for every disk pool containing space on the requested volume on the VTOC Screen (may also be specified as YES, Y, or A). NONE (Default) Ignore all disk pool information. All DASD entries defined to this VSE system will be displayed on the Help Screen and no pool limits will be displayed on the VTOC Screen (may also be specified as NO or N). Poolname Include only disk pool information for this Poolname.
VTOC Utilities Online VTOC Displays (TVTO) You can key the cuu of your choice in the first screen line just to the right of the constant 'CUU' or position the cursor anywhere on one of the list of available DASD's (shown as cuu=volser in up to 7 columns beginning on screen line 3) and pressing enter.
Online VTOC Displays (TVTO) Valid PF keys 13-14 User Reference VTOC Utilities PF Key Function Explanation PF1 HELP Display help screen. PF2 RFSH Read all VTOC entries again. PF3 END Return to CICS. PF4 FST Go to the first screen. PF5 LST Go to the last screen. PF7 BWD Back one screen. PF8 FWD Forward one screen.
Offload System Introduction Offload System Introduction Description BIM-EPIC provides offload/onload, backup/restore, offload version consolidation, and offload version copy functions for controlled sequential disk datasets versions; and is only available on BIM-EPIC systems supporting both disk and tape management.
Introduction Programs Offload System The offload system consists of four programs: Program Function TSIDOFD Selects datasets for offload and backup by creating control statements for TSIDOFL. TSIDOFL Offloads and backs up selected datasets. TSIDONL Restores offload and backup datasets back to disk and creates a listing of datasets on the offload tape. TSIDOFC Consolidates offload tapes and copies offload and backup tapes.
Offload System Selecting Datasets To Be Offloaded (TSIDOFD) Selecting Datasets To Be Offloaded (TSIDOFD) Description TSIDOFD creates control statements for input to TSIDOFL based on selection criteria you specify. These control statements determine which datasets will be offloaded or backed up. You specify selection criteria to TSIDOFD using INCLUDE and OMIT control statements.
Selecting Datasets To Be Offloaded (TSIDOFD) JCL Requirements Offload System [// xLBL OUTPUT,'sysin.data.set'] //EXEC TSIDOFD control statements /* An internal table is used during the dataset selection process to store each version selected. The capacity of this table is dependent on the amount of excess partition storage available (up to and not including partition GETVIS storage) and will never be less than 100.
Offload System Selecting Datasets To Be Offloaded (TSIDOFD) One primary set of parentheses must enclose all the parameter expressions on a single control statement. Commas or blanks can separate multiple parameter expressions. The parameters ALLVER, VOL, and POL each allow you to specify more than one value; in such cases, the values must be separated by commas within a set of parentheses.
Selecting Datasets To Be Offloaded (TSIDOFD) Offload System REPORT specifies whether the Preliminary Dataset Selection Report is to be printed and defaults to YES. This report shows the size of the internal selection table (in heading 2), the selection criteria used, and the actual dataset versions selected. CATALOG specifies whether selection should be for controlled disk datasets found in the BIM-EPIC catalog or for controlled start-track-1 disk datasets.
Offload System Selecting Datasets To Be Offloaded (TSIDOFD) ALLVER selects datasets by version number. ALLVER affects all datasets to be selected (VER affects only a specific dataset). You can specify up to five versions with a single ALLVER parameter. (e.g., ALLVER=n,n,n,n,n). SID selects datasets with the specified system ID. UID selects datasets with the specified user ID. DLA selects datasets which have not been accessed for the specified number of days. DLA is valid only for INCLUDE.
Offloading and Backing Up Datasets (TSIDOFL) Offload System Offloading and Backing Up Datasets (TSIDOFL) Description TSIDOFL offloads or backs up selected datasets according to the settings on an UPSI statement and the contents of control statements. Control statements indicating which datasets are to be processed can be generated by TSIDOFD or specified manually. They are supplied as SYSIPT data.
Offload System Offloading and Backing Up Datasets (TSIDOFL) /* // RESET SYSIPT UPSI Values UPSI 0 specifies OFFLOAD. UPSI 1 specifies BACKUP. Note that if control statements for start-track-1 datasets are submitted, UPSI 1 is automatically forced. UPSI x1 specifies special handling when the number of control statements exceeds the internal work area used by TSIDOFL.
Offloading and Backing Up Datasets (TSIDOFL) Offload System Syntax for Sequential Disk Versions Identified in the BIM-EPIC Catalog 'dataset-name',version-number Syntax for StartTrack-1 Disk Datasets 'dataset-name',POL=poolnm Parameters 'dataset-name',generation-number Parameter Required? Valid Default dataset-name Yes 1 to 44 characters None version/generation number No 1 to 9999/1-65534 1/None poolnm Yes 6 characters None dataset-name specifies the name of the dataset to be offloade
Offload System Restarting Offloads Offloading and Backing Up Datasets (TSIDOFL) The same dataset cannot be offloaded twice, so TSIDOFL automatically restarts with the next dataset to be offloaded. The datasets already offloaded are in the incomplete offload dataset version. Step Examples Action 1 Do not scratch the incomplete offload dataset version. 2 Restart the job in the TSIDOFL step. Disregard any error messages for missing datasets.
Offloading and Backing Up Datasets (TSIDOFL) Offload System The following job backs up five start-track-1 datasets named on the control statements supplied as SYSIPT data. All datasets are offloaded to a tape version that is retained under the output dataset name "START.TRACK1.DATA". // JOB BACKUP // TLBL OUTPUT,’START.TRACK1.DATA' // UPSI 1 // EXEC TSIDOFL ‘SNOOPY.DOG’,POL=WDPOOL ‘MICKEY.MOUSE’,POL=WDPOOL ‘TAZ.DEVIL’,POL=WBPOOL ‘WILEY.COYOTEIUS.MAXIMUMUS.HURTUM’,POL=WBPOOL ‘CRAYZY.
Offload System Onloading and Restoring Datasets (TSIDONL) Onloading and Restoring Datasets (TSIDONL) Description TSIDONL onloads or restores datasets back to disk. It can also be used to produce a report listing the datasets contained on the offload tape. TSIDONL functions are selected using UPSI values. You can onload a dataset from an offload tape only. TSIDONL assigns the dataset a current relative version based upon its absolute generation number.
Onloading and Restoring Datasets (TSIDONL) • Offload System The tape volume was created at a different site and is not known to the catalog at the site where it is being restored In all cases, the disk dataset to which a tape is being restored must be defined to the BIMEPIC catalog. Instead of using UPSI xxx1 for an uncataloged tape, we recommend that you ADD the tape volume to the BIM-EPIC catalog and then RETAIN it using the OF2 parameter.
Offload System TSIDONL Control Statements TSIDONL Control Statements Description Control statements are read if UPSI 010 or 110 is specified. There are two types of control statements for TSIDONL: • • A dataset-name control statement specifies a dataset to be onloaded or restored. A START control statement begins an onload or restore at a particular dataset on the tape.
TSIDONL Control Statements Restart Information Offload System Each backed up or offloaded dataset is processed as a separate entity. Therefore, if for any reason a multi-dataset onload or restore job terminates abnormally and is restarted, special restart considerations are necessary. In order to avoid dataset duplication and maintain version order integrity, the job must be restarted on the dataset being processed at the time the abend occurred. Use the following procedure.
Offload System TSIDONL Control Statements // JOB ONLOAD // TLBL INPUT,'USER.DATA.SET' // UPSI 010 // EXEC TSIDONL START='ACCOUNTS.PAY',112 /* /& The following job restores all datasets found on the start-track-1 disk dataset backup tape. // JOB RESTORE // UPSI 100 // EXEC TSIDONL /* /& The following job restores the three start-track-1 datasets named on the control statements supplied as SYSIPT data.
Differences Between TSIDONL Onload and TSIDONL Restore Differences Between TSIDONL Onload and TSIDONL Restore Description Suppose we have the following versions of a dataset called DATASET.A: Version number Absolute generation number (AGN) 1 46 2 45 3 44 4 43 5 42 6 41 Absolute generation numbers (AGN) run in inverse sequence to the version numbers within a dataset. At one time (when it was first created), version 2, AGN=45 was version 1.
Offload System Differences Between TSIDONL Onload and TSIDONL Restore Suppose now we onload our previously offloaded datasets. After doing this, DATASET.A would look as follows: Version number Absolute generation number (AGN) 1 48 2 47 3 46 4 45 5 (old ver. 3) 52 (AGN is used to find where the onloaded datasets belong) 6 (old ver. 4) 51 7 (old ver.5) 50 8 (old ver.
Consolidating Offload Versions (TSIDOFC) Offload System Consolidating Offload Versions (TSIDOFC) Description TSIDOFC consolidates one or more offload versions into a single version.. Control cards are used to report on consolidation candidates and to specify the versions to be consolidated.
Offload System Syntax Consolidating Offload Versions (TSIDOFC) Control statements can begin in any column. Continuations cannot be used. REPT [PCT=n] If used, it must be the only control statement submitted. PCT=n is optional and is meaningful only for offload datasets that reside on cartridge media.
Consolidating Offload Versions (TSIDOFC) Offload System CONO’s NV=4 would cause a sequence gap since there is no version 3. NV=3 or 2 would be ok since no sequence gap would occur. CONO must come after CONI. Example: CONI 5 12 CONO NV=5 COPY n n is the version number of the dataset that is input to the copy process. The version number of the output dataset will be 1. Only one version can be copied at a time. The input and output dataset names must be different. Only one COPY statement can be present.
Offload System Consolidating Offload Versions (TSIDOFC) The following job copies offload version 7 and creates version 1 in PAYR.MON.COPY. The new version 1 will be in BACKUP format. Version 7 may be in OFFLOAD or BACKUP format. // JOB OFCCONS // TLBL OFCINP,'PAYR.MONTHLY.OFLD’ // TLBL OFCOUT,'PAYR.MON.COPY’ // EXEC TSIDOFC COPY 7 /* /& Chapter 13.
Consolidating Offload Versions (TSIDOFC) 13-38 User Reference Offload System
A BIM-EPIC Report Fields and Examples Standard reports are listed by program name. Programs are presented in alphabetical order. Chapter Contents Customized Reports..................................................................................................A-2 TOJA Report Examples ............................................................................................A-3 TSIDARP Report......................................................................................................
Customized Reports Customized Reports Description In addition to the standard reports, you can use your own report writers to produce customized reports from BIM-EPIC data. The DSN Catalog contains all tape and dataset information, including BIM-EPIC dataset definitions (EDDs) and version data. We have provided the TSIDAC2 subroutine for access to the DSN Catalog. See Chapter 4 for procedures. The Recorder File contains all DSN Catalog changes, job accounting information, and user comments.
TOJA Report Examples TOJA Report Examples Description TOJA produces job accounting information online. For information on producing TOJA reports, see "Online Access to the Job Accounting Database" in Chapter 11. The report has three distinct levels: the Job Overview panel, the Program Overview panel, and the Program Audit panel. Each displays job accounting statistics in increasing detail. Job Overview Panel The Job Overview panel presents an overview of execution based on a jobname.
TOJA Report Examples Program Overview Panel The Program Overview panel displays statistics at the program level. BIM-EPIC/VSE ONLINE JOB ACCOUNTING FACILITY .
TOJA Report Examples The Program Audit Panel The Program Audit panel displays information about what datasets were processed by the program. BIM-EPIC/VSE ONLINE JOB ACCOUNTING FACILITY FILEID REC CREATION OPEN EXPIRY SERIAL REEL END DTF PROCESSED TYPE TIME CLOSE CUU DATE ACCEPTED TRACK TRACK TYPE ***************************************************************************** 3F8.IJSYSLN DO 10:19:29 C 400 11/18/1997 EPV400 030474 010000 32 3F8.
TSIDARP Report TSIDARP Report Description TSIDARP produces the Activity Log Report listing open and close activity by job name. Job data is listed in sections with information about the job and program information listed in the first line of the section. Dataset activity for that job is listed under the job name. Fields JOB NAME specifies the name of the job which initiated the open and close activity. Different jobs are separated from each other by a dotted line.
TSIDARP Report Activity Log Report Example J O B A C C O U N T I N G S Y S T E M TSIDARP= 6.01.00 C.P.U. NO. 111111 DATE 12/02/1997 A C T I V I T Y L O G RUN DATE 12/04/1997 TIME 13.19.49 PAGE 1 JOB PHASE C.P.U. OVER GEN/ SERIAL DTF TOTAL START/ END/ USAGE -D/S CREATION----DISK SPACE ALLOCATNAME NAME PART TIME HEAD REEL NO. TYPE UNIT I/O OPEN CLOSE MIN/SEC JOB DATE START REQST TRUNC DUMMY BG 00.1 00.1 09.30.15 09.30.17 .02 PROG TERMINATED INTERR.HEX CODE 00 .................................................
TSIDBRP Reports TSIDBRP Reports Description TSIDBRP creates the DSN/JOB Cross-Reference Report (a cross-reference to the Activity Log Report) listing open and close activity sequenced by dataset name. TSIDBRP also creates the Accepted Tapes Report which lists each time ACCEPT was used as a response to message EP008 or EP009. Cross-Reference Fields Each dataset is reported with a separate line for each open and each close.
TSIDBRP Reports Cross-Reference Report Example J O B A C C O U N T I N G DSN / JOB CROSS REFERENCE FILE NAME JOB NAME PHASE NAME VERIFY6.FILE01 CPUID RUN DATE TIME S Y S T E M RUN DATE 04/16/1998 SERIAL -DEVICEPART NO. TYPE NO. REEL NO. START TRACK TSIDBRP= 6.1 TIME 13.16.35 PAGE NO OF TRACKS VERIFY6 JCOPY G=0000002 222222 04/15/1998 06.19.25 BG CKD001 DISK 222222 06.19.
TSIDBRP Reports Accepted Tapes Report Fields REQUESTED FILE NAME is the name of the dataset requested by the job. REQUESTED SERIAL NO. is the volume serial number requested by the job. A serial number of ‘000000’ indicates that no real volume number is known. ACCEPTED FILE NAME is the name of the dataset accepted. ACCEPTED SERIAL NO. is the volume serial number accepted. A serial number of ‘000000’ indicates that no real volume number is known.
TSIDDIS Report TSIDDIS Report Description TISDDIS produces a summary report correlating dataset versions and tape volume serial numbers. It is listed in dataset name order. There is one entry for each dataset version. If a version spans more than one volume, there is an entry for each volume. For information on creating TSIDDIS reports, see 12-24 in this manual. Fields DATASET NAME indicates the dataset name. Versions and reels listed between this name and the next belong to this dataset name.
TSIDDIS Report TSIDDIS Report Example TSIDDIS= 6.01.00 TIME 14 06 30 DATA SET NAME $$$.VERIFY8.JUAN A-R TAPE ALERT.AUDIT.HIST AR.PROD.LGX.AR192BKP.GVEXPORT.AR192RST AR.PROD.LGX.EL588BKP.GVEXPORT.EL588RST AR.PROD.NCL.CASHRCT.CASHRBKP.DAILY AR.PROD.NCL.ELME3BKP.GVEXPORT.ELME3RST AR.PROD.NCL.ELME3BKP.GVEXPORT.OFFSITE AR.PROD.NCL.ERBFWD.EL863.MONTHEND AR.PROD.NCL.EREXTR.EL860.MONTHEND AR.PROD.NCL.EREXTR.EL860.OFFSITE AR.PROD.NCL.ERPNDB.EL860.MONTHEND AR.PROD.NCL.ERPNDB.EL860.OFFSITE AR.PROD.NCL.ERPYAJ.
TSIDJAC Report TSIDJAC Report Description TSIDJAC creates the Job Time Activity Report, which lists job accounting information by CPU and by job. Fields CPU NO. is the CPU being reported. JOB NAME is the name of the job which initiated the activity. RUN DATE is the date the job ran. PHASE NAME is the name of the program being reported. PART ID is the partition the job ran in. START TIME is the time (in hh.mm.ss format) the phase started. END TIME is the time the phase completed.
TSIDJAC Report Job Time Activity Report Example C.P.U. NO. 111111 JOB RUN NAME DATE RUN DATE 12/04/1997 PHASE PART NAME ID BGINIT 12/02/1997 DUMMY J O B A C C J O B T I M E START TIME O U N T I N G S Y S T E M A C T I V I T Y * END DURATION TIME TIME TSIDJAC= 6.01.00 PAGE 1 TOTAL I/O TIME 13.20.07 CPU OVER TIME HEAD BG 09.29.40 09.30.10 00.00.30 00.00.30* 00.00.30** 00.00.3 00.00.3* 00.00.3** 00.00.2 00.00.2* 00.00.2** 238 238* 238** 12/02/1997 BG 09.30.15 09.30.17 00.00.02 00.00.
TSIDLVT Report TSIDLVT Report Description TSIDLVT lists VTOC data in batch. The report format varies depending on the options you choose, and the following report only a sample of the reports you can create. For information on producing TSIDLVT reports, see 13-8 in this manual. Fields DISPLAY OF identifies the content of the report, either SER=volser or the name of the pool. FILE NAME is the name of the dataset residing in the specified pools of the VTOC.
TSIDLVT Report TSIDLVT Report Example *----------------------------------------------------------------------------------------------------------------------------------* * * * REPORT FOR SERIAL NUMBER=CKD001 * * * OPTIONS IN EFFECT - PRINT IN EXT SEQUENCE * * LIST EXPIRED EXTENTS * * IGNORE POOL LIMITS * * LIST FREE SPACE * * LIST IN RELATIVE TRACK/BLOCK FORMAT * * USE CONVENTIONAL DATE FORMAT MM/DD/YYYY * * LIST UNEXPIRED EXTENTS * *------------------------------------------------------------------------
TSIDMNT Reports TSIDMNT Reports Description TSIDMNT can produce a summary report or a detail report. To receive a summary report, request a display of all datasets or a group of datasets. To receive a detail report, request a specific dataset name or a specific volume serial number. For information on creating TSIDMNT reports, see Chapter 3. Summary Report DATASET NAME is the name of the dataset. SERIAL is the volume serial number(s) associated with the version. VN is the version number.
TSIDMNT Reports SYSnnn is the SYS number assigned to the dataset. REC is the actual record size of the current version BLK is the actual block size of the current version REV indicates whether this is a revolving tape dataset. COM is the user comment. TPA= is the output default for TPA devices (YES|NO) TPL is the tape pool ID. Version Information SER-NO is the tape or disk volume serial number associated with this version. VN is the version number. RL is the reel or extent sequence number.
TSIDOFD Report TSIDOFD Report Description TSIDOFD produces a report listing the datasets to be offloaded or backed up. To produce this report, see 13-17 in this manual. Fields DATASET NAME is the name of the dataset to offload or backup. VER is the version number of the dataset to offload or backup. ALL VER indicates all versions were selected. UID indicates whether the dataset was selected by user ID. SID indicates whether the dataset was selected by system ID.
TSIDOFL Report TSIDOFL Report Description TSIDOFL creates a report listing the datasets offloaded or backed up. To produce this report, see 13-22 in this manual. Fields DATASET NAME is the name of the dataset offloaded or backed up. VER is the dataset's version number. SERIAL is the volume serial number the dataset came from. CUU is the drive address the dataset came from. EXTENTS START is the former extent starting address. EXTENTS END is the former extent ending address.
TSIDONL Report TSIDONL Report Description TSIDONL creates a report listing the datasets that were onloaded. To create this report, see "Onloading and Restoring Datasets." Fields DATASET NAME is the name of the dataset onloaded. OLD VER is the version number of the dataset before it was onloaded. OLD GEN is the generation number of the dataset before it was onloaded. NEW VER is the version number of the dataset after it was onloaded. NEW GEN is the generation number of the dataset after it was onloaded.
TSIDPRV Report TSIDPRV Report Description TSIDPRV produces the Vaulting Method Report. The fields in this report are: Fields DATASET NAME is the name of the dataset. NO. CYC is the number of cycles to be maintained for the dataset. DAYS RET is the number of days each version is to be retained. METH NO. is the vaulting method assigned to the dataset. VER NO. and VAULT NAME represent the heart of the vaulting method report. They correlate each version number with its designated vault location.
TSIDSDS Report TSIDSDS Report Description TSIDSDS produces a summary report correlating dataset versions and tape volume serial numbers. It is listed in volume serial number order. For information on creating TSIDSDS reports, see 12-25 in this manual. Fields There is at least one entry for each version of a dataset. If a version spans more than one volume, there is an entry for each volume. SER NO is the volume serial number. DATASET NAME is the name of the dataset the referenced volume contains.
TSIDTAC Report TSIDTAC Report Description TSIDTAC creates the Date Time Activity Report, which lists job accounting information by CPU and by date and time. It is a cross reference to the Job Time Activity report. Fields CPU NO. is the CPU being reported. RUN DATE is the date the job ran. JOB NAME is the name of the job which initiated the activity. PHASE NAME is the name of the program being reported. PART ID is the partition the job ran in. START TIME is the time (in hh.mm.
TSIDTAC Report Date Time Activity Report Example C.P.U. NO.
TSIDUTL Reports TSIDUTL Reports Display ALL, Dataset Name Sequence The Display ALL, SEQ=DSN report gives you a detailed listing of all datasets in dataset name sequence. Each dataset is reported at two levels: BIM-EPIC dataset definition (EDD) and version information. BIM-EPIC Dataset Definition The first two lines for each dataset (beginning with the name) provide the dataset definition. The field titles are listed on these two lines. SID is the system ID. UID is the user ID.
TSIDUTL Reports LAST ACCESS JB NAME is the name of the last job that accessed this version. LAST ACCESS DATE is the date the version was last accessed. COUNT USE is the number of times the tape has been opened since it has contained this version. CLEAN DATE is the last clean date of the tape. If the dataset is a disk dataset, the display appears in the following format: EXT=starting address/allocation.actual usage TOTAL USE is the total number of times the tape was opened since the last cleaning.
TSIDUTL Reports TSIDUTL ALL,DSN Report Example TSIDUTL= 6.01.00 TIME 13.42.37 D A T A S E T M A N A G E M E N T S Y S T E M PAGE 2 DSPLY ALL,SEQ=DSN DATE 12/04/1997 SERIAL VER. REEL ---CREATION----EXPIRE BLOCK ---LAST ACCESS--USE CLEAN USE NO NO /EXT JB NAME DATE DATE TIME TP PT CUU COUNT JB NAME DATE COUNT DATE TOTAL VLT SLT ABSENTEE.TEMP SID= UID= RET= 0 CYC= 2 WORK REBLK=OPT REC= 1700 BLK=22100 DLA= 0 POOL=DISK02 EXT=0000060.0000030 SEC=000 ALR=0000000 DUMMY0 1 1 ABMSETUP 07/08/1997 07/08/1997 11.
Volume Serial Number and Vault Sequences Volume Serial Number and Vault Sequences Description This report lists tape datasets. Each tape volser is listed along with data for the version the tape contains. Dataset definitions are not listed. The first field listed is the version's dataset name. Refer to "Version Data" under "Display ALL, Dataset Name Sequence" for an explanation of the other fields contained in this report. Example TSIDUTL= 6.01.00 TIME 13.42.
Volume Serial Number and Vault Sequences Expiration Date, Creation Date, and Creation Job Sequences Each version is listed with all version data. Dataset definitions are not listed. The first field listed is the version's dataset name. Refer to "Version Data" under "Display ALL, Dataset Name Sequence" for an explanation of the other fields contained in this report. Display Active This is a detailed report listing the active versions of each dataset.
Volume Serial Number and Vault Sequences Display PULL Report This report lists only the most current version for each dataset. The fields in this report are described under "Display ALL, Dataset Name Sequence". Example TSIDUTL= 6.01.00 TIME 13.42.37 D A T A S E T M A N A G E M E N T S Y S DSPLY PULL,SEQ=DSN SERIAL VER.
Display Vault Report Display Vault Report Description This report lists the vault and slot locations of all tapes located in offsite vaults. Refer to "Version Data" under "Display ALL, Dataset Name Sequence" for an explanation of the fields contained in this report. Example TSIDUTL= 6.01.00 TIME 13.42.37 D A T A S DSPLY VAULT SERIAL VER. REEL ---CREATION----NO NO /EXT JB NAME DATE AR.PROD.NCL.ELME3BKP.GVEXPORT.OFFSITE 090783 1 1 1996 01/26/1997 AR.PROD.NCL.ELME3BKP.GVEXPORT.
Display Scratch Report Display Scratch Report This report lists scratch tapes along with data specific to the version the scratch tape contains. Refer to "Version Data" under "Dataset Name Sequence" for an explanation of the fields contained in this report. Description Example TSIDUTL= 6.01.00 TIME 13.42.37 ADFIL.BKUP ALERT.AUDIT.HIST BUD.ACASH.BKUP BUDGET.SQLBKUP CASH.BUD1.BKUP CONHIST.BACKUP CONSTR.BACKUP CONSTR.JOURNAL.BK ELECTRIC.METER.BK EPIC.DBA.WORK1 EPIC.DISK01.BKUP EPIC.DISK01.BKUP EPIC.DISK01.
Projected Scratch (PSCRATCH) Report Projected Scratch (PSCRATCH) Report Description This report lists all tapes that becomes scratch tapes by the specified date. It also reports current DSN Catalog utilization statistics. The projected date you requested is shown next to the report title PSCRATCH and written in Julian format. For instance PSCRATCH 96001 indicates a projected scratch date of January 1, 1996. At the end of the report, message EP119 is issued to report on DSN Catalog utilization.
TSIDVLT Reports TSIDVLT Reports Description TSIDVLT produces two reports listing tapes which should be moved. One is a Picking List which is sorted by the tape's current location. The other is a Distribution List which is sorted by the tapes' new destination. Both reports list the current location of tape reels and their new location. They are designed to assist vault workers in the physical movement of tapes from vault to vault. To produce these reports, see 13-8 in this manual.
TSIDVLT Reports Vault Movement Report Example TSIDVLT DATE 12/11/1997 ----------F R O M--------VAULT INFORMATION 1 VAULT 1 1 VAULT 1 1 VAULT 1 1 VAULT 1 1 VAULT 1 TSIDVLT DATE 12/11/1997 ----------F R O M--------VAULT INFORMATION 2 VAULT 2 2 VAULT 2 2 VAULT 2 2 VAULT 2 2 VAULT 2 2 VAULT 2 2 VAULT 2 TSIDVLT DATE 12/11/1997 ------------T O----------VAULT INFORMATION 1 VAULT 1 1 VAULT 1 1 VAULT 1 1 VAULT 1 1 VAULT 1 TSIDVLT DATE 12/11/1997 ------------T O----------VAULT INFORMATION 2 VAULT 2 2 VAULT 2 2 VAULT
Master Index BOOK CODES: (IS) Installation and System Guide (UR) User Reference A - - - suffix (UR) 1-14, 1-31 - - suffix (UR) 1-14, 1-31 $ $$$ datasets (UR) 7-31 $$BFCMUL (IS) 2-5 $DEFPROF user profile (UR) 2-12 $DEFSEC security profile (UR) 2-7, 2-8 $EPIC security profile (UR) 2-7, 2-8 $EPIC user profile (UR) 2-12 $JOBEXIT user exit (IS) 2-65 $SELECT file (IS) 3-15, 3-23 & &&dsname (UR) 6-23 &dsname (UR) 6-23 &n parameter (UR) 9-12 * ** DSN DELETED ** (UR) 1-35, 2-29, 2-46, 3-22 **** AUTO CATALOGUE *
Master Index ACLEJECT command (IS) 6-5 ACLIBM configuration option (IS) 5-8 ACLLeveling (IS) 5-59 ACLLIB configuration option (IS) 5-8 ACLLVLOO configuration option (IS) 5-9 ACLMEM configuration option (IS) 5-9 ACLOFFL control statement (IS) 2-27 ACLONL control statement (IS) 2-28 ACLOPT configuration option (IS) 5-9 ACLRECS configuration option (IS) 5-9 ACLSRVRI configuration option (IS) 5-10 ACLSRVRM configuration option (IS) 5-10 ACLSRVRO configuration option (IS) 5-10 ACLSRVRS configuration option (IS)
(UR) = User Reference Attention Routine BIM-EPIC Dispatcher (IS) 5-53 Attention Routine commands (UR) 12-5 AUTOATT configuration option (IS) 3-2, 5-11 AUTOATT configuration option (UR) 1-29 Autoattach AUTOATT (IS) 2-94, 5-11 configuration options (IS) 3-2 for VM/ESA 370 (IS) 3-41 for VM/ESA Version 1 Release 1.
Master Index special options (UR) 1-22 starting (IS) 5-2 system files (IS) 2-12 TLBL enhancements (UR) 5-2 upgrading from previous release (IS) 2-3 using JCL (UR) 1-36 utility programs (UR) 8-1 vaulting (IS) 6-38 BIM-EPIC dataset definitions allocation by logical records (UR) 1-14 automatic purge (UR) 1-26 block size (UR) 1-10 CISIZE (UR) 1-14 comment (UR) 1-9 creating (UR) 2-23 cycles retention (UR) 1-11 dataset name (UR) 1-9 days after last access (UR) 1-11 deleting (UR) 2-29, 2-39, 3-22 disk pool name (
(UR) = User Reference CATALOG command (UR) 2-24, 2-47, 3-12 Catalog maintenance SCRATCH (UR) 2-46 Catalog management ADD (UR) 2-34, 2-40, 3-8 CAPACITY (UR) 3-11 CATALOG (UR) 3-12 CATALOG (UR) 2-24, 2-47 CLEAN (UR) 3-18 CLEAN (UR) 2-45 CLOSE (UR) 3-19 CLOSE (UR) 2-38 CYCLE (UR) 2-51, 3-20 DELETE (UR) 3-22 DELETE (UR) 2-29, 2-39 DEQ (UR) 3-23 DISPLAY (UR) 3-24 DISPLAY (UR) 2-21 ENQ (UR) 3-27 functions (UR) 3-3 LOCK (UR) 3-28 LOCK (UR) 2-26, 2-35 MCATALOG (UR) 3-29 MOVE (UR) 3-30 MOVE (UR) 12-22 online See On
Master Index Library Management Feature (IS) 2-67 TSIDACC2 (UR) 4-5 COBOL copybook (UR) 11-10 Coding DD statements (UR) 6-2 Combining DSN Catalogs (IS) 6-70 Command help (UR) 2-16 Command syntax xi, x Comment (UR) 1-9 Common work datasets deleting (UR) 1-21 retention (UR) 1-21 Common work datasets (UR) 7-31 Compatibility with other software (IS) 2-8 Compiler work datasets (UR) 7-31, 7-33 Concatenating not eligible for dataset drop (UR) 6-4 Concatenating datasets DD statements (UR) 6-3 DLBL option E (UR) 5-
(UR) = User Reference JCLAC (IS) 5-20 JCLLANG (IS) 5-20 JCLLANG (UR) 9-1 JCLOPT (IS) 5-20 JCLOVRDE (IS) 5-20 JCLOVRDE (UR) 6-9, 6-17 JOBACCT (IS) 5-20 JOBACCT (UR) 11-1 JQNAME (IS) 5-20 JQWARN (IS) 5-21 JQWMSG (IS) 5-21 Memorex ATL (IS) 5-63 MINDEX (IS) 5-21 MINRET (IS) 5-21 MINRET (UR) 1-4 MODE (IS) 5-21 MODE (UR) 1-30 MSG088 (IS) 5-22 MULTCPU (IS) 2-68, 5-22 NCATDSK (IS) 5-22 NCATDSK (UR) 1-4, 1-20 NOGVIS (IS) 5-23 ONLREWCD (IS) 5-23 OPTI-TAPE ACL support (IS) 5-73 overriding (IS) 6-27 PASSWD (IS) 5-23 P
Master Index tape volume labels (UR) 1-30 Creation date changing (UR) 3-37 report listing (UR) A-30 Creation date (UR) 1-18 Creation job changing (UR) 3-37 report listing (UR) A-30 Creation job (UR) 1-18 Creation time (UR) 1-18 Cross-Reference Report (UR) 12-23 Cross-Reference Reports input to TSIDBRP (UR) 11-3 Cross-Reference Reports (UR) A-8 CTL control statement (IS) 2-32 Current condition code See Job management control language Current utilization, displaying (UR) 3-11 Customer support xii, xi Customi
(UR) = User Reference ABSTR parameter (UR) 6-30 additional parameters (UR) 6-2 allocation by logical record (UR) 6-30 ALX parameter (UR) 6-30 AMORG parameter (UR) 6-12 AMP (UR) 6-7 AMP parameter (UR) 6-12 BLKSIZE parameter (UR) 6-13 BUFSP parameter (UR) 6-12 catalog override example (UR) 6-9 cataloging (UR) 7-18 CATLG parameter (UR) 6-17 CLOSE parameter (UR) 6-24 CONDCAT parameter (UR) 6-17, 7-64 CONTIG parameter (UR) 6-30 continuations (UR) 6-3 CYL parameter (UR) 6-30 DATA parameter (UR) 6-39 dataset drop
Master Index Default profiles $DEFPROF (UR) 2-12 $DEFSEC (UR) 2-7 $EPIC (UR) 2-7, 2-12 user (UR) 2-12 Defaults density (UR) 1-12 disk pool (UR) 1-19 pools (UR) 1-14 security profiles (UR) 2-7 DEFEXT configuration option (IS) 5-17 DEFEXT configuration option (UR) 1-20 Define an EDD panel (UR) 2-23 DEFINE command (UR) 2-5 Defining datasets (UR) 7-5 EDDs (UR) 2-23 vault locations (IS) 6-39 vaulting methods (IS) 6-40 DEFPOL configuration option (IS) 5-17 DEFPOL configuration option (UR) 1-14, 1-20 DEFTPL confi
(UR) = User Reference Display PULL, DSN report listing (UR) A-30 Display scratch report listing (UR) A-33 Display vault report listing (UR) A-30 Displaying DSN Catalog entries (UR) 3-24, 4-2 EDDs (UR) 2-19, 2-22 online VTOC (UR) 13-11 tape information (UR) 2-42 tapes required by a job (IS) 6-53 version attributes (UR) 2-33 version information (UR) 2-30 VTOC entries (IS) 6-56 VTOC entries (UR) 1-31, A-15 Distribution tape loading library modules (IS) 2-12 DITTO (IS) 5-32 DITTO (UR) 7-35, 7-47 DL/1 datasets
Master Index version information (UR) 1-6 DSN Catalog (UR) 1-3 DSN Catalog entries (UR) 1-3, 2-41 DSN DD parameter (UR) 6-22 DSN parameter (UR) 6-7 DSN/JOB Cross-Reference Report (UR) 11-6, A-8 DSNAME (IS) 6-11 DSNAME configuration option (IS) 5-18 DSNWARN configuration option (IS) 5-18 DSNWMSG configuration option (IS) 5-18 DSORG DD parameter (UR) 6-14 DSPLY command VAULT (UR) 12-21 VLT (UR) 12-21 DSPLY command (IS) 6-7 DSPLY command (UR) 4-2 DTF names default dataset name (IS) 5-32 excluding from BIM-EPI
(UR) = User Reference in CICS (UR) 10-11 standard processing subroutines (UR) 10-9 Exiting Online Manager (UR) 2-4 TOJA (UR) 11-15 Expiration LABEL parameter (UR) 6-25 Expiration date changing (UR) 3-37 overriding (UR) 1-25 report listing (UR) A-30 EXPORT (UR) 7-45 EXTEND/VSE start before BIM-EPIC (IS) 2-8 Extending a tape MOD subparameter (UR) 6-15 Extent statement reusing space (UR) 7-10 Extent statements overriding (UR) 7-8 EXTENT statements controlled dataset (UR) 7-25 overriding EDD size (UR) 5-11 req
Master Index Holding drive assignment with TLBL option 8 (UR) 57 HSC pool definitions (IS) 5-72 I I option (UR) 5-11 IBL ACL requirements (IS) 2-5 IBM ACL ERD (IS) 2-25 IBM ACL support activating and deactivating (IS) 5-60 IBM utilities checkpoint/restart (UR) 7-54 DITTO (UR) 7-47 IBM utilities (UR) 7-35 IDCAMS backup and restore (UR) 7-43 example (UR) 6-27 import and export (UR) 7-45 REPRO (UR) 7-44 IDCAMS (UR) 7-35 IGNORE (UR) 7-60 Ignoring datasets DD statements (UR) 6-41 IJSYS files (UR) 7-7 IJSYSDR (
(UR) = User Reference GOTO (UR) 9-7, 9-9 HOLD (UR) 9-5 NAME (UR) 9-7 OR (UR) 9-9 RESET (UR) 9-13 SETC (UR) 9-11 SETG (UR) 9-11 TIME (UR) 9-5 TYPRUN (UR) 9-6 Job accounting activation (IS) 2-94 by CPU (UR) A-24 by CPU and by job (UR) A-13 by date and time (UR) A-24 database (UR) 11-13 database creation (IS) 2-85 installation (IS) 2-85 online installation (IS) 2-84 POWER (UR) 7-48 supervisor requirements (IS) 2-5 TOJA installation (IS) 2-87 TSIDJAC (UR) 11-8 TSIDJLD (UR) 11-10 TSIDTAC (UR) 11-9 Job accountin
Master Index Listing tapes to be moved (UR) A-35 Listing the datasets to be backed up (UR) A-19 Listing the datasets to be offloaded (UR) A-19 LMS pool definitions (IS) 5-67 Local Version Vector Table (IS) 3-15, 3-23 LOCALMOD disk (IS) 3-10, 3-20, 3-27 LOCK command (UR) 2-5, 2-26, 2-35, 3-28 Locked status (UR) 1-16 Locking EDD (UR) 2-26 version (UR) 2-35 Locking a dataset or version (UR) 3-28 LOG option (UR) 3-4 Logging VSAM datasets (UR) 7-28 Logical IOCS (UR) 1-17 LOGSRC option (UR) 5-4 LUB allocation di
(UR) = User Reference expiration date (UR) 3-37 security profiles (UR) 2-8 standard labels (IS) 2-58 tape modes (IS) 2-61 version display format (UR) 2-14 Modifying VSE labels TSIDGLB and TSIDPLB (UR) 8-21 Mounting tapes for output uncontrolled (UR) 12-7 MOVE command (UR) 2-43, 3-30 MOVESER control statement (UR) 12-20 MOVESLT control statement (UR) 12-20 Moving JCL (UR) 6-1 Moving the DSN Catalog See Maintenance procedures Moving the Recorder File See Maintenance procedures MSES/E service procedures (IS)
Master Index VTAM access (IS) 2-71 Online Manager (UR) 1-7 Online VTOC displays (UR) 13-11 Onloaded datasets listing (UR) A-21 Onloading datasets (UR) 13-27 ONLREWCD configuration options (IS) 5-23 OPEN command TSIDASS (UR) 8-2 OPEN not issued (UR) 7-35 OPEN parameters (UR) 8-3 Open version (UR) 1-16 Operating system requirements (IS) 2-5 Operator console (IS) 6-29 Operator console commands (UR) 12-5 OPT block size (UR) 6-13 OPTION control statement special options (IS) 5-29 OPTION control statement (IS) 5
(UR) = User Reference POOL-x (IS) 5-67 POOL-x (UR) 2-40 Posted events See Event posting Post-installation procedures (IS) 2-91 POWER queued jobs (UR) 10-4 POWER (IS) 2-9 POWER job accounting (UR) 7-48 POWER PDISPLAY,POFFLOAD, Printer/Punch Tape Spooling (UR) 7-49 Pre-4.
Master Index EDD block size (UR) 1-10 REC control statement (IS) 6-21 Recatalog a deleted version (UR) 3-8 RECMOVEn SAMPJOB (IS) 4-7 RECORD configuration option (IS) 5-23 RECORD configuration option (UR) 1-27, 11-1 RECORD control statement (IS) 5-50 Record length LRECL DD parameter (UR) 6-14 Recorder activating (IS) 5-45 activation (IS) 2-94 deactivating (IS) 5-45 Recorder File BACKUP (IS) 5-46 comments (UR) 1-27 configuration options (UR) 1-27 creating (IS) 2-17 creation of job accounting database (IS) 2-
(UR) = User Reference TSIDOFL (UR) A-20 TSIDONL (UR) A-21 TSIDPRV (UR) A-22 TSIDSDS (UR) A-23 TSIDTAC (UR) A-24 TSIDUTL (IS) 6-7 TSIDUTL (UR) 4-2 TSIDVLT (UR) A-35 vaulting cross-reference (UR) 12-18 Vaulting Cross-Reference (UR) A-22 Vaulting Cross-Reference Report (UR) 12-23 VTOC (UR) 13-7 REPRO (UR) 7-44 Request handling (IS) 5-53 Requirement for DTFDA datasets (UR) 7-10 Requirements, operating system (IS) 2-5 RERUN configuration option (IS) 5-23 Resequencing dataset extents (UR) 13-5 Resequencing index
Master Index Scanning JCL TYPRUN parameter (UR) 6-3 Scheduling dependent tasks (UR) 10-6 Scheduling programs (IS) 6-50 SCRATCH TSIDUTL (UR) 1-21 SCRATCH command (IS) 6-14 SCRATCH command (UR) 2-5, 2-52, 3-39 Scratch pools synchronizing (IS) 5-67, 5-72, 6-7 Scratch processing work datasets (UR) 1-21 Scratch processing (UR) 1-35 Scratch status (UR) 1-16, 2-41 Scratch tapes (UR) 12-2 Scratched tape versions (UR) 3-24 Scratching ACL cartridges (UR) 3-22 at close with TLBL option 4 (IS) 5-32 at close with TLBL
(UR) = User Reference SORTIN (IS) 5-31 SORTOUT (IS) 5-31 SORTWK datasets LUB allocation (IS) 5-31 SORTWRK datasets (UR) 7-31 SPACE DD parameter (UR) 6-27 Space holder records (UR) 1-43 SPACE parameter example (UR) 6-30 secondary extent size (UR) 13-3 SPACE parameter (UR) 6-8, 6-30 Space requirements (IS) 2-7 SPACE subparameter (UR) 6-28 Special DD names (UR) 6-5 Special options descriptions (IS) 5-31 EPS022 (UR) 7-47 EPS043 (UR) 12-4 Special options (IS) 5-29 Special terms xi, x Specifying DD statements (U
Master Index SYSCHK statements unsupported (UR) 6-5 SYSCKEOV statements unsupported (UR) 6-5 SYSID (IS) 6-15 SYSIN statements (UR) 6-5 SYSIPT (UR) 7-56, 7-59 SYSIPT data JMCL parameter (UR) 9-5 SYSLNK (UR) 7-33 SYSLST (UR) 7-56, 7-59 SYSMDUMP statements (UR) 6-5, 6-6 SYSnnn DD parameter (UR) 6-27 SYSnnn subparameter (UR) 6-29 SYSOUT parameter (UR) 6-6, 6-38 SYSOUT statements unsupported (UR) 6-5 SYSPCH (UR) 7-56, 7-59 SYSPRINT statements unsupported (UR) 6-5 SYSSTORE macro (IS) 3-22, 3-28 System datasets D
(UR) = User Reference manually controlled vaulting (UR) 12-22 moving to next vault (UR) 12-20, A-35 open processing (UR) 1-40 open status (IS) 5-31 open status (UR) 1-22 printing dataset labels (UR) 12-16 purging (UR) 2-39, 2-44 recording cleaning (UR) 2-45 reporting vault locations (UR) 12-21 required by a job (IS) 6-53 revolving (UR) 12-3 scratch (UR) 12-2 scratching (UR) 3-22 synchronizing scratch pools (IS) 6-7 use count (UR) 3-18 using Online Manager (UR) 2-40 volume labels (UR) 1-30 Tapes, output con
Master Index CAT (IS) 6-21 examples (IS) 2-23 REC (IS) 6-21 TSIDCDK (IS) 4-6, 4-7, 6-21 TSIDCHK (UR) 10-6, 10-8, 10-9 TSIDCLN (IS) 2-92 TSIDCLOC (UR) 10-5, 10-11 TSIDCMRG (IS) 6-70 TSIDCREL (UR) 10-4, 10-11 TSIDCUNL (UR) 10-7, 10-11 TSIDDEB BIM-EPIC upgrade (IS) 2-3 deactivating/reactivating BIM-EPIC (IS) 6-26 exceptions (IS) 6-27 reporting capabilities (IS) 6-25 Summary Report (IS) 6-30 TSIDDEB (IS) 5-2, 5-44, 6-24 TSIDDEL (UR) 8-7 TSIDDIS (UR) 12-24, A-11 TSIDDMP (UR) 7-47, 8-16 TSIDDTD (UR) 7-47, 8-9, 1
(UR) = User Reference report (UR) A-22 report examples (UR) A-22 TSIDPRV (UR) 12-18, 12-23 TSIDREC.
Master Index STK ACL support (IS) 5-68 TVTO (UR) 1-31, 13-11 TVTO installation (IS) 2-84 TVTO transaction (IS) 2-81 TYPEFLE=WORK control on disk only (UR) 1-5 DLBL option N required (UR) 5-11 do not use DLBL option F (UR) 5-10 secondary allocation unavailable (UR) 13-3 TYPEFLE=WORK (IS) 5-33 TYPEFLE=WORK (UR) 7-32 TYPRUN parameter SCAN (UR) 6-3 TYPRUN parameter (UR) 9-6 U UIN (IS) 5-31 UIN (UR) 7-7 UNCDSK configuration option ISAM limitation (UR) 7-26 uncontrolled DA datasets (UR) 7-25 UNCDSK configuratio
(UR) = User Reference VATTACH (IS) 3-2 VATTACH (UR) 1-29 VATTACH, VDETACH See Autoattach Vault locations (UR) 12-17 Vault method number (UR) 1-13 Vault Method Report (UR) 12-23 VAULT parameter (UR) 12-21 VAULT sequence (UR) 12-21 VAULTDEF macro Also see Vaulting assembling and linking (IS) 6-41 AVAULTS (UR) 12-22 VAULTDEF macro (IS) 6-39 VAULTDEF macro (UR) 12-17 Vaulting assembling and linking macros (IS) 6-41 assigning vaulting methods (UR) 12-19 creating methods (IS) 6-40 creating vaults (IS) 6-39 cross
Master Index VM configuration option CP commands (UR) 9-20 VM configuration option (IS) 3-2, 5-27 VM Directory HSC server entry (IS) 5-69 LMS server entry (IS) 5-64 VOL DD parameter (UR) 6-7 VOL parameter (UR) 6-35 VOL1 labels (UR) 12-2 Volser TSIDLBL (UR) 12-14 VOLSER statements TSIDINIT (UR) 12-11 VOLUME DD parameter (UR) 6-35 VOLUME parameter number of secondary extents (UR) 13-3 Start Track 1 datasets (UR) 6-27 VOLUME parameter (UR) 6-8 Volume serial number vault sequences (UR) A-29 Volume serial numbe
(UR) = User Reference MOVEs nullified by auto vaulting (UR) 3-30 MULTCPU=YES to share catalog (IS) 5-22 Must have QDAS Share File on shared volume (IS) 2-53, 5-55, 6-19 No concatenation code on last label statement (UR) 7-61 No other job or CPU during FASTRS (IS) 6-11 QDAS must be active for all sharing machines (IS) 5-52 RENAME won’t check for duplicate names (IS) 662 Reset Recorder whenever catalog backed up (IS) 42 SHARE=YES to share among physical CPUs (IS) 5-24 Tape reuse before scratch (UR) 1-22 TSID
