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



If by "resolved" you mean that the msg text is filled in, yes, I think the 
dspjoblog pgm gets it from the *msgf when you display the joblog.

If you write a msg from your own *msgf (not QCPFMSG) then delete the *msgf, 
you'll see "Message file not found" instead of the text.  Then if you 
recreate the *msgf, the text for that same msg will magically reappear.

--Dave

On Friday 19 March 2004 06:59, Ted Slate wrote:
>
> <snip>
>
> Just curious
> -  I'm seeing the messages stored in the user's qjobmsgq but un-resolved. 
> Are they actually stored resolved anywhere or do the dspjoblog pgms resolve
> them first before display.
>
> Thanks.
>
>
> From: "Dennis Lovelady" <dennislovelady@xxxxxxxxxxxxx>
>
> >Reply-To: MI Programming on the AS400 / iSeries <mi400@xxxxxxxxxxxx>
> >To: "MI Programming on the AS400 / iSeries" <mi400@xxxxxxxxxxxx>
> >Subject: Re: [MI400] QCMDEXC errors
> >Date: Wed, 17 Mar 2004 09:44:11 -0500
>
> From: "Ted Slate" <tslateone@xxxxxxxxxxx>
>
> >Sent: Wednesday, March 17, 2004 9:06 AM
> >
> > > I'm trying to get the error message occurring after a QCMDEXC call and
> > > failure.  <snip>
> > > Unfortunately, the only message I can seem to trap are the ones from
> > > prompted calls. For example, if I call RPG pgm "A" while "A" is in my
> >
> >stack
> >
> >I would suggest using QCAPCMD instead; opens up a number of possibilities.
> >--
> >Dennis Lovelady


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