9.2 Notes on JP1/AJS3 host settings

Note the following points when setting up hosts to run JP1/AJS3:

• Use JP1/AJS3 only in an environment where the IP address can be resolved from the local host name; otherwise; JP1/AJS3 will fail to start.

• If the character encoding used by the system is EUC and the character string displayed in the command execution result contains Japanese characters, the displayed execution result might be misaligned.

• If you execute a command using a character encoding different from that of the JP1/AJS3 service, depending on the command executed, messages in both character encodings will be output to the integrated trace log.

• Do not use disks mounted on file systems that are distributed over a network (such as an NFS) to store the files and directories to be created or referenced by JP1/AJS3. If you use such disks, JP1/AJS3 might not work properly. However, files and directories that are used only for the definition parameters of the following jobs can be stored on disks mounted on file systems that are distributed over a network (such as an NFS):

  • Execution file name for the job

  • Standard output file name for the job

  • Standard error output file name for the job

  • Environment file name for the job

  • File to transfer name for the job

  • Destination file name for the job

  • Work path for the job

  • Work directory for job environment settings

  • Home directory of the execution OS user

  If the network cannot be accessed while you are using the above definition parameters, job execution might fail or be delayed.

• If the OS of the host on which JP1/AJS3 operates is UNIX, NIS (Network Information Service) cannot be used for operation.

• If the OS of the host on which JP1/AJS3 operates is UNIX, do not start the JP1/AJS3 service or execute commands in an execution environment for which the ulimit or limit command was used to set the upper limit for the CPU time or file size. If the upper limit of the CPU time or file size is set, any processes exceeding the set upper limit will end abnormally, causing such phenomena as the stop of the JP1/AJS3 service.

• If the OS of the host on which JP1/AJS3 operates is UNIX, do not use the ulimit command to set the stack size to a value smaller than the system default.

  JP1/AJS3 only operates under the condition where the stack size is at least as large as the system default size. Therefore, if you set the stack size to a size that is smaller than the system default size, any of the following problems might occur, preventing JP1/AJS3 from operating correctly:

  • The job fails to start or ends due to abnormal detection, and thus cannot be executed.

  • The job cannot be forcibly terminated.

  • The JP1/AJS3 service does not start.

• If the OS of the host on which JP1/AJS3 operates is UNIX, do not change run level when the JP1/AJS3 service is running. In addition, do not execute rc script or inittab when the JP1/AJS3 service is running.

  JP1/AJS3 uses the rc script to initialize the embedded database. Therefore, if you change the run level or start inittab processing while JP1/AJS3 is operating, the processes of JP1/AJS3 terminate abnormally.

• If the OS of the host on which JP1/AJS3 operates is Solaris, in the PATH environment variable settings, do not specify /usr/ucb before specifying /usr/bin. If you specify /usr/ucb before specifying /usr/bin, JP1/AJS3 might stop functioning properly because the system assumes that commands used internally by JP1/AJS3 are in the /usr/bin directory.

• In accordance with the format specified in the RFC2609 standards, use only the following types of characters for the host name of the host to be installed:

  • Alphabetic characters (A to Z, a to z)

  • Numbers (0 to 9)^#1

  • Hyphen (-)^#2

  • Period (.)^#3

  #1

  Do not use a number directly after the last period.

  #2

  Do not use a hyphen for the first or last character of the host name.

  #3

  Do not use a period for the first or last character of the host name.

To Page Top