Memorex LOCK - VERSION 2-24 Especificaciones descargar pdf (Pagina 271)

SQL/VSE Tape Output Functions

Chapter 7. Running Jobs With BIM-EPIC 7-51

SQL/VSE Tape Output Functions

SQL/VSE is a long running task that manages database files for other tasks in the same VSE

environment. The ability to archive database files (and their corresponding journal files)

without having to terminate the SQL/VSE task is accomplished by invoking the operator

communications facility for the partition-id in which the SQL/VSE task is running (MSG pp,

where pp is the two character partition-id desired). At that point, SQL/VSE asks the console

operator various questions. However, accomplishing archive functions of SQL/VSE where

the output tape(s) are under the control of BIM-EPIC requires special considerations.

The problem arises because both BIM-EPIC and SQL/VSE want to manage the physical

device allocation processes. Such processes are expected as part of a dataset management

product such as BIM-EPIC but unusual when found as part of a database management product

such as SQL/VSE. When both products are present in the same VSE environment, a conflict

arises. Attempts to totally eliminate all the conflicts has not been entirely successful.

However, the following considerations will allow you to accomplish your necessary SQL/VSE

tape output operations and still maintain BIM-EPIC control of those tapes.

Although this discussion relates to the SQL/VSE tape output function for ARCHIVE, the same

concepts covered by this discussion should apply to other tape output operations.

Your BIM-EPIC system must be configured with TAPE=YES and TAPLUB=YES (or nnn).

Each tape dataset name placed in the TLBL control statement for use with the ARCHIVE

function must be cataloged and the SYSnnn operand specified with a value other than

SYS005. The logical unit number chosen must be outside the range of numbers that might be

used for other SQL/VSE requirements. Only prime dataset names should be used and the

definition for each unique dataset name used may reflect the same logical unit number for the

SYSnnn operand.

The TLBL's required for each output file should reflect an option value of '2' to assure each

output tape volume is unloaded when closed.

Once the ARCHIVE request has been entered, SQL/VSE needs to know if you wish to use a

particular tape device which has been previously allocated to the SQL/VSE partition (called

STATIC by SQL/VSE) or any currently available tape device of your choice (called

DYNAMIC by SQL/VSE). Respond with the cuu of any currently available tape device and

note that this particular tape device will not actually be used for any purpose by SQL/VSE and

will also not be available to any other task for the duration of the archive process. This is an

unavoidable requirement. Each output tape dataset created during the archive process is

written to tape residing on a tape device other than the one specified above. Therefore, the

archive process always requires the availability of two tape devices at a minimum.

Description

Configuration

Requirements

DSN Catalog

JCL Requirements

1 2 ... 266 267 268 269 270 271 272 273 274 275 276 ... 488 489

Sin comentarios

Memorex LOCK - VERSION 2-24 Especificaciones Pagina 271