Create Job Description (CRTJOBD)

The Create Job Description (CRTJOBD) command creates a job description object that contains a specific set of job-related attributes that can be used by one or more jobs. The attributes determine how each job is run on the system. The same job description can be used by multiple jobs. The values in the job description are usually used as the default values of the corresponding parameters in the Batch Job (BCHJOB) and Submit Job (SBMJOB) commands when their parameters are not specified.

The values in the job description can be overridden by the values specified on the BCHJOB and SBMJOB commands.

Restrictions:

To use this command, you must have:
- read (*READ) and add (*ADD) authority to the library where the job description is to be created.
- use (*USE) authority to the user profile specified on the User (USER) parameter.
To create a job description with an accounting code other than *USRPRF, you must have *USE authority to the Change Accounting Code (CHGACGCDE) command.

Parameters

Keyword	Description	Choices	Notes
JOBD	Job description	Qualified object name	Required, Positional 1
	Qualifier 1: Job description	Name
	Qualifier 2: Library	Name, *CURLIB
JOBQ	Job queue	Qualified object name	Optional, Positional 3
	Qualifier 1: Job queue	Name, QBATCH
	Qualifier 2: Library	Name, LIBL, CURLIB
JOBPTY	Job priority (on JOBQ)	1-9, 5	Optional
OUTPTY	Output priority (on OUTQ)	1-9, 5	Optional
PRTDEV	Print device	Name, USRPRF, SYSVAL, *WRKSTN	Optional
OUTQ	Output queue	Single values: USRPRF, DEV, WRKSTN Other values: Qualified object name*	Optional
	Qualifier 1: Output queue	Name
	Qualifier 2: Library	Name, LIBL, CURLIB
TEXT	Text 'description'	Character value, *BLANK	Optional
USER	User	Name, *RQD	Optional, Positional 2
ACGCDE	Accounting code	Character value, USRPRF, BLANK	Optional
PRTTXT	Print text	Character value, SYSVAL, BLANK	Optional
RTGDTA	Routing data	Character value, QCMDI, *RQSDTA	Optional
RQSDTA	Request data or command	Character value, NONE, RTGDTA	Optional
INLLIBL	Initial library list	Single values: SYSVAL, NONE Other values (up to 250 repetitions): Name	Optional
INLASPGRP	Initial ASP group	Name, *NONE	Optional
LOG	Message logging	Element list	Optional
	Element 1: Level	0-4, 4
	Element 2: Severity	0-99, 0
	Element 3: Text	NOLIST, MSG, *SECLVL
LOGCLPGM	Log CL program commands	NO, YES	Optional
LOGOUTPUT	Job log output	SYSVAL, JOBLOGSVR, JOBEND, PND	Optional
JOBMSGQMX	Job message queue maximum size	2-64, *SYSVAL	Optional
JOBMSGQFL	Job message queue full action	SYSVAL, NOWRAP, WRAP, PRTWRAP	Optional
SYNTAX	CL syntax check	0-99, *NOCHK	Optional
ENDSEV	End severity	0-99, 30	Optional
INQMSGRPY	Inquiry message reply	RQD, DFT, *SYSRPYL	Optional
HOLD	Hold on job queue	NO, YES	Optional
DATE	Job date	Date, *SYSVAL	Optional
SWS	Job switches	Character value, 00000000	Optional
DEVRCYACN	Device recovery action	SYSVAL, MSG, DSCMSG, DSCENDRQS, ENDJOB, ENDJOBNOLIST	Optional
TSEPOOL	Time slice end pool	SYSVAL, NONE, *BASE	Optional
AUT	Authority	Name, LIBCRTAUT, CHANGE, ALL, USE, *EXCLUDE	Optional
ALWMLTTHD	Allow multiple threads	NO, YES	Optional
SPLFACN	Spooled file action	SYSVAL, KEEP, *DETACH	Optional
DDMCNV	DDM conversation	KEEP, DROP	Optional

Top

Job description (JOBD)

Specifies the name and library of the job description being created.

This is a required parameter.

Qualifier 1: Job description

name: Specify the name of the job description.

Qualifier 2: Library

*CURLIB: The current library for the thread is used to locate the object. If no current library entry exists in the thread's library list, the library QGPL is used.
name: Specify the library where the object is located.

Job queue (JOBQ)

Specifies the name and library of the default job queue where jobs submitted using this job description are placed.

Qualifier 1: Job queue

QBATCH: The QBATCH job queue is the queue where the jobs are placed.
name: Specify the name of the job queue.

Qualifier 2: Library

*LIBL: All libraries in the thread's library list are searched until a match is found.
*CURLIB: The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.

name: Specify the library where the job queue is located.

Note: If the job queue does not exist when the job description is created, a library qualifier must be specified because the name of the qualified job queue is kept in the job description.

Print device (PRTDEV)

Specifies the qualified name of the default printer device for this job. If the printer file being used to create the output specifies to spool the file, the spooled file is placed on the device's output queue, which is named the same as the device.

Note: This assumes the defaults are specified on the Output queue (OUTQ) parameter for the printer file, job description, user profile and workstation.

*USRPRF: The printer device name for jobs that use this job description is taken from the user profile associated with the job at the time the job is started.
*SYSVAL: The value in the system value QPRTDEV at the time the job is started is used as the printer device.
*WRKSTN: The printer device used with this job description is the printer device assigned to the work station that is associated with the job at the time the job is started.
name: Specify the printer device to be used by jobs that use this job description.

Output queue (OUTQ)

Specifies the name and library of the output queue used as the default output queue for jobs that use this job description. This parameter applies only to spooled printer files that specify *JOB for the output queue.

Single values

*USRPRF: The output queue for jobs using this job description is obtained from the user profile associated with the job at the time the job is started.
*DEV: The output queue associated with the printer specified on the Device (DEV) parameter of the printer file is used. The output queue has the same name as the printer. The printer file DEV parameter is determined by the Create Printer File (CRTPRTF), Change Printer File (CHGPRTF), or the Override with Printer File (OVRPRTF) commands.
Note: This assumes the defaults were specified on the OUTQ parameter for the printer file, job description, user profile, and workstation.
*WRKSTN: The output queue to be used with this job description is the output queue assigned to the work station that is associated with the job at the time the job is started.

Qualifier 1: Output queue

name: Specify the name of the output queue to be used with this job description

Qualifier 2: Library

*LIBL: All libraries in the thread's library list are searched until a match is found.
*CURLIB: The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.

name: Specify the library where the output queue is located.

Note: If the output queue does not exist when the job description is created, a library qualifier must be specified because the qualified output queue name is kept in the job description.

User (USER)

Specifies the name of the user profile associated with this job description. The names QSECOFR, QSPL, QDOC, QDBSHR, QRJE, QSYS, QLPAUTO, QLPINSTALL, QTSTRQS, and QDFTOWN are not valid entries for this parameter.

*RQD: A user name is required to use the job description. For work station entries, you must enter a user name when signing on at the work station; the associated user name becomes the name used for the job. *RQD is not valid for job descriptions specified for autostart job entries or for those used by the Batch Job (BCHJOB) command. It is valid on the Submit Job (SBMJOB) command only if *CURRENT is specified on the User (USER) parameter.

name: Specify the user name that identifies the user profile associated with batch jobs using this job description. For interactive jobs, this is the default user name used to sign on the system without typing a user name.

Accounting code (ACGCDE)

Specifies the accounting code that is used when logging system resource use for jobs that use this description. If the job is submitted by the Submit Job (SBMJOB) command, the submitter's accounting code is used. To specify an accounting code other than *USRPRF, you must be authorized to the Change Accounting Code (CHGACGCDE) command.

*USRPRF: The accounting code for jobs using this job description is obtained from the user profile associated with the job.

*BLANK: An accounting code of 15 blanks is assigned to jobs that use this job description.
character-value: Specify the accounting code for jobs that use this job description and have accounting statistics logged in the system accounting journal QACGJRN. If less than 15 characters are entered, the string is padded with blanks on the right.

Routing data (RTGDTA)

Specifies the routing data used with this job description to start jobs.

QCMDI: The default routing data QCMDI is used by the IBM-supplied interactive subsystem to route the job to the IBM-supplied control language processor QCMD in the QSYS library.

*RQSDTA: Up to the first 80 characters of the request data specified on the Request data or command (RQSDTA) parameter are used as the routing data for the job.
character-value: Specify the routing data for jobs that use this job description. A maximum of 80 characters can be typed (enclosed in apostrophes if necessary).

Request data or command (RQSDTA)

Specifies the request data that is placed as the last entry in the job's message queue for jobs using this job description.

*NONE: No request data is placed in the job's message queue.

*RTGDTA: The routing data specified on the Routing data (RTGDTA) parameter is placed as the last entry in the job's message queue.
character-value: Specify the character string that is placed as the last entry in the job's message queue as a single request. A maximum of 256 characters can be entered (enclosed in apostrophes if necessary). When a CL command is entered, it must be enclosed in single apostrophes, and where apostrophes would normally be used inside the command, double apostrophes must be used instead.

Initial library list (INLLIBL)

Specifies the initial user part of the library list to be used for jobs using this job description.

Note: Duplication of library names in the library list is not allowed.

Single values

*SYSVAL: The system default library list is used for jobs that use this job description. The default library list contains the library names that were specified in the system value QUSRLIBL at the time a job using this job description is started.

*NONE: The user part of the library list is empty; only the system portion is used.

Other values (up to 250 repetitions)

name: Specify the library in the user part of the library list to be used for jobs using this job description.

Note: Libraries are searched in the same order as they are listed here.

Initial ASP group (INLASPGRP)

Specifies the initial setting for the auxiliary storage pool (ASP) group name for the initial thread of jobs using this job description. A thread can use the Set ASP Group (SETASPGRP) command to change its library name space. When an ASP group is associated with a thread, all libraries in the independent ASPs in the ASP group are accessible and objects in those libraries can be referenced using regular library-qualified object name syntax. The libraries in the independent ASPs in the specified ASP group plus the libraries in the system ASP (ASP number 1) and basic user ASPs (ASP numbers 2 - 32) form the library name space for the thread.

Restrictions:

The job descriptions QGPL/QDFTJOBD and QGPL/QDFTSVR cannot be changed to specify the name of an ASP group. For these job descriptions, the INLASPGRP must be *NONE.

*NONE: Specifies the initial thread of jobs using this job description will be started with no ASP group. The library name space will not include libraries from any ASP group. Only the libraries in the system ASP and any basic user ASPs will be in the library name space.
name: Specifies the name of the ASP group to be set for the initial thread of jobs using this job description. The ASP group name is the name of the primary ASP device within the ASP group. All libraries from all ASPs in this ASP group will be included in the library name space.

Message logging (LOG)

Specifies the message logging values used to determine the amount and type of information sent to the job log by this job. This parameter has three elements: the message (or logging) level, the message severity, and the level of message text.

Element 1: Level

4: A message logging level of 4 is used for jobs that use this job description.

0-4

Specify the message logging level to be used for the job's messages.

0

No messages are logged.

1

All messages sent to the job's external message queue with a severity greater than or equal to the message logging severity are logged. This includes the indications of job start, job end, and job completion status.

2

The following information is logged:

Logging level 1 information
Request messages which result in a high-level message with a severity code greater than or equal to the message logging severity. Both the request message and all associated messages are logged.

Note: A high-level message is one that is sent to the program message queue of the program that receives the request message. For example, QCMD is an IBM-supplied request processing program that receives request messages.

3

The following information is logged:

Logging level 1 and 2 information
All request messages
Commands run by a CL program are logged if it is allowed by the logging of CL programs job attribute and the log attribute of the CL program.

4

The following information is logged:

All request messages and all messages with a severity greater than or equal to the message logging severity, including trace messages.
Commands run by a CL program are logged if it is allowed by the logging of CL programs job attribute and the log attribute of the CL program.

Element 2: Severity

0: A message severity level of 0 is used for jobs that use this job description.

0-99: Specify the message severity level to be used in conjunction with the logging level to determine which error messages are logged in the job log.

Element 3: Text

*NOLIST: If the job ends normally, no job log is produced. If the job ends abnormally (if the job end code is 20 or higher), a job log is produced. The messages that appear in the job log contain both the message text and the message help.
*MSG: Only the message text is written to the job log.
*SECLVL: Both the message text and the message help (cause and recovery) of the error message are written to the job log.

Log CL program commands (LOGCLPGM)

Specifies whether the commands that can be logged and were run in a control language program are logged to the job log by way of the CL program's message queue. This parameter sets the status of the job's logging flag. If *NO is specified, the logging flag status is off and CL commands are not logged. If *YES is specified here and *JOB is specified on the Message logging (LOG) parameter of the Create CL Program (CRTCLPGM) command, all commands in the CL program that can be logged are logged to the job log.

*NO: The commands in a CL program are not logged to the job log.

*YES: The commands in a CL program are logged to the job log.

Job log output (LOGOUTPUT)

Specifies how the job log will be produced when the job completes. This does not affect job logs produced when the message queue is full and the job message queue full action specifies *PRTWRAP. Messages in the job message queue are written to a spooled file, from which the job log can be printed, unless the Control Job Log Output (QMHCTLJL) API was used in the job to specify that the messages in the job log are to be written to a database file.

The job log output value can be changed at any time until the job log has been produced or removed. To change the job log output value for a job, use the Change Job (QWTCHGJB) API or the Change Job (CHGJOB) command.

The job log can be displayed at any time until the job log has been produced or removed. To display the job log, use the Display Job Log (DSPJOBLOG) command.

The job log can be removed when the job has completed and the job log has not yet been produced or removed. To remove the job log, use the Remove Pending Job Log (QWTRMVJL) API or the End Job (ENDJOB) command.

*SYSVAL: The value specified in the system value QLOGOUTPUT is used.
*JOBLOGSVR: The job log will be produced by a job log server. For more information about job log servers, refer to the Start Job Log Server (STRLOGSVR) command.
*JOBEND: The job log will be produced by the job itself. If the job cannot produce its own job log, the job log will be produced by a job log server. For example, a job does not produce its own job log when the system is processing a Power Down System (PWRDWNSYS) command.
*PND: The job log will not be produced. The job log remains pending until removed.

CL syntax check (SYNTAX)

Specifies whether requests placed on the job message queue (for jobs using this job description) are checked for syntax as CL commands. When syntax checking is specified, the commands are checked for syntax as they are submitted instead of when the job is run, thus providing an earlier diagnosis of syntax errors. If checking is specified, the message severity that causes a syntax error to end processing of a job is also specified.

*NOCHK: The request data is not checked for syntax as CL commands.

0-99: Specify the lowest message severity that can cause running of a job to end. The request data is checked for syntax as CL commands. If a syntax error occurs that is equal to or greater than the error message severity specified here, the running of the job containing the erroneous command is suppressed.

End severity (ENDSEV)

Specifies the message severity level of escape messages that can cause a batch job to be ended. The batch job is ended when a request in the batch input stream results in an escape message whose severity code is equal to or greater than that specified here being sent to the request processing program QCMD or QCL. This parameter value is compared with the severity of any escape message not monitored that occurs as a result of running a noncompiled CL command in a batch job.

30: A batch input stream request that results in an escape message whose severity is equal to or greater than 30 causes the job to end.

0-99: Specify the message severity of an escape message that results from a request in the batch input stream and that causes the jobs that use this job description to be ended. Because escape messages typically have a maximum severity level of 50, a value of 50 or lower must be specified in order for a job to be ended as a result of an escape message. An unhandled escape message whose severity is equal to or greater than the value specified causes the job to be ended.

Inquiry message reply (INQMSGRPY)

Specifies the way that inquiry messages are answered for jobs that use this job description. You can specify that inquiry messages are to be answered in the usual manner, that a default reply be issued, or that if certain conditions are met, an answer is issued to the inquiry based on those conditions. The conditions met are listed in the system reply list entries of the Add Reply List Entry (ADDRPYLE) command.

*RQD: A reply is required for any predefined inquiry message that is issued by a job that uses this job description.

*DFT: The default message reply is used to answer any predefined inquiry messages issued during running of a job that uses this job description. The default reply is either defined in the message description or is the default system reply.
*SYSRPYL: The system reply list is checked to determine whether an entry matches the message identifier and optional compare value for any inquiry message issued by a job that uses this job description. If a match occurs, the reply value in that reply list entry is used. If no entry exists for that message, a reply is required.

Job switches (SWS)

Specifies the initial switch settings for a group of eight job switches used for jobs that use this job description. These switches can be set or tested in a CL program and used to control the flow of the program. The only values that are valid for each single-digit switch are 0 (off) or 1 (on).

00000000: The first setting for the job switches is all zeros for jobs that use this job description.

character-value: Specify any combination (enclosed in apostrophes if necessary) of eight 0's or 1's to change the job switch settings.

Device recovery action (DEVRCYACN)

Specifies the recovery action to take for the job when an I/O error is encountered on the *REQUESTOR device for interactive jobs that use this job description. This attribute is ignored for non-interactive jobs.

*SYSVAL: The value in the system value QDEVRCYACN at the time the job is started is to be used as the device recovery action for this job description.
*MSG: The application program requesting the I/O operation receives an error message indicating the operation has failed.
*DSCMSG: The job is automatically disconnected. Once the job has reconnected, it receives an error message indicating an I/O error has occurred and the device has been recovered. Even though the device has been recovered, the contents of the screen prior to the error must be displayed again.
*DSCENDRQS: The job is automatically disconnected. Once the job has reconnected, the End Request (ENDRQS) command will be issued specifying the processor that made the previous request. If there is no request processor, an error message will be issued.
*ENDJOB: The job is ended with the *IMMED option. A job log is produced for the job.
*ENDJOBNOLIST: The job is ended with the *IMMED option. No job log is produced for the job.

Time slice end pool (TSEPOOL)

Specifies whether interactive jobs are moved to another main storage pool when they reach the end of the time slice. The job is moved back to the pool in which it was originally running when a long wait occurs. This may help minimize the effect on interactive response time of other interactive jobs.

*SYSVAL: The value of the system value QTSEPOOL at the time the job is started is to be used as the time slice end pool action for this job description.
*NONE: The job is not moved when the end of the time slice is reached.
*BASE: The job is moved to the base pool when the end of the time slice is reached.

Authority (AUT)

Specifies the authority you are giving to users who do not have specific authority for the object, who are not on an authorization list, and whose group profile or supplemental group profiles do not have specific authority for the object.

*LIBCRTAUT: The authority to the object is the same as the value specified on the Create authority (CRTAUT) parameter of the library in which the object is being created. If the value specified on the CRTAUT parameter is changed, the new value will not affect any existing objects.

*CHANGE: The user can perform all operations on the object except those limited to the owner or controlled by object existence (*OBJEXIST) and object management (*OBJMGT) authorities. The user can change and perform basic functions on the object. *CHANGE authority provides object operational (*OBJOPR) authority and all data authority. If the object is an authorization list, the user cannot add, change, or remove users.

*ALL: The user can perform all operations except those limited to the owner or controlled by authorization list management (*AUTLMGT) authority. The user can control the object's existence, specify the security for the object, change the object, and perform basic functions on the object. The user also can change ownership of the object.

*USE: The user can perform basic operations on the object, such as displaying its contents. The user cannot change the object. *USE authority provides object operational authority, read authority, and execute authority.

*EXCLUDE: The user cannot access the object.

name: Specify the name of an authorization list to be used for authority to the object. Users included in the authorization list are granted authority to the object as specified in the list. The authorization list must exist when the object is created.

Allow multiple threads (ALWMLTTHD)

Specifies whether or not the job can run with multiple user threads. This attribute does not prevent the operating system from creating system threads in the job. This job attribute is not allowed to be changed once a job starts. This attribute applies to autostart jobs, prestart jobs, batch jobs submitted from job schedule entries and jobs started using the Submit Job (SBMJOB) and Batch Job (BCHJOB) commands. This attribute is ignored when starting all other types of jobs. This attribute should be set to *YES only in job descriptions used exclusively with functions that create multiple user threads.

*NO: The job cannot run with multiple user threads.
*YES: The job can run with multiple user threads.

Spooled file action (SPLFACN)

Specifies whether or not spooled files are accessed through job interfaces after the job ends. Keeping spooled files with jobs allows job commands such as the Work with Submitted Jobs (WRKSBMJOB) command to work with the spooled files even after the job has ended. Detaching spooled files from jobs reduces the use of system resources by allowing job structures to be recycled when the jobs end.

*SYSVAL: The value specified in the system value QSPLFACN is used.
*KEEP: When the job ends, as long as at least one spooled file for the job exists in the system auxiliary storage pool (ASP 1) or in a basic user ASP (ASPs 2-32), the spooled files are kept with the job and the status of the job is updated to indicate that the job has completed. When all remaining spooled files for the job are in independent ASPs (ASPs 33-255), the spooled files will be detached from the job and the job will be removed from the system.
*DETACH: When the job ends, the spooled files are detached from the job and the job is removed from the system.

DDM conversation (DDMCNV)

Specifies whether the connections using distributed data management (DDM) protocols remain active when they are not being used. The connections include APPC conversations, active TCP/IP conversations or OptiConnect connections. The DDM protocols are used in Distributed Relational Database Architecture (DRDA) applications, DDM applications, or DB2 Multisystem applications. For more information on distributed data management, see the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

*KEEP

The system keeps DDM conversation connections active when they are no longer being used, except when:

The routing step ends on the source system.
There is an explicit request that conversations be disconnected, using the Reclaim DDM Conversations (RCLDDMCNV) command or the Reclaim Resources (RCLRSC) command.
There is a communications failure or internal failure.
A DRDA connection to an application server not running on the iSeries ends.

*DROP

The system ends a DDM-allocated conversation when it is no longer being used. Examples include when an application closes a DDM file, or when a DRDA application runs an SQL DISCONNECT statement.

Examples

Example 1: Creating a Job Description for Interactive Jobs

CRTJOBD   JOBD(INT4)  USER(*RQD)  RTGDTA(QCMDI)
          INQMSGRPY(*SYSRPYL)
          TEXT('Interactive #4 JOBD for Department 127')

This command creates a job description named INT4 in the user's current library. This job description is for interactive jobs and is used by Department 127. When you sign on, you must type your password. The characters QCMDI are used as routing data that is compared with the routing table of the subsystem where the job is run. All inquiry messages are compared to the entries in the system reply list to determine whether a reply is issued automatically.

Example 2: Creating a Job Description for Jobs on a Specified Queue

CRTJOBD   JOBD(BATCH3)  USER(*RQD)  JOBQ(NIGHTQ)  JOBPTY(4)
          OUTPTY(4) ACGCDE(NIGHTQ012345)  RTGDTA(QCMDB)
          TEXT('Batch #3 JOBD for high priority night work')

This command creates a job description named BATCH3 in the user's current library. The jobs using this description are placed on the job queue NIGHTQ. The priority for jobs using this description and their spooled output is 4. QCMDB is the routing data that is compared with entries in the routing table of the subsystem where the job runs. The accounting code of NIGHTQ012345 is used when recording accounting statistics for jobs that use this job description.

Example 3: Specifying Request Data

CRTJOBD   JOBD(PAYWK)  USER(QPGMR)   RTGDTA(QCMDB)
          RQSDTA('CALL PAY025 PARM(WEEKLY UNION)')

This command creates a job description named PAYWK in the user's current library. Jobs using this job description run under the IBM-supplied user profile for the programmer, QPGMR, and use the accounting code found in that user profile. If the job is started via the SBMJOB command, the accounting code of the person submitting the command is automatically used. The routing data QCMDB is compared with entries in the routing table of the subsystem where the job is run. The request data passed to the command processing program is a CALL command that names the application program that is run and passes a parameter to it.