× 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: errmsgid keyword--unexpected results
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Fri, 13 Jul 2001 08:26:27 -0700

I saw that one.  I wondered about it since the build the subfile routine
starts with a write to the subfile control record to clear the subfile, but
the thing that fooled me was that when doing the same thing for the other
search argument, the error message behaved the way I thought it should.  

When I started on the 400, I was taught to avoid putovr and its friends--the
rationale being that we had at least a 56K data stream everywhere and didn't
need to economize and deal with the additional complexity.  Looks like I
should have learned something about it anyway.  One of my coworkers asked me
"Are you using putovr?"  I thought I wasn't.  <g>

-----Original Message-----
From: Simon Coulter [mailto:shc@flybynight.com.au]
Sent: Thursday, July 12, 2001 6:04 PM
To: MIDRANGE-L@midrange.com
Subject: Re: errmsgid keyword--unexpected results


M
Hello Joel,

You wrote:
>The other thing I'm curious about is documentation.  I spent a fair amount
>of time looking at both the DDS manual and the Display Programming manual.
>Is this covered in the parts related to PUTOVR et. al.?  I didn't think to
>look there.

I think earlier (as in S/38) documentation explained the relationship 
between ERRMSG, ERRMSGID, PUTOVR, etc. but I've known it for at least 12 
years.  The only reference I could find which hints at your problem is the 
following quote from the Restrictions and Notes section of the DDS manual 
under ERRMSG and ERRMSGID.

"For input or output capable fields, ERRMSG and ERRMSGID are in effect only 
if the record containing the field for which they are specified is already 
on the display."

Section 2.7.1.1 of the Application Display Programming manual also describes

this behaviour.

Regards,
Simon Coulter.

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