cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual



 o T Y  
PreviousContentsIndex



FIt is recommended that resources be listed in the RESOURCE list using %the editor as opposed to this method.

/SUBMIT=ACCOUNT:text

HThe ACCOUNT field will specify which account to charge the batch job to Gwhen submitted. This is an eight-character field. The privilege CMKRNL #is required to use this qualifier .'

/SUBMIT=CHARACTERISTICS:number

FThe CHARACTERISTICS field will specify the number of a characteristic +to be associated with the job. 2

/SUBMIT=CLI:name

HThe CLI field will specify the command language interpreter (CLI) to be Gused to process the job. The file specification will assume the device Fname SYS$SYSTEM: and the file type EXE (SYS$SYSTEM:filename.EXE). The Bdefault CLI is that defined in the user authorization file (UAF) .#

/SUBMIT=CPUTIME:delta_time

DCPUTIME will define a CPU time limit for the batch job. Time can be Hspecified as delta time, or as 0 or NONE (no limit on the time). If the Hqueue on which the job will execute has a defined CPUMAXIMUM value, the 8smaller of the PROCESS command and queue values is used.

/SUBMIT=DELETE



/SUBMIT=NODELETE

GThe DELETE field will control whether or not command files are deleted 2after processing. The default setting is NODELETE.

/SUBMIT=HOLD



/SUBMIT=NOHOLD

DThe HOLD field will place the job into a queue in the HOLD state. A Esubsequent DCL SET QUEUE/ENTRY command will be needed to release the 1job for execution. The default setting is NOHOLD.

/SUBMIT=KEEP



/SUBMIT=NOKEEP

?The KEEP field will indicate that the log file produced by the Hexecution of the job is to be kept and not deleted. The default setting is KEEP.#

/SUBMIT=LOG_FILE:file_spec



/SUBMIT=NOLOG_FILE

FThe LOG_FILE field specifies the name of the job log file. By default Fthe file is placed in the user's login directory. The default name is *the job name and the default type is .LOG.

/SUBMIT=NAME:text

HThe NAME field allows a different name (from that of the job itself) to 8be used when the job is entered into an execution queue.

/SUBMIT=NODE:node_name

@The NODE field indicates which node is to process the job. In a Hcluster, it is assumed that any node can process a job for execution on behalf of any cluster member.(

/SUBMIT=PARAMETER:(p1,p2,...p8)

DThe PARAMETER datum will provide the values of up to eight optional Dparameters (p1,p2,...p8) for each command procedure in the job. The Gsymbols are local to the specified command procedure. Characters other Athan alphanumeric characters must be included in quotation marks.#

/SUBMIT=PRINTER:queue_name



/SUBMIT=NOPRINTER

HThe PRINTER datum will queue the job log file for printing when the job Dis completed. PRINTER allows the user to specify a particular print ,queue. The default print queue is SYS$PRINT.(

/SUBMIT=PRIORITY:queue_priority

FThe PRIORITY field will specify what queue priority level to use when )entering the job into an execution queue.!

/SUBMIT=QUEUE:queue_name

GThe QUEUE field will identify the batch queue on which the job will be (entered. The default queue is SYS$BATCH.

/SUBMIT=RESTART



/SUBMIT=NORESTART

HThe RESTART field will mark the created job as being restartable. Thus, Eif the job is restarted during execution, the DCL symbol $RESTART is Fset to true. Then the user provided command procedure will check this ?value and continue execution as needed. The default setting is NORESTART.

/SUBMIT=RETAIN



/SUBMIT=NORETAIN

FFlag as retained in batch queue. Also determines whether the job will Cbe retained if delete_upon_completion is ON and the job fails. The default setting is NORETAIN.

/SUBMIT=USER:username

EThe USER field indicates on who's behalf the job is to be processted Ffor execution. Normally this user name is the same as person who owns 8the job. To change this field requires CMKRNL privilege.7

/SUBMIT=VARIABLE:(var1=value, var2=value etc.)

DThe VARIABLE qualifier creates or modifies one or more existing job Hvariables. If the job variable exists in the Notes cosection of the job /it will be modified, if not it will be created."

/PROCESS=WSDEFAULT:number

GThe WSDEFAULT field will define for a batch job a working set default, Hthe default number of physical pages that the job can use. If the queue Don which the job is executed has a nonzero working set default, the Fsmaller of the specified job and queue values is used. If the default Gset is 0, the smaller of the specified job and user authorization file (UAF) values is used.!

/PROCESS=WSEXTENT:number

EThe WSEXTENT field will define for a batch job a working set extent, Dthe maximum amount of physical memory that the job can use. The job Duses the maximum amount of physical memory only when the system has Cexcess free pages. If the queue on which the job is executed has a Gnonzero working set extent, the smaller of the specified job and queue Fvalues is used. If the default set is 0, the smaller of the specified 5job and user authorization file (UAF) values is used.

/PROCESS=WSQUOTA:number

GThe WSQUOTA field will define for a batch job a working set quota, the Famount of physical memory that the job is guaranteed. If the queue on Gwhich the job is executed has a nonzero working set quota, the smaller Hof the specified job and queue values is used. If the default set is 0, Cthe smaller of the specified job and user authorization file (UAF) values is used. 



/   
N
Note

 G

2 Please refer to the VMS DCL A Dictionary under the PROCESS command for a more complete  description








 o V T Y  
PreviousNextContentsIndex