User's Manual Part 4

FILE AUTHENTICATION
Introduction to File Authentication
112 OMNI 3600 REFERENCE MANUAL
Figure 40 Omni 3600 Application Memory Partitions
Rules for Storing Applications in Specific File Groups
Here are some important Omni 3600 file system features, as they relate to storing
application files in specific file groups, and how these features affect the file
authentication process:
• Most applications consist of more than one executable. For each executable
to run on the terminal, it must be signed and authenticated.
• Although not enforced by the operating system, it is recommended that only
one application be stored per file group in the application partition. Any
number of executable files can, however, be stored in a single file group.
• Using the CONFIG.SYS *GO variable, you can specify only one application to
automatically execute following a download and terminal restart. The defined
application is usually the main application stored in Group 1 and called from
the *GO variable in the CONFIG.SYS file in GID1.
• The main application stored in GID1 can access files, secondary applications,
or function libraries stored in any other file group.
• The application downloaded into GID1 is always the primary application for
the terminal. This application is owned by the primary terminal sponsor
(sponsor A) in cases where there are multiple sponsors.
• The Group 1 application controls any and all secondary applications stored in
terminal memory. That is, a secondary application can only be invoked by a
RUN command issued by the Group 1 application.
• An application stored in Groups 2–15 can only access files stored in its own
file group and in Group 15. For example, an application authorized by the
sponsor to be authenticated in Group 4 can only access files and libraries
stored in Group 4 and Group 15.
• If multiple applications (main and secondary) are to run on the same terminal,
each .OUT and/or shared library file must have its own matching signature file.
NOTE
The Omni 3600 operating system only enforces the rule that the main application
always be stored in GID1. You can, for example, store a shared library in any file
group. Rules for Storing Applications in Specific File Groups states reasons to
follow the guidelines previously described for storing applications and libraries in
specific file groups.