× 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.



Hello Rob,

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!  To make matters worse there are two sets of bits; the ones a
customer can set with the ALWUPD and ALWDLT parameters and an IBM
internal set.

You could patch the various allow flags but I solved this problem for
QWSRTVOI by using RSTOBJ.  It will restore a replacement member if you
get the file level identifier correct.  Here are the steps you need to
perform:

        Create a work file in which to make the source changes.  This
file must have the same name as the include file to want to change.
                CRTSRCPF  my-lib/inc-file
        Copy the broken source member from the include file to the work
file.
                CPYSRCF   qsysinc/inc-file my-lib/inc-file inc-mbr
        Make the appropriate source changes in the work file.
                STRSEU ...
        Determine the file level identifier of the include file
                DSPFD     qsysinc/inc-file
                and look for something like:
                File level identifier . . . . . . . . . . . :
0981209114910
        STRSST
                1-Start service tool
                4-Display/Alter/Dump
                1-Display/Alter storage
                1-Machine Interface (MI) object
                25-Space (19)
                        type the work file name
                        type the work library name
                        press Enter

                        Scroll down and find offset x'013D' which is
where the file level identifier is stored.
                        Change it to match the one you determined
earlier.  Just type the new values over the existing values in the text
area on the right-hand-side of the display.  Then press F11.
                        Press F3 until Exit and then press Enter
        Change the owner of the work file to be the same as the owner of
the include file.  This will be QSYS and is done to avoid ALWOBJDIF
requirements.
                CHGOBJOWN   my-lib/inc-file *FILE QSYS
        Create a save file
                CRTSAVF QTEMP/JUNK
        Save the work file and member
                SAVOBJ OBJ(inc-file) LIB(my-lib) DEV(*SAVF)
SAVF(QTEMP/JUNK) +
                        FILEMBR((inc-file (inc-mbr)))
        Rename the original broken member
                RNMM   qsysinc/inc-file inc-mbr new-mbr
        Restore the patched member
                RSTOBJ OBJ(inc-file) SAVLIB(my-lib) DEV(*SAVF)
SAVF(QTEMP/JUNK) +
                        FILEMBR((inc-file (inc-mbr))) RSTLIB(qsysinc)

Bingo! A new fixed member in QSYSINC.  The usual caveats apply and you
have to be god to this.

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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.