|
WORKQ
|
Defines the number of requests that can be on the platform server request queue at any one time.
The default value of
100 is typically too small for anything but a test system. You must specify a value larger than the total amount of locally initiated and remotely initiated transfers. This includes transfers that are being executed, inactive and in a hold state.
For example, the following statement allocates up to 5000 file transfer requests at any one time.
//STEP1 EXEC PGM=OSSERVER,PARM='WORKQ=5000'
|
|
PROFILEQ
|
Defines the number of user profile entries that can fit into the platform server user profile dataspace.
The default value of
4000 is sufficient for most systems and fits within a single cylinder on most DASD volumes.
For example, the following statement allocates dataspace for up to 6000 user profile entries.
//STEP1 EXEC PGM=OSSERVER,PARM='WORKQ=5000,PROFILEQ=6000'
|
|
DNIACTQ
|
Defines the number of DNIACT entries that can fit into the platform server dataspace.
The default value of
2000 entries is sufficient for most systems.
For example, the following statement allocates dataspace for up to 20000 DNIACT entries.
//STEP1 EXEC PGM=OSSERVER,PARM='WORKQ=1000,DNIACTQ=10000'
|
|
DNICFGQ
|
Defines the number of DNI configuration entries that can fit into the internal DNICFG dataspace.
The default value of
1000 means that 1000 DNI config members can be activated.
For example, the following statement defines 20000 DNI config members can be activated.
//STEP1 EXEC PGM=OSSERVER,PARM='WORKQ=1000,DNICFGQ=20000'
|
|
SSLDEBUG
|
Defines whether SSL debugging is turned on at startup.
The valid values are:
-
NO: SSL debugging is not turned on. This is the default value.
- YES: SSL debugging is turned on.
-
HIGH: detailed SSL debugging is turned on.
The
SSLDEBUG operator command can be used to turn on or turn off SSL debugging. For example, the following statement turns on SSL HIGH debugging at startup.
//STEP1 EXEC PGM=OSSERVER,PARM='SSLDEBUG=HIGH'
|
|
START
|
Defines whether the platform server WORKQ is initialized at startup.
The valid values are:
-
WARM: the WORKQ is not initialized at startup. Date in the WORKQ is retained and processed by the platform server.
-
COLD: the WORKQ is initialized at startup. All information in the WORKQ is lost. This option should only be used in severe situations where the platform server started task cannot be brought up because the WORKQ has been corrupted.
For example, the following statement WARM start the platform server WORKQ.
//STEP1 EXEC PGM=OSSERVER,PARM='START=WARM'
|
