Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Additional informational columns in load files

Log Master includes informational columns at the beginning of all records in the output load file, in addition to the columns that you specify in the WHERE clause or filter.

For more information about the additional columns and when they are included, see INFO COLUMNS.

If you move data from one table to another by using a load file, you must define additional columns in the target table to match these additional informational columns. The tables on the following pages show the layout of the additional columns and additional records. The tables show the informational columns that Log Master includes when you specify:

  • URID FIELDS as ALL

  • URID FIELDS as URID

  • URID FIELDS as NONE

  • URID TABLE as YES (the additional table that you must define)

The tables on these pages show the layout of the additional columns or records when the value of the FORMAT keyword is Log Master. If the value is SDF or CSV, the content and order of the columns is the same, but the type and length of the data in a column might be different.

  • To find the sequence and length of columns in an SDF load file, look at the output load control file.

  • To find the sequence of columns in a CSV load file, look at the output load control file (the length of columns in an output CSV load file varies for each record).

The following table shows the informational columns that Log Master includes if you specify URID FIELDS as ALL.

Column name

Data type

Description

#CONNECTION_TYPE

CHAR(8)

Connection type

#CONNECTION_ID

CHAR(8)

Connection ID

#CORRELATION_ID

CHAR(12)

Correlation ID

#AUTH_ID

CHAR(8)

Authorization ID

#PLAN_NAME

CHAR(8)

Plan name

#URIDLRSN

CHAR(6) 1

Unit of Recovery LRSN

(the same as #URIDBEGINPOINT if not data sharing)

#URIDBEGINPOINT

CHAR(6) 1

Unit of Recovery ID (RBA)

#URIDMEMBERID

SMALLINT

Data sharing member ID (0 if not data sharing)

#URIDTIMESTAMP

CHAR(26)

Unit of recovery date and time

#URIDDISP

CHAR(1)

Unit of recovery disposition:

  • C = Committed

  • A= Aborted

#URIDCOMMITLRSN

CHAR(6) 1

Unit of recovery COMMIT LRSN

(the same as #UORCOMMITPOINT if not data sharing)

#URIDCOMMITPOINT

CHAR(6) 1

Unit of recovery COMMIT (RBA)

#DB_NAME

CHAR(8)

Database name

#TS_NAME

CHAR(8)

Table space name

#TB_CREATOR

CHAR(8)

Table creator

#TB_NAME

CHAR(18)

Table name

#TB_SEQNUM

CHAR(3)

Table sequence number

This number can be greater than 1 only if the load file contains records from more than one 'instance' of the same table.

#LLRECTIMESTAMP

CHAR(26)

Date and time of log record represented in current load record

#LLPARTNUM

CHAR(2)

Number of partition (within partitioned table space) of log record represented in current load record

#LLRID

CHAR(5)

Record ID (RID) of log record represented in current load record

#LOGRBA

CHAR(6) 1

RBA/LRSN of log record represented in current load record

#CHANGE_TYPE

CHAR(1)

Type of modification:

  • I = INSERT

  • D = DELETE

  • U = UPDATE

  • M = MASSDELETE

  • E = EXCHANGE

#UPDATE_TYPE

CHAR(1)

Field is valid only when #CHANGE_TYPE is U:

  • A = After Image

  • B = Before Image

  • ' ' (blank) = Both images

1 If the DB2 subsystem is migrated to IBM DB2 11 NFM, this value will be CHAR(10). 

The following table shows the informational columns that Log Master includes if you specify URID FIELDS as URID.

Column name

Data type

Description

#URIDLRSN

CHAR(6) 1

Unit of Recovery LRSN

(the same as #URIDBEGINPOINT if not data sharing)

#URIDBEGINPOINT

CHAR(6) 1

Unit of Recovery ID (RBA)

#URIDMEMBERID

SMALLINT

Data sharing member ID (0 if not data sharing)

#DB_NAME

CHAR(8)

Database name

#TS_NAME

CHAR(8)

Table space name

#TB_CREATOR

CHAR(8)

Table creator

#TB_NAME

CHAR(18)

Table name

#TB_SEQNUM

CHAR(3)

Table sequence number

This number can be greater than 1 only if the load file contains records from more than one 'instance' of the same table.

#LOGRBA

CHAR(6) 1

RBA/LRSN of log record represented in current load record

#CHANGE_TYPE

CHAR(1)

Type of modification:

  • I = INSERT

  • D = DELETE

  • U = UPDATE

  • M = MASSDELETE

  • E = EXCHANGE

#UPDATE_TYPE

CHAR(1)

Field is valid only when #CHANGE_TYPE is U:

  • A = After Image

  • B = Before Image

  • ' ' (blank) = Both images

1 If the DB2 subsystem is migrated to IBM DB2 11 NFM, this value will be CHAR(10).


The following table shows the informational columns that Log Master includes if you specify URID FIELDS as NONE.

Column name

Data type

Description

#DB_NAME

CHAR(8)

Database name

#TS_NAME

CHAR(8)

Table space name

#TB_CREATOR

CHAR(8)

Table creator

#TB_NAME

CHAR(18)

Table name

#TB_SEQNUM

CHAR(3)

Table sequence number

This number can be greater than 1 only if the load file contains records from more than one 'instance' of the same table.

#LOGRBA

CHAR(6) 1

RBA/LRSN of the log record represented in current load record

#CHANGE_TYPE

CHAR(1)

Type of modification:

  • I = INSERT

  • D = DELETE

  • U = UPDATE

  • M = MASSDELETE

  • E = EXCHANGE

#UPDATE_TYPE

CHAR(1)

Field is valid only when #CHANGE_TYPE is U:

  • A = After Image

  • B = Before Image

  • ' ' (blank) = Both images

1 If the DB2 subsystem is migrated to IBM DB2 11 NFM, this value will be CHAR(10). 


The following table shows the format of the additional table that you must define when you specify URID TABLE as YES. The default name of the URID table in the control cards of the load control file is #ALPURID.#ALPURIDTABLE. To change the default table name, edit the load control file.

Column name

Data type

Description

#DB_NAME

CHAR(8)

Database name

#TS_NAME

CHAR(8)

Table space name

#TB_CREATOR

CHAR(8)

Table creator

#TB_NAME

CHAR(18)

Table name

#LOGRBA

CHAR(6) 1

RBA/LRSN of log record represented in current load record

#CONNECTION_TYPE

CHAR(8)

Connection type

#CONNECTION_ID

CHAR(8)

Connection ID

#CORRELATION_ID

CHAR(12)

Correlation ID

#AUTH_ID

CHAR(8)

Authorization ID

#PLAN_NAME

CHAR(8)

Plan name

#URIDLRSN

CHAR(6) 1

Unit of Recovery LRSN

(the same as #URIDBEGINPOINT if not data sharing)

#URIDBEGINPOINT

CHAR(6) 1

Unit of recovery ID (RBA)

#URIDMEMBERID

SMALLINT

Data sharing member ID (0 if not data sharing)

#URIDTIMESTAMP

CHAR(26)

Unit of recovery date and time

#URIDDISP

CHAR(1)

Unit of recovery disposition

  • C = Committed

  • A= Aborted

#URIDCOMMITLRSN

CHAR(6) 1

Unit of recovery COMMIT LRSN

(the same as #UORCOMMITPOINT if not data sharing)

#URIDCOMMITPOINT

CHAR(6) 1

Unit of recovery COMMIT (RBA)

#INSERTS

INTEGER

Number of INSERTs for the unit of recovery

#DELETES

INTEGER

Number of DELETEs for the unit of recovery

#UPDATES

INTEGER

Number of UPDATEs for the unit of recovery

#DELETERIS

INTEGER

Number of DELETEs due to referential integrity for the unit of recovery

#UPDATERIS

INTEGER

Number of UPDATEs due to referential integrity for the unit of recovery

1 If the DB2 subsystem is migrated to IBM DB2 11 NFM, this value will be CHAR(10).





Was this page helpful? Yes No Submitting... Thank you

Comments