Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 2 Configuring the Accesses to Adabas Data : Startup of the Server

Startup of the Server
To start the server, bring up the Native Execution Environment using the startup parameters described in Supplying the Startup Parameters.
When you start the server, you are connected to both Adabas and TIBCO Object Service Broker. When the Execution Environment requests an access to Adabas data, a thread to Adabas is established.
Because a separate Execution Environment is not required for each server, you can combine the parameters for the server with other parameters.
Using the MODIFY Operator Command
When you have an instance running, use the MODIFY operator command from the z/OS operator console to dynamically:
Increasing the Number of Server Tasks
If the number of server tasks is insufficient to process transaction requests, unsatisfied requests raise a SERVERBUSY exception and are queued until a free server is available. You can dynamically increase the number of tasks without restarting the Execution Environment by using a MODIFY operator command of the form:
MODIFY ee_jobname,STARTNUMSERVER=nn,TYPE=ADA
where
The number of new server tasks to start. This number can be from 1 to a value less than or equal to the value set in the Maximum Connection Count field in your Network Configuration.
Setting the Maximum Number of Tasks
Use the following MODIFY operator command to dynamically set the maximum number of tasks available in a particular Execution Environment:
MODIFY ee_jobname,SETNUMSERVER=nn,TYPE=ADA
where
The maximum number of tasks available for a particular Execution Environment. This number can be from 1 to a value less than or equal to the value set in the Maximum Connection Count field in your Network Configuration.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved