Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Base User's Guide


L.2 Setting up an environment in which JP1/Base administrators can use JP1/Base

The JP1/Base system administrator needs to perform the following tasks to allow JP1/Base administrators to operate JP1/Base:

Organization of this subsection

(1) Additional setup tasks for specific functionality

In an environment where JP1/Base administrators can use JP1/Base, additional setup is required before JP1/Base administrators can use the functionality below. These tasks must be performed by the JP1/Base system administrator.

(a) Setting shared directories for logical hosts, output destinations for operation log data, and directories used by event services

To allow JP1/Base administrators use of shared directories for logical hosts, output destinations for operation log data, and the directories used by the event service, JP1/Base administrators must be given access to all higher-level directories. Assign read and execute permission in the others category for all higher-level directories of the following directories:

  • Shared directory for each logical host

  • Output destination for operations log data (if the location was changed from the default)

  • Any directories other than default specified in the event server index file (index)

(b) Setup for executing ISAM-related utility commands

Change the umask value of ISAM-related utility commands to 002.

(2) Stopping operation by JP1/Base administrators

To stop JP1/Base administrators from using JP1/Base:

  1. Back up JP1/Base setup information and the event database.

    For details on how to back up the setup information and event database, see 3.5.3(1) Backing up JP1/Base setup information and 3.5.3(2) Backing up an event database.

  2. Uninstall JP1/Base.

    For details on how to uninstall JP1/Base, see 3.3.3 Uninstalling JP1/Base. Delete any JP1/Base files remaining in the installation folder after the uninstallation process.

  3. Perform a new installation of JP1/Base.

  4. Restore the JP1/Base setup information.

    For details on how to recover setup information, see 3.5.3(3) Recovering JP1/Base setup information.

    To keep an environment in which JP1/Base administrators are unable to use JP1/Base, you need to recover the setup information in such a manner that the backed up permissions, ownership, and group settings of the definition files are not restored, and the settings of the new installation in step 3 are kept.

  5. Restore the event database.

    For details on how to recover the event database, see 3.5.3(4) Recovering an event database.

    After recovering the event database, execute the following commands to change the owner, access permissions, and group of the database files:

    cd /var/opt/jp1base/sys/event/servers/default# or cd shared-directory/event#

    chmod 644 ./IMEvent*.*

    In HP-UX: chown root:sys ./IMEvent*.*

    In Solaris or Linux: chown root:root ./IMEvent*.*

    In AIX: chown root:system ./IMEvent*.*

    #: If you specified a different path for the event server directory in the event server index file (index), specify that path instead.

(3) Backup and recovery in environments where JP1/Base administrators can use JP1/Base

To back up and recover JP1/Base settings in an environment where JP1/Base administrators can use JP1/Base:

  1. Back up JP1/Base setup information and the event database.

    For details on how to back up the setup information and event database, see 3.5.3(1) Backing up JP1/Base setup information and 3.5.3(2) Backing up an event database.

  2. Recover the setup information and event database.

    For details on how to recover the setup information and event database, see 3.5.3(3) Recovering JP1/Base setup information and 3.5.3(4) Recovering an event database.

  3. Enable the setting that allows JP1/Base administrators to perform operations.

    Execute the jbssetadmingrp command to set up an environment in which JP1/Base administrators can use JP1/Base. Use the same name and gid for the JP1 administrators group as the host on which the backup was created.