NCL supports the retrieval of data across any number of alternate indexes. However, data updating is restricted to the base cluster for delimited format files. If a record that has been retrieved using an alternate index is to be updated, the ID operand on the &FILE statement is used to indicate that processing has swapped to the base cluster, and that the necessary key must be set (either on an &FILE SET or on the &FILE PUT) before the record can be written back to the UDB.
Even when using the base cluster, the base key must start at offset 0 within the record (RKP 0) for a UDB (or DELIMITED) format file. No updating is allowed for any cluster which violates this rule.
This restriction does not apply to unmapped format UDBs which can be updated even if the key does not start at offset 0. In this case if insufficient data is supplied to the left of the start of the key, null padding (X'00') is added up to the start of the key location.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |