× 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: *DATE on DSPF program
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Thu, 17 Sep 1998 11:57:14 -0400
  • Organization: commsoft

On Wednesday, September 16, 1998 2:10 PM, Leland, David 
[SMTP:dleland@Harter.com] wrote:
> I've posted this problem one other time but I was hopeful at the time
> that it would be resolved by IBM.  Well, I've officially received the
> word that it "works as designed".  So, now I'd like to know what you
> think.

Ask for the manual pages that would tell you this.

> Background:
> 1)  Date data types can be placed on Display Files as of V4R2M0
> (finally!)
> 2)  Error checking of date data types on display files is handled by the
> internal error checker (terrific!)
-snip-
> What do you think, should the program receive this error?  When you
> answer the error with a "D", the dump doesn't have the invalid date in
> it, but the original.

No, the program should not recieve this error.

> IBM's answer is that the date is in the "buffer" (whatever that is) and
> that the internal error checker checks twice - once when enter was
> pressed with the invalid date and again when the F3 (CA03) is pressed.

The RNX0112 message is NOT issued by the DDS validity checker; it is 
issued by the RPG ILE runtime modules.  Don't believe me?  Add a *PSSR and 
a DUMP to your code and watch as this "DDS validation error" gets trapped 
by the runtime code.

C     *PSSR         BEGSR
C                   Eval      PgmStat=%Status
C     'P'           DUMP
C                   Movel     '*CANCL'      Action            6
C                   ENDSR     Action

>what IBM told me is that is DOES work like the "VALUES" DDS
>keyword.  My question to them was, then why don't I receive a program
>error when I go through the exact same steps with a field on a screen
>with VALUES field validation?
>
>I couldn't get a straight answer on that one.

That's because the Date validity checking is NOT consistent with VALUES 
validity checking!

Keep the problem open until they make it consistent or show you the manual 
pages that describe the current behaviour.  As a work-around, you *might* 
consider adding a *PSSR, a test for status 00112 and a RETURN...

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

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


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.