1.2 Notes on using the commands
This section provides a list of notes when you use the commands.
You must open a command prompt as an administrator if you want to execute any command that requires Administrator permissions on a Windows Server host. You can open a command prompt as an administrator by right-clicking Command Prompt in the Start menu of Windows and then selecting Run as administrator. However, if the User Account Control (UAC) feature is disabled, you do not have to open a command prompt as the administrator.
When the JP1/AO server OS is Windows, if you enable QuickEdit Mode in a command prompt and then click the command prompt window, the window output is suspended until you disable the QuickEdit mode. For this reason, we recommend that you do not use the QuickEdit mode.
If you want to use a command in a cluster environment, run the command in the executing host. However, note that you can run the hcmds64getlogs command in the standby host.
If you want to suspend the execution of a command, press the Ctrl+C keys. After the command is suspended, check the suspension message for any problem. If you want to resume the command, then execute it again.
Do not press the Ctrl+S keys while a command is being executed. If you do so, the command output is stopped.
You cannot execute any commands other than the stoptask and submittask commands with other JP1/AO commands at the same time.
You might get a return value other than 2 (The command execution has been interrupted) depending on the type of the command when you interrupt the command immediately after its execution.
You can execute a maximum of 10 instances respectively for the stoptask and submittask command at the same time. If you attempt to execute the 11th instance, the following message appears and the task is not executed:
KNAE03236-E No more commands can be executed at the moment. Wait until one or more currently executing commands end, and then try again.
When you execute the following commands, you can change the subject identification information that will be output to the audit log by changing the user-specified properties file (config_user.properties) settings:
deleteremoteconnection command
deleteservicetemplate command
importservicetemplate command
listremoteconnections command
listservices command
listtasks command
setremoteconnection command
stoptask command
submittask command
When the JP1/AO server OS is Linux, if the maximum size of a core file when it is output is set to 0 in the standard setting, a core dump is not generated. To generate a core dump when an error occurs, execute the ulimit command to set the maximum size to unlimited before executing any command.
If the JP1/AO server OS is Windows, the specified file path is not case sensitive. If the JP1/AO server OS is Linux, the specified file path is case sensitive.