User Reference Version 7 Release 1B Disk/Tape Management Tool Copyright © 2006 by CSI International, Inc. BIM-EPIC is an proprietary product of CSI International, Inc. It cannot be reproduced, changed, copies, or stored in any form (including, but not limited to, copies on magnetic media) without the express prior written permission of CSI International, Inc.
Contents Trademark Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x Contacting BIM-EPIC Technical Support . . . . . . . . . . . . . . . . . . xiii Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv Chapter 1 Introduction Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Tape Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33 Managing Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34 Starting and Stopping Partitions. . . . . . . . . . . . . . . . . . . . . . . . . 1-35 Creating Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36 Activating BIM-EPIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37 Scratching or Deleting Datasets . . . . . . . . . . . . . . . . .
Maintaining Tape Volume Information . . . . . . . . . . . . . . . . . . . 2-48 Purging a Tape Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 Recording Tape Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51 Understanding Retention Concepts . . . . . . . . . . . . . . . . . . . . . . 2-52 Setting Dataset Definition Retention . . . . . . . . . . . . . . . . . . . . . 2-53 Modifying Dataset Definition Retention . . . . . . . . . . . . . . . . . .
SCRATCH Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48 TRANSFER Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50 UNLOCK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52 UPDATE Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54 Chapter 4 BIM-EPIC TLBL and DLBL Statements TLBL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 TLBL Options . . . . . . . .
Chapter 7 Running Jobs With BIM-EPIC Using Unsupported Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Using JCL and the DSN Catalog . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Using TLBL and DLBL Statements for Input . . . . . . . . . . . . . . . 7-4 Defining Datasets with TBL, DBL and DD Statements . . . . . . . 7-5 Naming Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Using LUB Allocation and the ASSGN Statement . . . . . . . . . .
Identifying VSE/ICCF and Interactive Partition GETVIS Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-56 Using the COBOL II Library Management Feature . . . . . . . . . 7-57 Restarting From a Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59 Choosing the Device Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61 Controlling System Datasets with VSE Device Independence . 7-64 Using Dummy Datasets and ASSGN IGNORE. . . . . . . . .
Chapter 10 BIM-EPIC Job Scheduling Scheduling Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Event Posting and Release of Matching Jobs (TSIDREL and TSIDCREL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 Event Posting (TSIDLOC and TSIDCLOC) . . . . . . . . . . . . . . . 10-4 Event Checking (TSIDCHK and TSIDCCHK). . . . . . . . . . . . . 10-5 Event Deletion (TSIDUNL and TSIDCUNL). . . . . . . . . . . . . .
VTOC Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7 VTOC Listings (TSIDLVT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8 Online VTOC Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11 Offload System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16 Selecting Datasets To Be Offloaded (TSIDOFD) . . . . . . . . . . 13-18 Offloading and Backing Up Datasets (TSIDOFL). . . . . . . . . .
Trademark Information 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® International Business Machines Corporation (IBM®) CMS IBM® Computer Associates International, Inc.
Preface Preface Most BIM-EPIC features operate in conjunction with controlled datasets, which BIM-EPIC catalogs and maintains. Controlled datasets are assumed in the discussion of each feature. Uncontrolled datasets are noted explicitly. BIM-EPIC configuration options govern how BIM-EPIC performs. Default options are assumed in the main body of this manual. Variations caused by non–default options are described in the BIM-EPIC Installation and System Guide.
Preface Element Example Description Square brackets [,PARM1=(value1, value2,...valuen)] information within square brackets indicates optional information. If the optional information is provided, do not include the brackets. Parentheses (value1,value2, ...valuen) Parentheses indicate required subparameters or values grouped together within a single parameter. If a parameter contains only one value, you do not need to include parentheses in your command or control statement.
Preface optional, valid values, and any default setting. Parameter tables display information in the following format: Parameter Required? Valid Entry Default value Yes 1 to 99 characters ----- PARM1 No See syntax VALUEA One of the following two is required: FUNCTION ----- ----- ----- NOFUNCTION ----- ----- ----- No YES or NO YES DOTHIS xii Connectivity Systems, Inc.
Contacting BIM-EPIC Technical Support Contacting BIM-EPIC Technical Support Normal Business Hours Support You can reach BIM-EPIC Technical Support at any time. Our normal operating hours are from 6:00 AM to 4:00 PM Pacific Time. In addition to our regular customer support, we have technicians available for emergency support 24 hours a day, 7 days a week. The phone number to call for emergency support is listed on the www.bimoyle.com home page.
Contacting BIM-EPIC Technical Support Step 2 Action If your problem is classified in category 1, 2, 3, or 4, you will need the following: A current TSIDDEB Summary Report. This contains details concerning BIM-EPIC and VSE environment. The CONSOLE LOG with our messages turned on. This provides a step-by-step history of the situation. The JCL, including expansions of // EXEC PROC and * $$SLI statements.
Related Publications Related Publications Description The following documents describe important BIM-EPIC technical information. They assume appropriate knowledge of the relevant IBM operating system. 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 BIM-EPIC User Reference Guide.
Related Publications xvi Connectivity Systems, Inc.
1 Introduction This chapter is an overview of the BIM-EPIC product. The BIM-EPIC Disk/Tape Management System User Reference manual is written to include all levels of programmer expertise. Even if you are very familiar with the topics discussed in this chapter, we encourage you to review this material, since several topics in this chapter contain information unique to BIM-EPIC.
Configuration Options BIM-EPIC Fundamentals Configuration Options Description 1-2 BIM-EPIC provides configuration options which allow you to customize many aspects of your processing. Consult your systems programmer or the BIM-EPIC Installation and System Guide if you have a question about a specific configuration option. Connectivity Systems, Inc.
Controlled Datasets Controlled Datasets Description BIM-EPIC controls datasets best when the dataset has a Dataset Name (DSN) Catalog entry. The information contained in a DSN Catalog entry determines how BIM-EPIC processes a dataset. When a dataset is controlled by the DSN Catalog, the following is available.
Start Track 1 Datasets Start Track 1 Datasets Description A Start Track 1 dataset is a disk dataset that is defined by specifying the number 1 (one) in the relative track field of the VSE EXTENT statement. For example: // DLBL MYFILE,’ANY.FILE’ // EXTENT SYS005,SYSWK3,1,0,1,20 In the above example, BIM-EPIC allocates 20 tracks to the MYFILE dataset since the number 1 is in the relative track field. Using any other number in relative track field indicates that BIM-EPIC will not handle the allocation.
Start Track 1 Datasets Configuration Options User Reference Start Track 1 datasets are affected by the AUTOCAT, CATRT1, MINRET, NCATDSK, and STRTRK configuration options. In addition, the datasets can be affected by other configuration options that apply to disk. See the BIM-EPIC Installation and System Guide for additional information. Connectivity Systems, Inc.
Other Types of Datasets Other 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 extents currently in use, even if the dataset contains multiple secondary allocations. BIM-EPIC controls TYPEFLE=WORK files on disk only. BIM-EPIC cannot control TYPEFLE=WORK files on tape.
Dataset Name Catalog Entries BIM-EPIC Datasets Dataset Name Catalog Entries Description The Dataset Name (DSN) Catalog information controls dataset actions based on information contained in the DSN Catalog. All information pertaining to a 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.
Dataset Name Catalog Management Dataset Name Catalog Management Description Most updates to the Dataset Name (DSN) Catalog are made automatically as datasets are processed. However, sometimes you may want to add a special dataset or change the defaults you have supplied for an existing BIM-EPIC dataset definition. This can be done using either the BIM-EPIC Online Manager or TSIDMNT. The BIM-EPIC Online Manager (EOM) is a panel-driven catalog management facility.
Dataset Name Catalog Maintenance Dataset Name Catalog Maintenance Description The Dataset Name (DSN) Catalog must be maintained regularly. Maintenance includes regular backups and scratch runs, as well as periodic re-indexing. Catalog maintenance is done using TSIDUTL. See the BIM-EPIC Installation and System Guide for additional information. User Reference Connectivity Systems, Inc.
BIM-EPIC Dataset Definition Components BIM-EPIC Dataset Definitions BIM-EPIC Dataset Definition Components Description The BIM-EPIC dataset definition (EDD) consists of several components. The following sections describe each component. Dataset Name BIM-EPIC uses the dataset name in the DSN Catalog to identify a dataset as a controlled dataset. Each time a controlled dataset is opened or closed, BIM-EPIC participates in the processing of the dataset.
BIM-EPIC Dataset Definition Components ! WARNING: Encrypted dataset versions must not be deleted from the DSN Catalog. Once a dataset version is deleted, its data cannot be decoded, making the dataset version is unreadable. In addition, once the dataset is cataloged, the encryption password cannot be added, changed, or deleted. User ID and System ID User ID and system ID assist in grouping tape datasets for reporting and scratching purposes.
BIM-EPIC Dataset Definition Components retained for the periods indicated in the Retention Days field and the DLA Retention field, BIM-EPIC can retain more versions than the number specified in the Cycles Retention field. Cycles 5 and Retentions Days 0 will insure that 5 versions are always present. Cycles 5 and Retention Days 60 may result in more than 5 versions being present.
BIM-EPIC Dataset Definition–Tapes BIM-EPIC Dataset Definition–Tapes Description BIM-EPIC dataset definitions (EDD) for tapes consist of several components. The following sections provide an overview of each component. Standard Label The label specifies whether an output tape dataset is created on a labeled tape or an unlabeled tape. Tape Density Tape density specifies which density to use when creating a tape dataset.
BIM-EPIC Dataset Definition–Tapes Revolving Tape Datasets When you specify Revolving Tapes=YES for a dataset, you establish an exclusive relationship between a dataset and the tape serial numbers the dataset uses. A revolving tape volume can contain one version of a specific dataset and can be written only on specific tape volumes. A revolving tape volume cannot be used in an Automated Cartridge Library (ACL).
BIM-EPIC Dataset Definition–Disks BIM-EPIC Dataset Definition–Disks Description BIM-EPIC dataset definitions (EDD) for disks consist of several components. The following sections provide an overview of each component. CISIZE CISIZE 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 written on FBA devices. CISIZE and block size are mutually exclusive.
BIM-EPIC Dataset Definition–Disks Allocation by Logical Records Allocation by logical records (ALR) automatically calculates the primary extent size. ALR overrides the primary extent size, if a primary extent size has been previously set. BIM-EPIC calculates the primary extent size based on: record length 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.
Versioning Datasets BIM-EPIC Versioning and Retention Versioning Datasets Description As each version of a dataset is created, BIM-EPIC automatically records attributes specific to that version in the DSN Catalog. This section describes the attributes that are recorded. Version Number The version number identifies the version of a dataset. The current or most recently created version is always version 1.
Versioning Datasets Status Type Indicator Conditional C Catalog Description Indicates the version was created with the TESTJOB utility or a conditional catalog option in the JCL. The version is accessible as input only if it is the latest version for the specific dataset. In addition, the version can be accessed only by a job with the same name as the job that created it. To make the version an active version, declare the version closed using Online Manager or TSIDMNT.
Versioning Datasets Extent Number and Address BIM-EPIC records the extent addresses for each disk dataset. This information includes: extent sequence (1 for primary, 2 for the first secondary, and so on) beginning relative track or block number size of the initial allocation amount of allocation used The amount of allocation used is smaller than the initial allocation if the dataset has been truncated.
Versioning Datasets Tape use count and tape error count are kept for each tape while the tape is associated with a version. Both counts start from the last date the tape was cleaned. Current Vault and Slot Location 1-20 The current vault and slot locations are recorded for each tape if the dataset is subject to a vault rotation method. Connectivity Systems, Inc.
Cataloging Datasets Automatically Cataloging Datasets Automatically Description If the new dataset and version are to be controlled, they must have an entry in the DSN Catalog. Dataset entries and version entries can be created automatically for uncontrolled datasets using AUTOCAT and AUTOLOG. In addition, dataset entries and version entries can be created automatically using the DD statement parameter DISP=(x,CATLG). AUTOCAT and AUTOLOG operate globally on all qualifying datasets.
Cataloging Datasets Automatically AUTOLOG AUTOLOG creates a BIM-EPIC dataset definition (EDD) for an input tape dataset that is not already in the DSN Catalog. However, unlike AUTOCAT, AUTOLOG does not automatically catalog any versions to the EDD. You can use AUTOLOG to force standard EP001 MOUNT messages for previously uncontrolled input tape datasets.
Retaining and Scratching Datasets Retaining and Scratching Datasets Description Versions of catalog-controlled datasets must be scratched before their tapes and disk space can be reused. Because BIM-EPIC does not scratch datasets unless specifically instructed to do so, you must provide BIM-EPIC specific instructions.
Retaining Dataset Retaining Dataset Description The 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 TSIDUTL SCRATCH function is executed. Versions are not scratched unless they meet eligibility criteria. A version is not eligible to be scratched until ALL the retention criteria have been satisfied.
Retaining Dataset Example 1 The following is an example of retaining x versions for y days. In the example, 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 the versions were created. The dataset definition specifies: Generation Dataset......YES Retention Days.......100 Retention Cycles.....10 Retention DLA........
Retaining Start Track 1 Datasets Retaining Start Track 1 Datasets Description BIM-EPIC 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 when a new version is created. TSIDUTL SCRATCH does not examine Start Track 1 datasets.
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 occasionally modify retention criteria. You can change retention for new versions, for existing versions, or for the entire dataset. Retention days or an expiration date specified on a TLBL statement, DLBL statement, or DD statement for an output dataset overrides the catalog default.
Purging Dataset Information Purging Dataset Information Description When Automatic Generation Purge (AGP) is enabled, BIM-EPIC automatically deletes DSN Catalog information pertaining to any disk dataset version with a version number that exceeds the cycle retention in the BIM-EPIC dataset definition (EDD). AGP is enabled by setting AGP=YES when creating or updating an EDD in the DSN Catalog.
Recording Dataset Activity Recording Dataset Activity Description The BIM-EPIC Recorder logs control dataset activity to a file, including: All DSN Catalog maintenance transactions, excluding TSIDVLT (vaulting) maintenance All open and close activities of controlled datasets Machine use and job accounting statistics The Recorder file is vital to emergency recovery of the DSN Catalog. The file contains a record of all changes made to the DSN Catalog since the last catalog backup.
Allocating Logical Unit Blocks (LUB) Allocating Logical Unit Blocks (LUB) Description The VSE Logical Unit Blocks (LUB) connects the logical unit (SYS number) in a file definition DTF with the physical device address (cuu) that controls the dataset. When a disk or tape dataset is opened, if the SYS number specified in the program is already in use, the LUB allocation feature assigns logical units for tape and disk devices.
Managing Tape Devices Managing Tape Devices Drive Assignments BIM-EPIC makes and releases drive assignments automatically using the Automatic Volume Recognition (AVR), Autoattach, and Early Drive Release features. Using these features, tape drives are assigned to a partition or virtual machine between open and close only. Performing the assignments in this manner frees up the tape drives between job start and open time or between close time and end-of-job, increasing the availability of the tape drives.
Managing Tape Devices completed, a mount message is sent to the operator. AVR puts the partition in a wait state until the operator responds. Autoattach Autoattach automatically attaches a tape drive to a Guest Virtual Machine (VM), and then AVR assigns the tape drive to the partition. Autoattach adds two new commands to VM: VATTACH corresponds to the IBM ATTACH command. VDETACH corresponds to the IBM DETACH command.
Managing Tape Volumes Managing Tape Volumes Description The BIM-EPIC tape initialization program, TSIDINIT, prevents initializing tapes with duplicate volume serial numbers and adds newly-acquired tape volumes to the DSN Catalog. TSIDLBL creates gummed volume labels for your tapes. Vault management facilities control tape vaulting functions. Tape versions are added to the DSN Catalog automatically as you process datasets. In most circumstances, tapes do not need to be added manually.
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 to use in your installation. Disk pools can include one or more disk volumes. In addition, part of a volume can be allocated to a disk pool. Each disk dataset must be assigned to a disk pool before allocation. Each time a dataset version is written, an allocation is made in that pool.
Starting and Stopping Partitions Starting and Stopping Partitions Description You can stop a partition by entering STOP in response 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 also be stopped and restarted at any time using VSE STOP and VSE START. User Reference Connectivity Systems, Inc.
Creating Reports Creating Reports Description BIM-EPIC programs provide a variety of reports describing tape and disk datasets, storage use, and job accounting. You can create customized reports containing BIM-EPIC data from the DSN Catalog and the Recorder file. See “Customized Reports” for additional information. 1-36 Connectivity Systems, Inc.
Activating BIM-EPIC Activating BIM-EPIC Description BIM-EPIC is available for use if you have performed an IPL on your system or you have deactivated and reactivated BIM-EPIC. Unless specifically instructed not to activate in a particular partition, BIM-EPIC becomes functional when the first OPEN command is issued in the partition. BIM-EPIC does no processing until it is activated. This means that JCL enhancements, such as dataset definition statements, cannot be processed until BIM-EPIC is activated.
Scratching or Deleting Datasets Scratching or Deleting Datasets Description BIM-EPIC provides several methods for scratching datasets. Datasets can be scratched upon request using JCL, Online Manager, TSIDMNT, or TSIDUTL. Regardless of which method you use, the BIM-EPIC scratch process performs the same actions. When BIM-EPIC scratches a disk dataset, three events occur: BIM-EPIC deletes the VTOC entry. The disk space is made available for reuse.
Using Job Control Language (JCL) BIM-EPIC Job Control Language Using Job Control Language (JCL) Description BIM-EPIC changes the way you use job control language (JCL) and offers many enhancements to standard VSE job controls. However, BIM-EPIC may require some changes in order to function properly. Physical Input/ Output Control System Programs that use physical input/output control systems (PIOCS) cause conflicts with tape and disk management programs.
Using Job Control Language (JCL) Depending on the processing situation, it may or may not be desirable to manually scratch the version. 1-40 Connectivity Systems, Inc.
Using Job Control Language Options Using Job Control Language Options Description User Reference Because BIM-EPIC offers DLBL, TLBL, and DD JCL options which VSE cannot process, BIM-EPIC processes these options and then generates the required VSE label information before providing the JCL statement to VSE for processing. Connectivity Systems, Inc.
Using Tape Processing BIM-EPIC Tape Processing Using Tape Processing Description Open processing, end-of-volume processing, and close processing are the most significant BIM-EPIC processing periods. In each case, processing is different for tape than for disk. Open Processing Open processing is the most important processing period. When a tape dataset is opened, BIM-EPIC carries out the following tasks: BIM-EPIC checks the JCL and DSN Catalog to determine if the dataset is tape or disk.
Using Tape Processing End-of-Volume Processing Close Processing BIM-EPIC performs similar steps for end-of-volume (EOV) processing as those performed for open processing. When performing EOV processing, BIM-EPIC gains control and then passes control to VSE. To perform EOV processing, BIM-EPIC carries out the following tasks: BIM-EPIC releases the most recent drive assignment. If Automatch is active, BIM-EPIC detaches the drive from the VSE machine.
Using Disk Processing BIM-EPIC Disk Processing Using Disk Processing Description The tasks performed for disk open, close, and end-of-extent processing are similar to the tasks performed for tape processing. For disk processing, BIM-EPIC must make the space allocation, which is more complicated than finding the correct tape volume. Quick Disk Allocation (QDAS) During every open process, VSE reads the VTOC sequentially, which can require thousands of I/O operations.
Using Disk Processing created. in the DSN Catalog and on the VTOC. For Start Track 1 datasets, BIM-EPIC must read each VTOC in the pool until the old dataset is located. BIM-EPIC decides which pool volume to allocate. BIM-EPIC checks the VTOC or QDAS map for a free extent with sufficient space. If BIM-EPIC cannot locate sufficient space in the pool for the extent, it issues a message and waits for a response from the operator.
Using Disk Processing When BIM-EPIC closes a dataset, it takes the buffer size into account. Using the buffer size and the amount of space left in the extent, BIM-EPIC determines if another extent is needed. If another extent is needed, BIM-EPIC makes the allocation. If VSE runs out of space when writing the buffered records, BIM-EPIC checks the VSE Label Area for another extent. If an extent is not there, BIM-EPIC will cancel the job.
2 BIM-EPIC Online Manager This chapter describes the BIM-EPIC Online Manager. Chapter Contents Using Online Manager Configuring Online Manager Managing Dataset Versions Retaining and Scratching Datasets User Reference Connectivity Systems, Inc.
Cataloging Manually Using Online Manager Cataloging Manually Description There are several reasons for performing manual DSN cataloging and catalog management instead of using automatic cataloging. Automatic cataloging is global in scope, so it will not match the exact requirements of all datasets.
Using Online Manager Using Online Manager Description Primary Option Menu You can access Online Manager using several methods. The following describes the various methods of access. Method of Access Description CICS You can access Online Manager with a CICS EPIC transaction. See the BIM-EPIC Installation and System Guide for information on installing the CICS transaction. If online access is done solely through BIM-FAQS/ASO or CA-FAQS/ASO, installing the CICS transaction is not required.
Using Online Manager Exiting Online Manager 2-4 To exit an online session, select X (Exit) from the Primary Option menu. Connectivity Systems, Inc.
Executing Management Commands Executing Management Commands Description You can execute TSIDMNT commands in command mode, while using Online Manager panels for your catalog management. Procedure To execute TSIDMNT commands: 1 Place the cursor in the panel command area. 2 Type EPIC followed by a space. 3 Place the cursor in the panel command area. 4 Type the normal TSIDMNT command syntax. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for command formats.
Maintaining User Profiles Configuring Online Manager Maintaining User Profiles Description To customize the display for dataset definitions and version information, the Online Manager provides two default profiles containing display layouts and confirmation options. $DEFPROF provides layouts that apply to all users who are not specifically defined to Online Manager. $EPIC provides a fixed-standard layout. You can use either default profile as your model.
Maintaining User Profiles From the User Profiles panel, you can create and modify user profiles to display different formats and confirmation options. Definitions The following describes the profiles displayed in the User Profiles panel. User ID Definition $DEFPROF Provides layouts that apply to all users who are not specifically defined to Online Manager. Procedures $EPIC Unsecured profile. $EPIC, which cannot be modified, is provided by the Online Manager to use as a model.
Customizing Dataset Screen Displays Customizing Dataset Screen Displays Description Procedure The Modify EDD Display panel provides the options that enable you to customize the screen display for BIM-EPIC dataset definitions (EDDs). The Current Display Order area provides the following options: F (Following) moves a field after another field. M (Move) moves a field to a new location. P (Preceding) moves a field before another field. R (Remove) removes a field from the display.
Customizing Dataset Screen Displays User Reference If you need to… Press return to the previous panel F3 accept the new display order F6 scroll to additional User Profile Definition panels F8 move one panel right F11 exit F12 Connectivity Systems, Inc.
Customizing Version Displays Customizing Version Displays Description Procedure The Modify Version Display panel provides the options that enable you to customize the screen display for BIM-EPIC dataset versions. The Current Display Order area provides the following options: F (Following) moves a field following another field. M (Move) moves a field to a new location. P (Proceeding) moves a field to precede another field. R (Remove) removes a field from the display.
Customizing Version Displays You can use function keys to perform certain tasks: User Reference If you need to… Press access the online help for additional information F1 return to the previous panel F3 accept the new display order F6 scroll back to the Modify Version Display panel F7 scroll to the Modify Profile Defaults panel F8 move one panel left F10 move one panel right F11 exit F12 Connectivity Systems, Inc.
Customizing Profile Defaults Customizing Profile Defaults Description The Modify Profile Defaults panel provides options that enable you to customize certain profile defaults. 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. Note: The $EPIC default profile always requests confirmation.
Customizing Profile Defaults You can use function keys to perform certain tasks: User Reference If you need to… Press access the online help for additional information F1 return to the previous panel F3 accept the new display order F6 scroll back to the Modify Version Display panel F7 exit F12 Connectivity Systems, Inc.
Using Online Manager Help Using Online Manager Help Description Procedure The Online Manager provides online help in several formats. These formats include: Panel Help Field Help Command Help Panel Help—Navigation Panel Help—General To access a specific Help format: Format Method Help for Help Select the H (Help) option on the Primary Option menu to obtain a description of the Help system. Panel Help Press F1 at the command line at anytime to display panel-specific help.
Using Online Manager Help Panel IDs Display (I) The following is an example of the Online Flow display showing the panel IDs. TSIO0901.
Searching for Dataset Definitions Searching for Dataset Definitions Description You can use the Search Catalog panel to search for a BIM-EPIC dataset definition (EDD) in the DSN Catalog.
Searching for Dataset Definitions Procedure To search for dataset definitions in the DSN Catalog: Step User Reference Action 1 Type a fully or partially qualified dataset name in the Name field. If you specify a partial dataset name, all EDDs containing that name criteria will display. You can use an asterisk (*) to substitute dataset levels or a question mark (?) to substitute an individual character. 2 Type E or X in the Level field to view selected EDDs.
Managing Dataset Definitions Managing Dataset Definitions Description Procedure The Manage EDDs panel lists BIM-EPIC dataset definitions (EDDs) matching the dataset name or expression you entered in the Search Catalog panel.
Managing Dataset Definitions Manage EDDs Panel The following is an example of the Manage EDDs panel. TSIO0101.Z ----------- BIM-EPIC - Manage EDDs ------------------ USER=SJA COMMAND ===> More: > _ _ _ _ _ _ _ _ _ Dataset Name Width: 25 Cyc Reten BATCH CONVERT OUT BILL BACKUP BILL.REPRINT.FILE BILLING.PAN.ORDER BILRECS BKUP TAPE BLS.REC BUD.ACASH.BKUP BUDGET.SQLBKUP BUDGET.
Displaying a Dataset Definition Displaying a Dataset Definition Description The EDD Information panel displays the BIM-EPIC dataset definition (EDD) attributes. You can update the attributes or create a new definition based on the displayed dataset definition. Procedure To display the EDD Information panel: Step EDD Information Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel.
Displaying a Dataset Definition Using TSIDMNT DISPLAY User Reference BIM-EPIC also provides TSIDMNT DISPLAY to list dataset definitions. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using DISPLAY. Connectivity Systems, Inc.
Creating a Dataset Definition Creating a Dataset Definition Description The Define an EDD panel allows you to create a new BIM-EPIC dataset definition (EDD). If you are using a modeled dataset, the attributes on the Define an EDD panel are the attributes of the modeled dataset. Procedure To display the Define an EDD panel: Step Action 1 Open the Primary Option menu. 2 Type D (Define). 3 Press Enter to open the Define an EDD panel.
Creating a Dataset Definition Step Action 2 Type a dataset name in the Dataset field. BIM-EPIC uses the dataset name as the key to locate a record in the DSN Catalog. Therefore, the dataset name must be unique. Use the Model field when you are defining a new dataset and want to model the new dataset after a previously defined dataset. 3 Update the dataset attributes. Note: Any changes you make on the Create an EDD panel override modeled attributes.
Updating a Dataset Definition Updating a Dataset Definition Description Online Manager provides the Update an EDD panel to enable you to modify BIM-EPIC dataset definitions (EDDs). The attributes displayed on this panel are defaults for all output datasets using the dataset name. Modifications affect subsequent versions only. Procedure To display the Update an EDD panel: Step Update an EDD Panel Action 1 Open the Primary Option menu. 2 Type M (Manage).
Updating a Dataset Definition Procedure To update the attributes for a dataset definition: Step 1 Using TSIDMNT UPDATE User Reference Action Update any attribute for the EDD using one of the following methods: To remove the Disk Pool specification, replace the current value with the word NO. To remove the Primary, Secondary, Max Sec, or Primary ALR value, replace the current value with a zero (0). 2 Press Enter to update the EDD. 3 Press F3 to exit without updating the EDD.
Releasing a Locked Dataset Definition Releasing a Locked Dataset Definition Description Releasing a locked BIM-EPIC dataset definition (EDD) allows the EDD to be used for a one-time output. Once this occurs, the EDD is placed in a locked state. You can release an EDD from the Manage EDDs panel. To permanently release an EDD, use the UNLOCK command. Procedure To access the Manage EDDs panel: Step 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel.
Releasing a Locked Dataset Definition Step Using TSIDMNT RELEASE User Reference Action 2 Type F (Release) to release the dataset definition. 3 Press Enter. BIM-EPIC also provides TSIDMNT RELEASE to allow a one-time use of a locked EDD. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using RELEASE. Connectivity Systems, Inc.
Unlocking a Dataset Definition Unlocking a Dataset Definition Description Unlocking a BIM-EPIC dataset definition (EDD) allows the EDD to be used for output (creating new versions with the EDD name and attributes). You can unlock an EDD from the Manage EDDs panel. Procedure To access the Manage EDDs panel: Step 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel.
Unlocking a Dataset Definition Step Using TSIDMNT UNLOCK User Reference Action 2 Type K (Unlock) to unlock the dataset definition. 3 Press Enter. BIM-EPIC also provides the TSIDMNT UNLOCK command to unlock an EDD. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using UNLOCK. Connectivity Systems, Inc.
Deleting a Dataset Definition Deleting a Dataset Definition Description When you delete a BIM-EPIC dataset definition (EDD), all version information is removed from the DSN Catalog, but tape volume information is kept under the internal-use dataset name ** DSN DELETED ** until the volume serial number is reused or purged. You can delete an EDD from the DSN Catalog using the Manage EDDs panel. Procedure To access the Manage EDDs panel: Step 1 Open the Primary Option menu. 2 Type M (Manage).
Deleting a Dataset Definition Step Using TSIDMNT DELETE User Reference Action 2 Type L (Delete) to delete the dataset definition. 3 Press Enter. BIM-EPIC also provides TSIDMNT DELETE to remove an EDD. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using DELETE. Connectivity Systems, Inc.
Displaying Version Information Managing Dataset Versions Displaying Version Information Description In order to view or modify a dataset version online, you must first locate the dataset entry in the DSN Catalog. Online Manager provides the Search Catalog panel for providing a list of dataset versions that match specific criteria.
Displaying Version Information Search Catalog Panel The following is an example of a Search Catalog panel. TSIO0100.
Selecting a Version from a List Selecting a Version from a List Description The Manage Versions panel lists dataset versions based on the search criteria specified on the Search Catalog panel.
Selecting a Version from a List Procedure To manage a version entry: Step Using TSIDMNT User Reference Action 1 Type the letter of the command you want to execute in front of the version you want to process. You can enter commands for as many entries as you want. 2 Press Enter to invoke the commands entered. 3 Press F3 to exit without performing any commands. BIM-EPIC provides TSIDMNT to manage dataset versions.
Displaying Version Attributes Displaying Version Attributes Description The Version Information panel lists information specific to a dataset version. From the Version Information panel, you can add a new version or display information on associated volumes. Procedure To display version attributes: Step Version Information Panel Action 1 Open the Manage Versions panel. 2 Type I (Information) next to the selected dataset name. 3 Press Enter to open the Version Information panel.
Adding Version Information Adding Version Information Description The Add a Tape Version panel allows you to add a new version to an existing BIM-EPIC dataset definition (EDD) or to add new volume serial numbers to an existing dataset version. Procedure To add a new tape version to a controlled dataset definition: Step Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel. 4 Type the name of the dataset definition in the Name field.
Adding Version Information Add a Tape Dataset Version Panel The following is an example of an Add a Tape Dataset Version panel. TSIO0203.
Locking a Version Locking a Version Description Locking a dataset version prevents the version from being used as input. You can lock a dataset version from any panel that allows general version management. Procedure To access the Manage Versions panel: Step Manage Versions Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel. 4 Type the dataset name and Level V on the Search Catalog panel. 5 Type V (Versions) in the Level field.
Locking a Version Using TSIDMNT LOCK 2-40 BIM-EPIC also provides TSIDMNT LOCK to lock a version. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using LOCK. Connectivity Systems, Inc.
Closing a Version Closing a Version Description It may be necessary to manually close a dataset version if it is in open status or if it is in conditionally cataloged status as a result of an abnormal termination of a job. You can close a version from the Manage Versions panel. You may want to delete the version after setting it to closed status since the data may be incomplete as the result of the abnormal termination.
Closing a Version Using TSIDMNT CLOSE 2-42 BIM-EPIC also provides TSIDMNT CLOSE to close a dataset version. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using CLOSE. Connectivity Systems, Inc.
Removing Version Information from the DSN Catalog Removing Version Information from the DSN Catalog Description Dataset version information can be removed from the DSN Catalog by deleting the associated dataset definition or by purging the associated tape volume serial number. If a disk-resident version, scratching the version will remove it from the DSN Catalog, as well. Procedure See “Deleting a Dataset Definition” or “Purging a Tape Volume” for specific information.
Managing Tapes Managing Tapes Tapes in the DSN Catalog Every tape BIM-EPIC uses for a controlled dataset is recorded in the DSN Catalog. Tapes are identified in the DSN Catalog by volume serial number. New tapes are automatically added to the DSN Catalog when BIM-EPIC-controlled datasets residing on tapes are processed. You can also enter tape information into the DSN Catalog using Online Manager or TSIDMNT ADD.
Managing Tapes is not associated with any pool. The tape can only be used to write datasets which are not assigned to a tape pool. Datasets can be assigned to a tape pool using manual cataloging or automatic cataloging. If you use ACL support with pooling, the same pools must also be defined to the ACL system. Refer to the vendor ACL documentation for information on defining pools to the ACL system. User Reference Connectivity Systems, Inc.
BIM-EPIC Tape Selection Process BIM-EPIC Tape Selection Process Description IM-EPIC controls which tapes can be used for output by checking the volume serial number of every tape processed. If the tape is controlled, the serial number is compared with the corresponding DSN Catalog entry for scratch status before the tape is used as output. If the tape is uncontrolled, BIM-EPIC checks to see if the volume serial number was initialized by VSE DITTO and if it is in expired status.
Displaying Tape Volume Information Displaying Tape Volume Information Description The Tape Volume Information panel displays information on any controlled tape volume. You can also execute tape functions from the Tape Volume Information panel. Procedure To access the Tape Volume Information panel: Step Tape Volume Information Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel. 4 Tab to the Volser field.
Maintaining Tape Volume Information Maintaining Tape Volume Information Description You can manage tape volume information using the Manage Tape Volumes panel. Procedure To access the Manage Tape Volumes panel: Step Manage Tape Volumes Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel. 4 Tab to the Volser field. 5 Type the volume serial number in the Volser (Volume Serial Number) field.
Maintaining Tape Volume Information Using TSIDMNT User Reference BIM-EPIC also provides TSIDMNT to manage tape volumes. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for additional information on using TSIDMNT. Connectivity Systems, Inc.
Purging a Tape Volume Purging a Tape Volume Description You can purge a tape volume from the DSN Catalog using the Manage Tape Volumes panel. Procedure To access the Manage Tape Volumes panel: Step Manage Tape Volumes Panel Action 1 Open the Primary Option menu. 2 Type M (Manage) 3 Press Enter to open the Search Catalog panel. 4 Tab to the Volser field. 5 Type the volume serial number in the Volser (Volume Serial Number) field. The following is an example of the Manage Tape Volumes panel.
Recording Tape Cleaning Recording Tape Cleaning Description You can record tape cleaning using either the Tape Volume Information panel or the Manage Tape Volumes panel. Procedure To access the Tape Volumes Information panel: Step Manage Tape Volumes Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel. 4 Tab to the Volser field. 5 Type the volume serial number in the Volser (Volume Serial Number) field.
Understanding Retention Concepts Retaining and Scratching Datasets Understanding Retention Concepts Description Retention is the amount of time a dataset is kept before the dataset is scratched. Retention is one of the most critical areas of information control. Scratching or making a tape available for reuse, occurs when a dataset version’s retention criteria have been met.
Setting Dataset Definition Retention Setting Dataset Definition Retention Description When a BIM-EPIC dataset definition (EDD) 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 To access the Define an EDD panel: Step Define an EDD Panel Action 1 Open the Primary Option menu. 2 Type D (Define). 3 Press Enter to open the Define an EDD panel.
Modifying Dataset Definition Retention Modifying Dataset Definition Retention Description When using the Update an EDD panel to modify an existing BIM-EPIC dataset definition (EDD), you can change the existing retention criteria. The changes will apply to all subsequent versions of that dataset. Access To access the Update an EDD panel: Step Update an EDD Panel Action 1 Open the Primary Option menu. 2 Type M (Manage). 3 Press Enter to open the Search Catalog panel.
Setting or Modifying Dataset Version Retention Setting or Modifying Dataset Version Retention Description You can 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, the version is put in active status automatically. Access To access the Retain a Version panel: Step Retain a Version Panel Action 1 Open the Primary Option menu. 2 Type M (Manage).
Setting or Modifying Dataset Version Retention Step 4 Using TSIDMNT RETAIN 2-56 Action Press F3 to exit without performing any updates. BIM-EPIC also provides TSIDMNT RETAIN to set and modify dataset version retention. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for information on using RETAIN. Connectivity Systems, Inc.
Cycling a Dataset Version Cycling a Dataset Version Description Cycling is a special purpose function that allows you to change the creation date, change the creation job name, or override the number of versions (cycles) retained for a dataset. You can also use this function to take one version out of the normal retention cycle and reserve it for special retention.
Cycling a Dataset Version Cycle a Version Panel The following is an example of a Cycle a Version panel. TSIO0211.
Scratching a Dataset Version Scratching a Dataset Version Description 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 using Online Manager or TSIDMNT. All other versions are eligible for scratch only after all of the retention criteria specified for the dataset version have been satisfied.
Scratching a Dataset Version Procedure To scratch a version: Step Print Options Action 1 Type S (Scratch) in front of the version you want to scratch. 2 Press Enter. Print output is controlled using the JCL // OPTION LOG. If the option is specified, all processed maintenance is printed on SYSLST. If // OPTION NOLOG is specified, only invalid commands are printed. If your system log option is NO LOG and you want a list of submitted commands, you must provide // OPTION LOG prior to //EXEC TSIDMNT.
Establishing Online Security Establishing Online Security Description Securing the Online Manager If security is desired, a panel-driven online security facility provides security for the Online Manager by performing the following tasks: Allows online catalog management functions and some BIM-EPIC system functions to be restricted to specific users Allows multiple users to inherit (model) an individual set of security attributes.
Establishing Online Security can create specific security profiles by department. Use $DEFSEC to access the default security settings. Procedure Secured Users Panel To access the Online Manager security system: From the Primary Option menu, type SECURITY on the command line to display a list of SECURED USERS or select SYSTEM to display the System Configuration menu. From the System Configuration menu, select SECURITY.
Establishing Online Security User Reference User ID Definition $EPIC Unsecured profile. $EPIC, which cannot be modified, is provided by the Online Manager to use as a model. After $DEFSEC is secured, you can grant total system access to selected users by modeling their user profiles after $EPIC. Profiles modeled on $EPIC can be modified to create custom security profiles. To prevent unauthorized access to the Online Manager, you cannot use $EPIC as a user ID.
Creating Security Profiles Creating Security Profiles Description You can use an existing security profile as a model when creating new security profiles. Procedure To create (model) a new secured profile based on an existing security profile: Step User Security Panel Action 1 Type SECURITY at the Online Manager command line to display the User Security panel. 2 Type M (Model) in front of the $DEFSEC profile. 3 Press Enter to open the new profile.
Creating Security Profiles Descriptions The following describes the input fields for the User Security panel. Field Definition Password Specifies the user password. An asterisk (*) at the end of the Password field or Verify field indicates that the field has an existing password. For privacy, neither the Password field nor Verify field is displayed on the screen. You can use the Model field to import security settings from another secured user profile. Verify Confirms the password.
Creating Security Profiles If the security profile is modeled after an existing profile, the relationship is removed and the Model fields should be empty. Sign–On Panel If a user profile requires a password to access Online Manager, the Sign-On panel is displayed when the user enters the EPIC transaction. The Sign-On panel prompts the user for a user ID and password. The panel recognizes only user IDs listed on the Secured Users panel.
Creating Security Profiles User Reference Step Action 10 Type U (Update) in front of $DEFSEC. 11 Press Enter to open the new model. 12 Modify $DEFSEC to deny all system access, including security, and catalog update functions to unsecured users. 13 Create the desired group security profiles. For example, you can create a department profile named DEPT1 and provide the profile with desired catalog update access for the entire department.
Creating Security Profiles 2-68 Connectivity Systems, Inc.
3 TSIDMNT—DSN CATALOG MANAGEMENT UTILITY BIM-EPIC provides the TSIDMNT program for managing the DSN Catalog. You can perform the same functions using Online Manager. Chapter Contents TSIDMNT Command Summary TSIDMNT Command List User Reference Connectivity Systems, Inc.
TSIDMNT Commands and Functions TSIDMNT Command Summary TSIDMNT Commands and Functions Description The following table provides a list of TSIDMNT commands and their associated functions. Command Function ADD Add a version of a controlled dataset to the DSN Catalog. ADS Add a new version to a controlled dataset. CAPACITY Display DSN Catalog utilization statistics. CATALOG Define a new EDD in the DSN Catalog. CLEAN Reset tape usage, error counts, and clean date.
TSIDMNT Commands and Functions User Reference Command Function SCRATCH Scratch a version of a dataset. TRANSFER Move a version from one dataset to another dataset. UNLOCK Unlock a locked EDD or version. UPDATE Change the attributes of a BIM-EPIC dataset definition (EDD). Connectivity Systems, Inc.
TSIDMNT Command Overview TSIDMNT Command List TSIDMNT Command Overview Description TSIDMNT commands must conform to the following syntax: command [ 'dataset-name' ] [ parameter-expressions ] The command must always be entered first and can be specified in full syntax or abbreviated to the first three letters. For example, to indicate the DISPLAY command, you can enter either DISPLAY or DIS. Definitions JCL Requirements The following describes each parameter in the command syntax.
TSIDMNT Command Overview Example The following provides an example of a command syntax. ADD ‘INVENTRY.FILE’, SER=‘IN0192,IN2323,IN2987,IN9870,IN4573,IN1029,IN3049’ User Reference Connectivity Systems, Inc.
ADD Command ADD Command Description ADD creates a new version to a controlled dataset. For tape versions, the volume serial number must not be in the BIM-EPIC Catalog unless the ESER parameter is used. See below for information describing the ESER parameter. Note: You can use CATALOG to create a new BIM-EPIC dataset definition (EDD) for a previously uncontrolled dataset. See “CATALOG Command” for additional information.
ADD Command Syntax Use TSIDVUT PACKSCAN ADD to recreate the VTOC entry as soon as possible. Use ADD to add the version to the DSN Catalog. The following provides an example of the ADD command syntax. ADD Parameters 'dataset-name' SER=volser1,volser2,....,volser23 ESER=volser1,volser2,....,volsern VOL=volser,start-track,tracks,... EVOL=volser,start-track,tracks,... [ ,VER=n ] [ ,GEN=n ] [ ,FIL=n ] [ ,BLK=n ] [ ,OFL=1 ] The following provides a description of the parameters you can use with ADD.
ADD Command Parameter Definition VOL/EVOL Use for disk versions. Specifies the extents the version occupies. The volume serial number specifies the volume that contains the extent. VOL subparameters are positional. If there are multiple extents, repeat the subparameters in extent sequence. Use EVOL instead of VOL if the version has more than 10 extents. You must also use EVOL to add extents to a version that is already in the DSN Catalog. Supply extent information using the same process as VOL.
ADD Command Examples The following example adds version number 3 to the PAYROLL.MASTER dataset. Version 3 is on tapes PY1234 and PY2764 with a block size of 10000. ADD 'PAYROLL.MASTER',VER=3,BLK=10000,SER=PY1234,PY2764 The following example adds version number 1 to the INVENTRY.237 dataset. Version 1 is on tape E93837. ADD 'INVENTRY.237',SER=E93837 The ADD statement is all one line with an * at the end. The VOL statement is indented a few spaces. The following example adds a multi-extent disk file.
ADS Command ADS Command Description ADS adds a new tape version to a controlled dataset. The volume serial numbers (volsers) must be in the BIM-EPIC catalog and in scratch status to use the ADS command. ADS cannot be used for Faketape volume serial numbers. Use PURGE and ADD to accomplish the desired action. BIM-EPIC resequences version numbers as you add new versions. For example, if you add a new version, the previous version 1 becomes version 2, version 2 becomes version 3, and so on.
ADS Command Parameter Required? Valid Entry Default Specify any combination of the following (optional): Definitions FIL No 2 to 255 None BLK No 1 to 65535|MAX|OPT None OFL No 1 None The following provides definitions for the parameters you can use with ADS. Parameter Definition dataset-name Specifies the name of the dataset to which the new version belongs. User Reference SER/ESER Specifies the tape volume serial number(s) on which this version is written.
ADS Command Parameter Definition BLK Specifies the block size of this version of the dataset. Block size options include: OFL=1 Examples MAX sets the block size to full track capacity for disk datasets and for tape datasets—64K for VSE/ESA 2.5 and later, or 32K for earlier VSE releases. OPT sets the block size to half track capacity for disk and for tape—32K for VSE/ESA 2.5 and later, or 16K for earlier VSE releases. Use to identify the version as an offload version.
CAPACITY Command CAPACITY Command Description CAPACITY displays DSN Catalog usage. The DSN Catalog usage is displayed as both the number of active/free records and as a percentage of catalog space. Syntax The following provides an example of the CAPACITY command syntax. CAPACITY Example (no parameters) The following is an example of a CAPACITY display. 119 TOTAL 119 CAPACITY 119 4560 User Reference CATALOG UTILIZATION ACTIVE FREE PCT 959 3601 21 Connectivity Systems, Inc.
CATALOG Command CATALOG Command Description CATALOG creates a new BIM-EPIC dataset definition (EDD) in the DSN Catalog. After the EDD has been created, versions can be created by running jobs that specify this dataset name in JCL or by using ADD. Syntax The following provides an example of the CATALOG command syntax.
CATALOG Command Definitions Parameter Required? Valid Entry Default 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 The following provides definitions for the common parameters you can use with CATALOG.
CATALOG Command Parameter Definition COP Use to define a new dataset that is similar to a previously cataloged dataset. You must specify the COP parameter immediately following the dataset name. Any parameters specified before the COP parameter will be ignored. You can specify additional parameters after the COP parameter if you need to change the copied attributes. CYC Specifies the number of cycles (versions) to retain. See the note below for additional information.
CATALOG Command Note: RET, CYC, DLA, and WRK (Retention Days, Cycles Retention, DLA Retention, and Generation or Work) work together to determine dataset retention. These are some of the most important attributes of any dataset. You must carefully make your selection. RET, CYC, and DLA criteria must be satisfied before a version can be automatically scratched by TSIDUTL SCRATCH. Parameters Definitions User Reference The following provides a description of the tape parameters you can use with CATALOG.
CATALOG Command Parameter Definition MOD Specifies the tape density.
CATALOG Command Parameters User Reference Parameter Definition NSU Specifies the dataset tape versions are part of a multi–dataset group. You must enter the name of first dataset on the tape. This dataset is referred to as the prime dataset elsewhere in BIM-EPIC documentation. The datasets that specify NSU are referred to as subdatasets. If used, the NSU parameter must be specified when the dataset is first cataloged.
CATALOG Command Definitions 3-20 Parameter Required? Valid Entry Default EXT No 1 to 999999 DEFEXT value EX2 No 0 to 999999 50% of EXT POL No 1 to 6 characters None or DEFPOL value SEC No 0 to 255 255 The following provides definitions for the disk parameters you can use with CATALOG. Parameter Definition AGP Specifies if dataset retention is controlled by the Automatic Generation Purge feature.
CATALOG Command Examples Parameter Definition SEC Specifies the maximum number of secondary extents that can be allocated for a version. If SEC=NO (default) is specified, 255 secondary extents are allowed. To inhibit all secondary allocations, specify SEC=0 (zero). The following example catalogs the PAYROLL.MASTER dataset. This example includes copying dataset attributes from the AP.MASTER dataset and changing the dataset password to PASSWORD. CATALOG 'PAYROLL.MASTER',COP='AP.
CLEAN Command CLEAN Command Description CLEAN records tape cleaning. CLEAN sets the use count and error count for cleaned tapes to zero (0). Syntax The following provides an example of the CLEAN command syntax. CLEAN Parameters Definition Example SER=volser1,volser2,... The following provides a description of the parameters you can use with CLEAN.
CLOSE Command CLOSE Command Description CLOSE changes only the DSN Catalog status of a version. CLOSE does not perform VSE close processing, such as writing tape or disk labels. BIM-EPIC accesses only active versions of a dataset. Datasets that are in open status or conditionally cataloged status cannot be accessed for reading and writing. Closed datasets become eligible for scratch differently than active datasets. To access or activate an open or conditionally cataloged dataset, you must use CLOSE.
CYCLE Command CYCLE Command Description CYCLE is a special command for overriding the normal Cycles Retention (CYC) of a dataset. CYCLE causes one version to be removed from the Cycles Retention logic. The cycled version is scratched only on the basis of the retention period. For example, you might use the cycled version to isolate the correct balance sheet from a series of trial balance runs. CYCLE looks very similar to RETAIN.
CYCLE Command Parameter Required? Valid Entry Default Specify at least one of the following (required): Definitions EXD No 1900001 to 2099366 None DAY No 1 to 999 None CDT No 1900001 to 2099366 None JOB No 1 to 8 characters None The following provides definitions for the common parameters you can use with CATALOG. Parameter Definition dataset-name Specifies the dataset name. Example VER Specifies the version number.
DELETE Command DELETE Command Description DELETE removes a dataset and all associated versions from the DSN Catalog and from BIM-EPIC control. All tapes associated with the dataset become scratch tapes and are listed under the dataset name ** DSN DELETED ** on BIM-EPIC reports and Online Manager panels. Disk space allocated to the dataset is freed. If an Automated Cartridge Library (ACL) is supported, DELETE sets the tape volume to scratch status in the ACL inventory.
DEQ Command DEQ Command Description DEQ dequeues the DSN Catalog after it has been enqueued with ENQ. In CA-EPIC for CMS, the DEQ command is only meaningful when sharing a BIM-EPIC DSN Catalog. Syntax The following provides an example of the DEQ command syntax. DEQ User Reference (no parameters) Connectivity Systems, Inc.
DISPLAY Command DISPLAY Command Description DISPLAY displays entries in the DSN Catalog. DISPLAY lists all cataloged information about a dataset and all associated versions. If a version resides on multiple volumes or extents, each volume or extent has a separate line in the display. Scratched tape versions continue to be displayed until the tapes are used to write other datasets. Most of the items listed in the reports are self–explanatory.
DISPLAY Command Parameters The following provides a description of the parameters you can use with DISPLAY. Parameter Required? Valid Entry Default Specify one of the following (required): dataset-name [DPW=password] No 1 to 44 characters [1-8 characters] None SER No 1 to 6 characters None ALL No ALL None string.
DISPLAY Command Examples Parameter Definition ACTIVE Displays only active versions. DSK Displays only disk versions. DSN Displays only dataset names, set summaries are omitted. JOB Displays the latest version of all datasets that were created by the specified job name. JOB also displays any open or conditionally cataloged datasets created by that job since the latest version was created. NEW Displays all datasets that have been created since the last execution of TSIDUTL DSPLY NEW.
ENQ Command ENQ Command Description ENQ enqueues the DSN Catalog and prevents access to the catalog by jobs running in other partitions or CPUs. To enqueue a DSN Catalog that is shared by two or more CPUs, you must specify MULTCPU=YES as a configuration option. In CA-EPIC for CMS, ENQ is meaningful only when sharing a BIM-EPIC DSN Catalog. Syntax The following provides an example of the ENQ command syntax. ENQ User Reference (no parameters) Connectivity Systems, Inc.
LOCK Command LOCK Command Description LOCK locks a dataset or version. If you do not specify a version, volume serial number, or generation number, the BIM-EPIC dataset definition (EDD) is locked for output. BIM-EPIC does not permit additional versions to be created until you release or unlock the EDD. 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 the version cannot be read until you release or unlock it.
MCATALOG Command MCATALOG Command Description MCATALOG specifies that a tape dataset can be accessed by more than one dataset name. The new dataset names are known as MCAT aliases. After MCATALOG has been specified for a version, the version is accessible by both the original dataset name and the MCAT alias(es). The dataset is retained until all retention criteria from all associated BIM-EPIC dataset definitions (EDDs) have been satisfied.
MCATALOG Command Note: Only MCAT parameters are positional. Example The following example associates version 2 of the PAYROLL.MASTER dataset to version 1 of the PAYROLL.PERM dataset, so the version can be accessed using either dataset name. MCA 'PAYROLL.MASTER',VER=2,'PAYROLL.PERM',VER=1 3-34 Connectivity Systems, Inc.
MOVE Command MOVE Command Description MOVE changes the vault location and slot location of a tape volume. If a non-virtual 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 MOVE is processed. MOVE is of no value for a virtual ACL because virtual tapes cannot be vaulted. Examples of virtual ACLs include VTS, Faketape, MAS, and Opti-Tape. ! Syntax WARNING: Vaulting reports do not reflect changes done by MOVE.
OFFLINE Command OFFLINE Command Description OFFLINE prevents BIM-EPIC from accessing a disk volume. When a volume is in OFFLINE status, BIM-EPIC will not use the volume for input or output actions. OFFLINE cannot disable volume access across machines. You must issue the OFFLINE command from each machine that has access to the device. If it is necessary to issue a VSE DVCDN command to a drive, the BIM-EPIC OFFLINE command should be issued first.
ONLINE Command ONLINE Command Description ONLINE enables BIM-EPIC to access a disk volume for both input and output datasets. If a disk volume has been placed in OFFLINE status or QUIESCE status, use ONLINE to restore access to the volume. ONLINE cannot enable a volume across machines. You must use the ONLINE command for each machine in which the OFFLINE command was used. See “OFFLINE Command ” for additional information. Syntax The following provides an example of the ONLINE command syntax.
PASSWORD Command PASSWORD Command Description PASSWORD enables you to enter the required password if your installation uses the PASSWD configuration option to invoke DSN Catalog update protection. The DSN Catalog password is required for all commands except for the following commands: CAPACITY DISPLAY HELP PASSWORD You must submit the PASSWORD command before any protected operation. The password is not printed on SYSLST if the command name (PASSWORD or PAS) begins in column 1.
PURGE Command PURGE Command Description PURGE removes 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 associated versions (tape and disk) or simply remove a tape volume and the associated versions. Datasets which are part of a multi–dataset group cannot be purged until all other datasets in the group are scratched or deleted. In addition, all versions must be in closed status before they can be purged.
PURGE Command Examples Parameter Definition SER Specifies a tape volume serial number when you want to remove that serial number from the DSN Catalog but leave the dataset under BIM-EPIC control. If the volume serial number contains non–alphanumeric characters, enclose the volume serial number in apostrophes. The following example purges PAYROLL.TABLE and all associated tape volumes. PURGE 'PAYROLL.TABLE' The following example purges volume PR3746 and the version written on it.
QUIESCE Command QUIESCE Command Description QUIESCE prevents disk volumes from being used for the creation of controlled datasets. BIM-EPIC will not allocate output datasets on a quiesced volume. Quiesced volumes are still eligible for BIM-EPIC input processing and for uncontrolled processing. QUIESCE cannot disable a volume across machines. You must use QUIESCE on all machines that have access to the volume. Use ONLINE to remove a volume from QUIESCE status.
RELEASE Command RELEASE Command Description RELEASE temporarily unlocks a BIM-EPIC dataset definition (EDD) or a locked version. RELEASE allows a one-time only access, while UNLOCK allows unlimited access. If you do not indicate a specific version, the EDD is released for output one time only. This release allows you to create one additional version of the dataset. The new version is placed in locked status automatically. If a specific version is indicated, that version is released for input.
RELEASE Command Examples Parameter Definition GEN Specifies a generation number from 1 to 999999. PWD Use if the dataset is password protected. The following example releases the PAYROLL.MASTER dataset, supplies the associated password, HARRY, and permits the creation of an additional version. RELEASE 'PAYROLL.MASTER',PWD=HARRY The following example releases the version of the PAYROLL.
RENAME Command RENAME Command Description RENAME allows you to change the name of a cataloged dataset. All existing versions of the original dataset will be referenced by the new dataset name. Dataset characteristics do not change. If the dataset is a disk dataset, the associated VTOC entries are renamed, as well. ! Syntax WARNING: Do not rename prime datasets or offload datasets. Results are unpredictable. The following provides an example of the RENAME command syntax.
RETAIN Command RETAIN Command Description RETAIN completes the following tasks: Alters an expiration date, a creation date, or a creation job name for a specific version. If the version is not in active status, it is set to active status. RETAIN specifies that a version is a TSIDOFL-created tape backup, not an offload of a Start Track 1 disk DSN created by TSIDOFL. Specifies that a version resides on an FSI Faketape device.
RETAIN Command Definition The following provides definitions for the parameters you can use with RETAIN. Parameter Definition dataset-name Specifies the name of the dataset you want to retain. specifier-expression VER=nnn Specifies the version number, where nnn is any number from 1 to 999. SER=xxxxxx Specifies the serial number, where xxxxxx identifies the first or only tape volume version. The serial number can be up to 6 characters.
RETAIN Command Example Parameter Definition OF2 (Optional keyword parameter) If used, place the parameter at the end of the RETAIN statement. You can use OF2 to identify the retained version as having FAVER2 offload format. In addition, you can use OF2 to assign FAVER2 offload format to a tape after the tape has been added to a dataset using the OF2 parameter. ST1 (Optional parameter) Use if a new version is a tape backup created by TSIDOFL BACKUP, not an offload of an EPIC Start Track 1 dataset.
SCRATCH Command SCRATCH Command Description SCRATCH scratches a version of a dataset. The version must be in active status to be scratched. If the version is in open status or conditionally cataloged status, use CLOSE to make the version active. If an Automated Cartridge Library (ACL) is supported, SCRATCH sets the tape volume to scratch status in the ACL inventory. In BIM-EPIC, you can use SCRATCH in a job stream to scratch disk datasets without supplying the dataset password.
SCRATCH Command Parameter Definition GEN Specifies the generation number of a disk version. 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. Note: Scratching by volume serial number is not valid for an NSU subdataset or an MCAT alias. Examples The following example scratches version 1 of the INVENTRY.SANDIEGO.3847 dataset. SCRATCH 'INVENTRY.SANDIEGO.
TRANSFER Command TRANSFER Command Description TRANSFER moves a version from one dataset to another dataset. The transferred version is no longer associated with the original dataset name. However, a transferred version retains all of the original characteristics, except for the version number. Note: If the version is a disk dataset, the associated VTOC entry is also renamed. Syntax The following provides an example of the TRANSFER command syntax.
TRANSFER Command TRA User Reference 'IRVINE.INVENTRY',VER=7,'SANDIEGO.INVENTRY' Connectivity Systems, Inc.
UNLOCK Command UNLOCK Command Description UNLOCK permanently unlocks a locked dataset or version. To unlock a dataset or version for a one-time only use, use RELEASE. You must use LOCK before you can use UNLOCK. 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. Syntax The following provides an example of the UNLOCK command syntax.
UNLOCK Command The following example unlocks version 6 of the INVENT.958575 dataset. The dataset can now be read as input an unlimited number of times. UNL 'INVENT.958575',VER=6 User Reference Connectivity Systems, Inc.
UPDATE Command UPDATE Command Description UPDATE changes the characteristics associated with a BIM-EPIC dataset definition (EDD) in the DSN Catalog. The updated characteristics will affect only versions created after an update. To update previously created versions, use CLOSE, CYCLE, or RETAIN. The parameters available with UPDATE are nearly identical to the CATALOG parameters. However, you cannot update the prime dataset name and encryption password.
UPDATE Command parameter. When the version is read by Dr.Crypto, the encryption key used to create the version is presented to Dr.Crypto to decrypt the data. If the ENC parameter is used to change the algorithm, new versions will be encrypted with that algorithm, but previously created versions will remain encrypted in the prior algorithm.
UPDATE Command 3-56 Connectivity Systems, Inc.
4 BIM-EPIC TLBL and DLBL Statements This chapter describes the TLBL statement and DLBL statement. BIM-EPIC TLBL statements can have a slightly different format than VSE TLBL statements and, as a result, provide additional options. BIM-EPIC DLBL statements have the same format as VSE DLBL statements but can also provide additional options. In addition, BIM-EPIC provides an MVS-style dataset definition (DD) statement for VSE. Each type of BIM-EPIC label statement provides unique benefits.
TLBL Statements TLBL Statements and Options TLBL Statements Description Typically, a user does not need to change existing TLBLs. However BIM-EPIC provides modifications to the standard VSE TLBL statement that can provide additional capability. Note: All TLBL fields are positional. TLBL Format The following identifies similarities and differences in TLBL formats.
TLBL Statements Definitions User Reference Parameter Required? Valid Entry Default disposition No See description below None The following provides definitions for the parameters you can use with CATALOG. Parameter Definition dtfname Specifies the symbolic name that the program uses for the dataset. For example TAPEIN and SORTIN. IBM refers to the dtfname field as the filename. dataset-name Specifies the name of the dataset that will be used. IBM refers to this field as the fileid.
TLBL Statements 4-4 Parameter Definition alpha-opts Provides compatibility with tape management products from other vendors. To use these options, the JCLOPT configuration option must be set to YES. The alpha-opts parameters can be alphabetic codes, version requests, and density requests, in any order, as long as they are separated from dataset-name and each other by commas. See “TLBL Options” for additional options.
TLBL Statements Parameter Definition densities supported for 3490E devices: F0—Buffered write mode (3490E) F8—Buffered write mode with IDRC (3490E) BIM-EPIC uses mode F0 and mode F8 to distinguish 3490E tape cartridge drives from 3480/3490. Because VSE/ESA does not support mode F0 and mode F8, BIM-EPIC sends mode 00 or mode 08 to the 3490E hardware, whenever mode F0 or mode F8 is specified. retention Specifies the number of days to retain this version.
TLBL Statements Examples Parameter Definition disposition Specifies file disposition. Values are DISP=OLD, DISP=NEW, or DISP=MOD. This parameter is identical to the VSE parameter and is valid only for Assembler language programs written for VSE/AF Release 1 and above. See the VSE System Control Statements documentation for additional information. The following examples show how TLBL statements can be used with BIM-EPIC.
TLBL Options TLBL Options Description BIM-EPIC TLBL option codes provide special processing that is unavailable with standard VSE TLBL parameters. See “TLBL Statements” for instructions and restrictions on specifying parameters. Alphabetic option codes, also known as alpha options, provide compatibility with other tape management products. Alpha options can be specified only within the TLBL dataset name field. Numeric codes can be specified only in the TLBL numeric-options parameter.
TLBL Options Alpha Code 4-8 Numeric Code Action Description 3 Do not rewind Prevents rewinding the tape at close. Use this option when you are creating multi-dataset tapes. R 4 Scratch at close Scratches the dataset when the dataset is closed as input. This option does not affect subdatasets. H 8 Hold the drive assignment at close Prevents BIM-EPIC from releasing the tape drive assignment at close. If Autoattach is on, this code prevents the drive from being detached.
TLBL Options Alpha Code User Reference Numeric Code Action Description 48 Concatenating datasets Reads multiple files using only one open command. The files are read as a single dataset. This process is called dataset concatenation. Use concatenation to read multiple files when your program performs only one open command. This option is valid for controlled datasets only. 64 Inhibit LUB allocation Inhibits LUB allocation for the dataset.
DLBL Statements DLBL Statements and Options DLBL Statements Description The BIM-EPIC DLBL statement is identical to the VSE DLBL statement, with additional BIM-EPIC options that provide special BIM-EPIC processing. BIM-EPIC DLBL options are specified within the file ID or 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 using commas.
DLBL Options DLBL Options Description DLBL option codes provide special BIM-EPIC processing that is unavailable with standard VSE DLBL parameters. See “DLBL Statements ” for an overview of DLBL statements. DLBL Option Codes The following option codes can be used with the DLBL statement. User Reference Code Action Description A Align allocation on Aligns the disk allocation on cylinder cylinder boundaries. Valid for CKD devices only.
DLBL Options 4-12 Code Action Description F Allow fragmentation When the requested amount of space is not available, this code allows BIM-EPIC to allocate the largest amount of contiguous space available. Do not use this code for TYPEFLE=WORK files, for example, compiler work files, and FORTRAN disk files or for any other files that do not support secondary extents. If you do not specify the F code and BIM-EPIC cannot find the requested contiguous extent in the pool, message EP038 is issued.
DLBL Options Code Action Description M Issue messages open/close Overrides configuration options ALLMALL=NO (default) and ALLMSG=NO for this dataset. Allocation messages are issued for the dataset and for all subsequent disk datasets that are opened. For output datasets, EP039 is issued after the dataset has been opened, displaying the allocated extents. EP052 is issued after the file has been closed, displaying the size of the truncated extent.
DLBL Options Code Action Description R=n Allocate by Logical Records (n=1 to 999999) Specifies the number of logical records the file is to contain. BIM-EPIC uses this number to calculate the size of the extent required. S Reuse same space Reuses the same extent space occupied by the current version for the next version of the dataset. This option affects single extent non-generation datasets only. When you use this option, you must also inhibit truncation, option code N, for the dataset.
5 Accessing the DSN Catalog This chapter discusses several ways to access the DSN Catalog. Chapter Contents Displaying DSN Catalog Entries Accessing DSN Catalog Records User Reference Connectivity Systems, Inc.
TSIDUTL DSPLY Displaying DSN Catalog Entries TSIDUTL DSPLY Description TSIDUTL DSPLY creates reports from the data maintained in the DSN Catalog. Reports can be created containing data associated with all datasets, all versions, specific datasets, or specific versions which match specified criteria and by media type (tape or disk). These reports can also be produced using different sort sequences. TSIDUTL DSPLY creates reports listing all datasets or groups of datasets in the DSN Catalog.
TSIDUTL DSPLY Parameters The following provides a description of the parameters you can use with TSIDUTL DSPLY.
TSIDUTL DSPLY Definitions The following provides definitions for the parameters you can use with TSIDUTL DSPLY. Parameter Definition dataset-qualifier ACTIVE Creates reports for active datasets only. ALL Creates reports for all datasets in the DSN Catalog. DISK Creates reports for disk datasets only. DSN Creates reports for a specified dataset only. NEW Reports dataset versions created since the last time the DSPLY NEW report was run.
TSIDUTL DSPLY Examples Parameter Definition CJOB Lists the job name. CDATE Lists the creation date. DSN Lists the dataset name. ERROR Lists the total errors. SERIAL Lists the tape volume serial number. VAULT Lists the vault and slot numbers. TAPEPOOL Lists the tape pool ID. XDATE Lists the expiration date. The following example produces a report listing all datasets belonging to the system ID=TS and the user ID=MR. The datasets are listed in the order they are found in the catalog index.
TSIDAC2 Subroutine Accessing DSN Catalog Records TSIDAC2 Subroutine Description TSIDAC2 provides the capability to access BIM-EPIC Catalog records from non-BIM-EPIC programs. This subroutine would be useful, for example, if you needed to produce reports not provided by BIM-EPIC. TSIDAC2 can be invoked from any programming language that supports the CALL facility/construct. TSIDAC2 is located in the BIM-EPIC installation library as member TSIDAC2.OBJ.
TSIDAC2 Subroutine Sequential and Random Access When using random access, TSIDAC2 returns the master record for a specific dataset the first time TSIDAC2 is called for that dataset. On each subsequent call, TSIDAC2 returns a detail record for that dataset. When using sequential access, TSIDAC2 returns each record in order for a single dataset. TSIDAC2 then moves to the next dataset in the DSN Catalog index and begins returning the index records, one record at a time.
TSIDAC2 Subroutine Step Return Codes Action Description 3 Call TSIDAC2 from your program. This call requires that a parameter list be passed to TSIDAC2. The parameter list consists of only the storage area discussed in step 1. 4 Following the TSIDAC2 call, you should check the return code that is passed back in the USER-RETURN-CODE field. The following return codes are used. Return Explanation Code 1 Function completed normally and the data has been returned in USER-CATALOG-DATA.
Search Arguments and Calls Search Arguments and Calls Description The following explains specific procedures you can use to gain access to the DSN Catalog when using TSIDAC2. Implement these procedures as steps 2 and 3 of the procedure outlined in the previous section. The examples use the COBOL copybook (TSIDAC2.C) to name the data fields described in this section. All examples are in COBOL.
Search Arguments and Calls To request a detail record by volume serial number: Step Example Action 1 Move a hex 02 to USR-KEY-POS-1 and move the six-digit volume serial number to USR-KEY-SER. 2 Call TSIDAC2. The following is an example of COBOL coding that you can use to request a detail record by volume serial number. WORKING-STORAGE SECTION. 01 HEX-NUMBER PIC S9(4) COMP VALUE +2. 01 HEX-REDEF REDEFINES HEX-NUMBER. 05 FILLER PIC X. 05 HEX02 PIC X. . . . PROCEDURE DIVISION. . . .
Search Arguments and Calls Step 4 Example Action Issue multiple calls to TSIDAC2. The following is an example of COBOL coding that you can use to specify a starting point for sequential processing. PROCEDURE DIVISION. . . . MOVE 'DATA.SET.NAME.B' TO USR-KEY. CALL 'TSIDAC2' USING ACC-RECORD. SEQUENTIAL-READ. MOVE SPACES TO USR-KEY. CALL 'TSIDAC2' USING ACC-RECORD. IF USER-RETURN_CODE = 1 GO TO END-OF-CATALOG. (process the catalog information here) GO TO SEQUENTIAL-READ.
Search Arguments and Calls Example The following is an example of COBOL coding that you can use to release the storage. PROCEDURE DIVISION. . . . MOVE LOW-VALUES TO USR-KEY. CALL 'TSIDAC2' USING DSN-RECORD. . . . 5-12 Connectivity Systems, Inc.
ADDRESS EPIC ADDRESS EPIC Description ADDRESS EPIC provides an interface between BIM-EPIC and the Global Subsystem (BIM-GSS). Knowledge of how to write and create GREXX IMOD is assumed. Return Codes The following return codes are used. Command Forms Return Code Explanation 0 Function completed normally. -1 ADDRESS EPIC command is invalid. -2 BIM-EPIC is not active. -3 Unknown environment.
ADDRESS EPIC variables. If n.0 is 0, there were no datasets found with a dataset name starting with the character string ii. COUNT is required. The value c or * specifies the number of EDD records that can be returned. The value c specifies the maximum number of EDD records that can be returned. COUNT * will return all matching records. SKIP may be used to specify the number of EDD records that will be bypassed before returning the records as stem variables.
6 BIM-EPIC DD Statement The BIM-EPIC statement is an MVS-style dataset label for VSE installations. For many users, the primary benefit of using the dataset definition (DD) statement is for compatibility with MVS, because the DD statement 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.
DD Statement Overview DD Statements DD Statement Overview Description All dataset definition (DD) statements follow the same format. The identifying characters are * //, which must be specified in columns 1 through 4. These are followed immediately by the DD name. Syntax The following provides an example of a DD statement syntax. * //ddname Definitions 6-2 DD parameter-expressions The following provides definitions for the parameters you can use with a DD statement syntax.
DD Statement Overview Parameter Definition parameter-expressions Can follow in any order, except where noted otherwise. A parameter-expression consists of a parameter and its value(s) joined by an equal sign (=). These expressions must be separated from each other using commas or blank spaces. Numeric values are automatically zero-filled on the left, if required, eliminating the need to use leading zeros. Most DD parameters are MVS-compatible.
DD Statement Syntax DD Statement Syntax Description You can specify multiple parameters in the dataset definition (DD) statement syntax. Some parameters may have multiple subparameters. BIM-EPIC DD conventions conform to MVS conventions, for example, separating multiple parameters and subparameters with commas and enclosing multiple subparameters in parentheses. Many subparameters are positional.
DD Statement Syntax Specifying Dataset Drop To take advantage of the BIM-EPIC dataset drop option, use multiple DD statements with the same dataset definition name. No special coding is required. Note: The dataset drop option is not valid under MVS. In addition, VSAM datasets, including VSAM-managed SAM datasets, are not eligible for a dataset drop. For example: * //TAPEIN * //TAPEIN * //TAPEIN ! Concatenating Datasets DD DD DD DSN=INVENTRY.1QTR(0),DISP=(OLD,KEEP) DSN=INVENTRY.
DD Statement Syntax *// INPUT DD ….. See Chapter 9, “TYPRUN ,” for additional information. 6-6 Connectivity Systems, Inc.
DD Statement Names DD Statement Names Description Several dataset definition (DD) statement names (ddnames) have special purposes in MVS. This section describes how BIM-EPIC uses these names. Unsupported DD Names Statements containing the following ddnames are ignored by BIM-EPIC.
DD Statement Names The following provides additional information describing the special ddnames. Name Description JOBCAT and STEPCAT JOBCAT and STEPCAT define VSAM catalogs used for VSAM clusters. In the BIM-EPIC DD, JOBCAT and STEPCAT also define catalogs used for VSAM/SAM datasets. These extensions are not available in MVS. JOBCAT defines the catalog for the entire job stream. STEPCAT defines the catalog for a specific step. Note: STEPCAT overrides a JOBCAT definition for that step.
DD Statement Names Name Description SYSABEND, SYSUDUMP, SYSMDUMP SYSABEND, SYSUDUMP, and SYSMDUMP determine the kind of dump that is produced when a job cancels. Their parameters 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. You must specify the SYSOUT parameter with the SYSABEND, SYSUDUMP, and SYSMDUMP ddnames. In MVS, SYSOUT identifies a print class.
Parameters for Tape and Disk Datasets DD Parameters Parameters for Tape and Disk Datasets Description This section provides descriptions for the tape dataset parameters and the disk dataset parameters as well as the purpose of each parameter. Syntax The following provides an example of the syntax showing the parameters available for use with tape datasets and disk datasets.
Parameters for Tape and Disk Datasets Parameter Description DSN Use the DSN parameter to specify the name or version of the dataset(s) you want to process. For input datasets, if you do not specify a particular version, all versions are read. This process is known as automatic concatenation. DSN is required for all tape datasets and disk datasets. The DSN parameter can specify CPU and partition independence or common work datasets. This is a BIM-EPIC extension not available with MVS.
Parameters for Processing Datasets Parameters for Processing Datasets Description This section describes the dataset definition (DD) statement parameters you can use to process different types of datasets. The JCLOVRDE configuration option determines how DD parameters affect DSN Catalog entries. This configuration option applies only to datasets that exist in the catalog at the time the dataset is opened for output.
Parameters for Processing Datasets uncataloged datasets defined with DD statements. See Chapter 1, “Cataloging Datasets Automatically,” for additional information on autocataloging using configuration options. The following example creates a new version of a previously cataloged dataset. The associated default block size is overridden. The actual block size is 4080. * //TAPEOUT * // DD DSN=SARS.BACKUP,DISP=(NEW,KEEP), DCB=BLKSIZE=4080 The following example creates a new, uncataloged dataset.
Parameters for Processing Datasets * //STEPCAT DD * //VSAMSAM DD * // DSN=CUSTOMER.CAT,DISP=SHR DSN=CUSTOMER.MASTER,DISP=SHR,AMP=AMORG, SPACE=(240,(1000,500)) You can process existing VSAM datasets using BIM-EPIC DD statements. To process an existing VSAM dataset, include the AMP parameter in your statement. Define the VSAM catalog with a STEPCAT DD statement or JOBCAT DD statement. BIM-EPIC cannot create new VSAM IDCAMS datasets. * //JOBCAT DD * //VSAMCLU DD 6-14 DSN=CUSTOMER.
AMP Parameter AMP Parameter Description Use the AMP parameter to define a VSAM cluster or a VSAM/SAM dataset. Syntax The following provides an example of a AMP parameter syntax. AMP=(AMORG [ ,BUFSP=x ]) Subparameters Definitions User Reference The following provides a description of the subparameters you can use with the AMP parameter.
DCB Parameter DCB Parameter Description Use the DCB parameter to define the characteristics of the dataset. DCB subparameters override the DSN Catalog entry on output, but not on input. Syntax The following provides an example of a DCB parameter syntax. DCB=( [ BLKSIZE=x ][ ,DEN=x ][ ,DSORG=x ][ ,LRECL=x ] ) Subparameters Definitions The following provides a description of the subparameters you can use with the DCB parameter.
DCB Parameter Subparameter Definition DEN Specifies a recording density for tape datasets.
DCB Parameter 6-18 Subparameter Definition LRECL Specifies the logical record length of a record in the dataset. The number indicated must be less than or equal to the record length specified in the DTF or FD entry. If the logical record length is greater, the LRECL subparameter is ignored. Connectivity Systems, Inc.
DISP Parameter DISP Parameter Description Use the DISP parameter to identify how to open a dataset and what is to be done to the dataset when it is closed. DISP subparameters define the initial 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 Definitions The following provides definitions for the subparameters you can use with the DISP parameter. Subparameter Definition initial-usage-status Specifies the status of a dataset at the time the dataset is opened. If initial-usage-status is not specified, NEW is used. 6-20 normal-end-status Specifies the action taken for the dataset if the job step ends normally. If normal-end-status is not specified, PASS is used if usage-status is NEW or MOD.
DISP Parameter Subparameter Definition CATLG Performs one of two functions: Catalogs the dataset automatically if no DSN Catalog entry for the dataset exists. Updates selected dataset definitions in the DSN Catalog, if configuration option JCLOVRDE=YES is specified.
DISP Parameter Subparameter Definition DELETE Causes the dataset to be scratched automatically, after the dataset has been closed. The setting of the DDGEN configuration parameter determines whether the scratch process is done when the dataset is closed, at end-of-step (EOS), or at end-of-job (EOJ). See DISP Parameter for more information. KEEP Determines the status of a closed dataset. For normal-termination, if KEEP is explicitly specified for tape datasets, the tape will be unloaded at close.
DISP Parameter Subparameter Definition MOD Specifies that new data is to be added/appended to an existing tape version. If using a disk version, the existing data will be overwritten. For both tape and disk, if there is no existing version, a new version will be created. When used for tape, MOD removes the existing end-of-file (EOF) marker and writes new data beginning at that point. A new EOF will be created when the dataset is closed.
DISP Parameter The following table describes the basic DISP and DDGEN combinations. For those combinations not explicitly defined in the table, the following rules apply: If usage-status is SHR, the status will be treated the same as OLD. If usage-status is MOD, the status will be treated the same as OLD if there is an existing version. If an existing version does not exist, the status will be treated the same as NEW. The CONDCAT normal-end-status will be treated the same as KEEP.
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 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. In cases of abnormal termination, you can override the end-of-step and end-of-job deletions.
DSN Parameter DSN Parameter Description Use the DSN parameter to specify the name of the dataset being processed. The DSN parameter is required for all tape datasets 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 the rules for dataset names with standard VSE JCL. Tape dataset names and disk dataset names can be up to 44 characters.
DSN Parameter Subparameter Definition .Gnnnn[Vnnn] Specifies a disk version by generation number. Insert the generation number after the G, but before the V, if a generation number exists. The Vnnn portion of the parameter is ignored by BIM-EPIC and can be omitted. The Vnnn portion is included for MVS compatibility only. In practice, as in MVS, this form is not usually used. Use - or + forms instead. (0) Specifies a version-by-version number. (-n) (0) Zero indicates the current version.
DSN Parameter Subparameter Definition &&dsname &dsname Specifies work datasets. In MVS, placing two ampersands (&&) before a dataset name indicate a temporary dataset. In BIM-EPIC, two ampersands (&&) before a dataset name indicate CPU and partition independence. A single ampersand (&) indicates CPU independence only. The dataset name can be up to 44 characters. CPU and partition independence can also be indicated using an equal sign (=) or a dollar sign ($), as with TLBL and DLBL statements.
FREE Parameter FREE Parameter Description Use the FREE parameter to specify when to release a tape drive assignment. FREE is valid for tape datasets only. When you are processing multi-dataset tapes, you must specify FREE=END for every dataset except the last one processed in the job. An example of this is at the end of this section. Syntax The following provides an example of a FREE parameter syntax.
LABEL Parameter LABEL Parameter Description Use the LABEL parameter to define the dataset retention. You can specify an explicit expiration date or specify the number of days for the dataset retention period. 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. If a dataset is already cataloged, a new version will take the LABEL value instead of the EDD value.
LABEL Parameter Examples The following is an example using the LABEL parameter. * * * * User Reference //OUTPUT // //OUTPUT // DD DD DSN=OUT.DATA.SET,LABEL=EXPDT=98365, DISP=(NEW,KEEP) DSN=OUT.DATA.SET,LABEL=RETPD=5, DISP=(NEW,KEEP) Connectivity Systems, Inc.
OPTION Parameter OPTION Parameter Description Use the OPTION parameter to invoke a BIM-EPIC feature where there is no equivalent MVS JCL parameter.
OPTION Parameter Definitions Subparameter Required? Valid Default RUN No SPACE= No 1 to 15 characters None SYSnnn No 000 to 254|RDR|IPT|LST|PCH None TPL= No A to Z or 0 to 9 (Use "¬" None {X'5F} to indicate no TPL value is desired) See below The following provides definitions for the subparameters you can use with the OPTION parameter. Subparameter Definition ALLMSGS Overrides configuration options ALLMALL=NO (default) and ALLMSG=NO for the dataset in the current job step only.
OPTION Parameter Subparameter Definition RESET Ends the Generic Device Independence for Unit Record (GDIUR) control of a dataset. If you use OPTION=RESET, it must be the only parameter specified on the DD statement with other OPTION subparameters used. A dataset definition (DD) statement with OPTION=RESET is required when the job does not contain TLBL, DLBL, or DD statements in any step following the DD statement used to invoke GDIUR control of the dataset.
OPTION Parameter Subparameter Definition SPACE=*.ddname[x] Specifies that the primary extent allocation will be based on the amount of space used by the dataset previously defined in the same job step. Use the ddname parameter to identify the dataset. RLSE is automatically invoked with SPACE refer-back. There are several ways you can specify the size of the allocation: To specify dataset is to be exactly the same size as the referenced dataset, use the format: SPACE=*.
OPTION Parameter Subparameter SPACE=*.ddname[x] Definition (continued) To allocate a new dataset one track larger than the space the referenced dataset occupies, specify: * //FILEOUT DD DSN=dataset-name,DISP=(NEW,CATLG) * //UNIT=SYSDA,OPTION=SPACE=*.REFFILE+1 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=*.
OPTION Parameter OUTFILE(OUT ENVIRONMENT ( PDEV(2400) RECFM(FIXBLK) BLKSZ(8000) RECSZ(40) )) /* /& User Reference Connectivity Systems, Inc.
SPACE Parameter SPACE Parameter Description Use the SPACE parameter to specify the disk dataset allocation. In addition, use SPACE 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 Use parentheses to enclose the SPACE positional subparameters.
SPACE Parameter Subparameter Required? Default If used, specify one of the following (optional): Definitions CONTIG No None MXIG No None ALX No None ROUND No None The following provides definitions for the subparameters you can use with the SPACE control dataset. Subparameter Definition type Specifies type of allocation. TRK Specifies allocation in tracks or FBA blocks. CYL Specifies allocation in cylinders and forces the dataset to begin and end on cylinder boundaries.
SPACE Parameter Subparameter Definition RLSE Causes unused allocated space to be truncated when the dataset is closed. If RLSE is not specified, truncation does not occur. Note: For cataloged datasets, if the DD SPACE parameter is not coded, truncation will occur. frag-control 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 code H. MXIG ALX Specify fragmentation without operator intervention.
SPACE Parameter Subparameters Definitions The following provides a description of the subparameters you can use with the SPACE uncontrolled datasets. Subparameter Required? Valid Default ABSTR Yes None size-specification Yes None start-address No 512, 1024, 2048, None 3072, 4096 index No None The following provides definitions for the subparameters you can use with the SPACE uncontrolled dataset.
UNIT Parameter UNIT Parameter Description Use the UNIT parameter to specifies a device or device type for processing. UNIT is required for disk output datasets. UNIT 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 $$$. When a dataset name begins with $$$, common work dataset, UNIT=DISK is forced. You can also use a group name to request a unit from a group of identical units.
UNIT Parameter Definitions The following provides definitions for the subparameters you can use with the UNIT parameter. Subparameter Definition group-name Specifies a generic request for a device group. This is the most generic kind of request. In MVS, group-name specifies a particular category of device defined in MVS customization. In BIM-EPIC, valid groups are: device-type User Reference DISK or SYSDA specifies any disk device.
UNIT Parameter Examples Subparameter Definition cuu Specifies the drive address to be used. If cuu is specified, it must be separated from device-type by a comma and both subparameters must be enclosed in parentheses, for example, UNIT=(CART,3F0). In the following example, the UNIT parameter indicates that this is a tape dataset. BIM-EPIC will select a tape drive based on the dataset MODE specification in its catalog entry. * //TAPEOUT * // DD DSN=INVENTRY.
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. The first four subparameters are positional. The last subparameter, SER or REF, is both keyword and positional.
VOLUME Parameter Subparameter Definition RETAIN Prevents tape rewinding when the tape is closed. RETAIN is frequently used when processing multi-datasets. If neither PRIVATE nor RETAIN is specified, the tape is rewound when it is closed. RETAIN is ignored for disk datasets. volume-sequence-number Selects the first reel to process in a multi-volume group. The volume-sequence-number parameter is ignored for disk datasets.
VOLUME Parameter Examples In the following example, the tape is unloaded at close. * //TAPEIN * // DD DSN=INVENTRY.FILE, DISP=(NEW,KEEP),VOL=(PRIVATE) The following example shows how to automatically catalog a prime dataset and two new subdatasets. The datasets are stacked on one tape to create a multi-dataset group. PRIME.DSN.1 is the first dataset on the tape, NEWSUB.DSN.2 is the second dataset, and NEWSUB.DSN.3 is the third dataset.
DD Statements For Printer and Punch Datasets DD Statements For Printer and Punch Datasets Description DD statements used to assign printer and punch datasets. Syntax The following provides an example of a print command syntax. * //ddname Parameters Definitions 6-48 DD SYSOUT=x[,OPTION=SYSnnn] The following parameters are valid for printer and punch datasets.
DD Statements For Printer and Punch Datasets Parameter Definition SYSnnn Specifies the programmer logical unit. Use SYSnnn if the ddname itself is not a logical unit specification. For example, if your COBOL program includes the statement: SELECT PRINT-OUT ASSIGN SYS006-UR-1403-S-PRINT. then the DD statement would be: * //PRINT DD SYSOUT=A,OPTION=SYS006 If no COBOL external name is used, do not use OPTION, since the ddname is a logical unit specification.
DD Statements for In-Stream Datasets DD Statements for In-Stream Datasets Description Use a DD statement to assign a logical unit to the data stream, when a job stream contains in-stream data. VSE requires the in-stream data be placed after the EXEC statement. Syntax The following provides an example of an in-stream dataset syntax. * //ddname Parameters Definitions 6-50 DD specifier[,OPTION=SYSnnn] The following parameters are valid for in-stream datasets.
DD Statements for In-Stream Datasets Parameter Definition SYSnnn Specifies a programmer logical unit. Use SYSnnn if the ddname itself is not a logical unit specification. For example, if your COBOL program includes the following statement: SELECT CARD-IN ASSIGN SYS005-UR-2540R-S-CARDIN. then the DD statement would be: * //CARDIN DD *,OPTION=SYS005 DD DATA,OPTION=SYS005 or * //CARDIN If no COBOL external name is used, do not use OPTION, since the ddname is itself a logical unit specification.
DD Statements for Dummy Datasets DD Statements for Dummy Datasets Description Dataset definition (DD) statements can define dummy datasets. Syntax The following provides an example of a dummy dataset syntax. * //ddname Parameters Definitions Example DUMMY[,OPTION=SYSnnn] The following parameters are valid for dummy datasets.
7 Running Jobs With BIM-EPIC BIM-EPIC is designed to work with your existing JCL. However, on occasion, JCL changes are necessary. 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. Recommendations for JCL and EDDs are presented for each topic when relevant.
Using Unsupported Datasets Dataset Considerations Using Unsupported Datasets Description BIM-EPIC does not control datasets that are defined in the JCL with the following DTF names: IJSYSNR IJSYSPC IJSYSRS In addition, BIM-EPIC does not control datasets processed with the following system utilities: DITTO basic and control functions Note: BIM-EPIC can control DITTO file functions. 7-2 Connectivity Systems, Inc.
Using JCL and the DSN Catalog Using JCL and the DSN Catalog Description For tape output datasets, JCL parameters always override corresponding DSN Catalog information. For DASD output datasets, except for “retention period,” the only item in the catalog entry that can be overridden is the “number of tracks to be allocated.” This is taken from the // EXTENT following the appropriate // DLBL statement. That DLBL statement must have the BIM-EPIC option code “O” specified.
Using TLBL and DLBL Statements for Input Using TLBL and DLBL Statements for Input 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. In this case, all versions of the dataset are read, beginning with the current version and ending with the oldest version.
Defining Datasets with TBL, DBL and DD Statements Defining Datasets with TBL, DBL 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, the JCL can be very concise. Using the DSN Catalog instead of JCL can be simpler, less error-prone, and easier to change.
Naming Datasets Naming Datasets Description See “Multi-Dataset Processing” for guidelines on naming datasets. For generation datasets, specify the dataset name as it appears in the EDD. BIM-EPIC inserts this extension and uses it in its internal processing. Note: For disk datasets, do not specify the G=nnnnnn extension that appears in the VTOC. 7-6 Connectivity Systems, Inc.
Using LUB Allocation and the ASSGN Statement Using LUB Allocation and the ASSGN Statement Using ASSGN Statements When using LUB allocation and Automatic Volume Recognition (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. However, ASSGN statements must be used whenever LUB allocation is inhibited.
Using LUB Allocation and the ASSGN Statement 7-8 Option 64 in the numeric options on a TLBL OPTION=SYSnnn parameter on a DD statement A default SYS number in the BIM-EPIC dataset definition Connectivity Systems, Inc.
Controlled Datasets Disk Processing Controlled Datasets EXTENT Statements For most controlled datasets, the EXTENT statement is not used. 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” for additional information.
Start Track 1 Datasets Start Track 1 Datasets Description To define a Start Track 1 dataset, you must specify allocation information with an EXTENT statement. DLBL Statements The EXTENT statement for a Start Track 1 dataset differs slightly from the standard VSE EXTENT statement.
Reusing Space Reusing Space DSN Catalog If you want to write a new version of a disk dataset in the same location in order to reuse the space, catalog the dataset as work and zero secondary allocations. For example, you can indicate WRK using Online Manager or WRK=YES using TSIDMNT. JCL Requirements Each time the dataset is created or modified, consider inhibiting truncation. This leaves space in the extent for a larger dataset the next time the dataset is processed.
Labeled and Unlabeled Tapes Tape Processing Labeled and Unlabeled Tapes 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 enables you to convert to labeled processing without making program changes. BIM-EPIC does not affect user header label processing.
Rewind Options and MTC Statements Rewind Options and MTC Statements Description You do not need to use MTC statements to rewind or FSF your tapes. BIM-EPIC will position the tape automatically for input or output processing. You can also use the BIM-EPIC rewind options for output or input processing to override equivalent options in your program.
Multi-Volume Processing Multi-Volume Processing Description Multi-volume processing can be used to process up to 255 volumes per tape dataset version and up to 255 extents per disk dataset version. JCL Requirements There are no JCL requirements. BIM-EPIC automatically performs multi-volume processing. 7-14 Connectivity Systems, Inc.
Multi-Dataset Processing 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 tape volume or on multiple tape volumes. BIM-EPIC will automatically handle tape positioning for both input and output processing.
Multi-Dataset Processing Explicitly (using JCL) If the datasets are associated using TLBL statements, the length of the prime dataset name is limited to 17 characters. However, the subdataset names can be a maximum of 44 characters. This type of association is made by specifying the prime dataset name when the subdataset names are defined to the catalog. If the datasets are associated using DD statements, the length of the prime dataset name can be up to 44 characters.
Multi-Dataset Processing Tape size (SIZ) Vaulting method (VLT) Tape pool (TPL) Several important limitations apply when creating a subdataset EDD. These limitations are: JCL Requirements User Reference You must catalog the subdatasets using Online Manager or TSIDMNT, or autocatalog them using DD statements. You cannot use TLBL statements to autocatalog subdatasets. You must enter the prime dataset name correctly when a subdataset is defined to the catalog.
Multi-Dataset Processing ! You must prevent the tape from being rewound for all datasets except the last. This can be accomplished with any of the following methods: Option 3 in a TLBL statement VOL=(,RETAIN) in a DD statement OPT=NOREW in a DD statement You may want to specify a rewind or unload option code for the last dataset.
Multi-Dataset Processing Be sure the dataset is not already controlled before you attempt to catalog it using this method. If the prime dataset or any subdataset is already controlled, DISP=(x,CATLG) is ignored. Example 1 The following example is one of the easiest situations for creating a multi-dataset group. The program creates datasets with different DTF names, but each DTF uses the same logical unit. The datasets are defined in the first step and are created in the second step.
Multi-Dataset Processing The following describes the options used in the example above. Example 2 Code Action 1 Rewinds the tape (for the last dataset) 3 Inhibits rewind at close (for all but the last dataset) 8 Holds the drive assignment at close (for all but the last dataset) 64 Inhibits LUB allocation (for all datasets) The following example creates multiple datasets with the same DTF name. This process requires a dataset drop.
Multi-Dataset Processing The last dataset does not require the tape and drive to be held, nor does it require a dataset drop. Example 3 The following example creates multiple datasets with different DTF names. Because different DTFs use different logical units, a logical unit must be supplied in the dataset definitions.
Multi-Dataset Processing // JOB XYZ * -----------------------------------------------------+ * CATALOG A PRIME DSN AND THREE SUB DSN'S + * -----------------------------------------------------+ * // EXEC TSIDMNT CAT 'PRIME' CYC=2 CAT 'SUB1' NSU='PRIME' CYC=2 CAT 'SUB2' NSU='PRIME' CYC=2 /* * * -----------------------------------------------------------+ * CREATE A PRIME AND 2 SUB DSN'S USING BIM-EPIC DD FACILITY. + * PROGX PERFORMS 3 OPENS FOR DTFNAME TAPEOUT.
Multi-Dataset Processing The following describes the options used in the examples above. Option Action DSN='xxxx(+0)' Sets the generation dataset. Use (+0) in parentheses to indicate that this is a generation dataset. See the BIM-EPIC Installation and System Guide for additional information. 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.
Multi-Dataset Processing // JOB XYZ * * ----------------------------------------------------------+ * READ VERY.LONG.NAME.FOR.NEWSUB.3 AS INPUT. THE PRIME DATASET + * NAME (VERY.LONG.NAME.FOR.PRIME.1) MUST BE SPECIFIED AND + * REFERRED TO BY THE DD FOR THE SUBDATSET. PROGY+ * PERFORMS 1 OPEN FOR DTFNAME TAPEIN. * ----------------------------------------------------------+ * * //DUMMY DD DSN='VERY.LONG.NAME.FOR.PRIME.1(0)', * // UNIT=TAPE * //TAPEIN DD DSN='VERY.LONG.NAME.FOR.NEWSUB.
Sequential Datasets Types of Datasets Sequential Datasets Description For disk, allocation is on track boundaries for CKD devices. If you specify DLBL option code A or SPACE=(...,ROUND) on a DD statement, BIM-EPIC makes the allocation on cylinder boundaries. Otherwise, there are no special requirements for sequential dataset processing. User Reference Connectivity Systems, Inc.
Direct Access Datasets Direct Access Datasets Description When using 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. When using uncontrolled direct access datasets with the configuration option UNCDSK: There is no limit to the number of extents when UNCDSK=NO. There is a limit of 5 extents when UNCDSK=YES.
ISAM Datasets ISAM Datasets Description BIM-EPIC can control ISAM datasets. The following MVT restrictions affect BIM-EPIC ISAM dataset processing. Note: VSE no longer supports ISAM. The following restrictions apply only to MVT and MVT/VSE. 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.
ISAM Datasets For Start Track 1, the SYS number for the overflow extent must be different from the SYS number for the index and prime data areas, as shown in the following example: // // // // DLBL MASTER,'EPIC.ISAM.MASTER.FILE',,ISE EXTENT SYSO4O,POOL80,4,1,1,15 Index EXTENT SYS041,POOL80,1,2,1,90 Prime EXTENT SYSO42,POOL80,2,3,1,30 Overflow For each DD statements, specify DCB=DSORG=IS or DCB=DSORG=ISU.
VSAM and VSAM-Managed SAM 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 your IBM documentation for additional information. You can have the VSAM dataset location and activity recorded in the DSN Catalog.
Common Work Datasets Common Work Datasets Description BIM-EPIC can release disk space or tapes used for controlled temporary datasets at close or at end-of-job. Examples of these datasets are compiler work files which are intermediate output files from various “translation” programs like those used for Command Level CICS, SQL, DB2, etc. To automatically delete these datasets without using the JCL requirements options below, use the BIM-EPIC Common Work Datasets (CWDS). CWDS dataset names begin with $$$.
CPU and Partition Independence CPU and Partition Independence Description CPU and partition independence are normally used with work datasets. CPU and partition independence 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 is no duplication of the dataset names in different partitions or machines. For example, in your JCL you could specify ===.SORTWRK1 as the dataset name.
CPU and Partition Independence Example The following dataset will have a unique name in the VTOC in any partition or CPU in which the dataset is used. // DLBL WORKOUT,'===.WORKFILE.1' 7-32 Connectivity Systems, Inc.
Common Work Datasets Common Work Datasets 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, for example $$$. or £££. if in the U.K., BIM-EPIC recognizes the dataset as a CWDS. The $$$. or £££. in the dataset name is replaced by the CPU ID and partition ID that executed the job.
TYPEFLE=WORK DTF Datasets TYPEFLE=WORK DTF Datasets 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.
Compiler Work Datasets Compiler Work Datasets Description \Compiler work datasets have the same requirements as TYPEFLE=WORK DTF datasets, described earlier in this chapter. However, there are a few additional requirements that are described in this section. DSN Catalog Compiler work datasets should be controlled with a disk pool that contains volumes of the same device type as SYS001, SYS002,SYS003, SYS004, and SYSLNK. JCL Requirements There are several JCL requirements you must consider.
Uncontrolled Datasets Uncontrolled Datasets Description Any dataset that is not controlled using the DSN Catalog or Start Track 1 is called an uncontrolled dataset. With a few exceptions, uncontrolled datasets are not provided with any additional features than are available when using standard VSE JCL. For uncontrolled tape datasets, BIM-EPIC provides protection for all output tapes to ensure that any tape with an active status in the BIM-EPIC Catalog is not used.
Physical IOCS Processing Physical IOCS Processing Description Some VSE system utilities, sort programs, report writers, database utilities, and other programs process datasets with Physical IOCS (PIOCS) instead of Logical IOCS (LIOCS). 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 the issues described below, you can make any PIOCS program work with BIM-EPIC-controlled datasets.
Physical IOCS Processing Utility Programs Many programs that use PIOCS do not issue an open request that BIM-EPIC can recognize. In this case, you can satisfy the BIM-EPIC open processing requirements by executing the TSIDASS OPEN function to simulate the opening of both input and output datasets. This is required only when the program does not issue an open or does I/O to the dataset before the dataset is opened.
Sorting with BIM-EPIC Sort Programs Sorting with BIM-EPIC Description This section describes the considerations necessary to use BIM-EPIC controlled datasets with sort programs. Specifically, this section covers the following sort programs: SYNCSORT using BIM-EPIC Interface IBM SORT beginning with DFSORT 3.3 CA-SORT All sort programs check the assignment of a particular logical unit number (SYSnnn) before actually opening a particular file.
Using the Sort Interface (TSIDSRT) Assigns tape datasets to a dummy tape device and opens disk datasets to satisfy pre-open checking Calls the sort program Uses the SORTE35 exit routine to write the SORTOUT dataset Allows access to DTF information necessary to support such BIM-EPIC options as disk dataset truncation, reblocking, and logging of block size, record size, and record count Closes SORTWK datasets to enable the datasets to be deleted Unless you are using a sort program that ha
Sorting Specifics Sorting Specifics Many BIM-EPIC features rely on DTF information that is automatically provided by the Logical Input Output Control Systems (LIOCS) access methods. BIM-EPIC also relies on the standard open, close, end-of-extent, and end-of-reel processing used by LIOCS. Not all sort programs use LIOCS to process data so the functionality of the BIM-EPIC features can vary depending on which sort product is used.
Sorting Specifics SYNCSORT using BIM-EPIC Interface SYNCSORT offers options to improve compatibility with BIM-EPIC. See the SYNCSORT Installation Guide for information describing these options. In addition, BIM-EPIC has special options which must be activated when using SYNCSORT. See the BIM-EPIC Installation and System Guide for additional information. When the special options are activated, LUB allocation and secondary SORTWK allocations are supported.
Using SORTWK Datasets Using SORTWK Datasets Description To provide optimal use 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 There are two DSN Catalog requirements to consider. JCL Requirements Catalog SORTWK datasets as work. If you use Online Manager, specify WRK. If you use TSIDMNT, specify WRK=YES.
Using SORTWK Datasets Sort defaults (standard or user-specified: SYS001 for SORTOUT, SYS002 for SORTIN1, SYS003 for SORTWK, and so on) Note: If LUB allocation is active for sort datasets, the SYS numbers checked by the sort in the pre-open processing may not be the same SYS numbers assigned by BIM-EPIC when the open actually occurs. JCL Requirements Pre-open assignments can be completed by using any of the following media: Media Method Disk Permanent assignments in partition start-up procedure.
Controlling IDCAMS Backup Datasets Additional Functionality Controlling IDCAMS Backup Datasets Description You can use BIM-EPIC to control the IDCAMS backup dataset. This backup dataset is produced by the BACKUP command and is used by the RESTORE command. IDCAMS allows 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.
Controlling IDCAMS REPRO Datasets Controlling IDCAMS REPRO Datasets Description You can use BIM-EPIC to control IDCAMS REPRO non-VSAM sequential datasets for both input and output. 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 and single or multiple tape volumes may be used. JCL Requirements for Tape There are two JCL requirements you must consider.
Using IDCAMS IMPORT/EXPORT Commands Using IDCAMS IMPORT/EXPORT Commands Description You can use BIM-EPIC to control the portable file produced by the EXPORT command and read by the IMPORT command. 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 and single or multiple tape volumes may be used. JCL Requirements for Tape There are two JCL requirements you must consider.
Using LIBR BACKUP/RESTORE Commands Using LIBR BACKUP/RESTORE Commands Description You can use BIM-EPIC to control the tape datasets created by the LIBR BACKUP command and read by the LIBR RESTORE command. DSN Catalog Only prime dataset definitions are allowed. Therefore, multi-dataset tape groups are specifically disallowed. JCL Requirements There are several JCL requirements you must consider. Each controlled dataset must be defined with a TLBL statement or DD statement.
Using DITTO Using DITTO Description You can use BIM-EPIC to control tape and sequential disk files logically accessed by DITTO. However, DITTO requires excessive JCL requirements. You can use TSIDDTD and TSIDDMP, which require minimal JCL, for equivalent results. When card-image processing is required, use your sort program if your sort program supports card-image processing or IDCAMS REPRO. DSN Catalog Only prime dataset definitions are allowed.
Using DITTO Examples 7-50 Many sample job streams for DITTO applications are supplied when BIM-EPIC is installed. See the BIM-EPIC Installation and System Guide for additional information. Connectivity Systems, Inc.
Using VSE/POWER ACCOUNT Command Using VSE/POWER ACCOUNT Command Description You can use BIM-EPIC to control tape and sequential disk files created by the VSE/POWER ACCOUNT command. DSN Catalog There are no tape dataset restrictions. For disk, the pool must be made up of the exact same DASD type as the type 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 they are needed.
Using VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling Using VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling Description With the introduction of standard label support for POWER tape spooling of print data, punch data, and POFFLOAD tapes, it is possible to use BIM-EPIC controlled tapes and dataset names for these functions even though some restrictions apply.
Using VSE/POWER PDISPLAY, POFFLOAD and Printer/Punch Tape Spooling 4140A NO ALTERNATE DRIVE ASSIGNED ... SYSXXX=CUU Since VSE/POWER has the tape drive assigned, BIM-EPIC is unable to use AVR on other tape drives to determine an available scratch tape. The operator must mount a fresh scratch tape on the indicated drive and respond with NEWTAP.
Setting DB2 Tape Output Functions Setting DB2 Tape Output Functions Description DB2 is a long running task that manages database files in a VSE environment. DB2 has the ability to archive database files and their corresponding journal files. This is done by invoking the VSE Operator Communications Facility in the DB2 partition, for example, MSGxx, where xx is the DB2 partition ID. DB2 then prompts the console operator with various questions that initiates the archive process.
Setting DB2 Tape Output Functions JCL Examples If TAPLUB=NO is set: // TLBL ARILARC,’yourDsn1’ // TLBL ARIARCH,’yourDsn2’ TAPLUB=YES or TAPLUB=nnn // TLBL ARILARC,’yourDsn1’,,,,,,64 // TLBL ARIARCH,’yourDsn2’,,,,,,64 or // TLBL ARILARC,’yourDsn1’,,,,,,66 // TLBL ARIARCH,’yourDsn2’,,,,,,66 User Reference Connectivity Systems, Inc.
Identifying VSE/ICCF and Interactive Partition GETVIS Requirements Identifying VSE/ICCF and Interactive Partition GETVIS Requirements Description The following GETVIS discussion applies to ICCF pseudo partitions and not to the ICCF partition. An ICCF pseudo partition has 48K of GETVIS. This allocation cannot be changed. If BIM-EPIC is active in the pseudo-partition, more than 48K of GETVIS will often be required to initiate many programs, for example, DTSUTIL.
Using the COBOL II Library Management Feature Using the COBOL II Library Management Feature Description BIM-EPIC requires the COBOL II Library Management feature be used when compiling COBOL II programs. Use the COBOL II CBL RES option to accomplished this task. In some cases, you may have COBOL II software which was not compiled with the Library Management feature. Special JCL is required to run these programs with BIM-EPIC. DSN Catalog No special entries are required.
Using the COBOL II Library Management Feature /* // EXEC PROGA 7-58 Connectivity Systems, Inc.
Restarting From a Checkpoint JCL Functions Restarting From a Checkpoint Description To prepare to restart programs from a checkpoint: 1. Close all output datasets using TSIDMNT or Online Manager CLOSE function. 2. 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.
Restarting From a Checkpoint 8. Execute the restart job. Example The following example shows how 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 code 64 inhibits LUB allocation. When a checkpoint is embedded, it is written to the same output tape as the output dataset using an assignment of SYS019.
Choosing the Device Type Choosing the Device Type Description Generic Device Independence (GDI) and Generic Device Independence for Unit Record Devices (GDIUR), sometimes called storage media independence, allow you to choose the type of media on which your dataset will be stored. With GDI, you can process the dataset on either tape or disk, without having to change the media type in the program’s dataset definition.
Choosing the Device Type No ASSGN statement or CLOSE statement is needed. GDIUR ensures that system logical units can never be left assigned to disk. Programs that use GDIUR can also take advantage of the BIM-EPIC reblocking facility to save disk space and improve performance. Eligibility You can use GDI or GDIUR for uncontrolled and controlled datasets. However, the following issues must be considered.
Choosing the Device Type JCL Requirements For uncontrolled tape or disk datasets, use the proper label, for example, TLBL, DLBL, or a DD statement with UNIT. Note: This applies to GDI only. You cannot use GDIUR with uncontrolled datasets. For controlled datasets, no JCL changes are required for GDI input (GDI only). For GDI output and GDIUR input and output, you must invoke GDI by changing the label type to TLBL or DLBL, or device type to UNIT=type.
Controlling System Datasets with VSE Device Independence Controlling System Datasets with 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 There are several JCL requirements you must consider.
Using Dummy Datasets and ASSGN IGNORE Using Dummy Datasets and ASSGN IGNORE Description Dummy processing and ASSGN IGNORE are only supported for LIOCS sequential access methods. DSN Catalog No special entries are required. JCL Requirements There are several JCL requirements you must consider.
Using Concatenating Datasets Using 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.
Using Concatenating Datasets In the following example, all versions of DAILY.TRANS are read with one open. For input with different dataset names, request concatenation explicitly. You must specify the version number of each version to be read in the DSN parameter. Specify a ddname only on the first statement. * //INPUT1 DD DSN='DAILY.TRANS',DISP=(OLD,KEEP) The following example concatenates versions 1 through 4 of the DAILY.TRANS dataset and version 1 of the DAILY.DEP dataset.
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. For... Use... DLBLs T TLBLs 16 or D DD statements Automatic.
Running Test Jobs With Production Datasets Running Test Jobs With Production Datasets Description The BIM-EPIC 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 option can include wildcard characters for greater flexibility in creating test job names. A question mark (?) specifies that any character in that position is a valid character.
Running Test Jobs With Production Datasets 7-70 Connectivity Systems, Inc.
8 BIM-EPIC Utilities This chapter describes how to use BIM-EPIC utility programs to control files processed with physical IOCS (PIOCS) instead of logical IOCS (LIOCS). In addition, this chapter presents the dataset copy and dump utilities TSIDDTD and TSIDDMP and the VSE label access subroutines TSIDGLB and TSIDPLB. See Chapter 7, “Running Jobs With BIM-EPIC,” for additional information on using these utilities. Chapter Contents Utility Programs User Reference Connectivity Systems, Inc.
Pre-Open Processing (TSIDASS) Utility Programs Pre-Open Processing (TSIDASS) Description TSIDASS processes controlled files used in programs that do not issue OPEN requests or that perform pre-open checking of assignments. You can also use TSIDASS to make assignments to SYSRDR, SYSIPT, SYSLST, and SYSPCH. The TSIDASS functions are done with the following control statements: ASSGN satisfies pre-open assignment checking for tape datasets.
Pre-Open Processing (TSIDASS) When the program issues an OPEN request for the dataset, BIM-EPIC then performs a normal device assignment to the real device. You can also use ASSGN to make assignments to the system logical units SYSRDR, SYSIPT, SYSLST, and SYSPCH. When you make these assignments, you must submit these statements last. TSIDASS stops processing control statements after one of these assignments is made.
Pre-Open Processing (TSIDASS) Syntax The following is an example of an OPEN statement syntax. OPEN dtfname,SYSxxx {,INPUT|,OUTPUT} Parameters The following provides a description of the parameters you can use with an OPEN statement.
Pre-Open Processing (TSIDASS) Syntax The following is an example of an RSTRT statement syntax. RSTRT dtfname,SYSxxx{,INPUT|,OUTPUT}[ ,EXT=nn] Parameters The following provides a description of the parameters you can use with an RSTRT statement.
Pre-Open Processing (TSIDASS) CHECK Parameter Definitions The following provides a description of the parameters you can use with a CHECK statement. Parameter Required? Valid Default dtfname Yes 1 to 7 characters None The following provides definitions for the parameters you can use with a CHECK statement. Parameter Definition dtfname dtfname identifies the dataset to be opened.
Pre-Open Processing (TSIDASS) // TLBL FILEIN,'PRODUCT.ID.MASTER',,,,,5 // EXEC TSIDASS CHECK FILEIN /* User Reference Connectivity Systems, Inc.
Sort Interface (TSIDSRT) Sort Interface (TSIDSRT) Description TSIDSRT is an interface program between BIM EPIC and your sort program. TSIDSRT solves problems that can occur with some SORT utility programs during both open and close. TSIDSRT calls your sort program to do the sort, but allows BIM EPIC to satisfy pre-open assignment checking, to truncate the SORTOUT file, and to close and delete SORTWK areas.
Sort Interface (TSIDSRT) RECORD TYPE=F,LENGTH=80 INPFIL BLKSIZE=1600 OUTFIL BLKSIZE=4000 END /* /& User Reference Connectivity Systems, Inc.
Deleting Datasets (TSIDDEL) Deleting Datasets (TSIDDEL) Description TSIDDEL deletes disk work datasets that are not closed by the same program that opens them. At any point in the job or job step, TSIDDEL can be used to free up disk space for other processing. These datasets can be either Start Track 1 or cataloged work datasets. Deletion of generation disk datasets is not supported. TSIDDEL is available as a batch program and as a callable subroutine. When using a DLBL, specify the DLBL option code D.
Deleting Datasets (TSIDDEL) Definitions Example The following provides definitions for the parameters you can use with a TSIDDEL statement. Parameter Definition dtfname Specifies the DTF name or DD name of the dataset to be deleted. The following example creates the SORTWK1 dataset in the first step. Option code D 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.
Copying and Merging Datasets (TSIDDTD) Copying and Merging Datasets (TSIDDTD) Description TSIDDTD is a dataset-to-dataset copy/merge utility program. You can use TSIDDTD to copy a single dataset or to merge multiple input datasets into a single output dataset. TSIDDTD uses standard LIOCS access methods enabling BIM-EPIC to completely control the input and output datasets. 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, TSIDDTD can only process tapes which follow standard LIOCS format conventions.
Copying and Merging Datasets (TSIDDTD) You can use control statement parameters to: Specify alternate DTF names Specify record characteristics Control unlabeled tape processing Limit total output Select specific records End processing before end-of-file (EOF) is reached on input All control statements will be processed before TSIDDTD begins the copy or merge operation. Parameters can be placed in columns 1 through 71 and must be separated with commas.
Copying and Merging Datasets (TSIDDTD) Parameter Required? Valid value No See text None HDRINFO No None OFF INNAME No 1 to 7 characters INPUT INPUT No '?' or 1 to 32767 None LRECL No 1 to 99999 None NOREWIN/NORE No WOUT None OFF NOTPMK No None OFF OBLKSIZE No 1 to 32767 Input BLKSIZE OUTNAME No 1 to 7 characters OUTPUT RECFM No F|V|S|U EDD information in catalog or U RECS No 1 to 999999 All RUNIN/RUNOUT No None OFF SEL No See FEOF All SKIP No 1 to 999
Copying and Merging Datasets (TSIDDTD) Parameter Definition FEOF Specifies a condition that causes TSIDDTD to act as if EOF was reached on input. If multiple parameters are specified on a single control statement, only another FEOF parameter may follow an FEOF parameter. When any one of multiple FEOF conditions is met, EOF will be assumed. Up to a total of 20 FEOF parameters can be submitted per TSIDDTD execution. When FEOF is specified, all FEOF subparameters are required and positional.
Copying and Merging Datasets (TSIDDTD) Parameter Definition INNAME Specifies an alternate input DTF name. INPUT Specifies the number of input datasets to merge into a single output. If the value ? is specified, for example, INPUT=?, the message EP712 will be issued. This message requires the operator to respond with the number of files to merged. LRECL Defines the dataset record size. For catalog-controlled datasets, the LRECL in the DSN Catalog is used if available.
Copying and Merging Datasets (TSIDDTD) Parameter Definition SEL Specifies selection criteria for copying. Subparameters are identical to FEOF subparameters. If the data matches the expression, the data is copied. If the data does not match the expression, the data is skipped. If multiple parameters are specified on a single control statement, only another SEL parameter may follow a SEL parameter. When any SEL condition is met, the data is copied.
Copying and Merging Datasets (TSIDDTD) The following example makes a duplicate copy of a multi-file tape containing three datasets. All of the datasets are controlled, so no control statements are necessary. TSIDDTD is executed three times, once for each dataset. In this example, use TLBL option 64 (Inhibit LUB allocation), option code 8 (Hold assignment), and option code 3 (No rewind) on the first two TLBL statements.
Printing Datasets (TSIDDMP) Printing Datasets (TSIDDMP) Description TSIDDMP is a dataset print utility program. You can use TSIDDMP to completely or selectively print a dataset in hex or character format. TSIDDMP will also print report files that have been written to disk or tape. TSIDDMP uses standard LIOCS access methods enabling BIM-EPIC to easily control the input datasets. TSIDDMP supports any sequential dataset with a fixed, variable, spanned, or undefined record format.
Printing Datasets (TSIDDMP) If record type, record size, and block size are not specified and cannot be obtained from the DSN Catalog, TSIDDMP will use an undefined record format with a block size of 32767. Note: Record type, record size, and block size may not be available in the catalog for some catalog-controlled datasets if they were created by programs that use PIOCS.
Printing Datasets (TSIDDMP) Definitions Parameter Required? Valid.7 Default type No C or X C value No See text None HDRINFO No None OFF INNAME No 1 to 7 characters INPUT LRECL No 1 to 32767 None NOREW No None OFF 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 The following provides definitions for the parameters you can use with a TSIDDEL statement.
Printing Datasets (TSIDDMP) Parameter Definition FEOF Specifies a condition that causes TSIDDMP to act as if EOF was reached on input. If multiple parameters are specified on a single control statement, only another FEOF parameter may follow an FEOF parameter. When any one of multiple FEOF conditions is met, EOF will be assumed. Up to a total of 20 FEOF parameters can be submitted per TSIDDMP execution. When FEOF is specified, all FEOF subparameters are required and positional.
Printing Datasets (TSIDDMP) Parameter Definition INNAME Specifies an alternate input DTF name. LRECL Defines the dataset record size. For catalog-controlled datasets, the LRECL in the DSN Catalog is used, if available. If LRECL is not specified, it will be set to one of the following values: The value of BLKSIZE. Undefined, if BLKSIZE is not specified. In this case, the input dataset is treated as unblocked. NOREW Prevents rewind of the input tape at close.
Printing Datasets (TSIDDMP) Examples The following example prints the entire contents of a catalog-controlled disk dataset in hex format. Control statements are not required. // JOB TSIDDMP DUMP DISK DATASET IN HEX // DLBL INPUT,'input.data.set' // EXEC TSIDDMP /* /& The following example prints the first 100 records of a file. The printout will be in character format (CTLCHAR forces CHARONLY). // JOB TSIDDMP PRINT BLOCKED REPORT TAPE IN CHARACTER FORMAT // TLBL INPUT,'input.data.
Accessing the VSE Label Area (TSIDGLB and TSIDPLB) Accessing the VSE Label Area (TSIDGLB and TSIDPLB) Description TSIDGLB and TSIDPLB are subroutines that read and write VSE labels in the VSE Label areas. TSIDGLB reads system-standard, partition-standard, and partition user labels. TSIDPLB modifies the label that TSIDGLB acquired. TSIDPLB writes the label to an area BIM-EPIC maintains. When BIM-EPIC is active, TSIDPLB checks for the label in this area before searching the VSE label area.
Accessing the VSE Label Area (TSIDGLB and TSIDPLB) TSIDGLB returns the label beginning at LBLFILNM. TSIDPLB writes the label from the same area. To read a label: Step Action 1 Move the DTF name of the label to be processed to FILENAME. 2 Call TSIDGLB, specifying FILENAME and LBLRETCD. The following is an example of TSIDGLB. ... MVC FILENAME,=CL7'INPFILE' CALL TSIDGLB,(FILENAME,LBLRETCD) ... COPY TSIDGLB ... To write a label: Step Action 1 Read the label using the TSIDGLB procedure.
BIM-EPIC Catalog-VTOC Reconciliation System BIM-EPIC Catalog-VTOC Reconciliation System Description 8-28 The reconciliation system consists of two programs, TSIDCVF and TSIDCVC. TSIDCVF reads the catalog and the VTOCs associated with a pool and outputs two files, one for the catalog and one for the VTOC. The catalog will be enqueued while TSIDCVF runs. TSIDCVC compares the two files, produced by TSIDCVF, looking for discrepancies. TSIDCVC then outputs any mismatches to SYSLST.
Selecting files to compare by pool (TSIDCVF) Selecting files to compare by pool (TSIDCVF) Description TSIDCVF creates two files, one contains the list of VTOC files and one contains the list of catalog files. Syntax The following is an example of a TSIDCVF command syntax. POOL poolid Definitions Examples The following provides the definition for the parameter you can use with a TSIDDEL statement. Parameter Definition poolid Specifies the name of a BIM-EPIC DASD pool.
Comparing catalog to VTOC (TSIDCVC) Comparing catalog to VTOC (TSIDCVC) Description TSIDCVC compares the two files created by TSIDCVF and creates a report showing any discrepancies. The files must first be sorted according to the example before being used by TSIDCVC. The TSIDCVC program does not take any input cards. Examples The following example uses BIM-EPIC controlled DSNs. As in the above TSIDCVF example, Start Track 1 DSNs can be used if desired. // DLBL SORTIN1,'CATALOG.
9 Job Management Control Language The BIM-EPIC 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 Using JMCL Statements Using JMCL Parameters Using the JMCL Interface User Reference Connectivity Systems, Inc.
VSE JCL Statements Using JMCL Statements VSE JCL Statements Description The BIM-EPIC Job Management Control Language (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 determine where the parameter can be specified.
Using JOB Statements Using JOB Statements Description When using JOB statements, EXEC statements, and OPTION statements, the JMCL parameters must follow at least one VSE keyword, or a comma between two spaces, and precede any comments. Syntax The following provides an example of an OPTION statement syntax. // JOB jobname parameters comments // EXEC program parameters comments // OPTION option parameters comments Example In the following example, the job name is PAYROLL.
Using Comment Statements Using Comment Statements Description VSE comment statements can use special JMCL parameters to invoke JMCL. See “Using JMCL Parameters” in this chapter for additional information. Syntax The following is an example of a VSE command syntax. * JMCL parameters Example The following is an example of a command statement with the parameters defined. * JMCL NAME=BGSTEP 9-4 Connectivity Systems, Inc.
JCL Syntax Checking Using JMCL Parameters JCL Syntax Checking Description HOLD JMCL parameters enable you to perform the following tasks: Retain datasets that have been flagged for purge (HOLD) Cancel a job if the job exceeds a specified time limit (TIME=n) Specify special processing for restarting canceled jobs (TYPRUN=RESTART) Prevent some job cancellations by requesting DD statement syntax checking (TYPRUN=SCAN and TYPRUN=SCANS) HOLD prevents datasets that have been flagged for purge a
JCL Syntax Checking Definition Example The following provides definitions for the parameters you can use with TIME. Parameter Definition nnnn Specifies the time period in minutes. Valid time periods are from 1 minute to 1440 minutes. No error message occurs if a number is specified out of this range. If you specify a number greater than 1440, the time limit is set to 1440, which indicates an unlimited time execution. The following is an example of a TIME command syntax.
JCL Syntax Checking Example Parameter Definition RESTART Restarts your job. When a job cancels, you may want to restart it at a job step other than the first step of the job. You can branch to the desired step with a JMCL GOTO parameter. However, if you have specified the JMCL parameter HOLD or configuration option PURBYP=YES, disk datasets flagged for purge are not purged when a job cancels. If you bypass steps with GOTO, work datasets created in those steps need to be specially purged.
Condition Checking and Branching Condition Checking and Branching Description The Condition Checking and Branching feature of JMCL allows you to bypass JCL statements without deleting them or making them comments before submitting the job. Condition checking using the IF parameter allows you to check whether certain conditions exist before you branch to a new part of the job using GOTO. Syntax The following is an example of a JMCL command syntax.
Condition Checking and Branching Parameter Definition NAME Marks the destination of the GOTO branch. If you bypass SYSIPT data during the branch, you must use the DATA parameter. See IF and Conditions for additional information. For example: {label | JOBEND} If you are restarting a job, you may need to use TYPRUN=RESTART. GOTO=label Note: If the step executed in the restart checks for a condition code, that condition code may be invalid at restart time.
IF and Conditions IF and Conditions Description IF tests for conditions that you specify. IF can test the current condition code, highest condition code, VSE cancel code, date, time, CPU, partition, and global constant. You can use IF to test multiple conditions using either the AND condition or the OR condition. See “Setting Values” in this chapter for additional information. When IF is used with GOTO, the branch occurs if the condition is true.
IF and Conditions Definitions The following provides definitions for the parameters you can use when using IF and conditions. Parameter Definition type Specifies the type of input data to be tested: operand Use... To test the... CC current condition code CPU CPU ID HC highest condition code DOSCC VSE cancel code PART partition ID DATE current date TIME current time Gnn global constant Specifies the kind of test: Use... To test whether the input data is...
IF and Conditions Example Parameter Definition TIME Specified in hh-mm-ss format. To test only a portion of the date and time, supply only the portion you want to test. You can use asterisks (*) as fillers for beginning parts of the field. For example, to test for the first day of the month, specify IF=(DATE EQ **-**-01). To test for January, specify IF=(DATE EQ **-01). The following provides several examples of IF job statements.
Setting Values Setting Values Description You can establish condition code values and a maximum of fifteen global constants with JMCL parameters. These constants can be tested with the IF parameter. SETC SETC sets the current condition code to a specified number. This action updates the highest condition code, if appropriate.
Setting Values 9-14 Parameter Definition constant Specifies the value of the constant. You can use spaces. Connectivity Systems, Inc.
Symbolic Replacements Symbolic Replacements Description Symbolic replacements replaces a set of characters found in your JCL. These replacements are useful for setting JCL subparameters or comments at execution time. 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.
Symbolic Replacements Example In the following example, &1 is changed to PAYROLL.INPUT. * JMCL &1='PAYROLL.INPUT' // DLBL INPUT,'&1' becomes // DLBL INPUT,’PAYROLL INPUT’ 9-16 Connectivity Systems, Inc.
RESET RESET Description RESET nullifies most JMCL parameters. You can use RESET to set the current or highest condition code to zero, nullify GOTO branches, and nullify TIME control over a job. For best results, 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. When RESET is specified on a JOB statement, it is processed before any other JMCL parameters.
RESET Example The following restart job 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.
TSIDJC2 Using the JMCL Interface TSIDJC2 Description Your batch program can interface with BIM-EPIC Job Management Control Language (JMCL) by calling the TSIDJC2 subroutine. TSIDJC2 can retrieve the following: DOS job name Program name Current date (mm/dd/yy) Current time (hh.mm.
TSIDJC2 The TSIDJC2 subroutine can be called from any language that uses standard VSE calling conventions. 9-20 Connectivity Systems, Inc.
Retrieving JMCL Data Retrieving JMCL Data GET REQUEST (G) Data can be retrieved from the JMCL system by passing the character G to TSIDJC2 in the request byte of the parameter list. If you are using TSIDJC2.A, this byte is labeled JCSREQ. If you are using TSIDJC2.C, this byte is labeled JCS-REQ. Control is returned to the next instruction following the CALL statement. COBOL Example The following example is a GET request in COBOL.
Updating JMCL Data Updating JMCL Data Description JMCL data can be updated by passing the character P to TSIDJC2 in the request byte of the parameter. If you are using TSIDJC2.A, this byte is labeled JCSREQ. If you are using TSIDJC2.C, this byte is labeled JCS-REQ. A PUT request updates the current JMCL condition code, the highest JMCL condition code, all JMCL symbolics, and all global constants.
Updating JMCL Data If you are using TSIDJC2.C, global constants G01 through G15 correspond to the parameter data fields JCS-GLOBAL-CONS-1 through JCS-GLOBAL-CONS-15. If the new global constant is less than 16 characters, the global constant must be left justified and padded with spaces on the right. To remove a global constant, clear the global constant data field with hex zeros or LOW-VALUES. COBOL Example The following example is a PUT request in COBOL.
TSIDJC2 Return Codes TSIDJC2 Return Codes Description TSIDJC2 returns a value in the return code byte of the parameter list. If you are using TSIDJC2.A, this byte is labeled JCSRC. If you are using TSIDJC2.C, the byte is labeled JCS-RC. All return codes are one-byte character values. Values 9-24 The following describes the TSIDJC2 return codes. Return Code Description 0 Successful completion of the GET or PUT request. 1 Neither BIM-EPIC nor the JMCL system is active.
Executing CP Commands Executing CP Commands Descriptoin You can execute any VM/CP command in your VSE job stream using the JMCL 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 The following is an example of a CP command syntax.
Executing CP Commands 9-26 Connectivity Systems, Inc.
10 BIM-EPIC Job Scheduling The BIM-EPIC job scheduling system can be used to control execution across all partitions and VSE machines sharing the same DSN Catalog. Chapter Contents Job Scheduling Activities Event Scheduling Activites Executing Various Activities Executing in CICS User Reference Connectivity Systems, Inc.
Scheduling Activities Job Scheduling Activities Scheduling Activities Description When a job, step, or process is complete, 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*. This event name is assigned by you so you can identify completed events. Like versions of a tape or disk dataset, posted events become eligible for scratch according to the retention criteria cataloged for the dataset. If *EPIC.EVENT.
Event Posting and Release of Matching Jobs (TSIDREL and TSIDCREL) Event Scheduling Activites Event Posting and Release of 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. In addition, the POWER job name must match the event name posted.
Event Posting (TSIDLOC and TSIDCLOC) Event Posting (TSIDLOC and TSIDCLOC) Description 10-4 TSIDLOC and TSIDCLOC post events. They do not release jobs. When you use TSIDLOC or TSIDCLOC, dependent jobs must issue a check for the posted event using TSIDCHK or TSIDCCHK. Connectivity Systems, Inc.
Event Checking (TSIDCHK and TSIDCCHK) Event Checking (TSIDCHK and TSIDCCHK) Description TSIDCHK and TSIDCCHK are used within a job to determine if an event has been posted before continuing with a dependent task. If the event has been posted, the job continues without interruption. If you use TSIDCHK to check for the event and the event is not posted, execution is interrupted. TSIDCHK issues a message to the operator and asks whether the job should be canceled or suspended.
Event Deletion (TSIDUNL and TSIDCUNL) Event Deletion (TSIDUNL and TSIDCUNL) Description TSIDUNL and TSIDCUNL delete posted events. Use TSIDUNL and TSIDCUNL to delete an event after all dependent tasks have completed. This is important if another processing cycle occurs before the event is scratched automatically during TSIDUTL processing. If you do not delete the events, they become eligible for scratch. 10-6 Connectivity Systems, Inc.
Executing in Batch Jobs Executing Various Activities Executing in Batch Jobs Description TSIDREL, TSIDLOC, TSIDCHK, and TSIDUNL can be executed in batch jobs instead of being invoked through a CALL routine. JCL Requirements The following example shows the JCL requirements for executing a batch job. // OPTION SYSPARM='event-name' // EXEC TSIDxxx // OPTION SYSPARM=' ' Two OPTION statements are required. One OPTION statement is required to specify the event name as a SYSPARM.
Executing Standard Processing Subroutines Executing Standard Processing Subroutines Description TSIDREL, TSIDLOC, TSIDCHK, and TSIDUNL are callable subroutines for non-CICS programs. Standard linkage conventions apply to all four subroutines. Processing Requirements To process requirements for TSIDREL, TSIDLOC, and TSIDUNL: Examples Step Action 1 Perform the event task. 2 Move the event name to the EVENT-NAME field.
CICS Subroutines Executing in CICS CICS Subroutines Description TSIDCREL, TSIDCLOC, TSIDCCHK, and TSIDCUNL are CICS subroutines that can be called from a CICS command-level program.
Return Codes Return Codes TSIDCREL The following describes the TSIDCREL return codes. Return Code Description 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.
Return Codes TSIDCCHK TSIDCUNL User Reference The following describes the TSIDCCHK return codes. Code Description M The event name is missing or invalid. N The event is not posted. Y The event is posted. The following describes the TSIDCUNL return codes. Code Description 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.
Processing Requirements Processing Requirements Description To process the TSIDCHK subroutines: Step Example Action 1 Move the event name to the EVENT–NAME field. See "Job Scheduling Activities" in this chapter for details describing event–name limitations. 2 Link to the subroutine. 3 Check the return code passed and process accordingly. The following is an example of a TSIDCHK subroutine. WORKING-STORAGE SECTION. 01 EVENT. 02 EVENT-NAME PIC X(08). 02 EVENT-RETURN-CODE PIC X(01).
Creating Job Setup/Run Sheets (TSIDFAV) Creating Job Setup/Run Sheets (TSIDFAV) Description Use TSIDFAV to create Job Setup/Run Sheets. UPSI Settings The following provides descriptions of the values associated with the TSIDFAV utility. Setting Action // UPSI 1XXXX Print comment cards. Modes of Execution User Reference // 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.
SET Control Statement SET Control Statement Description Use the SET control statement to define the partition ID and CPUID values used to replace equal signs (=) in the dataset name. SET must precede all job controls submitted. The SET control statement must begin on column 1. Syntax The folllowing is an example of a SET control statement syntax: SET PART=xx CPUID=y Parameters Definitions The following provides a description of the parameters you can use when using the SET control statement.
SET Control Statement // EXEC TSIDFAV VSE JCL -/* /& // JOB TSIDFAV * DISK INPUT // DLBL DISKIN,'FAV.INPUT.JCL' // ASSGN SYS004,DISK,... // UPSI XXXX0 // EXEC TSIDFAV /* POWER Mode REQUIRED When using POWER mode, the job control must be submitted backwards, in reverse order of execution, and upside down so that card column 1 is submitted to TSIDFAV in card column 80. This prevents POWER from processing any POWER JECL submitted as instream data.
SET Control Statement 10-16 Connectivity Systems, Inc.
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.
Recorder History Recorder History Description BIM-EPIC Recorder Backup files 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 any specified time period. To create a Recorder History dataset: Step 1 Action Create a new Recorder History dataset using a tape-to-tape copying utility, such as TSIDDTD.
Activity Log Report (TSIDARP) 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.
Activity Log Report (TSIDARP) EXCLUDE Control Statement The EXCLUDE control statement specifies a job excluded from the report. If used, EXCLUDE must come before the TSIDARP statement. You can use up to 20 EXCLUDE statements, each statement specifying a job name. Syntax The following is an example of an EXCLUDE control statement syntax. EXCLUDE=jobname TSIDARP Control Statement The TSIDARP control statement specifies dates, CPUs, and partitions to include in the report.
DSN/Job Cross-Reference Report (TSIDBRP) DSN/Job Cross-Reference Report (TSIDBRP) Descr‘iption TSIDBRP generates two reports: DSN/JOB Cross-Reference Report Accepted Tapes Report The DSN/JOB Cross-Reference report lists tape activity and is a cross-reference to the TSIDARP Activity Log report. The Accepted Tapes report lists the controlled tapes that were accepted as input with the ACCEPT response to BIM-EPIC message EP009.
DSN/Job Cross-Reference Report (TSIDBRP) UPSI Values Dataset Requirements The following UPSI values can be used when creating DSN/JOB Cross-Reference reports. Value Function 000 Creates both reports. UPSI 000 uses the TSIDARP Recorder Cross-Reference dataset as input. 010 Creates only the DSN/JOB Cross-Reference report. UPSI 010 uses the Recorder Cross-reference dataset as input. 100 Creates only the Accepted Tapes report. UPSI 100 uses the Recorder Cross-Reference dataset as input.
DSN/Job Cross-Reference Report (TSIDBRP) /* /& User Reference Connectivity Systems, Inc.
Job Time Activity Report (TSIDJAC) Job Time Activity Report (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 the Job Time Activity report to find out when a particular job was run. For example, you can provide information detailing the resources used, such as did the inventory program use 100% of the CPU.
Maintaining the Job Accounting Database Maintaining the Job Accounting Database Description TSIDJLD creates and maintains a job accounting database. You can access this database through CICS with the online access to the Job Accounting database (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 copybook, TSIDOJA.C, is provided. TSIDJLD uses a VSAM KSDS to store data.
Maintaining the Job Accounting Database You can submit both ADD control statements and DEL control statements in the same execution. All deletes are performed before new information is added. The control statement is 32 bytes long and consists of five fields: Syntax Bytes Field Contents 1–3 ADD or DEL 4–11 Job name 12–21 Jobs started on or after this date 22 Blank 23–32 Jobs started on or before this date The following is an example of a control statement syntax.
Maintaining the Job Accounting Database Examples Parameter Definition jobname Specifies a particular job to be added to or deleted from the database. You can specify a generic job name by ending the name with an asterisk. For example, specify TST* to process all jobs beginning with TST. All occurrences of that job or those jobs are added or deleted.
CICS Access to Job Accounting Database CICS Access to Job Accounting Database Description The CICS transaction TOJA provides online access to the BIM-EPIC job accounting database. TOJA consists of the following four panels: Job Selection Job Overview Program Overview Program Audit 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.
CICS Access to Job Accounting Database At the next level, the Program Overview panel displays an overview of the steps executed in a single job. BIM-EPIC/VSE ONLINE JOB ACCOUNTING FACILITY .
CICS Access to Job Accounting Database Accessing Job Accounting Database To access the Job Accounting Database: Step Action 1 From a CICS terminal, enter the TOJA transaction. The Job Selection panel displays. 2 To view all jobs, press Enter. To view several jobs beginning with the same character string, enter the string and press Enter. To view a single job, enter the job name and press Enter.
12 Managing Tape Volumes To protect controlled datasets effectively, BIM-EPIC controls the tape volumes where the controlled datasets reside. BIM-EPIC also protects the tape volume serial numbers. Every tape that contains a BIM-EPIC-controlled dataset is recorded in the DSN Catalog. Tapes are identified by volume serial number and controlled at the version level under the dataset name they contain.
Managing Tape Volumes Tape Utilities and Commands Tape Control and Protection Utilities 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 identification is essential for tape volume control. Volume serial numbers can be any six-character combination of alphanumeric characters.
Managing Tape Volumes Scratch Tapes Scratch tapes are produced by the SCRATCH function of TSIDUTL, TSIDMNT, and Online Manager. TSIDUTL DSPLY SCRATCH produces a report listing of all available scratch tapes. TSIDUTL PSCRATCH creates a report projecting which tapes will be eligible for scratch on a certain date. See the BIM-EPIC Installation and System Guide for additional information describing the TSIDUTL JCL requirements.
Managing Tape Volumes Small tapes are distinguished by their volume serial numbers which must end with the character S. Large tapes have no restrictions to their volume serial numbers. You can designate that a dataset should be written to small tapes with online or manual catalog maintenance using the Tape Size field. Revolving Tape Datasets In some cases, you may want to use a specific set of tapes for a dataset to ensure all versions of that dataset are contained on that specific set of tapes only.
Managing Tape Volumes It is the responsibility of the operator to ensure that tape drives are available when BIM-EPIC searches for a tape.
Attention Routine Commands Attention Routine Commands Description Certain BIM-EPIC services can be invoked by commands that the operator issues through the VSE Attention Routine (AR). Command Summary The BIM-EPIC AR commands are: Command Description EP ? (or EP HELP) Displays help information for BIM-EPIC AR commands. EP END STname Terminates a BIM-EPIC Dispatcher subtask. name is the name of the subtask being ended.
Attention Routine Commands CPUs are active with SHARE=YES. Because an AR cannot wait for a successful lock, BIM-EPIC issues this warning message when it cannot obtain a lock immediately. If you receive this warning message, try the command again. User Reference Connectivity Systems, Inc.
FREE and STATUS Commands FREE and STATUS Commands Description In addition to providing status information using Attention Routine (AR), BIM-EPIC also allows the operator to respond with 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. 12-8 Connectivity Systems, Inc.
FREE and STATUS Commands Tape Controls Mounting Tapes Description BIM-EPIC controls which tapes can be used for output. BIM-EPIC 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 the tape is in scratch status before being used as output. If the tape is uncontrolled, BIM-EPIC checks to determine if the volume serial number exists in the DSN Catalog.
FREE and STATUS Commands Requesting a Specific Version To request a specific version, type RERUN,n in response to a request for a tape mount, where n is the number of the version requested. Example To issue a new tape mount request for version number 3, type RERUN,3. Using ACCEPT The operator has the option to reply with ACCEPT to a mount request to force BIM-EPIC to use any desired volume. Each time ACCEPT is used, a notation is made in the TSIDBRP Accepted Tapes report.
Initializing Tapes for BIM-EPIC Control Initializing Tapes for BIM-EPIC Control Description TSIDINIT initializes tapes with BIM-EPIC VOL1 labels and enters the labels in the DSN Catalog under the dataset name ***.VOLUME.DSN.***. The tapes can then be used as controlled scratch tapes. Up to 10 tape drives can be used in the initialization process. TSIDINIT can be executed from JCL or from the operator console.
Initializing Tapes for BIM-EPIC Control In sequential initialization, TSIDINIT continues to initialize tapes until the operator replies STOP to the mount message. Sequential initialization requires 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.
Initializing Tapes for BIM-EPIC Control Parameters For non-virtual ACLs, a robot reads the cartridge barcodes. This requires the volume serial numbers specified to TSIDINIT match the appropriate barcodes. PARM='CONSOLE' can be specified on the VSE EXEC statement to allow the operator to control initialization from the console. This has the same effect as entering EXEC TSIDINIT after a VSE // PAUSE’ statement.
Initializing Tapes for BIM-EPIC Control Syntax The following is an example of a cuu statement syntax. CUU=cuu,cuu,cuu,... The cuu statement requires UPSI xx1x in the JCL. VOLSER Statements VOLSER statements identify which volume serial numbers are written in the VOL1 label. If random initialization is requested, one VOLSER statement is required for each volume serial number. If sequential initialization is requested, use only one statement to specify the starting volume serial number.
Initializing Tapes for BIM-EPIC Control // JOB INITTAPE // UPSI 10101 // EXEC TSIDINIT,PARM=’ACL=B1VTS,COUNT=10’ CUU=480,481 SR0010 /* /& The following example shows how TSIDINIT uses an ACL to do random initialization of tapes not in the BIM-EPIC Catalog that have labels or tape marks. TSIDINIT 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.
Initializing Tapes for BIM-EPIC Control Tape Print Requirements 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 comment, which is optional. Standard spacing for each label is one line for the comment, seven lines for the volume serial number, and two blank lines between labels. Example The following is an example of a volume serial number label.
Initializing Tapes for BIM-EPIC Control Definitions The following provides definitions for the parameters you can use when printing external volume labels. Parameter Definition volser [ -volser ] Specifies the range of volume serial numbers for the labels you want to create. If you want to create only one label, omit the hyphen and second volser. The last four characters in the volume serial number must be numeric. comment Example Specifies the comment to be printed on each label.
Initializing Tapes for BIM-EPIC Control If TSIDPRT is not activated using the PLTPI, enter the TPRT transition from a CICS terminal. When you activate TSIDPRT using this method, the terminal you use is not released until the TPRT is deactivated or until CICS is terminated. To deactivate TPRT, execute TSIDPEN in any available partition. This releases the label printer and any terminal used by TPRT. 12-18 Connectivity Systems, Inc.
Initializing Tapes for BIM-EPIC Control Tape Vaulting Processes Tape Vaulting Description The BIM-EPIC vaulting subsystem controls tape vaulting automatically. This section presents an overview of the programs and procedures involved with 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 each vault contains. Vaults are identified by integers.
Initializing Tapes for BIM-EPIC Control from Vault 0 in the BIM-EPIC ACL Inventory Management library member. At a later time, these volumes can be ejected from the ACL using EP ACL EJECT command or TSIDUTL ACLEJECT function. See the BIM-EPIC Installation and System Guide for additional information. Additional Reports 12-20 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.
Assigning Vaulting Methods to Datasets Assigning Vaulting Methods to Datasets Description User Reference After vaults and vaulting methods have been defined, the methods must be assigned to datasets before automatic vaulting can occur. Vaulting methods are assigned to datasets using Online Manager or TSIDMNT CATALOG or TSIDMNT UPDATE functions. If you are using Online Manager, place the vault method number in the Vault Method field of the BIM-EPIC dataset definition (EDD).
Moving Volumes (TSIDVLT) Moving Volumes (TSIDVLT) Description JCL Requirements TSIDVLT creates movement reports when moving tapes from one vault to another. TSIDVLT should be executed daily. TSIDVLT can be instructed to: perform actual vaulting actions. A report is produced describing the vault movements that occurred. perform projected vaulting actions. A report is produced describing what movements would take place, but no actual vault/slot movement occurs.
Moving Volumes (TSIDVLT) Example The following is an example of a TSIDVLT control statements. // JOB VAULTMOV // DLBL SORTWK1,'===.SORTWK1,(D)' // EXTENT SYS001 // EXEC TSIDVLT MOVESLT /* /& User Reference Connectivity Systems, Inc.
Reporting Current Locations of Vaulted Tapes Reporting Current Locations of Vaulted Tapes Description 12-24 The TSIDUTL DSPLY function 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 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 BIM-EPIC does not recognize manually controlled vaults, the vaults must be manually maintained by the user. Any version of any dataset can be moved to a manually controlled vault. Tapes are moved to or from manually controlled vaults using the Online Manager or TSIDMNT MOVE function.
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, the dataset must have a vaulting method assigned to it in the DSN Catalog. JCL Requirements The following is an example of the JCL requirements for creating a Vault to Dataset Cross-Reference report. // DLBL SORTWK1...
Vault To Dataset Cross-Reference Report (TSIDPRV) Tape Reports Dataset to Tape Report (TSIDDIS) Description TSIDDIS produces a summary report correlating dataset versions and tape volume serial numbers. The summary is listed in dataset name order and contains one entry for each dataset version. If a version spans more than one volume, there is an entry for each volume. See Appendix A, “TSIDDIS Report,” for an example of the TSIDDIS report.
Tape to Dataset Report (TSIDSDS) Tape to Dataset Report (TSIDSDS) Description TSIDSDS produces a summary report correlating dataset versions and tape volume serial numbers. The summary is in volume serial number sequence and contains 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 Appendix A, “TSIDSDS Report,” for an example of the TSIDSDS report.
13 Disk Space Management This chapter discusses how BIM-EPIC can help you to maximize and manage your disk space. Chapter Contents Datasets VTOC Offload and Onload User Reference Connectivity Systems, Inc.
Dataset Fragmentation Datasets Dataset Fragmentation Description When you create a dataset with a large primary allocation, there may not be enough contiguous free space in the pool to contain the entire primary allocation. BIM-EPIC responds to this condition by allocating the largest amount of contiguous free space to the primary extent and allocating secondary extents, as necessary, when the primary extent becomes full. This process is called dataset fragmentation.
Dataset Fragmentation Truncation occurs only on output for sequential disk datasets and is automatic for datasets defined with DLBL statements. However when using BIM-EPIC DD statements, truncation must be requested using the RLSE subparameter of the SPACE parameter. Truncation should be inhibited for TYPEFLE=WORK DTFs and for datasets that are opened as sequential I/O but are not accessed sequentially, for example, DL/1 datasets Truncation can also be inhibited using the DLBL option code N.
Converting Uncontrolled Disk Datasets Converting Uncontrolled Disk Datasets Description Existing uncontrolled disk datasets can be placed under BIM-EPIC control. Any existing dataset can be controlled as long as all the associated extents reside in a single-disk pool that is defined to BIM-EPIC. You can convert a disk dataset to catalog control or Start Track 1 control.
Converting Uncontrolled Disk Datasets Example The following is an example of converting a Start Track 1 dataset. // EXTENT SYS001,POOL50,1,0,1,10 User Reference Connectivity Systems, Inc.
Placing Datasets on Specific Volumes in a Pool Placing Datasets on Specific Volumes in a Pool Description All disk datasets can be assigned to a BIM-EPIC pool. If your pool is made up of more than one volume, BIM-EPIC can allocate a version of the dataset on any of those volumes. Procedure To allocate a disk dataset to a specific volume: Step 13-6 Action 1 QUIESCE all other volumes in the pool. 2 Create the dataset and inhibit truncation. 3 Reuse the same space when re-creating the dataset.
VTOC Utilities VTOC VTOC Utilities Description BIM-EPIC provides the following VTOC utilities: ! TSIDLVT displays VTOCs by BIM-EPIC pool sequence, volume sequence, extent sequence, or dataset sequence. In addition, VTOCs can display both active and expired datasets or active datasets only. TVTO is a CICS transaction that displays VTOCs by volume only. TSIDVUT allows modification of existing VTOC entries.
VTOC Listings (TSIDLVT) VTOC Listings (TSIDLVT) Description TSIDLVT produces printed reports of VTOC entries. TSIDLVT can display entries for all volumes in a BIM-EPIC 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 Listings (TSIDLVT) Control Statement Parameters The following provides an example of the control statement parameters. Parameters The following provides a description of the parameters you can use with TSIDLVT.
VTOC Listings (TSIDLVT) Parameter Definition EURO Prints dates in European format (dd/mm/yyyy). By default dates are printed in USA format (mm/dd/yyyy). CCHH Prints extents in cylinder/head (cchh) format. If cchh is not specified, extents will be shown in relative track/block format. SUM Skips detailed VTOC information and prints only summary information for the VOLSER or POOL. Note: You must specify either SER=volser or poolname.
Online VTOC Displays Online VTOC Displays Description The TVTO CICS transaction displays information about entries found in the VTOC on a specific DASD volume.
Online VTOC Displays attempted, or by pressing F1/PF1 from the VTOC screen. Error and informational messages are displayed on the top screen line just to the right of the CUU field. Pressing F3/PF3 from the Help screen terminates the TVTO transaction and returns control to CICS with a blank screen. The right-most fields on screen line 1 and screen line 2 display all the current settings which control the manner and sequence for entries that will display on the VTOC screen.
Online VTOC Displays Parameter Definition Cyl|Trk Controls the display of disk addresses for CKD devices only. Enter only the first letter of each choice: High|Size Expire Cyl (default with EPS065=NO) displays disk addresses in cylinder-head format Trk (default with EPS065=YES) displays disk addresses in track format Controls the display to show either the high disk address or the size occupied. The display also shows the starting, or low, disk address.
Online VTOC Displays Screen line 1 includes the cuu, VOLSER, and DASD models for the unit being displayed as well as the current date, time, current screen page number, and last screen page number. Screen line 2 provides titles for the columns that occupy all the remaining screen lines, except the last line, beginning on screen line 3. File Name is the full 44-character name of the file occupying this extent.
Online VTOC Displays Valid PF keys User Reference The following provides a description of each valid function key: Function Key Function Action F1/PF1 HELP Display Help screen F2/PF2 RFSH Read all VTOC entries again F3/PF3 END Return to CICS F4/PF4 FST Go to the first screen F5/PF5 LST Go to the last screen F7/PF7 BWD Back one screen F8/PF8 FWD Forward one screen Connectivity Systems, Inc.
Offload System Offload and Onload Offload System Description BIM-EPIC provides offload/onload, backup/restore, offload version consolidation, and offload version copy functions for controlled sequential disk dataset versions. These functions are only available on BIM-EPIC systems supporting both disk and tape management. Control statements identify the datasets processed by the offload, backup, version consolidation, and version copy functions.
Offload System could be consolidated into a new version of perhaps 1 or 2 tapes, freeing the five remaining tapes for other uses. The Offload Version Copy function copies an offload version into BIM-EPIC backup format. The Offload Version Copy function will copy an existing backup version or an existing offload version. Programs High Performance I/O The offload system consists of the following four programs: TSIDOFD selects datasets for offload and backup by creating control statements for TSIDOFL.
Selecting Datasets To Be Offloaded (TSIDOFD) Selecting Datasets To Be Offloaded (TSIDOFD) Description TSIDOFD creates control statements for input to TSIDOFL based on specific selection criteria specified in INCLUDE and OMIT control statements. These control statements determine which datasets will be offloaded or backed up.
Selecting Datasets To Be Offloaded (TSIDOFD) Start Track 1 disk datasets are selected for backup using the following criteria: Pool name Dataset name Dataset names beginning with a specific character string Datasets can be omitted from the inclusion list by: JCL Requirements Dataset name Dataset names beginning with a specific character string The following is an example of the JCL requirements for using TSIDOFD: [// xLBL OUTPUT,'sysin.data.
Selecting Datasets To Be Offloaded (TSIDOFD) Control Statements Dataset selection criteria are specified using INCLUDE and OMIT control statements. You can specify multiple parameters on any INCLUDE or OMIT control statement, but parameter expressions cannot be continued.
Selecting Datasets To Be Offloaded (TSIDOFD) Definitions User Reference Parameter Required With Required With Valid CATALOG=YES? CATALOG=NO? Default DLA No Not Allowed 1 to 365 None DSN No No 1 to 44 characters None NEW No Not Allowed None OFF POL No Yes 1 to 6 characters None SID No Not Allowed 2 characters None SLA No Not Allowed 1 to 365 None UID No Not Allowed 2 characters None VER No Not Allowed 1 to 9999 None VOL No Not Allowed 1 to 6 characters None
Selecting Datasets To Be Offloaded (TSIDOFD) Parameter Definition POL Selects datasets that are allocated to a specified pool. For INCLUDE, you can specify a maximum of 10 pool IDs. For CATALOG=YES only and if you are using OMIT, you can specify an additional 10 pool IDs to be OMITTED. You can specify multiple pool IDs on a single POL parameter, for example, POL=pool01,pool02,pool03. If CATALOG=YES, the POL parameter is checked against the current pool name in the dataset definition.
Selecting Datasets To Be Offloaded (TSIDOFD) Parameter Definition VER Selects a version number for a particular dataset. VER can be supplied only if the DSN parameter is also supplied. If the DSN parameter is omitted, all versions of the dataset are selected. Note: Subparameters can be specified only once for INCLUDE and once for OMIT. User Reference ALLVER Selects datasets by version number. ALLVER affects all selected datasets; VER affects only a specific dataset.
Offloading and Backing Up Datasets (TSIDOFL) Offloading and Backing Up Datasets (TSIDOFL) Description TSIDOFL offloads or backs up selected datasets according to the settings on the UPSI statement and the contents of control statements. Control statements specify which datasets and versions are to be processed and are supplied as SYSIPT data. These control statements can be generated by TSIDOFD or specified manually.
Offloading and Backing Up Datasets (TSIDOFL) {// TLBL OUTPUT,'offload.dataset.name'} // TLBL IJSYSIN,'sysin.dataset' // EXEC TSIDASS OPEN IJSYSIN,SYS020,INPUT /* // ASSGN SYSIPT,SYS020 // UPSI xx // EXEC TSIDOFL /* // RESET SYSIPT UPSI Values The following UPSI values can be used when offloading and backing up datasets. Position Setting Function 0 0 Specifies OFFLOAD function 1 Specifies BACKUP function.
Offloading and Backing Up Datasets (TSIDOFL) from being stored as the last accessed job and date for each version read by TSIDOFL. If you specify PARM=’DLAUPD=YES’ or do not specify the PARM operand, the offload/backup job name and current date will be stored as the last accessed job and date for each version read by TSIDOFL. Control Statements Use control statements to indicate which datasets to offload or backup. You can use TSIDOFD to generate these control statements.
Offloading and Backing Up Datasets (TSIDOFL) Parameter Definition version/ generation number Positional and only one number can be specified. If UPSI xx1 is not set, EPIC regards the number as a version number. If UPSI xx1 is set, EPIC regards the number as a generation-number. They are only valid for datasets defined in the catalog. poolnm Specifies the name of the pool where the dataset resides. It is only valid for Start Track 1 datasets.
Offloading and Backing Up Datasets (TSIDOFL) of output dataset name OFFLOAD.DATA.SET. If the dataset name does not exist, BIM-EPIC will create it as part of the OFFLOAD processing. // JOB OFFLOAD * //IJSYSIN DD DSN=SYSIN.DATASET,DISP=(OLD,DELETE) // UPSI 0 // EXEC TSIDOFL /* /& The following example backs up datasets based on the control statements supplied using the IJSYSIN input dataset SYSIN.DATASET. This input dataset is deleted when the dataset is closed.
Offloading and Backing Up Datasets (TSIDOFL) ‘CRAYZY.RABBUTTE’,POL=WBPOOL /* /& User Reference Connectivity Systems, Inc.
Onloading and Restoring Datasets (TSIDONL) Onloading and Restoring Datasets (TSIDONL) Description TSIDONL onloads or restores datasets back to disk. TSIDONL can also produce a report listing the datasets contained on an offload tape. Use UPSI settings to specify TSIDONL functions. You can onload a dataset only from an offload tape. TSIDONL assigns the newly created disk version a version number based on the absolute generation number the version had when it was offloaded.
Onloading and Restoring Datasets (TSIDONL) Setting Function 0xx0x1 Use the original generation number from the offloaded file(s) and change the creation date in the VTOC entry to the original creation date of the offloaded file(s). The version will not be onloaded if it is in SCRATCH status in the BIM-EPIC Catalog. Note: UPSI xxx1 applies to tapes containing offload or backup data for sequential disk versions identified in the BIM-EPIC Catalog.
Onloading and Restoring Datasets (TSIDONL) Onload versus Restore The following scenario describes the differences between TSIDONL Onload and TSIDONL Restore. Suppose you have a dataset named DATASET.A with the following information in the BIM-EPIC Catalog.
Onloading and Restoring Datasets (TSIDONL) If versions 3 through version 6 are not scratched and two new versions are created, DATASET.A contains the following: Onload Results Version Absolute Generation Number (AGN) Location 1 48 Disk 2 47 Disk 3 46 Disk 4 45 Disk 5 44 Tape 6 43 Tape 7 42 Tape 8 41 Tape If the previously offloaded versions (version 3 through version 6) are onloaded, DATASET.
Onloading and Restoring Datasets (TSIDONL) 6 47 Disk 7 46 Disk 8 45 Disk BIM-EPIC restores each version as version 1 in descending sequence based on the original version order. Since the most recent onloaded versions are once again on disk, they are assigned new AGNs. These TSIDONL Onload and TSIDONL Restore examples show why using onload instead of restore is the most used method for returning offloaded data to disk.
TSIDONL Control Statements TSIDONL Control Statements Description TSIDONL control statements are read if UPSI 010 or UPSI 110 is specified. There are two types of TSIDONL control statements: dataset-name specifies a dataset version to be onloaded or restored. START begins an onload or restore at a particular dataset and version on the tape. You can continue the control statement by placing a comma after the last parameter and then beginning the next parameter with the next control statement.
TSIDONL Control Statements Parameter Definition generation-number Specifies the absolute generation number (AGN) of the tape dataset to be onloaded or restored. To specify all generations of a dataset, use an asterisk (*). The generation number can be omitted for a work dataset. The AGN can be obtained from an Online Manager or TSIDMNT display of the dataset, or from the listing produced by TSIDOFL when the offload or backup was done.
TSIDONL Control Statements Syntax The following is an example of a START control statement syntax. START='dataset-name',generation-number Definitions The following provides the definitions for the parameters you can use for a Start Track 1 dataset. Parameter Definition dataset-name Specifies the name of the dataset to use to begin onload or restore processing. generation-number Specifies the absolute generation number of the disk dataset.
TSIDONL Control Statements The following example restores all datasets found on version 1 of the OFFLOAD.DATA.SET tape. // JOB RESTORE // UPSI 100 // EXEC TSIDONL /* /& The following restore example restores three Start Track 1 datasets named on the control statements. The second control statement contains the POL= parameter which causes that Start Track 1 dataset to be restored to the specified pool, WDPOOL, rather than the pool where the dataset was originally located.
Consolidating Offload Versions (TSIDOFC) 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. TSIDOFC can also copy an OFL-created offload or backup tape volume to another tape volume. JCL Requirements Control statements are supplied as SYSIPT data.
Consolidating Offload Versions (TSIDOFC) Syntax Control statements can begin in any column. Continuations cannot be used. REPT CONI CONO COPY Definitions [PCT=n] n n [n]...[n] NV=n n If used, REPT must be the only control statement submitted. The following provides the definition for the parameter you can use with the REPT control statement. Parameter Definition PCT=n Optional and is most accurate for offload datasets that reside on cartridge media.
Consolidating Offload Versions (TSIDOFC) The following provides the definition for the parameter you can use with the CONI control statement. Parameter Definition n n [n]...[n] Specifies a version numbers that are input to the consolidation process. There must be at least two values present with each value separated by a space. There can be as many versions specified as will fit on columns 1 through 72 of the control statement. Only one CONI statement can be present.
Consolidating Offload Versions (TSIDOFC) The following provides the definition for the parameter you can use with the CONO control statement. Parameter Definition NV=n Specifies the version number assigned to the consolidated output version if you want a version other than 1. The default value is 1. The version number is not assigned until the consolidation process has completed and the input versions have been scratched.
Consolidating Offload Versions (TSIDOFC) The following provides the definition for the parameter you can use with the COPY control statement. Parameter Definition n Specifies the version number of the dataset that is input to the copy process. The version number of the output dataset will be version 1. Only one version can be copied at a time. The input dataset name and output dataset names must be different.
Consolidating Offload Versions (TSIDOFC) // TLBL OFCINP,'PAYR.MONTHLY.OFLD’ // TLBL OFCOUT,'PAYR.MONTHLY.OFLD’ // EXEC TSIDOFC CONI 4 8 11 CONO NV=6 /* /& The following example 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 /* /& 13-44 Connectivity Systems, Inc.
A BIM-EPIC Report Fields and Examples BIM-EPIC produces several standard reports. This appendix lists the standard reports by report name, report examples, and general reports.
Customized Reports Customized Reports Description In addition to the standard reports, you can use your own report writers to produce customized reports using BIM-EPIC data. The DSN Catalog contains all tape and dataset information, including BIM-EPIC dataset definitions (EDDs) and version data. BIM-EPIC provides the TSIDAC2 subroutine for access to the DSN Catalog and the TSIDAC2.C or TSIDAC2.A copy books to map the catalog records.
TOJA Report Examples TOJA Report Examples Description TOJA displays job accounting information online. See Chapter 11, “CICS Access to Job Accounting Database,” for information on the TOJA report. The TOJA report has three displays: Job Overview Display Job Overview Program Overview Program Audit The Job Overview display presents an overview of job activity based on a job name. For each job, there is one entry for each program executed in that job.
TOJA Report Examples Program Overview Display Field Definition AR Specifies the number of audit records for the phase. There is one audit record for each open and one audit record for each close processed. CPU ID Specifies the CPU where the job ran. The Program Overview panel displays statistics at the program level. BIM-EPIC/VSE ONLINE JOB ACCOUNTING FACILITY .
TOJA Report Examples Program Audit Display Field Definition ALLBOUND Specifies the allbound times for the program as defined by IBM. PHASE CODE Specifies STEP for a phase record; LAST for an EOJ record. PHASE SEQ Specifies the step number of the phase. INPUT OUTPUT TABLES Specifies the I/O counts for each device. USER INFORMATION Specifies user information from the JOB statement.
TOJA Report Examples A-6 Field Definition SERIAL ACCEPTED Specifies the volume serial number if the ACCEPT command was issued. REEL TRACK Specifies the starting address of a disk dataset or the reel sequence number of a tape dataset. END TRACK Specifies the ending address of a disk dataset. DTF TYPE Specifies the DTF type of the dataset. Connectivity Systems, Inc.
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. Definitions The following describes the fields located on the Activity Log. Field Definition JOB NAME Specifies the name of the job which initiated the open and close activity.
TSIDARP Report A-8 Field Definition D/S CREATION: JOB Specifies the dataset creation job. D/S CREATION: DATE Specifies the dataset creation date. DISK SPACE ALLOCAT: START Specifies the beginning address of a disk extent. DISK SPACE ALLOCAT: REQST Specifies the amount of allocation requested for the extent. DISK SPACE ALLOCAT: TRUNC Specifies the extent size after truncation. Connectivity Systems, Inc.
TSIDARP Report Example The following is an example of a TSIDARP Activity Log report. C.P.U. NO. 111111 DATE 12/02/1997 JOB PHASE C.P.U. OVER GEN/ NAME NAME PART TIME HEAD J O B A C C O U N T I N G S Y S T E M TSIDARP= 6.01.00 A C T I V I T Y L O G RUN DATE 12/04/1997 TIME 13.19.49 PAGE 1 DTF TOTAL START/ END/ USAGE -D/S CREATION----DISK SPACE ALLOCATNO. TYPE UNIT I/O OPEN CLOSE MIN/SEC JOB DATE START REQST TRUNC SERIAL REEL DUMMY BG 00.1 00.1 09.30.15 09.30.17 .02 PROG TERMINATED INTERR.HEX CODE 00 ..
TSIDBRP Report TSIDBRP Report Description TSIDBRP creates the DSN/JOB Cross Reference report, which is 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. Each dataset is reported with a separate line for each open and each close.
TSIDBRP Report Example The following is an example of a TSIDBRP DSN/JOB Cross Reference report. J O B A C C O U N T I N G DSN / JOB CROSS REFERENCE JOB NAME FILE NAME S Y S T E M RUN DATE 04/16/1998 PHASE NAME VERIFY6.FILE01 CPUID TSIDBRP= 6.1 TIME 13.16.35 PAGE RUN DATE TIME 1 SERIAL -DEVICEPART NO. TYPE NO. REEL NO. START TRACK NO OF TRACKS TRACKS TRUNCT. VERIFY6 JCOPY G=0000002 222222 04/15/1998 06.19.25 BG CKD001 DISK 222222 06.19.
TSIDBRP Report Definitions The following describes the fields located on the Accepted Tapes report. Field Definition REQUESTED FILE NAME Specifies the name of the dataset requested by the job. REQUESTED SERIAL NO. Specifies the volume serial number requested by the job. A serial number of 000000 indicates that the real volume number is not known. Example J O B ACCEPTED FILE NAME Specifies the name of the dataset accepted. ACCEPTED SERIAL NO. Specifies the volume serial number accepted.
TSIDDIS Report TSIDDIS Report Description TISDDIS produces a summary report correlating dataset versions and tape volume serial numbers. The information in the TISDDIS summary report is listed by dataset name order with one entry for each dataset version. However, if a version spans more than one volume, there is an entry for each volume. See Chapter 12, “Dataset to Tape Report (TSIDDIS),” for additional information on the TSIDDIS report.
TSIDDIS Report Example The following is an example of the TSIDDIS Dataset Management report. 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.
TSIDJAC Report TSIDJAC Report Description TSIDJAC creates the Job Time Activity report, which lists job accounting information by CPU and by job. Definitions The following describes the fields located on the Job Time Activity report. Field Definition CPU NO. Specifies the CPU being reported. JOB NAME Specifies the name of the job which initiated the activity. RUN DATE Specifies the date the job ran. PHASE NAME Specifies the name of the program being reported.
TSIDJAC Report Example The following is an example of the TSIDJAC Job Time Activity report: J O B A C C O U N T I N G S Y S T E M C.P.U. NO. 111111 RUN DATE 12/04/1997 JOB RUN PHASE PART NAME DATE NAME ID BGINIT 12/02/1997 DUMMY TSIDJAC= 6.01.00 J O B T I M E A C T I V I T Y * START END DURATION TIME TIME TIME TIME 13.20.07 CPU OVER TIME HEAD PAGE TOTAL I/O 1 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.
TSIDLVT Report TSIDLVT Report Description TSIDLVT lists VTOC data in batch. The report format varies depending on the options you choose when submitting the JCL. See Chapter 12, “Moving Volumes (TSIDVLT),” for additional information on printing reports. Definitions User Reference The following describes the fields located on the TSIDLVT report. Field Definition DISPLAY OF Identifies the content of the report, either SER=volser or the name of the pool.
TSIDLVT Report Example The following is an example of the TSIDLVT report.
TSIDMNT Report TSIDMNT Report 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. See Chapter 3, “TSIDMNT—DSN CATALOG MANAGEMENT UTILITY,” for additional information on TSIDMNT report. Definitions The following describes the fields located on the TSIDMNT report.
TSIDMNT Report The following describes the BIM-EPIC dataset definition (EDD). A-20 Field Definition RET Specifies the number of days each version is to be retained. CYC Specifies the number of versions (cycles) to be maintained. VLT Specifies the number of the vault method assigned to the dataset. WORK Specifies a work dataset. PASSWORD Specifies the Unlock/Release password displayed at the far right. REBLK Specifies the default block size. POOL Specifies the disk pool name.
TSIDMNT Report Version Information User Reference The following describes the BIM-EPIC version information. Field Definition SER-NO Specifies the tape or disk volume serial number associated with this version. VN Specifies the version number. RL Specifies the reel or extent sequence number. CREDT Specifies the creation date in Julian format. EXPDT Specifies the projected expiration date. CREAT/JB Specifies the name of the creating job.
TSIDOFD Report TSIDOFD Report Description TSIDOFD produces a report listing the datasets to be offloaded or backed up. See Chapter 13, “Selecting Datasets To Be Offloaded (TSIDOFD),” for additional information on TSIDOFD reports. Definitions The following describes the fields located on the TSIDOFD report. Field Definition DATASET NAME Specifies the name of the dataset to offload or backup. A-22 VER Specifies the version number of the dataset to offload or backup.
TSIDOFD Report Example The following is an example of the TSIDOFD Data Selection report. TSIDOFD= 6.1 TIME: 15.32.06 INCLUDE PARAMETERS D A T A S E T S E L E C T I O N R E P 64,466=SELECTED ENTRY TABLE SIZE USED FOR THIS DATASET NAME / VER ALLVER 0001 DATASET NAME / VER ALLVER OMIT PARAMETERS DATASET NAME ABSENTEE.TEMP ACCTS.PAYABLE.TWO BATCH CONVERT OUT BILL.REPRINT.FILE BLS.REC COLLECT JOURNAL CONSTR.JOURNAL.FILE DAILY.BDTRNMT.BKUP DAILY.BILLING DB.MONTHLY.TRANS2 DCDCASTO.SORT DCDRATXT.OUTPUT DFR.
TSIDOFL Report TSIDOFL Report Description TSIDOFL creates a report listing the datasets offloaded or backed up. See Chapter 13, “Offloading and Backing Up Datasets (TSIDOFL),” for additional information on TSIDOFL reports. Definitions The following describes the fields located on the TSIDOFL report. Field Definition DATASET NAME Specifies the name of the dataset offloaded or backed up. VER Specifies the dataset's version number. SERIAL Specifies the volume serial number the dataset came from.
TSIDOFL Report Example The following is an example of the TSIDOFL Dataset Offload report. TSIDOFL= 6.1 TIME: 9.15.09 DATASET NAME VERIFY3.OFLONL01.FBA.RECFM.V VERIFY3.OFLONL01.FBA.RECFM.U VERIFY3.OFLONL01.FBA.RECFM.S VERIFY3.OFLONL01.FBA.RECFM.F VERIFY3.OFLONL01.CKD.RECFM.V VERIFY3.OFLONL01.CKD.RECFM.U VERIFY3.OFLONL01.CKD.RECFM.S VERIFY3.OFLONL01.CKD.RECFM.F TSIDOFL= 6.1 TIME: 9.15.
TSIDONL Report TSIDONL Report Description TSIDONL creates a report listing the datasets that were onloaded. See “Onloading and Restoring Datasets (TSIDONL),” for additional information on the TSIDONL report. Definitions The following describes the fields located on the TSIDONL report. Field Definition DATASET NAME Specifies the name of the dataset onloaded. OLD VER Specifies the version number of the dataset before it was onloaded.
TSIDPRV Report TSIDPRV Report Description TSIDPRV produces the Vaulting Method report. Definitions The following describes the fields located on the TSIDPRV report. Field Definition DATASET NAME Specifies the name of the dataset. User Reference NO. CYC Specifies the number of cycles to be maintained for the dataset. DAYS RET Specifies the number of days each version is to be retained. METH NO. Specifies the vaulting method assigned to the dataset. VER NO.
TSIDPRV Report Example TIME 14 09 28 The following is an example of the TSIDPRV report. * * V A U L T I N G M E T H O D DATE 12/04/1997 AR.PROD.NCL.ELME3BKP.GVEXPORT.OFFSITE 30 1 1 1 2 3 MAIN LIBRARY VAULT 1 VAULT 2 AR.PROD.NCL.EREXTR.EL860.OFFSITE 30 1 1 1 2 3 MAIN LIBRARY VAULT 1 VAULT 2 AR.PROD.NCL.ERPNDB.EL860.OFFSITE 30 1 1 1 2 3 MAIN LIBRARY VAULT 1 VAULT 2 AR.PROD.NCL.ERPYAJ.EL860.
TSIDSDS Report TSIDSDS Report Description TSIDSDS produces a summary report correlating dataset versions and tape volume serial numbers. The summary report is listed in volume serial number order. See Chapter 12, “Tape to Dataset Report (TSIDSDS),” for additional information on the TSIDSDS report. 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.
TSIDSDS Report Example TSIDSDS= 6.01.00 TIME 14 07 58 SER NO B12017S B12110S B12183S B12437S B12500S B12547S B12862S B12873S HEW001 JA0001 T12994 T13014S 000001 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000004 000006 000007 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 000009 A-30 --DATASET NAME-EPIC.DISK01.BKUP EPIC.DISK01.BKUP EPIC.DISK01.BKUP EPIC.
TSIDTAC Report TSIDTAC Report Description TSIDTAC produces 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. Definitions The following describes the fields located on the TSIDTAC report. Field Definition CPU NO. Specifies the CPU being reported. RUN DATE Specifies the date the job ran. JOB NAME Specifies the name of the job initiating the activity.
TSIDTAC Report Example C.P.U. NO. 111111 RUN JOB DATE NAME The following is an example of the TSIDTAC Date Time Activity report.
TSIDUTL Report TSIDUTL Report Description TSIDUTL enables you can obtain information using various report formats. The following provides an overview of several report formats. DSPLY ALL, Dataset Name Sequence The TSIDUTL DSPLY ALL, SEQ=DSN report format 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.
TSIDUTL Report Version Information The field titles listed at the top of each page refer to data recorded at the version level. The fields titles listed are: Field Definition SERIAL NO Specifies the tape or disk volume serial number. VER. NO Specifies the relative version number of the version. There may also be four status codes listed in this column. S—the version is scratched. O—the version is in open status. C—the version is conditionally cataloged.
TSIDUTL Report User Reference Field Definition VLT Specifies the current vault location of the tape. SLT Specifies the current slot location of the tape. TOTAL ACTIVE Specifies the total number of active tapes on the TSIDUTL report. TOTAL SCRATCH Specifies the total number of scratch tapes on the TSIDUTL report. Connectivity Systems, Inc.
TSIDUTL Report Example The following is an example of the TSIDUTL DSPLY ALL,DSN report format. 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.
Tape Dataset Summary Report Tape Dataset Summary Report Description The following report summarizes information about tape datasets. Each tape volume serial number (volser) is listed along with data for that version. Dataset definitions are not listed. The first field listed is the version dataset name. Other fields contained in this report are described later in this document. Example The following is an example of a Tape Dataset Summary report. SIDUTL= 6.01.00 TIME 13.42.
Tape Dataset Summary Report Expiration Date, Creation Date, and Creation Job Sequences A-38 Each version is listed with all version data. Dataset definitions are not listed. The first field listed is the version dataset name. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the other fields contained in the TSIDUTL report. Connectivity Systems, Inc.
Display Active Report Display Active Report Description User Reference The TSIDUTL Display Active report details the active versions of each dataset. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the fields contained in the TSIDUTL report. Connectivity Systems, Inc.
DSPLY NEW Report DSPLY NEW Report Description The TSIDUTL DSPLY NEW report lists all datasets created since the last time the report was created. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the fields contained in the TSIDUTL report. Example The following is an example of the TSIDUTL DSPLY NEW report. IDUTL= 6.1 IME 6.45.36 D A T A S E T M A N A G E M E N T S Y S T E M DSPLY NEW,SEQ=DSN SERIAL VER.
DSPLY PULL Report DSPLY PULL Report Description The TSIDUTL DSPLY PULL report lists only the most current version for each dataset. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the fields contained in the TSIDUTL report. Example The following is an example of the TSIDUTL DSPLY PULL report. 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 1 DSPLY PULL,SEQ=DSN DATE 12/04/1997 SERIAL VER.
DSPLY VAULT Report DSPLY VAULT Report Description The TSIDUTL DSPLY VAULT report lists the vault and slot locations of all tapes located in offsite vaults. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the fields contained in the TSIDUTL report. Example The following is an example of the TSIDUTL DSPLY VAULT report. 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 R.PROD.NCL.ELME3BKP.GVEXPORT.
DSPLY SCRATCH Report DSPLY SCRATCH Report Description The TSIDUTL DSPLY SCRATCH report lists scratch tapes along with data specific to the version contained on the scratch tape. See “DSPLY ALL, Dataset Name Sequence” for an explanation of the fields contained in the TSIDUTL report. Example The following is an example of the TSIDUTL DSPLY SCRATCH report. 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.
PSCRATCH Report (Projected Scratch) PSCRATCH Report (Projected Scratch) Description The PSCRATCH report lists all tapes that become scratch tapes by the specified date. This report also lists current DSN Catalog usage statistics. The requested projected date is shown next to the PSCRATCH report title and is written in Julian format. For example, PSCRATCH 96001 indicates a projected scratch date of January 1, 1996. At the end of this report, message EP119 is issued to report on DSN Catalog usage.
PSCRATCH Report (Projected Scratch) Example TSIDUTL= 6.01.00 TIME 13.42.37 SERIAL NO FILE NAME HEW001 IDCAMS.BACKUP JA0001 IDCAMS.BACKUP 000001 ELECTRIC.METER.BK 000007 PMTHIST.BKUP 000028 P.SQL.LOG.ARC 000062 UCAT110A.BKUP 000063 UCAT111A.BKUP 000065 UCAT112A.BKUP 000067 WWSTATS.BKUP.TAPE 000070 VSAM.BKUP.TEC 000079 MBOOKFL.BACKUP 000154 P.SQL.LOG.ARC User Reference The following is an example of the TSIDUTL PSCRATCH report.
TSIDVLT Report TSIDVLT Report Description TSIDVLT produces two reports listing tapes which should be moved. One is a Picking List which is sorted by the current location of the tape. The other is a Distribution List which is sorted by the new destination of the tape. 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.
TSIDVLT 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 2 2 VAULT 2 2 VAULT 2
TSIDVLT Report A-48 Connectivity Systems, Inc.
Index - - - suffix (UR), 15, 34 - - suffix (UR), 15, 34 Symbols "** DSN DELETED ** (UR), 26 $$$ datasets (UR), 33 $DEFSEC security profile (UR), 7, 61 to 62 $EPIC security profile (UR), 61 &&dsname (UR), 28 &dsname (UR), 28 &n parameter (UR), 15 ** DSN DELETED ** (UR), 38, 30, 52 **** AUTO CATALOGUE **** (UR), 21 ***.VOLUME.DSN.** (UR), 11 *EPIC.EVENT.
ADD command JCL requirements (UR), 7 parameters (UR), 7 syntax examples (UR), 9 ADD command (UR), 33, 2, 6 Adding EDDs (UR), 22 versions (UR), 37 ADDRESS EPIC, 13 decoding output from (UR), 14 return codes (UR), 13 ADDRESS EPIC (UR), 13 ADS command (UR), 10 After-hours support, xiv AGP configuration option (UR), 28 AGP.
IDCAMS (UR), 45 LIBR (UR), 48 Backup/Offload (UR), 34 Batch catalog management (UR), 8 BIM-EPIC dataset control (UR), 6 DLBL enhancements (UR), 10 JCL enhancements (UR), 41 job cancellation (UR), 39 restricting control (UR), 6 special options (UR), 24 TLBL enhancements (UR), 2 using JCL (UR), 39 BIM-EPIC Configuration options (UR) BIM-EPIC dataset definitions allocation by logical records (UR), 16 automatic purge (UR) block size (UR), 11 CISIZE (UR), 15 creating (UR), 22 cycles retention (UR), 12 dataset na
CAPACITY (UR), 13 CATALOG (UR), 14 CLEAN (ur), 22 CLOSE (UR), 23 CYCLE (UR), 24 DELETE (UR), 43, 26 DEQ (UR), 27 DISPLAY (UR), 28 ENQ (UR), 31 LOCK (UR), 32 MOVE (UR), 35, 25 OFFLINE (UR), 36 ONLINE (UR), 37 PASSWORD (UR), 38 PURGE (UR), 43, 39 QUIESCE (UR), 41 RELEASE (UR), 42 RENAME (UR), 44 RETAIN (UR), 45 SCRATCH (UR), 52, 48 TRANSFER (UR), 50 UNLOCK (UR), 52 UPDATE (UR), 54 vaulting (UR), 21 Catalog management (UR), 2, 2 Catalog overrides DD statements (UR), 13 Cataloging datasets DD statements (UR), 1
Condition checking and branching See Job management control language Conditional Cataloging (UR), 18 Conditional cataloging (UR), 69 Conditionally cataloged CONDCAT parameter (UR), 22 Conditions and IF (UR), 10 Configuration options AGP (UR), 28 AUTOATT (UR), 31 AUTOCAT (UR), 5, 21 AUTOLOG (UR), 21 AUTOSTP (UR), 31 CATRT1 (UR), 5, 22 CNTRL (UR), 6 CYCL (UR), 22 DDGEN (UR), 22, 26 DEFEXT (UR), 22 DEFPOL (UR), 15, 22 DSKRET (UR), 26 GDI (UR), 8, 12, 20 JCLLANG (UR), 1 to 2 JCLOVRDE (UR), 12, 22 JOBACCT (UR),
BIM-EPIC Processing (UR) confirmation options (UR), 12 EDD display format (UR), 8 version display format (UR), 10 CWDS. See Common work datasets CYCL configuration option (UR), 22 CYCLE command versions (UR), 57 CYCLE command (UR), 24 Cycles retention overriding (UR), 24 Cycles retention (UR), 12 CYL parameter (UR), 38 D DA datasets secondary allocation unavailable (UR), 2 DA datasets (UR), 6 DATA parameter (UR), 50, 10 Database utilities (UR), 37 Dataset defaults overriding (UR), 12 Dataset definitions.
FREE parameter (UR), 29 ignoring datasets (UR), 52 JCL requirements (UR), 2 JOBCAT (UR), 7 KEEP parameter (UR), 22 LABEL parameter (UR), 30 LRECL parameter (UR), 17 MOD subparameter (UR), 19 multi-dataset coding (UR), 9 MXIG parameter (UR), 38 NEW subparameter (UR), 19 OLD subparameter (UR), 19 OPTION (UR), 32 OPTION parameter (UR), 48 parameters (UR), 10 PASS parameter (UR), 22 pool request (UR), 45 printer and punch datasets (UR), 48 PRIVATE parameter (UR), 45 REF (UR), 45 RETAIN parameter (UR), 45 RLSE p
ADDRESS EPIC (UR), 14 Detail records (UR), 6 Detail report TSIDMNT (UR), 19 Device address (UR), 19 Device down (UR), 36 Device type, choosing (UR), 61 DFSORT (UR), 39 DHLDOPEN (UR), 24, 39 Direct access datasets DD statements (UR), 17 Direct access datasets (UR), 26 Disk datasets close processing (UR), 45 converting to controlled (UR), 4 grouping (UR), 11 names (UR), 10 open processing (UR), 44 placing on specific volumes (UR), 6 scratching (UR), 38 to 39 Disk pool name (UR), 15 Disk pools CPU independent
DSN catalog enqueuing (UR), 31 DSN Catalog (UR), 3 DSN Catalog efficiency (UR), 4 DSN Catalog entries (UR), 3, 46 DSN DD parameter (UR), 26 DSN parameter (UR), 11 DSN/JOB Cross-Reference Report (UR), 5, 10 DSORG DD parameter (UR), 17 DSPLY command VAULT (UR), 24 VLT (UR), 24 DSPLY command (UR) DTF names excluding from IBM-EPIC control (UR), 6 in TLBLs (UR), 2 TSIDDMP (UR), 20 TSIDDTD (UR), 12 unit record (UR), 3 DTFCD (UR), 3, 61 DTFCP (UR), 61 DTFDI (UR), 61 DTFPR (UR), 3, 61 DTFs TYPEFLE=WORK (UR), 34 DUM
controlled dataset (UR), 26 Start Track 1 dataset (UR), 26 Start Track 1 datasets (UR), 4 Extent statements overriding (UR), 9 F FAVER (UR), 45 FBA CISIZE (UR), 32 Field help (UR), 14 Forced initialization (UR), 12 FORTRAN (UR), 38 FRAG configuration option (UR), 2 Fragmentation DD statements (UR), 38 FREE command (UR), 8 FREE parameter (UR), 29 Free records, number of (UR), 13 G G option (UR), 12 GDI example (UR), 64 GDI (UR), 61 GDI configuration option TSIDDMP (UR), 20 TSIDDTD (UR), 12 GDI configuratio
Indexed sequential DD statements (UR), 17, 26, 38 Inhibiting LUB allocation TLBL option 64 (UR), 9 with SYS number (UR), 11 Inhibiting LUB allocation (UR), 7 Initializing tapes (UR), 33, 44, 11 Input DTF names TSIDDMP (UR), 20 TSIDDTD (UR), 12 IOMDTRT (UR), 45 ISAM datasets (UR), 6, 27 ISAM See Indexed sequential J JCL DD statements (UR), 12 specifying DD statements (UR), 2 JCL BIM-EPIC enhancements(UR), 41 JCL enhancements (UR), 16 JCL requirements (UR), 23 JCLLANG configuration option (UR), 1 to 2 JCLOPT
JCL requirements (UR), 32 parameters (UR), 32 syntax examples (UR), 32 LOCK command (UR), 32 Locked status (UR), 18 Locking version (UR), 39 Locking a dataset or version (UR), 32 Logging VSAM datasets (UR), 29 Logical IOCS (UR), 19 LUB allocation DTFPH (UR), 7 inhibiting with DD statements (UR), 34 inhibiting with SYS number (UR), 11 inhibiting with TLBL option 64 (UR), 9 physical IOCS (UR), 7 TSIDASS (UR), 7 TSIDMAP (UR), 7 warning (UR), 7 LUB allocation (UR), 30, 7 M M option (UR), 13 Main vault (UR), 35
MTC (UR), 13 MULTCPU configuration option CPU independence (UR), 28 MULTCPU configuration option (UR), 31 Multi-dataset groups prime dataset name (UR), 13 Multi-dataset processing autocatalog with DD statements (UR), 22 examples (UR), 19 FREE DD statement (UR), 29 refer-back with DD statements (UR), 45 scratching multi-dataset tapes (UR), 16 Multi-volume DD statements (UR), 45 processing limits (UR), 14 MVS compatibility (UR), 4, 42 MXIG parameter (UR), 38 N NAME parameter (UR), 8 NCATDSK configuration opt
Owner ID (UR), 13, 3 Ownership (UR), 3 P PACCT (UR), 51 Panel Descriptions Display (UR), 15 Panel help (UR), 14 Panel IDs Display (UR), 15 Panel navigation help (UR), 14 Parameter tables, xi Parameter-expressions defined (UR), 3 parameters (UR), 23 Partition independence disk pools (UR), 15, 34 Partition independence (UR), 31 Partitions starting/stopping (UR), 35 PASS parameter (UR), 22 PASSWD configuration option (UR), 38 PASSWORD command (UR), 38 Passwords EDD and version use (UR), 10 PDISPLAY,POFFLOAD,P
Purge command (UR), 48 Purging EDD (UR), 39 tape volumes (UR), 50 versions (UR), 39 volsers (UR), 39 with DD statements (UR), 22 Purging (UR), 38 Purging datasets with JMCL (UR), 5 PUT Request (UG), 22 Q QDAS access during open/EOX (UR), 44 and space holder records (UR), 45 Quick allocation with QDAS (UR), 44 QUIESCE command JCL requirements, 41 parameters (UR), 41 syntax examples (UR), 41 QUIESCE command (UR), 41 R Random access syntax examples, dataset (UR), 9 syntax examples, detailed record (UR), 10 s
display active (UR), 38, 43 display NEW (UR), 43 display NEW report (UR), 38 display PULL (UR), 43 display PULL report (UR), 38 display PULL, DSN report (UR), 38 display scratch report (UR), 43 display vault report (UR), 38 expiration date (UR), 38, 43 Report writers (UR), 37 Reports Activity Log Report (UR), 7 Create Date/Time Activity (UR), 31, 33 Create Job/Time Activity (UR), 15 creating (UR), 36 customized (UR), 2 Dataset to Tape (UR), 13 Dataset to Tape Report (UR), 27 offload tape datasets (UR), 30 o
Rewind tape DD statements (UR), 45 RLSE parameter (UR), 38 RMNTPRT configuration option (UR), 17 ROUND parameter (UR), 38 RPG-II (UR), 61 RSTRT (UR), 59 Rules for dataset retention work datasets (UR), 25 Rules for dataset retention (UR), 24 Running TVTO (UR), 11 Running TSIDLVT (UR), 17 S SAM datasets (UR), 6, 29 Scheduling dependent tasks (UR), 5 SCRATCH TSIDUTL (*UR), 23 SCRATCH command JCL requirements (UR), 48 parameters (UR), 48 syntax examples (UR), 49 SCRATCH command (UR), 48 Scratch procesisng (UR)
SHR subparameter (UR), 19 Sign-On panel (UR), 66 Size See Tape size Skip JCL See Job management control language Slots current (UR), 20 SM-2 (UR), 39 SM2 See Sort packages Small tapes (UR), 3 Smalltapes(UR), 3 SOL/VSE Tape Output Functions (UR), 54 SORT files (UR), 7 Sort programs CA-SORT (UR), 42 DFSORT (UR), 42 SYNCSORT (UR), 42 Sort programs (UR), 37, 39 SORTWRK datasets (UR), 33 SPACE DD parameter (UR), 34 Space holder records (UR), 45 SPACE parameter example (UR), 38 secondary extent size (UR), 2 SPACE
JMCL parameter (UR), 5 SYSLNK (UR), 35 SYSLST (UR), 61, 64 SYSMDUMP statements (UR), 7, 9 SYSnnn DD parameter (UR), 34 SYSnnn subparameter (UR), 36 SYSOUT parameter (UR), 9, 48 SYSOUT statements unsupported (UR), 5, 7 SYSPCH (UR), 61, 64 SYSPRINT statements unsupported (UR), 5, 7 System datasets DD statements (UR), 32 example (UR), 34 open across job boundaries (UR), 13 VSE device independence (UR), 64 System ID searching by (UR), 16 System ID (UR), 11 System logical units ASSGN (UR), 2 System options.
Terminating sequential access (UR), 11 Termination options DISP DD parameter (UR), 22 Test jobs (UR), 69 THLDOPEN (UR), 24, 39 TIME parameter (UR), 5 TLBL option codes (UR), 7 TLBL option codes 0 no options in effect (UR), 7 16 or D dataset drop (UR), 68 3 do not rewind (UR), 8 32 conditional catalog (UR), 69 64 no LUB allocation (UR), 9 TLBL option codes (UR), 7 TLBL options (UR), 7 TLBL statement format (UR), 2 parameters (UR), 2 syntax examples (UR), 6 TLBL statements BIM-EPIC differences (UR), 2 default
TSIDLVT, 7 control statements (UR), 8 report (UR), 17 VTOC data in batch (UR), 17 TSIDLVT (UR), 34, 8 TSIDMAP macro ILIST Parameter (UR), 6 TSIDMNT QUIESCE (UR), 41 reports (UR), 19 TSIDMNT command JCL requirements (UR), 4 parameters (UR), 4 syntax examples (UR), 5 TSIDMNT command (UR), 4 TSIDMNT.
U UIN (UR), 7 UNCDSK configuration option ISAM limitation (UR), 27 uncontrolled DA datasets (UR), 26 UNCDSK configuration option (UR), 6, 36 Uncontrolled datasets DD statement example (UR), 13 DD statements (UR), 13, 38 SAM (UR), 29 VSAM (UR), 29 Uncontrolled datasets (UR), 36 Uncontrolled tapes Early Drive Release (UR), 31 UNCTAP configuration option (UR), 6, 36, 9 UNCTAP configuration options Early Drive Release (UR), 31 UNCTL configuration option (UR), 6, 36 UNIT DD parameter (UR), 11 UNIT parameter (UR)
TSIDVLT (UR), 22 VAULTDEF macro (UR), 19 Vaulting Cross-Reference Report (UR), 26, 27 Vaulting method assignment (UR), 27 Vaulting methods (UR), 19 Vaults current (UR), 20 manually controlled (UR), 25 VDETACH (UR), 32 Version attributes block count (UR), 19 block size (UR), 19 creating job and device (UR), 19 creation date and time (UR), 19 current vault and slot (UR), 20 expiration date (UR), 19 extent number and address (UR), 19 file sequence number (UR), 18 generation number (UR), 17 last access (UR), 19
extent information (UR), 6 VSAM datasets (UR), 29 VSAM/SAM datasets DD statements (UR), 32 VSE Attention Routine (UR), 6 Operator console commands (UR), 6 system utilities (UR), 37 VSE label area accessing (UR), 26 TSIDGLB (UR), 26 TSIDPLB (UR), 26 VSE Label Area (UR), 42 VTAM accessing Online Manager (UR), 3 VTOC access during open/EOX (UR), 44 generation datasets (UR), 17 space holder records (UR), 45 updates during close (UR), 45 VTOC (UR), 44 VTOC entries displaying (UR), 34, 17 VTOC utilities batch rep
