This command applies only to Linux. You cannot use this command in Windows.
If an attempt to start the JP1/AJS3 CSA Web Application Server service fails, stop processing of this service might be performed within the command, causing the KNBB2524-E message to be displayed together with the KNBB2525-E message. In this case, no action is required for the KNBB2525-E message.

If you execute this command with this option omitted, startup processing is performed for the JP1/AJS3 CSA Web Application Server, and then for the JP1/AJS3 CSA HTTP Server. If an error occurs in the JP1/AJS3 CSA HTTP Server service during startup, the JP1/AJS3 CSA Web Application Server service is still running. The following table lists the services in which an error has occurred and the status of each service.

Table 7‒3: Services in which an error occurred and the service status
Service status	Service in which an error has occurred
Service status	JP1/AJS3 CSA Web Application Server	JP1/AJS3 CSA HTTP Server
Status of JP1/AJS3 CSA Web Application Server	Stop	Running
Status of JP1/AJS3 CSA HTTP Server	Stop	Stop

If an attempt is made to start the JP1 /AJS3 CSA HTTP Server service while it is already running, the KNBB2524-E message is displayed, and the command terminates abnormally.
By default, the JP1/AJS3 CSA HTTP Server service is started by the user privilege with the user ID nobody and the group ownership root. If an attempt to start the service fails with the KNBB2524-E message displayed, check if the nobody user exists in the system. If the nobody user does not exist, create that user, or open the setting file /opt/jp1ajs3csa/uCPSB/httpsd/conf/httpsd.conf in a text editor and specify that user and group ownership for the User and Group lines.
```
User nobody
Group root
```