com.ibm.pdp.maf.rpp.pac.program
Interface CDLineDataStructure

All Superinterfaces:
CDLine, Element

public interface CDLineDataStructure
extends CDLine

CDLineDataStrucure are used to describe three basic types of elements, which are specified in the Organization field:

For each external resource, you have its:


Field Summary
static java.lang.String copyright
           
 
Method Summary
 int getBreakLevel()
           
 java.util.List<DataStructureCall> getDataStructureCalls()
           
 java.lang.String getFileStatus()
           
 java.lang.String getRecordTypeDataElementCode()
           
 java.lang.String getResultDataStructureCode()
           
 java.lang.String getSortKeys()
           
 java.lang.String getSourceDataStructureCode()
           
 int getSyncLevel()
           
 int getTransactionBreakLevel()
           
 
Methods inherited from interface com.ibm.pdp.maf.rpp.pac.program.CDLine
getAccessKeyDataElementCode, getAccessMode, getBlockFactor, getBlockMode, getBlockType, getCobolRecordLevel, getCodeInProgram, getExternalName, getFormatType, getGeneratedDescriptionType, getIOMode, getOrganization, getPhysicalUnitType, getPhysicalUnitTypeComplement, getSubScheme, getUnitType, getUsage
 

Field Detail

copyright

static final java.lang.String copyright
See Also:
Constant Field Values
Method Detail

getBreakLevel

int getBreakLevel()

For sequentially accessed, sorted files, it is the number of Data Elements (elementary or group) on which a control break processing is specified for the Data Structure.

O is the default value.

1 to 9 levels, according to the number of Data Elements to be used for control break processing. These Data Elements are identified as the Sort key composition field for this Data Structure.

When there is a control break processing on a Data Structure, two indicators keep track of the status of the records being processed

Below, the term 'umpteenth key Data Element' includes all the key Data Elements up to and including the umpteenth level:

When these files are synchronized with others, the control breaks are kept synchronized through two additional switches:

For output files (Usage set to D: Output file): A value other than zero creates a duplicate file layout to be generated in the WORKING-STORAGE SECTION, prefixed by 1-. However you are advised to specify it in the work areas, using micropatterns.

Returns:

getDataStructureCalls

java.util.List<DataStructureCall> getDataStructureCalls()

List of the DataStrucutre called.

Returns:

getFileStatus

java.lang.String getFileStatus()

This field is optional.

If specified, it is a character string, on 10 characters maximum, in the following format:

ddsseeeeee, where:

The use of this field varies according to the Type of COBOL code and to the Data Structure call Organization.

Returns:

getRecordTypeDataElementCode

java.lang.String getRecordTypeDataElementCode()

Code of the Data Element whose values identify the different record types of a Data Structure.

This Data Element must belong to the common part Segment (00 Segment).

This name can also be specified in the Structure code field of the Segment Definition tab.

Returns:

getResultDataStructureCode

java.lang.String getResultDataStructureCode()

If the Data Structure has a Usage set to P: Principal, it is the Code in program' of the result output Data Structure (two characters).

If the Data Structure has a Usage set to R: Result or D: Output file, it is the Code in program of the principal input Data Structure (two characters).

Returns:

getSortKeys

java.lang.String getSortKeys()

It is the group of the Data Elements which make up the sort key for control break processing.

They are identified by the value entered in the Sort key field on the Segment -CE Lines tab.

The order for sorting these key Data Elements can be entered here. To do so, you use the values assigned on the -CE Lines tab in the appropriate order, from major to minor - left to right.

If you do enter anything here, the Data Elements coded with value 1 - 9 are taken as the default.

Note: For transaction files, include the 'action code' and 'record type' Data Elements as a part of the key. The order in which these Data Elements are sorted determines the sequence in which the transactions update the principal file, and the policy for duplicate record detection.

Returns:

getSourceDataStructureCode

java.lang.String getSourceDataStructureCode()

If the Data Structure has a Usage set to:

S: Selected, you must enter the Code in program (on two characters) of the input source. On the source Data Structure call line, you must enter the Code in program of the selected Data Structure.

Returns:

getSyncLevel

int getSyncLevel()

For sequentially accessed files, this field is used to set the synchronization of two or more files.

O is the default value.

1 to 9 levels. Enter the number of Data Elements (elementary or group) on which a file matching is to be synchronized for this Data Structure. This number identifies the number of the key fields (identified in the Sort key composition field) that are involved in the synchronization.

For an automatic synchronization, the following conditions must be met:

These Data Elements must have a display format (if they are numeric, they must be whole numbers and unsigned).

The switches generated to control file synchronization are:

Returns:

getTransactionBreakLevel

int getTransactionBreakLevel()

In a transaction file, it is the position, within the sort key, of the Action code (entered on the Segment Definition tab).

Example: If the value of the Sort key is ABCDE and the Action code is D, the value is 4.

It is the most minor key of the sort key. It is used to differentiate one type of transaction from another in the same principal file. Duplicates are detected if any key elements below this one are found to match.

By default, the value of this field is that of the Break level already entered in the previous window. The value must be one-character long.

Note: All spaces are replaced with zeros.

Returns: