The MARENCP control program must execute under the user ID SYSMAREN or another user ID with the TAPE-ADMINISTRATION privilege.
The MAREN subsystem cannot be activated until after the MARENCP task has been started during a BS2000 session. Prior to this, all interactive tasks involving tape processing are rejected, and all batch tasks wait for input from the operator. Therefore, when starting up a system, suitable start procedures must be used to ensure that the MAREN control program and the MAREN subsystem are activated.
In order to test MARENCP, you can use the system-specific MAREN parameter TEST-MODE to run the program in test mode. After the test phase has concluded, test mode must once again be disabled, see the MARENADM statement MODIFY-MAREN-PARAMETERS.
Starting MARENCP
The MARENCP control program is started by issuing the START-MARENCP command. MARENCP can also be called using START-EXECUTABLE-PROGRAM command for compatibility reasons.
| START-MARENCP | Alias: MARENCP | ||||||||
| |||||||||
VERSION =
The selected MARENCP version is used.
VERSION = *STD
Before MARENCP is called, the version is set by means of the SELECT-PRODUCT-VERSION command (in system mode). This set version is used as the default version.
VERSION = <product-version mandatory-man-corr>
Full version identifier.
VERSION = <product-version mandatory-man-without-corr>
Version identifier excluding the correction status.
VERSION = <product-version without-man-corr>
Version identifier excluding the release and correction status.
MONJV =
Specification of a job variable for monitoring the MARENCP run.
MONJV = *NONE
A monitor job variable is not used.
MONJV = <filename 1..54 without-gen-vers>
Explicit specification of the job variable for monitoring the MARENCP run.
CPU-LIMIT =
Maximum CPU time in seconds allocated for the program.
CPU-LIMIT = *JOB-REST
The remaining CPU time is to be used for the job.
CPU-LIMIT = <integer 1..32767 seconds>
Only the specified time is to be used.
Terminating MARENCP
MARENCP is terminated properly with the MARENADM statement STOP-CONTROL-PROGRAM. All open files of the MAREN catalog are closed.
In the event of severe errors, the control program terminates with a dump. The spin off is triggered in a procedure or ENTER file.
If the errors that lead to termination of the MARENCP run are easy to diagnose and therefore do not require a dump, they are simply logged by MARENCP. Appropriate messages are issued to SYSOUT and/or console and task switch 29 is set.