Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2

[Contents][Glossary][Index][Back][Next]

2.2 Setting up the scheduler service environment

To set up the scheduler service environment, perform the necessary setup operations in the manager environment (JP1/AJS3 - Manager). Nothing is required in the agent environment (JP1/AJS3 - Agent).

The table below describes the environment setting parameters to be used to set the scheduler service environment in the manager environment (JP1/AJS3 - Manager).

To determine whether an environment setting parameter is to be set in Windows or UNIX, see the Applicable OS column.

Table 2-2 Environment setting parameters (scheduler service environment setup)

No. Definition key Environment setting parameter Definition Applicable OS Applicable product
1 [JP1_DEFAULT\JP1AJSMANAGER] "DEFAULTSERVICENAME"=#1 The name of the default scheduler service Windows
UNIX		 M
2 "REMNETSERVICENAME"=#1 The name of the scheduler service that executes a remote jobnet Windows
UNIX		 M
3 "TRACELOGFILE"=#1 The name of the scheduler trace log file Windows
UNIX		 M
4 "VRSHIFT_IMMINT"=#1 Whether a jobnet stops immediately when it is interrupted or killed Windows
UNIX		 M
5 "VRSHIFT_INTRERUN"=#1 Whether succeeding units are rerun when a jobnet is interrupted Windows
UNIX		 M
6 "IPC_TIMEOUT"=#1 Remote communication timeout Windows
UNIX		 M
7 "IPC_LOCALTIMEOUT"=#1 Local communication timeout Windows
UNIX		 M
8 "IPCRETRYINTERVAL"=#1 Retry interval Windows
UNIX		 M
9 "IPCRETRYCOUNT"=#1 Retry count Windows
UNIX		 M
10 "EVENTRETRY"=#1 The action to be taken for an event service connection failure Windows
UNIX		 M
11 "MONLOG"=#1 Whether messages related to establishing and terminating connections from JP1/AJS3 - View to the scheduler service are to be output to the scheduler log Windows
UNIX		 M
12 "REUSELOGON"=#1 The method used to start the logon-session process Windows M
13 "LOGONSHMAX"=#1 The number of sessions that can share logon resources Windows M
14 [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER]#2 "MAXSESSION"= The maximum number of simultaneous sessions Windows
UNIX		 M
15 "AJSINETDLOGSIZE"= The size of the ajsinetd internal log Windows
UNIX		 M
16 "MONSYSLOG"=

In Windows:
Whether messages related to starting and terminating the ajsinetd process and the monitor server are to be output to the Windows event log

In UNIX:
Whether messages related to starting and terminating the ajsinetd process and the monitor server are to be output to the integrated trace log.
 Windows
UNIX		 M
17 "AUTHLOG"= Whether messages related to user authentication are to be output to the scheduler log Windows
UNIX		 M
18 "AUTHSYSLOG"=

In Windows:
Whether messages related to user authentication are to be output to the Windows event log and integrated trace log

In UNIX:
Whether messages related to user authentication are to be output to the syslog and integrated trace log
 Windows
UNIX		 M
19 "HIDEOTHERLHOST"= The scheduler services to be displayed for a login to JP1/AJS3 - View Windows
UNIX		 M
20 [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name]#2 "AUTORESTARTCOUNT"= The number of attempts to be made to restart the scheduler service Windows
UNIX		 M
21 "RESTARTCLRTIME"= The period of time until the restart count is cleared Windows
UNIX		 M
22 "MASTERDABEND"= The action to be taken for a scheduler service error Windows
UNIX		 M
23 "AJSLOGOUTPUTDEST"= The output-destination setting for the scheduler log file Windows
UNIX		 M
24 "LOGSIZE"= The size of the scheduler log file (when the file is output by a scheduler service) Windows
UNIX		 M
25 "AJSLOGFILE1"= The name of scheduler log file 1 Windows
UNIX		 M
26 "AJSLOGFILE2"= The name of scheduler log file 2 Windows
UNIX		 M
27 "LOGDLOG"= Whether log data about starting and terminating the scheduler log output process (ajslogd.exe for Windows and ajslogd for UNIX) is to be output to the scheduler log Windows
UNIX		 M
28 "LOGDSYSLOG"=

In Windows:
Whether log data about starting and terminating the scheduler log output process (ajslogd.exe) is to be output to the Windows event log and the integrated trace log

In UNIX:
Whether log data about starting and terminating the scheduler log output process (ajslogd) is to be output to syslog and the integrated trace log
 Windows
UNIX		 M
29 "AJSLOGOUTPUTYEAR"= Whether the year in a scheduler log date is to be output Windows
UNIX		 M
30 "AJSLOGOUTPUTEXTEND"= The setting for extended output of a scheduler log Windows
UNIX		 M
31 "AUTOSTART"= Whether a scheduler service is to be started automatically Windows
UNIX		 M
32 "SESSIONTIMEOUT"= The connection timeout period Windows
UNIX		 M
33 "AJSSERVICEID"= The scheduler service identification number Windows
UNIX		 M
34 "ISAMWRITEMODE"= The write mode for updating an ISAM file Windows
UNIX		 M
35 "TABLENAMEPREFIX"= The table name prefix Windows
UNIX		 M
36 "TABLENAMEPOSTFIX"= The table ID Windows
UNIX		 M
37 "RDBAUTHID"= The RDB permission identifier Windows
UNIX		 M
38 "RDBUSER"= The RDB access user name Windows
UNIX		 M
39 "RDBPASSWORD"= The RDB user password Windows
UNIX		 M
40 "RDBCHECKINTERVAL"= The RDB server disconnection detection interval Windows
UNIX		 M
41 "RDBHOST"= The name of the host at the RDB connection destination Windows
UNIX		 M
42 "RDBPORT"= RDB port number Windows
UNIX		 M
43 "RDBIPC"= The method used to communicate with the RDB server Windows
UNIX		 M
44 "RDBSENDMEMSIZE"= The size of send-data memory for RDB interprocess memory communication Windows
UNIX		 M
45 "RDBRECVMEMSIZE"= The size of receive-data memory for RDB interprocess memory communication Windows
UNIX		 M
46 "RDBCONNECTWAITTIME"= The maximum wait time for connection to RDB Windows
UNIX		 M
47 "AJSCHARCODE"= Character set Windows
UNIX		 M
48 "AJSTMPDIR"= The name of the directory for temporary files Windows
UNIX		 M
49 "JOBINFDIR"= The name of the directory for job error information Windows
UNIX		 M
50 "AJSBKUROOT"= The name of the directory for backup information Windows
UNIX		 M
51 "HNTRLOGLEVEL"= The level of the messages to be output to the integrated trace log file Windows
UNIX		 M
52 "SYSLOGCODE"= The character set for outputting a log file UNIX M
53 "AJSSYSLOG"=

In Windows:
Whether messages about starting and terminating a scheduler service are to be output to the Windows event log

In UNIX:
Whether messages about starting and terminating a scheduler service are to be output to the syslog file
 Windows
UNIX		 M
54 "NETSYSLOG"=

In Windows:
Whether messages about starting and ending a jobnet are to be output to the Windows event log

In UNIX:
Whether messages about starting and ending a jobnet are to be output to the syslog file
 Windows
UNIX		 M
55 "JOBSYSLOG"=

In Windows:
Whether messages about starting and ending a job in a jobnet are to be output to the Windows event log

In UNIX:
Whether messages about starting and ending a job in a jobnet to be output to be output to the syslog file
 Windows
UNIX		 M
56 "AJSLOG"= Whether messages about starting and terminating a scheduler service are to be output to the scheduler log file Windows
UNIX		 M
57 "NETLOG"= Whether messages about starting and ending a jobnet are to be output to the scheduler log file Windows
UNIX		 M
58 "JOBLOG"= Whether messages about starting and ending a job in a jobnet are to be output to the scheduler log file Windows
UNIX		 M
59 "OPELOG"= Whether the operation log is to be output Windows
UNIX		 M
60 "LOGINFOALL"= The output format of logs Windows
UNIX		 M
61 "REFLOG"= Whether the reference log is to be output Windows
UNIX		 M
62 "LOGHEADER"= Whether log information is to be output with the process ID added Windows
UNIX		 M
63 "INFOLOG"= Whether the information log is to be output Windows
UNIX		 M
64 "ROOTJOBNETSCHEDULERANGE"= The valid range for a root jobnet schedule Windows
UNIX		 M
65 "VIEWSTATUSRANGE"= The range of the generation information used as the basis for acquiring the status (definition for displaying the status in JP1/AJS3 - View) Windows
UNIX		 M
66 "STARTMODE"= The startup mode of a scheduler service Windows
UNIX		 M
67 "OVERSCHEDULE"= The mode for skipping a jobnet Windows
UNIX		 M
68 "SUPPRESS"= Whether the execution of a job in the jobnet and a jobnet is suppressed Windows
UNIX		 M
69 "EXECDEFER"= The repeat method of a jobnet Windows
UNIX		 M
70 "JOBSTATUSPORT"= The service name of the port used to acquire the job status Windows
UNIX		 M
71 "QUEUELESSMULTIREQ"= The maximum number of queueless job requests Windows
UNIX		 M
72 "UNITDEFINERELOAD"= Whether the jobnet definition is updated as soon as it is changed Windows
UNIX		 M
73 "MAXSAVEGEN"= The maximum number of saved generations Windows
UNIX		 M
74 "AJSPRINTNETSCHPRF"= The method for handling the schedule rules of nested jobnets Windows
UNIX		 M
75 "SUBMITRETRYINTERVAL"= The retry interval for submit processing Windows
UNIX		 M
76 "JOBEXECIPCBUFSIZE"= The size of the job execution information communication buffer for a scheduler service Windows
UNIX		 M
77 "BACKGROUNDLEAVE"= The method used to delete generations due to cancellation of registration or management of the number of saved generations Windows
UNIX		 M
78 "REQDAGTREQCONNECTTIMEOUT"= The timeout period for communication with the queueless agent service Windows
UNIX		 M
79 "REQDAGTRECONNECTTIMEOUT"= The timeout period for recovery processing for communication with a queueless agent service Windows
UNIX		 M
80 "COMMANDEVENT"= Whether a JP1 event is issued when a command is executed or an operation is executed from JP1/AJS3 - View Windows
UNIX		 M
81 "NONRELOADHOLDING"= Whether the definition of a unit on hold is reloaded Windows
UNIX		 M
82 "RJCUSE"= Whether the execution order of root jobnets spread among different scheduler services is to be controlled by using a jobnet connector Windows
UNIX		 M
83 "JOBDELAYWARNMSG"= Whether a start message is to be output to the integrated trace log when a scheduler service is started. The start message is generated when the scheduler service is stopped, if a job whose termination delay is monitored in accordance with a period of time required for the execution restarts its operation in the agent. Windows
UNIX		 M
84 "FGRECONLMT"= The number of reconnection attempts when the flow control process cannot communicate with the scheduler service inter-communication control process Windows
UNIX		 M
85 "SAVEGENTYPE"= The method for managing the number of logs to keep resulting from the execution of a jobnet for which start conditions are defined Windows
UNIX		 M
86 "AJSDBTYPE"= The database type Windows
UNIX		 M
87 "AJSDBDIRECTORY"= The name of the database directory Windows
UNIX		 M
88 "AJSSYSDIR"= The system folder of each scheduler service Windows
UNIX		 M
89 "AJSLOGDIR"= The log folder of each scheduler service Windows
UNIX		 M
90 [{JP1_DEFAULT|logical-host-name}\JP1AJS2\GATEWAY]#2 "GWMAXCONNECTION"= The maximum number of concurrent connections for the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd for UNIX) Windows
UNIX		 M
91 "GWPROCESSHA"= Whether the process that manages the scheduler service inter-communication control process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) terminates when the scheduler service inter-communication control process (ajsgwd.exe in Windows and ajsgwd in UNIX) terminates abnormally Windows
UNIX		 M
92 "GWRESTARTCOUNT"= The number of times automatic restart is to be attempted when the scheduler service inter-communication control process terminates abnormally Windows
UNIX		 M

Legend:
M: JP1/AJS3 - Manager

#1
Specify this item directly under the [JP1_DEFAULT\JP1AJSMANAGER] key.

#2
Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.
Note
You can specify a maximum of 20 scheduler services for the physical and logical hosts on a machine. Specify a service name that is unique among all physical hosts of the local host and all logical hosts. For the service name, specify a character string of no more than 30 bytes. You can use alphanumeric characters and the following symbols:
!, #, $, %, +, - (hyphen), . (period), _ (underscore)
Do not use any symbols other than those above.
If you use an invalid character, the command interpreter will not correctly recognize the scheduler service name when it analyzes the command line, and a failure might occur.

The following describes each of the environment setting parameters.

Parameters that are not described here are used for maintenance purposes. Do not change the values of those parameters.

The default value is used whenever a value is not specified for an environment setting parameter.

Organization of this section
(1) "DEFAULTSERVICENAME"="name-of-default-scheduler-service"
(2) "REMNETSERVICENAME="name-of-scheduler-service-executing-a-remote-jobnet"
(3) "TRACELOGFILE"="name-of-scheduler-trace-log-file"
(4) "VRSHIFT_IMMINT"="{V5|V6}"
(5) "VRSHIFT_INTRERUN"="{V5|V6}"
(6) "IPC_TIMEOUT"=dword:remote-communication-timeout-period
(7) "IPC_LOCALTIMEOUT"=dword:local-communication-timeout
(8) "IPCRETRYINTERVAL"=dword:retry-interval
(9) "IPCRETRYCOUNT"=dword:retry-count
(10) "EVENTRETRY"="{yes|no}"
(11) "MONLOG"="{none|all}"
(12) "REUSELOGON"={yes|no}"
(13) "LOGONSHMAX"=dword:number-of-logon-sessions-sharing-logon-resources
(14) "MAXSESSION"=dword:maximum-number-of-simultaneous-sessions
(15) "AJSINETDLOGSIZE"=dword:size-of-ajsinetd-internal-log
(16) "MONSYSLOG"="{none|all}"
(17) "AUTHLOG"="{none|all}"
(18) "AUTHSYSLOG"="{none|all}"
(19) "HIDEOTHERLHOST"="{yes|no}"
(20) "AUTORESTARTCOUNT"=dword:scheduler-service-restart-count
(21) "RESTARTCLRTIME"=dword:time-to-clear-the-restart-count
(22) "MASTERDABEND"="{yes|no}"
(23) "AJSLOGOUTPUTDEST"="{schedule|host}"
(24) "LOGSIZE"=dword:size-of-the-scheduler-log-file (when outputting the scheduler log for a scheduler service)
(25) "AJSLOGFILE1"="name-of-scheduler-log-file-1"
(26) "AJSLOGFILE2"="name-of-scheduler-log-file-2"
(27) "LOGDLOG"="{none|all}"
(28) "LOGDSYSLOG"="{none|all}"
(29) "AJSLOGOUTPUTYEAR"="{yes|no}"
(30) "AJSLOGOUTPUTEXTEND"="{yes|no}"
(31) "AUTOSTART"="{yes|no}"
(32) "SESSIONTIMEOUT"=dword:connection-timeout-period
(33) "AJSSERVICEID"=dword:scheduler-service-id-number
(34) "ISAMWRITEMODE"="{flush|noflush|sync}"
(35) "TABLENAMEPREFIX"="table-name-prefix"
(36) "TABLENAMEPOSTFIX"="table-ID"
(37) "RDBAUTHID"="RDB-permission-identifier"
(38) "RDBUSER"="RDB-access-user-name"
(39) "RDBPASSWORD"="RDB-user-password"
(40) "RDBCHECKINTERVAL"=dword:whether-to-use-the-RDB-server-connection-check-function
(41) "RDBHOST"="RDB-connection-destination-host-name"
(42) "RDBPORT"=dword:RDB-connection-port-number
(43) "RDBIPC"="{MEMORY|DEFAULT}"
(44) "RDBSENDMEMSIZE"=dword:size-of-data-send-memory-for-RDB-interprocess-memory-communication
(45) "RDBRECVMEMSIZE"=dword:size-of-data-receive-memory-for-RDB-interprocess-memory-communication
(46) "RDBCONNECTWAITTIME"=dword:maximum-wait-time-for-connection-to-RDB
(47) "AJSCHARCODE"="{C}"
(48) "AJSTMPDIR"="name-of-directory-for-temporary-files"
(49) "JOBINFDIR"="job-error-information-directory-name"
(50) "AJSBKUROOT"="backup-information-directory-name"
(51) "HNTRLOGLEVEL"="{none|error|warn|info}"
(52) "SYSLOGCODE"="{C}"
(53) "AJSSYSLOG"="{none|all}"
(54) "NETSYSLOG"="{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:connector}|all}"
(55) "JOBSYSLOG"="{none|{abend:warning:hold:enddelay}|all}"
(56) "AJSLOG"="{none|all}"
(57) "NETLOG"="{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer}|all}"
(58) "JOBLOG"="{none|{abend:warning:hold:enddelay}|all}"
(59) "OPELOG"="{none|{alter:stop:entry:leave:plan:intrpt:rerun:kill:change:calendar:delete:restore:define:copy:chgst:suspend:import:start:rgimport:release}|all}"
(60) "LOGINFOALL"="{yes|no}"
(61) "REFLOG"="{none|{backup:export:name:print:schedule:show:rgexport:release}|all}"
(62) "LOGHEADER"="{none|PID}"
(63) "INFOLOG"="{none|{START:REQUEST}|all}"
(64) "ROOTJOBNETSCHEDULERANGE"=dword:{00000018|00000030}
(65) "VIEWSTATUSRANGE"="{today|all}"
(66) "STARTMODE"="{cold|warm|hot}"
(67) "OVERSCHEDULE"="{exec|skip|plan}"
(68) "SUPPRESS"="{none|exec}"
(69) "EXECDEFER"="{oneday|twoday|unlimit}"
(70) "JOBSTATUSPORT"="service-name-of-the-port-for-acquiring-job-status"
(71) "QUEUELESSMULTIREQ"=dword:maximum-number-of-queueless-job-requests
(72) "UNITDEFINERELOAD"="{yes|no}"
(73) "MAXSAVEGEN"=dword:maximum-number-of-saved-generations
(74) "AJSPRINTNETSCHPRF"="{yes|no}"
(75) "SUBMITRETRYINTERVAL"=dword:retry-interval
(76) "JOBEXECIPCBUFSIZE"=dword:buffer-size-for-job-execution-information-communication
(77) "BACKGROUNDLEAVE"="{yes|no}"
(78) "REQDAGTREQCONNECTTIMEOUT"=dword:timeout-period-for-communication
(79) "REQDAGTRECONNECTTIMEOUT"=dword:timeout-period-for-communication
(80) "COMMANDEVENT"="{yes|no}"
(81) "NONRELOADHOLDING"="{yes|no}"
(82) "RJCUSE"="{yes|no}"
(83) "JOBDELAYWARNMSG"="{yes|no}"
(84) "FGRECONLMT"=dword:number-of-reconnection-attempts
(85) "SAVEGENTYPE"="{TOTAL|LEGACY}"
(86) "AJSDBTYPE"="{ISAM|EmbedDB}"
(87) "AJSDBDIRECTORY"="database-directory-name"
(88) "AJSSYSDIR"="name-of-system-directory"
(89) "AJSLOGDIR"="name-of-direcotry-for-log-files"
(90) "GWMAXCONNECTION"=dword:maximum-concurrent-connections
(91) "GWPROCESSHA"="{yes|no}"
(92) "GWRESTARTCOUNT"=dword:number-of-restarting-scheduler-service-inter-communication-control-process

(1) "DEFAULTSERVICENAME"="name-of-default-scheduler-service"

Use this parameter to specify the name of the default scheduler service.

If you have not specified the target scheduler service name (for example, when you execute a command), the system executes processing by using the scheduler service specified in this parameter.

If you execute a command that performs an operation on a unit in an environment in which there are multiple scheduler services, you can omit the -F schedule-service-name option.

Specifiable values
A character string of no more than 30 bytes

Default value
AJSROOT1

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When a process starts

(2) "REMNETSERVICENAME="name-of-scheduler-service-executing-a-remote-jobnet"

Use this parameter to specify the name of the scheduler service that executes a remote jobnet. If you omit this parameter, the scheduler service cannot execute the remote jobnet even if requested to by another host.

Specifiable values
A character string of no more than 30 bytes

Default value
None

Recommended value
Hitachi does not recommend that remote jobnet operation be used.

When the setting takes effect
Immediately (when a remote jobnet process is running)

(3) "TRACELOGFILE"="name-of-scheduler-trace-log-file"

Use this parameter to specify the name of the file to which the trace information of the scheduler service is output. Specify a full path name.

If you omit this parameter, trace information is not output.

The system records the scheduler trace information for the physical host and all logical hosts in the file specified in this parameter. Specify the name of a file on the local disk so that trace information will be reliably recorded.

Because the system creates a new file whenever trace information is output, do not specify the name of an existing file.

Specifiable values
A character string of no more than 255 bytes

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\log\tracelog
  • In UNIX:
    /var/opt/jp1ajs2/log/tracelog

Recommended value
Default value

When the setting takes effect
When a process starts

(4) "VRSHIFT_IMMINT"="{V5|V6}"

Use this parameter to specify whether to immediately change the jobnet status (that is, whether to immediately stop a jobnet) when you interrupt or kill the root jobnet while a scheduler service is suppressing job execution.

Specifiable values

V5
The jobnet status is changed immediately.

V6
The jobnet status is changed when the suppression of job execution is canceled.

Default value
V5

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(5) "VRSHIFT_INTRERUN"="{V5|V6}"

Use this parameter to specify whether to rerun the succeeding units of a nested jobnet that has been interrupted.

Change the parameter value if you do not want to rerun the succeeding units.

In an interrupted nested jobnet, there are some units whose execution has not terminated. Specify V5 to give priority to rerunning the units that follow the interrupted nested jobnet without also executing the units that have not terminated.

This parameter is effective when there is an interrupted nested jobnet before a unit that is to be rerun.

When there is no interrupted nested job ahead of the units to be rerun, but there is a nested job that has ended abnormally, you can rerun the units regardless of the setting of this parameter.

Specifiable values

V5
The units following an interrupted nested jobnet are rerun.

V6
The units following an interrupted nested jobnet are not rerun.

Default value
V6
During a new installation and setup of JP1/AJS3, V5 is set.

Recommended value
V5

When the setting takes effect
When the scheduler service starts

(6) "IPC_TIMEOUT"=dword:remote-communication-timeout-period

Use this parameter to specify the time to wait (timeout) for the originator to start communication with another host.

Customize this parameter if you want to quickly detect, on a fast network connecting machines, a machine that has failed to be activated.

Specify a value other than 0 when you want to set an explicit timeout period rather than depend on the OS timeout period.

For this parameter, the originator's settings are used for execution of the following operations:

If the originator is unable to start communication when the timeout period specified in this parameter expires, an error occurs.

Specifiable values
A hexadecimal value (in seconds) from 0 to 258 (0 to 600 in decimal)
When dword:00000000 is specified, control is determined by the OS timeout period.

Default value
dword:00000000 (0 in decimal)

Recommended value
Default value

When the setting takes effect
When a process starts

(7) "IPC_LOCALTIMEOUT"=dword:local-communication-timeout

Use this parameter to specify the time that the system will wait (timeout) for the originator to start communication for interprocess communication related to a JP1/AJS3 scheduler service. Because this parameter is used for internal processing, use only the standard setting.

Specify a value other than 0 when you want to use an explicit timeout period rather than depend on the timeout period of the OS.

If the originator cannot start communication when the timeout period specified for this parameter expires, an error occurs.

Specifiable values
A hexadecimal value (in seconds) from 0 to 3C (0 to 60 in decimal)
When dword:00000000 is specified, control is determined by the OS timeout period.

Default value
dword:00000000 (0 in decimal)

Recommended value
Default value

When the setting takes effect
When a process starts

(8) "IPCRETRYINTERVAL"=dword:retry-interval

Use this parameter to specify the retry interval when a communication error occurs.

Change this parameter to a value appropriate for the communication error status. If you change the parameter value, you also have to change the IPCRETRYCOUNT environment setting parameter value (retry count).

Each time a retry occurs, the specified value is incremented.

Specifiable values
A hexadecimal value (in seconds) from 0 to A (0 to 10 in decimal)

Default value
dword:00000001 (1 in decimal)

Recommended value
Default value

When the setting takes effect
When a process starts

(9) "IPCRETRYCOUNT"=dword:retry-count

Use this parameter to specify the number of retries attempted when a communication error occurs.

Change this parameter to a value appropriate for the communication error status. If you change this parameter value, you also have to change the IPCRETRYINTERVAL environment setting parameter value (retry interval).

When there is a heavy concentration of scheduler service interprocess communication, a temporary communication error might occur. Specify a value larger than the default value if you will simultaneously start multiple scheduler services or execute many JP1/AJS3 commands at one time.

Specifiable values
A hexadecimal value from 0 to 64 (0 to 100 in decimal)

Default value
dword:00000003 (3 in decimal)

Recommended value
Default value or a value larger than the default value, depending on operating requirements

When the setting takes effect
When a process starts

(10) "EVENTRETRY"="{yes|no}"

Use this parameter to specify whether to reconnect to an event service for which a connection error has occurred.

Change this parameter to enable reconnection each time the system outputs a JP1 event.

Use the default value (no) if the system does not reference JP1 events (from 4100 to 4142) output from the scheduler service.

Specifiable values

yes
An attempt to reconnect to the event service is made the next time an event is output.
If reconnection to the event service is successful, the JP1 event is output. However, note that, because the event service is not reconnected, the JP1 event for the error that occurs is not output (the failed event is not registered as a JP1 event).
If you specify yes, this function tries to connect to the event service for each event output until reconnection to the event service is successful. Therefore, the job performance might be adversely affected compared to when no is specified. Specify yes if reconnection to the event service has greater priority than performance.
If you specify yes, the system outputs an error message (KAVS0863-E Interprocess communication failed.:maintenance-information-1, maintenance-information-2, mainetnance-information-3) each time an error occurs on the connection with an event service. If the connection to the event service is not restored quickly, a large number of log messages will be output.

no
JP1 events are not output after an event service connection error occurs.
The event service will be connected again when the JP1/AJS3 service is restarted.

Default value
no

Recommended value
yes

When the setting takes effect
Immediately

(11) "MONLOG"="{none|all}"

Use this parameter to specify whether to output messages related to establishing and terminating connections to the scheduler service from JP1/AJS3 - View to the scheduler log.

Change the parameter value if you want to output the connection status from JP1/AJS3 - View to the scheduler log.

Specifiable values

none
Messages related to connections' from JP1/AJS3 - View to the scheduler service are not output.

all
Messages related to establishing and terminating connections from JP1/AJS3 - View to the scheduler service (KAVS0534-I, KAVS0535-I, KAVS0536-I, and KAVS0537-I) are output.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(12) "REUSELOGON"={yes|no}"

Use this parameter to select the method that will be used to start the logon session process that is executed after a logon using the OS user account.

Specify yes when multiple simultaneous sessions are to be mapped to the same OS user and then run, and a lack of desktop heap area prevents the process from starting.

Reuse the logon resources for starting the following processes:

Specifiable values

yes
Logon information is saved and reused for the sessions to be mapped to the same OS user.
Specifying yes enables these sessions to share desktop heaps, and helps reduce the consumption of the desktop heap area.
If there are multiple simultaneous sessions to be mapped to the same OS user, and the processes cannot be started because desktop heap area is insufficient, specify yes. If you specify yes and change the OS user information, you must restart the ajsinetd process.

no
Logon information is not reused for the sessions to be mapped to the same OS user.

Default value
no

Recommended value
yes

When the setting takes effect
When the ajsinetd process starts.
For details about how to start and stop the ajsinetd processes individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(13) "LOGONSHMAX"=dword:number-of-logon-sessions-sharing-logon-resources

When reusing a logon, you need to specify the number of sessions that are allowed to share the logon information.

A new desktop heap is assigned if the number of sessions for the same OS user exceeds the value specified in this parameter.

You can specify this parameter only if you specify yes for the REUSELOGON environment setting parameter.

Specifiable values
A hexadecimal value from 1 to 80 (1 to 128 in decimal)

Default value
dword:00000032 (50 in decimal)

Recommended value
Default value

When the setting takes effect
When the ajsinetd process starts.
For details about how to start and stop ajsinetd processes individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Supplementary note
How to estimate the number of logon sessions that share the logon resources:
If the desktop heap area is running low, change the number of logon sessions that can share the logon resources to a value in the range indicated below.
For the size of the desktop heap to be assigned to non-interactive processes, see the OS documentation.
Number-of-logon-sessions-sharing-the-logon-resources < size-of-the-desktop-heap-to-be-assigned-to-a-non-interactive-processes (in kilobytes)/10 (in kilobytes)

(14) "MAXSESSION"=dword:maximum-number-of-simultaneous-sessions

Use this parameter to specify a maximum number of JP1/AJS3 - View connections.

If the maximum number of JP1/AJS3 - View connections will exceed 50, specify an appropriate value. In addition, if there are resource restrictions and you want to limit the number of JP1/AJS3 - View connections, specify a smaller value.

If connection is attempted from JP1/AJS3 - View when the number of times specified here has been reached, the connection will fail.

Specifiable values
A hexadecimal value from 0 to 80 (0 to 128 in decimal)

Default value
dword:00000032 (50 in decimal)

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(15) "AJSINETDLOGSIZE"=dword:size-of-ajsinetd-internal-log

Use this parameter to specify the size of the ajsinetd internal log.

Specifiable values
00000000 or a value in kilobytes from 00000004 to 001E8480 in hexadecimal (in decimal 0 or a value from 4 to 2,000,000)
If you specify dword:00000000, the system does not create a log file.
If you omit this parameter, dword:00000080 is assumed. If the specified value is invalid, dword:00000000 is assumed.

Default value
dword:00000080 (128 in decimal)

Recommended value
Default value

When the setting takes effect
When the ajsinetd process starts.
For details about how to start or stop ajsinetd processes individually, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1 and jajs_hstd_stop in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(16) "MONSYSLOG"="{none|all}"

Use this parameter to specify whether to output messages related to starting and terminating the ajsinetd process, the ajsinetd process for acceptance processing, and the monitoring server to the following logs:

Change the parameter value if you do not need to check the connection status in the Windows event log or syslog log from JP1/AJS3 - View. If you change this parameter, you will not be able to check the connection status from JP1/AJS3 - View when an error occurs.

Specifiable values

none
The messages related to the ajsinetd process and the monitor server, are not output.

all
The ajsinetd process startup message (KAVS0530-I) and termination message (KAVS0531-I), ajsinetd process for acceptance processing startup message (KAVS0532-I) and termination message (KAVS0533-I), and the monitor server startup message (KAVS0534-I) and termination message (KAVS0535-I) are output.

Default value
none
During a new installation and setup of JP1/AJS3, all is set.

Recommended value
all

When the setting takes effect
Immediately (at the next login to JP1/AJS3 - View)

(17) "AUTHLOG"="{none|all}"

Use this parameter to specify whether to output the messages related to user authentication to the scheduler log.

Specifiable values

none
Messages related to user authentication are not output.

all
Messages related to user authentication are output.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
Immediately (the next time a user authentication request is received)

(18) "AUTHSYSLOG"="{none|all}"

Use this parameter to specify whether to output messages related to user authentication to the following file or logs:

Specifiable values

none
Messages related to user authentication are not output.

all
Messages related to user authentication are output.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
Immediately (the next time a user authentication request is received)

(19) "HIDEOTHERLHOST"="{yes|no}"

Use this parameter to specify the range of the scheduler services to be displayed when you log on to a host from JP1/ASJ3 - View in an environment in which JP1/AJS3 services has been established for logical hosts.

Specifiable values

yes
Only the scheduler service corresponding to the specified host name is displayed when you log on to a host from JP1/AJS3 - View.

no
All defined scheduler services established on the machine are displayed if you log on as a JP1 user mapped to the OS user with superuser permission or the Administrators permission.
If you log on as any other type of user, all defined scheduler services established on hosts that belong to the same user authentication block as the logged-on host are displayed. If any scheduler service other than the one for the logged-on logical host is failed over and does not exist on the logged-on physical host, do not access that scheduler service.
Also, if the ajsinetd process is not running on the connection-destination host, you cannot access the scheduler service on that host.
Specify this value if you want to access the scheduler services on all logical hosts in the JP1/AJS3 - Manager to which you log on from JP1/AJS3 - View.

Default value
yes

Recommended value
Default value

When the setting takes effect
Immediately (at the next login to JP1/AJS3 - View)

(20) "AUTORESTARTCOUNT"=dword:scheduler-service-restart-count

Use this parameter to specify the number of times that a scheduler service process will be automatically restarted if it has terminated abnormally.

Specify 0 to immediately stop job execution in JP1/AJS3 when a scheduler service has terminated abnormally. In addition, if you monitor the scheduler service status by executing the jajs_spmd_status command or a process, specify 0 for this parameter and yes for the MASTERDABEND environment setting parameter.

Note that this parameter is valid only in compatible ISAM configuration.

Specifiable values
A hexadecimal value from 0 to 3 (0 to 3 in decimal)
If you specify dword:00000000, the scheduler service is not restarted.
If you specify dword:00000001, the scheduler service is restarted only once.

Default value
dword:00000003 (3 in decimal)

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(21) "RESTARTCLRTIME"=dword:time-to-clear-the-restart-count

When a process in a scheduler service terminates abnormally and is then restarted, the system assumes normal operation and clears the restart count if the specified time elapses before it stops again. Specify the length of time that the system must operate before the operation is regarded as normal.

When it takes more than three minutes for the scheduler service to start, increase the value if you do not want to restart the system after an abnormal termination.

Note that this parameter is valid only in compatible ISAM configuration.

Specifiable values
A hexadecimal value (in seconds) from B4 to 15180 (180 to 86,400 in decimal)

Default value
dword:000000B4 (180 in decimal)

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(22) "MASTERDABEND"="{yes|no}"

Use this parameter to specify whether to stop all scheduler services and terminate the ajsmasterd process abnormally if a scheduler service terminates abnormally.

Note that this parameter is valid only in compatible ISAM configuration. In a standard configuration, this parameter is always no.

Specifiable values

yes
All scheduler services terminate, and the ajsmasterd process terminates abnormally.
Specify this value to monitor the operating status of JP1/AJS3 by executing the jajs_spmd_status command.
When you do this, you cannot restart the scheduler service by executing the jajs_spmd command with the -n jajs_schd option specified. To start the scheduler service, restart the JP1/AJS3 service.

no
Not all the scheduler services terminate.
If you specify this value, you can restart the scheduler service by executing the jajs_spmd command with the -n jajs_schd option specified.

Default value
no

Recommended value
Default value

When the setting takes effect
After JP1/AJS3 is restarted

Cautionary note

- In Windows:
On a logical host in a cluster configuration, if a scheduler service on the logical host terminates abnormally, the system performs the following operation:
  • If yes is specified, the JP1/AJS3 service on the logical host on which the scheduler service terminated, terminates abnormally.
  • If no is specified, the JP1/AJS3 service on the logical host on which the scheduler service terminated abnormally, does not terminate.

- In UNIX:
If a scheduler service in the JP1/AJS3 service that was started by executing the jajs_spmd command with the -HA option specified terminates abnormally, the system performs the following operation:
  • If yes is specified, the JP1/AJS3 service started by the jajs_spmd command with the -HA option specified terminates.
  • If no is specified, the JP1/AJS3 service started by executing the jajs_spmd command with the -HA option specified does not terminate.
Note that even if yes is specified, the system restarts the scheduler service only the number of times specified for the AUTORESTARTCOUNT environment setting parameter. If the scheduler service terminates abnormally after being restarted the specified number of times, all scheduler services terminate.

(23) "AJSLOGOUTPUTDEST"="{schedule|host}"

Use this parameter to specify whether to output the scheduler log by scheduler service or by host. Specify this parameter for each scheduler service.

Specifiable values

schedule
The scheduler log for a scheduler service is output to the files specified in the AJSLOGFILE1 and AJSLOGFILE2 environment setting parameters.
For each scheduler service, you can estimate and check the log size, and switch and back up logs.

host
The scheduler log for a host is output to the file specified in the HOSTLOGFILE1 and HOSTLOGFILE2 environment setting parameters.
Although it is necessary to estimate and check the file size, and to switch and back up logs for each host, the system can log the commands that are executed while the scheduler service is not running.

Default value
schedule

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(24) "LOGSIZE"=dword:size-of-the-scheduler-log-file (when outputting the scheduler log for a scheduler service)

Specify the size of the file to which the system outputs the scheduler log file for a scheduler service.

Because this log is used to check the execution status of a job or jobnet, specify a size that is sufficient for storing the log data for at least one day.

For details about how to estimate the size of a scheduler log file, see 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Specifiable values
  • In Windows:
    0 or a hexadecimal value (in kilobytes) from 4 to 1E8480 (0 or a value from 4 to 2,000,000 in decimal)
  • In UNIX:
    A hexadecimal value (in kilobytes) from 0 to 1E8480 (0 to 2,000,000 in decimal)
If you specify dword:00000000, the system does not create a log file.

Default value
  • In Windows:
    dword:00001400 (5,120 in decimal)
  • In UNIX:
    dword:00000000 (0 in decimal)
During a new installation and setup of JP1/AJS3, dword:00002800 (10,240 in decimal) is set.

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(25) "AJSLOGFILE1"="name-of-scheduler-log-file-1"

Use this parameter to specify the name of a log file. Specify a full path name.

Specify a file name different from the name of scheduler log file 2.

When the amount of information written to this file becomes equal to or greater than the specified size, the system writes subsequent information to log file 2.

Specify a unique file name that is not used on any other logical host.

In UNIX, when you use the scheduler log file, you cannot omit this parameter.

Specifiable values
A character string of no more than 255 bytes

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\schedule-service-name\ajs-log1.log (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log1.log
  • In UNIX:
    /var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log1.log

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(26) "AJSLOGFILE2"="name-of-scheduler-log-file-2"

Use this parameter to specify the name of a log file. Specify a full path name.

Specify a unique file name that is not used on any other logical host.

In UNIX, when you use the scheduler log file, you cannot omit this parameter.

Specifiable values
A character string of no more than 255 bytes

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log2.log (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log
  • In UNIX:
    /var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log2.log

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(27) "LOGDLOG"="{none|all}"

Use this parameter to specify whether to output the messages related to starting and terminating the scheduler log output process (ajslogd.exe for Windows and ajslogd for UNIX) to the scheduler log.

Specifiable values

none
The messages related to starting and terminating the scheduler log output process is not output.

all
The messages related to starting (KAVS0220-I) and terminating (KAVS0221-I) the scheduler log output process, are output.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(28) "LOGDSYSLOG"="{none|all}"

Specifiable values

none
The messages related to starting and terminating the scheduler log output process is not output.

all
The messages related to starting (KAVS0220-I) and terminating (KAVS0221-I) the scheduler log output process, are output.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(29) "AJSLOGOUTPUTYEAR"="{yes|no}"

Use this parameter to specify whether to output the year as part of the scheduler log date.

Change the parameter value if you use the year to manage scheduler log information.

Specifiable values

yes
The year is output. The system outputs the year, month, and day in the date section.

no
The year is not output. The system outputs only the month and day in the date section.

Default value
no

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(30) "AJSLOGOUTPUTEXTEND"="{yes|no}"

Use this parameter to specify the output format when the system outputs the execution log or operation log of units to the scheduler log.

Change the parameter value if you want to output the operation user type, requester information, and detailed options for command operation to the scheduler log.

If you specify yes for this parameter, the system outputs the detailed information to the scheduler log when you execute or manipulate a unit. By using this log, you can verify the validity of an operation. For details about this function and information that can be added, see C.1 Functions for verifying the legitimacy of JP1/AJS3 operations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The conditions governing when a log is output and the information to be added when a log is output vary according to the type of log. For details, see C.1 Log entries output by the scheduler services in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

yes
In addition to the information that is output when no is selected, detailed information, including operation user type, is also output.
The following information is added to the message:
  • Operation user type
  • Requester host IP address
  • Requester identification information
  • Options for command operations
  • Unit name

no
No additional detailed information, such as operation user information, is output.

Default value
no

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(31) "AUTOSTART"="{yes|no}"

Use this parameter to specify whether to automatically start a scheduler service when JP1/AJS3 - Manager is started.

Specifiable values

yes
A scheduler service is automatically started when JP1/AJS3 - Manager starts.

no
A scheduler service is started when the jajs_spmd command is executed.
Specify this value for a scheduler service that is not necessary during normal operation, such as a scheduler service is used only for testing.
If you specify no, the ajsmasterd process starts.

Default value
yes

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
After JP1/AJS3 is restarted

(32) "SESSIONTIMEOUT"=dword:connection-timeout-period

Specify how many minutes it is necessary to wait after the last communication for disconnection from JP1/AJS3 - View.

If the system is unable to communicate with JP1/AJS3 - View for the specified period of time since the last communication, the system assumes that JP1/AJS3 - View has failed and disconnects from JP1/AJS3 - View.

Specifiable values
A hexadecimal value (in minutes) from 1 to 78 (1 to 120 in decimal)

Default value
dword:00000078 (120 in decimal)

Recommended value
Default value

When the setting takes effect
On connection to JP1/AJS3 - View after a scheduler service has started or terminated

(33) "AJSSERVICEID"=dword:scheduler-service-id-number

Use this parameter to specify a scheduler service ID number.

Specify an ID number that is unique among all the physical hosts of the local host and all the logical hosts.

Because the system uses this ID number internally to identify a scheduler service when, for example, a temporary file name or key for interprocess communication is used, do not change the ID number after it has been specified. If you change the ID number, you will need to cold-start the scheduler service.

Specifiable values
A hexadecimal value from 1 to 14 (1 to 20 in decimal)

Default value
None

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(34) "ISAMWRITEMODE"="{flush|noflush|sync}"

Use this parameter to specify whether to permit synchronous writing when an ISAM file is updated.

Select the writing method appropriate for performance, reliability, and method of operation when an ISAM file is used.

Specifiable values

flush
Data in the buffer in memory is written to a disk each time a write operation finishes.

noflush
Data is written to a disk in response to OS buffering. There is no synchronization with JP1/AJS3 processing.

sync
Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but degrades performance. Note that synchronous writing is performed only for the status management files of jobs and jobnets. The system uses flush mode to write data to files that store unit definition information.

Default value
flush

Recommended value
  • For a physical host:
    flush (flush)
  • For a cluster configuration:
    sync (synchronization)

When the setting takes effect
When the scheduler service starts or terminates

(35) "TABLENAMEPREFIX"="table-name-prefix"

Use this parameter to specify a character string that will be prefixed to the name of a table that is stored in the scheduler service schema.

This environment setting parameter is set automatically during installation and setup. You do not need to change the value of this parameter.

Specifiable values
An alphanumeric character string of no more than 4 bytes
This value is not case sensitive, and all characters are treated as upper-case characters.

Default value
AJS

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates
If you change this parameter, you must re-create the scheduler database.

(36) "TABLENAMEPOSTFIX"="table-ID"

Use this parameter to specify a character string that will be suffixed to the name of a table that is stored in the scheduler service schema.

If you omit this parameter, you cannot add this character string later.

If you create multiple scheduler services in a single schema by using an RDB, specify a character string in this parameter that is different from the table name.

Specifiable values
An alphanumeric character string of no more than 4 bytes
This value is not case sensitive, and all the characters are treated as upper-case characters.

Default value
None

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates
If you change this parameter, you must re-create the scheduler database.

(37) "RDBAUTHID"="RDB-permission-identifier"

Use this parameter to specify a permission identifier to be used for setting up and operating the database.

Usually, you do not need to change this value.

Specifiable values
A value of no more than 8 bytes must be specified if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value
None

Recommended value
A value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(38) "RDBUSER"="RDB-access-user-name"

Use this value to define the name of the user who accesses the database.

Usually, you do not need to change this value.

Specifiable values
A value of no more than 8 bytes must be specified when you use an embedded database (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value
None

Recommended value
A value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(39) "RDBPASSWORD"="RDB-user-password"

Use this parameter to define a password for enabling access to the database.

Usually, you do not need to change this value.

Specifiable values
A value of no more than 30 bytes must be specified if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).
The passwords for an embedded database are not case sensitive. To distinguish between upper-case and lower-case characters, enclose the password character string in exclamation marks (!).
 
Example: "RDBPASSWORD"="!password!"

Default value
Not specified

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(40) "RDBCHECKINTERVAL"=dword:whether-to-use-the-RDB-server-connection-check-function

Use this parameter when you use the function for automatically stopping the scheduler service when the scheduler service is no longer able to continue processing for a reason such as a database server stoppage. You use this function to check the connection of the scheduler service to the database server and to automatically stop the scheduler service if it has been disconnected from the database server.

Usually, you do not need to change this parameter.

Specifiable values
A hexadecimal value from 1 to 15180 (1 to 86,400 in decimal)
If you specify a value outside this range, the function is disabled. If the function is disabled, the connection to the database server is not checked, and the scheduler service does not terminate automatically.

Default value
dword:00000000 (0 in decimal)
During a new installation and setup of JP1/AJS3, dword:0000012C (300 in decimal) is set.

Recommended value
dword:0000012C (300 in decimal)

When the setting takes effect
When the scheduler service starts

(41) "RDBHOST"="RDB-connection-destination-host-name"

Use this parameter to specify the name of the host on which the database is set up.

Usually, you do not need to change this value.

Specifiable values
A character string of no more than 511 bytes

Default value
None

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(42) "RDBPORT"=dword:RDB-connection-port-number

Use this parameter to specify the port number for the RDB connection.

Usually, you do not need to change this value.

Specifiable values
A hexadecimal value from 1389 to FFFF (5,001 to 65,535 in decimal) if an embedded database is used (when EmbedDB is specified for the AJSDBTYPE environment setting parameter).

Default value
None

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(43) "RDBIPC"="{MEMORY|DEFAULT}"

Use this parameter to specify the method for connecting to the RDB server.

Usually, you do not need to change this value.

Specifiable values

MEMORY
Interprocess memory communication is used for communication with the RDB server.

DEFAULT
TCP/IP communication is used for communication with the RDB server.

Default value
DEFAULT

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(44) "RDBSENDMEMSIZE"=dword:size-of-data-send-memory-for-RDB-interprocess-memory-communication

Use this parameter to specify the amount of memory used to store send data in interprocess memory communication with the RDB server.

This parameter is valid only if interprocess memory communication is specified as the method of communication with the RDB server (when MEMORY is specified for the RDBIPC environment setting parameter).

Usually, you do not need to change this value.

Specifiable values
Any hexadecimal value (in kilobytes).
However, to use RDB interprocess memory communication with JP1/AJS3, specify a value of dword:00000008 (8 in decimal) or greater.
If you specify 0, the default RDB value is used.

Default value
Default RDB value

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(45) "RDBRECVMEMSIZE"=dword:size-of-data-receive-memory-for-RDB-interprocess-memory-communication

Use this parameter to specify the amount of memory used to store receive data in interprocess memory communication with RDB.

This parameter is valid only if you specify interprocess memory communication as the method of communication with the RDB server (when MEMORY is specified for the RDBIPC environment setting parameter).

Usually, you do not need to change this value.

Specifiable values
Any hexadecimal value (in kilobytes).
However, to use the RDB interprocess memory communication with JP1/AJS3, specify a value of dword:00000040 (64 in decimal) or greater.
If you specify 0, the default RDB value is used.

Default value
Default RDB value

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates

(46) "RDBCONNECTWAITTIME"=dword:maximum-wait-time-for-connection-to-RDB

Use this parameter to specify the maximum wait time to wait for connection to the RDB server.

Usually, you do not need to change this value.

Specifiable values
A hexadecimal value (in minutes) from 0 to 3C (0 to 60 in decimal)
If you specify 0, the RDB connection wait function is disabled.

Default value
dword:00000001 (1 in decimal)

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts

(47) "AJSCHARCODE"="{C}"

Use this parameter to specify the character set for job definition information recorded in the scheduler service database.

Specifiable values

C
ASCII character set

Default value
None

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(48) "AJSTMPDIR"="name-of-directory-for-temporary-files"

Use this parameter to specify the name of a directory in which temporary JP1/AJS3 files are created. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be executing and referencing jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be referencing jobnets, set the operation permission (rx for UNIX).

If an error occurs during operations, a work file might remain under the specified directory.

For this reason, when no JP1/AJS3 services are running (for example, when the system is started), delete files and maintain the directory regularly. Note, however, if an embedded database is used, do not delete any files with names beginning with pd (such as pderr1.trc and pderr2.trc).

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or space ( ).

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\tmp\schedule
  • In UNIX:
    /var/opt/jp1ajs2/tmp/schedule
    When you add a scheduler service, create this directory. Make sure that this directory is neither a directory used by another scheduler service set on the local hosts (the physical host and all the logical hosts) nor a subdirectory of that directory.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(49) "JOBINFDIR"="job-error-information-directory-name"

Use this parameter to specify the name of the directory to be used to store the standard error output when a job is executed and if the standard error output file is not specified in the job definition. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be executing and referencing jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be referencing jobnets, set the operation permission (rx for UNIX).

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or space ( ).

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\jobinf (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\jobinf
  • In UNIX:
    /var/opt/jp1ajs2/jobinf
    When you add a scheduler service, create this directory. Make sure that this directory is neither a directory used by another scheduler service set on the local hosts (the physical host and all the logical hosts) nor a subdirectory of that directory.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(50) "AJSBKUROOT"="backup-information-directory-name"

Use this parameter to specify the name of the directory to be used to back up units. Specify a full path name.

Determine the name based on the operating environment after estimating the amount of required disk space.

For those users who will be backing up jobnets, set the update permission (rwx for UNIX) for this directory. For those users who will only be restoring jobnets, set the operation permission (rx for UNIX).

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or space ( ).

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\backup\schedule (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\backup\schedule
  • In UNIX:
    /var/opt/jp1ajs2/backup/schedule
    When you add a scheduler service, create this directory.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(51) "HNTRLOGLEVEL"="{none|error|warn|info}"

Use this parameter to specify the level of messages that the scheduler service outputs to the integrated trace log.

Specifiable values

none
No messages are output.

error
Error messages are output.

warn
Error and warning messages are output.

info
Error, warning, and information messages are output.

Default value
none
During a new installation and setup of JP1/AJS3, error is set.

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(52) "SYSLOGCODE"="{C}"

Use this parameter to specify the language type of the messages that are output by the scheduler service to the syslog file.

Specifiable values

C
The messages are output encoded with the English ASCII character set.

Default value
C

Recommended value
Default value

When the setting takes effect
After JP1/AJS3 is restarted

(53) "AJSSYSLOG"="{none|all}"

Use this parameter to specify whether to output messages related to starting and terminating the scheduler service to the Windows event log or syslog file.

Specifiable values

none
The messages related to starting and terminating the scheduler service is not output.

all
The messages related to starting (KAVS0200-I) and terminating (KAVS0201-I) the scheduler service, are output.

Default value
none

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(54) "NETSYSLOG"="{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:connector}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobnets to the Windows event log or syslog file.

Specifiable values

none
The messages related to starting and ending jobnet are not output.

abend
The abnormal end message for jobnets (KAVS0262-E) is output.

warning
The end with warning message for jobnets (KAVS0268-W) is output.

hold
The on-hold notification message for jobnets (KAVS0270-I) is output.

startdelay
The delayed-start notification message for jobnets (KAVS0275-I) is output.

enddelay
The delayed-end notification message for jobnets (KAVS0276-I) is output.

condition
The notification messages for jobnets reporting the start of start-condition monitoring (KAVS0240-I) and the end of start-condition monitoring (KAVS0241-I) are output.

execdeffer
The deferred-execution message for jobnets (KAVS0279-E) is output.

connector
Error messages related to the connection between the jobnet connector and the connection destination jobnet (KAVS0243-E, KAVS0244-E, KAVS4700-E to KAVS4708-E, KAVS4711-E to KAVS4716-E, and KAVS4730-E to KAVS4733-E) are output.

all
The following messages related to starting and ending jobnets are output:
  • Start (KAVS0260-I)
  • Normal end (KAVS0261-I)
  • Abnormal end (KAVS0262-E)
  • End with warning (KAVS0268-W)
  • On-hold notification (KAVS0270-I)
  • Delayed start (KAVS0275-I)
  • Delayed end (KAVS0276-I)
  • Start/end of start-condition monitoring (KAVS0240-I and KAVS0241-I)
  • Deferred execution (KAVS0279-E)
  • All registrations canceled (KAVS0267-I)
  • Jobnet connector connection error (KAVS0243-E, KAVS0244-E, KAVS4700-E to KAVS4708-E, KAVS4711-E to KAVS4716-E, and KAVS4730-E to KAVS4733-E)
The KAVS0260-I message (jobnet start) and the KAVS0261-I message (normal end) are output only when all is specified.

Default value
none

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(55) "JOBSYSLOG"="{none|{abend:warning:hold:enddelay}|all}"

Use this parameter to specify whether to output messages related to starting and ending the jobs in a jobnet to the Windows event log or syslog file.

Specifiable values

none
The messages related to starting and ending jobs are not output.

abend
The abnormal end message for jobs (KAVS0265-E) is output.

warning
The end with warning message for jobs (KAVS0269-W) is output.

hold
The on-hold notification message for jobs (KAVS0271-I) is output.

enddelay
The delayed-end message for jobs (KAVS0248-I) is output.

all
The following messages related to starting and ending jobs are output:
  • Start (KAVS0263-I)
  • Normal end (KAVS0264-I)
  • Abnormal end (KAVS0265-E)
  • Queuing cancellation (KAVS0266-I)
  • End with warning (KAVS0269-W)
  • On-hold notification (KAVS0271-I)
  • Delayed end (KAVS0248-I)
If you specify a value other than all, the start (KAVS0263-I), normal-end (KAVS0264-I), and queuing cancellation (KAVS0266-I) messages will not be output for jobs.

Default value
none

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(56) "AJSLOG"="{none|all}"

Use this parameter to specify whether to output messages related to starting and terminating the scheduler services to the scheduler log file.

Specifiable values

none
The messages related to starting and terminating the scheduler service, are not output.

all
The messages related to starting (KAVS0200-I) and terminating (KAVS0201-I) the scheduler service, are output.

Default value
all

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(57) "NETLOG"="{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobnets to the scheduler log file.

Specifiable values

none
The messages related to starting and ending jobnets are not output.

abend
The abnormal end message for jobnets (KAVS0262-E) is output.

warning
The end with warning message for jobnets (KAVS0268-W) is output.

hold
The on-hold notification message for jobnets (KAVS0270-I) is output.

startdelay
The delayed-start notification message for jobnets (KAVS0275-I) is output.

enddelay
The delayed-end notification message for jobnets (KAVS0276-I) is output.

condition
The notification messages for jobnets reporting the start of start-condition monitoring (KAVS0240-I) and the end of start-condition monitoring (KAVS0241-I) are output.

execdeffer
The deferred execution message for jobnets (KAVS0279-E) is output.

all
The following messages related to starting and ending jobnets are output:
  • Start (KAVS0260-I)
  • Normal end (KAVS0261-I)
  • Abnormal end (KAVS0262-E)
  • End with warning (KAVS0268-W)
  • On-hold notification (KAVS0270-I)
  • Delayed start (KAVS0275-I)
  • Delayed end (KAVS0276-I)
  • Start of start-condition monitoring notification (KAVS0240-I)
  • End of start-condition monitoring notification (KAVS0241-I)
  • Deferred execution (KAVS0279-E)
  • All registrations canceled (KAVS0267-I)
The KAVS0260-I message (jobnet start), the KAVS0261-I message (normal end), and the KAVS0267-I message (all registrations canceled) are output only when all is specified.

Default value
all

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

Cautionary note
Note that the default behavior of JP1/AJS3 and JP1/AJS2 version 06-71 and later is to output the start/end of start-condition monitoring notification, deferred execution, and all registration canceled messages for jobnets.

(58) "JOBLOG"="{none|{abend:warning:hold:enddelay}|all}"

Use this parameter to specify whether to output messages related to starting and ending jobs in a jobnet to the scheduler log file.

Specifiable values

none
The messages related to starting and ending jobs are not output.

abend
The abnormal end message for jobs (KAVS0265-E) is output.

warning
The end with warning message for jobs (KAVS0269-W) is output.

hold
The on-hold notification message for jobs (KAVS0271-I) is output.

enddelay
The delayed-end notification message for jobs (KAVS0248-I) is output.

all
The following messages related to starting and ending jobs are output:
  • Request for event job execution started (KAVS0242-I)
  • Start (KAVS0263-I)
  • Normal end (KAVS0264-I)
  • Abnormal end (KAVS0265-E)
  • Queuing cancellation (KAVS0266-I)
  • End with warning (KAVS0269-W)
  • On-hold notification (KAVS0271-I)
  • Submit started (KAVS0278-I)
  • Delayed end (KAVS0248-I)
If you specify a value other than all, the start (KAVS0242-I, KAVS0263-I, KAVS0278-I), normal-end (KAVS0264-I), and queuing cancellation (KAVS0266-I) messages will not be output for jobs.

Default value
all

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(59) "OPELOG"="{none|{alter:stop:entry:leave:plan:intrpt:rerun:kill:change:calendar:delete:restore:define:copy:chgst:suspend:import:start:rgimport:release}|all}"

Use this parameter to specify whether to output operation logs to the scheduler log file.

Specifiable values

none
Operation logs are not output.

alter
The execution log for the ajsalter command (log type: C001) is output.

stop
The execution log for the ajsstop command (log type: C002) is output.

entry
The operation log recording the registration of jobnets (log type: C101) is output.

leave
The operation log recording the cancellation of jobnet registration (log type: C102) is output.

plan
The operation log recording changes to jobnet plans (log type: C103) is output.

intrpt
The operation log recording the interruption of jobnets (log type: C104) is output.

rerun
The operation log recording the rerunning of jobnets (log type: C105) is output.

kill
The operation log recording killed jobs (log type: C201) is output.

change
The operation log recording changes to units (log type: C301) is output.

calendar
The operation log recording changes to the calendar information (log type: C401) is output.

delete
The operation log recording the deletion of units (log type: C302) is output.

restore
The operation log recording the restoration of units (log type: C303) is output.

define
The operation log recording the definition of units (log type: C304) is output.

copy
The operation log recording the copying and moving of units (log type: C305) is output.

chgst
The operation log recording changes to the job status (log type: C202) is output.

suspend
The operation log recording suspension or the cancellation of the suspended status (log type: C106) is output.

import
The operation log recording the import of units (log type: C306) is output.

start
The execution log for the ajsstart command (log type: C003) is output.

rgimport
The operation log recording the import of the registered execution-schedule information (log type: C107, C108) is output.

release
The execution log for the ajsrelease command (log type: C307) is output.

all
All operation logs are output.

Default value
all

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(60) "LOGINFOALL"="{yes|no}"

Use this parameter to specify the format of messages output to the scheduler log file, Windows event log, or syslog file.

Change the parameter value if you do not want to output messages that contain additional information such as the execution ID or the job number.

For details about the logs that can be output to the scheduler log file, see C.1 Log entries output by the scheduler services in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.

Specifiable values

yes
In addition to the message output when no is specified, messages are output in a format that includes detailed information such as the execution ID or the job number.
The following information is added to messages:
  • Execution ID is added to the log data related to starting and ending jobnets and jobs.
  • Job number is added to the log data related to starting and ending jobs.
  • Host name is added to log data related to the starting of jobs in the Windows event log or syslog. Host name is output to log data related to the ending of jobs, regardless of the setting.
  • Return value is added to the normal-end log data for jobs.

no
No additional detailed information, such as the execution ID or job number, is output.

Default value
no
During a new installation and setup of JP1/AJS3, yes is set.

Recommended value
yes

When the setting takes effect
When the scheduler service starts or terminates

(61) "REFLOG"="{none|{backup:export:name:print:schedule:show:rgexport:release}|all}"

Use this parameter to specify whether to output reference logs to the scheduler log file.

Specify this parameter when you want to keep logs that will be used by the reference commands, such as ajsprint.

Specifiable values

none
No reference logs are output.

backup
The reference log for backed-up units (log type: C504 and C511) is output.

export
The reference log for exported units (log type: C508) is output.

name
The reference log for output of unit names (log type: C507 and C512) is output.

print
The reference log for unit definitions (log type: C503 and C510) is output.

schedule
The reference log for output of jobnet schedule information (log type: C506) is output.

show
The reference log for output of the unit status (log type: C502 and C509) is output.

rgexport
The reference log for exporting the registered execution-schedule information (log type: C513 and C514) is output.

release
The execution log for the ajsrelease command (log type: C515) is output.

all
All reference logs are output:
  • Backed-up units (log type: C504 and C511)
  • Exported units (log type: C508)
  • Output of unit names (log type: C507 and C512)
  • Output of unit definitions (log type: C503 and C510)
  • Output of jobnet schedule information (log type: C506)
  • Output of the unit status (log type: C502 and C509)
  • Exported registered execution-schedule information (log type: C513 and C514)
  • ajsrelease command (log type: C515)

Default value
all

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

Cautionary note
The default log file size (LOGSIZE) in version 07-00 and later differs from that in version 06-71 and earlier because some commands for which logs were not output in version 06-71 or earlier have been changed so that operation logs can now be output in version 07-00 and later.

Supplementary note
Reference logs related to abnormal end will be output if you specify one or more of all, backup, export, name, print, schedule, show, rgexport, and release, and specify yes for the AJSLOGOUTPUTEXTEND environment setting parameter.

(62) "LOGHEADER"="{none|PID}"

Use this parameter to specify whether to output the log information with the process ID added.

Change the parameter value if you do not want to output log information with the process ID added.

Specifiable values

none
The process ID is not output as part of the log information (the specification in version 06-71 and earlier).

PID
The process ID is output as part of the log information.

Default value
none
During a new installation and setup of JP1/AJS3, PID is set.

Recommended value
PID

When the setting takes effect
When the scheduler service starts or terminates

(63) "INFOLOG"="{none|{START:REQUEST}|all}"

Use this parameter to specify whether to output information logs.

Change the parameter value if you do not want to perform any performance evaluations, such as evaluations of the command processing time and the maximum number of concurrently executable commands.

Specifiable values

none
The command execution start log (log type: I001) and the scheduler service request log (log type: I002) are not output.

START
The log recording the applicable command processing started (log type: I001) is output.

REQUEST
The log recording when processing requests from a command to the scheduler service started (log type: I002) is output.

all
The command execution start log (log type: I001) and scheduler service request log (log type: I002) are output.

Default value
none
During a new installation and setup of JP1/AJS3, all is set.

Recommended value
all

When the setting takes effect
When the scheduler service starts or terminates

(64) "ROOTJOBNETSCHEDULERANGE"=dword:{00000018|00000030}

Use this parameter to specify the valid range for the schedule of a root jobnet.

Change the parameter value if you want to set the valid range for the schedule of a root jobnet to 48 hours.

If you change the specified value, the execution schedules of the root jobnet before and after the change will be different, in which case you must review the cold-start and jobnet schedules.

Specifiable values

00000018
The valid range for the schedule of the root jobnet is set to 24 hours.

00000030
The valid range for the schedule of the root jobnet is set to 48 hours.
You can specify dword:00000030 only if you specify all for the VIEWSTATUSRANGE environment setting parameter as the range of the generation information to be used as the basis for acquiring the status displayed by JP1/AJS3 - View.

Default value
dword:00000018 (24 in decimal)

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(65) "VIEWSTATUSRANGE"="{today|all}"

Use this parameter to specify the range of the generation information to be used as the basis for acquiring the status to be displayed in JP1/AJS3 - View.

Change the parameter value if you want to determine the status to be displayed from the generation information for the current date between the base times.

Specifiable values

today
The status to be displayed is determined from the generation information for the current date between the base times.
You can specify today only if you specify 24 hours as the valid range for the schedule of the root jobnet (dword:00000018 is specified for the ROOTJOBNETSCHEDULERANGE environment setting parameter).
If you specify 48 hours (dword:00000030 is specified for the ROOTJOBNETSCHEDULERANGE environment setting parameter), you cannot specify today.

all
The status to be displayed is determined from the information for the generation or scheduled generation within the range of all days, including today.

Default value
all

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(66) "STARTMODE"="{cold|warm|hot}"

Use this parameter to specify the start mode of the scheduler service that starts when the JP1/AJS3 service is started.

When a scheduler service starts, the start mode determines whether the registration status existing when the scheduler service terminated previously, is preserved or canceled.

For details about the statuses of the jobnets and jobs in each start mode, see 7.2.1(3) Jobnet and job statuses for each start mode in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Specifiable values

cold
The registration status existing when the scheduler service was terminated previously, is canceled, and the scheduler service starts.

warm
The registration status existing when the scheduler service terminated previously, is preserved, and the scheduler service starts. However, the jobnet that was being executed the previous time the service terminates is treated as having terminated and is executed according to the schedule for the day on which the scheduler service is currently started.

hot
The registration status existing when the scheduler service terminated previously, is preserved, and the scheduler service starts.

Default value
warm

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(67) "OVERSCHEDULE"="{exec|skip|plan}"

When a scheduler service starts, if the scheduled execution start time of a jobnet, which is scheduled for execution that day has already passed, use this parameter to specify how to handle execution of the jobnet. If hot is specified for the STARTMODE environment setting parameter as the scheduler service start mode, all the jobnets are executed regardless of this parameter and the jobnet execution registration options.

If you start the scheduler service by executing the ajsstart command, the value of the OVERSCHEDULE environment setting parameter is not valid, and operation is determined by the ajsstart command. For details about the ajsstart command, see ajsstart in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Specifiable values

exec
The jobnets scheduled for execution that day are executed, except in the following cases:
  • The scheduled execution time of a jobnet for which you select the Execute from next time option in the Planned time passed when daemon starts column in the Register for Execution dialog box of JP1/AJS3 - View have already passed when you register the job for execution.
  • The scheduled execution time of a jobnet for which you specify the -o option in the ajsentry command has already passed when you register the job for execution.

skip
All jobnets scheduled for execution that day are executed except those jobs that are scheduled for execution before the scheduler service starts. These jobs are not executed because their status is skipped so not executed. In addition, jobnets are not executed in the following cases:
  • The scheduled execution time of a jobnet for which you select the Execute immediately option in the Planned time passed when daemon starts column in the Register for Execution dialog box of JP1/AJS3 - View has already passed when you register the job for execution.
  • The scheduled execution time of a jobnet for which you did not specify the -o option in the ajsentry command has already passed when you register the jobnet for execution.

plan
The jobnets scheduled for execution that day are not executed because their status will be skipped so not executed. Regardless of the option set when execution was registered, the jobnets scheduled for execution on the day that the scheduler service starts are not executed.

Default value
exec

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(68) "SUPPRESS"="{none|exec}"

Use this parameter to specify whether to suppress the execution of jobnets and the jobs in jobnets.

Specifiable values

none
The execution of jobs and jobnets is not suppressed.

exec
The execution of jobs and jobnets is suppressed.

Default value
none

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(69) "EXECDEFER"="{oneday|twoday|unlimit}"

Use this parameter to specify how long to wait before the status of a root jobnet registered for execution changes to skipped so not executed when the jobnet has not been executed and the scheduled start date and time have passed.

This parameter remains in effect regardless of the mode set at execution registration.

If you register a jobnet for immediate execution, the date and time that the jobnet is registered are regarded as the scheduled start date and time.

Specifiable values

oneday
The jobnet status changes to skipped so not executed one day after the scheduled date.

twoday
The jobnet status changes to skipped so not executed two days after the scheduled date.

unlimit
Although the scheduled date has passed, the jobnet status remains waiting for start time or on hold.

Default value
oneday

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(70) "JOBSTATUSPORT"="service-name-of-the-port-for-acquiring-job-status"

Use this parameter to specify the port number of the communication port to be used to acquire job status information.

To execute multiple scheduler services, you must specify a different service name for each scheduler service and set a unique port number in the services file.

Specifiable values
A service name defined in the services file

Default value
jp1ajs2report

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(71) "QUEUELESSMULTIREQ"=dword:maximum-number-of-queueless-job-requests

The number of concurrently requested queueless jobs equals the number of processes communicating with the queueless agent when a queueless job is executed. Use this parameter to specify the number of queueless job request processes (ajsreqd.exe for Windows and ajsreqd for UNIX) started for each scheduler service.

If distributing queueless jobs will affect job execution performance, specify this parameter only if you increase the number of processes that communicate with the queueless agent services.

Specifiable values
A hexadecimal value from 00000001 to 00000008 (1 to 8 in decimal)

Default value
dword:00000001 (1 in decimal)
In a queueless job system, distributing queueless jobs does not result in lower-execution performance, so you can use the default value.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(72) "UNITDEFINERELOAD"="{yes|no}"

If you change the definition of a job or jobnet after registering execution, use this parameter to specify whether to reload the changed definition just before execution so that the changes take effect immediately.

Change the value of the parameter if you do not want to immediately apply changes made to the already defined unit information.

Specifiable values

yes
The definition is reloaded immediately before a job or jobnet is executed.
If this value is set, the most recent changes to the definition will take effect for the generation that was being processed when the definition was changed.

no
The definition is not reloaded immediately before a job or jobnet is executed (This is the behavior in JP1/AJS2 06-51 and earlier versions).
If this value is set, the most recent changes to the definition will not take effect for the generation that was being processed when the definition was changed.

Default value
no
During a new installation and setup of JP1/AJS3, yes is set.

Recommended value
yes

When the setting takes effect
When the scheduler service starts

Cautionary note
JP1/AJS3 allows you to change the unit definition information that affects the execution of the unit, such as the file name, target host, and hold attribute, during registration for execution. However, some items in the changed unit information will not take effect for the generation that is being processed when you change the definition. For details, see 8.4 Changing the unit definition information during registration for execution in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

(73) "MAXSAVEGEN"=dword:maximum-number-of-saved-generations

Use this parameter to specify the maximum number of saved generations.

The value specified here is the maximum value that you can define for the number of logs to keep.

Change this value when you want to increase the number of logs to keep to 100 or more.

When you specify LEGACY for the SAVEGENTYPE environment setting parameter, the same number of execution results as the number of logs to keep is stored for each of the monitoring generations and execution generations.

When you specify TOTAL for the SAVEGENTYPE environment setting parameter, the same number of execution results as the number of logs to keep is stored, but in this case, the number of logs to keep is the sum of the number of monitoring generations and execution generations.

Specifiable values
A hexadecimal value from 63 to 3E7 (99 to 999 in decimal)

Default value
dword:63 (99 in decimal)

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

Cautionary notes
  • When you specify LEGACY for the SAVEGENTYPE environment setting parameter, if you increase the maximum number of specifiable generations, the number of records also increases. Before you increase the maximum number of saved generations, you must reduce the size of each root jobnet. For this purpose, divide the jobnets by applying a countermeasure such as reducing the number of records to be obtained by multiplying the number of logs to keep by the number of units.
  • If you increase the number of logs to keep to 100 or more, the versions of all instances of JP1/AJS3 - View must be version 07-00 or later. If you do this in JP1/AJS3 - View version 07-00 or later, and then update the detailed definitions in version of JP1/AJS3 - View earlier than 07-00, only the first two digits of the number of logs to keep appear. As a result, the number of logs to keep could be changed to an undesirable two-digit-number.
  • A system for which a smaller value is specified for the maximum number of saved generations might not be able to restore the jobnet definition information defined in a system in which the maximum number of saved generations is increased. For example, suppose you specify 200 as the number of logs to keep for a jobnet in a system in which the maximum number of saved generations is set to 200. If you output this definition information by using the ajsprint command and then try to define this output information by executing the ajsdefine command in a system in which the maximum number of saved generations is set to 150, an error occurs. The reason for the error is that the definition parameters contain a value larger than 150 (200 in this case).
  • An error dialog box asking you to change the maximum number of saved generations to a smaller value is displayed if the following sequence of operations is performed. First, you increase the maximum number of saved generations and define a jobnet with many saved generations, and then you reduce the maximum number of saved generations. Next, you open the Define Details window of the jobnet in JP1/AJS3 - View, in which the large value you originally specified for the number of logs to keep is displayed. Finally, you click the OK button to close the window.
  • If you register a jobnet defined with many saved generations, after increasing the maximum number of saved generations, and then you reduce the maximum number of saved generations, the system saves generations according to the registered maximum number of saved generations.
  • If you specify a decimal number exceeding 320 as the maximum number of saved generations, and then set the number of logs to keep to the maximum, the specified number of generations might not be saved, depending on how many future generations there will be. To increase the number of logs to keep, you must accurately estimate the number of future generations to be registered, and then use this estimate to determine the number of logs to keep. For details about the relationship between the numbers of logs to keep and the number of future generations, see B. List of Limits in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

(74) "AJSPRINTNETSCHPRF"="{yes|no}"

Specify whether to enable the scheduler rule, thereby freeing operation from the schedule of the upper-level jobnet, or to delete the scheduler rule, thereby making operation dependent on the schedule of the upper-level jobnet.

This option takes effect when you execute the ajsprint, ajsbackup, or ajsexport command, or choose Backup from JP1/AJS3 - View to back up a jobnet created by copying a root jobnet with a schedule rule to a nested jobnet.

Specifiable values

yes
The scheduler rule is enabled. Operation does not depend on the schedule of the upper-level jobnet.

no
The schedule rule is deleted. Operation depends on the schedule of the upper-level jobnet.

Default value
yes
During a new installation and setup of JP1/AJS3, no is set.

Recommended value
no

When the setting takes effect
When the scheduler service starts

(75) "SUBMITRETRYINTERVAL"=dword:retry-interval

If many jobs are executed simultaneously, although they may seem to have been submitted, they will be submitted in some cases they will not actually be queued (that is, their submission will be put on hold).

For such cases, you can use this parameter to specify a value in milliseconds for the period of time that needs to elapse before the submission will be retried.

However, be careful not to specify too small a value as the retry interval, because the system will attempt the job submission many times when there are jobs on hold, increasing the system load.

Specifiable values
A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)
If you omit this parameter or specify an invalid value, the system assumes the default value.

Default value
dword:00000BB8 (3,000 in decimal)

Recommended value
Set a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(76) "JOBEXECIPCBUFSIZE"=dword:buffer-size-for-job-execution-information-communication

Use this parameter to specify the buffer size to be used for communicating the job execution information of a scheduler service.

Specifiable values
A hexadecimal value (in bytes) from 00001000 to 00100000 (4,096 to 1,048,576 in decimal)
If you omit this parameter or specify an invalid value, the system assumes the default value.

Default value
dword:00000000 (0 in decimal)
If you do not specify a buffer size for communicating job execution information, the default value is assumed. In this case, the OS socket buffer is used as the default value.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(77) "BACKGROUNDLEAVE"="{yes|no}"

Use this parameter to determine the method to be used to delete generations when canceling registration or managing saved generations.

Change the parameter value if you want to create the generation management subprocess (ajsschbd) in the processing that deletes jobnet registration information so that generations will be deleted in the background.

If you change the value, you must restart the JP1/AJS3 service. You also need to perform migration by using a migration tool or by a cold-start.

For details about how to set the environment setting parameters, see 6.1.6 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values

yes
The generation management subprocess (ajsschbd) is used to delete the registration information of a jobnet.
If you specify yes, the generation management subprocess deletes registration information in the background, reducing the turnaround time for registration cancellation. Be careful when you specify yes, because doing so causes the system to use more resources for the generation management subprocess.

no
The schedule control process (ajsschd) is used to delete the registration information of a jobnet.
If you specify no, the schedule control process (ajsschd) deletes all the information of the generations to be deleted, increasing the turnaround time for registration cancellation in proportion to the number of generations or units to be deleted.

Default value
no
During a new installation and setup of JP1/AJS3, yes is set.

Recommended value
yes

When the setting takes effect
When the scheduler service starts

(78) "REQDAGTREQCONNECTTIMEOUT"=dword:timeout-period-for-communication

Use this parameter to specify how long to wait (the timeout period) for the requesting queueless-job request process to establish communication when connection processing is performed for a processing request (job execution, forced termination, or status confirmation) to a queueless agent service.

For a high-speed network between the manager host and an agent host, specify a smaller value when you want to quickly detect non-starting of an agent host. For a low-speed network and system, or for an environment in which the agent host is likely to be busy, specify a larger value. However, please note when specifying a larger value because a processing request will not be sent to another agent host until connection has been completed or the timeout period expires. If there are no special circumstances, we recommend that you use the default value of 15 seconds.

If communication is not established within the period specified by this parameter, the queueless job request process outputs the KAVS1930-W message and starts the reconnection processing. After the reconnection processing has started, processing requests to other agents that can communicate normally are executed as usual. However, processing requests to other relevant agents accumulate on the manager host as requests to a failed agent, and the reconnection processing is attempted one request at a time in the order they were executed. The timeout period for the reconnection processing differs according to the OS, and the reconnection processing will stop when the maximum communication-recovery-processing timeout period specified in the REQDAGTRECONNECTTIMEOUT environment settings parameter expires. Two reconnection attempts are performed at 60 second intervals, but if recovery is not possible, one of the following error messages is output:

If the reconnection is successful, the KAVS1929-I message is output, the accumulated requests are resent in order, and the system recovers from a failure status.

Specifiable values
A hexadecimal value (in seconds) from 00000000 to 00000258 (0 to 600 in decimal)
If you specify dword:00000000, the operation is controlled by the OS timeout period.

Default value
dword:0000000F (15 in decimal)

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(79) "REQDAGTRECONNECTTIMEOUT"=dword:timeout-period-for-communication

Specify how long to wait (the timeout period) for the requesting queueless-job request process to establish communication when reconnection processing is performed in either of the following cases:

- When a communication failure occurs for a processing request (job execution, forced termination, of status confirmation) to a queueless agent (the KAVS1930-W message is output)

- When disconnection of the communication line between the manager host and agent host was detected during execution of a job on a queueless agent (the KAVS1922-W message is output) and the system attempts to re-establish communication

This reconnection processing is performed in parallel with a processing request to another agent host.

Therefore, requests to other agent hosts able to perform communication normally do not have until connection is completed or until the timeout period expires.

Specifiable values
A hexadecimal value (in seconds) from 00000000 to 00000258 (0 to 600 in decimal)
If you specify dword:00000000, operation is controlled by the OS timeout period. For details about reconnection processing, see the explanation for the REQDAGTREQCONNECTTIMEOUT environment setting parameter that specifies the timeout period for connection processing.

Default value
dword:0000005A (90 in decimal)

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(80) "COMMANDEVENT"="{yes|no}"

Use this parameter to specify whether to issue a JP1 event when a command is executed or an operation is performed in JP1/AJS3 - View.

If you set in the OPELOG, REFLOG, and INFOLOG environment setting parameters that the command operation logs are to be output to the scheduler log, the same information is issued as a JP1 event. However, for the log reporting processing start requests to a scheduler service (log type: I002), no JP1 event is issued.

Specifiable values

yes
A JP1 event is issued when a command is executed or an operation is performed in JP1/AJS3 - View.

no
A JP1 event is not issued when a command is executed or an operation is performed in JP1/AJS3 - View.

Default value
no

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates

(81) "NONRELOADHOLDING"="{yes|no}"

Use this parameter if a unit definition on hold is not to be reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used. If you reload the unit definition on hold and change the specification for holding the unit definition from yes to no, a unit on hold is executed immediately.

Specifiable values

yes
A unit definition on hold is not reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used.

no
A unit definition on hold is reloaded when the function for immediately applying jobnet definition changes (UNITDEFINERELOAD) is used.

Default value
no
During a new installation and setup of JP1/AJS3, yes is set.

Recommended value
yes

When the setting takes effect
When the scheduler service starts

Cautionary note
If you specify no for this parameter, and change the hold specification for the unit definition from yes to no, the unit on hold is executed when:
  • Execution of a unit in the same scheduler service starts or ends.
  • One of the following operations is executed for a unit in the same scheduler service: rerun, hold, release hold, suspend, release suspension, or change schedule.
  • The scheduler service is restarted.
  • The ajsstop command is executed with the -r option specified.
Also note that if many units are on hold (200 units is the recommended maximum, although this limit might vary depending on the environment), more unit definitions must be reloaded than when yes is specified, resulting in increased I/O processing.
Specify no only if an operation procedure that releases a unit on hold by specifying no for the hold specification of the unit definition has been set up and modifying the operation procedure would be difficult.

(82) "RJCUSE"="{yes|no}"

Use this parameter to specify whether to control the execution order of root jobnets that have been distributed among different scheduler services by using a jobnet connector.

Specifiable values

yes
Specify this value to control the execution order of root jobnets distributed among different scheduler services.

no
Specify this value if you do not want to control the execution order of root jobnets distributed among different scheduler services.

Default value
no
During a new installation and setup of JP1/AJS3, yes is set.

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
After JP1/AJS3 service is restarted

(83) "JOBDELAYWARNMSG"="{yes|no}"

Use this parameter to specify whether to output a warning message to the integrated trace log when the scheduler service starts. The message that is output is generated if a job for which termination delay is monitored according to the required time for execution is executed on the job execution control agent when a scheduler service has been stopped.

Specifiable values

yes
The KAVS0249-W message is output.
Note, however, that the scheduler service is started in disaster recovery mode, the termination status will be unknown regardless of the job status on the job execution control agent. In this case, the message will not be output.

no
The message is not output.

Default value
no

Recommended value
Set the value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts

(84) "FGRECONLMT"=dword:number-of-reconnection-attempts

Use this parameter to specify the number of reconnection attempts if the flow control process cannot communicate with the scheduler service inter-communication control process.

Specifiable values
A hexadecimal value from 0 to 64 (0 to 100 in decimal)

Default value
dword:00000003 (3 in decimal)

Recommended value
Default value

When the setting takes effect
When the scheduler service starts

(85) "SAVEGENTYPE"="{TOTAL|LEGACY}"

Use this parameter to specify the method used to manage the number of logs to keep of the execution results for a jobnet for which start conditions are defined.

For details about how to manage the number of logs to keep, see 4.2.3 Jobnet generation management in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values

TOTAL
A new method used from version 9. The number of logs to keep can be specified as the sum of the number of monitoring generations and execution generations.

LEGACY
The legacy management method used through version 8. The number of execution results specified as the number of logs to keep is saved separately for the monitoring generation and the execution generation. Therefore, the number of execution results to be saved is the square of the number specified as the maximum number of saved generations.

Default value
LEGACY
During a new installation and setup of JP1/AJS3, TOTAL is set.

Recommended value
TOTAL

When the setting takes effect
When the scheduler service starts

(86) "AJSDBTYPE"="{ISAM|EmbedDB}"

Use this parameter to specify the type of database to be used.

Usually, you do not need to change this value.

Specifiable values

ISAM
The ISAM database is provided as a standard component of JP1/AJS3 - Manager.

EmbedDB
The embedded database can be used as the standard JP1/AJS3 - Manager database.

Default value
ISAM
During a new installation and setup of JP1/AJS3, EmbedDB is set.

Recommended value
The value set in JP1/AJS3 - Manager

When the setting takes effect
When the scheduler service starts or terminates
If you change this parameter, you must re-create the scheduler database.

(87) "AJSDBDIRECTORY"="database-directory-name"

Use this parameter to specify the name of the directory used to store the JP1/AJS3 unit information. Specify a full path name.

Change the parameter value if there is no more available disk space in the default directory or when you need to change the directory to a directory under a shared directory in a cluster configuration.

If you use multiple scheduler services, specify a directory that does not conflict with the directories of other scheduler services.

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or a space ( ).

Default value
During a new installation and setup of JP1/AJS3, the following path is set:
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\database\schedule\AJSROOT1 (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\database\schedule\AJSROOT1
  • In UNIX:
    /var/opt/jp1ajs2/database/schedule/AJSROOT1

Recommended value
Set the default value or a value appropriate for the operating environment.

When the setting takes effect
When the scheduler service starts or terminates
If you change this parameter, you must re-create the scheduler database.

Cautionary notes
  • For those users who define, execute, and reference jobnets, define the following permissions for the directory specified here and the files under the directory:
    - In Windows:
    Read and write permissions
    - In UNIX:
    Update permission (rwx)
  • The directory specified here will contain the files needed to perform exclusive editing of the unit, ISAM data files, and key files (if you specify ISAM as the JP1/AJS3 database). Do not delete these files.
  • In UNIX, create this directory when you add a scheduler service.
  • In UNIX, do not create a symbolic link for a file created in the directory specified in this parameter. If you do so, reorganization will break the link because the file is re-created. Use the directory specified in this parameter if you want to create a symbolic link.
    Do not use an NFS or network drive for the directory you specify in this parameter.

(88) "AJSSYSDIR"="name-of-system-directory"

Use this parameter to specify the name of the directory in which you create the JP1/AJS3 system files. Specify a full path name.

Determine a name appropriate for the operating environment after estimating the amount of the required disk space.

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or a space ( ).

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\sys\schedule\scheduler-service-name (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\sys\schedule\scheduler-service-name
  • In UNIX:
    /var/opt/jp1ajs2/sys/schedule/scheduler-service-name
If you have added a scheduler service, change the default value according to the operating environment.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(89) "AJSLOGDIR"="name-of-direcotry-for-log-files"

Use this parameter to specify the name of the directory in which JP1/AJS3 log files are created. Specify a full path name.

Determine a name appropriate for the operating environment after estimating the amount of the required disk space.

Specifiable values
  • In Windows:
    A character string of no more than 180 bytes
  • In UNIX:
    A character string of no more than 191 bytes
Do not use a semicolon (;) or a space ( ).

Default value
  • In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name (The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.)
  • In Windows Server 2003:
    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name
  • In UNIX:
    /var/opt/jp1ajs2/log/schedule/scheduler-service-name
If you have added a scheduler service, change the default value according to the operating environment.

Recommended value
Default value

When the setting takes effect
When the scheduler service starts or terminates

(90) "GWMAXCONNECTION"=dword:maximum-concurrent-connections

Use this parameter to specify the maximum number of concurrent connections used for communication by the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd for UNIX).

Specify a value equal to the number of JP1/AJS3 - Manager hosts in the system (including both physical and logical hosts). If you specify a value smaller than the actual value, communication with the scheduler service inter-communication control process might fail.

Specifiable values
A hexadecimal value from A to 400 (10 to 1,024 in decimal)

Default value
dword:A (10 in decimal)

Recommended value
The default value or the number of JP1/AJS3 - Manager hosts on which the scheduler service inter-communication control process has been set up.

When the setting takes effect
When the JP1/AJS3 service starts

(91) "GWPROCESSHA"="{yes|no}"

Specify whether to terminate the process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) that manages the scheduler service inter-communication control process if the scheduler service inter-communication control process (ajsgwd.exe for Windows and ajsgwd in UNIX) terminates abnormally.

Specifiable values

yes
The process that manages the scheduler service inter-communication control process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) is terminated.
In UNIX, you start the JP1/AJS3 service by executing the jajs_spmd command with the -HA option specified, when using a logical host in a cluster configuration, all instances of the JP1/AJS3 service terminate.

no
The process (ajsgwmasterd.exe for Windows and ajsgwmasterd for UNIX) that manages the scheduler service inter-communication control process is not terminated.
In UNIX, if you start the JP1/AJS3 service by executing the jajs_spmd command with the -HA option specified when using a logical host in a cluster configuration, operation can continue. This is because you can use functions other than the execution order control function for root jobnets between scheduler services.

Default value
no

Recommended value
Default value

When the setting takes effect
When the JP1/AJS3 service starts

(92) "GWRESTARTCOUNT"=dword:number-of-restarting-scheduler-service-inter-communication-control-process

Use this parameter to specify the number of times automatic restart is to be attempted if the scheduler service inter-communication control process terminates abnormally.

Specifiable values
A hexadecimal value from 0 to 3 (0 to 3 in decimal)

Default value
dword:00000003 (3 in decimal)

Recommended value
Default value

When the setting takes effect
When the JP1/AJS3 service starts

[Contents][Back][Next]

[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.