Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

4.3.2 Environment settings for scheduler services

This subsection explains the environment settings for the scheduler services in a JP1/AJS3 - Manager host.

For details about performing these settings, see 4.2 Environment setting parameter settings in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 13.2 Environment setting parameter settings in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

For details about specific settings (environment setting parameters), see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Determine the scheduler service settings for JP1/AJS3 - Manager, referring to the recommended values and setting criteria given in the following table.

Table 4-6 Environment settings related to scheduler services (JP1/AJS3 - Manager)

Setting description and parameter Criterion for changing the setting Recommended value When the setting takes effect

Default scheduler service name

Environment setting parameter:

DEFAULTSERVICENAME

Specify the name of the default scheduler service.
If you plan to use commands to operate on units in an environment with multiple scheduler services, you do not need to specify the -F scheduler-service-name option in a command to the scheduler service specified in this parameter. Determine according to your system operation. At process startup

Scheduler service name for executing remote jobnets

Environment setting parameter:

REMNETSERVICENAME

Specify this parameter to execute remote jobnets. Use of remote jobnets is not recommended. Immediately (when a remote jobnet process is activated)

Scheduler service restart count

Environment setting parameter:

AUTORESTARTCOUNT

Specify 0 to immediately halt job execution in JP1/AJS3 should the scheduler service end abnormally.
If you plan to monitor abnormal termination of a scheduler service within a process or by using the jajs_spmd_status command, specify 0 in this parameter and the appropriate value in the MASTERDABEND parameter.
Note that this environment setting parameter only takes effect to compatible ISAM configuration. Use the default (3). When the scheduler services start

Time until the restart count is reset

Environment setting parameter:

RESTARTCLRTIME

Increase the value when the scheduler service takes longer than three minutes to start and you do not want to continually restart the service at abnormal end.
Note that this environment setting parameter only takes effect to compatible ISAM configuration. Use the default (180). When the scheduler service starts

Processing when a scheduler service ends abnormally

Environment setting parameter:

MASTERDABEND

Specify yes if you plan to monitor JP1/AJS3 operations using the jajs_spmd_status command.
Note that this environment setting parameter only takes effect to compatible ISAM configuration. Use the default (no). When JP1/AJS3 is restarted

Output of ajsinetd process messages and monitor server start/end messages to the Windows event log or syslog

Environment setting parameter:

MONSYSLOG

Change the setting if there is no need to check the JP1/AJS3 - View connection status in the Windows event log or syslog file.
Note that if you change this setting, you will not be able to check the JP1/AJS3 - View connection status if a problem occurs. all
all is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. Immediately (when you next log in to JP1/AJS3 - View)

Output of monitor server start/end messages to the scheduler log when JP1/AJS3 - View requests connection to the scheduler service

Environment setting parameter:

MONLOG

Change the setting if you want to output the connection status from JP1/AJS3 - View to the scheduler log file. Determine according to your system operation. When the scheduler service starts or stops

Output of user authentication messages to the Windows event log or syslog, and to the integrated trace log

Environment setting parameter:

AUTHSYSLOG

Change the setting if you want to output user authentication messages to the Windows event log or syslog file. Determine according to your system operation. Immediately (on receipt of the next authentication request)

Output of user authentication messages to the scheduler log

Environment setting parameter:

AUTHLOG

Change the setting if you want to output user authentication messages to the scheduler log file. Determine according to your system operation. Immediately (on receipt of the next authentication request)

Maximum number of concurrent sessions

Environment setting parameter:

MAXSESSION

If the maximum number of connections from JP1/AJS3 - View is likely to exceed 50, increase the value accordingly. If there are resource constraints and you need to limit JP1/AJS3 - View connections, reduce the value. Determine according to your system operation. When the scheduler service starts or stops

Method for starting the logon session process

Environment setting parameter:

REUSELOGON

Specify yes if a large number of sessions mapped to the same OS user are started concurrently and the logon session process cannot start due to desktop heap shortages.
Logon resources are reused for the following types of process startup:

Connection of JP1/AJS3 - View

Remote execution of a command

Execution of a remote jobnet

Operation from JP1/AJS3 - Definition Assistant

Specify yes if the desktop heap is of insufficient size. At startup of the ajsinetd process^#1

Number of sessions that share logon resources

Environment setting parameter:

LOGONSHMAX

Specify this parameter to change the number of sessions that share logon information when logon resources are reused.
Adjust the desktop heap area, if insufficient, to within the following range. For details about the size of the desktop heap that is allocated to non-interactive processes, see the Windows documentation.
number-of-sessions-that-share-logon-resources <
size-of-desktop-heap-allocated-to-non-interactive-processes (kilobytes) / 10 (kilobytes) Use the default. At startup of the ajsinetd process^#1

Automatic start of the scheduler service

Environment setting parameter:

AUTOSTART

Specify no for a scheduler service that does not need to be activated during normal operation, such as one used for test purposes. Determine according to your system operation. When JP1/AJS3 is restarted

Scheduler service ID

Environment setting parameter:

AJSSERVICEID

Specify a number unique within the computer. Determine according to your system operation. When the scheduler service starts

Service name of the port used to acquire job statuses

Environment setting parameter:

JOBSTATUSPORT

You must specify this value if setting multiple scheduler services for one JP1/AJS3 service (physical host/logical host). Determine according to your system operation. When the scheduler service starts

Maximum number of queueless job requests

Environment setting parameter:

QUEUELESSMULTIREQ

Specify this parameter to increase the number of processes that communicate with the queueless agent service, thereby eliminating the effects that the transfer of queueless jobs might have on job execution performance. Use the default as queueless job transfers do not affect job execution performance in the present queueless job system. Use the default. When the scheduler service starts

Output destination for scheduler log files

Environment setting parameter:

AJSLOGOUTPUTDEST

Specify schedule to output the log data from each scheduler service to a different file. Specify host to output log data from different scheduler services to a single file per host. Use the default (schedule). When the scheduler services start

Size of the scheduler log file (when output per scheduler service)

Environment setting parameter:

LOGSIZE

As this file is used for checking the execution status of jobs and jobnets, specify a file size large enough to store at least one day's log data. Determine according to your system operation. When the scheduler service starts or stops

Name of the scheduler log file 1

Environment setting parameter:

AJSLOGFILE1

Determine according to your system operation. Use the default. When the scheduler service starts or stops

Name of the scheduler log file 2

Environment setting parameter:

AJSLOGFILE2

Determine according to your system operation. Use the default. When the scheduler service starts or stops

Output of the year to a scheduler log file

Environment setting parameter:

AJSLOGOUTPUTYEAR

Change the setting if you want to manage scheduler logs by date including the year. Determine according to your system operation. When the scheduler service starts or stops

Extended output to scheduler log files

Environment setting parameter:

UNIX

AJSLOGOUTPUTEXTEND

Change the setting if you want to include the operation user type, requester information, and detailed options of command operations in the data output to a scheduler log file. Determine according to your system operation. When the scheduler service starts or stops

Output of start/end messages about the scheduler log output process to a scheduler log file

Environment setting parameter:

LOGDLOG

Change the setting if you want to output messages about the start/end of the scheduler log output process to the scheduler log file. Determine according to your system operation. When the scheduler service starts or stops

Output of start/end messages about the scheduler log output process to the Windows event log or syslog, and to the integrated trace log

Environment setting parameter:

LOGDSYSLOG

Change the setting if you want to output messages about the start/end of the scheduler log output process to the Windows event log or syslog file. Determine according to your system operation. When the scheduler service starts or stops

Output of scheduler service start/end messages to the Windows event log or syslog

Environment setting parameter:

AJSSYSLOG

Specify this parameter if you want to output the start/end status of a scheduler service to the Windows event log or syslog file. Use the default (none). When the scheduler service starts

Format of output log data

Environment setting parameter:

LOGINFOALL

Change the setting if you do not want to output log entries in a format that includes additional information such as the execution ID and job number. yes
yes is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts or stops

Output of scheduler log data

Environment setting parameter:

INFOLOG

Change the setting if you do not want to evaluate performance such as command processing time and the number of concurrently executed commands. all
all is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts or stops

Output of an execution log for commands that reference a unit

Environment setting parameter:

REFLOG

Specify this parameter if you want to retain an execution log for reference commands such as ajsprint. Use the default (all). When the scheduler service starts or stops

Format of output log data

Environment setting parameter:

LOGHEADER

Change the setting if you do not want to output log entries in a format that includes the process ID as additional information. PID
PID is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts or stops

Output of jobnet start/end messages to the Windows event log or syslog

Environment setting parameter:

NETSYSLOG

Specify this parameter to output messages about the start/end status of jobnets to the Windows event log or syslog file. Use the default (none). When the scheduler service starts

Output of start/end messages about the jobs in a jobnet to the Windows event log or syslog

Environment setting parameter:

JOBSYSLOG

Specify this parameter to output messages about the start/end status of jobs in a jobnet to the Windows event log or syslog file. Use the default (none). When the scheduler service starts

Service start mode

Environment setting parameter:

STARTMODE

Specify hot to restart a service that ended abnormally at the previous session, resuming operation from its status at that time. Determine according to your system operation. When the scheduler service starts

Method of skipping jobnets

Environment setting parameter:

OVERSCHEDULE

Specify this parameter to change the execution method if the scheduled time for starting execution of a jobnet on a particular day is already past when the scheduler service starts. Determine according to your system operation. When the scheduler service starts

Suppress option

Environment setting parameter:

SUPPRESS

Change the setting if you want to suppress execution of jobnets and jobs. Determine according to your system operation. When the scheduler service starts

Applicability of Skipped so not exe. status for jobnets

Environment setting parameter:

EXECDEFER

Specify this parameter if you want to change the application of Skipped so not exe. status when a root jobnet registered for execution fails to execute by the scheduled start time. Determine according to your system operation. When the scheduler service starts

Effective time range of root jobnet schedules

Environment setting parameter:

ROOTJOBNETSCHEDULERANGE

Change the setting if you want to set an effective range of 48 hours for executing a scheduled root jobnet.
Because the root jobnet's execution schedule will be different after you change this setting, you must cold-start the scheduler service and review the jobnet schedule. Determine according to your system operation. When the scheduler service starts

Range of generation information acquired for status display in JP1/AJS3 - View

Environment setting parameter:

VIEWSTATUSRANGE

Change this setting to determine the status to display from today's generation information within the base time range. Determine according to your system operation. When the scheduler service starts

Whether changes to a jobnet definition take effect immediately

Environment setting parameter:

UNITDEFINERELOAD

Change this setting if you do not want changes to defined unit information to take immediate effect. yes
yes is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts

Display of scheduler services in JP1/AJS3 - View

Environment setting parameter:

HIDEOTHERLHOST

Specify no if you want to access the scheduler services of all logical hosts in the JP1/AJS3 - Manager to which you logged in from JP1/AJS3 - View. yes Immediately (when you next log in to JP1/AJS3 - View)

Method of managing the number of saved generations of a jobnet with start conditions

Environment setting parameter:

SAVEGENTYPE

Specify LEGACY to use the management mode in JP1/AJS2 version 8 and earlier. TOTAL When the scheduler service starts

Database directory name

Environment setting parameter:

AJSDBDIRECTORY

Change this setting if there is no space in the default directory, or if you need to change the default directory to one on the shared disk in a cluster configuration.
If using multiple scheduler services, specify a unique name for each database directory. Use the default or determine according to your system operation. When the scheduler service starts or stops^#2

Database type

Environment setting parameter:

AJSDBTYPE

There is no need to change the value set by JP1/AJS3 - Manager. Value set by JP1/AJS3 - Manager When the scheduler service starts or stops^#2

Table name prefix

Environment setting parameter:

TABLENAMEPREFIX

There is no need to change the default AJS. Use the default. When the scheduler service starts or stops^#2

Write mode for updating ISAM files

Environment setting parameter:

ISAMWRITEMODE

Choose an appropriate write mode according to performance, reliability, and operational requirements when using ISAM files. Specify flush for a physical host.
Specify sync for a cluster system. When the scheduler service starts or stops

RDB permission identifier

Environment setting parameter:

RDBAUTHID

Do not change the setting. -- When the scheduler service starts or stops

RDB access user name

Environment setting parameter:

RDBUSER

Do not change the setting. -- When the scheduler service starts or stops

RDB user password

Environment setting parameter:

RDBPASSWORD

Do not change the setting. -- When the scheduler service starts or stops

RDB server disconnection detection interval

Environment setting parameter:

RDBCHECKINTERVAL

Do not change the setting. dword:0000012C (300 in decimal notation) When the scheduler service starts

RDB connection-destination host

Environment setting parameter:

RDBHOST

Do not change the setting. -- When the scheduler service starts or stops

RDB port number

Environment setting parameter:

RDBPORT

Do not change the setting. -- When the scheduler service starts or stops

RDB server communication protocol

Environment setting parameter:

RDBIPC

Do not change the setting. -- When the scheduler service starts or stops

Sending memory size for communication between RDB processes

Environment setting parameter:

RDBSENDMEMSIZE

Do not change the setting. -- When the scheduler service starts or stops

Receiving memory size for communication between RDB processes

Environment setting parameter:

RDBRECVMEMSIZE

Do not change the setting. -- When the scheduler service starts or stops

RDB connection timeout

Environment setting parameter:

RDBCONNECTWAITTIME

Do not change the setting. -- When the scheduler service starts

Name of the directory for temporary files

Environment setting parameter:

AJSTMPDIR

No particular criteria. Determine according to your system operation and estimated disk space requirements. Use the default. When the scheduler service starts or stops

Name of the directory for job error information

Environment setting parameter:

JOBINFDIR

No particular criteria. Determine according to your system operation and estimated disk space requirements. Use the default. When the scheduler service starts or stops

Name of the directory for backup data

Environment setting parameter:

AJSBKUROOT

No particular criteria. Determine according to your system operation and estimated disk space requirements. Use the default. When the scheduler service starts or stops

File name of the scheduler trace log

Environment setting parameter:

TRACELOGFILE

Determine according to your system operation. Use the default.

In Windows Server 2008:
%ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog
(The default directory of %ALLUSERSPROFILE% is system-drive\Program Data.)

In Windows Server 2003:
JP1/AJS3-Manager-installation-folder\log\tracelog

In UNIX:
/var/opt/jp1ajs2/log/tracelog

At process startup

Timeout for remote communication

Environment setting parameter:

IPC_TIMEOUT

Specify a non-zero value if you want to explicitly specify a timeout period different from the OS timeout. Use the default (0). At process startup

Timeout for local communication

Environment setting parameter:

IPC_LOCALTIMEOUT

Specify a non-zero value if you want to explicitly specify a timeout period different from the OS timeout. Use the default (0). At process startup

Retry interval

Environment setting parameter:

IPCRETRYINTERVAL

Change this parameter, and the retry count value, according to the communication error status. Use the default (1). At process startup

Retry count

Environment setting parameter:

IPCRETRYCOUNT

Change this parameter, and the retry interval value, according to the communication error status. Use the default (3) or a larger value, depending on your system operation. At process startup

Processing when unable to connect to the event service

Environment setting parameter:

EVENTRETRY

Change this parameter if you want to establish a connection whenever a JP1 event is issued.
You can specify no if the JP1 events (4100 to 4142) output by a scheduler service will not be referenced. yes Immediately

Whether to immediately stop jobnet execution when a root jobnet is canceled or killed

Environment setting parameter:

VRSHIFT_IMMINT

Change the setting if you want to change the jobnet status when the jobs in a jobnet that was canceled or killed while the scheduler service was suppressing job execution are subsequently released from suppressed status. Use the default (V5). When the scheduler service starts

Whether to re-execute the remaining units in a canceled jobnet

Environment setting parameter:

VRSHIFT_INTRERUN

Change the setting if you do not want to re-execute the remaining units in a cancelled jobnet. V5
V5 is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts

Connection timeout

Environment setting parameter:

SESSIONTIMEOUT

No particular criteria. Use the default (120). At JP1/AJS3 - View connection after the scheduler service starts or stops

Size of the scheduler service's buffer for job execution information

Environment setting parameter:

JOBEXECIPCBUFSIZE

Determine according to your system operation. Use the default (0). When the scheduler service starts

Deletion of generations by unregistering jobnets and managing the number of logs to keep

Environment setting parameter:

BACKGROUNDLEAVE

Change this setting to unregister jobnets and delete the jobnet information in the background by creating a generation management subprocess (ajsschbd). yes When the scheduler service starts

Timeout for connection to a queueless agent

Environment setting parameter:

REQDAGTREQCONNECTTIMEOUT

Do not change the setting without good reason. Use the default (15). When the scheduler service starts

Timeout for recovery of the connection to a queueless agent

Environment setting parameter:

REQDAGTRECONNECTTIMEOUT

Do not change the setting without good reason. Use the default (90). When the scheduler service starts

Whether to issue a JP1 event when an operation is performed by command or from JP1/AJS3 - View

Environment setting parameter:

COMMANDEVENT

Change the setting if you want to monitor command operations or JP1/AJS3 - View operations using JP1 events. Determine according to your system operation. When the scheduler service starts or stops

Size of the internal log of the ajsinetd process

Environment setting parameter:

AJSINETDLOGSIZE

Determine according to your system operation. Use the default. When the ajsinetd process starts^#1

Table ID

Environment setting parameter:

TABLENAMEPOSTFIX

Specify this parameter to add a suffix to the table name stored in the scheduler services schema.
If you are creating multiple scheduler services in the same schema using the embedded database, make sure that you do not duplicate an existing suffix or table name. Determine according to your system operation. When the scheduler service starts or stops^#2

Output of scheduler service start/end messages to the scheduler log file

Environment setting parameter:

AJSLOG

Change the setting if you do not want to output scheduler service start/end messages to the scheduler log file. Determine according to your system operation. When the scheduler service starts

Output of jobnet start/end messages to the scheduler log file

Environment setting parameter:

NETLOG

Change the setting if you do not want to output jobnet start/end messages to the scheduler log file. Determine according to your system operation. When the scheduler service starts

Output of start/end messages about the jobs in a jobnet to the scheduler log file

Environment setting parameter:

JOBLOG

Change the setting if you do not want to output start/end messages about the jobs in a jobnet to the scheduler log file. Determine according to your system operation. When the scheduler service starts

Output of the operation history to the scheduler log file

Environment setting parameter:

OPELOG

Change the setting if you do not want to output the operation history to the scheduler log file. Determine according to your system operation. When the scheduler service starts or stops

Maximum number of saved generations

Environment setting parameter:

MAXSAVEGEN

Change the setting if you want to increase the maximum number of saved generations to 100 or more. Note that the number of records in this case will increase to a value equal to the number of saved generations multiplied by the number of registered units. This will have major effects on all operations that involve accessing the database, including unregistering jobs and so on. Take due consideration of how system performance will be affected if changing the maximum number of saved generations. Determine according to your system operation. When the scheduler service starts

Handling of the schedule rule for nested jobnets

Environment setting parameter:

AJSPRINTNETSCHPRF

The schedule rule makes jobnet execution dependent on the schedule of the upper-level jobnet. Change the setting if you do not want the schedule rule to take effect when the ajsprint, ajsbackup, or ajsexport command, or the Backup command in JP1/AJS3 - View, is executed on a jobnet created by copying a root jobnet with a schedule rule to a nested jobnet. no
no is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time. When the scheduler service starts

Retry interval for submit processing

Environment setting parameter:

SUBMITRETRYINTERVAL

When a large number of jobs are executed concurrently, they might be submitted but not actually queued (held submission). Specify this parameter to change the retry interval for submitting held jobs. Take care because specifying a small retry interval will result in persistent retries while submitted jobs are held, increasing the system load. Determine according to your system operation. When the scheduler service starts

Reloading of definitions for held units

Environment setting parameter:

NONRELOADHOLDING

Change the setting if you do not want to release the current held status of a unit by redefining its hold attribute from yes to no. yes When the scheduler service starts

Severity level of messages output to the integrated trace log

Environment setting parameter:

HNTRLOGLEVEL

Determine what value to set according to what level of messages will be output in your system. Determine according to your system operation. When the scheduler service starts

Whether to control the execution order of root jobnets in different scheduler services using a jobnet connector

Environment setting parameter:

RJCUSE

Change the setting if you want to control the execution order of root jobnets in different scheduler services. Determine according to your system operation. When the JP1/AJS3 service starts

Whether to output a message to the integrated trace log when the scheduler service restarts, reporting that the job execution control agent has started execution of a job that it was monitoring for end delay, based on the time required for execution, while the scheduler service was stopped

Environment setting parameter:

JOBDELAYWARNMSG

Change the setting to output a message to the integrated trace log when the scheduler service starts. Determine according to your system operation. When the scheduler service starts

Retry count when the flow control process and scheduler service inter-communication control process cannot be connected

Environment setting parameter:

FGRECONLMT

Specify this parameter if you want to change the retry count for connection between the flow control process and the scheduler service inter-communication control process. Use the default (3). When the scheduler service starts

Name of the parent directory for system files used by JP1/AJS3 scheduler services

Environment setting parameter:

AJSSYSDIR

Determine according to your system operation. Use the default. When the scheduler service starts or stops

Name of the parent directory for log files output by JP1/AJS3 scheduler services

Environment setting parameter:

AJSLOGDIR

Determine according to your system operation. Use the default. When the scheduler service starts or stops

Maximum number of scheduler service inter-communication control process connections

Environment setting parameter:

GWMAXCONNECTION

Change the setting if the number of JP1/AJS3 - Manager hosts in which a scheduler service inter-communication control process has been set up exceeds the default. Use the default or set the number of JP1/AJS3 - Manager hosts in which the control process has been set up. When the JP1/AJS3 service starts

Whether to terminate the manager process if the scheduler service inter-communication control process ends abnormally

Environment setting parameter:

GWPROCESSHA

Change the setting if you want to terminate the process that manages a scheduler service inter-communication control process that has ended abnormally. Use the default (no). When the JP1/AJS3 service starts

Automatic restart count when a scheduler service inter-communication control process ends abnormally

Environment setting parameter:

GWRESTARTCOUNT

Specify this parameter if you want to change the number of times that an abnormally ended scheduler service inter-communication control process is restarted automatically. Use the default (3). When the JP1/AJS3 service starts

#1

For details about how to start and stop a specific ajsinetd process, 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.

#2

If you change this parameter, you must recreate the scheduler database.

Setting description and parameter	Criterion for changing the setting	Recommended value	When the setting takes effect
Default scheduler service name Environment setting parameter: DEFAULTSERVICENAME	Specify the name of the default scheduler service. If you plan to use commands to operate on units in an environment with multiple scheduler services, you do not need to specify the -F scheduler-service-name option in a command to the scheduler service specified in this parameter.	Determine according to your system operation.	At process startup
Scheduler service name for executing remote jobnets Environment setting parameter: REMNETSERVICENAME	Specify this parameter to execute remote jobnets.	Use of remote jobnets is not recommended.	Immediately (when a remote jobnet process is activated)
Scheduler service restart count Environment setting parameter: AUTORESTARTCOUNT	Specify 0 to immediately halt job execution in JP1/AJS3 should the scheduler service end abnormally. If you plan to monitor abnormal termination of a scheduler service within a process or by using the jajs_spmd_status command, specify 0 in this parameter and the appropriate value in the MASTERDABEND parameter. Note that this environment setting parameter only takes effect to compatible ISAM configuration.	Use the default (3).	When the scheduler services start
Time until the restart count is reset Environment setting parameter: RESTARTCLRTIME	Increase the value when the scheduler service takes longer than three minutes to start and you do not want to continually restart the service at abnormal end. Note that this environment setting parameter only takes effect to compatible ISAM configuration.	Use the default (180).	When the scheduler service starts
Processing when a scheduler service ends abnormally Environment setting parameter: MASTERDABEND	Specify yes if you plan to monitor JP1/AJS3 operations using the jajs_spmd_status command. Note that this environment setting parameter only takes effect to compatible ISAM configuration.	Use the default (no).	When JP1/AJS3 is restarted
Output of ajsinetd process messages and monitor server start/end messages to the Windows event log or syslog Environment setting parameter: MONSYSLOG	Change the setting if there is no need to check the JP1/AJS3 - View connection status in the Windows event log or syslog file. Note that if you change this setting, you will not be able to check the JP1/AJS3 - View connection status if a problem occurs.	all all is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	Immediately (when you next log in to JP1/AJS3 - View)
Output of monitor server start/end messages to the scheduler log when JP1/AJS3 - View requests connection to the scheduler service Environment setting parameter: MONLOG	Change the setting if you want to output the connection status from JP1/AJS3 - View to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts or stops
Output of user authentication messages to the Windows event log or syslog, and to the integrated trace log Environment setting parameter: AUTHSYSLOG	Change the setting if you want to output user authentication messages to the Windows event log or syslog file.	Determine according to your system operation.	Immediately (on receipt of the next authentication request)
Output of user authentication messages to the scheduler log Environment setting parameter: AUTHLOG	Change the setting if you want to output user authentication messages to the scheduler log file.	Determine according to your system operation.	Immediately (on receipt of the next authentication request)
Maximum number of concurrent sessions Environment setting parameter: MAXSESSION	If the maximum number of connections from JP1/AJS3 - View is likely to exceed 50, increase the value accordingly. If there are resource constraints and you need to limit JP1/AJS3 - View connections, reduce the value.	Determine according to your system operation.	When the scheduler service starts or stops
Method for starting the logon session process Environment setting parameter: REUSELOGON	Specify yes if a large number of sessions mapped to the same OS user are started concurrently and the logon session process cannot start due to desktop heap shortages. Logon resources are reused for the following types of process startup: Connection of JP1/AJS3 - View Remote execution of a command Execution of a remote jobnet Operation from JP1/AJS3 - Definition Assistant	Specify yes if the desktop heap is of insufficient size.	At startup of the ajsinetd process^#1
Number of sessions that share logon resources Environment setting parameter: LOGONSHMAX	Specify this parameter to change the number of sessions that share logon information when logon resources are reused. Adjust the desktop heap area, if insufficient, to within the following range. For details about the size of the desktop heap that is allocated to non-interactive processes, see the Windows documentation. number-of-sessions-that-share-logon-resources < size-of-desktop-heap-allocated-to-non-interactive-processes (kilobytes) / 10 (kilobytes)	Use the default.	At startup of the ajsinetd process^#1
Automatic start of the scheduler service Environment setting parameter: AUTOSTART	Specify no for a scheduler service that does not need to be activated during normal operation, such as one used for test purposes.	Determine according to your system operation.	When JP1/AJS3 is restarted
Scheduler service ID Environment setting parameter: AJSSERVICEID	Specify a number unique within the computer.	Determine according to your system operation.	When the scheduler service starts
Service name of the port used to acquire job statuses Environment setting parameter: JOBSTATUSPORT	You must specify this value if setting multiple scheduler services for one JP1/AJS3 service (physical host/logical host).	Determine according to your system operation.	When the scheduler service starts
Maximum number of queueless job requests Environment setting parameter: QUEUELESSMULTIREQ	Specify this parameter to increase the number of processes that communicate with the queueless agent service, thereby eliminating the effects that the transfer of queueless jobs might have on job execution performance. Use the default as queueless job transfers do not affect job execution performance in the present queueless job system.	Use the default.	When the scheduler service starts
Output destination for scheduler log files Environment setting parameter: AJSLOGOUTPUTDEST	Specify schedule to output the log data from each scheduler service to a different file. Specify host to output log data from different scheduler services to a single file per host.	Use the default (schedule).	When the scheduler services start
Size of the scheduler log file (when output per scheduler service) Environment setting parameter: LOGSIZE	As this file is used for checking the execution status of jobs and jobnets, specify a file size large enough to store at least one day's log data.	Determine according to your system operation.	When the scheduler service starts or stops
Name of the scheduler log file 1 Environment setting parameter: AJSLOGFILE1	Determine according to your system operation.	Use the default.	When the scheduler service starts or stops
Name of the scheduler log file 2 Environment setting parameter: AJSLOGFILE2	Determine according to your system operation.	Use the default.	When the scheduler service starts or stops
Output of the year to a scheduler log file Environment setting parameter: AJSLOGOUTPUTYEAR	Change the setting if you want to manage scheduler logs by date including the year.	Determine according to your system operation.	When the scheduler service starts or stops
Extended output to scheduler log files Environment setting parameter: UNIX AJSLOGOUTPUTEXTEND	Change the setting if you want to include the operation user type, requester information, and detailed options of command operations in the data output to a scheduler log file.	Determine according to your system operation.	When the scheduler service starts or stops
Output of start/end messages about the scheduler log output process to a scheduler log file Environment setting parameter: LOGDLOG	Change the setting if you want to output messages about the start/end of the scheduler log output process to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts or stops
Output of start/end messages about the scheduler log output process to the Windows event log or syslog, and to the integrated trace log Environment setting parameter: LOGDSYSLOG	Change the setting if you want to output messages about the start/end of the scheduler log output process to the Windows event log or syslog file.	Determine according to your system operation.	When the scheduler service starts or stops
Output of scheduler service start/end messages to the Windows event log or syslog Environment setting parameter: AJSSYSLOG	Specify this parameter if you want to output the start/end status of a scheduler service to the Windows event log or syslog file.	Use the default (none).	When the scheduler service starts
Format of output log data Environment setting parameter: LOGINFOALL	Change the setting if you do not want to output log entries in a format that includes additional information such as the execution ID and job number.	yes yes is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts or stops
Output of scheduler log data Environment setting parameter: INFOLOG	Change the setting if you do not want to evaluate performance such as command processing time and the number of concurrently executed commands.	all all is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts or stops
Output of an execution log for commands that reference a unit Environment setting parameter: REFLOG	Specify this parameter if you want to retain an execution log for reference commands such as ajsprint.	Use the default (all).	When the scheduler service starts or stops
Format of output log data Environment setting parameter: LOGHEADER	Change the setting if you do not want to output log entries in a format that includes the process ID as additional information.	PID PID is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts or stops
Output of jobnet start/end messages to the Windows event log or syslog Environment setting parameter: NETSYSLOG	Specify this parameter to output messages about the start/end status of jobnets to the Windows event log or syslog file.	Use the default (none).	When the scheduler service starts
Output of start/end messages about the jobs in a jobnet to the Windows event log or syslog Environment setting parameter: JOBSYSLOG	Specify this parameter to output messages about the start/end status of jobs in a jobnet to the Windows event log or syslog file.	Use the default (none).	When the scheduler service starts
Service start mode Environment setting parameter: STARTMODE	Specify hot to restart a service that ended abnormally at the previous session, resuming operation from its status at that time.	Determine according to your system operation.	When the scheduler service starts
Method of skipping jobnets Environment setting parameter: OVERSCHEDULE	Specify this parameter to change the execution method if the scheduled time for starting execution of a jobnet on a particular day is already past when the scheduler service starts.	Determine according to your system operation.	When the scheduler service starts
Suppress option Environment setting parameter: SUPPRESS	Change the setting if you want to suppress execution of jobnets and jobs.	Determine according to your system operation.	When the scheduler service starts
Applicability of Skipped so not exe. status for jobnets Environment setting parameter: EXECDEFER	Specify this parameter if you want to change the application of Skipped so not exe. status when a root jobnet registered for execution fails to execute by the scheduled start time.	Determine according to your system operation.	When the scheduler service starts
Effective time range of root jobnet schedules Environment setting parameter: ROOTJOBNETSCHEDULERANGE	Change the setting if you want to set an effective range of 48 hours for executing a scheduled root jobnet. Because the root jobnet's execution schedule will be different after you change this setting, you must cold-start the scheduler service and review the jobnet schedule.	Determine according to your system operation.	When the scheduler service starts
Range of generation information acquired for status display in JP1/AJS3 - View Environment setting parameter: VIEWSTATUSRANGE	Change this setting to determine the status to display from today's generation information within the base time range.	Determine according to your system operation.	When the scheduler service starts
Whether changes to a jobnet definition take effect immediately Environment setting parameter: UNITDEFINERELOAD	Change this setting if you do not want changes to defined unit information to take immediate effect.	yes yes is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts
Display of scheduler services in JP1/AJS3 - View Environment setting parameter: HIDEOTHERLHOST	Specify no if you want to access the scheduler services of all logical hosts in the JP1/AJS3 - Manager to which you logged in from JP1/AJS3 - View.	yes	Immediately (when you next log in to JP1/AJS3 - View)
Method of managing the number of saved generations of a jobnet with start conditions Environment setting parameter: SAVEGENTYPE	Specify LEGACY to use the management mode in JP1/AJS2 version 8 and earlier.	TOTAL	When the scheduler service starts
Database directory name Environment setting parameter: AJSDBDIRECTORY	Change this setting if there is no space in the default directory, or if you need to change the default directory to one on the shared disk in a cluster configuration. If using multiple scheduler services, specify a unique name for each database directory.	Use the default or determine according to your system operation.	When the scheduler service starts or stops^#2
Database type Environment setting parameter: AJSDBTYPE	There is no need to change the value set by JP1/AJS3 - Manager.	Value set by JP1/AJS3 - Manager	When the scheduler service starts or stops^#2
Table name prefix Environment setting parameter: TABLENAMEPREFIX	There is no need to change the default AJS.	Use the default.	When the scheduler service starts or stops^#2
Write mode for updating ISAM files Environment setting parameter: ISAMWRITEMODE	Choose an appropriate write mode according to performance, reliability, and operational requirements when using ISAM files.	Specify flush for a physical host. Specify sync for a cluster system.	When the scheduler service starts or stops
RDB permission identifier Environment setting parameter: RDBAUTHID	Do not change the setting.	--	When the scheduler service starts or stops
RDB access user name Environment setting parameter: RDBUSER	Do not change the setting.	--	When the scheduler service starts or stops
RDB user password Environment setting parameter: RDBPASSWORD	Do not change the setting.	--	When the scheduler service starts or stops
RDB server disconnection detection interval Environment setting parameter: RDBCHECKINTERVAL	Do not change the setting.	dword:0000012C (300 in decimal notation)	When the scheduler service starts
RDB connection-destination host Environment setting parameter: RDBHOST	Do not change the setting.	--	When the scheduler service starts or stops
RDB port number Environment setting parameter: RDBPORT	Do not change the setting.	--	When the scheduler service starts or stops
RDB server communication protocol Environment setting parameter: RDBIPC	Do not change the setting.	--	When the scheduler service starts or stops
Sending memory size for communication between RDB processes Environment setting parameter: RDBSENDMEMSIZE	Do not change the setting.	--	When the scheduler service starts or stops
Receiving memory size for communication between RDB processes Environment setting parameter: RDBRECVMEMSIZE	Do not change the setting.	--	When the scheduler service starts or stops
RDB connection timeout Environment setting parameter: RDBCONNECTWAITTIME	Do not change the setting.	--	When the scheduler service starts
Name of the directory for temporary files Environment setting parameter: AJSTMPDIR	No particular criteria. Determine according to your system operation and estimated disk space requirements.	Use the default.	When the scheduler service starts or stops
Name of the directory for job error information Environment setting parameter: JOBINFDIR	No particular criteria. Determine according to your system operation and estimated disk space requirements.	Use the default.	When the scheduler service starts or stops
Name of the directory for backup data Environment setting parameter: AJSBKUROOT	No particular criteria. Determine according to your system operation and estimated disk space requirements.	Use the default.	When the scheduler service starts or stops
File name of the scheduler trace log Environment setting parameter: TRACELOGFILE	Determine according to your system operation.	Use the default. In Windows Server 2008: %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog (The default directory of %ALLUSERSPROFILE% is system-drive\Program Data.) In Windows Server 2003: JP1/AJS3-Manager-installation-folder\log\tracelog In UNIX: /var/opt/jp1ajs2/log/tracelog	At process startup
Timeout for remote communication Environment setting parameter: IPC_TIMEOUT	Specify a non-zero value if you want to explicitly specify a timeout period different from the OS timeout.	Use the default (0).	At process startup
Timeout for local communication Environment setting parameter: IPC_LOCALTIMEOUT	Specify a non-zero value if you want to explicitly specify a timeout period different from the OS timeout.	Use the default (0).	At process startup
Retry interval Environment setting parameter: IPCRETRYINTERVAL	Change this parameter, and the retry count value, according to the communication error status.	Use the default (1).	At process startup
Retry count Environment setting parameter: IPCRETRYCOUNT	Change this parameter, and the retry interval value, according to the communication error status.	Use the default (3) or a larger value, depending on your system operation.	At process startup
Processing when unable to connect to the event service Environment setting parameter: EVENTRETRY	Change this parameter if you want to establish a connection whenever a JP1 event is issued. You can specify no if the JP1 events (4100 to 4142) output by a scheduler service will not be referenced.	yes	Immediately
Whether to immediately stop jobnet execution when a root jobnet is canceled or killed Environment setting parameter: VRSHIFT_IMMINT	Change the setting if you want to change the jobnet status when the jobs in a jobnet that was canceled or killed while the scheduler service was suppressing job execution are subsequently released from suppressed status.	Use the default (V5).	When the scheduler service starts
Whether to re-execute the remaining units in a canceled jobnet Environment setting parameter: VRSHIFT_INTRERUN	Change the setting if you do not want to re-execute the remaining units in a cancelled jobnet.	V5 V5 is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts
Connection timeout Environment setting parameter: SESSIONTIMEOUT	No particular criteria.	Use the default (120).	At JP1/AJS3 - View connection after the scheduler service starts or stops
Size of the scheduler service's buffer for job execution information Environment setting parameter: JOBEXECIPCBUFSIZE	Determine according to your system operation.	Use the default (0).	When the scheduler service starts
Deletion of generations by unregistering jobnets and managing the number of logs to keep Environment setting parameter: BACKGROUNDLEAVE	Change this setting to unregister jobnets and delete the jobnet information in the background by creating a generation management subprocess (ajsschbd).	yes	When the scheduler service starts
Timeout for connection to a queueless agent Environment setting parameter: REQDAGTREQCONNECTTIMEOUT	Do not change the setting without good reason.	Use the default (15).	When the scheduler service starts
Timeout for recovery of the connection to a queueless agent Environment setting parameter: REQDAGTRECONNECTTIMEOUT	Do not change the setting without good reason.	Use the default (90).	When the scheduler service starts
Whether to issue a JP1 event when an operation is performed by command or from JP1/AJS3 - View Environment setting parameter: COMMANDEVENT	Change the setting if you want to monitor command operations or JP1/AJS3 - View operations using JP1 events.	Determine according to your system operation.	When the scheduler service starts or stops
Size of the internal log of the ajsinetd process Environment setting parameter: AJSINETDLOGSIZE	Determine according to your system operation.	Use the default.	When the ajsinetd process starts^#1
Table ID Environment setting parameter: TABLENAMEPOSTFIX	Specify this parameter to add a suffix to the table name stored in the scheduler services schema. If you are creating multiple scheduler services in the same schema using the embedded database, make sure that you do not duplicate an existing suffix or table name.	Determine according to your system operation.	When the scheduler service starts or stops^#2
Output of scheduler service start/end messages to the scheduler log file Environment setting parameter: AJSLOG	Change the setting if you do not want to output scheduler service start/end messages to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts
Output of jobnet start/end messages to the scheduler log file Environment setting parameter: NETLOG	Change the setting if you do not want to output jobnet start/end messages to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts
Output of start/end messages about the jobs in a jobnet to the scheduler log file Environment setting parameter: JOBLOG	Change the setting if you do not want to output start/end messages about the jobs in a jobnet to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts
Output of the operation history to the scheduler log file Environment setting parameter: OPELOG	Change the setting if you do not want to output the operation history to the scheduler log file.	Determine according to your system operation.	When the scheduler service starts or stops
Maximum number of saved generations Environment setting parameter: MAXSAVEGEN	Change the setting if you want to increase the maximum number of saved generations to 100 or more. Note that the number of records in this case will increase to a value equal to the number of saved generations multiplied by the number of registered units. This will have major effects on all operations that involve accessing the database, including unregistering jobs and so on. Take due consideration of how system performance will be affected if changing the maximum number of saved generations.	Determine according to your system operation.	When the scheduler service starts
Handling of the schedule rule for nested jobnets Environment setting parameter: AJSPRINTNETSCHPRF	The schedule rule makes jobnet execution dependent on the schedule of the upper-level jobnet. Change the setting if you do not want the schedule rule to take effect when the ajsprint, ajsbackup, or ajsexport command, or the Backup command in JP1/AJS3 - View, is executed on a jobnet created by copying a root jobnet with a schedule rule to a nested jobnet.	no no is set when you perform a new installation of JP1/AJS3 or set up JP1/AJS3 for the first time.	When the scheduler service starts
Retry interval for submit processing Environment setting parameter: SUBMITRETRYINTERVAL	When a large number of jobs are executed concurrently, they might be submitted but not actually queued (held submission). Specify this parameter to change the retry interval for submitting held jobs. Take care because specifying a small retry interval will result in persistent retries while submitted jobs are held, increasing the system load.	Determine according to your system operation.	When the scheduler service starts
Reloading of definitions for held units Environment setting parameter: NONRELOADHOLDING	Change the setting if you do not want to release the current held status of a unit by redefining its hold attribute from yes to no.	yes	When the scheduler service starts
Severity level of messages output to the integrated trace log Environment setting parameter: HNTRLOGLEVEL	Determine what value to set according to what level of messages will be output in your system.	Determine according to your system operation.	When the scheduler service starts
Whether to control the execution order of root jobnets in different scheduler services using a jobnet connector Environment setting parameter: RJCUSE	Change the setting if you want to control the execution order of root jobnets in different scheduler services.	Determine according to your system operation.	When the JP1/AJS3 service starts
Whether to output a message to the integrated trace log when the scheduler service restarts, reporting that the job execution control agent has started execution of a job that it was monitoring for end delay, based on the time required for execution, while the scheduler service was stopped Environment setting parameter: JOBDELAYWARNMSG	Change the setting to output a message to the integrated trace log when the scheduler service starts.	Determine according to your system operation.	When the scheduler service starts
Retry count when the flow control process and scheduler service inter-communication control process cannot be connected Environment setting parameter: FGRECONLMT	Specify this parameter if you want to change the retry count for connection between the flow control process and the scheduler service inter-communication control process.	Use the default (3).	When the scheduler service starts
Name of the parent directory for system files used by JP1/AJS3 scheduler services Environment setting parameter: AJSSYSDIR	Determine according to your system operation.	Use the default.	When the scheduler service starts or stops
Name of the parent directory for log files output by JP1/AJS3 scheduler services Environment setting parameter: AJSLOGDIR	Determine according to your system operation.	Use the default.	When the scheduler service starts or stops
Maximum number of scheduler service inter-communication control process connections Environment setting parameter: GWMAXCONNECTION	Change the setting if the number of JP1/AJS3 - Manager hosts in which a scheduler service inter-communication control process has been set up exceeds the default.	Use the default or set the number of JP1/AJS3 - Manager hosts in which the control process has been set up.	When the JP1/AJS3 service starts
Whether to terminate the manager process if the scheduler service inter-communication control process ends abnormally Environment setting parameter: GWPROCESSHA	Change the setting if you want to terminate the process that manages a scheduler service inter-communication control process that has ended abnormally.	Use the default (no).	When the JP1/AJS3 service starts
Automatic restart count when a scheduler service inter-communication control process ends abnormally Environment setting parameter: GWRESTARTCOUNT	Specify this parameter if you want to change the number of times that an abnormally ended scheduler service inter-communication control process is restarted automatically.	Use the default (3).	When the JP1/AJS3 service starts

[Contents][Back][Next]

[Trademarks]