csccompostart (Starting HCSC components)
Format
csccompostart [-h]
-user login-user-ID
-pass login-password
{-csc HCSC-server-name|-cluster cluster-name}
{-name service-ID|reception-ID|-all
|-namelist file-name-specifying-HCSC-components}
[-nogc]
Function
Starts HCSC components.
By setting up default values for mandatory options, such as the login user ID, in the HCSC-Manager command definition file, you can omit the specification of these values in this command.
For details on how to use this command, see the following locations in the Service Platform System Setup and Operation Guide according to the purpose of use:
Arguments
-h
Displays the usage of commands. When you specify this option, all other options are ignored even if specified.
-user login-user-ID ~ <one-byte alphanumeric characters and underscores (_)> ((1 to 16 characters))
Specifies the user ID that is used to log in to HCSC-Manager.
-pass login-password ~ <one-byte alphanumeric characters and underscores (_)> ((1 to 16 characters))
Specifies the password that is used to log in to HCSC-Manager.
-csc HCSC-server-name ~ <one-byte alphanumeric characters and underscores (_)> ((1 to 8 characters))
Specifies the HCSC server name of the HCSC components to be started.
-cluster cluster-name ~ <one-byte alphanumeric characters and underscores (_)> ((1 to 8 characters))
Specifies the name of the cluster where the HCSC components will be started in a batch. An error occurs if you specify the -cluster option when the cluster type is HA.
-name service-ID|reception-ID ~ <one-byte alphanumeric characters and underscores (_)> ((1 to 8 characters))
Specifies the service ID or reception ID of the HCSC components to be started. When you specify this option along with the -cluster option, all the HCSC components with the same service ID within the cluster will start.
-all
Starts all the stopped HCSC components within the specified range. When you specify this option along with the -csc option, all the stopped HCSC components within the specified HCSC server will start. When you specify this option along with the -cluster option, all the stopped HCSC components within the specified cluster will start.
The following table lists the order in which the HCSC components are started when you specify this option. If an error occurs during processing, the start processing will stop even if all the HCSC components are not started.
Starting order | Types of HCSC components | Starting order within HCSC components |
---|---|---|
1 | Service adapters | Ascending order of service IDs |
2 | Business processes | Ascending order of business process names |
3 | User-defined receptions | Ascending order of business process names and reception IDs |
-namelist file-name-specifying-HCSC-components ~ ((1 to 200 bytes))
Uses the HCSC component-specification file to specify the HCSC components to be started. Specify this file with an absolute or relative path. If the file does not exist, the command ends abnormally. For details on the HCSC component-specification file, see HCSC component-specification file.
Note that the HCSC components are started in the same order as that described for the -all option.
-nogc
Starts the components without generating Full GC. However, the specification of this option does not control Full GC generated automatically by JavaVM or Full GC issued by an abnormal J2EE server processing.
Execute the javagc command to explicitly generate Full GC when an HCSC component starts. For details on the javagc command, see javagc (Forced garbage collection) in the manual uCosminexus Application Server Command Reference Guide.
Examples of input
csccompostart -user admin -pass admin -csc HCSC -name BP1
csccompostart -user admin -pass admin -csc HCSC -all
csccompostart -user admin -pass admin -cluster Cluster -name BP1
csccompostart -user admin -pass admin -cluster Cluster -all
csccompostart -user admin -pass admin -csc CSCSrv1 -name BP1 -nogc
csccompostart -user admin -pass admin -csc CSCSrv1 -namelist hcsccomponent.txt
Return values
Return value | Meaning |
---|---|
0 | The command terminated normally. |
1 | The command terminated abnormally. |
2 | A communication timeout occurred. |
3 | An exclusion error occurred. |
9 | An error occurred when checking the execution permission. |
Notes