nerdexam
IBM

000-349 · Question #16

Refer to the Exhibit. A large corporation manufactures beds in different colors. The inventory file consists of three record types, a header, a detail, and bed color. The record type is the first…

The correct answer is A. Use the restart attribute on the detail record. Placing the restart attribute on the detail record causes the map engine to abandon the current detail record instance - and all its child color records - when any color record error is encountered, then resume processing at the next detail record.

Configuration

Question

Refer to the Exhibit. A large corporation manufactures beds in different colors. The inventory file consists of three record types, a header, a detail, and bed color. The record type is the first byte of each record (H=Header, D=Detail, C=Color). If there is an error in one of the bed color records, all of the color records under that detail record should be ignored. How do you specify that all color records should be ignored if one is found to be invalid?

Options

  • AUse the restart attribute on the detail record
  • BUse the restart attribute on the color record
  • CUse the restart attribute on the header record.
  • DUse the restart function in the map.

How the community answered

(46 responses)
  • A
    80% (37)
  • B
    2% (1)
  • C
    13% (6)
  • D
    4% (2)

Why each option

Placing the restart attribute on the detail record causes the map engine to abandon the current detail record instance - and all its child color records - when any color record error is encountered, then resume processing at the next detail record.

AUse the restart attribute on the detail recordCorrect

The restart attribute on the detail record defines the recovery boundary: when an error occurs in a subordinate color record, the engine discards the remainder of that detail record's children (all remaining color records) and restarts parsing at the next occurrence of the detail record, which exactly satisfies the requirement to ignore all color records under an invalid detail group.

BUse the restart attribute on the color record

Setting restart on the color record itself would only cause the engine to skip to the next individual color record, not abandon all color records under the current detail record, failing to satisfy the all-or-nothing requirement.

CUse the restart attribute on the header record.

Placing restart on the header record would cause the engine to skip the entire header and all subordinate detail and color records upon any color error, discarding far more data than intended.

DUse the restart function in the map.

There is no standalone restart function within the map itself; restart is an attribute applied to a specific group component in the type tree to define the error-recovery scope.

Concept tested: Restart attribute placement for group-level error recovery

Source: https://www.ibm.com/docs/en/b2b-integrator/6.2?topic=properties-restart-attribute

Topics

#restart attribute#error handling#record types#type tree

Community Discussion

No community discussion yet for this question.

Full 000-349 Practice