The path name indicates where the installation item (file) is to be found in the BS2000 system.
Format: :<cat-id>:$<userid>.<item-name> e.g. :HOME:$TSOS.SYSSDF.PERCON.029
The path name is registered in the SCI when the installation item is installed with IMON. At this time, too, the path name is assigned to the logical ID of the installation item.
The depot location can be modified after installation. Note the following:
If you change the path name in this way, you must use the IMON-GPN functions to redefine the logical ID/path name assignment and update the SCI.
The logical ID of an installation item is derived from the designator and unequivocally describes the installation item within its installation unit.
The logical ID is independent of the location of the file in the BS2000 system.
Format: <aaabbb>[.<extension>], e.g. SYSFGM.E
Note
In the case of software other than that supplied by Fujitsu Technology Solutions, the designator for an installation item can be in the format of the SDF data-type <filename 1..30 without-cat-user-gen-vers> without restrictive syntax rules.
Each release item has a logical ID defined in the SYSSII file and assigned to the path name on installation.
The logical ID enables users and other programs to identify and process the path name with the aid of the IMON-GPN functions.
The type of a release item or installation item determines the processing steps that must be performed for the item in question on installation. Additional information is defined in customizing (see "Installation preparation "). The accompanying document lists the type for each release item, complete with explanatory notes on the processing steps.
Examples
Release items of type “DAT” are installed without change in the system. Existing files are overwritten.
Release items of type “SDF” (syntax file) are treated in the same way as release items of type “DAT”. In addition, they can be activated or merged with the system syntax file (see figure 29 (Edit menu ) and figure 30 (Edit menu )).
- Release items of type *NP is a combination of the item types *PS and *NW.
It has been introduced for products for which the deinstallation in POSIX must be run with the old installation libraries (“SINLIBs”) also for the same main version.
Notes on POSIX-Processing
As for the type *PS, the type *NP describes the POSIX-satellites that can be deinstalled and installed automatically in the frame of the IMON installation in POSIX (via “POSIX Processing”).
The processing of the item types *PS and *NP differs only when the main version of the updated product remains the same.
In this case the following steps are schematically processed for *NP items:
1. creation of the new product files (“SINLIB”) with the suffix .NEW
2. POSIX package deinstallation on basis of the old product files
3. copy of the .NEW files on the files without suffix
4. POSIX package installation on basis of the new product files
In contrast the deinstallation of *PS items for same main version is run on basis of the new product files.
Remarks
1. The suffixes .NEW and .SAV are reserved for the processing of POSIX installation libraries (“SINLIBs”) of type *NP by IMON. The use of these suffixes for the renaming or the copy of POSIX installation libraries (of type *PS or *NP) leads to unexpected results.
The following table shows the contents of the various item types:
Item type | Contents |
DAT | Default file type |
MES | Message file (new format; message file created with MSGMAKER) |
SDF | SDF syntax file |
REP | RMS file for system corrections (reps) |
SSD | DSSM declaration file |
SSC | DSSM declaration file (new format; declaration file created with SSCM) |
SRC | Library with elements of the type S or M |
PL* | Library with elements of any type |
PLM | Library with elements of the type M |
PLR | Library with elements of the type R |
PLS | Library with elements of the type S |
DO | Procedure that can be called during execution of the installation procedure |
ENT | ENTER file that can be called during execution of the installation procedure and then deleted |
NST | Supply component that is not a BS2000 file (e.g. publication or data volume) |
%xx | Supply components for internal use, which have two alphanumeric characters xx, |
*DA | File of the type DAT, only of relevance for certain target versions |
*DC | File of DAT or *DA type that must also be copied under a specific name during installation |
*DF | Dummy installation item whose full installation path is specified |
*FE | Release Notice (English) |
*FG | Release Notice (German) |
*NW | File is assigned the standard suffix .NEW if it already exists in the target system prior to the installation |
*PS/*NP | POSIX item (mainly SINLIB) indicating that the linked item must be registered as a satellite in the POSIX system. |
The following table illustrates some examples of the connection between the path name, the logical name, the code for hardware dependency (TARGET), the item type, and contents of release items or installation items.
Path name | Logical name | TARGET | Type | Contents |
... .SYSLNK. ... | SYSLNK | A or S | DAT | Module library |
... .SKMLNK. ... | SYSLNK | K | DAT | Module library |
... .SKULNK. ... | SYSLNK | K | DAT | Module library |
... .SYSSSC. ... | SYSSSC | A | SSC | Subsystem declarations |
... .SYSSDF. ... | SYSSDF | A | SDF | SDF syntax file |
... .SYSMES. ... | SYSMES | A | MES | Message file |
... .SYSPRG. ... | SYSPRG | A or S | DAT | User program |
... .SYSFGM. ... .D | SYSFGM.D | A | *FG | Release Notice (German) |
... |
Installation items differ from the previous SYS files of the /390 mode in terms of their SKU and SKM usage classes:
Contents | /390 variant TPR and TU (as before) | x86 variant for TPR | x86 variant for TU |
Module library for dynamic reloading | SYSLNK.<product> | SKMLNK.<produc> | SKULNK.<product> |
Module library for static binding | SYSOML.<product> | SKMOML.<product> | SKUOML.<product> |
Program file (phase) | SYSPRG.<product> | - - - | - - - |
For the x86 variant the delivered and installed installation items are differentiated from each other using the usage classes SKU or SKM (e.g. SKULNK.<product> for a module library).