[an error occurred while processing this directive]
STANDARD: Z16SP020
DATE: 05/04/93
REVISION NUMBER: 02
ACCESS: B
TITLE: TLMS Standard
PURPOSE: To promote efficient use of the TLMS software
POLICY: Reference ACS Policies and Procedures Manual-Policy #Z16PP001
RESPONSIBLE
AREA: TSG/OPERATIONS
RELATED
MATERIALS: TLMS Manual
DEFINITIONS: NONE
1. The following are TLMS retention methods and their uses
at ACS:
Method Use
1. Catalog Control Not allowed; use #3.
2. Date Control Not allowed.
3. Catalog/Date Control Preferred for GDG &
Production Datasets;
Tape Retention Master
Entry required
4. Cycle Control Tape Retention Master
Entry Required
5. Elapsed Days Control Tape Retention Master
Entry Required
6. Move Immediate Control Tape Retention Master
Entry Required
7. Manual Control Allowed for Tape
Librarian only
8. Days Since Last Used Control Default
9. Expir'n Date Keyword Control Not allowed
2. The TLMS default retention is type 8 (Days Since Last Used
Control, with the number of days set at 45. Do not use
the 45 day default option for COM tape cartridges. While
certain exceptions will exist, normal requests for COM
tape cartridges should be handled by Method #8 on the
TLMS Request Form, with a specification of 10 days (this
will be more than ample time to send out and receive
back COM tape cartridges). See the next item (#3) for
information on submission of a TLMS Request Form.
3. All TLMS requests, including retention period changes when
the default is not appropriate, must be submitted to the ACS
Tape Librarian on a "TLMS REQUEST FORM" (ACS form #Z16D030).
The Tape Librarian or the designated backup person from the
Data Control Section is the only person authorized to change
retention files and other TLMS data files. NOTE: Certain
changes, if so indicated on the form, may require approval
above that of the Tape Librarian.
4. Volume serial numbers should never be specified in production
JCL or job documentation, except non-labeled volumes and
foreign volumes (cartridges that are not defined to TLMS).
These exceptions must have prior approval of the Data Control
Supervisor. See item #7 in module ODJE010 of the Operations
Documentation Standards for discussion of possible exceptions.
5. Because TLMS does not permit cycling or reusing of specific
volumes, jobs should not contain DD statements which reference
an older generation of a GDG for the purpose of writing on
that specific volume.
6. For a new tape cartridge. All three fields of the DISP para-
meter must be specified. In most cases, the fields should be
DISP=(NEW,CATLG,DELETE). TLMS does not permit the creation
of a new dataset over an existing one: Do not create a new
over an existing cataloged dataset using DISP=(OLD,KEEP,KEEP).
7. All datasets on a tape cartridge volume should have the same
TLMS retention criteria as the first dataset on that volume.
8. Blocking factors directly impact the performance of cartridge
tape drives. Block sizes should be as large as possible,
without exceeding DASD track size or 32K, whichever is smaller.
9. Any output tape cartridge with a disposition other than normal
return to the ACS tape cartridge library, must be written to
one of a predefined group of cartridges within the special
predefined group of cartridges that falls in the special range
of VOLSER numbers UVA000 - UVA999. Additionally, there must
be a TLMS auxiliary message generated at cartridge unload time
to inform computer operations of the exceptional disposition.
NOTE: This does not apply to tape cartridges that are to be
sent to off-site storage, as they are first returned to the
ACS tape cartridge library and then later pulled for relocation
to the off-site storage facility.
Tape cartridge users must provide Technical Services with the
DSNAME of all datasets that are to be forced to use the
special range of VOLSER numbers so that they may be added to
a TLMS table. Use a work request form to submit this infor-
mation. Tape Cartridge Users must then use a LABEL=EXPDT=97xxx
parameter on the DD statement of the output tape cartridge
dataset. TLMS uses this parameter to generate the necessary
messages which define the exceptional disposition of the
output tape cartridge. These messages, which cannot exceed
70 characters, are as follows:
LABEL=EXPDT=97001 - CARTRIDGE TO BE SENT TO SERVICE
BUREAU FOR MICROFICHE PRODUCTION
LABEL=EXPDT=97002 - CARTRIDGE TO BE RETURNED TO USER
DEPARTMENT FOR PROPER DISTRIBUTION
LABEL=EXPDT=97003 - CARTRIDGE TO BE RETURNED TO DATA
CONTROL FOR PROPER DISTRIBUTION
10. Permanent save retention will require an ACS director's
approval, and will not be permitted except in extreme situa-
tions. When requesting the preferred retention method (#3
-Catalog/Date), and if a retention period (date) is specified,
the retention period (date) must be of a specific duration and
not a permanent save, unless approved. The Tape Librarian
will process a TLMS Request Form with a permanent save reten-
tion period only if it has the above approval. All other
retention periods (dates) will be the result of user and ACS
discussion and agreement.
It is further proposed that the following suggestins be used with the TLMS:
1. Datasets that are expected to exceed the capacity of one
volume should not be output with other datasets on the same
volumes. There is very little benefit in having other data-
sets on the same volumes with multi-volume datasets, and it
adds complexity to keeping track of datasets and volumes on
TLMS reports and inquiry screens.
2. Incoming foreign volumes should be copied to a cataloged
dataset. This would provide TLMS protection of the data.
Non-labeled foreign volumes are most susceptible to inadver-
tent destruction.
3. Except for tape cartridges received from outside sources and
certain tape cartridges sent to outside sources, all tape
cartridge datasets should be cataloged in the MVS systems
catalog. To retrieve a cataloged dataset, only the DSNAME
parameter and OLD, SHR, or MOD in the DISP parameter need to
be coded; volume, label, and device information is not needed.
4. On multiple dataset volumes, each physical dataset should be
cataloged.
[an error occurred while processing this directive]
[an error occurred while processing this directive]
