The documentation is maintained by the SSDT and can be found in the
OECN$ROOT:[SAAS.V2P1.DIST] distribution directory.
5.1 Documentation Changes
5.2 Documentation Summary
The following are documentation files for the School Asset Accounting System (SAAS) - Equipment Inventory Subsystem (EIS) and Vehicle Information Subsystem (VIS) packages. Below is a brief description of the contents and the intended audience of the document.
| Document File | Revision Date | Description |
|---|---|---|
| SAAS/EIS | ||
| EIS_USER_GUIDE | March, 2003 | SAAS/EIS User Guide |
| EIS_USER_GUIDE_UPDATE | March, 2003 | SAAS/EIS User Guide Updates |
| EIS_REFERENCE_MANUAL | March, 2003 | SAAS/EIS User Guide |
| EIS_REFERENCE_MANUAL_UPDATE | March, 2003 | SAAS/EIS User Guide Updates |
| EIS21_SYSMAN_HANDBOOK | March, 2001 | SAAS/EIS System Manager Handbook. Contains documentation on appraisal tape specs, system manager conversion instructions, GAAP startup instructions, purge program, file layouts, and fiscal closing instructions. |
| EIS_APPRAISAL_TAPE_SPEC | May, 2002 | EIS V2.1 Import/Export Tape Specifications. |
| SAAS_FIXED_ASSET_MAN | October, 1990 | User information on the concepts of fixed asset accounting from the State Auditor's Office. |
| EIS_GAAP_CHECKLIST | December, 1995 | Contains information useful for districts just starting up on EIS and for those districts preparing for the GAAP startup year. |
| SAAS/VIS | ||
| VIS10_SWUM | June, 1996 | SAAS/VIS User Manual |
| VIS10_SYSMAN_HANDBOOK | June, 1996 | SAAS/VIS System Manager Handbook. Contains documentation on fiscal closing instructions, VIS edit programs, and some problems and limitations. |
The following four EIS training manuals are available: EIS Beginners, EIS Intermediate, EIS Advanced, and EIS GAAP. Instructor's versions are also available. These contain additional notes and hints to aid in the training. The manuals are located in the following directories, respectively: TRAINING:[EIS.BEGINNER], TRAINING:[EIS.INTERMED], TRAINING:[EIS.ADVANCED], and TRAINING:[EIS.GAAP]. In addition to the manuals, the directory contains an introductory file, AAAREADME.1ST, and a set of data files designed to accompany the manual.
All documentation produced for these manuals was developed with a Digital product called VAX Document. This product enables us to provide two versions of the documentation for various types of printers. The version which has an extension of .LN03 can be printed on a laser printer; while version with the extension of .PS is to be printed on a ScriptPrinter.
| Document File | Revision Date | Description |
|---|---|---|
| EIS_BEG_TRAINING_MANUAL | March, 2001 | Beginning EIS Training Manual. |
| EIS_BEG_TRAINING_INST | March, 2001 | Beginning EIS Training Manual for Instructor. |
| EIS_INTER_TRAINING_MANUAL | March, 2001 | Intermediate EIS Training Manual. |
| EIS_INTER_TRAINING_INST | March, 2001 | Intermediate EIS Training Manual for Instructor. |
| EIS_ADV_TRAINING_MANUAL | March, 2001 | Advanced EIS Training Manual. |
| EIS_ADV_TRAINING_INST | March, 2001 | Advanced EIS Training Manual for Instructor. |
| EIS_GAAP_MANUAL | May, 2003 | EIS GAAP Training Manual. |
The users have the ability to print the updates to the documentation manuals since the previous release, without having to print the entire documentation manuals. The updates are contained in a separate file which uses the same naming convention as the normal manual with "_UPDATE" appended. The update files are available in .LN03 and .PS versions. You will find updates to both the user and system manager manuals if changes have taken place.
The update files will include *ONLY* the modified chapters of the documentation manual, a new table of contents, and an index if one exists in the documentation manual. Updated documentation is also included in the normal documentation manuals. Therefore, if you plan to print the newest version of the entire user or system manager manual, it will *NOT* be necessary to print the update file.
It should be noted that even though the purpose of the update files is to allow the users to print only the updates, there may be cases when it would be more practical to print the entire documentation manual, rather than trying to use the update file. For instance, if a new chapter is added at the very beginning of the manual, the numbering for all subsequent chapters will change as well (the size of the update file could be almost as large as the normal documentation manual). SSDT will advise you in the release notes when the changes are so numerous that we recommend that you print the entire documentation manual.
There will only be one _UPDATE file provided each release for every manual. We do not plan to distribute updates for previous releases, as we do for the release notes.
SSDT strongly advises that you print new documentation manuals before you try to utilize the _UPDATE files.
If you print a .PS version of the entire documentation manual, be sure to print the .PS version of the _UPDATE files. The _UPDATE pages will not fit into the manual properly if you try to mix the various documentation formats.
If there are no changes in the documentation manuals, no _UPDATE file
will exist on the release.
6 Installing CDD/DTR Definitions
The SAAS distribution contains optional CDD and DTR definitions that are acceptable for use with DTR, 20/20 and other products that are integrated with DEC CDD/Repository. Data names for COBOL are provided in the record definitions. The CDD definitions are optional and are not necessary to successfully install and utilize the base SAAS package. However, there are a few "supported" DTR reports. If you wish to be able to use these reports, you must install the CDD definitions.
The INSTALL_PACKAGE procedure in OECN$UTL will load the CDD definitions into the CDD when either the "CDD" or "FULL" option is used to install SAAS. INSTALL_PACKAGE is the only supported method for installation of CDD definitions for SAAS Version 2.1.
The CDD definitions for SAAS Version 2.1 will be loaded into the CDD path referenced by the OECN$CDD_SAAS logical. This logical must be defined prior to executing INSTALL_PACKAGE and should be defined as a system logical. SSDT recommends that the SAAS definitions be placed in a separate CDD directory from other CDD definitions. This increases the efficiency of the CDD, allows the SAAS definitions to be treated as a 'database' from 20/20, and simplifies security maintenance. For example:
$ DEFINE/SYSTEM OECN$CDD_SAAS CDD$TOP.OECN.SAAS21 |
After defining the OECN$CDD_SAAS logical, the INSTALL_PACKAGE may be executed. Below is sample run of the CDD installation:
$
$ @OECN$UTL:INSTALL_PACKAGE CDD OECN$ROOT:[SAAS.V2P1.DIST]
OECN INSTALL_PACKAGE (V1.1-010) Copyright © 1991, Ohio Dept of Ed, IMS
%OECNINS-I-BEGIN, Begin CDD installation for SAAS Version 2.1 on NWOCA0::
at 14-MAR-1994 15:09:36.41
%OECNINS-I-CDD, Loading CDD definitions to CDD$TOP.OECN.SAAS21
OECN INSTALL_CDD (V1.0-001) Copyright © 1994, Ohio Dept of Ed, IMS
%OECNINS-I-START, Starting CDD install for SAAS Version 2.1
%OECNINS-I-RECORD, Processing record OECN$CDD_SAAS.ACQUISITION_REC
.
.
.
|
Please implement this release as soon as possible. It is difficult for the SSDT to provide assistance to your problems if you are not utilizing the current version of the software supplied.
Please refer to the documentation files contained on the release tape to obtain a history of the modifications the software has gone through. The release documentation files are named in the format of "RELyymm.DOC" where yymm is the release date.
Should you experience any problems, or have any questions, concerning the OpenVMS/Alpha version of the SAAS Version 2.1 software please feel free to contact SSDT for assistance using one of the following options:
Send E-mail to ssdt-feedback@nwoca.org
Visit the OECN Public Forum at http://forums.oecn.k12.oh.us/forums/oecn/
DAS restricted Forum at http://forums.oecn.k12.oh.us/forums/das/
SSDT Home Page at http://ssdt.oecn.k12.oh.us/
End of Documentation for SAAS Version 2.1 Release: 05.03