|
Actually the motivation behind disallowing changes was to prevent a user from modifying the include file and then having the modification disappear when they upgraded to the next release. What you point out is an unintended, though useful, side effect of having the file read only. Bruce "Simon Coulter" <shc@flybynight.c To: rpg400-l@midrange.com om.au> cc: Sent by: Subject: Re: QSYSINC/QRPGSRC,QUSRSPLA rpg400-l-admin@mi drange.com 11/28/2002 06:17 AM Please respond to rpg400-l You cannot change the members in the IBM-supplied includes -- all the includes have bits set in the object header which disallow changes. Rochester does that so they don't have to support calls from sites where the problem is really that the includes were changed by an idiot -- they make enough errors on their own without supporting customer mistakes too!...
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.