Since the initial documentation of SPOOLJOB in FR80 User Note 3, several new parameters have become available. These are listed below.
This appends an entry to the file LOG(/LOG) in the user's proper directory stating the Deletion Code for SPOOLJOB. This file is automatically listed and erased when the user does a STATE. (See 1906A User Notes 42 and 46.) A full list of all Deletion Codes used by SPOOLJOB is given below.
If neither EJ nor MOPEJ are specified, SPOOLJOB will exit-on termination. An EJ causes the job to obey an Endjob - a monitoring file will only be produced if the job does not delete properly.
If this parameter is present, then a broadcast is sent to the user when the job finishes - if he is. logged in on the same username with the jobname given. This parameter also causes LOG to be obeyed.
If neither EJ nor MOPEJ are given the macro performs an exit.
The urgency parameter has three legal values for 'a' .
URH Urgency High URM Urgency Medium (this is the default) URZ Urgency Low (it is not expected that this will be used)
See 1906A User Note 54.
The use of the PLOT parameter does not remove any delay which the user has set on his spooled job. If PLOTNOW is supplied to SPOOLJOB as a parameter then the delay is set to zero and the job is flagged to be plotted. This causes the job to be despooled at the next opportunity.
If for some reason the user does not wish his output to be sent to the file SPOFILE (1/FRME), he may specify a filename (using the *TP parameter) to which he wishes his output to be sent. The directory is that from which SPOOLJOB was issued.
It should be noted that the JT and UR parameters have no effect when SPOOLJOB is issued by a runjob and these should be specified in the JD parameter in the normal way.
SPOOLJOB can detect a number of errors, some of which may be called fatal, others non-fatal. Some of these errors cause any PLOT/ERASE action specified to be ignored and this is best summarised by means of the following table. All errors produce a message on the monitoring file which will be automatically listed.
CODE | REASON | PLOT/ERASE ACTION TAKEN |
---|---|---|
ER | The specified jobname is not on the spool or this user did not produce the area | NO |
PE | This indicates that SPOOLJOB was called with no parameters | NO |
CS | Checksum error on Spool. This indicates that no FR80 ENDJOB ORDER was detected and usually indicates that the user job terminated abnormally | YES |
PM | Indicates that one or more invalid parameters were detected. Invalid parameters are ignored and processing continues with next valid parameters | YES |
OK | Normal termination of SPOOLJOB | YES |
D2 | Indicates a disc error in reading data | NO |
XX | SPOOLJOB detected an order it could not translate. This is a probable error in SPOOLJOB | NO |
00 | Indicates that the FR80 Endjob instruction was encountered whilst the user was frame skipping | NO |
The following have also changed since the initial documentation on SPOOLJOB: