ajschange
- Organization of this page
Format
ajschange [-F service-name] [attribute-information-change-options] [schedule-information-change-options] [job-information-change-options] [relationship-change-options] [root-jobnet-execution-order-control-information-change-options] [wait-condition-change-options] [-R] [-L|-E] [-T] [-G|-N|-J] [-S] job-name-or-jobnet-name-or-job-group-name...
Description
Modifies the definition of a unit.
Execution privileges
You must have any of the following JP1 privileges:
- When updating (defining) an element
-
-
JP1_AJS_Admin privilege
-
JP1_AJS_Manager privilege
-
JP1_AJS_Editor privilege
-
- When changing an attribute of an element using the -g, -o, or -m option
-
-
JP1_AJS_Admin privilege
-
Owner of the unit
-
- Cautionary note
-
If User who owns is specified for Executed by for the unit, any JP1 user who has a JP1 privilege level for the jobnet other than JP1_AJS_Admin can only modify a unit he or she owns.
If no JP1 resource group is specified for the unit, any user can perform any operation for the unit even if they do not have the above JP1 privilege level.
If no owner is specified for the unit, any user can modify attributes for the unit even if they do not have the above JP1 privilege level.
Arguments
-F service-name
Specify the name of the target scheduler service.
You can specify a character string of 1 to 30 bytes.
-R
Modifies the definitions of all jobnets, job groups, and jobs contained in the specified unit.
If you specify this option with the -L, -E, -T, -G, -N, and/or -J options, the system modifies the definitions according to the specification of each option.
-L
Modifies the definitions of job groups, jobnets not registered for execution, and jobs.
If you specify this option with the -T, -N, and/or -J options, the system modifies the definitions of jobnets or jobs not registered for execution according to the specification of each option. You cannot specify this option with the -E and/or -G option.
-E
Modifies the definitions of jobs and jobnets registered for execution.
If you specify this option with the -T, -N, and/or -J options, the system modifies the definitions of jobnets or jobs registered for execution according to the specification of each option. You cannot specify this option with the -L and/or -G option.
-T
Modifies the definitions of root jobnets.
If you specify this option with the -E or -L option, the system modifies the definitions of root jobnets according to the specification of each option. If you specify this option with the -N option, the -N option is disabled. You cannot specify this option with the -G or -J option.
-G
Modifies the definitions of job groups.
You cannot specify this option with the -L, -E, -T, -N, -J, or a relationship change option.
-N
Modifies the definitions of jobnets.
If you specify this option with the -T option, this option is disabled. If you specify this option with the -E or -L option, the system modifies the definitions of jobnets according to the specification of each option. You cannot specify this option with the -G or -J option.
-J
Modifies the definitions of jobs.
You cannot specify this option with the -T, -G, or -N option or a relationship change option.
-S
Allows you to change the definition of a suspended jobnet or a job in a suspended jobnet, even if the jobnet is already registered for execution.
If you specify this option together with an option that modifies an item that cannot be modified while a jobnet is suspended, the command terminates abnormally.
job-name-or-jobnet-name-or-job-group-name
Specify the name of the job, jobnet or job group for which you want to modify definitions.
You can specify a character string of 1 to 930 bytes.
You can specify more than one job name, jobnet name, or job group name. You should not, however, specify the following pairs of units, which have different definition information:
-
Job group and manager job group
-
Jobnet and manager jobnet
You can specify a logical host name as a job, jobnet or job group name. You cannot specify an execution ID.
attribute-information-change-options
These options modify the attributes of a unit.
These options are common to all units. (The -H and -I options are, however, exceptions. You can specify the -H and -I options only for manager units.)
- -m permission-mode
-
Specify the permission mode when modifying the JP1 user settings for job execution.
You can specify four octal digits.
The following is the meaning of each digit, starting from the left:
- 1st digit
-
Specify the handling of the user for job execution
0 to 3: Assumes the JP1 user who has registered the jobnet to be the user for job execution.
4 to 7: Assumes the JP1 user who owns the job to be the user for job execution.
- 2nd to 4th digits
-
Specifies any value between 0 and 7.
This option is valid for only jobs. It is invalid if specified for non-job units.
- -o owner-name
-
Modifies the owner of the unit.
You can specify a character string of 1 to 31 bytes.
- -g JP1-resource-group-name
-
Modifies the group name for the owner of the unit.
You can specify a character string of 1 to 63 bytes. Use alphanumeric characters and an underscore (_) to specify the name.
- -C comment
-
Modifies the comment for the unit.
You can specify a character string of 1 to 80 bytes.
- -H manager-host-name
-
Modifies the manager host name.
You can specify this option only for a manager unit.
You can specify a character string of 1 to 255 bytes.
- -I manager-unit-name
-
Modifies the manager unit name.
You can specify this option only for a manager unit.
You can specify a character string of 1 to 961 bytes.
schedule-information-change-options
These options modify the schedule defined for a jobnet (if you modify the schedule, the system will recalculate the schedule upon the end of command execution).
You can specify these options only for a jobnet.
- -D job-group-name
-
Specify the name of the job group in which the target calendar information is defined, when modifying the calendar information.
You can specify a character string of 1 to 930 bytes.
- -d [N,]{[[year/]month/]{[+|*|@]day|[+|*|@]b[-day]|[+]{sun|su|mon|mo|tue|tu|wed|we|thu|th|fri|fr|sat|sa}[:{n|b}]}|en|ud|undefine}
-
Modifies the date on which you want to start executing the jobnet.
You can specify up to 144 dates in one command.
To clear all definitions, specify -d 0, ud, or -d 0, undefine.
-
N
Specify the corresponding rule number if you specify more than one starting date for executing the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
year
Specify the year of the starting date for executing the jobnet.
You can specify a value between 1994 and the value of the SCHEDULELIMIT environment setting parameter for the year. For details about the SCHEDULELIMIT environment setting parameter, see 20.4.2(123) SCHEDULELIMIT in the JP1/Automatic Job Management System 3 Configuration Guide.
By default, the system assumes the year in which you registered the jobnet for execution.
-
month
Specify the month of the starting date for executing the jobnet.
You can specify value between 1 and 12 for the month.
By default, the system assumes the month in which you registered the jobnet for execution.
-
+
Specify the execution start date using the number of days following the base date.
-
*
Specify the execution start date using the number of open days following the base date.
-
@
Specify the execution start date using the number of closed days following the base date.
-
day
Specify the day of the execution start date.
You can specify the following values:
- When specifying an absolute date
-
-
Year/month/day specification: 1 to last day of specified year/month.
-
Month/day specification: 1 to last day of specified month. For February, however, 1 to 29.
-
Day specification: 1 to 31.
-
- When specifying a relative date or the number of open or closed days
-
1 to 35 (days).
If you omit the specification of + (relative date), * (number of open days) or @ (number of closed days), the system assumes an absolute day of the month in which you registered the jobnet for execution.
-
b
Sets the last day of the month to the jobnet start date.
-
-day
Specify the starting date for executing the jobnet using the number of days between the date and the end of the month.
You can specify the following values:
- When specifying an absolute date
-
-
Year/month/day specification: 0 to (last day of specified year/month -1).
-
Month/day specification: 0 to (last day of specified month -1). For February, however, 0 to 28.
-
Day specification: 0 to 30.
-
- When specifying a relative date or the number of open or closed days
-
0 to 34 (days).
You can specify this option with + (relative date), * (number of open days) or @ (number of closed days).
-
sun|su|mon|mo|tue|tu|wed|we|thu|th|fri|fr|sat|sa
Specify Sunday, Monday, Tuesday, Wednesday, Thursday, Friday and Saturday as the starting date for executing the jobnet.
-
n
Specify the week for the day; a value between 1 and 5 (specifying 1 for Sunday, for example, indicates the first Sunday of the month).
By default, the system assumes the start date to be the next day of the week after the date when the jobnet was registered for execution and the date when the ajsschedule command was executed. If you do not specify anything when either year or month is specified for the execution start date, the system assumes the first week when you register anything for execution and when you execute the ajsschedule command.
-
en
Changes the defined execution start date to the date on which you registered the jobnet for execution.
-
ud|undefine
Clears the entire schedule for the jobnet.
If you specify this option, specify 0 for N (jobnet rule number).
Specifying this option causes the -d, -t, -V, -W, -K, -y, -s, and -h options to be disabled.
-
- -t [N,][+]hour:minute
-
Modifies the time at which you want to start executing the jobnet.
You can specify up to 144 times in one command.
-
N
Specify the corresponding rule number if you specify more than one starting date for executing the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
+
Handles the time specified with hour:minute as a relative time.
By default, the system handles the specified time as an absolute time.
-
hour:minute
Specify the starting time for executing the jobnet.
You can specify a value between 0 and 47 for the hour.
You can specify a value between 0 and 59 for the minute.
-
- -V [N,]{hour:minute|M-minute|U-minute|C-minute}
-
Modifies the delay time for starting the jobnet.
You can specify up to 144 times in one command.
-
N
Specify the corresponding rule number if you specify more than one delay time for starting the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
hour:minute
Specify an absolute time.
You can specify a value between 0 and 47 for the hour.
You can specify a value between 0 and 59 for the minute.
-
M-minute
Specify the number of minutes relative to the starting time for executing the root jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
U-minute
Specify the number of minutes relative to the starting time for executing the upper-level jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
C-minute
Specify the number of minutes relative to the starting time for executing the relevant jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
- -W [N,]{hour:minute|M-minute|U-minute|C-minute}
-
Modifies the delay time for ending the jobnet.
You can specify up to 144 times in one command.
-
N
Specify the corresponding rule number if you specify more than one delay time for ending the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
hour:minute
Specify an absolute time.
You can specify a value between 0 and 47 for the hour.
You can specify a value between 0 and 59 for the minute.
-
M-minute
Specify the number of minutes relative to the starting time for executing the root jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
U-minute
Specify the number of minutes relative to the starting time for executing the upper-level jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
C-minute
Specify the number of minutes relative to the starting time for executing the relevant jobnet.
You can specify a value between 1 and 2,879 for the minute.
-
- -K [N,]linked-rule-number
-
Modifies the rule number to be linked with that for the upper-level jobnet if you have more than one schedule defined.
You can specify up to 144 numbers in one command. You cannot specify a rule number for the root jobnet.
-
N
Specify the rule number for the schedule for the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
linked-rule-number
Specify the rule number for the upper-level jobnet that corresponds to the above rule number.
-
- -y [N,]processing-cycle,{y|m|w|d}
-
Modifies the processing cycle for the jobnet.
You can specify up to 144 processing cycles.
-
N
Specify the corresponding rule number if you specify more than one delay time for starting the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
processing-cycle, {y|m|w|d}
Modify the processing cycle and its unit (for example, specify -y 6, m to process the jobnet at intervals of six months).
-
y
Specifies the processing cycle in years. You can specify a value between 1 and 9 for the processing cycle.
-
m
Specifies the processing cycle in months. You can specify a value between 1 and 12 for the processing cycle.
-
w
Specifies the processing cycle in weeks. You can specify a value between 1 and 5 for the processing cycle.
You cannot specify this if an open day or closed day is used to define the starting date for executing the jobnet. If you specify this, the schedule is calculated assuming that one week is equal to seven open days or seven closed days. We recommend that you specify the processing cycle on a daily basis. A good example would be "7,d", instead of "1,w".
-
d
Specifies the processing cycle in days. You can specify a value between 1 and 31 for the processing cycle.
-
- -s [N,] {af|be|no|ca}
-
Modifies the method of shifting the execution date if the scheduled date of jobnet execution falls on a closed day in the JP1/AJS3 calendar.
You can specify up to 144 methods in one command.
-
N
Specify the corresponding rule number if you specify more than one delay time for starting the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
af
Executes the jobnet by shifting the execution day to a day after the scheduled date of execution.
-
be
Executes the jobnet by shifting the execution day to a day before the scheduled date of execution.
-
no
Forcibly executes the jobnet even if the scheduled date of execution is a closed day, provided a scheduler service is running.
-
ca
Does not execute the jobnet if the scheduled date of execution is a closed day.
-
- -h [N,] shift-days
-
If you specify af (shifting to a day after the execution day) or be (shifting to a day before the execution day) for the -s option, the -h option specifies the period into which the system can shift the execution day.
You can specify up to 144 periods.
-
N
Specify the corresponding rule number if you specify more than one delay time for starting the jobnet.
You can specify a value between 1 and 144.
By default, the system assumes 1 as the rule number (that is, you will modify a schedule having a rule number of 1).
-
shift-days
You can specify a number between 1 and 31 (days). (For example, specify -s af -h 5 if you want the system to find a substituting execution day by selecting each following day within five days including the scheduled execution day.)
-
- -p year/month/day
-
Modifies the expiration date for jobnet execution.
-
year
Specify the year of the expiration date.
You can specify a value between 1994 and the value of the SCHEDULELIMIT environment setting parameter for the year. For details about the SCHEDULELIMIT environment setting parameter, see 20.4.2(123) SCHEDULELIMIT in the JP1/Automatic Job Management System 3 Configuration Guide.
-
month
Specify the month of the expiration date.
You can specify value between 1 and 12 for the month.
-
day
Specify the day of the expiration date.
You can specify a value between 1 and 31 for the day.
-
- -l number-of-logs-to-keep
-
Modifies the number of logs to store the results of jobnet execution.
You can specify a number between 1 and 99 (logs).
You can, however, enable the system setting option to increase the number of generations to up to 999.
- -n priority-value
-
Modifies the assumed value of the execution priority for jobs in the jobnet.
You can specify a value between 1 and 5.
The lowest priority is 1 and the highest is 5.
- -b {y|w|a|n}
-
Modifies the hold attribute for the jobnet. If you specify w or a for a nested jobnet, the system assumes n.
-
y
Holds the execution of the jobnet.
-
w
Holds execution only if the previous execution of the jobnet has terminated abnormally or with a warning.
-
a
Holds execution only if the previous execution of the jobnet has terminated abnormally.
-
n
Does not hold the execution of the jobnet.
One of the job information change options (the option for modifying the job hold attribute) has the same name as this option. Be careful not to mix up these options when specifying wildcard characters if there are several types of units.
-
job-information-change-options
These options modify the definition information for a job.
The following table lists the job information change options that can be used for individual jobs.
No. |
Job |
Job information change option |
---|---|---|
1 |
Unix job and Unix job for recovery |
|
2 |
PC job and PC job for recovery |
|
3 |
custom Unix job and custom Unix job for recovery |
|
4 |
custom PC job and custom PC job for recovery |
|
5 |
QUEUE job and QUEUE job for recovery |
|
6 |
OR job and OR job for recovery |
None |
7 |
judgment job and judgment job for recovery |
-b {y|n} |
8 |
flexible job and flexible job for recovery |
|
9 |
HTTP Connection job and HTTP Connection job for recovery |
|
- -c command-text
-
Modifies a command text.
You can specify a character string of 1 to 1,023 bytes.
- -z script-file-name
-
Modifies the name of the script file for a Unix job. For a PC job, flexible job, or QUEUE job, this option modifies the name of the execution file.
You can specify a character string of 1 to 511 bytes.
- -v environment-variable-file-name
-
Modifies the environment variable file name.
Use a full path to specify the file name.
You can specify a character string of 1 to 511 bytes.
- -i standard-input-file-name
-
Modifies the standard input file name.
Use a full path to specify the file name.
You can specify a character string of 1 to 511 bytes.
- -u standard-output-file-name
-
Modifies the standard output file name.
Use a full path to specify the file name.
You can specify a character string of 1 to 511 bytes.
You can output the standard output file as a temporary file by specifying $JP1AJS2_JPQSTDOUTTEMP$.
You can also specify a macro variable.
- -e standard-error-output-file-name
-
Modifies the standard error output file name.
Use a full path to specify the file name.
You can specify a character string of 1 to 511 bytes.
- -w warning-threshold
-
Modifies the threshold value for completion with a warning.
You can specify a value between 0 and 2,147,483,647.
If the specified value is greater than the abnormal threshold, the value is defined as the abnormal threshold value.
- -a abnormal-threshold
-
Modifies the threshold value for abnormal end.
You can specify a value between 0 and 2,147,483,647.
If the specified value is smaller than the abnormal threshold, the value is defined as the abnormal threshold value.
A value that is smaller than the lower limit or greater than the upper limit of the return code to be automatically retried cannot be specified if the retry settings for the unit to be updated is set and a return code to be automatically retried is specified.
- -j job-execution-agent-host-name-or-relay-agent-name
-
Modifies the name of the job execution agent host or the relay agent.
For a flexible job, if the value for @SYSTEM is used for update, the definition of the relay agent name is initialized.
You can specify a character string of 1 to 255 bytes.
- -U remote-execution-user
-
Modifies the name of the user who executes the job.
You can specify a character string of 1 to 63 bytes.
- -b {y|n}
-
Modifies the hold attribute for the job.
This option cannot be specified for a job specified in a start condition.
-
y
Holds the execution of the job.
-
n
Does not hold the execution of the job.
One of the schedule information change options (the option for modifying the job hold attribute) has the same name as this option. Be careful not to mix up these options when specifying wildcard characters if there are several types of units.
-
- -q queue-name
-
Modifies the name of the queue for queuing the job.
You can specify a character string of 1 to 63 bytes.
- -k job-name
-
Modifies the job name.
You can specify a character string of 1 to 63 bytes.
relationship-change-options
These options modify the relationship of the execution order for jobnets and jobs. You can specify these options only for a jobnet.
You can specify up to 20 -A options (make relation options) and 20 -B options (break relation options) in one command.
- -A preceding-unit-name, succeeding-unit-name [,{seq|con}]
-
Specify the names of the preceding and succeeding units between which you want to create a relationship (associate units). You must also specify the connection type.
You can specify a character string of 1 to 30 bytes for each unit name (preceding-unit-name and succeeding-unit-name).
If the relation line is already set for the preceding and succeeding units whose relationship is to be set, the command returns 0 and ends normally.
-
seq
Specifies forward connection.
-
con
Specifies the judgment connection of a judgment job and a dependent unit.
The system does not create a relationship in any of the following cases:
-
If the same unit name is specified for the preceding unit as well as the succeeding unit
-
If the unit of the specified preceding unit name or succeeding unit name does not exist
-
If a recovery unit is specified as the preceding unit name, and a regular unit is specified as the succeeding unit name
-
If you attempt to set a reverse relationship for units between which you have already set a relationship
-
If you specify a relationship and cancel a relationship, at the same time, between the same preceding unit and succeeding unit
-
If you specify a job group, manager job group, manager jobnet, or root jobnet
-
If there are two or more preceding units when the succeeding unit is a judgment job
-
If the preceding unit is other than an event job when the succeeding unit is an OR job
-
If you specify a unit other than a judgment job as the preceding unit for a judgment connection
-
If the judgment connection of a judgment job and a dependent unit makes other than 1-to-1 matching
-
If you specify a start condition unit name for the name of the preceding or succeeding unit
-
- -B preceding-unit-name, succeeding-unit-name
-
Specify the names of the preceding and succeeding units between which you want to break a relationship (cancels the association between units).
You can specify a character string of 1 to 30 bytes for each unit name.
If the relation line does not exist for the preceding and succeeding units whose relationship is to be broken, the command returns 0 and ends normally.
root-jobnet-execution-order-control-information-change-options
These options modify the information that control the execution order of root jobnets based on jobnet connectors. You can specify these options only for a root jobnet that has not been registered, and for a planning group whose units have not been registered.
- -M whether-to-control-the-root-jobnet-execution-order
-
Specify whether to control the root jobnet execution order.
-
y: The root jobnet execution order is controlled.
-
n: The root jobnet execution order is not controlled.
If you change the value of this option from y to n, the specifications of the -O (jobnet connector name), -Qh (host to connect), and -Qs (connection service name) options are cleared (neither y nor n is set). For the -P (root jobnet execution order control method) and -Qx (linkage of root jobnet execution order control between scheduler services) options, n is set.
-
- -O jobnet-connector-name
-
Specify the full name of the unit of the jobnet connector to be connected. You can specify a character string of 1 to 930 bytes.
You can specify this option if y is specified for the -M option. Specifying this option if n is specified for the -M option results in an error.
- -P root-jobnet-execution-order-control-method
-
Specify the method for controlling the root jobnet execution order.
-
y: Root jobnets are executed synchronously with jobnet connectors.
-
n: Root jobnets are executed asynchronously with jobnet connectors.
You can specify this option if y is specified for the -M option. Specifying this option if n is specified for the -M option results in an error.
-
- -Qx linkage-of-root-jobnet-execution-order-control-between-scheduler-services
-
Specify whether to establish linkage between scheduler services when the execution order of root jobnets is controlled.
You can only specify this option for a planning group whose units have not been registered, and for a root jobnet that has not been registered.
If you change the value of this option from y to n, the specifications of the -Qh (host to connect) and -Qs (connection service name) options are cleared (neither y nor n is set).
-
y
Linkage between scheduler services is established.
Root jobnet execution order control is linked with jobnet connectors including those defined on other hosts or those defined in other scheduler services.
-
n
Linkage between scheduler services is not established.
Root jobnet execution order control is linked with only jobnet connectors defined in the same scheduler service.
-
- -Qh connection-host-name
-
Specify the name of the host on which a jobnet connector to be connected is defined. You can specify a character string of 1 to 255 bytes. You cannot specify space, tab, or linefeed characters.
You can specify this option only if y is specified for the -Qx option (linkage of root jobnet execution order control between scheduler services).
- -Qs connection-service-name
-
Specify the name of the scheduler service on which a jobnet connector to be connected is defined. You can specify a character string of 1 to 30 bytes. You cannot specify a null string ("") to reset the scheduler service name definition to the default status.
You can specify this option only if y is specified for the -Qx option (linkage of root jobnet execution order control between scheduler services).
wait-condition-change-options
These options modify wait conditions.
You can apply these options to suspended units by specifying them together with the -S option.
- -Qm {and|or}
-
Specify the wait method. This option must be specified together with the -Qn option and the -Qu option if no units whose ends are being waited for are defined for the target unit.
If "" is specified for this option, and is assumed.
-
and
The unit starts executing when all units whose ends are being waited for finish executing.
-
or
The unit starts executing when any one of the units whose ends are being waited for finish executing.
-
- -Qn {y|n}
-
Specify how the unit behaves when there are no applicable generations of the root jobnet of the unit whose end is being waited for. This option must be specified together with the -Qm option and the -Qu option if no units whose ends are being waited for are defined for the target unit.
If "" is specified for this option, n is assumed.
-
y
Start executing.
-
n
Do not start executing.
-
- -Qu name-of-unit-whose-end-is-being-waited-for
-
Specify the full path name of an additional unit whose end is being waited for by a wait condition. You can specify a character string of 1 to 930 bytes. The unit you specify is added to the units already defined for the wait condition.
If you specify a unit that is already defined as a unit whose end is being waited for by that wait condition, the command ends normally without the unit being added.
You cannot add more than 32 units whose ends are being waited for.
You can specify multiple instances of this option together with the -Qd option (which deletes units whose ends are being waited for).
If you specify this option together with the -Qd option and specify the same unit name in both options, the -Qd option takes precedence and the specified unit is deleted.
This option must be specified together with the -Qm option and the -Qn option if the command targets a unit for which no units whose ends are being waited for are defined.
- -Qd name-of-unit-whose-end-is-being-waited-for-to-delete
-
Specify the full path name of a unit whose end is being waited for that you want to delete from a wait condition. You can specify a character string of 1 to 930 bytes. The unit you specify is removed from the wait conditions defined for the target unit.
If you specify a unit that is not defined as a unit whose end is being waited for by the wait condition, the command ends normally.
You can specify multiple instances of this option together with the -Qu option (which adds units whose ends are being waited for).
If you specify this option together with the -Qu option and specify the same unit name for both options, the -Qd option takes precedence and the specified unit is deleted.
- -Qz
-
Deletes all units whose ends are being waited for defined in the wait condition.
You cannot specify this option with the -Qu option or -Qd option.
- -Qg {exec|execdeffer|none}
-
If a jobnet with start conditions is specified as the jobnet whose end is being waited for, specify the behavior when the execution generation ends abnormally.
To specify this option for a unit for which no unit whose end is being waited for is specified, you must also specify the -Qm, -Qn, and -Qu options.
If "" is specified for this option, none is assumed.
-
exec
Start executing.
-
execdeffer
Do not start executing. Note, however, that if the execution generation is in the Skipped so not exe. status, execution starts.
-
none
Do not start executing.
-
- -QU {y|n}
-
Specify the behavior when a jobnet with start conditions is specified as the jobnet whose end is being waited for, and the status of the monitoring generation changes to Unmonitored + Ended.
To specify this option for a unit for which no unit whose end is being waited for is specified, you must also specify the -Qm, -Qn, and -Qu options.
If "" is specified for this option, n is assumed.
-
y
Start executing.
-
n
Do not start executing.
-
Notes
-
Either of the following users can change the unit definition:
-
A user who was granted the update privilege when the unit was defined or when the unit's attributes were changed
-
A JP1 user mapped to the OS user who has Administrators or superuser privileges
Note, however, that if yes is set after changing the ADMACLIMIT environment setting parameter from its default, even a JP1 user who was mapped to an OS user with Administrators or superuser privileges must have the update privilege.
-
-
We recommend that you not execute this command during the execution of a jobnet. (This command terminates abnormally if some other process is using the target unit. You cannot use JP1/AJS3 - View to manipulate or update a unit while you are modifying the definition of the unit with this command. You cannot execute a unit while you are manipulating it.)
-
We recommend that you cancel the registration of jobnets before attempting to change the contents of the definitions of registered jobnets (Otherwise, you cannot change the related information). Use the ajsleave command when canceling the registration of jobnets.
-
If you specify any invalid option for the unit, this command will terminate abnormally. Do not use wildcard characters for modification (use a regular expression, such as A* for a name starting with A).
-
Modifying the schedule disables any temporary plan modification you specified previously.
-
If you shift the execution start day to a day previous to the target day, the schedule for the past becomes invalid; the system does not execute the jobnet.
-
If you use the command to define a jobnet, the system does not check the consistency of the execution order of units. A jobnet in which units will result in a loop or a judgment job without any associated dependent units results in an error and is placed in Invalid exe. seq. status.
-
To leave information undefined (default), specify "" for the option.
-
If you specify the -t, -V, -W, -K, -y, -s, or -h option with a rule number not contained in the schedule definition for the jobnet, the command will end normally, without adding any schedule. When adding a schedule rule, also specify the -d option.
-
If the release target jobnet (root jobnet for which release entry is made) is changed, the jobnet definitions in Being applied status are also changed.
-
You cannot control the execution order of release target jobnets (root jobnets for which release entry is made).
-
You cannot use the -A or -B option to change the definition of a relation line associated with a suspended unit. To change a relation line for a suspended unit, use the ajschgnet command.
Return values
0 |
Normal end |
Multiple of 4 within the range from 4 to 124 |
Abnormal end |
Additional information
To leave information undefined (default) for an attribute information change, schedule information change or job information change option, specify "" for the option.
Example 1
The following command changes the starting time for executing jobnet net1 to 17:00 (absolute time) on every Friday in October 2010:
ajschange -d 2010/10/fr -y 1, w -t 17:00 net1
Example 2
The following command changes the standard output file for job net1/job1 to /dev/null:
ajschange -u /dev/null net1/job1
Example 3
The following command creates a relationship between two jobs, net1/job1 and net1/job2:
ajschange -A job1, job2 net1
Example 4
The following command sets the execution order control information for root jobnet /net1 so that it is executed synchronously with jobnet connector /net2/netconl:
ajschange -M y -O /net2/netconl -P y /net1
The following command cancels the execution order control for root jobnet /net1:
ajschange -M n /net1