Programming Fundamentals

In standard COBOL, the verbs ACCEPT, MOVE, and STRING are all valid COBOL verbs. FIND is not a standard COBOL verb - it's typically used in database systems like SQL or in some mainframe query utilities, but not in core COBOL programming. This makes 'FIND' the correct answer to what 'is not a COBOL verb'.

eval() is a JavaScript/ActionScript function that evaluates a string expression and can access variables, properties, objects, or movie clips by name. It dynamically executes code stored as strings. The other options (toEval, toStr, string) are not valid functions for this purpose.

COMP-1 (single-precision floating point) in COBOL does not accept a PIC (PICTURE) clause because it uses internal binary representation, not the character-based format that PIC defines. COMP, COMP-3, and DISPLAY can all have PIC clauses to define their data layout. COMP-1 is pre-defined as a 4-byte floating-point format.

The BufferedWriter constructor requires a Writer object as its argument. On line 15, a File object is passed, which does not inherit from Writer, causing a compilation failure. Lines 16, 17, and 18 are valid because FileWriter, PrintWriter, and BufferedWriter all extend Writer.

The answer to the question is A. NULL.

When a variable is declared in PL/SQL without an initial value, it is initialized to NULL. This means that the variable has no value, and any attempt to use it will result in a NULL value.

Option B is incorrect because the value of a NUMBER variable is not automatically initialized to 0. Option C is incorrect because a compilation error will not occur if a variable is declared without an initial value. Option D is incorrect because an exception will not be raised if a variable is declared without an initial value.

Here is an example of how a NULL value is handled in PL/SQL:

DECLARE
  v_number NUMBER;
BEGIN
  v_number := NULL;
  dbms_output.put_line(v_number); -- This will print 'NULL'
END;

As you can see, the value of v_number is printed as NULL when it is first used in the executable section of the PL/SQL block. This is because the variable was declared without an initial value, and therefore its value is NULL.

NULL represents unknown or missing data. Any comparison operation involving NULL (including NULL = NULL) yields NULL, not TRUE or FALSE. This is three-valued logic: TRUE, FALSE, or NULL (unknown). Use IS NULL or IS NOT NULL to test for NULL values.

Error trapping uses EXCEPTION handlers within the EXCEPTION section of a PL/SQL block. The EXECUTABLE section contains the runtime code that may raise exceptions. The EXCEPTION section is where handlers are defined. Header has no error handling. Declarative defines variables/types.

In QTP (QuickTest Professional) scripting, function names must follow specific naming conventions. The function name must start with 'func' followed by the actual name. 'funcOpenWindow()' follows this convention correctly. The other options are invalid: 'functionOpenWindow()' uses the full word 'function', 'funOpenWindow123()' is an incorrect abbreviation, and 'OpenWindow()' lacks the required prefix. These naming rules help distinguish user-defined functions from built-in functions and keywords.

IfNull is primarily a SQL function (like MySQL's IFNULL), not a DataStage transformer function. DataStage uses SetNull(), MakeNull(), NullToEmpty(), IsNull(), and NullToValue() for null handling. The question tests familiarity with DataStage-specific function names versus generic SQL functions.

A scope terminator marks the end of a verb or statement in COBOL. Explicit scope terminators like END-IF, END-PERFORM, END-READ make the code more readable and prevent ambiguity by clearly defining where a conditional or iterative construct ends. Both options 1 and 2 correctly describe the purpose of scope terminators.

JCL steps can be skipped using both conditional processing methods. The COND parameter tests return codes from previous steps. IF/THEN/ELSE (or IF/THEN/ELSE/ENDIF) constructs provide conditional logic. Statement D is false - steps can indeed be conditionally executed or skipped.

JCL steps can be skipped using both conditional processing methods. The COND parameter tests return codes from previous steps. IF/THEN/ELSE (or IF/THEN/ELSE/ENDIF) constructs provide conditional logic. Statement D is false - steps can indeed be conditionally executed or skipped.

JCL steps can be skipped using both COND parameters on EXEC statements and IF/THEN/ELSE construct statements. COND conditionally skips based on return codes from previous steps. IF/THEN/ELSE provides more complex conditional logic. Both are valid methods for conditional execution.

When exception B is raised in the inner block's ELSE clause, it has no matching handler in that inner block (which only handles A). Unhandled exceptions propagate to the enclosing block, where B is caught. Option B correctly describes this propagation behavior.