mainframe Online Quiz - 27

In BPEL, a 'pick' activity (often called 'receive choice') with an 'onAlarm' event handler (timeout element) is the standard construct for waiting for multiple possible events with a time limit. If the timeout expires before the message arrives, the onAlarm branch executes, enabling default processing. Parallel wait or subsequent wait activities don't provide the same event-driven timeout behavior.

When an SCA export has no binding explicitly defined during deployment, the SCA container automatically defaults to an SCA binding. This allows the module to be deployed and accessed for testing within the same SCA domain. Web Service bindings require explicit configuration, and the module remains accessible.

A graduated discount rate (where different purchase thresholds trigger different discount percentages) is best implemented as a rule set. Rule sets can contain multiple rules with conditions and actions, allowing for complex logic like 'if purchases > $1000 then discount = 10%, else if > $500 then discount = 5%'. Decision tables are better for uniform condition-action matrices, not graduated logic.

The 'Requires Own' option on a BPEL activity prevents the entire process (including previous activities) from being retried if that specific activity fails. This is used for activities that shouldn't be repeated, such as financial transactions or external calls with side effects. It doesn't force retries of the current or previous activities.

In WebSphere Process Server / Integration Developer, Java snippets allow integration developers to call arbitrary Java code or methods directly within a business process flow to implement logic not easily modeled using standard visual activities. The truncated options do not correctly define this behavior.

For interacting with third-party or non-IBM messaging middleware that supports JMS, the 'Generic JMS' binding should be used. MQ JMS is specific to IBM MQ. Regular JMS and Web Service-SOAP over JMS bindings are also for specific purposes. Generic JMS provides flexibility for various JMS providers.

When SCA modules are deployed in different clusters within the same cell, the SCA binding automatically handles the remote communication through the cell's SCA domain. No changes to bindings or additional references are needed because SCA provides location transparency. The second module can continue calling the first's SCA export seamlessly.

When a business rule needs to evaluate multiple independent factors (traffic citations and accident rate) to determine an outcome (insurance quote), a decision table is ideal. Decision tables clearly map combinations of condition values to actions, making them perfect for multi-factor decision logic. Rule sets are better for sequential conditions, not parallel factors.

When interface operations have incompatible input/output types that need transformation, the 'Extract' parameter transformation type should be used. Extract allows pulling specific data from one structure and mapping it to another structure. Move and Assign are for direct transfers, Submap is for reusing existing maps.

AA is the standard abbreviation for Application Architecture in enterprise systems context, particularly in legacy and mainframe environments. The other options (Access, Action, Answer) are not standard abbreviations in this domain.

A COBOL IF statement evaluates a single condition at a time. While you can combine conditions using AND/OR connectors, the fundamental IF construct makes one comparison decision. For multiple independent comparisons, you need nested IFs.

COBOL IF statements can encounter logical errors (wrong condition logic), runtime errors (invalid data type comparison), and infinite loops (when combined with PERFORM or if condition never becomes false due to state changes). All three error types are possible in IF-based control flow.

COBOL's PERFORM...UNTIL structure is analogous to a do-while loop in languages like Java and C++ - it executes the code block, then checks the condition, repeating until the condition becomes true. It's not a for loop (fixed iteration) or a method call.

The AFTER clause in COBOL PERFORM statements allows condition checking after initial execution, enabling the loop to run once before evaluation. Standard PERFORM checks first, inline PERFORM is about code placement, and the functionality is definitely possible in COBOL.

Starting with A=0, B=9, the loop PERFORM UNTIL A>B executes while A<=9. A increments by 2 each iteration: 0, 2, 4, 6, 8, 10. The condition A>B becomes true when A=10. The loop runs for A=0,2,4,6,8 - that's 5 additions.

When an IF condition evaluates to true, the first action is executing the code or function within the IF block. Only after execution does flow continue to any ELSE or statement exit. It doesn't exit immediately, exit the program, or re-execute.

Not negative means a value is greater than or equal to zero (>=0). This includes zero and all positive numbers. It doesn't mean equal to 0 only, or >=1 (which excludes zero), or <=0 (which would include negative numbers).

ASCII collating sequence orders characters by their numerical code values: spaces (32), special characters (33-47), digits 0-9 (48-57), uppercase A-Z (65-90), then lowercase a-z (97-122). This is the standard ASCII ordering.