Programming Fundamentals

JCLLIB statement rules in JCL are specific. Option C is correct because only one JCLLIB statement is allowed per JOB - it defines the private library for the entire job. Option D is correct because JCLLIB must be placed before the first EXEC statement in the job. Option A is incorrect because JCLLIB is job-scoped, not per EXEC. Option B is incorrect because JCLLIB is a statement type itself and follows JCL naming rules. The JCLLIB statement enables cataloged procedure access by specifying a private library search order.

In JCL, COND parameters test if a condition is true to bypass/skip execution. To execute only if the previous return code (RC) is strictly less than 8, we want to bypass if RC is greater than or equal to 8. Hence, COND=(8,LE) is correct because it bypasses execution if 8 is Less than or Equal to RC (meaning RC >= 8).

The COND parameter controls conditional step execution based on previous step return codes. Option B is correct because a COND parameter on an EXEC calling a procedure applies to ALL steps in that procedure, not just the first. Option D is correct because COND can test multiple step return codes - if any condition is true, the step is bypassed. Option A is incorrect because COND only skips execution when its condition evaluates TRUE (meaning the condition was met). Option C is incorrect because COND tests return codes, not just checks them - it evaluates whether codes meet specified comparison criteria (EQ, NE, GT, LT, GE, LE).

JCL JOB statement positional parameters follow strict order: accounting information (in parentheses), then programmer name. Option A correctly places accounting info (ATUT000) in positional form followed by the programmer name (TU00001). Option B is equivalent with quoted parameters. Options C and D are incorrect because they reverse the positional order or use improper syntax.

INFO-FUNCTION-KEY is specifically designed to store the function key number when a function key is received in CICS. The other variables serve different purposes: INFO-PROGRAM-ID for program name, INFO-CONVERSATION for mode status, and INFO-PREVIOUS-PROGRAM-ID for tracking the prior program.

In APS (Application Development System) COBOL generators, the INFO-PASSOFF variable is set to 'Y' when the program is invoked using a PASSOFF statement, whereas the other options store different context metadata.

In COBOL, CONTINUE is a no-op statement that transfers control to the next sequential instruction, while NEXT SENTENCE transfers control to the first statement following the next period, making the statement true.

To compile a COBOL program without errors, the minimum requirements are: Identification Division (which contains the Program-ID paragraph) and the Program-ID paragraph itself (which specifies the program name). All these components are mandatory and must be present for the program to be syntactically valid and compilable.

In COBOL EVALUATE statements, WHEN clauses are evaluated in the order they appear. The first matching WHEN clause is executed, so the order is significant. This is similar to case/switch statements in other languages where clause order matters for matching logic.

In Java, dividing a floating-point number by zero does not throw an exception. Instead, it produces positive or negative infinity (Float.POSITIVE_INFINITY in this case). Only integer division by zero throws ArithmeticException. Therefore the statement does NOT throw an exception, making 'False' the correct answer.

Macro functions (created with #define) are expanded by the preprocessor before compilation begins, resulting in text substitution. Inline functions are expanded by the compiler during compilation, with the inline keyword being a hint (not a guarantee) for function call replacement. Option A is wrong because it misstates when inline expansion occurs. Option C reverses the correct phases.

Both malloc and new can allocate memory for any type, not just arrays or objects. In C++, new automatically initializes objects by invoking their constructors, whereas malloc simply allocates raw bytes of memory without performing initialization.

Pass by reference in C++ uses reference variables (using & in the parameter list) which act as aliases without explicit pointer dereferencing syntax, whereas pass by address passes pointer values that must be explicitly addressed and dereferenced. They are distinct concepts and mechanisms.

.NET has two levels of compilation. First, the language compiler (like C# or VB.NET) converts source code to Intermediate Language (IL). Second, the JIT compiler converts IL to native machine code at runtime. This two-stage process enables cross-language integration.