The independent DBH can be terminated by means of the DAL commands:
CLOSE RUN-UNITS:
Normal termination of the DBHCLOSE CALLS:
Fast normal termination of the DBH%TERM:
Immediate abortion of the DBH
Normal termination of the DBH
Example
UDSADM statement:
01 //EXECUTE-DAL-CMD CMD=CLOSE RUN-UNITS
Messages:
% UDS0220 UDS RECEIVED COMMAND: CLOSE RUN-UNITS (OPOX073,09:35:23/4TUC)
02 % UDS0241 UDS TERMINATION INITIATED ON TRANSACTION (OPCF024,09:35:23/4TUC)
% UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:35:23/4TUC)
03 % UDS0241 UDS TERMINATION INITIATED ON SERVERTASK (OPO0024,09:35:29/4TUC)
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (OPCC758,09:35:30/4TUC)
4TUC: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TUC: ------------------------------------------------------------------------
4TUC: CUSTOMER 6 68 37 23 23
04 % UDS0213 UDS NORMAL SYSTEM TERMINATION WITH ***************7 DML-STATEMENTS 2019-01-29 09:35:30 (OPOB033,09:35:30/4TUC)
01 | The DAL command:
starts the normal termination procedure. |
02 | No more transactions are permitted. |
03 | Once all transactions have been terminated, the master task terminates all server tasks. |
04 | Once all server tasks have been terminated, the master task invalidates the session log file (SLF), deletes the temporary realms and deletes the RLOG files that belong to this configuration name and that are logically empty. |
Note on UDS-D/openUTM
CLOSE RUN-UNITS is rejected if there are still secondary subtransactions or openUTM transactions in the PTC state.
The database administrator can nonetheless terminate the DBH normally, provided the PTC state is terminated first (see section “Terminating the PTC state”).
Fast normal termination of the DBH
Example:
UDSADM statement:
01 //EXECUTE-DAL-CMD CMD=CLOSE CALLS
Messages:
% UDS0220 UDS RECEIVED COMMAND: CLOSE CALLS (OPOX073,09:29:54/4TMW)
% UDS0241 UDS TERMINATION INITIATED ON TRANSACTION (OPCF024,09:29:54/4TMW)
02 % UDS0348 UDS CANCEL ALL TRANSACTIONS STARTED (OPC1035,09:29:54/4TMW)
% UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:29:54/4TMW)
03 % UDS0241 UDS TERMINATION INITIATED ON SERVERTASK (OPO0024,09:30:00/4TMW)
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (OPCC758,09:30:01/4TMW)
4TMW: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TMW: ------------------------------------------------------------------------
4TMW: SHIPPING 1 88 58 24 24
4TMW: CUSTOMER 0 35 22 8 8
04 % UDS0213 UDS NORMAL SYSTEM TERMINATION WITH ***************1 DML-STATEMENTS 2019-01-29
09:30:01 (OPOB033,09:30:01/4TMW)
01 | The DAL command:
accelerates termination of the DBH. |
02 | FINISH WITH CANCEL is enforced upon all uncompleted transactions, i.e. all changes made during these transactions are rolled back with the aid of the associated before-image files. The DBH passes status code 122 or 151 to application programs whose transactions were aborted with FINISH WITH CANCEL. |
03 | The master task then attempts to terminate the DBH normally. |
04 | The session is not held to be terminated until the master task has deleted the contents of the SLF. |
Note on UDS-D/openUTM
CLOSE CALLS is rejected if there are still secondary subtransactions or openUTM transactions in the PTC condition.
The database administrator can nonetheless terminate the DBH normally, provided the PTC state is terminated first (see section “Terminating the PTC state”).
Immediate abortion of the DBH
Example
UDSADM statement:
01 //EXECUTE-DAL-CMD %TERM
Messages:
% IDA0N51 PROGRAM INTERRUPT AT LOCATION '0003AD70 (SCCDUMP), (CDUMP), CODE=UDS'
02 % IDA0N53 DUMP BEING PROCESSED. PLEASE HOLD ON
% IDA0N54 'USERDUMP' WRITTEN TO FILE '$XXXXXXX.DUMP.DBH.4TMW.00006'
% IDA0N55 TITLE: 'TSN-4TMW UID-XXXXXXX AC#-Z1285 USERDUMP PC-00034D98 EC-50 VERS-120 DUMP-TIME 2019-01-29 09:30:01'
% UDS0220 UDS RECEIVED COMMAND: %TERM (OPOX073,09:30:01/4TMW)
03 % UDS0202 UDS ABNORMAL SYSTEM TERMINATION WITH **************23 DML-STATEMENTS 2019-01-29 09:30:01 (OPY8003,09:30:01/4TMW)
% EXC0732 ABNORMAL PROGRAM TERMINATION. ERROR CODE 'NRT0101': /HELP-MSG NRT0101
01 | The DAL command:
dispenses with the normal termination activities of the DBH and terminates the session by the shortest route (emergency halt). |
02 | The DBH places a memory dump of its main memory area in the file DUMP.jobname.tsn.nnnnn (when PP DUMP=ALL) or SYS.ADUMP.jobname.tsn.nnnnn (when PP DUMP=STD). |
03 | The master task aborts the session; the databases of the DB configuration are marked as inconsistent if updates have been performed since the last consistency point. The interrupted session can be resumed by means of a session restart. The session is not held to be terminated until the SLF or its contents have been deleted. |