Start file

Users have the option of creating a SAM or ISAM file which will be processed automatically when LMS is started. The file may contain any LMS statements desired. The LMS statements which are to be executed automatically when LMS is started may also be stored in a library member.

SYSDTA must have the value PRIMARY or SYSCMD when LMS is started or the sequence of start statements will not be executed. After the start file has been processed, SYSDTA is reset to its original value.

LMS searches for the start file as follows:

1. via the S variable SYSLMSPAR

2. via the link name $LMSPAR

3. under the file name SYSPAR.LMS

4. via the global start file

The system administrator can select any installation location for the global start file. The logical identification SYSPAR is defined for this global start file in the SYSSII file.

The system administrator informs the installation monitor of the installation file name using the SET-INSTALLATION-PATH command. If no installation file name is defined for the global start file, a global start file is sought via the file name $.SYSPAR.LMS.

The names $LMSPAR, SYSLMSPAR, SYSPAR.LMS and the global start file must not be used except in conjunction with the start file. Using any of these names for other purposes, for example SYSPAR.LMS as the name of a PLAM library, may lead to errors when LMS starts. Following output of an error message, the LMS run is continued.

The S variable SYSLMSPAR must contain a valid value of the TO-FILE= operand of the ASSIGN-SYSDTA command (see the ASSIGN-SYSDTA command in [4 (Related publications)]). In other words, the variable may contain the name of a file or a library member in the form *LIB-ELEM(LIB=...,ELEM=...,TYPE=...).

The S variable must be declared with SCOPE=TASK if it is to be set in a procedure (e.g. the LOGON procedure) yet still be accessible outside the procedure for other LMS runs. Otherwise, the variable need not be declared.

The start file can be switched off with /ADD-FILE-LINK FILE-NAME=*DUMMY,LINK-NAME=$LMSPAR, provided the sequence of start statements is not referenced using the variable SYSLMSPAR. If the variable exists but should not cause the sequence of start statements to be executed, the variable must contain the string *DUMMY.

Examples

• The values LOGGING=*MAXIMUM and TYPE=S are to be preset in the SYSPAR.LMS file.

  The start file contains the statements:

  //MODIFY-LOGGING-PARAMETERS LOGGING=*MAXIMUM

  //MODIFY-LMS-DEFAULTS TYPE=S

  Following the /START-LMS call, the above values are set automatically.

• This time, the start statements are to be stored in the START member under type S in the library X.

  The S variable SYSLMSPAR contains:

  /SYSLMSPAR=’*LIB-ELEM(LIB=X,ELEM=START,TYPE=S)’

  The START member contains the statements:

  //MODIFY-LOGGING-PARAMETERS LOGGING=*MAXIMUM

  //MODIFY-LMS-DEFAULTS TYPE=S

  Following the /START-LMS call, the above values are set automatically.