Personally, I really don't see a use for the ALWDLT, ALWUPD pair.  A 
static table that you want people to really jump through hoops if they 
want to change it, like (perhaps a bad example) the 50 states and their 
abbreviations.  But any QSECOFR can get around that with DLTF and by 
recreating it.  Same as a process to rebuild an audit file, something I 
feel better left up to journals.
But if you really want that, and the ability to do edit codes, then, by 
all means, submit a DCR.
https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change?OpenForm
For both, you should submit two different DCR's.
Still, all-in-all, SQL has a lot less limitations than DDS directly.  Like 
constraints, etc.
Will they start enhancing DDS in the future?  I'd sooner bet on the return 
of the 8-track.  Then again, CL was pretty dead until recent releases of 
V5.
Rob Berendt
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.