|
Our GL "last update number used" is approaching its 7-digit max, and my fear is that either (1) it won't quietly roll on its own after 9999999, or (2) it will, and we'll have a zero which would indicate that the transaction remains unprocessed. I can do a Maintain Application Control (31/GLU) to change the number, but the question is - can we just shut down the GL subsystem, set the last update number to 0000001 and restart the subsystem without a hitch? Has anyone else had to do this? TIA, -BobE bob.ellsworth@xxxxxxxxxx Pollak Engineered Products _________________________________________________________________ This electronic mail transmission contains confidential information intended only for the person(s) and/or organization named. Any use, distribution, copying or disclosure by or to any other person outside your organization is strictly prohibited. If you received this transmission in error, please send an electronic mail message to postmaster@xxxxxxxxxx so we may instruct you regarding its disposition.
As an Amazon Associate we earn from qualifying purchases.
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
