Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Installation Definition File (IDF file)

&pagelevel(4)&pagelevel

Products can be registered in the SCI even if they were not installed with IMON. The user must generate an IDF (Installation Definition File) for these products.

An installed product corresponds to an installation unit. The individual installed product files correspond to the installation items.

The IDF file generated in this way is the input file for the Add... menu option in the Edit menu or the ADD-INSTALLATION-UNITS statement for registering in the SCI the installation units and installation items contained in the file.

Structure of the IDF file

The IDF is a SAM or ISAM file with a maximum record length of 2032 bytes. Any suitable editor can be used to generate and edit the IDF.

The individual records are structured in accordance with the syntax rules described below.

The syntax consists of keywords (in uppercase letters) and parameters. The rules are as follows:

  • Blanks and end-of-record markers are separators. Multiple consecutive blanks or endof-record markers are interpreted as one separator.

  • A comment is introduced by the keyword *REMARK.

  • Square brackets [...] enclose optional information.

  • Uppercase and lowercase letters are permissible.

  • You can specify multiple *ITEM ... *FILE lines for a *UNIT. Multiple *UNIT ... *ITEM ... *FILE specifications can be strung together.

  • An installation unit (*UNIT) cannot be described more than once in an IDF.

  • An installation item (*ITEM) can be defined only once in an installation unit (*UNIT).

Syntax in the IDF

*UNIT <IU-name>'BLANK'<IU-version>'BLANK'<IU-correction-state> 
     *ITEM [<II-name>'BLANK'<II-version>'BLANK'<II-type>] 
           *FILE <filename 1..54 with-cat-user without-gen-vers>

Description of the keywords and parameter values

*UNITDescription of an installation unit (see "Installation unit (IU) ")

<IU-name>

Name of the installation unit Syntax: <text 1..30 without-sep>.

<IU-version>

Version designation of the installation unit. format: “[m]m.n”

<IU-correction-state>

Correction state of the installation unit. Must consist of one alpha character followed by two digits

Syntax: <alphanum-name 3..3>


Example: A00.

*ITEM

Description of an installation item (see "Installation item (II) ") belonging to the preceding installation unit.

<II-name>

Name of the installation item

Syntax: <filename 1..30 without-cat-user-gen-vers>

<II-version>

Version of the installation item. The value set can be up to 5 characters in length

Syntax: <char 1..5>

<II-type>

                                           

Type of the installation item (see "Path name, logical ID and type of an installation item ")

Syntax: <char 3..3>



*FILE

                                           

The path name of the installation item with catalog and user IDs

Syntax: <filename 1..54 with-cat-user without-gen-vers>


The following substitutions are automatic:

  • If the path name has an alias, the alias is substituted

  • A default is inserted if the user ID is omitted (user ID of the current task or TSOS, if the TSOS privilege is available)

  • $.<name> causes the system default user ID (DEFLUID) to be inserted

  • The standard catalog ID (DEFCAT) of the user ID is inserted if the catalog ID is omitted

Example of an IDF file for ARCHIVE

ARCHIVE V9.0 was installed without IMON and is now to be registered in the SCI file via an IDF file using the ADD-INSTALLATION-UNITS statement (or the corresponding Add ... option in the Edit menu):

*REMARK Example of an IDF file for ARCHIVE 
*UNIT   ARCHIVE 12.0   C00
   *ITEM   SKMLNK.ARCHIVE.120.TPR      001   DAT
           *FILE  :AB01:$TSOS.SKMLNK.ARCHIVE.120.TPR
   *ITEM   SYSFGM.ARCHIVE.120.D        001   *FG
           *FILE  :AB01:$TSOS.SYSFGM.ARCHIVE.120.D
   *ITEM   SYSFGM.ARCHIVE.120.E        001   *FE
           *FILE  :AB01:$TSOS.SYSFGM.ARCHIVE.120.E
   *ITEM   SYSLIB.ARCHIVE.120          001   DAT
           *FILE  :AB01:$TSOS.SYSLIB.ARCHIVE.120
   *ITEM   SYSLNK.ARCHIVE.120          001   DAT
           *FILE  :AB01:$TSOS.SYSLNK.ARCHIVE.120
   *ITEM   SYSLNK.ARCHIVE.120.TPR      001   DAT
           *FILE  :AB01:$TSOS.SYSLNK.ARCHIVE.120.TPR
   *ITEM   SYSMES.ARCHIVE.120          001   MES
           *FILE  :AB01:$TSOS.SYSMES.ARCHIVE.120
   *ITEM   SYSNRF.ARCHIVE.120          001   DAT
           *FILE  :AB01:$TSOS.SYSNRF.ARCHIVE.120
   *ITEM   SYSPAR.ARCHIVE.120          001   *NW
           *FILE  :AB01:$TSOS.SYSPAR.ARCHIVE.120
   *ITEM   SYSPRG.ARCHIVE.120          001   DAT
           *FILE  :AB01:$TSOS.SYSPRG.ARCHIVE.120
   *ITEM   SYSPRG.ARCHIVE.120.DIRCONV  001   DAT
           *FILE  :AB01:$TSOS.SYSPRG.ARCHIVE.120.DIRCONV
   *ITEM   SYSREP.ARCHIVE.120          001   *DF
           *FILE  :AB01:$TSOS.SYSREP.ARCHIVE.120
   *ITEM   SYSRME.ARCHIVE.120.D        001   *FG
           *FILE  :AB01:$TSOS.SYSRME.ARCHIVE.120.D
   *ITEM   SYSRME.ARCHIVE.120.E        001   *FE
           *FILE  :AB01:$TSOS.SYSRME.ARCHIVE.120.E
   *ITEM   SYSRMS.ARCHIVE.120          001   REP
           *FILE  :AB01:$TSOS.SYSRMS.ARCHIVE.120
   *ITEM   SYSSDF.ARCHIVE.120          001   SDF
           *FILE  :AB01:$TSOS.SYSSDF.ARCHIVE.120
   *ITEM   SYSSII.ARCHIVE.120          001   DAT
           *FILE  :AB01:$TSOS.SYSSII.ARCHIVE.120
   *ITEM   SYSSSC.ARCHIVE.120          001   SSC
           *FILE  :AB01:$TSOS.SYSSSC.ARCHIVE.120