Execution of JMU

JMU creates the ISAM file SJMSFILE. The file name is ascertained from the task file table (link name SJMSFILE) and can be defined with. If the file already exists, JMU updates it:

/ADD-FILE-LINK LINK-NAME=SJMSFILE,FILE-NAME=<filename>

The file need not necessarily exist before /ADD-FILE-LINK is executed, or it can exist and be empty. In both cases, it is created by JMU.

/ADD-FILE-LINK is not mandatory. If the link name SJMSFILE has not been assigned, JMU processes the file with the file name SJMSFILE as before and automatically assigns the link name SJMSFILE to it.

The user must not assign the link name SJMSFILE to a file which is not to be processed by JMU.

The program is started using /START-JMU.

START-JMU                                                                 Alias: JMU

VERSION = *STD / <product-version>

,MONJV = *NONE / <filename 1..54 without-gen-vers>

,CPU-LIMIT = *JOB-REST / <integer 1..32767 seconds>

JMU is controlled by means of control statements read from SYSDTA.

JMU uses the dialog interface SDF (see the “Commands” manual [1 (Related publications)] and the “SDF Dialog Interface” manual [20 (Related publications)]). Syntax errors in interactive mode cause a correction dialog to be initiated with the user. A correction dialog is not possible in batch or procedure mode, but SDF does not allow the statement to be simply ignored. All the statements following an incorrect statement are skipped until the system encounters a STEP or END statement. Processing then continues with the statement (or command) following the STEP or END statement. Message CMD0230 is output to inform the user that statements have been omitted.

The SJMSFILE file is updated in the same session in which the control statements were given. However, the updates do not have any effect until the next session.
The desired changes should be entered in a copy of the SJMSFILE, and the updated file used in a session only when the changes have been verified as correct

It is advisable to maintain a copy of the SJMSFILE, or a procedure for reconstructing it.

There is a risk that it will not be possible to process the SJMSFILE file using the job management systems of operating system versions later than the one used to create the file. It is therefore recommended that a copy of the JMU control statements be preserved for reconstructing the file in a new version of the operating system.

 

Use of link names by JMU

JMU evaluates the link names SJMSFILE and SJMUPROC. If the SJMSFILE link name is already defined in the task file table, the corresponding file is processed by JMU. Otherwise, SJMSFILE is used as the file name.

When the CREATE-PROCEDURE-FILE statement is processed, the link name
SJMUPROC is evaluated and assigned to a file where necessary. This link name should therefore only be used in the cases described under the CREATE-PROCEDURE-FILE statement.

Compatibility

Inconsistencies may occur when a SJMSFILE is processed by an earlier version of JMU than that under which the SJSMFILE was created.