

Executing PAEZIP/ARCHIVE OPTION(*DSP) command will display the above panel. This is the control center for archiving objects. Any time you want to know what the status of an object is, look at this panel. Any time you want to change any of the control fields look at this panel. The control fields on this panel are:
User Option:
*AUTO will automatically decompress object if touched, *USER indicates that the user will be asked if the object should be decompressed. It will be the users decision to decompress or not to decompress. The person who touched the object is the one getting the message..
CMP:
Compression is N = normal or X = maximum. Normal compression does not take to long but the compression is not dense. Maximum compression is slower but the compression is more dense, thus saving more space. If Member processing is desired, X=maximum compress is mandatory. Normal compression will not work for member processing.
HLD:
Hold determines if an object should be compressed. N = object will be compressed or Y = object is held and will not be compressed until changed to a N. Objects that are placed into the archive file by the PAEZIP/ARCHIVERPT (*FILE) will automatically be given a Y indicating that the object will NOT be compressed until it is changed to N. This also gives you the ability to control when a particular object is to be compressed. User Option above controls decompression.
MBR:
Members are to be processed individually. This in important when source files like QCLSRC is to be archived on a member basis. Member archiving is ideal place to use the control field. Member decompress will not take very long because of the size of the member.
DLY DAYS:
Number of days an object is not to be touched by the compression routine. 5 = do not touch the object for the next 5 days. After that, the object can be compressed. For example, let say that you were working an accounts payable program in QRPGSRC. It would not no sense to constantly compress and decompress this member daily. Determine how long that you would be working on this RPG member. Let's say that it would take you a week to complete the changes to the program, then change DLY DAYS to 7 or 8. That will indicate that the member will not be compressed or decompressed for that number of days.
PAEZIP/ARCHIVE command help text in HTML
PAEZIP/ARCHIVE command help text in Text
There is help text for each field on the panel. The Status field will display the current status of each record in the Archive file. After running the PAEZIP/ARCHIVERPT OPTION(*FILE), the status will be suspended. In order to start archiving an object, the HLD field will have to be changed to "N" from "Y". A "Y" is the default when objects are first entered into the Archive file when the PAEZIP/ARCHIVERPT OPTION(*FILE) is executed. ARCHIVERPT *FILE is the method of loading the Archive File automatically. However, you can add library/object name in by hand. The next time the command PAEZIP/ARCHIVE OPTION(*COMP) is executed, ISM will check each record in the file to see if the object(s) needs to be archived. Notice the below two panels which show objects which are suspended.
PAEZIP/ARCHIVERPT command help text in HTML
When you execute PAEZIP/ARCHIVERPT OPTION(*FILE) or OPTION(*REPORT) the system defaults are used unless you change the parms in the command itself. Changing the parms in the command are only temporary. These defaults can be changed by pressing F10 on the Object Archive Management Panel.

System Defaults help Text, HTML format
System Defaults help Text, Text format
Notice below that the command PAEZIP/ARCHIVE OPTION(*COMP) was executed. It compressed those objects that were to be archived because HLD had been changed to "N". Remember, "Y" says not to archive object. "N" says the object should be archived.

The first time an object is touched in some manner. For example, if the object is a physical file (PF), a program accessed the PF or a query is executed against the PF. Just about any function that touches the file will cause the file to be restored. See, the Dynamic Retrieval Section for those commands that will not dynamically/automatically decompress a compressed object. Notice below that the status of LMDOBJPF file is RESTORED. This indicates that the file had been compressed (Archived) but the file was touched so ISM restored (decompressed ) the file dynamically/automatically. The user did not have to do anything. It is all done dynamically/automatically.


The above example shows the object has a status of Pending. That object will be compressed the next time compression is scheduled to run. Compression is scheduled in the FREE IBM job scheduling system. To view when compression is scheduled to run, execute WRKJOBSCDE PAEARCHIVE command. The execution time or attributes can be changed with the CHGJOBSCDE PAEARCHIVE command. In this example, the compression is scheduled to execute everyday at 3AM in the morning. Compression is slower than decompression so it is wise to have the compression scheduled when there is less activity on the system.

IBM has provided a table in their Planning for HSM manual SG24-4450-01. The following is copyrighted by IBM and is presented to explain how dynamic retrieval is implemented in OS/400. To view this table click below.
Commands that effect Dynamic Retrieval