DBUTLTY LOCK OPTION=HOTCOPY DFDSS backup

Products

• Datacom/DB
• Datacom
• DATACOM - AD
• Datacom/AD

Issue/Introduction

Running Datacom DBUTLTY with:

LOCK OPTION=HOTCOPY,DBID=nnn

This is done before a DFDSS backup and will be in effect until an UNLOCK is run,

Will this stop batch jobs and CICS transactions from starting? Will they have to wait until the UNLOCK? 

How can you monitor what DBIDs have a LOCK set?

Environment

Release: 15.1

Resolution

New batch jobs and CICS transactions will be able to run and update the database while the LOCK OPTION=HOTCOPY is in effect.

They will not wait to start until the UNLOCK is performed.

The LOCK OPTION=HOTCOPY does the following:

• Any Index Area and data area buffers with pending writes are written to DASD.
• Delay rows being moved by an update command to a row in a compressed table having its physical size changed.
• Delay if rows are moved by system tools ONLINE_TABLE_MOVE (TM24), Block size Alter 24x7 (BA24), and DBUTLTY function OLREORG.
• Delay if rows being added that cross a 64k track boundary and MUF protects the rows to speed physical retrieval of empty blocks. There is no way to know how many rows can be added at the time this boundary is reached. A DSNTYPE=BASIC type file is limited to 64k tracks on one volume. For DSNTYPE=LARGE will allow up to 16,383K tracks per volume.
  So the 64k boundary will only occur if files are allocated as DSNTYPE=LARGE.
• Delay if rows being added require that the data area be extended.

To monitor what DBIDs have a LOCK set use the following SQL command:

SELECT MUF_NAME, LOCK_VALUE FROM sysadm.MUF_LOCKS_VALUE 
     WHERE SUBSTR(LOCK_VALUE,1,6) = 'DBSMVR'; 

 

Additional Information

See Datacom documentation section Creating Copies of Databases and Data Areas and LOCK (Lock a Database with OPTION=HOTCOPY)

Article 47123 COMM STATUS not displaying LOCKs