• Subject: Re: show message on line 24
  • From: "James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 29 Mar 2001 21:19:29 -0800
  • Organization: Progressive Data Systems, Inc.

Dan,

As you do, for an application a separate message file is appropriate,
but since I'm not at my AS/400 I'm going to ask a dumb question: Do all
entries in QCPFMSG _have_ to start with CPF?  I don't think so.

So how about this:  You write a small CL utility program.  Upon an error
you want to display your own message DCL1001 (Dan's CL message 1001). 
Is it possible to MONMSG that the message was not found, call another CL
that adds the message to QCPFMSG and upon return your utility CL loops
back to show the message?  So you write a program (ADDDCLMSG or some
such) and pass to it which message that needs to be added and this way
you also have a single program that contains all of your own utility
messages?

This way even an OS upgrade would be self refreshing with user messages?

Just a thought.

D.BALE@handleman.com wrote:
> 
<<snip>>
> 
> I just know someone's gonna ask, well why not just create the message file?
> (Hey, Leif, why didn't you just create a message file?)  Maybe I'm just lazy,
> but I just think it's overkill to create a message file for a single-app
> utility.  I _do_ define message files for entire "application systems" that
> I've designed and written in the past.  But for the simple CL utility program?
>  Eh...
<<snip>>
+---
| 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.