Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Troubleshooting


2.12.2 Procedure for re-creating the execution environment database for QUEUE jobs and submit jobs

To re-create the database used by the execution environment for QUEUE jobs and submit jobs:

  1. Make sure that the JP1/AJS3 service is not running.

  2. Use the jpqexport command to back up the definition of the execution environment for QUEUE jobs and submit jobs.

    In Windows:

    jpqexport [-mh logical-host-name] -dt isam -co jpqsetup.conf#

    In UNIX:

    /opt/jp1ajs2/bin/jpqexport [-mh logical-host-name] -dt isam -co jpqsetup.conf#

    Although you can use any file name, for management purposes, we recommend that you use jpqsetup.conf.

    #

    Specify -mh logical-host-name to match the operating environment.

    Depending on how an ISAM file is corrupted, attempts by the jpqexport command to access the file might result in an error. If you created a backup of the configuration definition file for the execution environment for QUEUE jobs and submit jobs (jpqsetup.conf), use it. If you do not have a backup, see jpqimport in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2, and create the configuration definition file for the execution environment for QUEUE jobs and submit jobs.

  3. Delete the files and temporary files in the database storage directory for the execution environment for QUEUE jobs and submit jobs.

    In Windows:

    del execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs\*#1

    del work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing\M_JPQ*#2

    In UNIX:

    rm execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs/*#1

    rm work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing/M_JPQ*#2

    #1

    For execution-environment-database-storage-directory-for-QUEUE-jobs-and-submit-jobs, specify the folder specified in the DatabasePath environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Database] definition key. For details about the DatabasePath environment setting parameter, see 2.3.2(3) DatabasePath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

    #2

    For work-directory-when-execution-environment-manager-process-for-QUEUE-jobs-and-submit-jobs-is-executing, specify the folder specified in the WorkPath environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1NBQMANAGER\Process] definition key. For details about the WorkPath environment setting parameter, see 2.3.2(1) WorkPath in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

  4. Use the jpqimport command to re-create the ISAM files by using the file you backed up in step 2 as the execution environment definition for QUEUE jobs and submit jobs.

    In Windows:

    jpqimport [-mh logical-host-name] -dt isam -ci jpqsetup.conf#

    In UNIX:

    /opt/jp1ajs2/bin/jpqimport [-mh logical-host-name] -dt isam -ci jpqsetup.conf#

    #

    Specify -mh logical-host-name to match the operating environment.

  5. Check the messages that are output when you execute the jpqimport command, and check whether the ISAM files are created successfully.

    If the jpqimport command did not terminate normally, you will not be able to start the JP1/AJS3 service. If you are unsure as to whether the command was executed successfully, use the jpqexport command as described in step 2 to output the definition again. Then check whether the agent definition and queue definition in the definition output before re-creation of the ISAM files matches those in the definition after re-creation.

  6. Restart the JP1/AJS3 service.

For details about the jpqexport and jpqimport commands, see 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2 or 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.

For details about the jbsgetcnf command, see the Job Management Partner 1/Base User's Guide.