Specifications

PERFORMING DOWNLOADS
Omni 37xx Download Differences
88 OMNI 37XX REFERENCE MANUAL
Redirecting Files to Other File Groups
GID1 is the default system mode setting for performing downloads. Using the
system mode menu options, you can select another file group (GID 2–15) as the
target group for the application download. If you select another group, files
download directly into the RAM of that file group.
To redirect files from the selected target file group to another file group as part of
the download operation, insert a zero-length SETGROUP.n file in the batch
download list (the same as SETDRIVE.x). The syntax of this convention is
SETGROUP.n, where
n = 1–15, for GIDs 1–15.
To create a zero-length SETGROUP file on the download computer, use the DOS
command REM as in the following example:
REM >SETGROUP.2
If you do not insert SETGROUP.n special files into the download list, all files
download into the target group selected in system mode. If no number is added to
the SETGROUP filename, SETGROUP.1 (GID1) is assumed.
Restrictions on File Redirection
The Omni 37xx file system restricts how you can redirect files to other file groups.
Here are the important points to remember:
• The main application must always be downloaded into GID1.
• Because of the way file groups are managed in the Omni 37xx file system,
only two schemes are available for redirecting files during a batch application
download:
• If, using system mode menu options, you select Group 1 (default) as the
target group for the download, files can be redirected to any other file
group, including GID15.
• If, using system mode menu options, you select a file group other than
Group 1 (GIDs 2–14) as the target group for the download, files can be
redirected only into the selected file group or into GID15.
In the following example, GID1 is selected as the target group for the download.
The download list loads FOO.OUT into Group 1 RAM, GOO.OUT into GID2, and
the shared library, COMN.LIB, into GID15. When the terminal restarts after the
download, the file authentication module is invoked for all three files, based on the
certificate data that authorizes them to be stored in their respective file groups.
If FOO.OUT is authenticated, the GID1 application, FOO.OUT, executes, as
specified by the *GO variable, when the terminal restarts following successful file
authentication. The function library stored in GID15 can be shared by both
applications, as both Group 1 and Group 2 applications can access Group 15:
FOO.OUT
FOO.P7S
*GO=FOO.OUT