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



Hi Rob,

The  message subfile does not include everything in the user's joblog, just the messages in the program's message queue.

And for these programs, the only messages are the ones the users need to see, or at least, the relevant messages are the ones that show up first in the message subfile.

I'm actually running on memory here; I haven't seen one in use recently.  In fact, the program I looked at has the message subfile code unchanged since 1994!

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 9/2/2020 4:13 AM, Rob Berendt wrote:
It sounds like your "users" are much more adept than most. Looking at joblogs trying to resolve errors and all. Normally that would fall in the IT realm to look at that level.
If they are this good then why not show them Run SQL Scripts and have them run something like this instead?

Select
ORDINAL_POSITION, -- A unique number for each row that indicates the time order of messages in the job log.
MESSAGE_ID, -- The message ID for this message.
MESSAGE_TYPE, -- Type of message.
MESSAGE_SUBTYPE, -- Subtype of message.
SEVERITY, -- The severity assigned to the message.
MESSAGE_TIMESTAMP, -- The timestamp for when the message was issued.
FROM_LIBRARY, -- The library containing the program or service program that sent the message.
FROM_PROGRAM, -- The program or service program name that sent the message.
FROM_MODULE, -- The module that sent the message.
FROM_PROCEDURE, -- The procedure that sent the message.
FROM_INSTRUCTION, -- The instruction that sent the message.
TO_LIBRARY, -- The library containing the program or service program that received the message
TO_PROGRAM, -- The program or service program name that received the message.
TO_MODULE, -- The module that received the message.
TO_PROCEDURE, -- The procedure that received the message.
TO_INSTRUCTION, -- The instruction that received the message.
FROM_USER, -- The userid of the job when the message was sent.
MESSAGE_FILE, -- The message file containing the message.
MESSAGE_LIBRARY, -- The name of the library containing the message file.
MESSAGE_TOKEN_LENGTH, -- The length of the MESSAGE_TOKENS string.
MESSAGE_TOKENS, -- The message token string. If the value is longer than 2048 characters, it will be truncated with no warning.
MESSAGE_TEXT, -- The first level text of the message including tokens.
MESSAGE_SECOND_LEVEL_TEXT -- The second level text of the message including tokens.
from table(qsys2.joblog_info('794178/ROB/ROBHQ1')) A
where message_id not in('CPI9160', 'CPI9200')
order by ordinal_position desc;


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.