Contents Index JAMS Home Support

Submits a JAMS based batch job.

Format

SUBMIT job-name-list

Parameters

job-name-list

The job-name-list parameter is the name of one or more Setup or Job definitions. If the job-name-list parameter contains more than one name, the names must be separated by commas.

You can submit a Job on a remote node by specifying the remote node name and access control information in the standard DECnet format.

Description

The SUBMIT command is very similar to the standard OpenVMS SUBMIT command. However, the JAMS version of the SUBMIT command is used to submit a JAMS Job or Setup definition, rather than a command file.

The JAMS SUBMIT command is used to submit one or more JAMS Jobs. You will be prompted for values for the Job's parameters and Report overrides. This prompting can be disabled with the /NOPROMPT qualifier.

Qualifiers

OpenVMS SUBMIT Command Qualifiers

The following table lists the level of support provided by the JAMS SUBMIT command for the qualifiers supported by the standard OpenVMS SUBMIT command.

Qualifier	Support Provided
/AFTER	Supported
/BACKUP	NOT Supported
/BEFORE	NOT Supported
/BY_OWNER	NOT Supported
/CHARACTERISTICS	Supported
/CLI	Supported
/CONFIRM	NOT Supported
/CPUTIME	Supported
/CREATED	NOT Supported
/DELETE	Supported
/EXCLUDE	NOT Supported
/EXPIRED	NOT Supported
/HOLD	Supported
/IDENTIFY	Supported
/KEEP	Supported
/LOG_FILE	Supported
/MODIFIED	NOT Supported
/NAME	Supported
/NOTIFY	Supported
/PARAMETERS	Supported
/PRINTER	Supported
/PRIORITY	Supported
/QUEUE	Supported
/REMOTE	NOT Supported
/RESTART	Supported
/SINCE	NOT Supported
/USER	Supported
/WSDEFAULT	Supported
/WSEXTENT	Supported
/WSQUOTA	Supported

In addition to the supported OpenVMS SUBMIT command qualifiers, the following JAMS specific qualifiers are available:

/AGENT=agent-node

The /AGENT qualifier is used to specify the node name where this job's execution request should be sent. This node must be running the JAMS Agent or, if this is an rexec job, an rexec server.

/DEBUG

/NODEBUG (default)

The /DEBUG qualifier specifies that Jobs should be submitted in debug mode. This mode is used by programmers to test and debug Jobs. When a Job is submitted in debug mode, it is always submitted under the OpenVMS username of the person making the request. If the System definition specifies a OpenVMS username, it is ignored.

When submitting a Job in debug mode, the logical names used during Job parsing do not need to be defined at the executive level. This enables a programmer to define logical names in their process specific logical name tables which will direct the JAMS parsing routines to a test version of the Job source files and/or the Systems template library.

/DEPENDENCIES=(entry[,...])

The /DEPENDENCIES qualifier is used to force a Job to wait in a batch queue until the specified jobs have completed successfully. You specify the Jobs by their JAMS entry numbers. You can specify up to 32 entry numbers. If you specify only one entry number, you can omit the parentheses.

This qualifier is very useful when you want to create a stream of Jobs. You can create one Job which submits all of the Jobs in the stream using this qualifier to define the stream dependencies.

/JOB

The /JOB qualifier is used when you want to submit a Job definition without searching for a Setup definition first. If the /JOB qualifier is present, a Job with the specified name will be searched for, and if it is found, submitted. Using this qualifier is the only way to submit a Job which has the same name as a Setup definition.

The default action, if neither /SETUP or /JOB are specified, is to search first for a Setup, then if the Setup was not found, search for a Job with the given name.

This is a positional qualifier. If it is supplied after the SUBMIT command, it applies to all of the names in the Job name list. If it is supplied after a name in the Job name list, it applies only to the preceding name.

/PROMPT (default)

/NOPROMPT

If you specify /NOPROMPT, you will not be prompted for the values for a Job's parameters or Report overrides. Default values are taken instead.

/SET_SYMBOLS

/NOSET_SYMBOLS (default)

If you specify /SET_SYMBOLS, a DCL symbol will be defined, or updated, for each of the Job's parameters. The symbol name will be the same as the parameter name, and the value will be the value used when submitting the Job.

If a symbol is being created, it is created in the local symbol table. If it is being updated, it is updated in whichever table it is currently defined.

/SETUP

The /SETUP qualifier is used when you want to submit a Setup definition. If the /SETUP qualifier is present, a Job with the specified name will not be searched for, and if the Setup does not exist, an error will be returned.

The default action, if neither /SETUP or /JOB are specified, is to search first for a Setup, then if the Setup was not found, search for a Job with the given name.

This is a positional qualifier. If it is supplied after the SUBMIT command, it applies to all of the names in the Job name list. If it is supplied after a name in the Job name list, it applies only to the preceding name.

/SUBMIT (default)

/NOSUBMIT

The /NOSUBMIT qualifier is useful when you are testing a Job definition or a template library. If you specify /NOSUBMIT, the job is not submitted to a batch queue. Instead, a file is created in the current default directory with the name of the Job and an extension of .JAMS. This file contains the parsed Job Source file exactly as it would be submitted to a batch queue.

/USE_SYMBOLS (default)

/NOUSE_SYMBOLS

If the /USE_SYMBOLS qualifiers is specified, either explicitly or by default, when JAMS is building a parameter screen, it will use the value of DCL symbols whose names match a parameter's name for the parameter's default value.

When JAMS determines the default value for a parameter, it takes the following steps:

1. Use the default value entered in the parameter definition.
2. If a Setup is being submitted, use the default value from the Setup's parameter screen.
3. If /USE_SYMBOLS is specified, see if there is a DCL symbol with the same name as the parameter and use the symbol's value, if defined.
4. If a value was specified with the /PARAMETER qualifier, use the specified value.

EXAMPLES

JAMS> SUBMIT MYJOB
      

This example searches for a Setup named MYJOB. If a Setup with this name is not found, it searches for a Job named MYJOB. If one of these is found, you are prompted for the Job's parameters, and then for the scheduled date and time and any report overrides.

JAMS> SUBMIT APPLE::MYJOB
      

This example searches the JAMS database on the remote node APPLE for a Setup named MYJOB. If a Setup with this name is not found, it searches for a Job named MYJOB. If one of these is found, you are prompted for the Job's parameters, and then for the scheduled date and time and any report overrides. The Job or Setup is submitted on node APPLE.

JAMS> SUBMIT/NOSUBMIT TESTJOB
      

This example does not actually submit a Job. It will go through the normal job submission sequence but, instead of submitting the job, it will create a file named TESTJOB.JAMS in the current default directory. This file contains the parsed and expanded command file of the job TESTJOB. The /NOSUBMIT qualifier is used to test parameter substitution and template expansion.

Copyright © 2000, MVP Systems, Inc. All rights reserved.