Programming Fundamentals

In COBOL, GO BACK is equivalent to STOP RUN in a stand-alone program because GO BACK returns control to the calling program, and when there is no caller (stand-alone), it terminates the program. FINISH, STOP, and EXIT are not valid COBOL verbs for program termination in this context. EXIT PROGRAM exists but is for called programs, not stand-alone programs.

In COBOL, the GOBACK statement is the preferred alternative to STOP RUN in stand-alone programs. GOBACK returns control to the caller and closes all files, achieving the same functionality as STOP RUN. FINISH, STOP (without RUN), and EXIT are not valid COBOL statements for program termination.

Index-names defined via the INDEXED BY clause represent binary displacement values managed internally by the compiler. Because they are not standard data items, standard COBOL prohibits displaying index-names directly with a DISPLAY statement, making the statement true.

Using NEXT SENTENCE in COBOL transfers program control to the statement immediately following the next period. Since the period is placed after ADD +1 TO INPUT-COUNT., executing NEXT SENTENCE skips the addition step entirely, leaving INPUT-COUNT unchanged.

When defining ASCENDING or DESCENDING KEY for table sorting or searching with SEARCH ALL, the key data items must be comparable and have a total ordering. Floating-point numbers should not be used as keys because they can have representation issues (like NaN, infinity, or precision problems) that make sorting and binary search unreliable and unpredictable.

EJECT is a COBOL compiler directing verb that advances the compiler listing to a new page. It helps organize printed source code listings for better readability.

The EJECT statement in COBOL is specifically designed to force a new page in compiler listings, similar to a page break in document formatting. This is a standard compiler-directing statement that controls output pagination. Option A correctly identifies this functionality.

ASCENDING and DESCENDING keys are used for sorting and table searching operations (SORT, SEARCH ALL). Floating-point numbers are approximate values and may have tiny representation errors, making them unreliable for exact comparisons required by these operations. Therefore, floating-point items cannot be used as sort/search keys. Option A is correct.

Static variables in OBI EE are defined once in the repository and don't require initialization blocks - their values are set at design-time. Dynamic variables, system session variables, and non-system session variables all require initialization blocks to populate their values at runtime.

STOP RUN is technically valid in COBOL syntax even within subroutines, though it's generally considered poor practice as it abruptly terminates the entire program unit. The question asks about technical possibility, not best practices.

In COBOL, a period ('.') terminates the entire IF statement structure. In line 3, 'MOVE 200 TO VALUE-B.' has a period at the end, which prematurely terminates the outer 'IF A > B' statement. Thus, the subsequent 'END-IF' lines will cause compiler errors as they are unmatched.

In COBOL, the EXIT statement performs no operation when executed. It serves as a paragraph terminator or control transfer point but takes no action.

An initial value property in Oracle Forms sets the default value for an item when a record is created, but this value can be altered programmatically using triggers like When-New-Form-Instance, When-New-Block-Instance, or When-New-Record-Instance. The statement incorrectly claims it cannot be changed.