Example of information for sizing - syncsort_capacity_management - 12.60

AVM900I   16,308  RECORDS READ         SIZE IS    66.80 MB
AVM901I   64,485  RECORDS IN WORK      SIZE IS    7.04 MB
AVM902I   71,550  RECORDS IN AVMDATA   SIZE IS    6.11 MB

These messages are produced by Acquire and show the quantity of data read in, the quantity that translated to in the WORKxx files, plus the size of data written out.

If you provided a control card of COMPRESS=Y you will also see this message:

AVM903I INLINE COMPRESSION CPU=0.266     SAVED   7.20 MB

This shows the trade-off between CPU and output file size. An additional 0.266 CPU seconds took 7.2 MB off the output file size, which otherwise would have been 13.31 MB in size

If you coded a USS path you will see this message:

AVM904I 20100429000253_aszv00050002.1010  SIZE IS   5.90 MB

This shows the file name written to and the size of that file. The two file sizes (AVMDATA and USS) will be close to each other, as they contain the same information, but will never exactly the same. Data sent to AVMDATA is always slightly larger as it is a RECFM=VB file and the 4 byte lengths of records and blocks con­tribute to the total file size, whereas USS is a continuous stream of bytes, with records delimited by New Line characters (x‘15’).

If you also coded a USSCOMP=Y control card the AVM904I message will look like this:

AVM904I 20100429000253_ezzv00050002.1010  SIZE IS   0.83 MB

You can see the slightly different file name generated to inform Control Center this is compressed data in EBCDIC, and also see the greatly reduced size of the com­pressed USS file.