You are here: Development Standards > Upgrading OSAS > Converting to 7.6x > System File Changes

# System File Changes

Enhancements to OSAS version 7.5 included changes to certain system files. Programs must be changed to accommodate these enhancements.

OSMN

The OSAS menu structure is now contained within a single OS file (OSMN). While each application menu file still exists on the installation media, at installation time, these files are merged into the OSMN file. Modifications that add a menu file will not have to change in any manner, as the installation will automatically merge those application menus into the OSMN file.

xx.PTL and OSPTL

In a similar manner to string template files OSTPL and the application specific xx.TPL files, we have added a set of files that will hold the templates used for pick screen defaults. These are the OSPTL file, and the application specific xx.PTL files. If you intend to use pick screen defaults, those definitions should be entered into your xx.PTL files thru the ‘Create xx.PTL File’ function from the System File Maintenance menu in the Software Developer’s Kit.

xxAPPL.TXT

A new field has been added to each application’s xxAPPL.TXT file. This entry is called “ApplGl”, and it is located at the end of the ‘Application Information’ section. You must add this entry to your xxAPPL.TXT file, and set the value to either Y or N. (i.e. ApplGl = Y).

OSINFO.xxx

Several new paths have been added for the archive and Email system to use. While your modification should not have to worry about these directories, you should be aware that setting these paths may affect your modifications. These paths are:

- ‘Archive’ – Reports are archived to this folder
- ‘ArchiveShare’ – This should be the share equivalent to the ‘Archive’ folder, that can be accessed across the network.
- ‘FormsArchive’ – Forms are archived to this folder. Forms are items such as customer invoices and statements, Payable checks, and Purchase Orders.
- ‘FormsArchiveShare’ – This should be the share equivalent to the ‘FormsArchive’ folder, that can be accessed across the network.
- ‘Email’ – This folder is now used for copies of Email attachments that are sent out. This replaces the \osas\documents\forms folder that was used in version 7.5x.
- ‘EmailShare’ – This should be the share equivalent to the ‘Email’ folder, that can be accessed across the network.

OSCODE

The access code file has been restructured to function as the Role file. This file is also a mandatory file, unlike prior versions where this file was only created if an access code was being used. While this file functions similarly in that entries into this file are disallowed access for, the structure is slightly different than in prior versions.

OSSE

This new file for version 7.6 holds all of the next sequence numbers that are needed for history files that need a unique sequence number. In prior versions, typically a ‘NXTSEQ’ record was kept in the history file, and was used to generate a sequence number. Those records have been removed and new records are kept in the OSSE file that keeps track of what the next sequence number should be for a particular history file. This helps to maintain data normalization rules with sequence driven files. Use GENSEQ.PUB to retrieve and reserve the next available sequence number for your history files as needed.

GLDRxxx renamed to RMDRxxx

The GLDRxxx file was added at version 7.50 to support drill-down functionality from General Ledger back to the base application. This was has now been renamed to the RMDRxxx file, and now stores multiple years of entries as well. This was done so files that do not have a tie to General Ledger can use this file to store transaction post codes as needed.

xxTRSHDR and xxTRSDTL

Starting with version 7.6, F2 inquiry windows have the ability to use Translations. This allows the translation of fields that have little meaning (example: order type of 1, 2, or 3) to text that is meaningful to the user (example: New Order, Invoice, Misc. Credit). The ‘Inquiry Windows’ function in Resource Manager will make these files if they do not exist. If your application does not provide any transactions but provides F2 inquiry windows, these empty files should be included with your application.