A developer is working with a mainframe legacy application. How can they build the execution object model (XOM) with the information from this application?

Question

Options

• AImport the Cobol copybook.
• BExtract objects through SQL queries.
• CUse the Decision Engine API to map Cobol structures.
• DUse the Rule Designer migration tool to convert the source Cobol copybook.

• A
  3% (1)
• B
  95% (37)
• C
  3% (1)

Explanation

Extracting objects through SQL queries (B) is correct because mainframe legacy applications typically store their data in relational databases (such as IBM DB2), and querying the database schema via SQL exposes the data structures needed to define the XOM in IBM Operational Decision Manager (ODM).

Option A is wrong because importing a COBOL copybook defines data layouts for programs, not a method for generating the XOM in ODM. Option C is wrong because the Decision Engine API is used to execute rules at runtime, not to map legacy structures into an object model. Option D is wrong because Rule Designer's migration tool is intended for converting rules, not for transforming COBOL copybooks into an executable object model.

Memory tip: Think of SQL as your "schema extractor" - mainframe data lives in relational databases, so SQL gives you the structural blueprint ODM needs to build the XOM.

No community discussion yet for this question.