Hitachi

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

2.2.2 Details of the environment setting parameters for scheduler services

Organization of this subsection

(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 the value appropriate for the operating environment.

When the setting takes effect

When a process starts

To Page Top

(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)

To Page Top

(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

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\tracelog

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\log\tracelog

  • For 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

To Page Top

(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

To Page Top

(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

To Page Top

(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 hosts, a host 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

To Page Top

(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

To Page Top

(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

To Page Top

(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

To Page Top

(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, maintenance-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

To Page Top

(11) "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 ajsinetd process 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.

To Page Top

(12) "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 process 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)

To Page Top

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

Use this parameter to specify the maximum allowable number of simultaneous sessions for JP1/AJS3 - View. If the specified number has been reached and you attempt to connect from JP1/AJS3 - View, the attempt will fail.

If you select scheduler services in the tree area of the JP1/AJS3 - View window, a connection is established for each scheduler service you select. Accordingly, in an environment in which there are multiple scheduler services, the maximum number of connections that will be established is number-of-scheduler-services x number-of-JP1/AJS3 - View-instances.

If the maximum number of JP1/AJS3 - View connections exceeds 50, specify a value based on the maximum number. Also, when you want to restrict JP1/AJS3 - View connections because of resource limitations on the machine, change the value of each host to a smaller one appropriate for operation of the physical host or logical host. You do not need to change the value in any other case.

Specify the environment setting parameter for restricting the number of connections on each host. To restrict the maximum allowable number of simultaneous sessions for JP1/AJS3 - View for each scheduler service rather than by host, use the SERVICEMAXSESSION environment setting parameter. If you use both the MAXSESSION environment setting parameter and the SERVICEMAXSESSION environment setting parameter, note the following:

For example, if scheduler services AJSROOT1 and AJSROOT2 have been created, the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT1 is 25, and the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT2 is 25, you must specify a value of 50 or larger for the MAXSESSION environment setting parameter.

Specifiable values

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

Default value

dword:00000032 (50 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When any scheduler service on an applicable host starts or stops

Cautionary note

If the maximum allowable number of simultaneous sessions has been exceeded, a message (KAVV452-E) is displayed in the JP1/AJS3 - View window (Summary Monitor window) for each monitored unit that is unable to establish a connection. This message is displayed whenever the window is updated.

To Page Top

(14) "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.

To Page Top

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

Use this parameter to specify whether messages related to connections of the following program to the scheduler service and disconnections from it are to be output to the scheduler log:

Change the parameter value if you want to output to the scheduler log the status of the connections established by this program to the scheduler service.

Specifiable values
none

Messages about the connections of this program to and disconnections from the scheduler service are not output.

all

Messages related to the connections of this program to and disconnections from the scheduler service are output.

The following messages are output:

  • JP1/AJS3 - View connection message (KAVS0534-I)

  • JP1/AJS3 - View disconnection message (KAVS0535-I)

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

To Page Top

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

Use this parameter to specify whether to output the following messages to the log:

The messages are output to the following logs.

Change the parameter value if you do not need to check the status of connections established by JP1/AJS3 - View in the Windows event log or syslog. If you change this parameter and an error occurs, you will not be able to check the status of connections for JP1/AJS3 - View.

Specifiable values
none

Messages related to starting and terminating the ajsinetd process or to connecting and disconnecting JP1/AJS3 - View are not output.

all

The following messages are output:

  • ajsinetd process start message (KAVS0530-I)

  • ajsinetd process stop message (KAVS0531-I)

  • Acceptance processing start message for the ajsinetd process (KAVS0532-I)

  • Acceptance processing end message for the ajsinetd process (KAVS0533-I)

  • JP1/AJS3 - View connection message (KAVS0534-I)

  • JP1/AJS3 - View disconnection message (KAVS0535-I)

Default value

none

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

Recommended value

all

When the setting takes effect

Immediately (For messages related to connection and disconnection of JP1/AJS3 - View, the setting takes effect the next time you log in to JP1/AJS3 - View after the scheduler service starts.)

To Page Top

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

Use this parameter to specify whether messages related to user authentication are to be output to the scheduler log for each host.

Specifiable values
none

Messages related to user authentication are not output.

all

Messages related to user authentication are output.

The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the scheduler log for each host.

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)

To Page Top

(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.

  • In Windows:

    The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the Windows event log and the integrated trace log.

  • In UNIX:

    The log message (KAVS1009-W) generated when authentication of the ajsinetd process is rejected is output to the syslog file and the integrated trace log.

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)

To Page Top

(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/AJS3 - 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 host 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)

To Page Top

(20) "CONRESTRICTLOG" = "{none|all}"

Use this parameter to specify whether messages related to restricting connection sources are to be output to the scheduler log of each host.

Specifiable values
none

Messages related to restricting connection sources are not output.

all

All messages related to restricting connection sources are output.

An entry (KAVS8040-E) reporting the rejection of a connection attempt due to the restriction on connection sources in the ajsinetd process and ajscdinetd process is output to the scheduler log of the applicable host.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

(21) "CONRESTRICTSYSLOG" = "{none|all}"

Use this parameter to specify whether messages related to restricting connection sources are to be output to the following log file.

Specifiable values
none

Messages related to restricting connection sources are not output.

all

Messages related to restricting connection sources are output.

An entry (KAVS8040-E) reporting the rejection of a connection attempt due to the restriction on connection sources in the ajsinetd process and ajscdinetd process is output to the Windows event log or syslog.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

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

Use this parameter to specify whether to prevent the display of a scheduler service without access permissions in JP1/AJS3 - View (that is, whether the scheduler service reference restriction function is enabled or disabled).

Specifiable values
yes

The scheduler service reference restriction function is enabled. Scheduler services without permissions are not displayed in JP1/AJS3 - View.

no

The scheduler service reference restriction function is disabled. Scheduler services without access permissions are displayed in JP1/AJS3 - View.

Default value

no

Recommended value

no

When the setting takes effect

Immediately (at the next login to JP1/AJS3 - View)

Supplementary note

If you change the access permissions of a scheduler service, restart JP1/AJS3 - View. The change is reflected in JP1/AJS3 - View.

To Page Top

(23) "CHANGEPASSWORD" = "{yes|no}"

Use this parameter to permit changing JP1 user passwords.

When this functionality is enabled, you can change JP1 user passwords by selecting Options and then Change Password in the connected JP1/AJS3 - View.

Because you must meet the conditions for using this functionality, see the cautionary notes in 6.6.4 Settings for permitting changing JP1 user passwords in JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.7.3 Settings for permitting changing JP1 user passwords in JP1/AJS3 - View in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX), and then decide whether the functionality can be enabled beforehand.

Specifiable values
yes

Changing JP1 user passwords in JP1/AJS3 - View is permitted.

no

Changing JP1 user passwords in JP1/AJS3 - View is not permitted.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

(24) "CHANGEPWDLOG" = "{none|all}"

Use this parameter to specify whether messages related to changing JP1 user passwords are to be output when the JP1 user password change function is enabled in JP1/AJS3 - View (when the CHANGEPASSWORD environment setting parameter is set to yes).

Specifiable values
none

Messages related to changing JP1 user passwords are not output.

all

The following messages related to changing JP1 user passwords are output:

KAVS1010-I (The password was changed successfully)

KAVS1011-E (The password could not be changed)

KAVS1015-I (Changing of the password is now starting)

Default value

all

Recommended value

all

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

(25) "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

To Page Top

(26) "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

To Page Top

(27) "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.

To Page Top

(28) "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

To Page Top

(29) "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 the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(30) "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.

When you use multiple scheduler services, specify a unique file name for each scheduler service.

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

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\schedule-service-name\ajs-log1.log

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log1.log

  • For 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

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

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

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

When you use multiple scheduler services, specify a unique file name for each scheduler service.

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

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log2.log

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log

  • For 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

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(32) "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

To Page Top

(33) "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

To Page Top

(34) "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

To Page Top

(35) "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.

Specifying yes for this parameter increases the amount of information that will be output to the scheduler log. 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 and take into consideration all the factors in changing the value of the LOGSIZE environment setting parameter that specifies the size of a scheduler log. For details about the LOGSIZE environment setting parameter, see (29) LOGSIZE.

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

To Page Top

(36) "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

Scheduler services are not automatically started when JP1/AJS3 - Manager starts.

Specify no when there are scheduler services that do not need to be started.

If you specify no, some processes do not start because scheduler services do not start when JP1/AJS3 - Manager starts. Accordingly, the execution result of the jajs_spmd_status command differs from when yes is specified.

  • Standard configuration:

    The jajs_schd process and its subprocesses do not start. If you want to start a specific scheduler service, use the jajs_spmd command with the -n option specified or the ajsstart command.

  • Compatible ISAM configuration:

    The execution result of the jajs_spmd_status command is the same as when yes is specified. If you want to start a specific scheduler service, use the ajsstart command.

For details about the jajs_spmd command, see jajs_spmd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

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.

Default value

yes

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(37) "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

To Page Top

(38) "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 the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(39) "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

To Page Top

(40) "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

A 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.

To Page Top

(41) "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.

Usually, you do not need to change this value.

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 the value appropriate for the operating environment.

A 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.

To Page Top

(42) "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

To Page Top

(43) "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

To Page Top

(44) "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

To Page Top

(45) "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

To Page Top

(46) "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

To Page Top

(47) "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

To Page Top

(48) "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

To Page Top

(49) "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

To Page Top

(50) "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

To Page Top

(51) "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

To Page Top

(52) "AJSCHARCODE" = "{C|SJIS|EUC|UTF-8}"

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

You must specify one of the listed specifiable values.

If the character set does not match the actual data type, the information will not be displayed correctly in JP1/AJS3 - View.

Do not change the character set while a job is being defined or executed in JP1/AJS3. If you want to change the character set during JP1/AJS3 operation, you must first cancel registration of all the jobnets and back up the unit. After changing the character set, restart the JP1/AJS3 - Manager host, restore the unit, and then register the jobnets for execution.

Specifiable values
C

ASCII character set

SJIS

Shift JIS character set

EUC

EUC character set

UTF-8

UTF-8 character set

Note: UTF-8 is enabled for UNIX only.

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

To Page Top

(53) "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 spaces.

Default value
For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

  • For a physical host:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp\schedule

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For a logical host:

    shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

  • For a physical host:

    JP1/AJS3-Manager-installation-folder\tmp\schedule

  • For a logical host:

    shared-folder\jp1ajs2\tmp\schedule

For Windows Server 2003:

  • For a physical host:

    JP1/AJS3-Manager-installation-folder\tmp\schedule

  • For a logical host:

    shared-folder\jp1ajs2\tmp\schedule

In UNIX:

  • For a physical host:

    /var/opt/jp1ajs2/tmp/schedule

  • For a logical host:

    shared-directory/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

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(54) "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. 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 spaces.

Default value

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\jobinf

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\jobinf

  • For 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

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(55) "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 spaces.

Default value

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\backup\schedule

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\backup\schedule

  • For 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

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(56) "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

To Page Top

(57) "SYSLOGCODE" = "{C|LANG-environment-variable-value}"

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.

LANG-environment-variable-value (character string other than C)

Operation depends on the settings of the LANG environment variable at the time the scheduler service starts. However, in some systems, a message in the language type corresponding to the LANG environment variable at the time the scheduler service starts might not be output to syslog. In such a system, make sure that this parameter is set to C. Check whether Japanese can be output in the system you are using by executing the logger command to output a message in Japanese and then confirming that the message is correctly output to syslog.

The LANG environment variable value differs depending on the OS.

The following table describes the values that can be specified for the LANG environment variable.

Table 2‒3: Specifiable values of the LANG environment variable

OS

Environment variable value for setting Shift JIS

Environment variable value for setting EUC

Environment variable value for setting UTF-8#1

HP-UX

ja_JP.SJIS

japanese

ja_JP.eucJP

japanese.euc

ja_JP.utf8

Solaris

ja_JP.PCK

ja#2

ja_JP.eucJP#2

ja_JP.UTF-8

AIX

Ja_JP

Ja_JP.IBM-932

ja_JP

ja_JP.IBM-eucJP

JA_JP

JA_JP.UTF-8

Linux

Not available

Not available

ja_JP.UTF-8

ja_JP.utf8
#1

In compatible ISAM configuration, UTF-8 can be used in Linux only.

#2

In Solaris 11, ja and ja_JP.eucJP can be used.

In Solaris 10, only ja can be used.

Default value

C

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(58) "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

To Page Top

(59) "NETSYSLOG" = "{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:connector:prewait}|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.

prewait

Messages related to the start and end of waiting in accordance with a jobnet wait condition and the messages related to endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-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)

  • Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-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

To Page Top

(60) "JOBSYSLOG" = "{none|{abend:warning:hold:enddelay:prewait:retry}|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.

prewait

Messages related to the start and end of waiting in accordance with a job wait condition and the messages related to endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E) are output.

retry

The automatic retry notification messages generated when a job ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I) are 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)

  • Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E)

  • Automatic retry of a job that ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-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

To Page Top

(61) "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

Messages related to starting (KAVS0200-I) and terminating (KAVS0201-I) the scheduler service and to the abnormal end message for processes (KAVS0204-E) 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

To Page Top

(62) "NETLOG" = "{none|{abend:warning:hold:startdelay:enddelay:condition:execdeffer:prewait}|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) and the block notification messages (KAVS0272-E and KAVS0273-E) are 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.

prewait

Messages related to the start and end of waiting in accordance with a jobnet wait condition and those related to endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-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)

  • Block notification (KAVS0272-E and KAVS0273-E)

  • Delayed start (KAVS0275-I)

  • Delayed end (KAVS0276-I)

  • Notification of the next queued execution schedule (KAVS0277-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)

  • Notification of the wait for the end of start-condition monitoring (KAVS1420-I)

  • Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4950-I, KAVS4955-I, and KAVS4957-E)

If you specify a value other than all, the following messages are not output:

  • Start (KAVS0260-I)

  • Normal end (KAVS0261-I)

  • Notification of the next queued execution schedule (KAVS0277-I)

  • All registrations canceled (KAVS0267-I)

  • Notification of the wait for the end of start-condition monitoring (KAVS1420-I)

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.

To Page Top

(63) "JOBLOG" = "{none|{abend:warning:hold:enddelay:prewait:retry}|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.

prewait

Messages related to the start and end of waiting in accordance with a job wait condition and messages related to endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E) are output.

retry

The automatic retry notification messages generated when a job ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-I) are 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)

  • Start or end of waiting in accordance with a wait condition, and endless waiting (KAVS4951-I, KAVS4956-I, and KAVS4971-E)

  • Automatic retry of a job that ends abnormally (KAVS4675-I, KAVS4676-I, KAVS4677-E, and KAVS4678-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

To Page Top

(64) "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

To Page Top

(65) "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

To Page Top

(66) "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.

To Page Top

(67) "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

To Page Top

(68) "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

To Page Top

(69) "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 generation information used as the basis for acquiring the status via 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

To Page Top

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

Use this parameter to specify the range of generation information to be used as the basis for acquiring the status via 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

To Page Top

(71) "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. When you restart a service in which an error has occurred, specify this value if you want the restarted service to inherit the status existing when the scheduler service terminated abnormally.

Default value

warm

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(72) "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

To Page Top

(73) "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

To Page Top

(74) "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

To Page Top

(75) "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

To Page Top

(76) "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

To Page Top

(77) "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.

To Page Top

(78) "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 and increase the maximum number of specifiable generations, the number of records obtained by multiplying the number of logs to keep by the number of registered units also increases. This greatly affects operations that access the database. Before you increase the maximum number of saved generations, you must divide the jobnets by, for example, reducing the number of records obtained as described above to reduce the size of each root jobnet. For details about the relationship between the number of logs to keep and performance, see 7.2 Relationship between number of logs to keep and performance in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

  • 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 dialog box 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 dialog box.

  • 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.

To Page Top

(79) "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

To Page Top

(80) "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

To Page Top

(81) "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

To Page Top

(82) "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 (for Windows) or 15.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 (for UNIX).

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

To Page Top

(83) "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

To Page Top

(84) "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:

Unless there are special circumstances, we recommend that you use the default value of 90 seconds.

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

To Page Top

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

Specify whether to issue a JP1 event when a command is executed or when an operation is performed from 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 when an operation is performed from JP1/AJS3 - View.

no

A JP1 event is not issued when a command is executed or when an operation is performed from 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

To Page Top

(86) "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.

To Page Top

(87) "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

To Page Top

(88) "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

To Page Top

(89) "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

To Page Top

(90) "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 total management method). 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 individual management method). 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

To Page Top

(91) "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.

To Page Top

(92) "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 spaces.

Default value

During a new installation and setup of JP1/AJS3, the following path is set:

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\database\schedule\AJSROOT1

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\database\schedule\AJSROOT1

  • For Windows Server 2003:

    JP1/AJS3-Manager-installation-folder\database\schedule\AJSROOT1

  • In UNIX:

    /var/opt/jp1ajs2/database/schedule/AJSROOT1

Recommended value

The value set at the time of installation or setup.

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.

  • This directory must be created 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.

    For this parameter, you cannot specify a directory mounted on an NFS file system or a similar file system connected to a network or a network drive.

To Page Top

(93) "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.

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

For users with administrator permissions or superuser permissions, set the update permission (rwx for UNIX) for this directory. For all users, 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 spaces.

Default value

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\sys\schedule\scheduler-service-name

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\sys\schedule\scheduler-service-name

  • For 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, create this directory newly.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(94) "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.

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

For all users, set the update permission (rwx for UNIX) for this directory.

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 spaces.

Default value

  • For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:

    %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name

    The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

    A folder protected by the system is the path to a folder in any of the following:

    - system-drive\Windows

    - system-drive\Program Files

    - system-drive\Program Files (x86) (for 64-bit Windows)

  • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:

    JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name

  • For 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, create this directory newly.

Recommended value

The value set at the time of installation or setup.

When the setting takes effect

When the scheduler service starts or terminates

To Page Top

(95) "PREWAITUSE" = "{yes|no}"

Use this parameter to specify whether to use wait conditions.

Specifiable values
yes

Wait conditions are used.

no

Wait conditions are not used.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Supplementary notes

  • If you want to change the setting from yes to no, cancel the registration of all units with wait conditions before you change the setting to no. Alternatively, cold-start the scheduler service after changing the setting to no.

  • Even if the setting is no, you can still define wait conditions. Note, however, that if you execute a unit with a wait condition, it will terminate abnormally.

  • If the database configuration of JP1/AJS3 is a compatible ISAM configuration, wait conditions cannot be used even if the setting is yes.

  • If the database configuration of JP1/AJS3 is a standard configuration or a standard configuration without ISAM, changing the setting to yes starts the flow control subprocess (ajsflbd).

To Page Top

(96) "PREWAITEXTEND" = "{none|condition}"

Use this parameter to extend the wait condition function. When the PREWAITUSE environment setting parameter is set to yes, specify for this parameter a value appropriate for the operating environment.

The setting of this parameter is ignored in the following cases:

Specifiable values
none

You can apply wait conditions to the following units:

Units capable of accepting wait conditions:

  • A root jobnet without start conditions and its lower-level units

  • Nested jobnet

  • A root jobnet directly under a planning group and its lower-level units

  • Standard job

  • Jobnet connector

  • Event job in a jobnet

  • Action job

  • Custom job

  • Passing information setting job

Units specifiable as a unit whose end is being waited for:

  • A root jobnet without start conditions and its lower-level units

  • Nested jobnet

  • Planning group

  • Lower-level units in root jobnet directly under planning group

  • Standard job

  • Jobnet connector

  • Event job in a jobnet

  • Action job

  • Custom job

  • Passing information setting job

For details, see Table 2-9 in 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

condition

In addition to the case in which none is set, you can apply wait conditions to the following units.

Units capable of accepting wait conditions:

  • Root jobnet with a start condition

Units specifiable as a unit whose end is being waited for:

  • Root jobnet with a start condition

For details, see Table 2-9 in 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Default value

none

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(97) "FLBDLOGSIZE" = dword:size-of-flow-control-subprocess-internal-log-file

Use this parameter to specify the size of an internal log file for a flow control subprocess.

You do not need to specify this parameter if wait conditions will not be used (the PREWAITUSE environment setting parameter is set to no).

Because this log file is used to check the execution status of units with wait conditions, specify a size large enough for storing the log data of at least one day. For details about how to estimate the file size, see 3.4.7 Estimating the size of log files output by a flow control subprocess in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

The two files whose size you specify here will be used as log files.

Specifiable values

A hexadecimal value (in kilobytes) from 0 to 1E8480 (0 to 2,000,000 in decimal)

If you specify a value from 0 to 3, a log file is not created.

Default value

dword:00002800 (10,240 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(98) "AGENTPROFMEMSIZE" = dword:memory-size-used-by-execution-agent-profile

Use this parameter to specify the size of memory that can be used by an execution agent profile.

If many units are specified in an execution agent profile, allocate only the amount of memory required for the execution agent profile. For details about how to estimate the size of memory used by an execution agent profile, see 3.2.1(2)(a) @SYS_RESTRICT_START.

The specified value needs to be added to the estimate for required memory.

If an attempt to allocate memory fails, an error message is output and the execution agent profile is not enabled.

Specifiable values

A hexadecimal value (in kilobytes) from 200 to 1400 (512 to 5,120 in decimal)

Default value

dword:00000200 (512 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

(99) "UNITPROFMEMSIZE" = dword: memory-size-used-by-unit-attribute-profile

Use this parameter to specify the size of memory that can be used by a unit-attribute profile.

If many units are specified in a unit-attribute profile, allocate only the amount of memory required for the unit-attribute profile. For details about how to estimate the size of memory used by a unit-attribute profile, see 3.2.2(2)(a) @SYS_PROFILE_START.

The specified value needs to be added to the estimate for required memory.

If an attempt to allocate memory fails, an error message is output and the unit-attribute profile is not enabled.

Specifiable values

A hexadecimal value (in kilobytes) from 80 to 500 (128 to 1,280 in decimal)

Default value

dword:00000080 (128 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the JP1/AJS3 service starts

To Page Top

(100) "UNITDEFDIVIDEUPDATE" = "{yes|no}"

Use this parameter to specify whether writing to a database during the following unit operations is to be divided into parts.

Specifiable values
yes

Writing to a database during unit operations is divided.

Division limits the consumption of an embedded database's exclusive resources to prevent a resource insufficiency.

no

Writing to a database during unit operations is not divided.

If a large number of units are operating at the same time, an embedded database's exclusive resources might become insufficient.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

  • If you have specified yes for this parameter, and an error occurs after unit information has been divided and written to the database, a unit whose unit information has been written up to the point of the error might be created or deleted. If an error occurs, restore the unit as described in the output message.

  • If the total number of units subject to operations by commands or from JP1/AJS3 - View or JP1/AJS2 - View satisfies the following expression, specify yes for the UNITDEFDIVIDEUPDATE environment setting parameter.

    (a + b + c + d) / 4 x 1.2 > 4,000

    a: (total-number-of-job-groups x 2) + total-number-of-the-calendar-definition-year-items-defined-in-job-groups

    b: (total-number-of-jobnets x 2) + total-number-of-the-schedule-rules-defined-in-all-jobnets

    c: total-number-of-jobs x 2

    d: total-number-of-relation-line-connections-defined-in-jobs-and-jobnets

To Page Top

(101) "EXECREGISTRATIONNUMBER" = "{calendar|execution}"

Use this parameter to specify whether the execution registration number is treated as a calendar date or an execution date.

Specifiable values
calendar

The execution registration number is treated as a calendar date (this is the behavior in 09-10 and earlier versions).

execution

The execution registration number is treated as an execution date.

If a base time has been set or if the system operates on a 48-hour cycle, specify execution to ensure that a temporary-change operation is re-executed correctly.

Default value

calendar

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary note

Do not change this parameter during operation. If you do so, the execution registration numbers in the temporary change information displayed in the JP1/AJS3 - View window or by using a command will no longer be consistent with the execution registration numbers held by JP1/AJS3. As a result, a temporary-change operation will not be re-executed correctly. If you change this parameter during operation, cold-start the scheduler service.

To Page Top

(102) "SAVEPLANINFO" = "{yes|no}"

Use this parameter to specify whether to use the temporary-change operation and management functionality. This functionality allows you to display temporary change information and re-execute temporary-change operations. For details about this functionality, see 4.5.16 Displaying and re-executing temporary change operations for a job or jobnet in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values
yes

The temporary-change operation and management functionality is used.

no

The temporary-change operation and management functionality is not used.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

  • If yes is specified for this parameter and the base time is not set to 0:00, or if dword:00000030 is set for the ROOTJOBNETSCHEDULERANGE environment setting parameter, change the value of the EXECREGISTRATIONNUMBER environment setting parameter to execution to ensure that temporary-change operations are re-executed correctly.

  • If you changed the parameter setting from yes to no during operation, cold-start the scheduler service. If you do not cold-start the scheduler service, the temporary change information file will not be deleted.

To Page Top

(103) "DEFLENTYPE" = "{byte|sjis}"

Use this parameter to specify whether the number of characters that can be specified for the following items in a UTF-8 environment should conform to the number of characters that can be specified in a Shift JIS environment.

This environment setting parameter is automatically set by executing the ajsembdbsetup command and cannot be changed by the jajs_config command.

For details, see 15.1.9 Setting for changing the number of characters specifiable for a unit name in a UTF-8 environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

Specifiable values
byte

The number of usable characters is the number of characters after conversion to the number of bytes in a UTF-8 environment.

sjis

The number of usable characters is the same as that in a Shift JIS environment.

Default value

byte

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Supplementary note

If you specify the -e byte option for the ajsembdbsetup command, byte is set. If you specify the -e sjis option, sjis is set. If you specify the -del option, byte is set.

To Page Top

(104) "RERUNSUBORDINATE" = "{yes|no}"

Use this parameter to specify whether to re-execute dependent units. Specify yes to allow dependent units to be re-executed.

For details about this functionality, see 4.5.11 Rerunning a job or jobnet in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.

Specifiable values
yes

A dependent unit can be re-executed.

no

A dependent unit cannot be re-executed.

Default value

no

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(105) "SERVICEMAXSESSION" = dword:maximum-allowable-number-of-simultaneous-sessions-for-each-scheduler-service

Use this parameter to specify the maximum allowable number of simultaneous sessions for JP1/AJS3 - View for each scheduler service. If you attempt to connect from JP1/AJS3 - View when the specified number has been reached, the attempt will fail.

Specify this environment setting parameter to restrict the number of connections for each scheduler service. To restrict the maximum allowable number of simultaneous sessions for JP1/AJS3 - View according to the host rather than according to the scheduler service, use the MAXSESSION environment setting parameter. When you use the SERVICEMAXSESSION environment setting parameter, note the following:

For example, if scheduler services AJSROOT1 and AJSROOT2 have been created and the setting value of the MAXSESSION environment setting parameter is 50 (default value), and the setting value of the SERVICEMAXSESSION environment setting parameter for AJSROOT1 is 25, you must specify 25 or a smaller value for the SERVICEMAXSESSION environment setting parameter for AJSROOT2.

Specifiable values

A hexadecimal value from 00000000 to 00000080 (0 to 128 in decimal)

If you specify dword:00000000, JP1/AJS3 - View cannot be connected.

Default value

None.

If you do not set a value, no restrictions on the maximum allowable number of simultaneous sessions for a scheduler service are applied. Therefore, the maximum allowable number of simultaneous sessions for JP1/AJS3 - View will depend on the MAXSESSION environment setting parameter.

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

Cautionary notes

  • Specify the SERVICEMAXSESSION environment setting parameter for all scheduler services. If this environment setting parameter is set for only some scheduler services on the same logical host or same physical hosts, but not for others, a message (KAVS1014-W) is output at scheduler service startup.

  • If the maximum allowable number of simultaneous sessions has been exceeded, a message (KAVV452-E) is displayed in the JP1/AJS3 - View window (Summary Monitor window) for each monitored unit that is unable to establish a connection. This message is displayed whenever the window is updated.

  • To disable the SERVICEMAXSESSION environment setting parameter, delete the definition key by using the jbsunsetcnf command, and then reset the other environment setting parameters of the deleted definition key. Before performing this operation, back up the definition beforehand by using the jbsgetcnf command.

To Page Top

(106) "DEFAULTPRIORITY" = dword:default-execution-priority-of-a-job

Specify the default execution priority to be used if the execution priority of a job and of all upper-level jobnets is set to None.

For details about the job execution priority, see 2.1.4(2) Execution priority in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide. For details about the value specified for the execution priority of jobs, see 7.8.2 Notes on the execution priority of jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Specifiable values

A hexadecimal value from 1 to 3 (1 to 3 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

When the scheduler service starts

This setting does not apply to jobs for which the execution start processing has begun and for which the job status is Waiting to execute, Now queuing, or Now running.

Supplementary note

If you specify an execution priority that is higher than that of other processes, a job process started from JP1/AJS3 might use a large portion of the CPU, thus affecting other processes. For this reason, you cannot specify 4 or 5 for the DEFAULTPRIORITY environment setting parameter. If it is necessary to specify an execution priority of 4 or 5 for a certain job, carefully consider the system environment and the manner in which operations are performed, and then specify the execution priority of the job in the job definition.

To Page Top

(107) "AJSPRINTSORTUNITINF" = "{yes|no}"

Use this parameter to determine whether to fix the order of relation line information entries that are output when the ajsprint command is executed with the -f or -a option specified. If the -f option is specified, each entry of relation line information is output as the value represented by the %ar format indicator. If the -a option is specified, each entry of relation line information is output as the ar parameter.

If the ajsprint command is executed without specifying the -s option, the command uses the AJSPRINTSORTUNITINF environment setting parameter instead of the -s option.

If the values of the -s option and the AJSPRINTSORTUNITINF environment setting parameter are different, the -s option takes precedence over the parameter.

For details about the ajsprint command, see ajsprint in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Specifiable values
yes

Fixes the output order of relation line information entries for units. If yes is specified, the following rules apply when relation line information entries are output:

  1. Entries are output in ascending order of the character codes of the preceding unit names.

  2. Entries whose preceding units are the same are output in ascending order of character codes of the succeeding unit names.

no

Does not fix the output order of relation line information entries for units. If no is specified, the output order of relation line entries depends on the unit creation order.

Default value

no

Recommended value

yes

When the setting takes effect

When the scheduler service starts

To Page Top

(108) "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).

In the following cases, you do not need to estimate or change the value of this environment setting parameter:

If execution sequence control for different scheduler services is used, you must determine the value to be specified for GWMAXCONNECTION environment setting parameter by using the method for estimating the maximum number of concurrent connections for physical and logical hosts. If the maximum number of concurrent connections exceeds the specified value, the process that controls communication between scheduler services might fail to communicate.

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 value determined by using the method for estimating the maximum number of concurrent connections

When the setting takes effect

When the JP1/AJS3 service starts

Supplementary note

To estimate the maximum number of concurrent connections for physical and logical hosts, follow the procedure described below.

If the estimated value is less than 10, you do not need to change the default value.

  1. For all scheduler services configured on the host, list the jobnet connectors and connection-destination jobnets for which Other service is specified for Connection range.

    These jobnets are those for which the letter y is output when the ajsprint command with the format indicator %Ce specified for the -f option is executed. For the command syntax, see ajsprint in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

  2. Count the number of connection destination hosts. Count jobnet connectors and connection-destination jobnets listed in 1. that have the same value for Host to connect as a single host.

    To output the value of Host to connect, execute the ajsprint command with the format indicator %Ch specified for the -f option.

  3. Calculate the maximum number of concurrent connections by using the following formula:

    2 x number-of-connection-destination-hosts-counted-in-2.

To Page Top

(109) "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

To Page Top

(110) "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

To Page Top

Trademarks

Copyright (C) 2012, 2014, Hitachi, Ltd.

Copyright (C) 2012, 2014, Hitachi Solutions, Ltd.