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.

Logical log data set record (DLDS)

If Log Master for DB2 creates an output logical log file as a data set, the control file contains one instance of the Logical Log Data Set Record (DLDS).

The DLDS record contains the data set name of the logical log data set when it was created by Log Master. The product initially duplicates this information in the platform-independent Current Path Record. If you move the logical log, be sure to update the Current Path Record to indicate the new location of the logical log data set. Do not update the Logical Log Data Set Record.

Use the SEGMENTED field of this record to determine when the logical log data file contains segmented logical log records. For more information, see Normal and segmented logical log record formats.

Record status: DB2 specific

Field name

Offset

Definition

Description

Dec

Hex

CNTLRECORDTYPE

00

00

CHAR(4)

Control record type: DLDS - Logical Log DS Record (DB2)

ORIGDATADSNAME

04

04

CHAR(44)

Name of logical log data set when created

RECORDFORMAT

48

30

CHAR(3)

Logical log file RECFM

VB - variable blocked

VBS - variable block spanned (VBS is tolerated, but ignored in versions later than 2.2.00.)

DATEFORMAT

51

33

CHAR(8)

Date/Times in logical log file are:

DB2I - DB2 DB2ISO format

SASTIME - SAS format

EXPANDVAR

59

3B

CHAR(1)

N - VAR fields are not expanded to full length

Y - VAR fields are expanded to full length or padded as required

SEGMENTED

60

3C

CHAR(1)

N - logical log file does not contain segmented records

Y - logical log file contains segmented records

DDLOBJECTS

61

3D

CHAR(1)

N - logical log file does not contain DDL information

Y - logical log file contains DDL information

LOBSINCLUDED

62

3E

CHAR(1)

N - logical log file does not contain LOB data (column values)

Y - logical log file contains LOB data

XMLINCLUDED

63

3F

CHAR(1)

N - logical log file does not contain XML data (column values)

Y - logical log file contains XML data

XMLSTRINGINCLUDED

64

40

CHAR(1)

N - XML string information was not created with this logical log file

Y - logical log file points to XML string information in separate data set

MERGED

65

41

CHAR(1)

N - logical log file was not created by merging multiple logical log files

Y - logical log file was created by merging multiple logical log files

CMDSINCLUDED

66

42

CHAR(1)

N - logical log file does not contain DB2 command information

Y - logical log file contains DB2 command information

INLINELOBSINCLUDED

67

43

CHAR(1)

N - logical log file does not contain inline LOB data (column values)

Y - logical log file contains inline LOB data

(Total Length)

68

44

Not applicable

Not applicable



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

Comments