Information

Title	Loading some attributes via delta.df does NOT affect _mstrblk._mstrblk-timestamp

URL Name	loading-some-attributes-via-delta-df-does-not-affect-mstrblk-mstrblk-timestamp

Article Number	000169200

Environment	Product: OpenEdge Version: All Supported Versions OS: All Supported Platforms

Question/Problem Description

If you manually change the schema using the dictionary, the _mstrblk-timestamp is always changed as described.

However, if you change a field display format, description etc (non crc affect change) using a .df file, it does not change the timestamp.

Steps to Reproduce	- Create two identical databases proenv>prodb sports1 sports proenv>prodb sports2 sports - Connect to both dbs proenv>prowin -db sports1 -1 -db sports2 -1 - Run the following code from the procedure editor to show the timestamp for sports1 before making manual changes in the dictionary FIND FIRST sports1._mstrblk. MESSAGE sports1._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX. - Choose Tools >> Data Dictionary and modify the format of a field in one of the tables in sports1 - Back out to the Procedure Editor again and run the below code, taking note that the timestamp changed: FIND FIRST sports1._mstrblk. MESSAGE sports1._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX. - Create an incremental .df using the Data Administration tool (e.g. Admin >> Dump >> Create Incremental .df file) Note: See Progress knowledgebase article 000070200 for details - Back out to the Procedure Editor and run the following code and take note of the timestamp FIND FIRST sports2._mstrblk. MESSAGE sports2._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX. - Load the .df into sports2 - Back out to the Procedure Editor and run the following code and take note of the timestamp (nothing changed) FIND FIRST sports2._mstrblk. MESSAGE sports2._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX.

Steps to Reproduce

- Create two identical databases
proenv>prodb sports1 sports
proenv>prodb sports2 sports

- Connect to both dbs
proenv>prowin -db sports1 -1 -db sports2 -1

- Run the following code from the procedure editor to show the timestamp for sports1 before making manual changes in the dictionary
FIND FIRST sports1._mstrblk.
MESSAGE sports1._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX.

- Choose Tools >> Data Dictionary and modify the format of a field in one of the tables in sports1

- Back out to the Procedure Editor again and run the below code, taking note that the timestamp changed:
FIND FIRST sports1._mstrblk.
MESSAGE sports1._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX.

- Create an incremental .df using the Data Administration tool (e.g. Admin >> Dump >> Create Incremental .df file)
Note: See Progress knowledgebase article 000070200 for details

- Back out to the Procedure Editor and run the following code and take note of the timestamp
FIND FIRST sports2._mstrblk.
MESSAGE sports2._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX.

- Load the .df into sports2

- Back out to the Procedure Editor and run the following code and take note of the timestamp (nothing changed)
FIND FIRST sports2._mstrblk.
MESSAGE sports2._mstrblk._mstrblk-timestamp VIEW-AS ALERT-BOX.

Clarifying Information

Error Message

Defect Number	OCTA-20551

Enhancement Number

Cause

The exact cause is not known at this time.

Resolution

None at this time.

Workaround

Notes

Keyword Phrase

Last Modified Date	2/15/2023 5:48 PM

Loading some attributes via delta.df does NOT affect _mstrblk._mstrblk-timestamp

Information