toxicology data management system

National Toxicology Program Support

Database Administration Procedures

Revision History

  -------------- ------------------ --------------- ---------------------
  **Date         **Document         **Revision      **Reason for
  Released**     Number**           Level**         Revision**

  April 1998     TS-1000-2.2        2.2             Placed document into
                                                    new Word format

  April 1995     TS-1000-2.1        2.1             Policy change in
                                                    database backup
                                                    labeling scheme.
                                                    Revised pages 5-7.

  Dec. 1994      TS-1000-2.0        2.0             Addresses updated
                                                    database procedures.

  July 1987      TS-1000-1.0        1.0             New
  -------------- ------------------ --------------- ---------------------

National Toxicology Program Support

Database Administration Procedures

> Prepared for: National Institute of Environmental Health Sciences
>
> Research Triangle Park, NC 27709
>
> Contract no.: 273-95-I-0012
>
> Prepared by: Technology Planning & Management Corporation
>
> Imperial Center
>
> Canterbury Hall, Suite 310
>
> 4815 Emperor Boulevard
>
> Durham, NC 27703

Table of Contents

**Table of Contents**

Introduction

General Database Administration

Database Administrator Duties

Assistant Database Administrator

Performance Management

Maintenance of DBA Materials

ADABAS/NATURAL

NATURAL Program Standards and Guidelines

ADABAS/NATURAL Utilities

ADABAS File Definition

Database Recovery

Backups

Preparations for Data Restoration

Data Restoration

TDMS Accounts

Adding User Accounts

Passwords and User ID

APPENDIX A

ADABAS FILE INFORMATION

ADABAS FIELD INFORMATION

NATURAL USER ID ASSIGNMENT

DATA DEFINITION MODULE FORM

Introduction

The purpose of this document is to establish and maintain a consistent
set of control and standards for use by Database Administration on the
TDMS Mainframe Computer at NIEHS.

Standards in this document are enforced and maintained by the Database
Administrator (DBA). The DBA is responsible for the following duties:

-   Enforce data definition and data usage policies.

-   Advise how to access and update data in databases.

-   Establish standard coding procedures.

-   Maintain and expand procedures to edit and validate data in
    databases.

-   Ensure the National Institute of Environmental Health Sciences
    (NIEHS) operations use standard database procedures; such as, backup
    and restart/recovery procedures.

The Quality Assurance and User Support Manger's oversee the following:

-   General administration of databases

-   NATURAL Program Standards and Guidelines

General Database Administration

This chapter will report the various duties and functions of the
Database Administrator .

# Database Administrator Duties

DBA's have general administration responsibilities and control of the
TDMS Production, Benchmark, and Test Databases. Major concerns include:

-   Establishing and enforcing standards and procedures.

-   Providing assistance to software and liaison groups.

-   Monitoring actual and planned usage of databases.

-   Maintaining an adequate interface with the vendor.

# Assistant Database Administrator

The assistant DBA keeps the database operative in the DBA's absence. The
Assistant DBA is trained in routine database administrative procedures
and in troubleshooting procedures.

# Performance Management

The DBA establishes and maintains the stable performance of database
software for all TDMS databases. The DBA monitors database performance
statistics to tune operating parameters of the database and makes
recommendations to the NIEHS Office of Computer Technology Services
(OCTS) for hardware configuration and database physical design.

# Maintenance of DBA Materials

The DBA maintains and updates manuals for vendors and staff.

# ADABAS/NATURAL

The DBA executes utilities for ADABAS and NATURAL.

## NATURAL Program Standards and Guidelines

NATURAL programming standards and guidelines are described in *Software
and Documentation Standards*.

## ADABAS/NATURAL Utilities

Executed ADABAS utilities are automatically recorded bi-weekly in ADABAS
checkpoint backup logs.

## ADABAS File Definition

An ADABAS file must first be defined in the Test Database before it can
be defined in the Benchmark or Production Databases. The file in the
Test Database will contain only a sample of the data eventually loaded
in the Benchmark or Production Databases.

Database Recovery

This chapter will discuss the procedures to follow if the database
becomes corrupted.

If part of the database becomes corrupted, the data from backup media
and ADABAS protection logs must be restored. A weekly backup is the
first step to ensuring a complete database recovery. Following is a
discussion of database backups succeeded by the steps to prepare for and
implement a full database restoration.

# Backups

The production, bench and test databases, and the protection logs for
each, are automatically backed up following the nightly Update procedure
on Wednesday mornings (to tape media for long-term storage), and via
disk-to-disk backups completed nightly, on Monday, Tuesday, Thursday,
and Friday. Update submits the digital command language (DCL) procedure
STARBACKUPPROCS: ADABAS_BACKUP and STARMAINTCOM:BACKUP_TDMS_DBS. The
first of these procedures can also be submitted manually using the DCL
procedure STARBACKUPPROCS: SUBMIT\_ BACKUP (instructions on how to use
it are in the procedure itself); the second procedure can be submitted
either manually or it submit itself upon completion, it's operation is
independent of Update.

Tape database backups are identified by a one- or two-character prefix,
which identifies the database, and a three-character sequence number,
which is automatically increased by one after each series of backups.
The current cartridge sequence number is kept in the file
BACKPARMS:BACKUP\_ LABEL.DAT. The file BACKPARMS: BACKUPS_TOBEDONE.DAT
shows which databases should be backed up. Normally, all three databases
are backed up, but this file can be edited to backup only one or two
databases. Disk-to-disk backups are kept on a separate disk, used for
this purpose alone, under the specification
NTP_BACKUP1:\[SAG.ADABAS.DB00X.BACKUP\], where X equals the database
number.

Tape database backups are performed on a TZ87 backup device. For
Production database backups, the one-character database identification
sequence is 7, followed by the three-character sequence number
(001-999), and the two-character cartridge sequence number (01-09,
depending on how many cartridges are required, normally 05). An example
of a cartridge label for the Production database backup is 754501,
754502, 754503, 754504, 754505.

The production database is backed up each Tuesday and Thursday night
after the successful completion of each evening UPDATE cycle. Each back
up set is kept on-site for two weeks. After two weeks, they are
transferred to off-site for at least two months. Disk-to-disk database
backups are completed in addition to the weekly TZ87 tape backup,
following the production days when the tape backup is not done. The main
function of the tape backup is long term storage, whereas the
disk-to-disk backups function as the first choice for database restores.
Non-production databases are also backed up twice weekly via
disk-to-disk procedures; the frequency of these backups may vary
depending on the volume of non-production database activity

For the first 999 backups, the one-character database identification
sequence was P. It was changed to the database number after the
three-character sequence number reached 999. This change was made to
eliminate conflicts in the Storage Library System between cartridges
still off-site from the first rotation and cartridges that would have
gone off-site in the second rotation with the same label.

For Bench database backups, the one-character database identification
sequence is 5, followed by the three-character sequence number and the
two-character cartridge sequence number (normally 01). An example of a
cartridge label for the Bench database backup is 554501.

Test database backup labels are slightly different. They begin with a
one-character sequence, 1, followed by the three-character sequence
number and a two-character cartridge sequence number (normally 01). An
example of a cartridge label for the Test database backup is 154501.

Protection log backups are letters PTG followed by the three-character
sequence number. There is no cartridge sequence number. This backup
always uses one cartridge. An example is PTG545.

For the first 999 backups, the first three letters of the database
identification sequence were PLG. The letters were changed to PTG after
the three-character sequence number reached 999. This change was made to
eliminate conflicts in the Storage Library System between cartridges
still off-site from the first rotation and cartridges that would have
gone off-site in the second rotation with the same label.

An entry is entered on the ADABAS Backup Log every time an ADABAS TDMS
database backup is performed. The Backup Log contains the following
information:

-   Tape label

-   Number of cartridges

-   Date of backup

-   time of backup

-   Date stored off-site

-   Date returned from off-site

-   Date scratched

-   Responsible person for each

Logs are automatically printed for each backup and maintained on-line
for as long as the backup is stored, either on- or off-site. Off-site
storage is based on government policy and is determined by the year and
month of completion. Code that assigns the off-site storage period is
included in the backup procedure and follows this criteria:

-   Two months of backups are archived at all times, in addition to
    backups from the first week of each month. Backup tapes are
    scratched after April of each calendar year. At the beginning of
    April, backups from March and February are archived and January
    backups are scratched, with the exception of backups from the first
    week in January. In early May, backups from April and March are
    archived, and February backups are scratched, except for backups
    from the first week in February. This process of archiving and
    scratching backups continues throughout the calendar year.

-   Cartridges with labels beginning with \"7\" and \"PTG\" are kept
    on-site for two weeks following their creation. After two weeks they
    are shipped off-site. The first set created each month, except those
    created on quarterly months, remain off-site for one year; the first
    sets created on quarterly months are kept off-site permanently.
    \"7\" and \"PTG\" tapes that are not the first set of the month
    remain off-site for two months (following their two weeks\' of
    on-site storage) and are then brought back on-site and made
    available for re-use.

-   The \"5\" and \"1\" cartridges (Bench and Test Databases) are kept
    on-site for two weeks, but are not shipped off-site. After they are
    kept on-site for two weeks they are made available for re-use.

# Preparations for Data Restoration

Prior to data restoration, notify the Systems group to put the Index
File at the beginning of the disk. Execute the ADABAS disk setup
procedure for the disk to be restored, for example:

\@dsa39:\[adabas.startup.alloc_disks\]allocate_adadsk8

# Data Restoration

Follow these steps to perform Data Restoration on the prepared disk:

1.  Restore the Database from backup media as follows:

```{=html}
<!-- -->
```
a)  Notify the Operations group to mount the backup cartridges.

b)  Set the default to the directory that contains the backup
    procedures:

**\$** SET DEF BACKPROCS

c)  Execute the backup procedure.

**\$** \@SUBMIT_RESTORE

Respond to the following prompts as shown in the brackets (\<\>):

What is the tape label of the first volume? \<P66770\>

Please respond to the following question with 'TEST', 'BENCH,' (and) or
'PROD.' \<PRODBENCHTEST\>

Enter a valid file number, or '\*' for all files. \<\*\>

d)  The backup proceeds. After it has completed, check the log file and
    verify that there were no errors.

```{=html}
<!-- -->
```
2.  Bring the database up- this may take a while. This command will make
    sure the database is not available to all users.

**\$**\@SADSTART PROD ONE

3.  Regenerate the P logs using ADAREC. An example session of this
    process follows. The following steps must be executed from the
    ADABAS account. For more information consult the ADABAS UTILITIES
    reference guide.

**\$** SET DEF DB007

**\$** DIR PLOG.DAT

Output:

Directory DISK\$PROJ10: \[ADABAS.DB007\]

PLOG.DAT;4292

PLOG.DAT;4291

\$ DEFINE RECIN PLOG.DAT;4291

**\$ ADAREC**

Output:

%ADAREC-I-STARTED

**ADAREC:** LIST=FULL

Output:

Protection log 2599

Block 1 - checkpoint SYNC - USERID ADANUC

Block 2 - checkpoint SYNX - USERID ADABCK DUMP DATABASE

Block 3 - checkpoint SYNP - USERID ADADBM DELCP (safely ignore)

82 modifications in file 1

13 modifications in file 38

**ADAREC:** EXIT

Output:

%ADAREC-I-STARTED

**ADAREC:** LIST=FULL

Protection log 2600

**ADAREC:** EXIT

**\$**

4.  Bring the database down and up.

**\$**SADSTOP PROD

**\$**\@SADSTART PROD ALL

5.  Verify the database came back up correctly and notify all users.

TDMS Accounts

This chapter will discuss howTDMS accounts and passwords are set up and
maintained by the DBA and Production Control Specialist

# Adding User Accounts

The DBA and the Production Control Specialist add TDMS user accounts and
set up users as NATURAL users. A TDMS account allows a user to login to
the NIEHS TDMS mainframe; however, no interaction with the database is
possible until the account is set up as a NATURAL user. See the *TDMS
Production Control Procedures* manual for detailed steps on how to add
TDMS user accounts and setup NATURAL users.

# Passwords and User ID

The DBA implements and maintains the ADABAS file and field level
password security for all databases. Read‑only access is granted for the
Production Database. Only OCTS, ASI, or employees who work with TDMS are
given read access. NTP employees and contractors may be given read
access with approval of the NTP Data Management Coordinator.

The DBA implements and maintains NATURAL password security for all
databases.

[APPENDIX A]{.underline}

# ADABAS FILE INFORMATION

### FORM NO. DBA-1-5/87

Complete form number DBA-1-5/87 to request a database file to be
defined.

[File Name]{.underline}

The name of the file may be up to 16 characters.

Example: TD_ANIMAL

[TEST DBID=1\<\> BENCHMARK DBID=5\<\> PRODUCTION DBID=7\<\>]{.underline}

Check the TEST box for initial file definition. A file must be defined
in the Test Database prior to a request for the file to be defined in
the Benchmark or Production databases.

[Number of Records to Load]{.underline}

This is the number of records to be initially loaded from a sequential
file. The file may be defined with zero records initially loaded.

[Filename of Load Data]{.underline}

This is the file name of a sequential file that contains the data to be
initially loaded to the file. The record layout must be the same as the
physical design of the file.

[Growth Rate]{.underline}

This is the estimated number of records to be added to the file in a
given time period.

[File Security]{.underline}

To protect a database file, the DBA assigns to the database file a read
protection level and/or an update protection level. The protected
database file and the password assigned to the database file work
together to allow a user oar a group of users access and /or protection
levels.

[Comments]{.underline}

Up to 30 character per line may be used to describe the file.

+-----------------------------------+-----------------------------------+
| ADABAS FILE INFORMATION           |                                   |
+-----------------------------------+-----------------------------------+
| Date:                             | Control #:                        |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\     | \_\_\_\_\_\_\_\_\_\_\             |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
+-----------------------------------+-----------------------------------+
| Originator:                       |                                   |
| \                                 |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+
| 1.  File Name:                    |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_\_\_\_  |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| TEST DBID=1\<\> BENCHMARK         |                                   |
| DBID=5\<\> PRODUCTION DBID=7\<\>  |                                   |
|                                   |                                   |
| 2.  Number of Records to Load:    |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| 3.  File Name of Loaded Data:     |                                   |
|     \_                            |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| 4.  Growth Rate:                  |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_\_      |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| 5.  File Security:                |                                   |
|                                   |                                   |
| Read Protected\<\> Update         |                                   |
| Protected \<\>                    |                                   |
|                                   |                                   |
| 6.  Comments:                     |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_\_\     |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+
| Approval Signatures:              |                                   |
|                                   |                                   |
| Technical Support Manager/DBA:    |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_        |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| Completed By:                     |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_      |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| Completion Date:                  |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_          |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+

#  ADABAS FIELD INFORMATION

### FORM NO. DBA-2-5/87

Complete form number DBA‑2‑5/87 along with DBA‑1‑5/87 when requesting a
database field to define. The fields should be listed in the desired
sequence that is determined by the results of the physical file design.

[File Name]{.underline}

This is the name of the file from the DBA‑1‑5/ 87 form.

[TEST DBID=1 \< \> BENCHMARK DBID=5 \< \> PRODUCTION DBID=7 \<
\>]{.underline}

Check the TEST box for initial file definition. A file must be defined
in the Test Database prior to a request for the file to be defined in
the Benchmark or Production databases.

[Field Type]{.underline}

This is a two character code that designates the field type:

**GR** ‑ for a group field

**MU** ‑ for a multiple value field

**PE** ‑ for a periodic group

**Blank** ‑ if none of the above apply

[Field Level]{.underline}

ADABAS level number assigned to the field. Example: the group PERSON
(field level 1) contains the fields NAME, FIRST‑NAME, INITIAL, and P‑DES
(which is itself a group consisting of the fields SEX, AGE,
FAMILY‑STATUS, and NUMBER‑OF‑DEPENDENTS). (Note: A periodic group (PE)
level definition must be level 1.)

[Field Code]{.underline}

This specifies the ADABAS two character field name. E1 ‑ E9 are not
allowed as ADABAS two character field names. Two character field names
that could be confused as syntax such as AT or B4 should also be
avoided.

[Field Name]{.underline}

This specifies the name of the field. A value from 3 to 32 characters
may be used. This name must be unique within a file. Fields that are a
logical connector to more than one file should have the same name.

[Format and Length]{.underline}

The field formats and their maximum field lengths for both the field
definition and the Data Definition Module (DDM) are:

  ----------------------------------- -----------------------------------
  **FORMAT**                          **MAXIMUM LENGTH**

  Alphanumeric (A)                    253 positions

  Packed (P)                          27 positions + sign

  Binary (B numeric)                  8 postions

  Binary (B non-numeric)              128 positions

  Flosting (F)                        8 postiions

  Unpacked (U)                        27 positions + sign

  Integer (I)                         8 positions

  Numeric (N)                         27 positions + sign
  ----------------------------------- -----------------------------------

The field definition and the data definition module format and length
are not necessarily the same for a field.

[Occurrences to Load]{.underline}

This is the number of occurrences in the input data to be initially
loaded for a multiple value field (up to 191) or a periodic group (up to
99).

Field Suppression

  ------------ --------------------------------------------------------------
  **NU-**      Indicates null value suppression for the field

  **FI-**      Indicates that the field is to occupy a fixed amount of
               storage with no suppression

  **Blank-**   Indicates normal suppression
  ------------ --------------------------------------------------------------

Index

  ------------ --------------------------------------------------------------
  **DE-**      The field is a desciptor

  **UQ-**      The field is a descriptor that contains an unique value in the
               file; ADABAS will not allow duplicate values in the files.

  **SB-**      The field is a subdescriptor

  **SP-**      The field is a superdescriptor

  **PH-**      The field is a phonetic descriptor

  **Blank-**   If none of the above apply
  ------------ --------------------------------------------------------------

[Heading text]{.underline}

Default heading text to be used when displaying the field in NATURAL.

[Edit mask]{.underline}

This signifies how numeric fields are to be edited when displayed in
NATURAL.

  ----------- --------------------------------------------------------------
  **Z-**      Suppress leading zeros up to the decimal \$

  **Blank**   No editing
  ----------- --------------------------------------------------------------

<table style="width:100%;">
<colgroup>
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 7%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="14">ADABAS FIELD INFORMATION</td>
</tr>
<tr class="even">
<td colspan="7"><p>Date: _______________________________</p>
<p>Originator: ___________________________</p></td>
<td colspan="7">Control #: ___________________________</td>
</tr>
<tr class="odd">
<td colspan="14"><ol type="1">
<li><p>File Name:
_______________________________________________________________</p></li>
</ol>
<p>TEST DBID=1&lt;&gt; BENCHMARK DBID=5&lt;&gt; PRODUCTION
DBID=7&lt;&gt;</p></td>
</tr>
<tr class="even">
<td>Type</td>
<td>Level</td>
<td>Code</td>
<td>Field Name</td>
<td>Frmt</td>
<td>Lnght</td>
<td colspan="2">Occ</td>
<td>Supp</td>
<td>Index</td>
<td>Frmt</td>
<td>Lnght</td>
<td>Heading</td>
<td>Mask</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="14"></td>
</tr>
<tr class="odd">
<td colspan="14"><p>Approval Signatures:</p>
<p>Technical Support Manager/DBA:
_______________________________________________</p>
<p>Completed By: ___________________________________________</p>
<p>Completion Date: _________________________________________</p></td>
</tr>
</tbody>
</table>

# NATURAL USER ID ASSIGNMENT

### FORM NO. DBA-3-5/87

Form DBA‑3‑5/87 is completed and given to the DBA when an entity
requires a NATURAL parameter file. Entity is used here instead of User
ID because it is possible for more than one user to use a NATURAL user
ID.

[Entity name]{.underline}

This is a generic name or the user\'s VMS user ID. For example: ALPHA.

[Responsible Person]{.underline}

Person responsible for the distribution and use of NATURAL user ID.

[Database Read/Update Criteria]{.underline}

For each NATURAL user ID the DBA can assign Database Read and/or Update
privilege.

[Read]{.underline}

Check this space if the NATURAL user ID requires read only access.

[Update]{.underline} ­

Check this space if the NATURAL user ID requires update access.

[TEST DBID=1 \< \> BENCHMARK DBID=5 \< \> PRODUCTION DBID=7 \<
\>]{.underline}

Check the correct box for database identification.

+-----------------------------------+-----------------------------------+
| NATURAL USER ID ASSIGNMENT        |                                   |
+-----------------------------------+-----------------------------------+
| Date:                             | Control #:                        |
| \_\_\_\_\_\_\_\_\_\_\_\           | \_\_\_\_\_\_\_\                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
|                                   |                                   |
| Originator:                       |                                   |
| \_\_\_\_\_\_\_\                   |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+
| 1.  Entity Name:                  |                                   |
|                                   |                                   |
|  \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| 2.  Responsible Person:           |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_        |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| 3.  Read \<\> Update \<\>         |                                   |
|                                   |                                   |
| 4.  TEST DBID=1\<\> BENCHMARK     |                                   |
|     DBID=5\<\> PRODUCTION         |                                   |
|     DBID=7\<\>                    |                                   |
+-----------------------------------+-----------------------------------+
| Approval Signatures:              |                                   |
|                                   |                                   |
| Technical Support Manger/DBA:     |                                   |
| \_\_\_\_                          |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| NTP Data Management Coordinator:  |                                   |
| \_                                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| (If applicable)                   |                                   |
|                                   |                                   |
| Completed By:                     |                                   |
| \_\_\                             |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| Completion Date:                  |                                   |
| \                                 |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+

# DATA DEFINITION MODULE FORM

### FORM NO. DBA-4-5/87

[TEST DBID=1\<\> BENCHMARK DBID=5\<\> PRODUCTION DBID=7\<\>]{.underline}

Check the correct box for database identification.

**[DELETE A FILE]{.underline}**

When a file is to be deleted from the Test, Benchmark or Production
Databases, the requester submits the request on form DBA.

[File Name or Number]{.underline}

This is the file name or file number to be deleted.

**[FILE MODIFICATION]{.underline}**

[Modification Description]{.underline}

Submit a DBA‑4‑5/87 Form to the DBA when a file requires modification.
The request is made to the current Data Definition Module. For example:
if a field is to be inserted in an existing file indicate where to
insert on the Data Dictionary. Attach either the current DDM or form
DBA‑2‑5/87.

[File Name or Number]{.underline}

This is the file name or number to be modified.

**[FIELD MODIFICATION]{.underline}**

Submit a DBA‑4‑5/87 Form to the DBA when a field requires modification.
The request is made to the current Data Definition Module.

[File Name or Number]{.underline}

This is the file name or number that contains the field to be modified.

[Field Name]{.underline}

The name of the field being modified.

[Field Location]{.underline}

Attach either the current DDM or Form DBA­2‑5/B7.

+-----------------------------------+-----------------------------------+
| DATA DEFINITION MODULE FORM       |                                   |
+-----------------------------------+-----------------------------------+
| Date:                             | Control #:                        |
| \_\_\_\_\_\_\_\_\_\_\_\           | \_\_\_\_\_\_\_\                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |
|                                   |                                   |
| Originator:                       |                                   |
| \_\_\_\_\_\_\_\                   |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+
| 1.  TEST DBID=1\<\> BENCHMARK     |                                   |
|     DBID=5\<\> PRODUCTION         |                                   |
|     DBID=7\<\>                    |                                   |
|                                   |                                   |
| 2.  File Delete                   |                                   |
|                                   |                                   |
| ```{=html}                        |                                   |
| <!-- -->                          |                                   |
| ```                               |                                   |
| a)  File Name or Number:          |                                   |
|     \_\_\_\_\_                    |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| ```{=html}                        |                                   |
| <!-- -->                          |                                   |
| ```                               |                                   |
| 3.  File Modification             |                                   |
|                                   |                                   |
| ```{=html}                        |                                   |
| <!-- -->                          |                                   |
| ```                               |                                   |
| a)  File Name or Number:          |                                   |
|     \_\_\_\_\_                    |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| b)  Modification Description      |                                   |
|     (attach copy of DBA-2-5/87)   |                                   |
|                                   |                                   |
| ```{=html}                        |                                   |
| <!-- -->                          |                                   |
| ```                               |                                   |
| 4.  Field Information             |                                   |
|                                   |                                   |
| ```{=html}                        |                                   |
| <!-- -->                          |                                   |
| ```                               |                                   |
| a)  File Name:                    |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_\_\_\_  |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| b)  Field Name:                   |                                   |
|     \_\_\_\_\_\_\_\_\_\_\_\_\_    |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| c)  Field Location (attach copy   |                                   |
|     of DBA-2-5/87)                |                                   |
+-----------------------------------+-----------------------------------+
| Approval Signatures:              |                                   |
|                                   |                                   |
| Technical Support Manger/DBA:     |                                   |
| \_\_\_\_\_\_\_\_\_                |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| Completed By:                     |                                   |
| \_\_\_\_\_\_\_\                   |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
|                                   |                                   |
| Completion Date:                  |                                   |
| \_\_\_\_\_\                       |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
| \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                                   |
| _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                                   |
+-----------------------------------+-----------------------------------+