HP 3000 Manuals HP 3000 Manuals
HP ALLBASE/4GL Files HP ALLBASE/4GL uses a number of different types of files. They are: * S-files. * Program files. * Command files. * Application databases. * Terminal support files. S-Files The HP ALLBASE/4GL S-files are a set of 11 pairs of files. They contain the definition of any completed applications on the system, and the application developers' input for applications under development. The S-files are named S01D to S11D, and S01I to S11I. Each S-file consists of a pair of files. One file is a data file (identified by the D suffix on the name), and the other file is an index file (identified by the I suffix on the name). Each index file is matched to the corresponding data file and must not be copied separately, or deleted. If necessary, you can use the HP4REMK utility program to rebuild the S-file indexes. Refer to "Using Remake and Reorder" , for information about the HP4REMK utility. One set of S-files can support a number of applications and a number of users working simultaneously. In effect, a set of S-files is an HP ALLBASE/4GL system. One MPE/iX system can support multiple sets of HP ALLBASE/4GL S-files. Each S-file set requires a system administrator, and can support different system-wide configurations, user name lists, and applications.
NOTE The developer environment S-files are not the same as the run-time environment S-files. The two types of S-files are not interchangeable.
All the files in each set of S-files must be in the same MPE/iX group and account. Copying S-Files. If required, you can use more than one set of S-files on the MPE/iX system. If you do create more than one set of S-files, each set must reside in a separate MPE/iX group.
CAUTION Always use the command file HP4SCOPY.HP4GL.SYS to create new copies of the HP ALLBASE/4GL S-files. Attempting to use FCOPY directly will waste disk space.
Each of the HP ALLBASE/4GL S-files has a file limit of 2 000 000 records to allow for expansion. Since the FCOPY command always creates a file with 32 extents, the first extent will occupy up to 250 000 sectors of disk space. To avoid using excessive disk space, the HP4SCOPY command file uses the BUILD command to create suitable files, and then copies the S-files into the new files. To use the HP4SCOPY command file, enter the following command at the MPE/iX prompt: HP4SCOPY.HP4GL.SYS src=src_grp [dest=dest_grp] [overwrite={Y}] [ {N}] In this command, the term src_grp is the group containing the files you wish to copy, and dest_grp is the group you want to copy the files to. For the HP ALLBASE/4GL developer environment, the MPE/iX sub-system installation procedure installs a set of S-files in the HP4GL.SYS group. In general, you should leave the S-files in the HP4GL.SYS group in their original state. This ensures that you have a "clean" set of S-files if you need to establish a new HP ALLBASE/4GL environment. For the HP ALLBASE/4GL run-time environment, the S-files are installed in the HP4GLR.SYS group. The HP4SCOPY command file is also in the HP4GLR.SYS group. Refer to S-File Size Limits for more information about S-file sizes. Program Files The HP ALLBASE/4GL program files are the executable program files that run HP ALLBASE/4GL. Only one set of program files is required on each MPE/iX system, as more than one set of S-files can use the same set of program files simultaneously. The HP ALLBASE/4GL program files reside in the PUB group of the SYS account. Some of the program files in the developer environment have an equivalent program file in the run-time environment. They differ sightly in functionality and therefore require a different name. To differentiate the developer version of a program file from its run-time equivalent, the run-time program file has an "R" appended to its name. Where this occurs it is indicated by the following notation: filename[R] The HP ALLBASE/4GL program files are listed in the table below. Table C-1. Program Files in the Developer Environment Name Purpose Stand-Alone Use HP4ARPT Administrator reports No HP4ATOS ASCII to S-file conversion program Stand-alone only HP4CHKAP Application consistency checker Yes HP4DRPT Developer reports No HP4FUTL File create/delete/reformat No utility HP4GEN Generate program No HP4GLB Main HP ALLBASE/4GL program Yes HP4LD Application loading program No HP4REMK S-file index rebuilding program Stand-alone only HP4REOD S-file reorder/compacting program Stand-alone only HP4RP Report painter No HP4SORT Report sorting program No HP4SP Screen painter No HP4STOA S-file to ASCII conversion program Stand-alone only HP4TUPLD HP TurboIMAGE/iX database Stand-alone only definition loading program HP4ULD Application unloading program No Table C-2. Program Files in the Run-Time Name Purpose Stand-Alone Use HP4ARPTR Administrator reports No HP4CHAPR Application consistency checker Yes HP4FUTLR File create/delete/reformat No utility HP4GLBR Main HP ALLBASE/4GL program Yes HP4LDR Application loading program No HP4REMKR S-file index rebuilding program Stand-alone only HP4REODR S-file reorder/compacting program Stand-alone only HP4SORTR Report sorting program No MPE/iX Command Files HP ALLBASE/4GL uses a number of MPE/iX command files. These files are used at the following times: * During the product installation process. * To start HP ALLBASE/4GL from the MPE/iX prompt. * To create new copies of the HP ALLBASE/4GL system files. The command files are located in the PUB.SYS group and the HP4GL[R].SYS group. The command files are listed in the following table. Table C-3. Command Files in the PUB.SYS Name Purpose Stand-Alone Use HP4GL Start-up command file for HP Yes ALLBASE/4GL developer HP4GL2 Used by HP4GL command file No HP4GLR Start-up command file for HP Yes ALLBASE/4GL run-time environment HP4GL2R Used by HP4GLR command file No Table C-4. Command Files in the HP4GL[R].SYS Name Purpose Stand-Alone Use HP4BLD[R] Builds HP ALLBASE/4GL environment Yes during installation HP4BLD2 Used by HP4BLD[R] No HP4SCOPY Copies HP ALLBASE/4GL S-files Yes (Used by HP4BLD[R]) Application Databases HP ALLBASE/4GL provides facilities for applications to access HP ALLBASE/SQL and HP TurboIMAGE/iX databases. The databases used in an application can be located anywhere in the MPE/iX file system. HP ALLBASE/4GL also provides the facilities needed to create and maintain KSAM data files and serial data files from within HP ALLBASE/4GL. KSAM data files do not need to be unique to an HP ALLBASE/4GL application or even a set of HP ALLBASE/4GL S-files. However, we recommend that only applications in one set of S-files use any given set of data files. Non-HP ALLBASE/4GL applications can use HP ALLBASE/4GL KSAM data files, however the HP ALLBASE/4GL transaction control system may not operate correctly if HP ALLBASE/4GL and non-HP ALLBASE/4GL applications use these data files simultaneously. Terminal Support Files Special files are required to provide the correct support for HP ALLBASE/4GL terminals. These files must be in the HP4TERM.SYS group and account. Refer to HP ALLBASE/4GL Terminals for more information about these files.