Get messages after running DDUPDATE 1000 APPLYCXX to add a KEY dynamically. Where are they documented?

Document ID : KB000014231
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

I ran DDUPDATE 1000 APPLYCXX to add a KEY dynamically.

I'm getting messages and like to know more about their meaning.

Question:

Can you tell me more about the process and what messages to expect?

Environment:
z/OS CA Datacom 15.x
Answer:

When you run that 1000 APPLYCXX to add/delete a key , a process ***DBKEY starts in the MUF and when that process completes the new key gets a status LD (see CXX report) and can be used by the applications. 

 

When that process starts , you see message DB02814I with STARTED in the text .

From your MUF : DB02814I - DYNAMIC INDEX ADD STARTED FOR KEY EQTK7 BASE 60 TBL EQT.

 

When the process ends , you get this message with ENDED instead of STARTED .

 

Other messages that are possible are :

 

 

DB02815I

DYNAMIC INDEX fff aaa

Reason:

The asynchronous index work that is associated with an APPLYCXX add or delete request was interrupted. The fff is either ADD or DELETE. If aaa is ABORTED BY EOJ, it was interrupted by a MUF EOJ request. If aaa is REQUEST ABORTED, it was interrupted by a REQABORT request.

Action:

None. The index work that is required to process the APPLYCXX delete request is rescheduled when the first URT is opened against the affected table.

 

DB02816E

DYNAMIC INDEX fff UNEXPECTED RETURN CODE cc(iii)

Reason:

The message details database errors that were encountered during the asynchronous index work that is associated with an APPLYCXX delete or add request. The fff is the function, either ADD or DELETE. The cc is the return code, and iii is the internal return code.

Action:

Determine what caused the return code and correct it. The required index work to process the APPLYCXX delete or add request is rescheduled when the first URT is opened against the affected table.

 

 

Note that when you reqabort the process , cancel the MUF or just EOJ , this ***DBKEY starts again when this base gets opened again . 

Additional Information:

See the online documentation on dynamically adding/deleting keys here