8.1 Checking definitions before live JP1/AJS3 operation
JP1/AJS3 allows you to check whether job definitions are valid before you deploy them, to prevent failures in a production environment.
The following figure shows the sequence of operations involved in a definition pre-check, up to the point when you begin live operation.
|
Use the ajschkdef command to run a definition pre-check. When you execute the ajschkdef command, the check results are output to the pre-check result file. You can see the results of the pre-check by viewing the file. The pre-check result file is output to the following location by default:
- In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:
-
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajscheckfile.txt
The default location of %ALLUSERSPROFILE% is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86)
- In Windows, if the installation folder is other than the above:
-
JP1/AJS3 - Manager-installation-folder\log\ajscheckfile.txt
- In UNIX:
-
/var/opt/jp1ajs2/log/ajscheckfile.txt
For details on the ajschkdef command, see ajschkdef in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
Before you run a definition pre-check, you must set up the definition pre-check function. For details on how to set up the function and its environment, see 6.5.1 Setting up the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows systems) or 15.5.1 Setting up the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX systems).
- Organization of this section