Programming Fundamentals

To call an external procedure that returns a value, you must: (2) Declare it with RETURNS clause specifying the return type, (3) Declare both the parameter and result variables, and (6) Call it as a function assignment with the parameter. Option A is incomplete (no RETURNS, wrong call syntax), Option B uses wrong call syntax (CALL with function), Option D omits RETURNS.

VAR1 is 'PL/I' (5 chars). VAR2 receives 'PL/I' but is 10 chars, so it becomes 'PL/I ' (padded with 5 blanks). VAR3 is CHAR(2), so it receives only the first 2 characters 'PL'. RESULT, which is CHAR(5), gets 'PL' from VAR3, then padded with 3 blanks → 'PLbbb'. The variable length truncation at assignment to VAR3 is the key behavior.

Option 2 (DCL ARRAY_1 (5,2) DEC FIXED (3)) is NOT correct because PL/I requires the data type attributes to precede the dimension bounds. The correct form is either option 1 (type first, then bounds) or option 3 (bounds with separate type clauses). Option 4 is also invalid syntax.

In SyncSort processing, OUTFIL executes last as it handles final output file writing and formatting. The execution order is: SORT/INCLUDE statements → INREC → sorting → OUTREC → OUTFIL.

Perl supports lexical scoping through the 'my' keyword, which declares variables with lexical scope limited to their block. This is a fundamental feature of modern Perl. The statement is TRUE, so A is correct.

Interpreted languages like Perl generally execute slower than compiled languages because they must parse and translate code at runtime. However, modern JIT compilation and optimized engines make the absolute statement 'never execute as fast' technically debatable, though traditionally accepted as true in this context.

TYPE=SCAN is a JCL parameter that validates the JCL syntax for errors without executing the job. It's a syntax-checking feature, not related to previous jobs or doing nothing.

In COBOL, the EXIT statement is a no-operation statement that simply provides a common end point for a series of procedures or a paragraph. It does not terminate the program, loop, or paragraph on its own; it merely acts as a placeholder.

In an independent COBOL program (not called by another program), GO BACK functions identically to STOP RUN - it terminates the program and returns control to the operating system. It will not cause infinite loops (B), prevent execution (C), or cause compiler errors (D).

ExitAction is the specific QTP statement that terminates execution of the current action and moves to the next action. Exit alone is used in procedures, 'Exit Action' with a space is invalid syntax, and Exit Now is not a valid QTP statement.

There are two CASE syntax forms in SQL: simple CASE (CASE expression WHEN value THEN result) and searched CASE (CASE WHEN condition THEN result). While they provide similar conditional logic, they are syntactically different - the simple CASE compares a single expression to values, while searched CASE evaluates full boolean conditions.

The yield keyword in C# signals the compiler that the method is an iterator block. It enables lazy evaluation by returning elements one at a time when requested, rather than building the entire collection first. This is essential for implementing custom iterators with IEnumerable.

The #pragma directive provides compiler-specific instructions or options for compilation. It's used for things like warning suppression, optimization settings, or other compiler behaviors. #fcompile, #file, and #instruct are not standard preprocessor directives.

C# does NOT support implicit fall-through from one case label to another, unlike C or C++. Each case block must explicitly end with a break, return, goto, throw, or similar statement. The only exception is empty case labels that immediately follow each other. This design prevents accidental fall-through bugs that are common in C-style languages.