|
ALTSEQ is the way to go. It IS file-level, so it is used for all key fields, EXCEPT for those that have the NOALTSEQ keyword on them. In the following it says that ALTSEQ is not valid with binary, packed, and floating point. I don't know if this invalidates for the entire composite key, or just for individual fields. From the DDS Reference The ALTSEQ keyword is not valid under the following conditions: - When you specify FILETYPE(*SRC) on the Create Physical File (CRTPF) or Create Logical File (CRTLF) commands. - When key fields have a data type of packed decimal, binary, or floating-point. - When key fields are specified with ABSVAL or SIGNED. For those fields, NOALTSEQ (a key field-level keyword) is assumed and does not need to be specified. You can specify NOALTSEQ for any field in a composite key that does not require the alternative sequence. - When you specify a value other than *SRC on the SRTSEQ parameter on the Create Physical File (CRTPF) or Create Logical File (CRTLF) command. The ALTSEQ keyword cannot be specified with the REFACCPTH keyword. ALTSEQ causes zoned key fields to default to unsigned sequence. You can override the default by specifying the SIGNED keyword for individual key fields. At 08:31 AM 9/14/02 -0400, you wrote:
Gary, Check out the ALTSEQ keyword in DDS. However be careful, because this is a file-level keyword and will apply to the all the fields in your file. Bill --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.