Processing, DBUTLTY and SQL Messages › CA Datacom/DB Processing Messages (DB0xxxxc) › DB00319I

DB00319I

In the message LXX DYNAMIC EXTEND - X, one of the following text strings replace the ‘X’. Each is a specific condition in error and needs its action.

LXX DYNAMIC EXTEND - DELAY NEXT, FIRST WRAP

Reason:

The message occurs if the LXX was successfully extended with extra space and new log records caused the LXX to be at its wrap point. However, this is the first wrap of the MUF execution and the additional space needs to be at least at the second wrap.

Action:

None. The message is informational only. The extend completion is checked again at the next wrap point.

LXX DYNAMIC EXTEND - DELAY NEXT, LBSN BUSY

Reason:

This message occurs if the LXX was successfully extended with extra space and new log records caused the LXX to be at its wrap point. However, current log activity does not allow the extend to complete successfully at this time. It is checked at the next and all succeeding wrap points. The LBSN BUSY refers to an active request or active transaction that still has requirements of the LXX being large enough to include the active request or active transaction.

Action:

None. The message is informational only. The extend completion is checked again at the next wrap point.

LXX DYNAMIC EXTEND - DELAY UNTIL WRAP POINT

Reason:

This message occurs if the following situations occur:

• The log (LXX) was set to DYNAMIC_EXTEND and more space was added successfully
• MUF opens the LXX and sees a dynamic extend has been done. However, the additional space has not yet been accepted into the normal processing.

The delay is done when the LXX is next required to wrap from the physical back area to the beginning.

Action:

None. The message is informational only.

LXX DYNAMIC EXTEND - REJECT BECAUSE PREVIOUS

Reason:

A DYNAMIC_EXTEND is being requested for the LXX. However, it has previously been subject to a dynamic extend and that space has not yet been accepted into the normal processing.

Action:

Allow a previous extend to be accepted by adding more log records. When more log records have been added to the point of the prior extend space being reported as COMPLETE, request an extra dynamic extend.

LXX DYNAMIC EXTEND - REJECT BECAUSE HAS SHADOW

Reason:

This informational message occurs if a DYNAMIC_EXTEND is being requested for the LXX but the MUF currently has a Shadow MUF.

Action:

Set the Shadow MUF to EOJ if an extend is needed. When it has completed, retry the DYNAMIC_EXTEND.

LXX DYNAMIC EXTEND - REJECT BECAUSE MUFPLEX 2+

Reason:

A DYNAMIC_EXTEND is being requested for the LXX. However, the MUF is currently part of a MUFPLEX with two or more enabled.

Action:

Set all MUFs other than one to EOJ if an extend is needed. When all are terminated, the dynamic extend is allowed. After the extend, the other MUFs can be restarted.

LXX DYNAMIC EXTEND - REJECT BECAUSE FIXED BLK

Reason:

The message occurs if a DYNAMIC_EXTEND is requested for the LXX but the LXX is not in the variable style.

Action:

Version 15.0 supports the older style LXX formats only to ease the upgrade from a previous version. This is useful during the time when you need to fallback to the prior version. Once the fallback time has passed, the LXX should be fully spilled and initialized as variable. Then it can be increased in size or in a MUF after it has been initialized as variable.

LXX DYNAMIC EXTEND - COMPLETED

Reason:

A DYNAMIC_EXTEND of the LXX occurred. Additionally, the log has reached the wrap point and integrated the new space into the normal processing.

Action:

None.