Replication Status

The replication status information follows the data set parameters (records per area, record per block, etc.).

It is organized as follows:

global db linked file template

The following table briefly describes the replication status information. Do not make changes to the replication status information unless you are instructed to do so.

Column

Description

Data Set Structure Number

The DMSII structure number of the data set or remap.

RecType

The record type for variable format data sets.

AFN
ABSN
SEG
INX

The information in these columns represent the physical point in the audit file for the data set.

Date Time

The point in time of the data set in the audit file. If you upgraded from a previous release, notice that the year portion of the date now takes four digits instead of two.

Note: The first time you run the Span Accessory, there is no audit file time and date. Therefore, the date and time column contains 00000000000000, which is the host zero date. After the data set is replicated, the date and time stamp indicate the position in the audit file.

Mode

Indicates the data set status, as follows:

 

Mode = 0

The data set needs to be extracted.

 

Mode = 1

The data set is in the fix up phase.

 

Mode = 2

The data set is in the update phase.

 

Mode = 3

The data set was reorganized.

 

Mode = 4

The data set was purged.

DMS Format Level

This is the data set format level. The Span Accessory puts the format level in this column during the clone and during DMSII reorganizations.

Note: Zero is a valid format level. The format level will change when the DMSII data set is reorganized.

Client Format Level

This is the format level in the client database.

Do not make changes to the replication status information in the Span Accessory parameter file except in the following circumstances:

  • Modify Mode when you do a purge or reorganization. A mode of 3 indicates a data set reorganization; a mode of 4 indicates data set purge (DMUTILITY initialize).
  • After the reorganization on the client side, change the mode to 2 and then update the Client column (Format Level) to match the DMSII column (also under Format Level). The DMSII and Client columns are as follows:
    • The DMSII column is the DMSII update level (when the data set was added to or modified in the database definition). Each DASDL compile increments the level by one. For example, if you reorganized a data set the tenth time you update the DASDL, that data set has the number 0010 in the DMSII column. Note, however, that if the data set was ALTERed using GenFormat, the format level is recomputed and will have no obvious relationship with the DASDL compile number.
    • The Client column represents the update level of the data set in the Client database. Using the example of a data set reorganized on the tenth update, you would update the Client column to 0010 (the same as the DMSII level) after you reorganized that data set in the Client database.

Purges

When you purge a data set in the DMSII database, the value for mode changes to 4. A mode of 4 indicates that the data set was purged; however, there is no DMS format level change. Instead, when you get a mode of 4, you must purge the corresponding table (data set) in the client database and then change the mode to 2.

Reorganizations

When you change the DMSII database layout (for example, adding a data item), two things happen, as follows:

  • The DMSII format level corresponding to the changed data set is increased to the current database update level. The client format level, however, does not change. Instead, update the client database with the change and then increase the client format level to match the DMSII level.

    Note: The change to the client database may require you to do a reorganization on the client.

  • The mode changes to 3. Once you add the data item, for example, to the client database and you increase the client format level, change the mode back to 2.