This section contains information on executing the batch , creating master files, backing up master files, producing indexes, using the utility, using the Group Processing Option, writing user exits, executing from a user program, and installing and using the User Contributed Routines (UCRs).
This section contains information on executing the batch
CA Librarian, creating master files, backing up master files, producing
CA Librarianindexes, using the
CA Librarianutility, using the Group Processing Option, writing user exits, executing
CA Librarianfrom a user program, and installing and using the User Contributed Routines (UCRs).
CA Librarianis a highly sophisticated and flexible storage medium with a wide variety of services for storing, retrieving, and manipulating data. The data can be source programs, test data, text, or anything that can be represented on 80-byte records.
CA Librarianis an executable program that responds to a set of control statements and associated options.
CA Librariancan accept any data in an 80-byte record format and store the data on a specialized library called a master file. Master files are allocated through job control and initialized (defined) using
CA Librarian. An
CA Librariansite can have one master file initialized for all users, or it can have many master files. You can designate some of them for general use and tailor others to store a particular type of source program.
Information is stored on a master file in discrete, uniquely-named collections of records called members. The information on the member is retrieved by member name. The number of members that you can store on a master file is limited only by the size of the area allocated for the master file.
Once information is stored as a member,
- Insert, delete and replace records.
- Compare a member to another member or another file.
- Resequence the records of a member.
- Merge members.
- Obtain a listing of the contents of a member.
- Provide a variety of master file listings and indexes.
Master files must be allocated on disk. Member data records and control information are created and edited on disk files.
The following documentation updates have been made in the second edition of this documentation:
- Traditional and Wide Record Formats for Master Files -- Provided update on where to find more information about LAMSERV implementation; clarified that wide record master files can occupy secondary extents butnotmultiple volumes.
Wide Record Master Files
There are now two types of
CA LibrarianMaster Files, Traditional (Advanced File Organization or AFO) and Wide Record master files. Traditional master files are designed as direct access data sets using BDAM or VSAM access methods. Wide Record master files are designed as partitioned data sets using PDS or PDS/E organizations. Complete compatibility with
CA Librarianapplications from release 4.1 or earlier is assured. However, there are a small number of compatibility considerations that apply when using wide record support.
- Statement level archiving.
- An advanced file comparison utility, the Comparator II.
- Compression of data.
- Automatic job control statement generation.
- An optional direct interface between IBM software andCA Librarianmaster files through theCA LibrarianAccess Method.
The archiving facility is an advanced
CA Librarianfeature that lets you recreate previous versions or levels of an updated member. When archiving is activated for a member,
CA Librarianretains all records in the member that would otherwise be deleted during an update operation. As updates progress, the records are marked to indicate the levels where each record belongs. If you request an earlier level of a member,
CA Librarianreconstructs the level using the records marked as belonging to the specified level.
The following shows the development of multiple levels in an archived member.
INITIAL FIRST SECOND MODULE UPDATE: MODULE UPDATE: MODULE -------- ---------- --------- ---------- ---------- |010 A| |-REP ALL| |010 A | |-REP ALL| |010 AAA| |020 B| |010 A | |020 B | |010 AAA| |010 A | |030 C| |020 B | |030 CC| |030 CC | |020 B | |040 D| |030 CC | |030 C | |040 DD | |030 CC | |050 E| |040 DD | |040 DD| |050 E | |030 C | |060 F|-->|050 E |-->|040 D |-->|060 F |-->|040 DD | |070 G| |060 F | |050 E | |070 GG | |040 D | |080 H| |070 GG | |060 F | |080 HHH | |050 E | |090 I| |080 HH | |070 GG| |090 III | |060 F | |100 J| |090 I | |070 G | |100 J | |070 GG | -------- |100 J | |080 HH| ---------- |070 G | ---------- |080 H | |080 HHH| |090 I | |080 HH | |100 J | |080 H | --------- |090 III| |090 I | Deleted or replaced records |100 J | retained within the module. ----------
You can retain as many as 255 archived levels for a single member. The current level number and the total number of levels maintained for a member are reported on the Management Index listing. You can request that
CA Librarianaccess an earlier level of a member by specifying its absolute level number, its relative level number, or the date the level was current.
A master file must be initialized to support archiving, but an archived master file can contain both archived and non-archived members.
Comparator II is an advanced file comparison utility that defines comparison strings for any two files and produces a report on the results of a comparison of these files.
Many options are available for selecting the files, defining the strings, and formatting the reports. You can find complete information about Comparator II in the
You can store
CA Librarianmembers according to one of three compression levels:
- NONEEach record is stored in its original 80-byte image.
- PARTAll spaces are removed from each record before it is stored on the master file.
- FULLAll spaces are removed from each record and each set of four bytes is compressed into three. For members sequenced in columns 1 through 6 only, COBOL reserved words are compressed into a single byte. Full compression is the default.
Under standard conditions, you should store members fully compressed. This saves both disk space and I/O operations. When saving space is not a primary consideration, use either of the alternate levels of compression.
CA Librariancompresses a member when it is first added to the master file; thereafter, only the changes applied to the member pass through the compression algorithm.
CA Librariandecompresses a member only when it is selected for compilation, printing, or punching.
Set the compression level default in the COMPRESS parameter when you initialize the master file. See the
Getting Startedfor more information. You can change the compression level of any member at any time, but only the changes applied to the member are compressed to the new level.
Job Stream Creation and Automatic JCL Generation
You can direct
CA Librarianto write data to an intermediate data set with a ddname of OSJOB. The data set can be a complete job that, when executed, produces an assembly or a compilation, or it can be a file passed as the SYSIN file to an assembler or compiler. In the case of a complete job stream, you can store the JCL with each member or
CA Librariancan generate the JCL automatically from parameters stored with the member. You can supply these parameters during member level processing or at master file initialization on a -JCL statement. The -JCL statement and its options are described in the
Batch Command Referencesection.
CA LibrarianAccess Method
CA LibrarianAccess Method (LIB/AM) z/OS and OS/390 is an option providing a direct read-only interface between IBM language translators and
CA Librarianmaster files. LIB/AM allows members stored on a master file to be read as if they were members stored on a partitioned data set. LIB/AM is installed as an z/OS and OS/390 subsystem.
For more information on LIB/AM, see the
CA Librarianand Other Products
The following interfaces are available to integrate
CA Librarianinto a variety of processing environments:
- CA Librarianand CA Roscoe
- CA Librarianand CA Datacom Datadictionary
- CA Librarianand VM/ESA
- CA Librarianand ISPF/TSO
- CA Librarianand SAF-compatible Security Systems
CA Librarianand CA Roscoe
CA Vollie, an online program development system for VSE installations, can access and update its own online library, as well as VSE source statement libraries.
CA Vollie provides 3270 screen handling capabilities and extended utilities for POWER/VS. Both remote job entry and job output are provided. CA Vollie supports the immediate update of a
CA Librariandisk master file through the immediate online update (IOU) facility.
CA LibrarianArchiving feature and date stamps are supported.
For more information on accessing
CA Librarianthrough CA Vollie, refer to current CA Vollie documentation.
CA Librarian/CA Datacom Datadictionary Interface (LIB/DD)
CA Librarian/CA Datacom Datadictionary interface (LIB/DD) provides facilities for integrating
CA Librarianmaster files and CA Datacom Datadictionary. LIB/DD lets you expand a CA Datacom Datadictionary record entity referenced by a COPYDD statement in an
CA LibrarianCOPYDD option activates the interface. The
Usingsection describes the function and use of the COPYDD statement while the
Batch Command Referencesection provides detailed information on the COPYDD option.
To use LIB/DD, your site must have installed
CA Librarian, CA Datacom Datadictionary, and LIB/DD.
For instructions on installing CA Datacom Datadictionary, see the
Datacom System Generation Facility Installationsection. For instructions on installing the LIB/DD interface, see the
CA Librarianand VM/ESA
Users in an IBM VM/ESA environment can gain online access to
CA Librarianmaster files through the
CA Librariancomponent VM/ESA ISPF (LIB/CMS-ISPF). The LIB/CMS-ISPF component provides a set of VM/ESA-like terminal commands for adding, accessing, editing, and updating
CA Librarianmembers. In addition, you can display a variety of master file and member indexes on the terminal screen. You can also submit jobs to batch machines through the LIB/CMS-ISPF component.
With the LIB/CMS-ISPF component, users have the advantage of a totally interactive environment supported by the control security, auditing, and recovery features of
You can perform all LIB/CMS-ISPF component activities through CA-supplied ISPF menus and panels. An extensive HELP facility is available through ISPF and native command mode processing.
CA LibrarianRelease 3.7, LIB/CMS users can initialize master files and process members in a VM/ESA stand-alone environment without recourse to other operating systems. For a complete description of these facilities and any LIB/CMS-related system service routines, consult the
Systems Services (VM/ESA)section.
For more information on the LIB/CMS-ISPF terminal commands, See the
Command Reference (LIB/CMS)section. For information on installing the LIB/CMS-ISPF component, See the
CA Librarianand ISPF/TSO (ELIPS)
CA LibrarianInteractive Productivity Services) is an interactive ISPF application that provides online access to
CA Librarianfor the ISPF/PDF environment. ELIPS takes advantage of the facilities introduced with version 2 of PDF to provide a user accessing an
CA Librarianmaster file with all of the convenience and power of ISPF.
ELIPS uses the ISREDIT services of ISPF/PDF version 2 to permit direct editing of
CA Librarianmembers. No modifications to IBM code were made to accomplish this. Working as a standard ISPF application, the ELIPS edit function uses the File Access Interface Routines (FAIR) to extract the records from a master file and then uses the Immediate Online Update (IOU) to directly update the master file.
The ELIPS functions let a programmer directly edit a member on a master file, browse a member, copy or rename members in the same master file, delete members from a master file, view or update control information, print a member from an ELIPS session, or view master file and site defaults and the list of valid language types. There is a HELP facility available to ELIPS users complete with tutorial displays.
No modifications to ISPF or TSO are required when ELIPS is installed. ELIPS offers shared master file protection and safeguards against potentially conflicting concurrent member updates. Extensive exit capabilities make it possible to tailor ELIPS to meet any needs or to conform to any online processing standards.
ELIPS Command Referencesection for a complete description of the facilities of ELIPS.
Note:For important information regarding ELIPSGEN and VIO, refer to Step 13A Assemble and Link the ELIPSGEN (specifically the VIO macro parameter section) of the
CA Librarianand Security Systems
CA Librarianoffers a comprehensive security structure for both the batch and online environments of
CA Librarianand its Change Control Facility (LIB/CCF). The security structure provides three tiers of control over a master file in the z/OS and OS/390 and VM/ESA environments. These tiers are: MCD security, Basic security, and Member security.
MCD security permits management to restrict access to selected
CA Librarianmaster file members without implementing an external access control facility.
MCD security protects members on the master file through a management code and member status values. The management code consists of an arbitrary code assigned to a master file. The member status values let you designate the degree of protection for each member on the master file.
Basic and Member security permit management to restrict access to master files and their members through an active access control facility. To provide this protection,
CA Librarianuses Unicenter TNG Framework for z/OS and OS/390 to interface with the following security systems: CA Top Secret, CA ACF2, RACF, or any other security system compatible with the IBM System Authorization Facility (SAF).
CA Librarianuses integrated calls to whichever access control facility is present. No modifications or exits are needed to access these security systems.
For Basic security, master files are defined as resources and access rules are specified for each
CA Librarianmaster file. Permission to access the master file grants access to its members.
Member security goes one step further than Basic security in that you can define individual members as resources requiring their own access rules. To protect individual members,
CA Librarianuses a process known as surrogate naming. Surrogate naming involves the assignment of an alternate qualifier (or surrogate) name to the master file during master file initialization or reinitialization. Then, in the access control facility, access rules are defined for the master file members using the surrogate name in place of the master file's data set name.
Basic and Member security extend master file protection beyond the management codes and member status values of MCD security. You can choose between maintaining, supplementing, or replacing MCD security with Basic or Member security.
For a complete description of the security interface, see the