PAPERWORK REDUCTION ACT
   MANAGEMENT SYSTEM II

SYSTEM ADMINISTRATOR MANUAL
                    TIDE*
                       •   CoroorationV

-------
    PAPERWORK REDUCTION ACT
     MANAGEMENT SYSTEM II

  SYSTEM ADMINISTRATOR MANUAL
         PREPARED FOR:
   INFORMATION POLICY BRANCH
ENVIRONMENTAL PROTECTION AGENCY
       401  M STREET,  S.W.
    WASHINGTON,  D.C.  20460
          PREPARED BY:
       COMPEX CORPORATION
5500 CHEROKEE AVENUE, SUITE 550
   ALEXANDRIA,  VIRGINIA 22312

     CONTRACT #  68-01-7444
       DELIVERY ORDER # 6
        DECEMBER 27,  1989

-------
                        TABLE OF CONTENTS

1.0  INTRODUCTION 	   1
     1.1  Overview	   1
     1.2  Conventions 	   1

2.0   SYSTEM ADMINISTRATION within PRAMS II 	   2
     2. l   Adding or Updating a User	   3
          2.1.1   Adding a New User	   3
          2.1.2   Modifying the User Table	   4
     2.2   Updating System Tables 	   5
     2.3   Updating the AA/Division Table 	   5
     2.4   Updating the Agencies Table  	   7
     2.5   Updating the Events Table  	   9
     2.6   Archiving Records  	   10
     2.7   Backup/Export Data Files	12
     2.8   Restore Data Files	13

3.0  SYSTEM ADMINISTRATION external to PRAMS II  	   15
     3.1  Print Reports from Disk Files	15
          3.1.1  Print Report Files from Hard Disk	15
          3.1.2  Print Report Files from Floppy  Disk   ....   16
     3.2  Recover from System Failure 	   17
     3.3  Print SF-83 Data for All ICRs	18

INDEX

APPENDIX A

APPENDIX B

-------
                         LIST OF FIGURES
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
System Administration Menu
Add A New User	,
AA/Div Table  	 ,
Edit Agencies Table . .  . ,
Event Codes Table . . .  . ,
                              	   2
                              	   4
                              	   6
                              	   8
                              	   9
Backup Caution Message  	   12

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL




1.0  INTRODUCTION

1.1  Overview

This manual is for the  administration  of  the Paperwork Reduction
Act Managements System  II  (PRAMS II).   It should be used only by
personnel designated as System Administrator and with a PRAMS II
security level which allows write access to all files.

This document covers all aspects of  system  administration including
the following:

          o    Table Maintenance

          o    Archiving records

          o    Exporting databases

          o    Backup/Restore data

          o    Print reports from disk  files

          o    Recover  from system failure

          o    Dump SF-83  data for all  ICRs  to printer

The  first four items listed above are an  integrated  part of  PRAMS
II  and may  be  accessed through the system  menus by authorized
users.  The last three  functions are performed outside of PRAMS II
in the  DOS environment.

1.2  Conventions

The conventions used in this manual,  and those related to the  PRAMS
II operational environment, are listed in the first section of the
PRAMS   II  User  Manual.    Please   refer  to  this  document for
clarification of terminology.
 December 27,  1989   ver 1.1                                 Page 1

-------
    PRAMS II                              SYSTEM ADMINISTRATOR MANUAL



    2.0   SYSTEM ADMINISTRATION within PRAMS II

    The System Administration functions allow authorized users to:

         (1)  add/update the user table

         (2)  update the system tables

         (3)  archive records

         (4)  backup/export data files

         (5)  export data to dbase

         (6)  restore data files.

    The SYSTEM ADMIN MENU is accessed through the PRAMS II MAIN MENU.
 Screen 1.5              PAPERWORK  REDUCTION  ACT             Ver. 1.0
                           MANAGEMENT  SYSTEM  II
                        **  SYSTEM ADMIN MENU  **
                       1   ADD/UPDATE USER TABLE
                       2   UPDATE SYSTEM TABLES
                       3   ARCHIVE RECORDS
                       4   BACKUP/EXPORT DATA FILES
                       5   EXPORT TO  DBASE  III
                       6   RESTORE DATA FILES
                       R   RETURN TO MAIN MENU
Add a new User or Edit old User Profile - User ID,Password,Access Level,etc
                                 Figure 1
                        System Administration Menu
     December 27,  1989   Ver 1.1                                 Page 2

-------
PRAMS II
                                 SYSTEM ADMINISTRATOR MANUAL
2.1   Adding or Updating a User

The System Administrator has the ability  to  add new users or
to update passwords or security levels of existing users.
steps

2.1.1
   Adding a New User

1.   From the MAIN MENU select SYSTEM ADMINISTRATION.

2.   From the  SYSTEM  ADMIN MENU select  ADD/UPDATE  USER
     TABLE.

3.   At the prompt, type  to add a new user.

4.   Fill in the information requested:
       (see Figure 2 on following page)
          User ID:
          Password:
           User  Name:
           Security:
                 This is restricted to 10 characters. It
                 is  recommended  that the  person's  full
                 name or first initial  and last name be
                 used.

                 The  password can  be  a  maximum of 10
                 characters  (numbers or letters).   The
                 password  does  not  have  to be  a word;
                 however,  it  is  recommended   that  the
                 password selected is one which the user
                 will be able to remember.  For security
                 purposes,  the password does  not appear
                 on the screen when  entered at  login.

                 Input the user's  name  here.  This field
                 may contain up to 25 characters.
                 Enter  the   level   of
                 assigned to this user.
security  being
                          0    Read  only  access
                          1    Read  and write  access.
 *NOTE;     Only the System Administrator  should be granted  a
           security level  of  1;  all  others must  be  0.   The
 December 27,  1989  Ver 1.1
                                                       Page  3

-------
PRAMS II
                            SYSTEM ADMINISTRATOR MANUAL
     5.
password for the System Administrator must be kept
from general distribution to maintain data integrity.

When prompted,  press  to add additional new users;
Press  to return to the SYSTEM ADMIN MENU.
Screen 1.5. la PAPERWORK REDUCTION ACT Page 1 of 1


* NEW USER INPUT *
User ID: [ ]
Password: [ ]
User Name: [ ]
Security: [0]



                             Figure  2
                          Add A New  User
 2.1.2   Modifying the User Table

     1.   From  the MAIN MENU select SYSTEM ADMINISTRATION.

     2.   From  the  SYSTEM ADMIN MENU  select ADD/UPDATE USER
          TABLE.

     3.   At  the prompt,  type  to modify  a user profile.

     4.   Enter the  user  ID for the profile  to be modified.
 December 27,  1989   ver 1.1
                                                  Page 4

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
     5.    The information displayed on the screen corresponds
          with the data entered when the user was initial added
          to the system:

          (1)  User ID

          (2)  Password

          (3)  User Name

          (4)  Security.

          Any of this information can  be changed by the System
          Administrator.

The security function and the maintenance  of the User Table is
crucial to PRAMS II data integrity.  Copies of the system are
available to all  Desk Officers  for personal use in verifying
the status of  their  ICRs.   The  Desk Officers must be entered
into  the  system  with a  security level  of zero  to prevent
"write" access to the data files.  Only the PRAMS II software
residing  on   the  System  Administrator's  PC  should  have
modifiable databases.


2.2   Updating System Tables

Certain "look-up"  tables used in  PRAMS II  can be updated by
the System  Administrator in  order to provide for additional
options and codes.  By selecting UPDATE SYSTEM TABLES  from the
SYSTEM ADMIN MENU, the System Administrator may update:

      (1)  the  AA/Division Table;

      (2)  the  Agencies Table; and

      (3)  the  Events  Table.


2.3   Updating the AA/Division  Table

Accessing this option from the TABLE SELECTION menu allows the
System  Administrator  to add  additional  AA  Codes,  division
codes, office  abbreviations,  mail codes,  and  descriptive text
 for  these codes.  In Version 1.0, PRAMS  II does not  utilize
 December 27,  1989   Ver 1.1                                 Page 5

-------
    PRAMS II
                  SYSTEM ADMINISTRATOR MANUAL
    this table  for any specific  purpose.   The addition  of this
    table is in conformance to the original PRAMS databases.
    Steps
         1.   From the MAIN MENU select SYSTEM ADMINISTRATION.

         2.   From  the SYSTEM  ADMIN MENU  select UPDATE  SYSTEM
              TABLES.

         3.   From  the   TABLE  SELECTION  menu   select  UPDATE
              AA/DIVISION TABLE.

         4.   The screen  for  updating the AA/Division codes will
              appear,  (see Figure 3 on following page)  Visible on
              the screen will be four columns: AA_CODE,  DIV_CODE,
              OFFICE  and  MAIL_CODE.   Use the  right  arrow key to
              scroll   to   the  right   to   view   the   OD_NAME
              (office/division name) field.  Use the left  arrow key
              to move  back.
Screen 1.5.2.1
PAPERWORK  REDUCTION  ACT
               Page  1 of 1
  FILE: AA/DIV.DBF
                              Help     Exit
                 AA CODE
   DIV CODE   OFFICE
                                                 Record 1/136
MAIL CODE
1


1


1
1


1
A
A
AR
AR
AR
AR
AR
AR
AR
10
20
1
2
3
10
11
21
22
OCR
OSDBU
OAR
OAR
OAR
OAQPS
OAQPS
OMS
QMS
A105
A149C
ANR443
ANR443
ANR445
MD10
MD15


i I i
                                 Figure 3
                               AA/Div Table
     December 27,  1989  ver 1.1
                                        Page  6

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
          The up and down arrow keys may also be used to scroll
          through this list.

          To edit the table, move the  cursor  to  the field to
          be edited and begin to type.

          To delete a  record,  press the   key;  pressing
          the  key a second time will  recall ("un-delete")
          the  record.    The  record  will  be  "marked  for
          deletion";  it will be deleted from the screen. When
          the modifications are completed  the database will be
          packed and  these record will  be  permanently removed.
          To add a new record,  move the cursor to the end of
          the file and press the down arrow key (or press the
           key to move to the end of the file, one page
          at a time).  A blank line will  be displayed and the
          "" indicator will be  displayed  next to the word
          "record".  Enter the new  record.

          Online help is available  by pressing .

     5.   To end the updating process, press .  A prompt
          will  appear  asking if all modifications  have been
          made.  Press   to save the changes/modifications
          and  return  to   the  previous  menu; press    to
          continue with the editing process.


2.4    Updating  the Agencies Table

When entering data into the PRAMS II system, agency codes are
used  to indicate  the  agency  from  which  the  applicable form
originated.  When reports are generated from the system, these
codes  are  replaced with the  name of the  agency.   In order to
add  new  agencies,  or  modify  existing  agencies  within the
system,  the  System  Administrator  can  utilize  the  UPDATE
AGENCIES TABLE  function.

Steps

      1.    From  the MAIN MENU  select SYSTEM  ADMINISTRATION.

      2.    Select UPDATE SYSTEM  TABLES  from the  SYSTEM ADMIN
           MENU.
 December 27, 1989  Ver 1.1                                  Page 7

-------
   PRAMS II
                 SYSTEM ADMINISTRATOR MANUAL
        3.   Select UPDATE AGENCIES TABLE from the TABLE SELECTION
             menu.
Screen 1.5.2.1
PAPERWORK  REDUCTION  ACT

FILE: AGENCIES. DBF











 Help  Exit
Record 1/10
AGENCYCODE AGENCYNAME
0
10
20
30
40
50
60
70
80
90
This
This
THis
THis
This
This
THis
This
This
This
is
is
is
is
is
is
is
is
is
is
the
the
the
the
the
the
the
the
the
the
Title
Title
title
title
title
title
title
title
title
title
for
for
for
for
for
for
for
for
for
for
code
CODE
CODE
CODE
CODE
CODE
CODE
CODE
CODE
CODE
00
10
20
30
40
50
60
70
80
90

                                Figure 4
                           Edit  Agencies  Table
         4.    A listing will appear on the screen with the agency
              codes (and their names)  that are currently  in  the
              system.  (See  Figure 4 above)  These codes, and their
              corresponding names, may be modified and  new ones may
              be added.

              To move  throughout this  listing, use the arrow keys.

              For specifics regarding editing this table,  see the
              discussion on UPDATING THE AA/DIVISION TABLE.

              Online help is available by pressing .
    December 27, 1989  Ver 1.1
                                       Page 8

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
          When finished with the updating process, press .
          A prompt will appear asking if all modifications have
          been    made.        Press        to   save    the
          changes/modifications and  return  to the  previous
          menu; press  to continue with the editing process.
2.5   Updating the Events Table

Unlike the AA/Oivision and Agencies tables, updating the Events
Table has ramifications  beyond report listings.   The Events
Table is  used to verify  all  event codes used  when Tracking
Events are entered.  Therefore, if new Event Codes are entered,
and incorrectly input,  or existing  Event Codes are erroneously
modified or deleted, the effects will trickle-down throughout
the database and cause problems when Tracking  Events are added.
Therefore, it is imperative that caution be used when editing
this  table  and  that  all changes  are  verified  prior  to
continuing with routine data entry.

Steps

     1.   From the MAIN MENU select SYSTEM ADMINISTRATION.

     2.   From  the SYSTEM ADMIN  MENU  select  UPDATE EVENTS
          TABLES.

     3.   The  screen  will appear  with the  listing  of the
          system's  current event codes  and  their name.  Edit
          this   list   in   the  same   manner  as  editing  the
          AA/DIVISION TABLE and  the AGENCIES TABLE  (see  steps
          above).

          Online help  is  available by pressing  .

     4.   When finished with the  updating process,  press .
          A prompt will appear asking  if all modifications have
          been    made.       Press       to    save   the
          changes/modifications  and  return  to  the  previous
          menu; press  to continue  with the editing process.
 December 27,  1989  Ver 1.1                                 Page 9

-------
     PRAMS II
                        SYSTEM ADMINISTRATOR MANUAL
Screen 1.5.2.1
     PAPERWORK  REDUCTION  ACT
Page 1 of 1
  FILE: EVENTS.DBF
                                  Help   Exit
      EVENT CODE   EVENT NAME
                                                 Record 1/16
      AD
      CR
      CS
      DD
      DI
      HR
      II
      10
      IS
      OA
      OD
      PO
      RP
      SD
OMB approval date
Correction received from OMB
Correction Sent to OMB
To Division Director
Deleted by program
Hold for rule
In IPB
In OMB
Informal submission to OMB
Out of OMB - approved
Out of OMB - Disapproved
Resubmitted by Program
Returned to Program
Signed by Director
                                  Figure 5
                              Event  Codes Table
      2.6   Archiving Records

      In order to keep the  number of records within PRAMS  II  at a
      level which is  manageable  (and thus keeping system access time
      minimal),   an  archive  procedure is  available to store  old
      records.

      Conditions for archiving an ICR must be handled  on a case by
      case  basis.    The  ICR  should  only  be archived  when it  is
      determined that the related ICR data will no longer be required
      in the active  PRAMS  II environment.   Archiving  affects all
      records  (package,   tracking  events,  OMB  responses,  etc.)
      associated with a given ICR number.

      The archive process  writes the  selected records to a dBASE III
      files.   Before using  these files  in  dBASE  III,  review the
      database  structures  for  the  "ARC  " files as  listed  in the
      December 27, 1989  Ver l.l
                                             Page 10

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
Appendix on  Database File Structures.  Once an ICR is archived
the data nay only be utilized through dBASE III.  The records
may be viewed by using the  "browse"  function  in dBASE III on
the database files which are prefixed with "ARC_".

NOTE:   Archived data  cannot be  restored to  PRAMS  II   (see
Backup/Export Data Files).

When using the archive procedure, the option is given to delete
the select record(s)  from the database.  If the records are not
deleted, the archive will serve  primarily as a backup.  If the
records are deleted from  the database, then the archive becomes
the only electronic record of this ICRs.

Steps

     1.    From the MAIN  MENU select  SYSTEM ADMINISTRATION.

     2.    Select ARCHIVE RECORDS from  the SYSTEM ADMIN MENU.

     3.    A prompt will appear requesting an ICR number.  Enter
           the number for the ICR which to be archived.
 December 27, 1989  ver 1.1                                Page 11

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
     4.   After entering a number, the system will verify that
          the ICR number currently exists in the system.
          If an invalid ICR number has been entered, an error
          message will appear stating that the number entered
          is not  in  the database.   Press   to  enter a new
          number; press  to return to the previous menu.
          If a valid number has been entered, the system will
          verify that the number selected is to be archive.


2.7   Backup/Export Data Files

Backups of the database can be made by using the Backup/Export
Data Files menu option.  Backups are made to floppy diskettes
and can  be  used (1)  for distribution of  the current data to
other users of  the PRAMS II system  or (2) for backup purpose
to  guard  against   unforseen   problems  with   the  System
Administrator's computer.

NOTE:     Backup  and  archive  do  not   accomplish   the  same
          function.   Backups are made onto  floppy  disks  and
          can be  restored  to  PRAMS II.

Steps

     1.   From  the MAIN MENU  select SYSTEM ADMINISTRATION.

     2.   From  the SYSTEM ADMIN MENU select BACKUP/EXPORT DATA
          FILES.

     3.   A   caution  message  will  appear  on  the   screen
          explaining the process of the backup/export function.
           (see  Figure  6 on following page).

          Before  beginning,  be  sure to have  a  number of  high-
          density, formatted floppy disks for  this  procedure.

          If  enough  disks  are  not  available to  complete  the
          backup  procedure:

           (1)   get more disks and,  if not already  formatted,
                format them on another computer;  or

           (2)   when  prompted for a new disk,  press 
                to abort the process.
 December 27, 1989  ver l.l                                Page 12

-------
   PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
             The  data  backed-up  during  this  process  can be
             restored onto  another system on which PRAMS  II  has
             been installed  (see steps below).
           BACKUP  &  EXPORT   DATA   FILES

THIS SELECTION WILL ALLOW THE SYSTEM ADMINISTRATOR TO WRITE THE PRAMS
DATA FILES OUT TO A SERIES OF FLOPPY DISKS FOR EITHER BACKUP STORAGE
OR EXPORT TO A DESK OFFICER'S PC WHERE THE FILES MAY BE RESTORED AND
VIEWED WITH DBASE III.

             ******  CAUTION  ******
THIS PROCESS UTILIZES THE DOS "BACKUP" ROUTINE.  THE ADMINISTRATOR
MUST HAVE A SUFFICIENT NUMBER OF HIGH-DENSITY,FORMATTED FLOPPY DISKS
READY AND AVAILABLE BEFORE THIS PROCESS IS EXECUTED.

IF THE NUMBER OF AVAILABLE FORMATTED DISKS IS INSUFFICIENT FOR THE
DATA EXTRACTION, THERE ARE TWO OPTIONS: (1) GET MORE DISKS & PREPARE
THEM ON ANOTHER MACHINE  (THE SYSTEM WILL PAUSE AND WAIT FOR YOU) ;
(2) AT THE PROMPT FOR THE NEXT DISK, PRESS  and  AT THE SAME
TIME (THIS WILL ABORT THE PROCESS. YOU WILL HAVE TO RESTART FROM THE
BEGINNING).

THE DATA FILES ON THE FLOPPIES MAY BE RESTORED TO THIS OR ANY OTHER
PC-DOS SYSTEM BY ISSUING THE DOS COMMAND "RESTORE"  (WITH PARAMETERS)
FROM THE COMMAND LINE.  REFER TO PRAMS2 USER MANUAL FOR MORE DETAILS.


                                Figure 6
                         Backup caution Message
    2.8   Restore Data Files

    The backed-up data  files made from PRAMS  II  (see directions
    above)  can  be restored  to  any PRAMS  II system  through the
    RESTORE DATA  FILES  menu  option.   This option  is  used by the
    System Administrator  to update the  users' systems  with the
    latest version of the database files.  This process should be
    December 27, 1989  Ver 1.1                                Page 13

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
done on  a regular basis  to maintain  current data  for Desk
Officer status queries.   (See section on maintaining Read Only
systems for details on this process.)

Steps

     1.   From the MAIN MENU select SYSTEM ADMINISTRATION.

     2.   Select RESTORE DATA FILES from the SYSTEM ADMIN MENU.

     3.   A  caution  message  will   appear  on  the   screen
          explaining  the  restore  process.   Press   to
          remove the message from the screen.

          A prompt will appear,  giving the option to proceed
          with the restore.   Press  to  continue (BE SURE TO
          HAVE THE BACK-UP DISKETTES AVAILABLE; PLACE THE FIRST
          DISKETTE INTO THE A: DRIVE).

          Press  to return to the previous menu.
 December 27,  1989  Ver l.l                                Page 14

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL



3.0  SYSTEM ADMINISTRATION external to PRAMS II

3.1  Print Reports from Disk Files

When generating reports (see User Manual:Generating Reports),
an option is provided to write the  report  to a disk file for
printing at a later time.  This is the recommended approach to
report generation to the savings  in  time  and the avoidance for
system  failure due  to  printer  malfunction.    The  following
outlines  the  procedures  for printing  a  report  that  was
previously written to disk.

*NOTE;    This operation is performed outside of the PRAMS II
          system.   All  steps are  done  from  the  DOS command
          line.

3.1.1  Print Report  Files from Hard Disk

Steps

     1.   After  all  operations are  completed within PRAMS II
          and reports have been written to file, exit PRAMS II.

     2.   Change  to the REPORTS sub-directory by typing "cd
          reports".

     3.   To verify the existence  of report  files, type "dir
          *.prn".  All reports written to disk files are given
          the  extension ".PRN".

     4.   Make sure that the  default printer  on the  system  is
          the  same as that selected when generating the reports
          and  it is on-line and  ready.

      5.   Type "print "  where filename is the name
          assigned to the file  during  the report  generation
          process.   To  print all  report  files,  simply type
          "print *.PRN".

      6.   If this is the first report printed in  this manner,
          DOS  will prompt for the print driver. Press the Enter
          key  for the default, LPT1.

      7.   After  the report has printed  successfully, you may
          want to delete the  print  file  from the  REPORTS  sub-
          directory. To do this, type "del ",  where


 December 27,  1989Ver  1.1Page 15

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL



          filename is the name of the file to delete.

     8.   To return to the PRAMS II directory, type "cd .."

It  is  recommended  that  the  report  file  be deleted  after
printing to conserve free disk space.
3.1.2  Print Report Files from Floppy Disk

On occasion, it may be desirable to transfer the report files
to a floppy disk and print the reports from another PC.
Steps
     1.   After all  operations  are  completed within PRAMS II
          and reports have been written to file, exit PRAMS II.

     2.   Change  to  the REPORTS sub-directory by typing "cd
          reports".

     3.   To verify  the existence  of report files,  type "dir
          *.prn".  All reports written to disk  files  are given
          the extension ".PRN".

     4.   Insert  a formatted  floppy disk into the  "A" drive.
           (This is the  top  floppy disk drive on most PCs.)

     5.   Type  "copy  a:*.*" where  filename is the
          name of  the report file you wish to print on another
          PC.   If you are going to print all  report files in
          the REPORTS sub-directory, use "*.PRN" for filename.

     6.   When  the  DOS  prompt  returns and  the  light  on the
           floppy  drive  goes out, remove the disk.   You may now
          take the disk to the PC from which you will print the
          reports.

     7.   Make  sure  that the  default printer on the system is
          the same as that selected when generating the reports
          and  it  is  on-line and ready.

     8.    Place the  disk with the copied report files into the
           "A"  drive.

     9.    Type  "print a:" where filename is the name
           assigned  to  the  file during the  report generation
 December 27, 1989  Ver l.l                                Page 16

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
          process.   To print all  report files,  simply type
          "print A:*.PRN".

     10.  If this is the first report printed in this manner,
          DOS will prompt  for the print driver. Press the Enter
          key for the default, LPT1.

    *NOTE:     Do NOT  remove  the floppy disk from drive "A"
               until all printing is complete.

     11.  If  the   printer  should  run  out   of  paper  or
          malfunction, you may correct the error and the print
          job will resume.  This is the prime benefit of using
          this  method  to  print  reports.  Once   all  report
          printing  is completed, you may remove the floppy.


3.2  Recover from System Failure

There exists the possibility that at some point in time PRAMS
II may undergo a system failure.  This would be the result of
a loss  in power  during an operation  in which the  database is
open.   Another  possible cause may be  a  hard  disk crash.  In
either  case, the  System  Administrator  must  follow certain
recovery procedures.

In the  case  of  a system power failure or an unforseen  system
program execution  failure  from which the user must reboot the
PC to regain control, all database files  should  remain intact.
Only the  index  files will sustain damage.  Therefore, it will
be  necessary to  rebuild  all index  files  before  re-entering
PRAMS II.  This  is  accomplished  by the following  procedures.
 Steps
      1.    Exit  PRAMS II,  if  you are not  already at the  DOS
           command line.

      2.    If  it was necessary to reboot, change to the ALLPRAMS
           directory by  typing "cd  \ALLPRAMS".

      3.    To   invoke   the   index   building  program,   type
           "reindall".

      4.    The system  will  begin  re-indexing  all  PRAMS  II
           databases.  The procedure  will  take approximately 7
 December 27,  1989  Ver 1.1                                Page 17

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
          minutes.   To verify operation, note  the flickering
          of the red "hard disk access" light on the front of
          the PC.

     5.   When the  operation is completed, the DOS prompt will
          return and  the  red  light  will  cease  flickering.
          PRAMS II  may now be restarted in the usual manner.

If a hard  disk failure should  occur, all data  will be lost.
It will be necessary  to restore all datafiles  from the most
recent system  backup,  (see details on backup  and restore in
section 2.0 above.)
3.3  Print SF-83 Data for All ICRs

During the transition from  the  old  PRAMS  to PRAMS II, it may
be  necessary  to print the  data  for all ICRs  in  PRAMS II to
verify accuracy of the data.
Steps
      1.   Exit  PRAMS  II,  if you  are not already  at the  DOS
          prompt.

      2.   Verify  that  the   printer  is  on-line  and  has  an
          adequate  supply  of  paper.   (This   operation  will
          consume a significant volume of paper).

      3.   From  the ALLPRAMS  directory type "dumpier".

      4.   The program  will  execute and print  each ICR.   The
          first 2 pages will  contain the most recent SF-83 data
          and the  ICR  Summary  totals,  if any.   The  following
          pages will contain a  listing of any  tracking events
          associated with the ICR.

      5.   The DOS prompt will return when the task is complete.
 December 27,  1989   ver 1.1                                Page 18

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
                            INDEX
     AA/Division Table
          example of	6
          system administration and 	 5
          updating  	 5
     Agencies Table
          example of	8
          system administration and 	 5
          updating  	 7
     Archiving Records  	   10
          data base structure of	10
          using the data	10
     Backup of data	11
     Event Codes
          example of editing the table   	 9
          system administration and 	 5
          updating  	 9
     Export of data	11
     Password
          adding   	 3
     Restoring Data Files	12
     Security
          levels of	3
     System Administration
          AA/Division Table  	 5
          AA/Division Table, updating  	 5
          adding a password  	 3
          adding a user	3
          adding a user ID	3
          adding user name	3
          Agencies Table and   	 5
          Agencies Table,  updating  	 7
          Archiving Records  	   10
          backing-up data  files	11
          Event Codes and	5
          Event Codes, updating  	 9
          exporting data  files	11
           functions  	  2
           look-up  tables   	  5
          modifying a user profile  	  4
           restoring data  files	12
           security levels  	  3
           updating a  user  profile	3
 December 27, 1989  Ver l.l                                Page 19

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
          updating tables 	  5
     User ID
          adding  	  3
          modifying 	  4
     User Name
          adding  	  3
 December 27,  1989   Ver  1.1                                Page 20

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
                          APPENDIX A




                     DATABASE STRUCTURES
 December 27, 1989  ver l.l                                Page 21

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
                     DATABASE STRUCTURES
There are a total of 15 databases in the PRAMS  II

   PACKAGE.DBF
   TRACKING.DBF
   EVENTS.DBF
   ICR.DBF
   ICW.DBF
   ICB_PROF.DBF
   AGENCIES.DBF
   SYSTEM.DBF
   TRAKTEMP.DBF
   AADIV.DBF
   ARC_ICR.DBF
   ARC_PKG.DBF
   ARC_ICB.DBF
   ARC_ICW.DBF
   ARC TRK.DBF
There are  14 associated  index  files:

    PACKAGEl.NDX
    PACKAGE2.NDX
    TRAKICR.NDX
    TRAKPKG.NDX
    TRAKDATE.NDX
    ICRINDEX.NDX
    ICRAGNCY.NDX
    ICROMBAG.NDX
    ICW_ICR.NDX
    ICB.NDX
    TTMPDATE.NDX
    AGENCIES.NDX
    ICW  DATE.NDX
 December 27,  1989  Ver 1.1                                Page 22

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
There are 12 nemo files associated with the databases,

   ICR.DBT
   PACKAGE.DBT
   ICB_PROF.DBT
   ICW.DBT
   TRACKING.DBT
   ACR_ICR.DBT
   ARC_PKG.DBT
   ARC_ICW.DBT
   ARC_ICB.DBT
   ARC TRK.DBT
The  following  pages  provide  detailed  database structures,
index  associations,  and index keys  for  each database in  the
PRAMS2 system.
 December 27,  1989  Ver 1.1                                Page 23

-------
PRAMS II
                                      SYSTEM ADMINISTRATOR MANUAL
Structure for database : PACKAGE. DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Field name
ICR NUMBER
PKG_NUMBER
TTL RECHRS
TTL HOURS
TTL RESPON
ADJUSTMENT
PGM CHANGE
TAB DIFFER
CUR OMB IN
REQ BURDEN
REC RETENT
HR PER KPR
NO REC KPR
HR PER RSP
PER RSPOND
NO RESPDNT
STAT FLAG
ED FLAG
REQ X DATE
REVIEW TYP
FR DATE
COLECT TYP
PKG ABSTRC
OTHER AUTH
USC CHAPTR
USC TITLE
AFFECTPUB7
AFFECTPUB6
AFFECTPUB5
AFFECTPUB4
AFFECTPUB3
AFFECTPUB2
AFFECTPUB1
POC MAIL
POC PHONE
POC FIRST
POC LAST
OMB X DATE
PKG TITLE
CUR OMB NO
NEW NO FLG
OBLIGATION
GEN_COMNTS
Type Width
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Logical
Logical
Date
Numeric
Date
Character
Memo
Character
Character
Numeric
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Date
Memo
Numeric
Logical
Numeric
Memo
4
2
14
18
12
14
14
18
18
18
2
7
8
7
4
8
1
1
8
1
8
1
10
20
24
2
1
1
1
1
1
1
1
6
10
10
15
8
10
10
1
1
10
Dec


2
2







2

2





























                                                          Page 24

-------
PRAMS II
                   SYSTEM ADMINISTRATOR MANUAL
   44  OMBPREVRSP
   45  OMBPREVHRS
   46  OMBNEWRESP
   47  OMBNEWRPT
   48  OMBRESPADJ
   49  OMBRPTADJ
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
 8
 8
 8
 8
10
10
Structure of PACKAGE.DBF, continued
   50  OMBPRGCRSP
   51  OMBPRGRPT
   52  FREQ_RR_1
   53  FREQ_RR_2
   54  FREQ_RR_3
   55  FREQ_RR_4
   56  FREQ_RR_5
   57  FREQ_RR_6
   58  FREQ_RR_7
   59  FREQ_RR_8
   60  FREQ_RR_9
   61  FREQ_DSCRP
   62  PURPOSE_1
   63  PURPOSE_2
   64  PURPOSE_3
   65  PURPOSE_4
   66  PURPOSE_5
   67  PURPOSE_6
   68  PURPOSE_7
   69  STAT_CMNTS
   70  OMB_CMNTS
   71  OMB_CONDIT
   72  OMB_APPROV
   7 3  DABO_NAME
   74  DO  INITALS
Numeric         8
Numeric         8
Character       1
Character       1
Character       1
Character       1
Character       1
Character       1
Character       1
Character       1
Character       l
Character      25
Character       1
Character       1
Character       1
Character       1
Character       1
Character       1
Character       1
Memo           10
Memo           10
Logical         1
Logical         1
Memo           10
Character       2
 This  database  uses  the memo  file:  PACKAGE.DBT
 This  database  is associated  with  index  file(s):
        :  PACKAGE2.NDX  (ICR_NUMBER)+STR(PKG_NUMBER)
        :  PACKAGE1.NDX  (icr_number)
 December 27,  1989  Ver l.l
                                        Page 25

-------
PRAMS II
       SYSTEM ADMINISTRATOR MANUAL
Structure for database :  TRACKING.DBF
Field  Field name  Type
Width    Dec
    4
    2
    2
    8
   10
    1
    1
This database uses the memo file:  TRACKING.DBT

This database is associated with index file(s) :
       : TRAKICR.NDX   (icr_number)
       : TRAKPKG.NDX   (ICR_NUMBER)+STR(PKG_NUMBER)
                     :       TRAKDATE.NDX
(ICR_NUMBER)+STR(PKG_NUMBER)+DTOS(EVNT_DATE)
1
2
3
4
5
6
7
ICR NUMBER
PKG NUMBER
EVNT CODE
EVNT DATE
EVNT CMNTS
EVNT CLOSE
ICW FLAG
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Structure for database  : EVENTS.DBF

Field  Field name  Type        Width
    1  EVENT_CODE  Character       2
    2  EVENT NAME  Character       50
         Dec
Structure  for database  :  ICR.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Field name
ICR NUMBER
SUM RESP
SUM RPT HR
SUM ADJRSP
SUM ADJRPT
SUM PC RSP
SUM PC HRS
EXP DATE
DIV CODE
INIT DATE
ICR TITLE
AGENCY
CUR OMB NO
PENDING
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Date
Numeric
Date
Memo
Numeric
Numeric
Logical
Width Dec
4
10
10
10
10
10
10
8
2
8
10
2
8
1
 December 27,  1989   Ver 1.1
                            Page 26

-------
PRAMS II
                               SYSTEM ADMINISTRATOR MANUAL
15
16
17
18
19
ICR CMNTS
DABO NAME
AA CODE
TE STATUS
TE DATE
Memo
Memo
Character
Character
Date
10
10
3
2
8
This database uses the memo file called: ICR.DBT.

This database is associated with the following index files:

       : ICRINDEX.NDX  (icr_number)
       : ICRAGNCY.NDX  (AGENCY)+STR(ICR_NUMBER)
       : ICROMBAG.NDX  (AGENCY)+STR(CUR_OMB_NO)
Structure for database : ICW.DBF
Field
    1
    2
    3
    4
    5
    6
    7
    8
    9
   10
   11
   12
   13
   14
   15
   16
   17
   18
   19
   20
   21
   22
   23
   24
   25
   26
   27
Field name
ICR_NUMBER
ICW_LOGGED
DESK_OFFC
ICB_OMB_NO
EFFCT_DATE
AGNCY_NUMB
FUNCT_CODE
EXPIR_DATE
RESPDJDLD
RESP_NEW
RESP_DIFF
RSP_ADJ_ER
RSPADJREST
RSPADJCIU
RSP_PRG_CH
HOURSJDLD
HOURS_NEW
HOURS_DIFF
HRS_ADJ_ER
HR_ADJREST
HR_ADJ_CIU
HRS_PRG_CH
ICW_ID_NO
OMBRESPOLD
OMBRESPNEW
OMBRESPDIF
OMBRSPADER
Type
Numeric
Date
Character
Numeric
Date
Numeric
Character
Date
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Width
    4
    8
   40
    8
    8
    6
    3
    8
   10
   10
   10
   10
   10
   10
   10
   10
   10
   10
   10
   10
   10
   10
    6
   10
   10
   10
   10
Dec
 December 27,  1989   Ver l.i
                                                   Page  27

-------
PRAMS II
   SYSTEM ADMINISTRATOR MANUAL
28
29
30
31
32
33
34
35
36
37
38
39
OMBRSADRES
OMBRSADCIU
OMBRSPRGCH
OMBHRS OLD
OMBHRS NEW
OMBHRS DIF
OMBHRSADER
OMBHRADRES
OMBHRADCIU
OMBHRPRGCH
ICW COMNTS
OMBAGNCYNO
Structure for ICW.
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Memo
Numeric
DBF, continued
10
10
10
10
10
10
10
10
10
10
10
6

   40  OMBFUNCODE  Character
   41  OMBEXPIRE   Date
3
8
This database uses the memo file: ICW.DBT

This database is  associated with index file(s):

        :  ICW_ICR.NDX   (icr_number)
        :  ICW_DATE.NDX   (ICR_NUMBER)+DTOS(EFFCT_DATE)
 Structure  for  database  :  ICB PROF.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Field name
ICR NUMBER
CURRENT FY
NEXT FY
ORIG EST1
ADJ HOURS 1
PRG CHANG 1
EST HOURS2
ADJ HOURS 2
EST TOTAL1
PRG CHANG 2
PASS BACK
APPEAL 2
ALLOWANCE 2
CLOSE OUT
ICB COMNT
ICB REASON
REASON 1
Type Width Dec
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Character
Character
Memo
Memo
Logical
4
4
4
10
10
10
10
10
10
10
10
10
20
1
10
10
1
 December 27, 1989  Ver 1.1
                        Page 28

-------
PRAMS II
SYSTEM ADMINISTRATOR MANUAL
   18  REASON_2    Logical         1
   19  REASON_3    Logical         1
   20  REASON_4    Logical         1
   21  REASON_5    Logical         1
   22  REASON_6    character      50
   23  REASON_ICR  Numeric         4
   24  ESTJTOTAL2  Numeric        10

This database uses the memo file: ICB_PROF.DBT

This database is associated index file:
       : ICB.NDX  (icr_number)
 December 27,  1989  Ver 1.1
                     Page 29

-------
PRAMS II
                               SYSTEM ADMINISTRATOR MANUAL
Structure for database :  AGENCIES.DBF
Field  Field name
    1  AGENCYCODE
    2  AGENCYNAME
            Type
            Numeric
            Character
            Width
                2
               50
         Dec
This database is associated with index file(s)
       : AGENCIES.NDX  (icr_number)
Structure for database : SYSTEM.DBF
Field
    1
    2
    3
    4
    5
Field name
USER_ID
PASSWORD
LASTUPDATE
FULLNAME
SEC LEVEL
Type
Character
Character
Date
Character
Numeric
Width
   10
   10
    8
   25
    1
Dec
Structure for database  : TRAKTEMP.DBF
Field
1
2
3
4
5
6
7
Field name
ICR NUMBER
PKG NUMBER
EVNT CODE
EVNT DATE
EVNT CMNTS
EVNT CLOSE
ICW FLAG
Type
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Width
4
2
2
8
10
1
1
                                        Dec
 This  database  uses  the  memo  file: TRAKTEMP.DBT

 This  database  is  associated  with  index  file(s):
                     :       T  T  M  P  D  A  T
 (ICR_NUMBER)+STR(PKG_NUMBER)+DTOS(EVNT_DATE)
                                                NDX
 Structure for database :  AADIV.DBF
 Field  Field name
     1  AA_CODE
     2  DIV CODE
             Type
             Character
             Numeric
             Width
                 3
                 2
          Dec
 December 27,  1989  Ver 1.1
                                                    Page 30

-------
PRAMS II
                               SYSTEM ADMINISTRATOR MANUAL
    3  OFFICE
    4  MAIL_CODE
    5  OD NAME
            Character
            Character
            Character
                5
                7
               80
Structure for database : ARC ICR.DBF
Field
    1
    2
    3
    4
    5
    6
    7
    8
    9
   10
   11
   12
   13
   14
   15
   16
   17
Field name
ICR_NUMBER
SUM_RESP
SUM_RPT_HR
SUM_ADJRSP
SUM_ADJRPT
SUM_PC_RSP
SUM_PC_HRS
EXP_DATE
DIV_CODE
INIT_DATE
ICR_TITLE
AGENCY
CUR_OMB_NO
PENDING
ICR_CMNTS
DABO_NAME
AA CODE
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Date
Numeric
Date
Memo
Numeric
Numeric
Logical
Memo
Memo
Character
Width
    4
   10
   10
   10
   10
   10
   10
    8
    2
    8
   10
    2
    8
    1
   10
   10
    3
Dec
This  database uses the memo  file: ARC  ICR.DBT
 Structure  for  database  : ARC  PKG.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
Field name
ICR NUMBER
PKG NUMBER
TTL RECHRS
TTL HOURS
TTL RESPON
ADJUSTMENT
PGM CHANGE
TAB DIFFER
CUR OMB IN
REQ BURDEN
REC RETENT
HR PER KPR
NO REC KPR
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Width
4
2
14
18
12
14
14
18
18
18
2
7
8
Dec


2
2







2

 December 27, 1989  Ver 1.1
                                                    Page 31

-------
PRAMS II
SYSTEM ADMINISTRATOR MANUAL
14
15
16
17
18
19
20
21
22
23
24
HR PER RSP
PER RSPOND
NO RESPDNT
STAT FLAG
ED FLAG
REQ X DATE
REVIEW TYP
FR DATE
COLECT TYP
PKG ABSTRC
OTHER AUTH
Structure for ARC_
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
USC CHAPTR
USC TITLE
AFFECTPUB7
AFFECTPUB6
AFFECTPUB5
AFFECTPUB4
AFFECTPUB3
AFFECTPUB2
AFFECTPUB1
POC MAIL
POC PHONE
POC FIRST
POC LAST
OMB X DATE
PKG TITLE
CUR OMB NO
NEW NO FLG
OBLIGATION
GEN COMNTS
OMBPREVRSP
OMBPREVHRS
OMBNEWRESP
OMBNEWRPT
OMBRES PADJ
OMBRPTADJ
OMBPRGCRSP
OMBPRGRPT
FREQ RR 1
FREQ RR 2
FREQ RR 3
FREQ RR 4
FREQ RR 5
FREQ RR 6
Numeric
Numeric
Numeric
Logical
Logical
Date
Numeric
Date
Character
Memo
Character
7 2
4
8
1
1
8
1
8
1
10
20
PKG. DBF, continued
Character
Numeric
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Date
Memo
Numeric
Logical
Numeric
Memo
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Character
Character
Character
Character
Character
Character
24
2
1
1
1
1
1
1
1
6
10
10
15
8
10
10
1
1
10
8
8
8
8
10
10
8
8
1
1
1
1
1
1
 December 27, 1989  Ver 1.1
                     Page 32

-------
PRAMS II
SYSTEM ADMINISTRATOR MANUAL
58 FREQ_RR_7 Character
59 FREQ RR 8 Character
60 FREQ RR 9 Character
61 FREQ DSCRP Character
62 PURPOSE_1 Character
63 PURPOSE 2 Character
64 PURPOSE 3 Character
65 PURPOSE 4 Character
66 PURPOSE 5 Character
67 PURPOSE 6 Character
68 PURPOSE 7 Character
69 STAT CMNTS Memo
70 OMB CMNTS Memo
71 OMB CONDIT Logical
72 OMB APPROV Logical
73 DABO NAME Memo
74 DO_INITALS Character
This database uses the memo file:
Structure for database : ARC_ICB.
1
1
1
25
1
1
1
1
1
1
1
10
10
1
1
10
2
ARC_PKG.DBT
DBF
Field Field name Type Width Dec
1 ICR NUMBER Numeric
2 CURRENT FY Numeric
3 NEXT FY Numeric
4 ORIG EST1 Numeric
5 ADJ HOURS 1 Numeric
6 PRG CHANG 1 Numeric
7 EST HOURS2 Numeric
8 ADJ HOURS2 Numeric
9 EST TOTAL1 Numeric
10 PRG CHANG2 Numeric
11 PASS BACK Numeric
12 APPEAL 2 Numeric
13 ALLOWANCE2 Character
14 CLOSE_OUT Character
15 ICB COMNT Memo
16 ICB REASON Memo
17 REASON 1 Logical
18 REASON 2 Logical
19 REASON 3 Logical
20 REASON 4 Logical
21 REASON 5 Logical
22 REASON 6 Character
4
4
4
10
10
10
10
10
10
10
10
10
20
1
10
10
1
1
1
1
1
50
 December 27,  1989  Ver 1.1
                     Page 33

-------
PRAMS II
    SYSTEM ADMINISTRATOR MANUAL
   23  REASON_ICR  Numeric
   24  EST TOTAL2  Numeric
 4
10
This database uses the memo file:  ARC ICB.DBT
Structure for database :  ARC ICW.DBF
Field Field name
1 ICR NUMBER
2 ICW LOGGED
3 DESK OFFC
4 ICB OMB NO
5 EFFCT DATE
6 AGNCY NUMB
7 FUNCT CODE
8 EXPIR DATE
9 RESPD OLD
10 RESP NEW
11 RESP DIFF
12 RSP ADJ ER
13 RSPADJREST
Structure for ARC_
14 RSPADJCIU
15 RSP PRG CH
16 HOURS OLD
17 HOURS NEW
18 HOURS DIFF
19 HRS ADJ ER
20 HR ADJREST
21 HR ADJ CIU
22 HRS PRG CH
23 ICW ID NO
24 OMBRES FOLD
25 OMBRES PNEW
26 OMBRESPDIF
27 OMBRSPADER
28 OMBRSADRES
29 OMBRSADCIU
30 OMBRSPRGCH
31 OMBHRS OLD
32 OMBHRS NEW
33 OMBHRS DIF
34 OMBHRS ADER
Type
Numeric
Date
Character
Numeric
Date
Numeric
Character
Date
Numeric
Numeric
Numeric
Numeric
Numeric
Width Dec
4
8
40
8
8
6
3
8
10
10
10
10
10
ICW . DBF , continued
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
10
10
10
10
10
10
10
10
10
6
10
10
10
10
10
10
10
10
10
10
10
December 27, 1989  Ver 1.1
                        Page 34

-------
PRAMS II
                   SYSTEM ADMINISTRATOR MANUAL
   35  OMBHRADRES  Numeric        10
   36  OMBHRADCIU  Numeric        10
   37  OMBHRPRGCH  Numeric        10
   38  ICW_COMNTS  Memo           10
   39  OMBAGNCYNO  Numeric         2
   40  OMBFUNCODE  Character       3
   41  OMBEXPIRE   Date            8

This database uses the memo file:  ARC ICW.DBT
structure for database : ARC TRK.DBF
Field  Field name  Type
    1  ICR_NUMBER
    2  PKG_NUMBER
    3  EVNT_CODE
    4  EVNT_DATE
    5  EVNT_CMNTS
    6  EVNT_CLOSE
    7  ICW FLAG
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Width
    4
    2
    2
    8
   10
    1
    1
                     Dec
 This database uses the memo  file: ARC TRK.DBT
 December 27, 1989  Ver 1.1
                                        Page 35

-------
PRAMS II                              SYSTEM ADMINISTRATOR MANUAL
                          APPENDIX B




                INPUT FORMS STORAGE STRUCTURES
 December 27, 1989  Ver l.i                                Page 36

-------
PRAMS II
              SYSTEM ADMINISTRATOR MANUAL
            DATABASE FIELD STORAGE OF INPUT FORMS
Input forms utilized in the PRAMS system are listed here with
the respective  databases  and field names  as  related to each
form.  The Forms represent the screen input forms  as  detailed
above.   (The  item  number  on  the  input form, if any,  is shown
next to the input prompts listed below.)
Standard Form 83

This form utilizes two databases,  with each database using one
index file:

1.   ICR.DBF  with ICRINDEX.NDX which  orders the database  by
     ICR number.

2.   PACKAGE.DBF  with  PACKAGE1.NDX which  orders this database
     by ICR number.
 Input Prompt/Display:

 ICR  number
 Desk Officer  Initials
 Agency  Name  (#1)

 Agency  code  (#2)

 First name   (#3)
 Last name   (#3)
 Mail code   (#3)
 Telephon number (#3)
 Title (#4)

 Legal authorities(#5)
 Affected Public(#6)
Field Name;

ICR_NUMBER
ICR_NUMBER
PKG_NUMBER

DO_INITALS
DABO_NAME
DABO_NAME
AGENCY
PKG_NUMBER
POC_FIRST
POC_LAST
POC_MAIL
POC_PHONE
PKG_TITLE
ICRJTITLE
USC_TITLE
USC_CHAPTR
OTHER_AUTH
AFFECTPUB7
AFFECTPUB6
(system generated)
Database;

 ICR
 PACKAGE
 PACKAGE

 PACKAGE
 PACKAGE
     ICR
 ICR
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 ICR
 PACKAGE
 PACKAGE
  PACKAGE
 PACKAGE
 PACKAGE
 December 27, 1989  Ver l.l
                                    Page 37

-------
PRAMS II
               SYSTEM ADMINISTRATOR MANUAL
Abstract (#13)
Collection type  (#14)
Type of review (#15)

(#17)
Number of respondents
Respns per respondnt
Total annual responss
Hours per response
AFFECTPUB5
AFFECTPUB4
AFFECTPUB3
AFFECTPUB2
AFFECTPUB1
PKG_ABSTRC
  COLECT_TYP
  REVIEW TYP
  NO_RESPDNT
  PER_RESPOND
  TTL_RESPON
  HR PER RSP
 (#18)
 Number of recordkeepers   NO_REC_KPR
 Hours per recordkeeper    HR_PER_KPR
 Total rec. keeping  hours  TTL_RECHRS
 Retention period          REC_RETENT

 (#19)
 Requested hours           REQ_BURDEN
 In  current OMB inventory  CUR_OMB_IN
 The difference            TAB_DIFFER
 Program  change            PGM_CHANGE
 Adjustment                ADJUSTMENT
 (#20)
 Current  OMB  number

 (#21)
 Request  Exp.  date

 Purpose  (#22)
 Frequency (#23)
   CUR  OMB NO
   REQ_X_DATE

   PURPOSE_1
   PURPOSE_2
   PURPOSE_3
   PURPOSE_4
   PURPOSE_5
   PURPOSE_6
   PURPOSE_7

   FREQ_RR_1
   FREQ_RR_2
   FREQ_RR_3
   FREQ RR 4
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
                               PACKAGE
 PACKAGE
 PACKAGE

 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE

 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 December 27, 1989  Ver l.l
                                    Page 38

-------
PRAMS II
             SYSTEM ADMINISTRATOR MANUAL
SF-83 (continued)

Input Prompt/Display:
 (#24)
Respondents Obligation

 (#25)
Educational Instituions

 (#26)
Statistical/Sampling
General Comments

ICR Comments
Field Name:
FREQ_RR_5
FREQ_RR_6
FREQ_RR_7
FREQ_RR_8
FREQ_RR_9
FREQ_DSCRP
OBLIGATION


 ED_FLAG


 STAT_FLAG
 STAT_CMNTS

 GEN_COMNTS

 ICR CMNTS
Database:
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE
 PACKAGE


PACKAGE


PACKAGE
PACKAGE

PACKAGE

ICR
 Profile  Sheet  for original clearance  (EPA Form  2B)

 This  form utilizes three databases and three  index  files:

 1.    ICR.DBF with  ICRINDEX.NDX which orders this database  by
      ICR number.

 2.    ICR_PROF.DBF with ICR_PROF.NDX which orders this database
      by  ICR number.

 3.    PACKAGE.DBF WITH  PACKAGE1.NDX which  orders this database
      by  ICR number.
 Input Prompt/Display;

       ICR Number
    Field Name;             Database:

    ICR_NUMBER             ICR
    ICR_NUMBER             ICB_PROF
    ICR_NUMBER             PACKAGE
    PKG_NUMBER (set to 0)   PACKAGE
 December 27, 1989  Ver 1.1
                                  Page 39

-------
PRAMS II
          SYSTEM ADMINISTRATOR MANUAL
(#1)  ICR Title
(#2)  Fiscal Years

(#3)  New ICR /Active ICR
      (not input here)

(#4)  Previous Clearance

(#5)  Originating Office

(#6)  Contact Person

              Mail Code
              Phone

(#7)  Burden Hours
Form 2B  (continued)

Input Prompt/Display;

      AA Code
      Division code

(#8)  Abstract

      ICR Comments
ICR_TITLE
FY_CURRENT
FY_NEXT
PENDING
  ICR
  ICB_PROF
  ICB_PROF
  ICB PROF
(not processed here)

(intentionally omitted)

POC_FIRST
POC_LAST
POC_MAIL
POC_PHONE

ORIG EST1
Field Name:

AA_CODE
DIV_CODE

PKG_ABSTRC

ICR  CMNTS
  PACAKGE
  PACKAGE
  PACAKGE
  PACKAGE

  ICB PROF
Database;

  ICR
  ICR

  PACKAGE

  ICR
 Inventory Correction  Worksheet   (ICW)

 This  form utilizes  one  database  and  one index  file:

 1.    ICW.DBF with ICW.NDX which  orders this database by  ICR
      number.
 Input Prompt/Display;

 ICR Number

 Completion Date

 Desk Officer
 Field Name;

 ICR_NUMBER

 ICW_LOGGED

 DESK OFFICE
Database;

  ICW

  ICW

  ICW
 December 27, 1989  Ver l.l
                               Page 40

-------
    PRAMS II
          SYSTEM ADMINISTRATOR MANUAL
    Effective Date

     (#2) Agency/Bureau  #

     (#4) Functional  code

     (#7) Expiration  date

     (#16)
     Number  of respondents  (old)
     Number  of hours  (old)
     Number  of respondents  (new)
     Number  of hours  (new)
     Respns  difference (new-old)
     Hours difference (new-old)
     Adjustment  to responses
     Adjustment  to hours
     Error correction to respns
     Error correction to hours
     Change  in use:  responses
     Change  in use:  hours
     Program change:  responses
     Program change:  hours

     ICW comments

ICR Profile  Sheet (EPA Form 2A)
EFFCT_DATE

AGNCY_NUMB

FUNCT_CODE

EXPIR DATE
RESPD_OLD
HOURS_OLD
RESP_NEW
HOURS_NEW
RESP_DIFF
HOURS_DIFF
RSP_ADJ_ER
HRS_ADJ_ER
RSPADJREST
HR_ADJREST
RSPADJCIU
HR_ADJ_CIU
RSP_PRG_CH
HRS_PRG_CH

ICW CMNTS
  ICW

  ICW

  ICW

  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW
  ICW

  ICW
This input procedure utilizes 3  databases.  The ICR database and the PACKAGE
database are used for displaying the top portion  of the  form.  They are both
indexed on ICR number, utilizing PACKAGE1.NDX  AND  ICRINDEX.NDX, respectively.
Only the ICB_PROF.DBF database is utilized for the input of data.  This
ICB_PROF database is coordinated with index file ICB_PROF.NDX which orders
the database by ICR number.
Input Prompt/Display;

ICR Number
Expiration date
ICR Title
Contact

Phone
OMB number
Most recent approvl by OMB
Field Name:

ICR_NUMBER
EXP_DATE
ICRJTITLE
POC_FIRST
POC_LAST
POC_PHONE
CUR_OMB_NO
SUM RPT HR
Database;

ICR
ICR
ICR
PACKAGE
PACKAGE
PACKAGE
ICR
ICR
     December 27,  1989  Ver  l.l
                               Page  41

-------
     PRAMS II
           SYSTEM ADMINISTRATOR MANUAL
Original estimate
(0 if no Form 2B submitted)

Total estimate
 (as of 9/10/this FY)
All adjustments (this FY)
All Program changes  (this FY)
Estimated Total
(Should be same as ESTJTOTALl)

Proposed adjustment  (next FY)
Proposed Prg_Change  (next FY)
Total Estimate (next FY)
Reason  (for adjustment or
program change)

Reason  (if ICR should not
be on the FY ICB)
Collection completed
Collection cancelled
Collection started and ends
 during the "current FY"

Collection combined
 with other ICR

Rule not going final in  FY 90
Other reason
ORIG EST1
ESTJTOTAL1
ADJ_HOURS1
PRG_CHANG1

EST_HOURS2

ADJ_HOURS2
PRG_CHANG2
ESTJTOTAL2

ICB REASON
REASON_1
REASON_2

REASON  3
REASON_4
REASON_ICR
REASON_5
REASON  6
ICB PROF
ICB_PROF
ICB_PROF
ICB_PROF

ICB_PROF

ICB_PROF
ICB_PROF
ICB_PROF

ICB PROF
ICB_PROF
ICB_PROF

ICB PROF
ICB_PROF
ICB_PROF
ICB_PROF
ICB  PROF
      December 27, 1989  ver 1.1
                                Page 42

-------
     PRAMS II
           SYSTEM ADMINISTRATOR MANUAL
OMB Response to an Inventory Correction Worksheet (ICW)

The OMB Response procedure in the case of an ICW, utilizes two
databases: ICW.DBF, indexed on ICR number with ICW.NDX,  and ICR.DBF
indexed on ICR number with ICRINDEX.NDX.
Input Prompt/Display:
Field Name;
Database:
ICR Number

Agency code

Function code







Expiration date

old response


inventory

old rpt hrs inventory

OMB approved

OMB approved

OMB approved

OMB approved






ICR_NUMBER

AGNCY NUMB
OMBAGNCYNO
FUNCT CODE
OMBFUNCODE
EXPIR DATE
OMBEXPIRE
RESPD OLD
OMBRESPOLD
HOURS OLD
OMBHRS OLD
response inventory RESP_NEW

OMBRES PNEW
rpt hrs inventory HOURS_NEW

OMBHRS NEW
resp difference RESP_DIFF

OMBRES PDIF
rpt hrs difference HOURS_DIFF






These six are OMB approved


Adjustments broken out.





OMB approved
changes






Prg responses

OMBHRS_DIF
RSP ADJ ER
OMBRSPADER
HRS ADJ ER
OMBHRSADER
RSPADJREST
OMBRSADRES
HR ADJREST
OMBRADRES
RSPADJCIU
OMBRSADCIU
HR ADJ CIU
OMBHRADCIU

RSP_PRG_CH
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW
ICW

ICW
      December 27,  1989  Ver l.i
                                Page 43

-------
     PRAMS II
           SYSTEM ADMINISTRATOR MANUAL
(OMB ICW Response cont'd)

Input Prompt/Display:

OMB approved rpt hrs Prg
 changes

ICW Comments
Field Name:
OMBRSPRGCH

HRS_PRG_CH
OMBHRPRGCH
ICW COMNTS
Computations involving the
above data fields update the
following fields in the database
file called ICR.DBF:
SUM_RESP
SUM_RPT_HR
SUM_ADJRSP
SUM_ADJRPT
SUM_PC_RSP
SUM_PC_HRS
EXP DATE
Database;
ICW

ICW
ICW
ICW
ICR
ICR
ICR
ICR
ICR
ICR
ICR
OMB Response to Standard Form 83

The OMB Response input procedure in the case of Standard Form 83
utilizes two databases :ICW.DBF, indexed on ICR number with
ICW.NDX, and ICR.DBF indexed on ICR number with ICRINDEX.NDX.
Input Prompt/Display:

ICR Number

OMB Approved expiration date
ICR OMB Approval flag
OMB assigned OMB number
Previous Total number of
 responses
Previous Total reporting hours
New Total number of  responses
New Total reporting  hours
Field Name:

ICR_NUMBER
PKG_NUMBER
OMB_X_DATE
OMB_APPROV
CUR_OMB_NO

OMBPREVRSP
OMBPREVHRS
OMBNEWRESP
OMBNEWRPT
Database:

PACKAGE
PACKAGE
PACKAGE
PACKAGE
PACKAGE

PACKAGE
PACKAGE
PACKAGE
PACKAGE
      December  27,  1989  Ver  1.1
                                Page 44

-------
     PRAMS II
           SYSTEM ADMINISTRATOR MANUAL
(OMB SF-83 Response cont'd)

Input Prompt/Display:
Field Name;
The following fields are calculated
from other inputs in the lew response:
Is there a condition for
 renewal
or other comments associated
 with this OMB response form?
                                OMBNEWRPT
                                OMBRESPADJ
                                OMBRPTADJ
                                OMBPRGCRS
                                OMBPRGRPT
                                NEW NO FLG
OMB_CONDIT

OMB CMNTS
Computations from the above data
update the following fields in the
database file called ICR.DBF:
NEW Total # of Responses

Total Reporting Hours
SUM_RESP

SUM RPT HR
* Total of Adjstmnts for
 Responses
(_sumadjrsp+mOMBRSPERR+niOMBRSPEST
 +mOMBRSPCIU)                   SUM_ADJRSP

* Total Adjustments to Rporting Hrs
(_sumadj rpt+mOMBRPTERR+mOMBRPTEST
+mOMBRPTCIU)                    SUM_ADJRPT

* Total Program Changes for  Respnses
(_sum_pcrsp+mOMBPGCRSP)         SUM_PC_RSP

* Total Program Changes to Rprt Hrs
(_SUm_pchrs+mOMBPRGRPT)         SUM_PC_HRS
 Expiration date
 (Old OMB Approved Expiration
  Date)
Database;
                     PACKAGE
                     PACKAGE
                     PACKAGE
                     PACKAGE
                     PACKAGE
                     PACKAGE
PACKAGE

PACKAGE
ICR

ICR
 EXP  DATE
                      ICR
                      ICR
                      ICR
                      ICR
 ICR
      December  27,  1989   Ver 1.1
                                Page 45

-------
     PRAMS II
                      SYSTEM ADMINISTRATOR MANUAL
Current OMB number
(Old OMB Assigned OMB number)
           CUR OMB NO
ICR
Package Tracking Event

Below lists the four databases are used for this input procedure.
The index files used with each database (if any) are also listed
along with the respective index key fields.  Although all four
databases are used during the procedure, only the ICR and the
TRACKING databases are altered by it.

PACKAGE.DBF:
     PACKAGE2.NDX 	 Indexed on ICR NUMBER and PKG NUMBER
TRACKING.DBF;
     TRAKICR.NDX
     TRAKPKG.NDX
     TRAKDATE.NDX

ICR.DBF;
     ICRINDEX.NDX
     ICRAGNCY.NDX
     ICROMBAG.NDX
•  Indexed on  ICR_NUMBER
•  Indexed on  ICR_NUMBER and  PKG_NUMBER
•  Indexed on  ICR_NUMBER &  PKG_NUMBER &
   tracking event date

Indexed on ICR number
Indexed on agency and ICR number
Indexed on agency and current  OMB number
Input Prompt/Display;

ICR number
(Previously input &  screened)

Package number
(Previously input &  screened)

Event Code:

Date:

Comments:
          Field  Name;

          ICR_NUMBER


          PKG NUMBER
          EVNT_CODE
          TE_CODE
          EVNT_DATE
          TE_DATE
          EVNT CMNTS
Database;

ICR
PACKAGE
TRACKING
PACKAGE
TRACKING

TRACKING
ICR
TRACKING
ICR
TRACKING
      December  27,  1989   Ver 1.1
                                           Page 46

-------
     PRAMS II
           SYSTEM ADMINISTRATOR MANUAL
ICW Tracking Event

Below lists the three databases are used during this input
procedure.  The index files used with each database (if any) are
also listed along with the respective index key fields.  The events
database is used for reference only.
ICR.DBF:
     ICRINDEX.NDX

ICW.DBF;
     ICW.NDX

TRACKING.DBF:
     TRAKICR.NDX
     TRAKPKG.NDX
     TRAKDATE.NDX
EVENTS.DBF
indexed om ICR number
indexed on ICR number
Indexed on icr number
Indexed on ICR number and package number
Indexed on ICR number and package number
 and tracking event date.
Input Prompt/Display;

ICR number
(Previously  input & screened)

Event Code:
 Date:
 Comments:
Field Name:

ICR NUMBER
EVNT_CODE
TE_CODE
ICW_FLAG

EVNT_DATE
TE_DATE

EVNT CMNTS
Database:

ICR
ICW

TRACKING
ICR
ICW

TRACKING
ICR

TRACKING
      December 27,  1989   ver l.l
                                Page 47

-------
T1PEX
  •  Corporation^

-------