9.3 Notes on the JP1/AJS3 database

Note the following points in regard to the JP1/AJS3 database:

• High-priority processes (the JP1/AJS3 scheduler services) can monopolize the CPU, causing JP1/AJS3 processing performance to decline. However, setting a lower priority for the JP1/AJS3 scheduler services, and a higher priority for the ajsmonsvr process and commands that operate on units, can also cause start delays in jobs and jobnets. When executing commands for operating on units, make sure you use them in an environment where they have the same priority as the scheduler services.

  This can be more of an issue in UNIX, depending on the set of nice values. Note the following in regard to the nice value at process startup:

  • When executing a command that operates on units

    Execute the command with the same nice value as the JP1/AJS3 service.

  • When executing, as a JP1/AJS3 job, a command that operates on a unit (including a command that operates on a unit and is executed within a script specified as a job)

    Change the jobnet's Priority parameter from the default (None) to 3. If you start the JP1/AJS3 service with a nice value of 20, +20 applies to the default setting of None and corresponds to a nice value of 39 (the capped maximum), resulting in the lowest job priority. With a setting of 3, however, +0 applies and corresponds to a nice value of 20. This means that the job will be executed with the same nice value as the JP1/AJS3 service, and is less likely to monopolize the CPU.

• When the configuration of the JP1/AJS3 - Manager database is the standard configuration, the system can operate for a very long time as long as the ajsembdbreclaim command is executed periodically. If the system is changed significantly (if you delete or cancel registration of a large-scale jobnet, for example), check the number of unused segments by executing the ajsembdbstatus command. When the data storage rate decreases after prolonged system operation, a message is output to the Windows event log or syslog. If necessary, reorganize the database. For details about the output messages, see 5.2.1 How to check the database usage in the JP1/Automatic Job Management System 3 Administration Guide.

• For the items below, consecutive single-byte space characters placed at the end of the line might become invalid. Do not enter any spaces after a comment.

  • Comment of unit definition

  • Comment of release

  • Description of execution agent group

  • Description of execution agent

To Page Top