×
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.
On 24 Jan 2013 07:52, Mike Cunningham wrote:
This is going to date us for how long we have been on this platform.
Our QCLSRC and QDDSSRC files have an attribute of PF38-SRC. This
attribute setting is preventing us from using Rational to edit the
source. What's going to be the best way to get rid of that attribute?
You can't just change it. There is no command to do that. So we are
thinking rename QCLSRC to something else, create a new QCLSRC then
copy every member over to the new file. 2,076 members in QCLSRC and
13,304 members in QDDSSRC. Would anyone have any other options to
make this change?
There should be no reason to make the change; i.e. I would consider
it a defect that the editor could not support them as a source file,
because there is no legitimate reason [it is just one bit in the file
header].
But if making the change, best to use save\restore instead of copying
the data. Restore the members and data of the saved database source
physical file [with the System/38 attribute] into a new database source
PF file previously created with the same name, record length, and owner
using OPTION(*OLD) MBROPT(*NEW) ALWOBJDIF(*FILELVL) FILEMBR((QCLSRC
*ALL) (QDDSSRC *ALL)). Best before the restore to also have issued a
GRTOBJAUT with REFOBJ from the old version of the file to the newly
created file; that can be done after, but duplicates some effort across
all members that would already have been done during restore processing.
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.