CHGJOBJS (Change Job Using Job Scheduler)

Note: To use this command, have the 5722-JS1 (Job Scheduler for iSeries) licensed program installed.

CHGJOBJS Command syntax diagram

 

Purpose

The Change Job Job Scheduler (CHGJOBJS) command allows you to change a job in the job schedule.

Note: When referring to a job in this command, we are referring to an entry in Job Scheduler. An entry in Job Scheduler is a user-defined name for commands or programs that you want to process at scheduled times and dates. Job Scheduler jobs (entries) are not OS/400 objects.

Jobs can be a single job or a member of a group of jobs or an application. Use this command to change the schedule of a batch job to be submitted once and so on, based on the schedule code you specify. You can schedule jobs with user-defined calendars, holiday exception calendars and fiscal year calendars.

The job schedule entry contains all of the information needed to submit the job, including the commands to process, the job description and user profile under which the job is run, the job queue to which the job is submitted, the message queue to which messages are sent and so on.

At the date and time you specify or Job Scheduler calculates, the job is submitted to the specified job queue. This command does not guarantee that the job will begin running at the scheduled time, however. The job will not begin running if the job queue is held or attached to an inactive subsystem, or if the maximum number of active jobs allowed to run in the subsystem or on the system at one time has been reached.

Each job schedule entry is identified by a user-defined job, which is specified on the JOB parameter of this command.

Restrictions:

  1. The user must have use authority to the job description and the user profile.

  2. The user must have use and add authorities to the message queue and the output queue.

  3. The user must have read authority to the job queue and to all libraries associated with the specified objects.

  4. The user must have use authority to the *ADDJOB function.

 

Required Parameters

JOB
Specifies the name of the job schedule entry that you want to change. You must specify a job and alternately can specify a group to which the job belongs as well as a sequence number for the job within the group.

The first job of a group must be sequence number 1. Subsequent sequence numbers should leave gaps (10, 20, 30 and so on) to allow job insertions if necessary. An entire group can be held or released by holding or releasing the first member of the group. Individual jobs within a group may also be held or released.

Element 1: Job

job-name: Specify the job that you want to change.

Element 2: Group

*NONE: There is not a group associated with this job.

group-name: Specify the name of the group of which this job is a member.

Element 3: Group sequence

*NONE: There is not a sequence number assigned to the job.

group-sequence-number: Specify the sequence number of the job. Sequence numbers can range from 1 to 99.

 

Optional Parameters

APP
Specifies the name of the application to which the job specified in the JOB parameter belongs.

*SAME: The current value for the parameter does not change.

*NONE: This job does not belong to an application.

application-name: Specify the name of the application to which the job that you are adding belongs.

SCDCDE
Specifies the schedule code that you want to assign to the job.

*SAME: The current value for the parameter does not change.

*DAILY: The job is scheduled to run on a daily basis or on selected days every week. For example, it may be scheduled to run on Wednesday only, or every day of the week.

*CALENDAR: You are using a calendar to schedule the job. Calendars are user defined in the Work with Calendars display.

*DATE: The job is scheduled to run on specific dates throughout the year. They are retained in the system in month day (mmdd) or day month (ddmm) format depending on the system value and will be submitted on the specified dates. Up to 13 dates can be scheduled.

*DAY: The job is to be run on particular calendar days of the month, every month. These are entered in day (dd) format.

*NUMDAY: The job runs every specified number of days. The number of days specified must be 99 or less.

Note: If the scheduled time to run is greater than the current time, Job Scheduler will count that time as a whole day (if you enter a Job Scheduler job on Monday at 3:00 p.m. to run every 2 days at 5:00 p.m., the job will run the first time on Tuesday at 5:00 p.m.).

*MINUTES: The job runs every specified number of minutes.

*ONCE: The job is to be run once. The SAVE parameter prompt indicates whether the job is to be saved (*YES) or deleted (*NO) after it is run. If it is a job group, the SAVE parameter will not be shown and will assume saved (*YES). The date that the job is scheduled to be run is typed into the SNGDAY parameter. Leaving the date blank will run the job when the scheduled time is reached.

*MONTHEND: The job runs on the last day of the month.

*FIRST: The job is to run on the first designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the first Tuesday of each month.

*SECOND: The job is to run on the second designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the second Tuesday of each month.

*THIRD: The job is to run on the third designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the third Tuesday of each month.

*FOURTH: The job is to run on the fourth designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the fourth Tuesday of each month.

*FIFTH: The job is to run on the fifth designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the fifth Tuesday of each month. If there is not a fifth occurrence in a month, the job will not run and will be scheduled for the next time there is a fifth occurrence of a selected day in a month.

*LAST: The job is to run on the last designated day of every month or specified fiscal periods. This option is used in conjunction with the SNGDAY parameter. For instance, if *TUE is specified in the SNGDAY parameter, the job will be scheduled to run on the last Tuesday of each month.

*FIRSTWRK: The job is to run on the first working day of every month or specified fiscal periods. This option is used in conjunction with the Work days prompt in the system controls.

*LASTWRK: The job is to run on the last working day of every month or specified fiscal periods. This option is used in conjunction with the Work days prompt in the system controls.

*DEPJOB: The job is to run depending on the outcome or processing of another job.

*ALTERNATE: The job is to run when a regular job ends abnormally and has this job defined as its alternate job.

*NONE: The job is a subordinate job group and does not have a schedule code. Subordinate job groups assume the schedule code of the first job in the group.

*JOBCTL: The job is scheduled to run based on the schedule code specified in the job controls.

TIME
Specifies the time or times that you want the job to process on specified days. Times are entered in hour, minute (HHMM) format and can range from 0001 to 2400 (midnight).

You can enter multiple values for this parameter. If you are on an entry display and you need additional entry fields to enter these multiple values, type a plus sign (+) in the entry field opposite the phrase "+ for more", and press the Enter key.

*SAME: The current value for the parameter does not change.

scheduled-time: Specify the time that you want the job to run.

ITVMIN
Specifies the number of minutes that you want to use as an interval with the *MINUTES schedule code. Interval times can range from 1 to 720 minutes. The ITVMIN parameter is required when you use the *MINUTES schedule code.

*SAME: The current value for the parameter does not change.

number-of-minutes: Specify the number of minutes between submissions of the job.

CAL
Specifies the name of the calendar that you want to use to schedule the job. A calendar is a user-defined set of days or dates used with the *CALENDAR schedule code. It can be used to specify Job Scheduler processing.

*SAME: The current value for the parameter does not change.

*NONE: This job does not use a calendar.

calendar-name: Specify the name of the calendar that you want to use for this job.

HDYCAL
Specifies the name of the holiday calendar that you want to use with a job. A holiday calendar is a user-defined set of exception days or dates used with the *CALENDAR schedule code. It can be used to determine whether a job will process.

*SAME: The current value for the parameter does not change.

*NONE: This job does not use a holiday calendar.

holiday-calendar-name: Specify the name of the holiday calendar that you want to use for this job.

FSCCAL
Specifies the name of the fiscal year calendar that you want to use with the job specified in the JOB parameter. Fiscal year calendars are made up of 12 or 13 periods with starting and ending dates for each period.

*SAME: The current value for the parameter does not change.

*NONE: There is not a fiscal calendar for this job.

fiscal-calendar-name: Specify the name of the user-defined fiscal year calendar that you want to use for this job.

DAY
Specifies the days that you want this job to process. Days of the week are used with the *DAILY and *MINUTES schedule codes or job groups with a sequence greater than 1.

You can enter multiple values for this parameter. If you are on an entry display and you need additional entry fields to enter these multiple values, type a plus sign (+) in the entry field opposite the phrase "+ for more", and press the Enter key.

*SAME: The current value for the parameter does not change.

*ALL: The job runs on all days of the week.

*MON: The job is scheduled to run on Monday.

*TUE: The job is scheduled to run on Tuesday.

*WED: The job is scheduled to run on Wednesday.

*THU: The job is scheduled to run on Thursday.

*FRI: The job is scheduled to run on Friday.

*SAT: The job is scheduled to run on Saturday.

*SUN: The job is scheduled to run on Sunday.

SNGDAY
Specifies the day of the week that you want this job to process. Single day is used with the *FIRST, *SECOND, *THIRD, *FOURTH, *FIFTH AND *LAST schedule codes.

Note: *SUN is the default day of the week when *FIRST, *SECOND, *THIRD, *FOURTH, *FIFTH or *LAST is specified.

*SAME: The current value for the parameter does not change.

*SUN: The job is scheduled to run on Sunday.

*MON: The job is scheduled to run on Monday.

*TUE: The job is scheduled to run on Tuesday.

*WED: The job is scheduled to run on Wednesday.

*THU: The job is scheduled to run on Thursday.

*FRI: The job is scheduled to run on Friday.

*SAT: The job is scheduled to run on Saturday.

ITVDAY
Specifies the number of days that you want to use as an interval with the *NUMDAY schedule code. Intervals can range from 1 to 99 days.

Note: The ITVDAY parameter is required when you use the *NUMDAY schedule code.

*SAME: The current value for the parameter does not change.

number-of-days: Specify the number of days between submissions of the job.

DATE
Specifies the dates that a job is scheduled to be processed. Dates are entered in month, day (MMDD) format or (DDMM) format depending on the system value. The DATE parameter is required when the SCDCDE parameter contains *DATE.

You can enter multiple values for this parameter. If you are on an entry display and you need additional entry fields to enter these multiple values, type a plus sign (+) in the entry field opposite the phrase "+ for more", and press the Enter key.

*SAME: The current value for the parameter does not change.

dates-of-the-year: Specify the dates that you want to schedule a job to run.

SNGDATE
Specifies the date that a job is scheduled to be processed. Dates are entered in month, day (MMDD) format. The SNGDAY parameter is used when the SCDCDE parameter contains *ONCE.

*SAME: The current value for the parameter does not change.

*NEXT: The job is to be processed when the scheduled time is reached.

single-date: Specify the single date of the year that the job is to be submitted.

SAVE
Specifies whether this job is to be saved after it has run. The SAVE parameter is used with the *ONCE schedule code.

*SAME: The current value for the parameter does not change.

*YES: The job is to be saved after it has run.

*NO: The job is to be deleted after it has run.

DAYMONTH
Specifies the days of the month that you want this job to process. Days of the month are used with the *DAY schedule code. Days of the month can range from 1 to 31.

You can enter multiple values for this parameter. If you are on an entry display and you need additional entry fields to enter these multiple values, type a plus sign (+) in the entry field opposite the phrase "+ for more", and press the Enter key.

*SAME: The current value for the parameter does not change.

day-of-month: Specify the days of the month that you want the job to run.

FSCPERIOD
Specifies the periods within a fiscal year for the job. Periods are used when a fiscal calendar name is specified in the FSCCAL parameter. Periods can range from 1 to 13.

You can enter multiple values for this parameter. If you are on an entry display and you need additional entry fields to enter these multiple values, type a plus sign (+) in the entry field opposite the phrase "+ for more", and press the Enter key.

*SAME: The current value for the parameter does not change.

*ALL: All periods are to be included for the job.

fiscal-period-number: Specify the fiscal periods that you want to include for the job.

TEXT
Specifies the text related to the job.

*SAME: The current value for the parameter does not change.

*NONE: The job does not have any text description associated with it.

print-text: Specify the text description associated with the job.

RMTLOCNAME
Specifies the location and network identification of the remote location name on which to run the job.

Note: A value specified in the RMTLOCNAME parameter will be ignored when used with schedule code *ALTERNATE.

*SAME: The current value for the parameter does not change.

*JOBCTL: Use the remote location name specified in the job controls.

*LCL: Run the job on the local iSeries 400.

remote-location-name: Specify the name of the location associated with the system on which to run the job.

network-ID.location-name: Specify the network identifier and the name of the location associated with the system. Specify these values using the format nnnnnnnn.cccccccc where nnnnnnnn is the network identifier and cccccccc is the location name.

RANGE
Specifies the starting and ending time and date range for the job.

Note: If you are using the *MINUTES schedule code, the Beginning time value is used in conjunction with the Ending time. The *MINUTES schedule code is the only schedule code that uses these two values to indicate when a job starts and stops. The Beginning date and Ending date can be used with most schedule codes.

Note: A value specified in the RANGE parameter will be ignored when used with schedule codes *ALTERNATE, *DEPJOB and *GROUP (subordinate job group).

This parameter contains two lists of two elements each.

Element 1: Beginning time

*SAME: The current value for the parameter does not change.

*NONE: No beginning time is specified for this job.

beginning-time: Specify the beginning time for the job in hour, minute (HHMM) format.

Element 2: Beginning date

*SAME: The current value for the parameter does not change.

*NONE: No beginning date is specified for this job.

beginning-date: Specify the beginning date for this job in job date format.

Element 3: Ending time

*SAME: The current value for the parameter does not change.

*NONE: No ending time is specified for this job.

ending-time: Specify the ending time for this job in hour, minute (HHMM) format.

Element 4: Ending date

*SAME: The current value for the parameter does not change.

*NONE: No ending date is specified for this job.

ending-date: Specify the ending date for this job in job date format.

MAXRUN
Specifies the maximum run duration in minutes for the job.

Note: A value specified in the MAXRUN prompt will be ignored when used with schedule code *ALTERNATE.

*SAME: The current value for the parameter does not change.

*NOMAX: There is no maximum duration for the job.

maximum-run-time: Specify the number of minutes that is the maximum duration for this job. After this number of minutes has passed, Job Scheduler will end the job whether it has completed or not. The maximum minutes can range from 1 to 9999 minutes.

PGRRCPNORM
Specifies the pager recipient who is to receive normal completion messages for the job that you are submitting. This field is used in conjunction with command specified in the CHGPGRJS command.

Note: A paging product must be installed before this feature may be used.

You can specify the pager message that you want to send to the specified recipient when the job completes normally. The values that you specify for Pager recipient normal and Pager message are the substitution values used for the &RCP and &MSGTXT variables respectively in the CHGPGRJS.

Element 1: Pager recipient normal

*SAME: The current value for the parameter does not change.

*JOBCTL: You are using the pager recipient specified in the Job Scheduler job controls.

*NONE: No pager recipient is assigned to receive messages when this job completes normally.

recipient-name: Specify the name of a recipient who is to receive messages from the job when it completes normally.

Element 2: Pager message

*SAME: The current value for the parameter does not change.

*JOBCTL: The pager recipient is sent the pager message from the Job Scheduler job controls.

*COMP: The job completion of the job is sent.

pager-message: Specify the pager message that you want to send to the pager recipient when this job completes normally.

PGRRCPABN
Specifies the pager recipient who is to receive abnormal completion messages for the job that you are submitting. This field is used in conjunction with the CHGPGRJS command.

Note: A paging product must be installed before this feature may be used.

You can specify the pager message that you want to send to the specified recipient when the job completes abnormally. The values that you specify for Pager recipient abnormal and Pager message are the substitution values used for the &RCP and &MSGTXT variables respectively in the CHGPGRJS command.

Element 1: Pager recipient abnormal

*SAME: The current value for the parameter does not change.

*JOBCTL: You are using the pager recipient specified in the Job Scheduler job controls.

*NONE: No pager recipient is assigned to receive messages when this job completes abnormally.

recipient-name: Specify the name of a recipient who is to receive messages from the job when it completes abnormally.

Element 2: Pager message

*SAME: The current value for the parameter does not change.

*JOBCTL: The pager recipient is sent the pager message from the Job Scheduler job controls.

*COMP: The job completion of the job is sent.

pager-message: Specify the pager message that you want to send to the pager recipient when this job completes abnormally.

ALTJOB
Specifies the name of the alternate job for the job. Alternate jobs only run when a regular job ends abnormally. Jobs are not required to have alternate jobs. You can also specify the group and sequence number for the alternate job that you specify.

*SAME: The current value for the parameter does not change.

*NONE: The job does not have an alternate job.

Element 1: Alternate job

alternate-job-name: Specify the name of the alternate job that you want to use with the job that you are adding.

Element 2: Group

*NONE: The alternate job does not have an alternate group.

group-name: Specify the name of the group associated with the alternate job for this job.

Element 3: Group sequence

*NONE: The alternate job does not have a sequence number assigned.

group-sequence-number: Specify the sequence number assigned to the alternate job. Sequence numbers can range from 1 to 99.

RPTDSTID
Specifies the report distribution ID that is used to distribute the reports generated as a result of processing the job.

*SAME: The current value for the parameter does not change.

*NONE: The job does not have a report distribution ID.

report-distribution-ID: Specify the report distribution ID that you want to associate with this job.

RCYACN
Specifies the recovery action to be taken if the job cannot be submitted at the designated time because the system is powered down or in restricted state. The action specified on the parameter occurs at the next IPL or when the Job Scheduler system becomes active.

Jobs submitted during IPL or when the system comes out of restricted state are submitted in the same order that they would have been had the jobs been submitted at the times specified in the job schedule entries. If multiple occurrences of a recurring job are missed, the job is submitted only once. The first missed occurrence of the job is calculated from the current date.

Since the scheduler portion of IPL need not be complete for the IPL of the system to be complete, other jobs may start on the system before all of the jobs have been submitted.

This parameter does not apply:

  • When a job is released after being held at the date and time it was to be submitted.

Note: A value specified in the RCYACN prompt will be ignored when used with schedule code *ALTERNATE, *DEPJOB and *GROUP (subordinate job group).

*SAME: The current value for the parameter does not change.

*JOBCTL: The job uses the recovery action specified in the Job Scheduler job controls.

*SBMRLS: The job is submitted in release state (RLS).

*SBMHLD: The job is submitted in the held state (HLD).

*NOSBM: The job is not submitted.

Specifying *NOSBM affects only missed occurrences of the job. If the job schedule entry is a recurring job, future occurrences are not affected.

JOBD
Specifies the name of the job description used with this job.

*SAME: The current value for the parameter does not change.

*JOBCTL: The system default job description is used for this job.

*USRPRF: The job description in the user profile under which the submitted job runs is used as the job description of the submitted job.

job-description-name: Specify the name (library-name/job-description-name) of the job description used for the job.

*LIBL: The library list is used to locate the job description name.

*CURLIB: The current library for the job is used to locate the job description name. If no library is specified as the current library for the job, QGPL is used.

library-name: Specify the name of the library where the job description name is located.

JOBQ
Specifies the name of the job queue in which this job is placed.

*SAME: The current value for the parameter does not change.

*JOBCTL: The system default job queue is used for this job.

*JOBD: The submitted job is placed on the job queue named in the specified job description.

job-queue-name: Specify the name (library-name/job-queue-name) of the job queue on which the submitted job is placed.

*LIBL: The library list is used to locate the job queue name.

*CURLIB: The current library for the job is used to locate the job queue name. If no library is specified as the current library for the job, QGPL is used.

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

JOBPTY
Specifies the job queue scheduling priority. Valid values range from 1 through 9, where 1 is the highest priority and 9 is the lowest priority.

*SAME: The current value for the parameter does not change.

*JOBCTL: The scheduling default specified in the Job Scheduler job controls is used for the job.

*JOBD: The scheduling priority specified in the job description is used for the job.

scheduling-priority: Specify a value, ranging from 1 through 9, for the scheduling priority for the job.

OUTPTY
Specifies the output queue priority for spooled output files that are produced by this job. Valid values range from 1 through 9, where 1 is the highest priority and 9 is the lowest priority.

*SAME: The current value for the parameter does not change.

*JOBCTL: The output priority default specified in the Job Scheduler job controls is used for the job.

*JOBD: The output priority specified in the job description is used for the job.

output-priority: Specify a value, ranging from 1 through 9, for the output priority for the job.

PRTDEV
Specifies the qualified name of the default printer device for this job.

*SAME: The current value for the parameter does not change.

*JOBCTL: The printer specified in the Job Scheduler job controls is used by the job as the printer device.

*USRPRF: The printer device specified in the user profile where the submitted job runs is used as the printer device for this job. The printer device name is obtained from the profile when the job is submitted.

*SYSVAL: The printer device specified in the system value, QPRTDEV, when this job is submitted is used.

*JOBD: The printer device specified in the job description is used for the submitted job.

printer-device-name: Specify the name of the printer device used for the submitted job.

OUTQ
Specifies the qualified name of the output queue that is used for spooled output produced by the job. This parameter only applies to spooled printer files that specify *JOB for the output queue.

*SAME: The current value for the parameter does not change.

*JOBCTL: The output queue specified in the Job Scheduler job controls is used as the job's output queue.

*JOBD: The output queue named in the job description used with the submitted job is the job's default output queue.

output-queue-name: Specify the name (library-name/output-queue-name) of the output queue that is used as the default output queue by the submitted job.

*LIBL: The library list is used to locate the output queue name.

*CURLIB: The current library for the job is used to locate the output queue name. If no library is specified as the current library, QGPL is used.

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

USER
Specifies the name of the user profile for the job being submitted. If *RQD is specified in the job description, *JOBD cannot be specified; a user name must be specified instead.

Note: The following IBM-supplied objects are not valid on this parameter:

  • QDBSHR

  • QDFTOWN

  • QDOC

  • QLPAUTO

  • QLPINSTALL

  • QRJE

  • QSECOFR

  • QSPL

  • QSYS

  • QTSTRQS

*SAME: The current value for the parameter does not change.

*JOBCTL: The user profile specified in the Job Scheduler defaults is used for the job being submitted.

*CURRENT: The same user profile used by the job that is currently running is used for the submitted job.

*JOBD: The user profile named in the specified job description is used for the job being submitted.

user-name: Specify the name of the user profile that is used for the job being submitted. You must be authorized to the user profile; the user profile must be authorized to the job description.

PRTTXT
Specifies up to 30 characters of text that is printed at the bottom of each page of printed output and on separator pages.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job control is used for this job.

*BLANK: No text is printed.

*JOBD: The value in the job description is used for this job.

*SYSVAL: The system value, QPRTTXT, is used for this job.

print-text: Specify the character string that is printed at the bottom of each page. A maximum of 30 characters can be entered, enclosed in apostrophes. The text on the listing will be centered in the same way it is entered.

RTGDTA
Specifies the routing data used to start the first routing step in the job. The routing data is used to determine the routing entry that identifies the program that the job runs.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls for routing data is used for this job.

*JOBD: The routing data specified in the job description is used to start the routing steps.

routing-data: Specify the character string that is used as routing data for the job. A maximum of 80 characters can be entered, enclosed in apostrophes if necessary.

CURLIB
Specifies the name of the current library associated with the job being run.

*SAME: The current value for the parameter does not change.

*JOBCTL: The Job Scheduler job control is used for the submitted job.

*USRPRF: The current library in the user profile where the submitted job runs is used as the current library for the submitted job.

*CRTDFT: There is no current library for the submitted job. If objects are created in the current library, QGPL is used as the default current library.

current-library-name: Specify the name of a library used as the current library of the submitted job.

LIBL
Specifies the name of the library list that is used to search for any operating system object names that were specified without a library qualifier. If you want to select a library list from a list, place the cursor within the LIBL parameter and press F4.

*SAME: The current value for the parameter does not change.

*JOBD: The library list in the job description used with this job is used as the initial user part of the library list for the job.

*SYSVAL: The system default user library list is used by this job. It contains the library names that were specified in the system value, QUSRLIBL, at the time that the job is started.

*NONE: The user portion of the initial library list for this job will be empty.

*JOBCTL: The Job Scheduler job control is used for the library list.

library-list-name: Specify the name of the library list that you want to use for this job.

LOG
Specifies the message logging values used to determine the amount and type of information sent to the log by this job. This parameter has three elements: the message (or logging) level, the message severity, and the level of message text. If no values are specified on this parameter, the values specified in the job description associated with this job are used.

Element 1: Level

*SAME: The current value for the parameter does not change.

*JOBCTL: The value specified in the Job Scheduler job controls for logging is used for this job.

*JOBD: The value specified for message logging in the job description is used for this job.

message-level: Specify a value, ranging from 0 to 4, that specifies the message logging level used for this job's messages.

0: No information is logged for the job.

1: The following information is logged: All messages sent to the job's external message queue with a severity level greater than or equal to the message severity specified (this includes the indications of job start, job end and job completion status).

2: The following information is logged:

  • Logging level 1 information

  • Requests or commands being logged from a CL program for which messages are issued with a severity code greater than or equal to the severity level specified.

  • All messages associated with a request, or commands being logged from a CL program, that results in a high-level message with a severity level greater than or equal to the severity specified.

3: The following information is logged:

  • Logging level 1 information

  • All requests or commands being logged from a CL program.

  • All messages associated with a request, or commands being logged from a CL program, that results in a high-level message with a severity level greater than or equal to the severity specified.

4: The following information is logged:

  • All requests or commands being logged from a CL program and all messages with a severity code greater than or equal to the severity specified, including trace messages.

    Note: A high-level message is one that is sent to the program message queue of the program that received the request or commands being logged from a CL program.

  • Message severity

    *SAME: The current value for the parameter does not change.

    *JOBCTL: The value specified in the Job Scheduler job controls for message severity is used for this job.

    *JOBD: The value specified for message logging in the job description is used for this job.

    message-severity: Specify a value, ranging from 00 to 99, that specifies the lowest severity level that causes an error message to be logged in the job's log.

  • Message text

    *SAME: The current value for the parameter does not change.

    *JOBCTL: The value specified in the Job Scheduler job controls for message text is used for this job.

    *JOBD: The value specified for message logging in the job description is used for this job.

    *MSG: Only message text is written to the job's log or shown to the user.

    *SECLVL: Both the message text and message help of the error message is written to the job's log or shown to the user.

    *NOLIST: No job log is produced if the job competes normally. If the job ends abnormally (if the end of job code is 20 or higher), a job log is produced. The messages appearing in the job's log contain both message text and online help information.

LOGCLPGM
Specifies whether the commands that are 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 *JOB has been specified for the Message logging prompt (LOG parameter) in the Create CL Program (CRTCLPGM) command, the flag set in the LOGCLPGM parameter Log CL program commands prompt (LOGCLPGM parameter) is used. Other values for the Message logging prompt (LOG parameter) override the Log CL program commands prompt (LOGCLPGM parameter). The commands are logged in the same manner as the requests.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls is used for this job.

*JOBD: The value specified in the job description is used.

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

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

INQMSGRPY
Specifies the way that predefined messages that are sent as a result of running this job are answered. You can specify that no change is made in the way that predefined messages are answered, or that all inquiry messages require a reply, or that a default reply is issued, or that the system reply list is checked for a matching reply as each predefined inquiry message is sent.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls for inquiry message reply is used for this job.

*JOBD: The inquiry message reply control specified in the job description used with this job is used.

*RQD: A reply is required by the receiver of the inquiry message for all inquiry messages that occur when this command is run.

*DFT: The default message reply is used to answer any inquiry messages that occur when this command is run.

*SYSRPYL: The system reply list is checked to see if there is an entry for any inquiry message that is issued as a result of running this job that has a message identifier and any comparison data that match the inquiry message identifier and message data. If a match occurs, the reply value in that entry is used. If no entry exists for that message, a reply is required.

HOLD
Specifies whether this job is held at the time that it is put on the job queue. A job placed on the job queue in the hold state is held until it is released by the Release Job (RLSJOB) command or ended, either by the End Job (ENDJOB) command or by the Clear Job Queue (CLRJOBQ) command.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls for hold on job queue is used for this job.

*JOBD: The value specified in the job description determines whether the job is held when it is put on the job queue.

*YES: The job is held when it is put on the job queue until it is released by a Release Job (RLSJOB) command or ended by an End Job (ENDJOB) command.

*NO: The job is not held when it is put on the job queue.

SWS
Specifies the first settings for a group of eight job switches used with this job. These switches can be set or tested in a CL program and used to control the flow of the program. Only 0's (off) and 1's (on) can be specified in the 8-digit character string.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls for job switches is used for this job.

*JOBD: The value specified in the job description is the first setting for the job's switches.

switch-settings: Specify any combination of eight zeros and ones that is used as the first switch setting for the submitted job.

MSGQ
Specifies the name of the message queue to which a completion message is sent when the submitted job has completed running, either normally or abnormally. If an abnormal ending occurs, the help information for the completion message specifies the possible causes.

*SAME: The current value for the parameter does not change.

*JOBCTL: The value in the Job Scheduler job controls for message queue is used for this job.

*USRPRF: A completion message is sent to the message queue specified in the user profile of the submitter.

*NONE: No completion message is sent.

message-queue-name: Specify the name (library-name/message-queue-name) of the message queue on which the completion message is to be sent.

*LIBL: The library list is used to locate the message queue name.

*CURLIB: The current library is used to locate the message queue name.

library-name: Specify the name of the library where the message queue name is located.

ACGCDE
Specifies the accounting code that is used when logging system resource use for jobs that use this description.

*SAME: The current value for the parameter does not change.

*JOBCTL: The accounting code for jobs using this description is obtained from the job controls.

*JOBD: The accounting code for jobs using this description is obtained from the description.

*USRPRF: The accounting code for jobs using this 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 description.

accounting-code: Specify the accounting code that you want to use for jobs using this description.

RUNPTY
Specifies the run for the job. Run priority is a value ranging from 1 (highest priority) through 99 (lowest priority), that represents the importance of the job when it competes with other jobs for machine resources. This value represents the relative (not absolute) importance of the job. If the job is rerouted, this value is reset according to the job's importance within the job class.

*SAME: The current value for the parameter does not change.

*JOBCTL: The run priority is obtained from the job controls.

*NOCHG: The run priority is not changed when job processing starts.

machine-running-priority: Specify the run priority, ranging from 1 through 99, that the job uses.

Example for CHGJOBJS

Example 1: Changing a Job 

CHGJOBJS JOB(JOB02) APP(ACCTG)
SCDCDE(*DAILY) FSCPERIOD(*ALL)
TEXT('Change to JOB02')

In this example JOB02 is changed. It's application is changed to the accounting application, it is changed to run according to schedule code *DAILY for all fiscal periods.

Error messages for CHGJOBJS

None