×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
CRPence wrote:
If information is required of the SQL sequence, the database SQL
interfaces provided to access details about the sequence should be
utilized & referenced. For example, there is the SYSSEQ catalog VIEW
in QSYS2.
I just realized that the information in the SYSSEQUENCES table does not actually provide enough information to recreate the sequence item.
For instance ... if you create a sequence and specify an increment of 1 that it should cache 10 values ... and use the sequence once ... the last assigned sequence column will contain a value 10 times the increment value ... even though the sequence was only used once. I'm assuming the cached values are stored in the data area.
Oddly enough ... I noticed that, if you alter the sequence to turn OFF the cache, the maximum assigned value in the SYSSEQUENCES table does *not* get fixed ... and the next value generated by the sequence will be based off the last cached value.
david
This mailing list archive is Copyright 1997-2024 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.
midrange.com
