The Submit Job 2 tool is designed to allow you to submit a job and
use the defaults that are in the specified JOBD. SBMJOB2 differs
from the system supported SBMJOB command which uses *CURRENT for
several of the parameters meaning that the values of the current job
are passed into the batch job.
When system operators are submitting work on the behalf of other
users, or performing standard fixed tasks, it is often desirable to
use the JOBD values rather than *CURRENT.
Two commands are provided:
** SBMJOB2 - Defaults most parameters to *JOBD. The exceptions
are:
-- USER which defaults to *CURRENT.
-- RQSDTA which defaults to *CMD
A typical command would be entered as:
SBMJOB2 JOBD(xxxx) CMD('CALL xxxx')
This would submit a job requesting a CALL to the named
program. The user profile would be the current user. The
command comes from the CMD parameter. All other values would
come from the JOBD.
SBMJOB2 allows you to have job descriptions that may be
specific for an application area, but still allows the
submitter to determine the command to be run, The batch job
operates under the submitters user profile by default.
SBMJOB2 is close to the function performed by SBMJOB on S/38.
** SBMJOB3 - Defaults everything to *JOBD. This requires that
the submitter be authorized to the user profile in the *JOBD.
A typical command would be entered as:
SBMJOB3 JOBD(xxxx)
If the defaults are taken, the user must be authorized to the
user profile name in the JOBD. If the JOBD specifies
USER(*RQD), SBMJOB3 will fail. It is possible to specify
USER(*CURRENT) on SBMJOB3.
If the defaults are taken, the command to be run must exist as
the RQSDTA within the JOBD. It is possible to specify a
command in the RQSDTA parameter of SBMJOB3.
SBMJOB3 allows you to create very specific job descriptions
where everything is pre-specified in the JOBD.
Since the RQSDTA parameter of SBMJOB3 specifies *JOBD, any
value specified on the CMD parameter will be ignored (no error
message occurs). Because of the confusion this would
generate, only informed users should be authorized. See the
section on security.
Both SBMJOB2 and SBMJOB3 are created as duplicates from the system
supported SBMJOB command. The command processing program is the same
as the system SBMJOB. Therefore, all prompts, help text etc. are
the same. The only differences are in the command defaults.
Each command is secured by an authorization list.
** To use SBMJOB2, the user must be authorized to the TAASBMJOB2
authorization list.
** To use SBMJOB3, the user must be authorized to the TAASBMJOB3
authorization list.
Command parameters *CMD
------------------
The following describes the parameters where some change has
occurred:
---------- Defaults ------------
Parameter SBMJOB SBMJOB2 SBMJOB3
--------- ------ ------- -------
CMD Note 1 Note 1 Note 2
PRTDEV *CURRENT *JOBD *JOBD
OUTQ *CURRENT *JOBD *JOBD
USER *CURRENT *CURRENT *JOBD
PRTTXT *CURRENT *JOBD *JOBD
RQSDTA *CMD *CMD Note 2
SYSLIBL *CURRENT *SYSVAL *SYSVAL
CURLIB *CURRENT *USRPRF *USRPRF
INLLIBL *CURRENT *JOBD *JOBD
All the other parameters in the JOBD default to *JOBD or are not
pertinent.
The SYSLIBL parameter does not use a *JOBD value because it is not
supported in the JOBD. The *SYSVAL default, provides a general use
solution.
The CURLIB parameter does not use a *JOBD value because it is not
supported in the JOBD. The *USRPRF default, provides a general use
solution.
Note 1. The CMD parameter is not strictly required for
SBMJOB2. It is not a parameter in the JOBD.
However, if you don't enter the CMD parameter and
are using the system supplied routing entries,
unless the RQSDTA parameter has a value on SBMJOB or
in the JOBD, the batch job will run without any
function being performed. For typical situations,
good practice says to always use the CMD parameter.
Note 2. The intent of SBMJOB3 is that the command to be run
be pre-established in the JOBD using the RQSDTA
parameter.
Because of the *JOBD default for RQSDTA, any command
entered for the CMD parameter is ignored.
If you are using the system supplied routing entries
and the JOBD does not have RQSDTA and none was
specified on SBMJOB3, the batch job will run without
any function being performed.
Security
--------
The SBMJOB2 command is created with the *PUBLIC being excluded. The
SBMJOB2 authorization is controlled by the authorization list
TAASBMJOB2. Use EDTAUTL to add users to the authorization list.
The SBMJOB3 command is created with the *PUBLIC being excluded. The
SBMJOB3 authorization is controlled by the authorization list
TAASBMJOB3. Use EDTAUTL to add users to the authorization list. Be
sure that any users of SBMJOB3 understand that they cannot use the
CMD parameter.
Command parameters
------------------
The parameters are the same as the SBMJOB command with the exception
that the defaults have been changed as described previously.
Restrictions
------------
None.
Prerequisites
-------------
None.
Implementation
--------------
The tool is ready to use, but the users of the commands must be
authorized to the corresponding authorization lists.
For SBMJOB2, use EDTAUTL for the TAASBMJOB2 authorization list.
For SBMJOB3, use EDTAUTL for the TAASBMJOB3 authorization list.
Objects used by the tool
------------------------
Object Type Attribute Src member Src file
------ ---- --------- ---------- ----------
No object TAAJOBQ QATTCMD
No object TAAJOBQ2 QATTCMD
SBMJOB2 *CMD No source
SBMJOB3 *CMD No source
The command source is used for documentation only. The commands are
created using CRTDUPOBJ from the system SBMJOB command. The defaults
are changed using CHGCMDDFT. The CPP is the same as the system
SBMJOB command.
|
