To All,

I've just had the misfortune to have to redo the entries in a binding
directory.  I didn't create them and they had hardcoded library names.  I
wanted to change the library name to *LIBL.

There is no CHGBNDDIRE but the ADDBNDDIRE has a *REPLACE option but that
requires you to type the full identifier of the item to replace.

WRKBNDDIR doesn't really help because it restricts option 1 to the
extended action line thus forcing you to key in all the parameters as if
you were using ADDBNDDIRE from the command line.

What IDIOT designed this?  How could System DCG or Usability let this sort
of crap out in public?  Whoever is responsible for this junk interface
should be forced to used it for a few days.

It is actually easier to write a CL script that does DSPBNDDIR to an
outfile, does RMVBNDDIRE *ALL, and then reads the outfile performing an
ADDBNDDIRE for each entry changing the parameters as required.  That's not
how usability is supposed to work.

I notice a creeping tendency to omit a CHG command and use a *REPLACE
option on many OS functions.  For example, ADDEXITPGM springs to mind, and
there are APIs that behave this way too.  Well, just stop it Rochester,
you'll go blind!

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-Ups:

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

This mailing list archive is Copyright 1997-2022 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.