You cannot specify COMPRESS(*NO) for the cases discussed in this
topic.
You cannot specify COMPRESS(*NO) for the following types of access paths
over the to-file, including when the access path is contained in a logical
file and is based on the to-file member:
- Unique keys (you specified the UNIQUE keyword in the DDS).
- Select or omit specifications without the DYNSLT keyword (in the DDS for
the file), and immediate or delayed maintenance (MAINT(*IMMED) or MAINT(*DLY)
specified on the CRTPF or CRTLF command).
- Floating-point key field or logical numeric key field (in the DDS for
the file), and immediate or delayed maintenance (MAINT(*IMMED) or MAINT(*DLY)
specified on the CRTPF or CRTLF command). Note that a logical numeric key
field comply is one of the following fields:
- A numeric key field in a logical file
- A field specified as a to field on the JFLD keyword that has different
attributes than in the based-on physical file
- A field specified as a sequencing field on the JDUPSEQ keyword that has
different attributes than in the based-on physical file
You cannot specify COMPRESS(*NO) for any of the following cases:
- If you use the JRNPF command to journal the to-file
- If the to-file member is in use or if any access path over the to-file
member is in use
- If you specify an EOFDLY wait time for the from-file on an OVRDBF command