Issue the following MVS console start command to start the NDZ Server:
START NDZ STARTED TASK NAME
Issue the following MVS console stop command to stop the NDZ Server:
STOP NDZ STARTED TASK NAME
NDZ will perform the shutdown process after the last client disconnects. The following
message displays in the MVS console if there are clients connected to the NDZ Server when
the STOP command is issued:
NDZMAIN Stop requested. Waiting for clients to finish
To force NDZ termination despite the connected clients, add the F option to the stop command. Example:
STOP NDZ STARTED TASK NAME F
NDZ displays the following message in the console and performs the shutdown process:
NDZMAIN Forced stop requested
Use the MVS console modify command to issue commands to the NDZ Server:
MODIFY NDZ STARTED TASK NAME,COMMAND PARAMETER1, PARAMETER2, ...
NDZ Servers accept the following commands:
The D CLI modify command lists the clients that are currently connected to the NDZ Server. The output message has the following format:
---------------------------------------------
NDZ CLIENTS REPORT
CURRENT DATE AND TIME 18.06.2024 11:31:32.54
MAXIMUM NUMBER OF CLIENTS ALLOWED 4
NUMBER OF CONNECTED CLIENTS 3
CLIENT JOB NAME JOB ID USER ID PROGRAM LIBRARY
1 NDZDS1K1 J0208314 USER NDZDS1K1 NDZ1
2 NDZDS1K2 J0208315 USER NDZDS1K2 NDZ2
3 NDZDS1K3 J0208316 USER NDZDS1K3 NDZ3
---------------------------------------------
Where:
| Report Item | Explanation |
|---|---|
| CLIENT | The client slot which the current client occupies. Client numbers are in the interval between 1 and the value of ndz.maxClients parameter in the ndz.properties file. |
| JOBNAME | The name of the client's job. |
| JOBID | The ID of the client's job. |
| USERID | The User ID that is associated with the client job. |
| PROGRAM | The name of the Natural program that the client is executing at the moment. |
| LIBRARY | Natural Library where the program is present. |
The D CPU modify command displays CPU utilization report at the moment and the workload distribution.
--------------------------------------------- NDZ CPU UTILIZATION STATISTICS (SECONDS) CURRENT DATE AND TIME 18.06.2024 11:25:17.20 GENERAL PROCESSORS: 5 ZIIPS: 1 NORMALIZ. FACTOR: 13.51 NUMBER OF EXCPS 1548481 TOTAL TIME ON GP (EXCL. ZIIP ELIGIBLE) 0.48% 0.241684 TCB TIME ON GP 0.45% 0.227081 SRB TIME ON GP 0.03% 0.014456 ENCLAVE SRB TIME ON GP 0.00% 0.000147 ZIIP ELIGIBLE TIME ON GP 0.64% 0.318578 TOTAL TIME ON ZIIP (NORMALIZED) 98.88% 49.360806 TCB TIME ON ZIIP 98.88% 49.360543 ENCLAVE SRB TIME ON ZIIP 0.00% 0.000263 TOTAL CPU TIME 100.00% 49.921068 ---------------------------------------------
| Report Item | Explanation |
|---|---|
| GENERAL PROCESSORS | The number of GPs running under your z/OS system. |
| ZIIPS | The zIIP normalization factor indicates the ratio of zIIP to GP speed. |
| NORMALIZ.FACTOR |
This factor tells you how fast your zIIP runs compared to a throttled GP with reduced power. In the example above, the value of 13.51 means that one zIIP is about 13.5 times faster than one GP. |
| NUMBER OF EXCPS | This EXCP number refers to the number of I/O signals. |
| TOTAL TIME ON GP (EXCL. ZIIP ELIGIBLE) | The total GP time consumed within the NDZ WLM enclave. |
| TCB TIME ON GP | The GP time consumed within the TCB execution. |
| SRB TIME ON GP | The GP time consumed within the SRB execution. |
| ENCLAVE SRB TIME ON GP | The GP time consumed within the NDZ WLM enclave SRB. |
| ZIIP ELIGIBLE TIME ON GP |
The CPU time within the NDZ WLM enclave on the GP qualified for zIIP but not used by it. A non-zero value means that zIIP-eligible workload could not be offloaded because no zIIP was available. |
| TOTAL TIME ON ZIIP (NORMALIZED) | The total zIIP time consumed within the NDZ WLM enclave. |
| TCB TIME ON ZIIP | The zIIP time consumed within the TCB execution. |
| ENCLAVE SRB TIME ON ZIIP | The zIIP time consumed within the NDZ WLM enclave SRB. |
| TOTAL CPU TIME | The total CPU time (GP plus zIIP) consumed. |
The R modify command reloads the static profiles cache from directory specified in the ndz.staticPath. This command can be used to reload the static profile when the property ‘ndz.automaticProfileReload’ is set to false. The command output is shown in STDOUT as below.
[2024-06-18 09:33:18 GMT] Static Profiles reloaded
Release a client slot that is held by a non-executing client job.
Important:
This command SHOULD NOT be used to cancel the
execution of NDZ client jobs that are currently executing. Please use the appropriate
MVS or JES2 command instead if you need to cancel a job. Using this command on a job
that is currently in execution can lead to unexpected results including, but not limited
to, loss of uncommitted data.
If a NDZ client job abnormally terminates or is cancelled, it usually disconnects from NDZ and releases the client slot it was occupying automatically. If the client job doesn't disconnect automatically, you can issue this command to release the client slot that is currently held by the job that is no longer running. To release a client slot:
Identify the Job ID of the client job.
Issue the D CLI modify command to list all clients that
are connected to the NDZ Server.
Check the CLIENT# and JOBID columns to identify the client number of the job.
Issue the P CLI=client number
modify command, where client number is the
value from the CLIENT# column.