|
Hello Diane, You wrote: >The MATRMD header file will be fixed in the release following V5R1. Do >you need a fix for earlier releases? No. It's not a serious problem and the fact that it wasn't reported probably indicates that no one in customer land is using it. I know how expensive PTFs are to ship so save the money for something important. I'll remember it is broken and fix it on 450 and 510. For this exercise I created my own header (since the IBM supplied files in QSYSINC have the allow update attribute turned off). If I really want to fix it in the QSYSINC header. I'll just patch my header file member to have the same member level ID as the IBM one, save the member, and then restore it over the top of the IBM one. Done this before so I know it works. I had to resort to this because I couldn't find the extra bits that set the internal IBM allow update flag that was preventing me from editing it directly. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.