Tech Tip: CA Datacom Core Products Version 15.1 Additional Enhancements provided via PTF RO92259/AREA_EXTENT_TRACKING

Document created by KarinaPulinx Employee on Nov 29, 2016Last modified by KarinaPulinx Employee on Nov 30, 2016
Version 2Show Document
  • View in full screen mode

Tech Tip from Karina Pulinx, Principal Support Engineer for November 29, 2016.

 

This is another in the series of tips for CA Datacom Core Products Version 15.1 enhancement PTF RO92259.

RO92259 delivers 10 new features.

 

One of these new features is Multi-User startup and console command AREA_EXTENT_TRACKING.

The AREA_EXTENT_TRACKING n option defines the level or quantity of messages requested by the database administrator.

The message currently works for data areas and occurs in MUF but not in DBUTLTY or any single user.

 

The n drives the quantity of messages.

 

.Set as 999, a message is generated for every extent of every area first block use. This is the number of potential extents from the back to the front.

As a database administrator, you will typically use this setting when you begin testing.

.Set to 1 to drive the message when the last potential extent first block usage is to drive the message.

.Set to 2 to drive the message when the second to last potential extent first block usage is to drive the message.

 

Example

 

An area defined as SPACE=((CYL,(100,50)),VOL=SER=(SYSDA,8) has 128 potential extents.

 

The following DB02827W message occurs, as requested, at the time the first block of an extent is used initially.

This is a high-water mark or a maximum usage. The DB02827W message has variable numbers that will soon be documented in DocOps.ca.com.

 

DB02827W - AREA_EXTENT_TRACKING dbid area-name STARTING EXTENT 8 REMAINING 0 EXPECTED 8

Attachments

    Outcomes