13.3 Notes on local actions

• Do not use perform the OS shutdown command (e.g. shutdown or halt) from a local action.

• The commands below cannot be executed as local action functions.

  • Commands requiring interactive operations

  • Commands that display a screen

  • Commands accompanied with escape sequences or control codes

  • Commands through which a daemon is not terminated

  • Commands requiring interaction with the desktop such as the Windows message mechanism or DDE (for Windows)

  • Commands for which data is input from the standard input

• The result of the command output to the KNAM3208-I message can be a maximum of 4095 bytes, including message text. Control characters are replaced with single-byte spaces when the characters appear in the output result.

• Only processes that were started by JP1/Base are forcibly terminated when an action that is running is canceled in Windows.

• Some commands executed by an action might remain if JP1/Base is stopped when the system load is high (e.g. when the CPU utilization is high or there are not enough user ports). To avoid such a situation, do the following when using a local action function:

  • Decrease the number of commands that can be simultaneously executed to reduce the load of the local action function.

  • Make sure actions do not establish further action conditions.

  • Avoid executing batch files where many commands are executed by one action.

• The service (jbslcact process) of a local action function connects to an event service during startup. A pause status is entered if the service cannot establish a connection. For operation using a cluster system, therefore, an event service must be started prior to the JP1/Base service.

• An event handled as a local action is an event registered after a local action function is started. An event registered during local action startup or a local action pause, or during a failover is not treated as an object.

• For local actions, execute the command using the following processing:

  • For Windows:

    Execute cmd.exe /c execution-command from the local action.

  • For UNIX:

    Using the OS user login shell, execute, for example, /bin/sh -c execution-command (if the login shell is /bin/sh) from the local action.

    If /sbin/false, /bin/false, /bin/true, /sbin/nologin, or the like is set as the login shell, execution cannot be performed normally.

    Furthermore, OS user passwords are not recognized, and therefore account locks and the like are not recognized.

To Page Top