Allow up to 250 pay groups to process at one time. Previously, the limit was 120. This change was necessary for the larger districts.

1.2 STRSAD: Generate error message if name or address blank

When running STRSAD, an error message will be printed if any part of the employee's name or address is missing. To correct errors, modify the name or address in USPSCN/BIOSCN. This change is required according to an STRS mandate.

1.3 USPSCN/PAYSCN: Allow object codes other than 1XX

In USPSCN/PAYSCN it was only allowing 1XX object codes to be entered if the user had SYSMAN privileges. This has been changed so that all users now can enter object codes other than 1XX.

1.4 USPSCN/UPDCAL: Allow object codes other than 1XX

In USPSCN/UPDCAL it was only allowing 1XX object codes for payments for special entered pay accounts. With this change, it will provide a warning message if a 1XX object code is not used. The warning states, "Misc. pay accounts are GENERALLY 1XX object codes. Press the accept key to continue." This will allow the districts the ability to use UPDCAL for payment of fringe benefits and board provided amounts.

2 Problems Corrected

Corrected a problem with the recent changes to audit benefit balances. When using the deferred leave option, changes to 'Deferred Sick,' 'Deferred Vacation', and 'Deferred Personal' were being written to the USPAUD.SEQ file twice. This has been corrected.

3 Technical Enhancements and Changes

The documentation is maintained by the SSDT and can be found in the OECN$ROOT:[USPS.V4P2.DIST] distribution directory.

5.1 Documentation Summary

The following are documentation files for the Uniform Staff Payroll System package and a brief description of the contents and intended audience of the document.

Documentation produced for this package 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.

Table 1 Documentation Summary

Document File	Revision Date	Description
USPS_USER_GUIDE	March, 2006	USPS User Guide
USPS_REFERENCE_MANUAL	March, 2006	USPS Reference Manual
USPS_SYSMAN_MANUAL	March, 2006 USPS System Manager Manual

5.2 Documentation _UPDATE Files

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 Package Installation and Logicals

Installing USPS involves first using the OECN_INSTALL procedure to unpack the savesets into the OECN$ROOT:[USPS.V4P2.DIST]. After the distribution directories have been prepared, INSTALL_PACKAGE is used to transfer the package from the distribution directory into the user execution directory. See the VAXMGR_HANDBOOK in OECN$ROOT:[DOCUMENT.DIST] for more information about OECN_INSTALL and INSTALL_PACKAGE.

Prior to executing INSTALL_PACKAGE it is necessary to define several system logicals required by the package. The table below lists the logicals which should be defined prior to executing INSTALL_PACKAGE for USPS:

Table 2 System Logicals

Logical	Description
OECN$PAY_42	Shared directory. Contains executables and files shared by all USPS
OECN$CDD_PAY_42	CDD path name (optional, see next section)
OECN$MENU$FILES 1	Location for menu files
OECN$HELP 1	Location of VMS help libraries

The USPS 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 USPS package. However, the 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 OECN$UTL will load the CDD definitions into the CDD when either the "CDD" or "FULL" option is used to install USPS. INSTALL_PACKAGE is the only supported method for installation of CDD definitions for USPS Version 4.2

The USPS CDD definitions for USPS Version 4.2 will be loaded into the CDD path referenced by the OECN$CDD_PAY_42 logical. This logical must be defined prior to executing INSTALL_PACKAGE and should be defined as a system logical. SSDT recommends that the USPS definitions be placed in a separate CDD directory from other CDD definitions. This increases the efficiency of the CDD, allows the USPS definitions to be treated as a 'database' from 20/20, and simplifies security maintenance. For example:

$ DEFINE/SYSTEM OECN$CDD_PAY_42 CDD$TOP.OECN.USPS42

After defining the OECN$CDD_PAY logical, the INSTALL_PACKAGE may be executed. Below is sample run of the CDD installation:

$ $ @OECN$UTL:INSTALL_PACKAGE CDD OECN$ROOT:[USPS.V4P2.DIST] OECN INSTALL_PACKAGE (V1.1-010) Copyright © 1991, Ohio Dept of Ed, IMS %OECNINS-I-BEGIN, Begin CDD installation for USPS Version 4.2 on NWOCA0:: at 14-MAR-1994 15:09:36.41 %OECNINS-I-CDD, Loading CDD definitions to CDD$TOP.OECN.USPS42 OECN INSTALL_CDD (V1.0-001) Copyright © 1994, Ohio Dept of Ed, IMS %OECNINS-I-START, Starting CDD install for USPS Version 4.2 %OECNINS-I-RECORD, Processing record OECN$CDD_PAY.ABSENCE_REC . . .

7 UDMS Dictionary Implementation

USPS contains a dictionary for use with the UDMS Report Writer product. The dictionary will be installed automatically when OECN$UTL:INSTALL_PACKAGE is executed with either the FULL or UDMS option. If a version of the dictionary has already been installed, INSTALL_PACKAGE will merge the updated version into the local copy. Thus, reports and additional views developed locally will be preserved.

USPS also contains a sharable image which is used by UDMS. The sharable image provides 3GL functions which are used in calculated fields by the UDMS dictionary. To make this image available to UDMS, you must define the following logical during system startup:

$ DEFINE/SYSTEM OECN$USPS_SHR OECN$PAY:USPSSHR.EXE

8 Implementation of this Release

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 USPS Version 4.2 software please feel free to contact SSDT for assistance using one of the following options:

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 USPS Version 4.2 Release: 2007.06