Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Configuration) Guide


4.5.4 JP1/AJS3 commands that can be executed from JP1/AJS3 - View

You can execute JP1/AJS3 commands not only from the manager host but also from JP1/AJS3 - View. Executing JP1/AJS3 commands from JP1/AJS3 - View allows you to collect the operating status and job definition information for JP1/AJS3 - Manager without logging in to the manager host. Before executing JP1/AJS3 commands from JP1/AJS3 - View, you need to determine some items and specify settings. This subsection describes points to consider when executing JP1/AJS3 commands from JP1/AJS3 - View.

Organization of this subsection

(1) JP1/AJS3 commands for which execution from JP1/AJS3 - View is permitted

The following table lists the JP1/AJS3 commands executable from JP1/AJS3 - View.

Table 4‒11: JP1/AJS3 commands executable from JP1/AJS3 - View

No.

Command

Description

1

ajslogprint

Extracts and outputs information from the scheduler log.

2

ajsprint

Outputs the definition of a unit.

3

ajsshow

Outputs information about a unit, including the execution history, current status, and next scheduled execution.

4

ajsstatus

Outputs the operating environment of the scheduler service.

Use JP1/AJS3 - Manager to specify which of the above JP1/AJS3 commands are commands that JP1/AJS3 - View users are permitted to execute. Based on your operation needs, consider which JP1/AJS3 commands require permission to be executed from JP1/AJS3 - View.

For details about commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(2) JP1 users permitted to execute JP1/AJS3 commands

Consider which JP1 users should be permitted to execute which JP1/AJS3 commands. JP1/AJS3 commands to be executed from JP1/AJS3 - View must be defined in advance in an executable command settings file (jajsExecutableCommand) on the manager host. Creating this executable command settings file allows JP1/AJS3 commands to be executed from JP1/AJS3 - View. Depending on where the executable command settings file is stored, the settings in the file apply to all JP1 users or to an individual user.

The following figure shows how to store the executable command settings file.

Figure 4‒5: Storing the executable command settings file

[Figure]

If both the files for individual JP1 users and the common file for all JP1 users are stored, the files for individual JP1 users have precedence. The following figures show examples of setting executable command settings files.

Figure 4‒6: Example of setting executable command settings files (if a common file for all JP1 users has not been created)

[Figure]

Figure 4‒7: Example of setting executable command settings files (if a common file for all JP1 users has been created)

[Figure]

Cautionary note

If many JP1 users are permitted to execute JP1/AJS3 commands, multiple users might execute commands at the same time. This might increase the load on the manager host and affect JP1/AJS3 operations. Therefore, we recommend that you examine each JP1 user, and then specify commands for which execution from JP1/AJS3 - View is permitted.

For details about how to set executable command settings files, see 11.1.1 Types of customization methods in the JP1/Automatic Job Management System 3 Operator's Guide.

(3) JP1 user permissions

JP1/AJS3 commands are executed (from JP1/AJS3 - View) under the JP1 user's permissions that were used when the user logged in to the manager host from JP1/AJS3 - View. Therefore, confirm that the JP1 users who want to execute JP1/AJS3 commands from JP1/AJS3 - View have the permissions necessary to execute those commands.

For details about permissions necessary for executing JP1/AJS3 commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

(4) JP1/AJS3 commands to be registered

To execute JP1/AJS3 commands from JP1/AJS3 - View, you need to register command arguments and execution-result output destinations in advance in JP1/AJS3 - View.

Registered information can be shared with other JP1 users by using a common user profile. Therefore, we recommend the following operation: First, the system administrator registers command arguments and execution-result output destinations, and then uploads the common user profile to the JP1/AJS3 - Manager host. Next, JP1 users download the common user profile.

Do not use wildcard characters or the -R option to specify a unit name. If you use them, many units are subject to processing and command execution might take a long time. If you need to use wildcard characters or the -R option, also use the -E, -L, or -T option to narrow down the target units.

For details about how to register commands, see 10.4.1 Registering JP1/AJS3 commands in the JP1/Automatic Job Management System 3 Operator's Guide.