ajsembdbreclaim

Format

ajsembdbreclaim
      -m {manager|
          scheduler [-F scheduler-service-name]|
          agent}
      [-mh logical-host-name]
      [-t {d|f}]
      [-r {1|2}]

ajsembdbreclaim
      -m manager
      [-mh logical-host-name]
      -t f
      -r 2

ajsembdbreclaim
      -m manager
      [-mh logical-host-name]
      -t d
      -r 2

ajsembdbreclaim
      -m manager
      [-mh logical-host-name]
      -t f
      -r 1

ajsembdbreclaim
      -m manager
      [-mh logical-host-name]
      -t d
      -r 1

ajsembdbreclaim
      -m scheduler
      [-F scheduler-service-name]
      [-mh logical-host-name]
      -t f
      -r 2

ajsembdbreclaim
      -m scheduler
      [-F scheduler-service-name]
      [-mh logical-host-name]
      -t d
      -r 2

ajsembdbreclaim
      -m scheduler
      [-F scheduler-service-name]
      [-mh logical-host-name]
      -t f
      -r 1

ajsembdbreclaim
      -m scheduler
      [-F scheduler-service-name]
      [-mh logical-host-name]
      -t d
      -r 1

ajsembdbreclaim
      -m agent
      [-mh logical-host-name]
      -t f
      -r 2

ajsembdbreclaim
      -m agent
      [-mh logical-host-name]
      -t d
      -r 2

ajsembdbreclaim
      -m agent
      [-mh logical-host-name]
     -t f
      -r 1

ajsembdbreclaim
      -m agent
      [-mh logical-host-name]
      -t d
      -r 1

To Page Top

Description

Maintains the areas in the embedded database used by JP1/AJS3.

You can execute this command only when the embedded database is running. You can execute the command regardless of the operating status of JP1/AJS3.

To Page Top

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

To Page Top

Storage directory

In Windows:

JP1/AJS3 - Manager-installation-folder\tools\

In UNIX:

/opt/jp1ajs2/tools/

To Page Top

Arguments

To Page Top

Notes

• This command is implemented by a script. If you specify an excessively long character string or an invalid character string or value for an option, an unexpected error might occur. You must use the number of characters allowed for a character string or a value in the option as specified in the DBMS and JP1/AJS3 specifications.

• If either of the following conditions is met, a timeout error might occur for the ajsembdbreclaim command:

  • When the job execution load of a job or jobnet is high

  • When a unit is operated by using a command or in JP1/AJS3 - View

  • When the usage states of scheduler services or the delay states of jobnets with start conditions are aggregated from the Web GUI (Management Portal)

  If a timeout error occurs, re-execute the ajsembdbreclaim command when none of the preceding cases applies.

• If a failure such as a communication or disk failure occurs during execution of this command, the command might not respond. If the non-responding command cannot be killed manually (for example, when a job is automatically executed from another job), you can specify the embedded database system common definition pd_utl_exec_time to kill the command. For details about pd_utl_exec_time, see the system common definition in the 23.1.1 Examining the embedded-database operating environment and operating method in the JP1/Automatic Job Management System 3 Configuration Guide.

• If multiple ajsembdbreclaim commands are executed concurrently for a single embedded database, one of the commands might abnormally terminate and the message KFPA11770-I will be displayed. In this case, no action is needed if any one of the commands is executed successfully. Note that if multiple ajsembdbreclaim commands are executed concurrently for a single embedded database, a conflict might occur during log output processing, and the following message might be output between lines in the output result:

  The process cannot access the file. The file is being used by another process.

  You can ignore this message because there are no problems with the output results.

• If you execute the ajsembdbreclaim command in a state in which large quantities of unavailable areas occur in the database because maintenance has not been performed for a long time, a lot of data is sent to the system log. An embedded database terminates abnormally if the system log capacity is insufficient. Therefore, estimate the required system log capacity and, if the log capacity is insufficient, add a system log and then execute the ajsembdbreclaim command. For details about how to check the unavailable area and the system log capacity required for execution of the ajsembdbreclaim command, see 9.1.1 Analyzing the database area in the JP1/Automatic Job Management System 3 Administration Guide.

• When -m manager is specified for the ajsembdbreclaim command and the command is executed, even if the KAVS2117-E message is output, maintenance processing other than the maintenance processing of the scheduler service that detects an abnormality will continue. For the maintenance processing of the scheduler service that detected the abnormality, remove the cause of the problem, and then execute the ajsembdbreclaim command again if necessary.

• Do not execute the ajsembdbreclaim command at the same time with maintenance performed by the automatic maintenance function.

To Page Top

Return values

To Page Top

Actions to be taken if an error occurs

If a command error occurs, take the indicated action in the following table.

To Page Top