9.5.1 Notes when using JP1/AJS3 for x86 in a WOW64 environment

This subsection gives cautionary notes on using JP1/AJS3 for x86 in Windows on Windows 64 (hereafter, WOW64) environmentsof Windows.

When a 32-bit application is executed in a WOW64 environment, calls to the file system are redirected from %systemroot%^#\system32 to %systemroot%\syswow64, and access requests to the registries HKEY_LOCAL_MACHINE\Software and HKEY_CLASS_ROOT are redirected to HKEY_LOCAL_MACHINE\Software\SysWow64 or elsewhere. That is, the operating system isolates 32-bit applications from 64-bit applications, and prevents file and registry collisions.

#: %systemroot% is an environment variable that points to the directory in which the Windows system is installed. The default setting is C:\WINDOWS.

Because JP1/AJS3 for x86 environments is a 32-bit application, calls are redirected as described above. This redirection causes the problems described in the following table.

Table 9‒2: Problems JP1/AJS3 can cause in a WOW64 environment
Problem	Affected functionality	Problem details
Even if a 64-bit program under `%systemroot%\system32` is specified as an executable file, the program cannot start.	PC job (include Queueless job), QUEUE job that runs under Windows, or flexible job	Even if a file under `%systemroot%\system32` is specified as the executable file for a PC job or a QUEUE job to run on Windows, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the job fails to start or ends abnormally if no compatible 32-bit file is found under `%systemroot%\syswow64`. For a PC job, the following problems might occur: Problem 1: The message KAVU4550-W is output to the integrated trace log, and the job fails to start. This message might appear, for example, when the backup utility in the system tools (`ntbackup`) is executed. Problem 2: The message `This` `application` `has` `failed` `to` `start` `because` `netman.dll` `was` `not` `found.` is output to the Windows event log, and the job ends abnormally with return code `128`. This message might appear, for example, when the `ipconfig` command in the system tools is executed.
	`jp1exec` command	When an executable file under `%systemroot%\system32` is specified in the `jp1exec` command, the command fails to start and the job that executed the command ends abnormally.
	JP1/AJS3 - View tool execution	When an executable file under `%systemroot%\system32` is registered with the command for starting a JP1/AJS3 - View tool, the command fails to start the tool.^#
Files under `%systemroot%\system32` can neither be referenced nor updated.	Monitoring Files job	If a file under `%systemroot%\system32` is specified as a monitoring-target file^# and the file is updated, monitoring access to the monitoring-target file under `%systemroot%\system32` is redirected to `%systemroot%\syswow64`. Therefore, no event is detected, and the job remains in the running state.
	Monitoring Log Files job	If a log file under `%systemroot%\system32` is specified as a monitoring-target log file^# and the log file is updated, monitoring access to the monitoring-target log file under `%systemroot%\system32` is redirected to `%systemroot%\syswow64`. Therefore, no event is detected, and the job remains in the running state.
	Judgment job	Even if a file under `%systemroot%\system32` is specified as the judgment condition, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the files under `%systemroot%\system32` cannot be judged, and dependent units are not executed.
	Standard input file for a PC job	Even if a file under `%systemroot%\system32` is specified as the standard input file for a PC job, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the standard input file cannot be found, and the job fails to start.
	Standard output file for a PC job	Even if a file under `%systemroot%\system32` is specified as the standard output file for a PC job, access to the file is redirected to `%systemroot%\syswow64`. Therefore, if JP1/AJS3 starts a 64-bit program, the program can neither reference nor update the standard output file. If, however, JP1/AJS3 starts a 32-bit program, the program can reference and update the standard output file.
	Standard error output file for a PC job	Even if a file under `%systemroot%\system32` is specified as the standard error output file for a PC job, access to the file is redirected to `%systemroot%\syswow64`. Therefore, if JP1/AJS3 starts a 64-bit program, the program can neither reference nor update the standard error output file. If, however, JP1/AJS3 starts a 32-bit program, the program can reference and update the standard error output file.
	Transfer source file for a PC job	Even if a file under `%systemroot%\system32` is specified as the transfer-source file for a PC job, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the transfer-source file cannot be found, and the job fails to start.
	Transfer destination file for a PC job	Even if a file under `%systemroot%\system32` is specified as the transfer-destination file for a PC job, access to the file is redirected to `%systemroot%\syswow64`. Therefore, if JP1/AJS3 starts a 64-bit program, the program can neither reference nor update the transfer-destination file. If, however, JP1/AJS3 starts a 32-bit program, the program can reference and update the transfer-destination file.
	Command	Even if a file under `%systemroot%\system32` is specified as the file for command input or output, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the specified file can neither be referenced nor updated.
	Environment settings	Even if a file under `%systemroot%\system32` is specified in the environment settings, access to the file is redirected to `%systemroot%\syswow64`. Therefore, the specified file can neither be referenced nor updated.

#: In the Files dialog box, you cannot specify a file under %systemroot%\system32.

To prevent these problems, take the following actions:

Do not specify files under %systemroot%\system32 as files to be referenced or updated by JP1/AJS3.
Specify the files under %systemroot%\sysnative instead of files under %systemroot%\system32.

To Page Top