jajs_log.bat or _04.bat

Organization of this page

Format
Function
Permissions for execution
Command stored in:
Arguments
Notes
Return values
Messages
Example

Format

jajs_log.bat | _04.bat
     [-f storage-folder]
     [-t]
     [-u]

To Page Top

Function

These commands acquire maintenance information, such as various JP1/AJS3 - Definition Assistant logs and OS information.

_04.bat is the data collection tool for JP1/AJS3 - Definition Assistant 10-00 and earlier. In JP1/AJS3 - Definition Assistant 10-50 and later, you can also use jajs_log.bat as a data collection tool.

Both data collection tools have the same basic functions. Use either one of these based on the usage and if customization is necessary.

The following table shows the usage and customizability of jajs_log.bat and _04.bat.

Table 7‒4: Usage and customizability of the data collection tools
Data collection tool	Usage	Customizable
`jajs_log.bat`	Used if you have not changed the log output destination or if you do not need to collect other information.	N
`_04.bat`	Customized and used if you have changed the log output destination or if you will collect other information.^#	Y

Legend:

Y: Can customize the data collection tool.

N: Cannot customize the data collection tool.

#

For details about how to customize the tool, see the manual JP1/Automatic Job Management System 3 Configuration Guide.

By default, the data collection tool execution result is output to the following folders under %TEMP%\jp1ajs2\backlog:

JP1_DEFAULT\JP1_DEFAULT_1st

Data for the first report is output.
JP1_DEFAULT\JP1_DEFAULT_2nd

Data for the second report is output.
JP1_DEFAULT\JP1_DEFAULT_3rd

Other data is output.

To Page Top

Permissions for execution

Administrators group permissions

To Page Top

Command stored in:

For jajs_log.bat: JP1/AJS3 - Definition-Assistant-installation-folder\tools
For _04.bat: JP1/AJS3 - Definition-Assistant-installation-folder\tools

To Page Top

Arguments

`-f` `storage-folder`

Specify the name of the folder to output the collected data to using the absolute path or the relative path from the location where the command is executed. However, you cannot specify directly under the drive.

If the path includes a blank space, surround the path in double quotation marks ("") to specify the blank space.

If you specify a folder that does not exist, a new folder is created using that name.

If there is already collected data in the specified storage folder, a message will be displayed to confirm you want to overwrite the file.

If you omit this option, the data is output to %TEMP%\jp1ajs2\backlog. If you specify this option, this option's value is prioritized more than if you changed the storage folder through customization.

`-t`

Specify this option when you are not acquiring the hosts or services file.

To Page Top

Notes

If you execute this command while the JP1/AJS3 service is running, the job may end abnormally. Therefore, the tool does not collect data from the ISAM database.
If you collect data from the logical host of the cluster configuration, execute this command on the host where the logical host is operating.
This tool does not compress the collected data. Compress it using a separate compression tool.
If the file that outputs the batch file execution result is completed, a message is output to confirm the overwriting of information. To overwrite the file, respond with y, and to cancel, respond with n.
When a batch file is executed, an error message that says Sharing Violation may be displayed for files in the installation-folder-of-JP1/AJS3 - Manager-or-JP1/AJS3 - Agent\sys folder. However, this is not a problem.
Directly after you execute the data collection tool, if you operate, such as move or delete, the collected data, a message may be output that says, The process cannot access the file because it is being used by another process. This is output because the process for internally collecting the OS information is still operating, even if the data collection tool is terminated. If this message is output, wait a while and then operate the data.
If you are using Outlook, when you execute the data collection tool, the following message dialog box may be displayed:
```
A program is trying to access e-mail addresses you have stored in Outlook. Do you want to allow this?
```
This is due to the operation of the machine configuration information collection program (msinfo32) executed within the data collection tool. There is no problem with the data collection tool or with Outlook.

The data collection tool does not collect email addresses. Click the No button on the message dialog box.
If you execute the data collection tool, you must start the command prompt as the administrator. If you do not start the command prompt as the administrator, the UAC feature's confirmation dialog box is displayed numerous times while the data collection tool is operating. You do not have to start the command prompt as the administrator if the UAC feature is disabled.
Do not execute multiple instances of the data collection tool.

To Page Top

Return values

`0`	Ended normally.
Value other than `0`	Ended abnormally.

To Page Top

Messages

Message	Explanation	Operation
`Finished.` `Press` `any` `key.`	Processing ended normally. Press any key.	Waits for a response from the user.
`Failed.` `Press` `any` `key.`	Processing did not end normally. Press any key. See any messages output by the OS, remove the cause of the error, and then re-execute the command.	Waits for a response from the user.
`File` `file-name` `is` `exist.` `Delete` `to` `continue?` `(y/n)`	The file created last time still exists. To delete it and continue processing, press y, to cancel, press n.	Waits for a response from the user.
`Directory` `directory-name` `is` `exist.` `Delete` `to` `continue?` `(y/n)`	The directory created last time still exists. To delete it and continue processing, press y, to cancel, press n.	Waits for a response from the user.
`Error` `exist` `in` `option.`	There is a mistake in the option specification. Specify the correct option and execute the command again.	Processing ends.
`The` `collection` `of` `detailed` `information` `on` `EmbedDB_JF*`^# `begins.`	Begins collection of the detailed information of the embedded database.	Processing continues.
`The` `collection` `of` `detailed` `information` `on` `EmbedDB_JF*`^# `ended.`	Ends collection of the detailed information of the embedded database.	Processing continues.
`The` `collection` `of` `detailed` `information` `on` `JP1/Base` `begins.`	Begins collection of the detailed information of JP1/Base.	Processing continues.
`The` `collection` `of` `detailed` `information` `on` `JP1/Base` `ended.`	Ends collection the detailed information of JP1/Base.	Processing continues.
`The` `collection` `of` `Event` `Log` `in` `text` `format` `begins.`	Begins collection of the event log in text format.	Processing continues.
`The` `collection` `of` `Event` `Log` `in` `text` `format` `ended.`	Ends collection of the event log in text format.	Processing continues.

#: _JF* is the identifier (_JF0, _JF1, _JF2, ...) for the embedded database. This command collects the detailed information for each identifier.

To Page Top

Example

In this example, the command collects data from the physical host.

jajs_log.bat
or
_04.bat

To Page Top