|
|
|
The IUI can recognize sequential data sets which have been compressed using a noncustom technique or an FDT generated by the IUI, but which have not yet been implemented (that is, registered to the Control File). These have commonly been implemented using the SUBSYS JCL parameter under earlier versions. The IUI marks them COMPRESD in the work list and fills in the FDT or algorithm name if available. Because they are already compressed, they must be implemented differently from uncompressed data sets.
Because the sequential data sets are already compressed, instead of being analyzed they must be implemented exactly as they are compressed. Without recompression, they must be recognized as already compressed the next time they are accessed, whether for input or output.
The IUI internally enters the correct implementation line command for a compressed data set. With no further action on your part, implementation is attempted on the compressed data set when you select Implement from the Task menu.
If the IUI knows the correct FDT or algorithm, you cannot change it. If the IUI could not determine the correct FDT or algorithm, you must enter it on the Implementation panel. If the FDT is not found on the Control File or if the ICB does not match, it is rejected and the implementation is not performed. If you have the correct FDT in a load library, you can add it to the Control File and try the implementation again.
Because the data set is compressed, the uncompressed DCB attributes are unavailable, so you must supply them, by supplying either a DCBMODEL data set or the individual attributes on the Implementation panel, shown previously. You can override selected attributes in the DCBMODEL data set by supplying them on the panel.
| Copyright © 2012 CA. All rights reserved. |
|