| Author |
Message
|
| sriramkothuri |
 Posted: Tue Jul 22, 2003 7:33 am Post subject: How to change the Time stamp for Logs |
 |
|
Newbie
Joined: 04 Apr 2003
Posts: 8
|
How can we change the the timestamp on queue manager log files.Currently it is showing GMT ,we would like to have it changed to EST.
Is this configurable at MQ level or OS level(.profile)? |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue Jul 22, 2003 7:47 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I havent seen this before and neither do i think there is a way out. From my understanding, MQ gets the local time of the system. So, if you set it to GMT you would get the respective output in the logs. Likewise for EST, i guess. Not 100% sure though.
Cheers
Kumar |
|
| Back to top |
|
|
| sriramkothuri |
| Posted: Tue Jul 22, 2003 11:23 am Post subject: |
|
|
Newbie
Joined: 04 Apr 2003
Posts: 8
|
The server on which mq is running the time is EST but the log files for queue manager errors are having GMT has time stamp.
rs52$ pwd
/var/mqm/qmgrs/MBRS52/errors
rs52$ ls -ltr
total 1360
-rw-rw-rw- 1 mqm mqm 256054 Jul 18 05:29 AMQERR03.LOG
-rw-rw-rw- 1 mqm mqm 256622 Jul 20 02:40 AMQERR02.LOG
-rw-rw-rw- 1 mqm mqm 178556 Jul 22 13:33 AMQERR01.LOG
rs52$ tail AMQERR01.LOG
None.
-------------------------------------------------------------------------------
07/22/03 17:33:57
AMQ9001: Channel program ended normally.
EXPLANATION:
Channel program 'P0.MBRS52/FLOGWY' ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
rs52$ |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jul 22, 2003 11:35 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Not sure whats wrong here. But per my experience Mq uses the system time for each and everything and there is nothing to configure or change it. And you should see the same time in the logs. So, i would go back and check again to confirm that the system time is infact what i think ought be.
Also, you posted the log times, but never posted the system time. So i cannot say there is a problem here.
Cheers
Kumar |
|
| Back to top |
|
|
| sriramkothuri |
| Posted: Tue Jul 22, 2003 11:39 am Post subject: |
|
|
Newbie
Joined: 04 Apr 2003
Posts: 8
|
Kumar
If you look at the ls -ltr output ,the time stamp for AMQERRo1.log as
july 22 13:33
and the amq error message timestamp is 17:33.
Thanks |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jul 22, 2003 11:46 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
What is your TZ env. variable set too ??? if not set like the following set it
then restart the qmgr.
For EST/EDT time
export TZ=EST5EDT
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jul 22, 2003 11:47 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Sorry i missed that out.
Try this.
Write up a small program in c, to get the system time and see the output to check if it makes any difference. It surely looks like there is something out of whack here, but as i said before MQ uses the local system time.
The other suggestion would be to somehow force an FFST to occur. Verify the time the FD file shows to see if that matches with the system time or the time you expect.
Cheers
Kumar |
|
| Back to top |
|
|
| sriramkothuri |
| Posted: Tue Jul 22, 2003 11:48 am Post subject: |
|
|
Newbie
Joined: 04 Apr 2003
Posts: 8
|
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jul 22, 2003 11:53 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Do you know how TZ is set and if it is set during MQSeries startup.
The fastest way to try it is to restart the queue manager from the command line where you know the ENV variable is set.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| sriramkothuri |
| Posted: Tue Jul 22, 2003 11:54 am Post subject: |
|
|
Newbie
Joined: 04 Apr 2003
Posts: 8
|
Here is the contents of FDC file
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- Sunday July 20 04:03:50 GMT 2003
Host Name :- rs52 (AIX 4.3)
PIDS :- 5724B4101
LVLS :- 530.3 CSD03
Product Long Name :- WebSphere MQ for AIX
Vendor :- IBM
Probe Id :- XC338001
Application Name :- MQM
Component :- xehAsySignalHandler
Build Date :- Mar 4 2003
CMVC level :- p530-CSD03J
Build Type :- IKAP - (Production)
UserID :- 00010083 (mqm)
Program Name :- runmqdlq
Process :- 00272138
Thread :- 00000002
Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL
Minor Errorcode :- OK
Probe Type :- MSGAMQ6209
Probe Severity :- 3
Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred.
FDCSequenceNumber :- 0
Arith1 :- 15 f
Arith2 :- 272138 4270a
Comment1 :- SIGTERM |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jul 22, 2003 11:56 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well here is an FDC from one our HPUX boxes
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Tuesday June 24 16:07:35 EDT 2003 |
| Host Name :- ppsdev (HP-UX B.11.11) |
| PIDS :- 5765B74 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for HP-UX |
| Vendor :- IBM |
| Probe Id :- ZL000028 |
| Application Name :- MQM |
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
