Migration changes

The following table details the changes to numeric types:

For more information, see Designing a BOM for a COBOL model.

The following table details the changes to domains:

For more information, see Working with domains and COBOL.

The following table details changes to variable sets:

DataItem.intitem(“pic 9(5)”, 12345)
DataItem.shortitem(“pic 9(3)”, 12)
DataItem.longitem(“pic 9(11)”, 123456)
DataItem.stringitem(“pic x(5)”, “C0”)
DataItem.doubleitem(“9v9”, 123.456)

For more information, see Variable mapping for COBOL.

The following table details the change to the location of configuration data for COBOL code generation:

For more information, see Generating a COBOL XOM.

The following table details the change to encoding:

For more information, see Setting the copybook importer options.

The following changes are made to tables that use Occurs Depending On:

• odoTable is changed from type Array to type List.

• odoObject is deleted.

01 Root.
  05 odoObject pic 9.
  05 odoTable pic x(20) occurs 0 to 10 times depending on odoObject.

Root {
   int odoObject;
   String[] odoTable;
}

Root{
   List<String> odoTable;
}

Required action: Take either of the following actions to replace the deleted ODO object:

• Use the size of the Root.odoTable List to represent the Root.odoObject usage in rules.

• Add a read-only attribute to the BOM to replace the deleted Root.odoObject attribute and implement a B2X mapping for the added attribute using the size of Root.odoTable list.

For more information, see Table mapping between COBOL and Java.

The following table details the change to redefines statements. BOM attributes that you do not select in the migration wizard configuration are deleted.

01 Root.
  05 redefined-item pic 9.
  05 redefining-item redefines redefined-item pic x.

Root{
   int redefined_item;
   String redefining_item;
}

Root{
    int redefined_item;
}

Required action: Update any rules that use the deleted BOM attributes.

For more information, see REDEFINES statements in the copybook

BOM Methods for Level 88 item conditions are deleted.

Required action: Rewrite the rules or regenerate the BOM methods for the level 88 data item conditions that were deleted.

To support the COBOL code generation, you must add the COBOL method mapping for manually created BOM methods.

The following table details changes to data types. Data types are not supported. The BOM items that correspond to these data types are deleted during migration.

01 Root.
    05 Alphabetic pic A(20).
    05 AlphaNumericEdited pic XBX
    05 NumericEdit pic 9B9.
    05 ExternalFloat pic +99V9E99

Required action: Regenerate the deleted BOM attributes for the unsupported COBOL data types.

To regenerate the BOM attributes:

1. Update the copybook to ensure that it uses only supported COBOL data types.

2. Update the COBOL XOM to reflect the copybook changes.

3. Update the BOM to reflect the updated Java XOM.

For more information, see COBOL data item mapping to Java structures and Handling data type differences between Java and COBOL.

The following table details a change to COBOL mapped methods. You no longer need to use an index value to reference the current element in an array. Instead, you use the {} placeholder.

01 Root.
    05 CreditCard occurs 5 times.
       10 name pic x(20)
       10 name pic x(20)
       10 ids pic 9(10)

CreditCard{
public boolean 
validateCardbyID(int Ids);  }
Mapped method body:
move 'F' to <return> 
IF {ids} = ids of CreditCard of Root(Index1 of <this>)
set BoolValue of <return> to true
END-IF

Mapped method body:
move 'F' to <return>
IF {ids}=ids of {this}
set BoolValue of <return> to true
END-IF

If your rule project includes an index placeholder in a COBOL mapped method, choose one of the following options for the rule project:

• Continue using index placeholders to refer to array elements in the project. This is the default option. It requires no manual action.

• Enable the use of the new placeholders and update existing placeholders to use {} placeholders. Note that once you enable the use of the new placeholders, you cannot revert to using index placeholders.

To use the new {} placeholders in the rule project, change the default configuration for the migrated project by adding the following statements to its <rule project>/resources/cobol/CobolGenConfig.xml file:

<CobolGenConfig>
<CompatibleMode compatible="false" />
</CobolGenConfig>

For more information, see Implementing BOM methods for COBOL code generation.