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


  1.  Home
  2. RPG400-L
  3. January 2002

Re: Compile default

>From: Mike.Collins@syan.co.uk
>Date: Mon, 14 Jan 2002 17:10:18 +0000
> ...
>CHGCMDDFT CRTBNDRPG NEWDFT('FIXNBR(xyz)'). You may wish to create a
>duplicate object of the command in a library above QSYS so that your new
>default is not eradicated when you upgrade OS/400.

Using the old *CMD in the next release will probably cause the
command to fail if any new command parameters have been added,
or any parameters have been changed.  (This has been the case for
the last few releases of RPG.)

A better way to handle future releases is to have a CL program
with the CRTDUPOBJs and CHGCMDDFTs.  Then you just run that CL
when you get a new release.

Lori, for your FIXNBR case, I wouldn't change the command default.  It
allows _all_ decimal data errors in files to go undetected by _all_
programs.  If it wasn't possible to fix up individual files, I'd limit
the damage by just specifying FIXNBR in the H spec of whatever program
needed it.

Barbara Morris

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.