Conditional operations define test conditions that compare values held by different fields. When the test condition is true for the input record or control break being processed, the specified action occurs. Otherwise, the specified action is ignored, and control passes to the next processing statement.
Types of Conditional Operations
CA Culprit can perform the following types of conditional operations:
When a compound test operation is specified on a process parameter, CA Culprit breaks down the compound operation into a series of simple test operations. Each of these system-generated statements is printed on the Input Parameter Listing, as shown in the following figure. CA Culprit uses the following criteria to resolve compound test operations into simple test operations:
Input Parameter Listing of a Compound Test Operation:
mm/dd/yy INPUT PARAMETER LISTING Vnn.n PAGE 3 ******** PROCESS USER INTERNAL LABEL SEQUENCE PROCESS STATEMENT ******** 01 7 010 1 $ IF ((SALARY GT 10000) ─┐ 01 7 $ AND (TITLE NE 'DATA ENTRY CLERK ')) ├── User input 01 7 $ OR EMP-LNAME EQ ('BREEZE ' TO 'LANCHESTER ') │ 01 7 $ TAKE ─┘ 01 7 2 SALARY GT 10000 INTSEQ-4 ──┐ 01 7 3 B INTSEQ-5 │ CA-Culprit's interpretation 01 7 4 TITLE NE 'DATA ENTRY CLERK ' TAKE ├── of the compound test 01 7 5 EMP-LNAME GE 'BREEZE ' INTSEQ-7 │ operation 01 7 6 B INTSEQ-8 │ 01 7 7 EMP-LNAME LE 'LANCHESTER ' TAKE │ 01 7 8 $ ──┘
Note: CA-Culprit generates simple test operation statements from a compound test operation statement; CA-Culprit also generates branch instructions to internal sequence numbers (INTSEQ-4) in order to preserve the logic of the original expression.
|
Copyright © 2014 CA.
All rights reserved.
|
|