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


  • Subject: RE: changing defaults?
  • From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
  • Date: Fri, 26 Nov 1999 22:56:19 -0500

>Barbara,

Our re-create program does the following:

        - Archives our old command to our ARCHIVES library
        - Re-duplicates the command from QSYS to our library
        - Re-applies the CHGCMDDFTs

This procedure prevents problems with IBM changing the CPP-- we always have
the latest version.

--Paul E Musselman
PaulMmn@ix.netcom.com




Barbara wrote, in part:

>But you run the risk of the interface between the command and its CPP.
>changing.  If you are lucky, your version of the command would break
>noisily.  If you are unlucky, it would fail silently (appear to run
>fine, but not do what you want).
>
>A better way is to add your CHGCMDDFT to a CL program that you run
>whenever you get a new release of OS/400.
>
>It's still a good idea to leave the original command alone and only
>change a copy though.  Even better is give a new name to the version
>with different defaults.
>
>Barbara Morris



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.