Operation

Starting Natural for Db2 for zIIP

Issue the following MVS console start command to start the NDZ Server: 

START NDZ STARTED TASK NAME

Stopping Natural for Db2 for zIIP

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

This section covers the following topics:

NDZ Server Commands

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:

D CLI - Display clients

This command lists the clients that are currently connected to the NDZ Server in the STDOUT file. The output message has the following format: 

---------------------------------------------
yyyy-MM-dd hh:mm:ss LIST OF CLIENTS CONNECTED
---------------------------------------------
 CLIENT#  JOBNAME  JOBID    USERID   PROGRAM 
  cli#  name   job id user   prog.
---------------------------------------------
yyyy-MM-dd hh:mm:ss END OF LIST              
---------------------------------------------

Where:

  • CLIENT# = The client slot which this client occupies. Client numbers are in the interval between 1 and the value of CLIENTS parameter in the NDZ Parameter module.

  • 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.

P CLI=CLIENT NUMBER – Stop client

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:

  1. Identify the Job ID of the client job.

  2. Issue the D CLI modify command to list all clients that are connected to the NDZ Server.

  3. Check the CLIENT# and JOBID columns to identify the client number of the job.

  4. Issue the P CLI=client number modify command, where client number is the value from the CLIENT# column.