casstart [/res-name] [/oconfig-name][/uusername] [/ppassword] [/cgroup] [/w] [/s:start-type] [/mhost:port]
| /res-name | Name of the enterprise server to start. Defaults to ESDEMO |
| /oconfig-name | When using this option in MSS-enabled regions, config-name should be the name of a SIT. The region starts up using the specified SIT rather than the one defined in the Enterprise Server Administration pages. |
| /uuserid | An authorized user. This user must exist within the security domains of both the enterprise server and
Micro Focus Directory Server. That is, the security configuration for both enterprise server and Directory Server must be able to verify
the user credentials supplied. Note that enterprise server and Directory Server may be using different security managers.
It might be necessary that the user is defined in more than one security repository.
In order to update Directory Server status information, within the Directory Server domain, the user must have modify permission on the appropriate enterprise server resource within the Servers resource class. In order to successfully run the casstart command, within the enterprise server's security domain, the user must have alter permissions on the casstart resource within the OPERCMDS resource class. Exception: This parameter is only required if you have configured security.
|
| /ppassword | The password for the user |
| /cgroup | The sign-on group for the user. By default, when a user requests access to a resource, some external security managers only
apply rules that refer to that user and the user's current sign-on group.
If this option is not specified, the user is signed on with a default group as determined by the security manager. |
| /w |
Introduces a delay to the end of the startup process, to enable other essential processes for the region to start before control is passed to the user. It prevents the casstart process from exiting until the region has either started or the delay expires. Omitting this parameter means that casstart can exit before the region is ready to accept requests. [2] |
| /s:start-type | Where
start-type can be
w for warm or
c for cold. This option is used to start enterprise server instances that are part of a PAC. Only the first enterprise server
instance started in a PAC can be cold started.
Note: It is not mandatory to cold start the first enterprise server in a PAC.
The remaining enterprise server instances that are part of the PAC should be performed as warm starts. See
Starting a PAC for more information.
Note:
|
| /mhost:port | Enables you to specify the host and port that casstart should look for an MFDS service on, where the default host and port (localhost:86 or 127.0.0.1:86) is not the port the target MFDS service is bound to. |
Comments:
On UNIX you can use a dash (-) before an option as an alternative to a forward slash (/).
The command line utilities casstart, casstop, casfile, casout, and cassub can be invoked by a program using the call interface and passing the command line parameters to the call. For instance, you could use the following to start a server:
01 ws-cmd-parms. 05 ws-cmd-len pic x(02) comp-x. 05 ws-cmd-value pic x(1024). ...... ...... ...... *> Start up the Server move 1 to ws-cmd-len move low-values to ws-cmd-value string "-rMyRegion" delimited by size " -uSYSAD -pSYSAD /w" delimited by size into ws-cmd-value with pointer ws-cmd-len end-string subtract 1 from ws-cmd-len call 'casstart' using ws-cmd-parms end-call ...... ......When used on platforms that support running both 32-bit and 64-bit applications, casstart checks its environment to determine whether to start the enterprise server in 32-bit or 64-bit mode. If the server's working mode (as specified when it was created) does not match the mode specified by the environment, casstart fails and issues an appropriate message. On UNIX platforms, you choose the mode by setting the COBMODE environment variable to 32 or 64 as appropriate. On Windows platforms, you can choose the environment by choosing the relevant command prompt from the Start menu.
You can only invoke the casstart command from the command line or from the Micro Focus Directory Server (MFDS); it cannot be invoked, for example, from a batch job.