| Author |
Message
|
| BrianMc |
 Posted: Fri Jan 31, 2003 12:48 am Post subject: AMQERR01.LOG and switching date |
 |
|
Apprentice
Joined: 01 Oct 2002
Posts: 33
Location: Ireland
|
Hi.
In my AMQERR01.LOG files the date keeps "switching". I have cut and paste a section of the log. Notice the date going from 01/29/03 to 29/01/03 and "pm" appears!
01/29/03 12:05:49
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'XXXX.TO.YYYY' closed because no messages arrived on the
transmission queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
01/29/03 12:05:49
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'XXXX.TO.YYYY' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
29/01/03 12:06:32 PM
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'YYYY.TO.XXXX' closed because no messages arrived on the
transmission queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
29/01/03 12:06:32 PM
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'YYYY.TO.XXXX' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
Any ideas?
Brian. |
|
| Back to top |
|
 |
| bduncan |
| Posted: Fri Jan 31, 2003 9:38 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Huh.. Never noticed that (and I've browsed many an MQ log!) but I wonder if it's just a locality issue. Most places (feel free to jump on me if I'm wrong) use the DD/MM/YYYY format, while those of us in the U.S. (along with the "english" measurement system, steering wheels on the left side of our cars, etc.) like to do it MM/DD/YYYY. Presumeably MQSeries utilizes the locality of the server it's running on to figure out how to format its logs. But perhaps there are a few places in the code that aren't utilizing it. Who knows... It would be interesting to see what your log looks like later in the day. 12pm happened not to be a good number, because it's the same in military time. I'm guessing that if you saw this switch around 4pm, you'd see it go between 4:00:00pm and 16:00:00, because again, it seems most places use what us Yanks call military time...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| BrianMc |
| Posted: Mon Feb 03, 2003 3:32 am Post subject: |
|
|
Apprentice
Joined: 01 Oct 2002
Posts: 33
Location: Ireland
|
The switch happens several times throughout the day. Here is another example:
01/29/03 15:35:31
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'XXXX.TO.YYYY' started.
ACTION:
None.
-------------------------------------------------------------------------------
29/01/03 03:35:37 PM
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'YYYY.TO.XXXX' started.
ACTION:
None.
-------------------------------------------------------------------------------
01/29/03 15:55:13
AMQ7467: The oldest log file required to start queue manager XXXX is
S0000002.LOG.
EXPLANATION:
The log file S0000002.LOG contains the oldest log record required to restart
the queue manager. Log records older than this may be required for media
recovery.
ACTION:
You can move log files older than S0000002.LOG to an archive medium to release
space in the log directory. If you move any of the log files required to
recreate objects from their media images, you will have to restore them to
recreate the objects.
-------------------------------------------------------------------------------
Would it be worth my while opening a call with IBM?
Brian. |
|
| Back to top |
|
|
| bduncan |
| Posted: Mon Feb 03, 2003 1:40 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
It's probably not harming anything, but I'm sure IBM would be interested to know if their logging is prone to this problem. Especially if you have some application parsing the logs and generating graphs or whatever... You want to have the right time points...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| nimconsult |
| Posted: Mon Feb 03, 2003 11:03 pm Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
Isn't it something like different processes with different locales are writing to the log?
I do not have this mix with exactly the same messages, so I suppose there is something specific with this installation.
Hey I just have one idea: It seems that messages related to channels are different from the others.
Do you start the listener with "runmqlsr"? With which user? My guess would be that the user starting the "runmqlsr" has some different locale.
Are you talking about the Windows platform?
Nicolas
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| BrianMc |
| Posted: Tue Feb 04, 2003 6:34 am Post subject: |
|
|
Apprentice
Joined: 01 Oct 2002
Posts: 33
Location: Ireland
|
Thanks guys,
The "switching" is occurring on a Sun Solaris box V8.1 and MQ V5.1
It seems to be happening when the Mainframe to Server channel is started or ends.
01/29/03 12:05:49
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'Sun Solaris.TO.Mainframe' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
29/01/03 12:06:32 PM
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'Mainframe.TO.Sun Solaris' closed because no messages arrived on the
transmission queue within the disconnect interval period.
ACTION:
None.
-------------------------------------------------------------------------------
29/01/03 12:06:32 PM
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'Mainframe.TO.Sun Solaris' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
01/29/03 12:13:04
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'Sun Solaris.TO.Mainframe' started.
ACTION:
None.
I have checked the date on the server and it is correct. The listener is running in my inetd.conf file. I got that checked and it is configured the same on all servers and this is the only one with the problem!
Could it be the application? |
|
| Back to top |
|
|
|
|
