|
Mark, Darren is right, this problem will be fixed in SP3. You can view the full APAR text here: http://as400service.ibm.com/n_dir/nas4apar.NSF/4bed1015550802c186256a8800493bcb/d3972fc284cf9c0686256a940079f148?OpenDocument Thanks, Violaine Batthish CODE Project Lead batthish@ca.ibm.com IBMCA(BATTHISH) WDT/400 page: http://www.ibm.com/software/ad/wdt400 WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support darren@dekko.com Sent by: To: code400-l@midrange.com code400-l-admin@mi cc: drange.com Subject: Re: Why??? 10/05/2001 09:34 AM Please respond to code400-l That error is a well known booboo in CODE that is fixed in SP3. I know because I installed SP3 before all the installation problems were discovered and it was pulled back by IBM, and it does not occur for me anymore. MWalter@hanoverwir e.com To: code400-l@midrange.com Sent by: cc: code400-l-admin@mi Fax to: drange.com Subject: Why??? 10/05/2001 08:25 AM Please respond to code400-l >Good Morning all, >I don't know why little things bother me. But here goes. >Why is CODE/400 showing the following code in error? > c evalr ohhead = %trim(fmarr(dmn)) + ' ' + > c %trim(%editc(*year:'Z')) >RNF5272E Either a valid Operation Code or Conditioning-Indicator entry must >be specified. > >I delete the message and the source compiles and runs fine. > > >Thanks, > >Mark _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l.
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.