A RANK statement is invalid in the same run as an EXCEPTION, OUTPUT, LIST(BOTH), or PLOT control statement. These are mutually exclusive functions.
The total amount of storage required for the RANK reports requested in a single step should not exceed 640 KB. This is the product of the total number of lines in the RANK reports and the length of the records passed to the RANK report generation process. If this storage exceeds 640 KB, a warning message will be issued, and the reports will be truncated.
The RANK statement separates statements executed on the first pass from those executed on the second pass. Only fields that are specified on the LIST statement are available in the second pass, so the fields on which the report is to be ranked must be specified in the LIST statement. The only fields that can be referenced in the second pass, other than those specified in the LIST statement are:
Note: The RANK statement can work on individual records as they are read into CA JARS Wizard and processed before the SORT/BREAK (detail level) or after they go through SORT/BREAK processing (summary level).
To RANK at the detail level, use COMPUTE(P) statements for any calculations on the field(s) to be RANKed.
To RANK at the summary level, use all COMPUTE (but not COMPUTE(P)) statements for any calculations on the fields(s) to be RANKed.
Detail example:
COMPUTE(P) 1.CPU/TIME = 1.CPU/TIME / 1000 COMPUTE(P) CPU RATIO(B) (3) (.6) = 1.CPU/TIME / 1.ELAPSED/TIME SORT BREAK USERID, DATE, CPU RATIO RANK 20, CPU RATIO LIST USERID, DATE, 1.CPU/TIME, 1.ELAPSED/TIME, CPU RATIO(L10)
Summary example:
SORT BREAK USERID, DATE, CPU RATIO COMPUTE 1.CPU/TIME = 1.CPU/TIME / 1000 COMPUTE CPU RATIO(8) (3) (.6) = 1.CPU/TIME / 1.ELAPSED/TIME RANK 20, CPU RATIO LIST USERID, DATE, 1.CPU/TIME, 1.ELAPSED/TIME, CPU RATIO(L10)
| Copyright © 2012 CA. All rights reserved. |
|