Re: show message on line 24 -- MIDRANGE-L

James,

No, QCPFMSG does not require all message IDs begin with CPF*.  In fact, IBM
uses a bunch of different ones in QCPFMSG: CAE, CPA, CPC, CPD, CPE, CPF, CPG,
CPI, CPP, CPX, CPZ, KBD, KEY, MCH, OPT, QWM, QWX.

So, let's say I pick DJBnnnn.  I'd be concerned that IBM may use DJB in the
future.

Plus, any upgrade is going to replace the old QCPFMSG object.  Oops, just read
the rest of your post.  Yes, I guess that could work, as long as you didn't
have to worry about IBM using DCL1001 in the future.  Even if I didn't have to
worry about that though, in my mind, it's another level of complexity added
where I'd rather stay with the KISS principle.

However, I will say that I see a valuable use for that in my apps that do use
their own message file.  Well, I think I do - I'll have to flesh that out a
little more.  I won't go into detail here, but it has to do with maintaining a
message file.  Hint:  IBM could have made life so much easier if they'da added
Option 3=Copy on the WRKMSGD command.  But since they didn't, all the
maintenance I do on my own message files comes from a CL program that has all
the ADDMSGD's for each message description I have in the file.  So if I want
to copy a message to a new one and modify it from there, I have to do that in
SEU on the CLP source.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
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
+---