LINC Programming Reference Manual - Public Support Login - Unisys

START (ST)
To avoid duplication, LINC will only restart jobs in Ispec or Report recovery, where those
START; commands were apparently not successfully executed for those jobs prior to the
failure. START; commands that were successfully executed prior to the failure will be
ignored.
If the failure is due to a system halt/load, the MCP will automatically restart all jobs that
were active at the time of the interruption.
The chargecode that applies to your WFL start is dependent on the values of the :COD LINC
System command and the GLB.CHARGECODE System Data item. For further details, see
$ ‘‘GLB.CHARGECODE’’, in this manual
$
$
"Setting Chargecodes for LINC Systems and Reports" in your MCP Based LINC
Administration and Operations Guide
"Report and WFL Job Chargecodes" in your MCP Based LINC Administration and
Operations Guide
For an OS 2200 based LINC System
The START; command executes an OS 2200 based ECL runstream. The request is passed to
the LINC Background Run which performs an @START of the runstream. Consequently,
the run is executed under the same account/userid as the LINC Background Run.
No status is returned on the success or otherwise of the runstream.
There is only one parameter for the START; command. This is the element name of the
runstreams. No parameters can be passed to the runstream.
All runstreams to be accessed by the START; command must be copied into the following
file:
GLB.STATUS is set to indicate the result of the START; command, as shown in the
following table.
Value Result Indicated
INVAL The runstream cannot be located.
Space The LINC Background Run has been instructed to start the runstream. If for some
reason it cannot be started, EXEC will reject the START command from the LINC
Background Run, the runstream will not be started, and LINC logic will not receive
error notification.
1-242 v