The Report Writer extracts data from various data files and generates output that is suitable for printing. The report is generated in four steps:

1. Examine the report definition.
2. Collect the applicable data.
3. Sort the collected data in the correct order.
4. Format and output the sorted data.

Over 220 predefined report definitions are included, providing a wide variety of possible examples

1.6 FORMAT Program

The FORMAT program is designed to read and write fixed length, blocked records in either ASCII or EBCDIC from either LABEL or NOLABEL media. FORMAT also allows for numbering the records, removing tabs, converting everything to uppercase and several other very useful features. Features exist to make an image copy of the entire medium, and optionally put that image file on disk. Such an image file will behave exactly like an on-line medium when used with the FORMAT program.

This chapter is designed for those people who are assigned the responsibility of responding to system requests to load and unload media. This section of the manual covers the main aspects of operations both for sites that have continuous OPERATOR coverage of the system and sites that have a limited schedule of coverage.

The following section provides some helpful background information about MEDIA. The component programs are discussed in overview and some of the concepts you need are described.

To be an OPERATOR you must have the OPERATOR privilege. Please contact your MANAGER if you do not and you need to perform any of these OPERATOR commands. For a description of OPERATOR privilege see the overview section of the General User's Guide.

In MEDIA, all of the commands and display formats are designed to look and operate like those in any VMS utility. All VMS wildcards are supported and VMS conventions for dates and times are honored. MEDIA can be treated as a convenient extension of VMS. All of the basic operations of a media library that are automated under MEDIA are shown in the Overview of Functions Table.

MEDIA

Backup/Restore

Track storage medias physical and online location. Locate needed files using contents displays. Release unwanted media into the released pool. Manage SCRATCH media when needed. Execute MEDIA procedures on mounted media.

Create and submit backup jobs at regular intervals. Restore files selectively that have been backed up. Manage the source disks and target media assignments for backups. Use restore via search to restore large quantities of backed up files. Auto submit backup jobs using predetermined intervals. Recover from data disasters with full disk recovery. Simple commands allow user to restore needed files without waiting for Media Librarian.

2.1.1 Programs

The MEDIA program controls all aspects of media library management. It automatically tracks media and their contents directory file.

The BCKMGR program automatically tracks and submits jobs, maintaining an extensive database of backup activity. The VAULT program maintains and manages a database of the backed up files so that users can restore files from off-line storage without the assistance of the MANAGER.

The Server Process is a detached process that runs continuously on the system, to coordinate and share data across a cluster. It monitors drive activities, creates batch jobs as scheduled, coordinates all medium access and performs various related control functions. The server process is designed to minimize the number of operator responses required. For example, your MANAGER can set a parameter¹

so that the system leaves a labelled tape on-line until the next request. If the same tape is requested for the next job, you won't have to do a thing. The system will recognize that the correct tape is already mounted and will execute the job.

2.1.2 Pools

Media are categorized into three groups within the library called pools. See Figure 2-1 These pools are not necessarily physically separated from each other within the library because the pools are invisibly managed by MEDIA system. The pools can be divided into subpools that can be associated with different job queues, different types (e.g. cartridge tapes vs. nine track tapes), different functions or useful attributes, if desired.

• The Available pool consists of media which are available for assignment to users. When the medium is moved into the available pool, all attribute information is reset to the defaults and the medium will be re-initialized as soon as it is allocated. General users can allocate media from this pool without OPERATOR or MANAGER intervention. The system selects from this pool on a first in, first out basis.
• The Allocated pool consists of media that have been assigned to a particular user. These media are in active use and can be accessed by the general user to whom they are ASSIGNed using MEDIA system.
• The Released pool consists of media that were allocated to users, but are no longer needed by them. MEDIA holds these media with data intact for a specified length of time (set by the MANAGER) before re-initializing them, allowing both a safety margin for the user to change his mind about needing a particular medium and a chance to clean or recertify a medium before it is moved into the available pool. The system moves these media from one pool to the next on a first in, first out basis.

Figure 2-1 Media Pools

2.1.3 Access control

1. MANAGERS can access all media
2. OPERATORS have "read only" access to all on-line information at all times
3. All other users can access their own media and any media set to general access.

In addition to being able to read the on-line directory information for any medium in the database, OPERATORS have sufficient privilege to add media permanently to the database. Once added, that media can be removed only by someone with OPERATOR privilege or by the MANAGER.

2.1.4 Job queues

A VMS job queue is used to simplify the user/ OPERATOR interaction. When a user creates a MEDIA job it is INSERTed into a VMS queue. ² Thus when a user makes a request it is submitted into a queue, releasing their terminal for other uses. When the job is completed a message is sent back to the original user indicating this. You can then control this queue to coordinate when jobs are performed so as to match your work schedule. Mount requests can only come from a job executing in a running queue.

2.1.5 Load requests

A load request is an OPCOM (OPERATOR communication) message that appears on the OPERATOR'S terminal requesting a tape or disk to be loaded. ³ In general mount OPCOM messages originate as a result of using the VMS MOUNT or the MEDIA MOUNT commands.² In this manual only the behavior using the MEDIA commands is covered.

Two kinds of load requests can be issued, interactive and batch. Interactive requests are generated by a user sitting at a terminal and entering a MOUNT command. Batch requests are generated by a MEDIA job executing in a batch queue. When you are away from the console, these jobs just accumulate in the queue. You have control over when and in what sequence the batch queue operates. At most sites, the MANAGER sets the system to batch mode for greater efficiency.

2.1.6 Volume sets

Media can be attached together, so that the system considers them to be a single medium with several volumes. This can be very useful for organizational purposes.

While attached, the entire volume set can be addressed by the name of the first volume in the set, although the individual media do retain their separate names. A medium must be detached from the set before it can be released or independently overwritten. There are several commands to attach or detach a medium to or from a volume set. It is also possible for you to extend a volume as needed during a job execution.

2.1.7 Using templates

The use of templates is a convenient and time saving way of accessing media. MEDIA uses templates to define charateristics of media which can be used to simplify operations.

2.1.7.1 Scratch templates

Scratch templates are designed to define the characteristics of a scratch medium. Scratch media is media that resides in the available pool but which may be picked at random by the operator so a specific name need not be chosen. A scratch template is an entry in the MEDIA database that represents the desired characteristics of a scratch medium when the job runs.

Once the scratch template is created, it may be assigned to a job. When the job is executed a message is sent to the operator requesting scratch media. If the media meets the characteristics of the template, it is acceptable for the job.

2.1.7.2 Other templates

Two other types of templates are used in MEDIA.

A template is used in the ADD NEW media operation to define the default characteristics for each media type in the system.
The MCL Modify Multiple Media menu uses templates to designate the fields that are to be changed in a multiple modify operation.

2.2 Operator functions

This section describes some typical sequences of OPERATOR functions. The typical sequence are:

• At the start of shift, the OPERATOR enables the terminal and checks the queue for media needed for those jobs currently in the queue.
• The OPERATOR then retrieves the necessary media from the library, or other storage area, and then starts the queue.
• The OPERATOR responds to each mount request as it is issued.
• At the end of the shift, the OPERATOR stops the queue, unloads and resets the removable devices controlled by MEDIA and disables his terminal.

Each of these activities is described in the following sections.

2.2.1 Defining operator terminals

Before you can perform operations involving the REPLY command, you need to define your terminal as an OPERATOR terminal. This is done using the DCL command REPLY/ENABLE at the desired terminal in the format:

$ REPLY/ENABLE=MEDIUM_TYPE(S)

For example, if you are the OPERATOR handling tapes, you would type:

$ REPLY/ENABLE=TAPES

If you are going to handle tapes and disks, you enter:

$ REPLY/ENABLE=(TAPES,DISKS)

This allows MEDIA to send OPERATOR messages to that terminal based on the generic type of medium involved. When you enter the enable command, the following OPCOM messages will appear:

%%%%%%%%%% OPCOM dd-mmm-yyy hh:mm:ss.cc %%%%%%%%%% Operator TERMINAL: has been enabled, username YOURNAME %%%%%%%%%% OPCOM dd-mmm-yyy hh:mm:ss.cc %%%%%%%%%% Operator status for TERMINAL: TAPES, DISKS

When you have finished using that terminal, you can disable it by entering the command:

$ REPLY/DISABLE

and you will see the following message:

%%%%%%%%%% OPCOM dd-mmm-yyy hh:mm:ss.cc %%%%%%%%%% Operator TERMINAL: has been disabled, username YOURNAME

2.2.2 Queue ops

The batch queue that is defined in MEDIA as it is installed is called SYS$TAPE. This section uses the basic queue name SYS$TAPE in examples, but your MANAGER may have defined other queues as the system was configured. The functions described for SYS$TAPE are equally applicable to any other queue defined for your system. ⁶

2.2.2.1 Examining the queue

$ SHOW QUEUE/ALL SYS$TAPE

As the system is installed, this produces the following type of display:

Jobname Username Entry Status ------- -------- ----- ------ 1200 HOSKINS 463 Executing 1322 JEEVES 464 Pending B400 WILEY 465 Pending

This display can be modified easily to add the location and volume set list by using a command procedure ⁷

(@MEDIA_LIBRARY:TAPEQUE.COM) supplied with the system when distributed. Check with your MANAGER for this information. As an example of the altered display:

$ @MEDIA_LIBRARY:TAPEQUE Batch queue SYS$TAPE Media Username Entry Status Location ----- -------- ----- ------ -------- 1. 1200,1201,1202 MOSSBERG 453 Executing LIBRARY 2. 1322 JOHNSON 454 Pending CABINET B 3. B400 SYSTEM 456 Pending LIBRARY

Having determined what media are needed for the jobs waiting in the queue, you can now go collect them from their various locations, and go to the next step.

2.2.2.2 Starting and stopping the queue

The queue can be started using the DCL command:

$ START/QUEUE SYS$TAPE

To stop the queue, type:

$ STOP/QUEUE SYS$TAPE

If it is the end of shift and you need to unload all tape reels (or removable disk packs) that are still mounted, you could by typing:

$ MEDIAS SET/DEVICE */UNLOAD/RESET

unload any medium that are still loaded and not currently in use. After the unload, just remove and store the media.