×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Karl, sorry this is late, I'm getting caught up here.

QUSERMSG is not an object anywhere on our systems.  I'm guessing this is a
home-grown message file.  I'm fairly certain these are not IBM messages.

Seeing that *LIBL is referenced, I'd do a WRKOBJ *ALL/QUSERMSG to see if
it's out there, but just not in that user's library list.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Lauritzen, Karl
Sent: Friday, May 03, 2002 7:30 PM
To: 'midrange-l@midrange.com'
Subject: UML Messages


I getting a lot of these in user job logs. I have no idea what they are.
Should I be concerned?
Where can I find these?

I do a WRKOBJ on the message of qusermsg and I get nothing.

Only one user is getting these. I suspect he may be doing something I am
unaware of.


Message identifier UML2108 not found in message file QUSERMSG in *LIBL
Message identifier UML8003 not found in message file QUSERMSG in *LIBL
Message identifier UML9002 not found in message file QUSERMSG in *LIBL
Message identifier UML9002 not found in message file QUSERMSG in *LIBL
Message identifier UML9002 not found in message file QUSERMSG in *LIBL
Message identifier UML2113 not found in message file QUSERMSG in *LIBL

Karl Lauritzen Jr.
National Lloyds Insurance
American Summit Insurance



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