Re: Do go looking for FDCs when "nothing" is wrong?
If I remember correctly, that watertower is actually in Northern California. Railtown 1897, in Jamestown near Yosemite. My biggest problem with FDCs is that if I'm working late and logged in on the mqm id, then forget to log out, when that connection times out mq generates an FDC and I get paged after getting to sleep as I have a cron that checks for new FDC files and pages for production systems. You'd think I'd learn not to forget. Bill William M. Pigg Bill Pigg/San Jose/IBM [EMAIL PROTECTED] 408.717.7076 pager: 408-552-0012, http://www.arch.com/message [EMAIL PROTECTED] Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Do go looking for FDCs when "nothing" is wrong? I can make it through a day with out an FDC file, but I never could have made it through puberty with out Petticoat Junction! Ya think that water tower is anywhere in Georgia? Couldn't resist in having a little fun! Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Robert Broderick <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Re: Do go looking for FDCs when "nothing" is wrong? List <[EMAIL PROTECTED] .AC.AT> 01/09/2004 10:09 AM Please respond to MQSeries List WHO Starski and Hutch OH CRAP I've dated myself!!! OH Well I'll just hop in the GENERAL and scoot over to Petticote Junction to hide in the water tower with the girls bobbee >From: earMERC Roberts <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: Do go looking for FDCs when "nothing" is wrong? >Date: Fri, 9 Jan 2004 09:45:39 -0500 > >Watch yourself there! HuggyBear is a personal friend of mine. A couple of >detectives might come looking for you soon. > >:<[) > >Ernest Roberts >IT - Sr Sys Prog >MBUSA, LLC > > >- Forwarded by Ernest Roberts/171/DCAG/DCX on 01/09/2004 09:45 AM - > > Robert Broderick > <[EMAIL PROTECTED] To: >[EMAIL PROTECTED] > OTMAIL.COM> cc: > Sent by: MQSeries Subject: Re: Do go >looking for FDCs when "nothing" is wrong? > List > <[EMAIL PROTECTED] > .AC.AT> > > > 01/09/2004 08:12 > AM > Please respond to > MQSeries List > > > > > > >AAAH!!! But then the IBM addiction would subside. Not a good thing for >a >pusher!! Remember the guy "Huggy Bear" from that show long ago. I believe >he >now works for IBM as their Marketing Management Director. (He still has the >outlandish outfits on too00. Upsets prople at the board meetings!!!). And >you wonder where all this good marketing comes from!! > >Going back to something less serious. FDC can be like rabbits. BUT the will >be caused by some problem somewhere. I don't think the code has a random >FDC >generator built in. "FULL TIME JOB" maybe and maybe not. I just think it is >better to err on the side of caution. I also don't think you could possibly >track and debug all the FDC but it is nice to be warned that they are >occuring. ESP when you start getting repeated EMAILs righ after you did an >upgrade or installed some idiots application. > > > bobbee > > > >From: Bill Anderson <[EMAIL PROTECTED]> > >Reply-To: MQSeries List <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: Do go looking for FDCs when "nothing" is wrong? > >Date: Thu, 8 Jan 2004 15:15:25 -0500 > > > >I second the motion on the new manual thing. Help me help myself, and I > >don't have to clog up the Passport Advantage line with yet another phone > >call > > > >Bill Anderson > >Senior Systems Analyst > >SITA Atlanta, GA > >770-303-3503 (office) > >404-915-3190 (cell) > >[EMAIL PROTECTED] > >http://www.mconnect.aero/ > > > > > > > > "Potkay, Peter M > > (PLC, IT)" To: > >[EMAIL PROTECTED] > > <[EMAIL PROTECTED] cc: > > RTFORD.COM> Subject: Re: Do go > >looking for FDCs when "not
Re: Do go looking for FDCs when "nothing" is wrong?
I can make it through a day with out an FDC file, but I never could have made it through puberty with out Petticoat Junction! Ya think that water tower is anywhere in Georgia? Couldn't resist in having a little fun! Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Re: Do go looking for FDCs when "nothing" is wrong? List <[EMAIL PROTECTED] .AC.AT> 01/09/2004 10:09 AM Please respond to MQSeries List WHO Starski and Hutch OH CRAP I've dated myself!!! OH Well I'll just hop in the GENERAL and scoot over to Petticote Junction to hide in the water tower with the girls bobbee >From: earMERC Roberts <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: Do go looking for FDCs when "nothing" is wrong? >Date: Fri, 9 Jan 2004 09:45:39 -0500 > >Watch yourself there! HuggyBear is a personal friend of mine. A couple of >detectives might come looking for you soon. > >:<[) > >Ernest Roberts >IT - Sr Sys Prog >MBUSA, LLC > > >- Forwarded by Ernest Roberts/171/DCAG/DCX on 01/09/2004 09:45 AM - > > Robert Broderick > <[EMAIL PROTECTED] To: >[EMAIL PROTECTED] > OTMAIL.COM>cc: > Sent by: MQSeries Subject: Re: Do go >looking for FDCs when "nothing" is wrong? > List > <[EMAIL PROTECTED] > .AC.AT> > > > 01/09/2004 08:12 > AM > Please respond to > MQSeries List > > > > > > >AAAH!!! But then the IBM addiction would subside. Not a good thing for >a >pusher!! Remember the guy "Huggy Bear" from that show long ago. I believe >he >now works for IBM as their Marketing Management Director. (He still has the >outlandish outfits on too00. Upsets prople at the board meetings!!!). And >you wonder where all this good marketing comes from!! > >Going back to something less serious. FDC can be like rabbits. BUT the will >be caused by some problem somewhere. I don't think the code has a random >FDC >generator built in. "FULL TIME JOB" maybe and maybe not. I just think it is >better to err on the side of caution. I also don't think you could possibly >track and debug all the FDC but it is nice to be warned that they are >occuring. ESP when you start getting repeated EMAILs righ after you did an >upgrade or installed some idiots application. > > >bobbee > > > >From: Bill Anderson <[EMAIL PROTECTED]> > >Reply-To: MQSeries List <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: Do go looking for FDCs when "nothing" is wrong? > >Date: Thu, 8 Jan 2004 15:15:25 -0500 > > > >I second the motion on the new manual thing. Help me help myself, and I > >don't have to clog up the Passport Advantage line with yet another phone > >call > > > >Bill Anderson > >Senior Systems Analyst > >SITA Atlanta, GA > >770-303-3503 (office) > >404-915-3190 (cell) > >[EMAIL PROTECTED] > >http://www.mconnect.aero/ > > > > > > > > "Potkay, Peter M > > (PLC, IT)" To: > >[EMAIL PROTECTED] > > <[EMAIL PROTECTED]cc: > > RTFORD.COM>Subject: Re: Do go > >looking for FDCs when "nothing" is wrong? > > Sent by: MQSeries > > List > > <[EMAIL PROTECTED] > > AC.AT> > > > > > > 01/08/2004 02:55 PM > > Please respond to > > MQSeries List > > > > > > > > > > > > > >You know, I was thinking to myself looking at these FDCs "Holy cr*p, this > >whole place is about to fall apart right before my eyes!!!".
Re: Do go looking for FDCs when "nothing" is wrong?
WHO Starski and Hutch
OH CRAP I've dated myself!!!
OH Well I'll just hop in the GENERAL and scoot over to Petticote Junction to
hide in the water tower with the girls
bobbee
From: earMERC Roberts <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Do go looking for FDCs when "nothing" is wrong?
Date: Fri, 9 Jan 2004 09:45:39 -0500
Watch yourself there! HuggyBear is a personal friend of mine. A couple of
detectives might come looking for you soon.
:<[)
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
- Forwarded by Ernest Roberts/171/DCAG/DCX on 01/09/2004 09:45 AM -
Robert Broderick
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
OTMAIL.COM>cc:
Sent by: MQSeries Subject: Re: Do go
looking for FDCs when "nothing" is wrong?
List
<[EMAIL PROTECTED]
.AC.AT>
01/09/2004 08:12
AM
Please respond to
MQSeries List
AAAH!!! But then the IBM addiction would subside. Not a good thing for
a
pusher!! Remember the guy "Huggy Bear" from that show long ago. I believe
he
now works for IBM as their Marketing Management Director. (He still has the
outlandish outfits on too00. Upsets prople at the board meetings!!!). And
you wonder where all this good marketing comes from!!
Going back to something less serious. FDC can be like rabbits. BUT the will
be caused by some problem somewhere. I don't think the code has a random
FDC
generator built in. "FULL TIME JOB" maybe and maybe not. I just think it is
better to err on the side of caution. I also don't think you could possibly
track and debug all the FDC but it is nice to be warned that they are
occuring. ESP when you start getting repeated EMAILs righ after you did an
upgrade or installed some idiots application.
bobbee
>From: Bill Anderson <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Do go looking for FDCs when "nothing" is wrong?
>Date: Thu, 8 Jan 2004 15:15:25 -0500
>
>I second the motion on the new manual thing. Help me help myself, and I
>don't have to clog up the Passport Advantage line with yet another phone
>call
>
>Bill Anderson
>Senior Systems Analyst
>SITA Atlanta, GA
>770-303-3503 (office)
>404-915-3190 (cell)
>[EMAIL PROTECTED]
>http://www.mconnect.aero/
>
>
>
> "Potkay, Peter M
> (PLC, IT)" To:
>[EMAIL PROTECTED]
> <[EMAIL PROTECTED]cc:
> RTFORD.COM>Subject: Re: Do go
>looking for FDCs when "nothing" is wrong?
> Sent by: MQSeries
> List
> <[EMAIL PROTECTED]
> AC.AT>
>
>
> 01/08/2004 02:55 PM
> Please respond to
> MQSeries List
>
>
>
>
>
>
>You know, I was thinking to myself looking at these FDCs "Holy cr*p, this
>whole place is about to fall apart right before my eyes!!!". But I went
and
>actually looked at all my prod QMs. About 40% have no FDCs. The other 40%
>have some, but only at the rate of maybe 1 or 2 every 3 months. A couple
>here and there were weird (like 30 FDCs in a minute a year ago and
nothing
>since).
>
>The queue managers that are running on Windows 2000 machines under
control
>of MSCS are loaded with FDCs. Like 10 or 20 a month.
>
>I am going to focus on those, even though "nothing" is wrong. Maybe IBM
>will
>be able to help me flip a switch somewhere which would cause 90% of those
>to
>go away. I just hesitate to do it because nothing seems wrong, and this
>could turn into a full time job. Oh well, look out bullet, cuz I'm about
to
>bite ya!
>
>
>If I can get it to the point where we only see 1 or 2 FDCs a month, I
think
>an email with the servername in question when an FDC is thrown is a good
>idea. A great idea would be the ability to actually understand FDCs. A
new
>manual perhaps? Please? :)
>
>
>
>
>-Original Message-
>From: Robert Broderick [mailto:[EMAIL PROTECTED]
>Sent: Thursday, January 08, 2004 2:03 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Do go looking for FDCs when "nothing"
Re: Do go looking for FDCs when "nothing" is wrong?
Watch yourself there! HuggyBear is a personal friend of mine. A couple of detectives might come looking for you soon. :<[) Ernest Roberts IT - Sr Sys Prog MBUSA, LLC - Forwarded by Ernest Roberts/171/DCAG/DCX on 01/09/2004 09:45 AM - Robert Broderick <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OTMAIL.COM>cc: Sent by: MQSeries Subject: Re: Do go looking for FDCs when "nothing" is wrong? List <[EMAIL PROTECTED] .AC.AT> 01/09/2004 08:12 AM Please respond to MQSeries List AAAH!!! But then the IBM addiction would subside. Not a good thing for a pusher!! Remember the guy "Huggy Bear" from that show long ago. I believe he now works for IBM as their Marketing Management Director. (He still has the outlandish outfits on too00. Upsets prople at the board meetings!!!). And you wonder where all this good marketing comes from!! Going back to something less serious. FDC can be like rabbits. BUT the will be caused by some problem somewhere. I don't think the code has a random FDC generator built in. "FULL TIME JOB" maybe and maybe not. I just think it is better to err on the side of caution. I also don't think you could possibly track and debug all the FDC but it is nice to be warned that they are occuring. ESP when you start getting repeated EMAILs righ after you did an upgrade or installed some idiots application. bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 15:15:25 -0500 > >I second the motion on the new manual thing. Help me help myself, and I >don't have to clog up the Passport Advantage line with yet another phone >call > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > > > > "Potkay, Peter M > (PLC, IT)" To: >[EMAIL PROTECTED] > <[EMAIL PROTECTED]cc: > RTFORD.COM>Subject: Re: Do go >looking for FDCs when "nothing" is wrong? > Sent by: MQSeries > List > <[EMAIL PROTECTED] > AC.AT> > > > 01/08/2004 02:55 PM > Please respond to > MQSeries List > > > > > > >You know, I was thinking to myself looking at these FDCs "Holy cr*p, this >whole place is about to fall apart right before my eyes!!!". But I went and >actually looked at all my prod QMs. About 40% have no FDCs. The other 40% >have some, but only at the rate of maybe 1 or 2 every 3 months. A couple >here and there were weird (like 30 FDCs in a minute a year ago and nothing >since). > >The queue managers that are running on Windows 2000 machines under control >of MSCS are loaded with FDCs. Like 10 or 20 a month. > >I am going to focus on those, even though "nothing" is wrong. Maybe IBM >will >be able to help me flip a switch somewhere which would cause 90% of those >to >go away. I just hesitate to do it because nothing seems wrong, and this >could turn into a full time job. Oh well, look out bullet, cuz I'm about to >bite ya! > > >If I can get it to the point where we only see 1 or 2 FDCs a month, I think >an email with the servername in question when an FDC is thrown is a good >idea. A great idea would be the ability to actually understand FDCs. A new >manual perhaps? Please? :) > > > > >-Original Message- >From: Robert Broderick [mailto:[EMAIL PROTECTED] >Sent: Thursday, January 08, 2004 2:03 PM >To: [EMAIL PROTECTED] >Subject: Re: Do go looking for FDCs when "nothing" is wrong? > > >I don't know. I have had sites where I showed up the first day and the file >systems were pretty full because of the FDC issues. But as things got under >control and the environment stabilized the issue of FDC's showing up became >became lees of an issue if non-existent. I don't recall being iat a site >where the FDC continued to run "out of hand" after making the environment >"well". > >bobbee > > > >From: Bill Anderson <[EMAIL PROTECTED]> >
Re: Do go looking for FDCs when "nothing" is wrong?
We have a script that monitors for FDC's, it looks for new files in the relevant directories and sends an email to the support team if necessary. Matt. -Original Message- From: Conklin, William [mailto:[EMAIL PROTECTED] Sent: 09 January 2004 13:31 To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? Matt, When you say you monitor for the FDC's, do you have an automatic way to this or just take a peek occasionally? Thanks Bill C. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 5:23 AM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I tend to agree. I take all FDC's very seriously. We monitor for them. The only one's that I tend to ignore without contacting IBM are those where an application connected locally to the queue manager has crashed (due to non mq related problems), these can be determined by the process name in the FDC. If FDC's are generated when they shouldn't be, then I would imagine that IBM would be keen to hear about those so they can get the code fixed. Matt. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 08 January 2004 19:03 To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive == This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. == Instruction
Re: Do go looking for FDCs when "nothing" is wrong?
Matt, When you say you monitor for the FDC's, do you have an automatic way to this or just take a peek occasionally? Thanks Bill C. -Original Message- From: Gurney, Matthew [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 5:23 AM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I tend to agree. I take all FDC's very seriously. We monitor for them. The only one's that I tend to ignore without contacting IBM are those where an application connected locally to the queue manager has crashed (due to non mq related problems), these can be determined by the process name in the FDC. If FDC's are generated when they shouldn't be, then I would imagine that IBM would be keen to hear about those so they can get the code fixed. Matt. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 08 January 2004 19:03 To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive == This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. == Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
AAAH!!! But then the IBM addiction would subside. Not a good thing for a
pusher!! Remember the guy "Huggy Bear" from that show long ago. I believe he
now works for IBM as their Marketing Management Director. (He still has the
outlandish outfits on too00. Upsets prople at the board meetings!!!). And
you wonder where all this good marketing comes from!!
Going back to something less serious. FDC can be like rabbits. BUT the will
be caused by some problem somewhere. I don't think the code has a random FDC
generator built in. "FULL TIME JOB" maybe and maybe not. I just think it is
better to err on the side of caution. I also don't think you could possibly
track and debug all the FDC but it is nice to be warned that they are
occuring. ESP when you start getting repeated EMAILs righ after you did an
upgrade or installed some idiots application.
bobbee
From: Bill Anderson <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Do go looking for FDCs when "nothing" is wrong?
Date: Thu, 8 Jan 2004 15:15:25 -0500
I second the motion on the new manual thing. Help me help myself, and I
don't have to clog up the Passport Advantage line with yet another phone
call
Bill Anderson
Senior Systems Analyst
SITA Atlanta, GA
770-303-3503 (office)
404-915-3190 (cell)
[EMAIL PROTECTED]
http://www.mconnect.aero/
"Potkay, Peter M
(PLC, IT)" To:
[EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
RTFORD.COM> Subject: Re: Do go
looking for FDCs when "nothing" is wrong?
Sent by: MQSeries
List
<[EMAIL PROTECTED]
AC.AT>
01/08/2004 02:55 PM
Please respond to
MQSeries List
You know, I was thinking to myself looking at these FDCs "Holy cr*p, this
whole place is about to fall apart right before my eyes!!!". But I went and
actually looked at all my prod QMs. About 40% have no FDCs. The other 40%
have some, but only at the rate of maybe 1 or 2 every 3 months. A couple
here and there were weird (like 30 FDCs in a minute a year ago and nothing
since).
The queue managers that are running on Windows 2000 machines under control
of MSCS are loaded with FDCs. Like 10 or 20 a month.
I am going to focus on those, even though "nothing" is wrong. Maybe IBM
will
be able to help me flip a switch somewhere which would cause 90% of those
to
go away. I just hesitate to do it because nothing seems wrong, and this
could turn into a full time job. Oh well, look out bullet, cuz I'm about to
bite ya!
If I can get it to the point where we only see 1 or 2 FDCs a month, I think
an email with the servername in question when an FDC is thrown is a good
idea. A great idea would be the ability to actually understand FDCs. A new
manual perhaps? Please? :)
-Original Message-
From: Robert Broderick [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 2:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Do go looking for FDCs when "nothing" is wrong?
I don't know. I have had sites where I showed up the first day and the file
systems were pretty full because of the FDC issues. But as things got under
control and the environment stabilized the issue of FDC's showing up became
became lees of an issue if non-existent. I don't recall being iat a site
where the FDC continued to run "out of hand" after making the environment
"well".
bobbee
>From: Bill Anderson <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Do go looking for FDCs when "nothing" is wrong?
>Date: Thu, 8 Jan 2004 13:20:17 -0500
>
>I just had to ring in on this one. The thing is, the queue manager seems
to
>have sort of a "hair trigger" in regard to what sort of problems cause it
>to write an FDC file. I find them often, and have no way of quickly
>determining why it (more commonly they) are there. If I got serious about
>hunting them down every time, I could make a career out of It. It doesn't
>help any that little or no documentation exists on how to effectively
>troubleshoot using one. On more than one occasion I have opened a ticket
>with IBM to help me solve a problem where FDC files were produced, and
had
>a 2nd level support person tell me to send them, but they don't often
>contain much useful data.
>
>I do think it is wise to automate handling them. I need to find the time
to
>write a script that not only finds them but potentially parses them and
>write things like the date / time stamp, program name, and probe
>descript
Re: Do go looking for FDCs when "nothing" is wrong?
I tend to agree. I take all FDC's very seriously. We monitor for them. The only one's that I tend to ignore without contacting IBM are those where an application connected locally to the queue manager has crashed (due to non mq related problems), these can be determined by the process name in the FDC. If FDC's are generated when they shouldn't be, then I would imagine that IBM would be keen to hear about those so they can get the code fixed. Matt. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 08 January 2004 19:03 To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive == This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. == Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
I do! In my experience they (almost) always indicate some sort of a problem (even if it's just a flaky network connection bringing a channel down). Dave Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
I think there are cases where the product doesn't have a good error message to generate and defaults to an FDC file. I have had a couple instances (one I believe was when I was using incorrect SSL settings and connecting as a client) where the qmgr threw FDCs which were a result of errors in my application. That' why I sometimes ignore FDCs. I could go to IBM support for each of these, but many times they correlate to some error or problem that is obvious. Ideally mq would generate a more friendly error, but this may not always be possible. Nick -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Potkay, Peter M (PLC, IT) Sent: Thursday, January 08, 2004 11:55 AM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? You know, I was thinking to myself looking at these FDCs "Holy cr*p, this whole place is about to fall apart right before my eyes!!!". But I went and actually looked at all my prod QMs. About 40% have no FDCs. The other 40% have some, but only at the rate of maybe 1 or 2 every 3 months. A couple here and there were weird (like 30 FDCs in a minute a year ago and nothing since). The queue managers that are running on Windows 2000 machines under control of MSCS are loaded with FDCs. Like 10 or 20 a month. I am going to focus on those, even though "nothing" is wrong. Maybe IBM will be able to help me flip a switch somewhere which would cause 90% of those to go away. I just hesitate to do it because nothing seems wrong, and this could turn into a full time job. Oh well, look out bullet, cuz I'm about to bite ya! If I can get it to the point where we only see 1 or 2 FDCs a month, I think an email with the servername in question when an FDC is thrown is a good idea. A great idea would be the ability to actually understand FDCs. A new manual perhaps? Please? :) -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 2:03 PM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are
Re: Do go looking for FDCs when "nothing" is wrong?
I second the motion on the new manual thing. Help me help myself, and I don't have to clog up the Passport Advantage line with yet another phone call Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ "Potkay, Peter M (PLC, IT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: RTFORD.COM> Subject: Re: Do go looking for FDCs when "nothing" is wrong? Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 01/08/2004 02:55 PM Please respond to MQSeries List You know, I was thinking to myself looking at these FDCs "Holy cr*p, this whole place is about to fall apart right before my eyes!!!". But I went and actually looked at all my prod QMs. About 40% have no FDCs. The other 40% have some, but only at the rate of maybe 1 or 2 every 3 months. A couple here and there were weird (like 30 FDCs in a minute a year ago and nothing since). The queue managers that are running on Windows 2000 machines under control of MSCS are loaded with FDCs. Like 10 or 20 a month. I am going to focus on those, even though "nothing" is wrong. Maybe IBM will be able to help me flip a switch somewhere which would cause 90% of those to go away. I just hesitate to do it because nothing seems wrong, and this could turn into a full time job. Oh well, look out bullet, cuz I'm about to bite ya! If I can get it to the point where we only see 1 or 2 FDCs a month, I think an email with the servername in question when an FDC is thrown is a good idea. A great idea would be the ability to actually understand FDCs. A new manual perhaps? Please? :) -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 2:03 PM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Ins
Re: Do go looking for FDCs when "nothing" is wrong?
You know, I was thinking to myself looking at these FDCs "Holy cr*p, this whole place is about to fall apart right before my eyes!!!". But I went and actually looked at all my prod QMs. About 40% have no FDCs. The other 40% have some, but only at the rate of maybe 1 or 2 every 3 months. A couple here and there were weird (like 30 FDCs in a minute a year ago and nothing since). The queue managers that are running on Windows 2000 machines under control of MSCS are loaded with FDCs. Like 10 or 20 a month. I am going to focus on those, even though "nothing" is wrong. Maybe IBM will be able to help me flip a switch somewhere which would cause 90% of those to go away. I just hesitate to do it because nothing seems wrong, and this could turn into a full time job. Oh well, look out bullet, cuz I'm about to bite ya! If I can get it to the point where we only see 1 or 2 FDCs a month, I think an email with the servername in question when an FDC is thrown is a good idea. A great idea would be the ability to actually understand FDCs. A new manual perhaps? Please? :) -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 2:03 PM To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee >From: Bill Anderson <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Do go looking for FDCs when "nothing" is wrong? >Date: Thu, 8 Jan 2004 13:20:17 -0500 > >I just had to ring in on this one. The thing is, the queue manager seems to >have sort of a "hair trigger" in regard to what sort of problems cause it >to write an FDC file. I find them often, and have no way of quickly >determining why it (more commonly they) are there. If I got serious about >hunting them down every time, I could make a career out of It. It doesn't >help any that little or no documentation exists on how to effectively >troubleshoot using one. On more than one occasion I have opened a ticket >with IBM to help me solve a problem where FDC files were produced, and had >a 2nd level support person tell me to send them, but they don't often >contain much useful data. > >I do think it is wise to automate handling them. I need to find the time to >write a script that not only finds them but potentially parses them and >write things like the date / time stamp, program name, and probe >description (just to name a few) to a log file that could be imported into >a spread sheet. Then you could look for trends. If something specific >continues to occur over and over, that would be justification to launch a >science project to determine why, and fix it. > >I would love to know enough about FDC files to write a program, or Perl >script that could parse hundreds of them and write a report based on some >key data. But that's not likely to wind up on my project plan list any time >soon! > > >Cheers > >Bill Anderson >Senior Systems Analyst >SITA Atlanta, GA >770-303-3503 (office) >404-915-3190 (cell) >[EMAIL PROTECTED] >http://www.mconnect.aero/ > >Instructions for managing your mailing list subscription are provided in >the Listserv General Users Guide available at http://www.lsoft.com >Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
I don't know. I have had sites where I showed up the first day and the file systems were pretty full because of the FDC issues. But as things got under control and the environment stabilized the issue of FDC's showing up became became lees of an issue if non-existent. I don't recall being iat a site where the FDC continued to run "out of hand" after making the environment "well". bobbee From: Bill Anderson <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Do go looking for FDCs when "nothing" is wrong? Date: Thu, 8 Jan 2004 13:20:17 -0500 I just had to ring in on this one. The thing is, the queue manager seems to have sort of a "hair trigger" in regard to what sort of problems cause it to write an FDC file. I find them often, and have no way of quickly determining why it (more commonly they) are there. If I got serious about hunting them down every time, I could make a career out of It. It doesn't help any that little or no documentation exists on how to effectively troubleshoot using one. On more than one occasion I have opened a ticket with IBM to help me solve a problem where FDC files were produced, and had a 2nd level support person tell me to send them, but they don't often contain much useful data. I do think it is wise to automate handling them. I need to find the time to write a script that not only finds them but potentially parses them and write things like the date / time stamp, program name, and probe description (just to name a few) to a log file that could be imported into a spread sheet. Then you could look for trends. If something specific continues to occur over and over, that would be justification to launch a science project to determine why, and fix it. I would love to know enough about FDC files to write a program, or Perl script that could parse hundreds of them and write a report based on some key data. But that's not likely to wind up on my project plan list any time soon! Cheers Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Tired of slow downloads? Compare online deals from your local high-speed providers now. https://broadband.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
Ditto on that Nick -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bill Anderson Sent: Thursday, January 08, 2004 10:20 AM To: [EMAIL PROTECTED] Subject: Do go looking for FDCs when "nothing" is wrong? I just had to ring in on this one. The thing is, the queue manager seems to have sort of a "hair trigger" in regard to what sort of problems cause it to write an FDC file. I find them often, and have no way of quickly determining why it (more commonly they) are there. If I got serious about hunting them down every time, I could make a career out of It. It doesn't help any that little or no documentation exists on how to effectively troubleshoot using one. On more than one occasion I have opened a ticket with IBM to help me solve a problem where FDC files were produced, and had a 2nd level support person tell me to send them, but they don't often contain much useful data. I do think it is wise to automate handling them. I need to find the time to write a script that not only finds them but potentially parses them and write things like the date / time stamp, program name, and probe description (just to name a few) to a log file that could be imported into a spread sheet. Then you could look for trends. If something specific continues to occur over and over, that would be justification to launch a science project to determine why, and fix it. I would love to know enough about FDC files to write a program, or Perl script that could parse hundreds of them and write a report based on some key data. But that's not likely to wind up on my project plan list any time soon! Cheers Bill Anderson Senior Systems Analyst SITA Atlanta, GA 770-303-3503 (office) 404-915-3190 (cell) [EMAIL PROTECTED] http://www.mconnect.aero/ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
Peter, Lets just say that "No FDC is a good FDC". So while there may be a good reason to ignore FDC's unless you have an issue. How do you know you are arguing with a 500 pound black bear in the dark unless he "reaches out and touches you" Not a pleasant thing if you have ever been there. Proactive monitoring and the ole "Stich in time saves your arse" is a good way to go. Have I looked at the dir and said WOW where did these come from and deleted them? Yes. But not on production. Here is where you can qualify things. I am in financials. So if you get a flag in production. Act on it. The transfer you may have saved today will keep your job tomorrow. Doing this on QA?? I have seen sites where QA quickly becomes production in the thick of things. Try explaining to the snr. mgt WHY the QA QMGR cannot be used in an emergency. Remember also QA is where the Business people are shacking things down. These are also the people (not your imed manager) who control your source of income. ENOUGH SAID!!! The dev box??? Tough luck dev guys!! (hahaha) This one depends on how busy you are and how critical things get. All said an done, I don't like some wise guy (or GAL) coming up to me infront of people and making me look bad by pointing out somethings I should know. So I like the little script there that EMAILs a warning about the creation of a file. Also being in contact with IBM support about your FDC gives you a chance to excercise your invested support dollars AND maybe learn something you didn't know before from some IBM MQSeries wiseguy!!! bobbee From: "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Do go looking for FDCs when "nothing" is wrong? Date: Thu, 8 Jan 2004 12:29:27 -0500 Peter, I bet you get responses all over the place on this one! Personally, while I usually only worry about looking at the FDCs right away at if there is a problem, I do have a script that runs regularly on each qmgr machine and checks for FDCs and lets me know if there are any. And then I will take a look at the them. And I have seen places that actively monitor the error directories for FDCs. --Rebecca Rebecca Bullock Computer Sciences Corporation MFCoE/Newark CS Team Educational Testing Service Account Princeton, NJ 08541 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 12:04 PM To: [EMAIL PROTECTED] Subject: Do go looking for FDCs when "nothing" is wrong? I was just poking around on one server, and I happened to find a ton of FDCs. I went to look at the QA version of this server, and there were FDCs. The production version - FDCs. I started looking at other unrelated queue managers - about half had at least one FDC! Some had 20 or 30, some in one day, other spread out over the years. All are 5.3 CSD04. Both Solaris and Windows. The worst ones were the queue managers participating in Microsoft Clusters. Based on this, I feel like there is a ton of stuff that needs fixing. The first thing you do when you have major problem is go look for the inevitable FDC. BUT, everything seems fine! There are no issues, MQ keeps working, all application areas are happy. Do you guys generally go looking for problems by trying to debug FDCs? Maybe even have monitoring tools alert you anytime any FDC is created anywhere? Or unless there is a symptom of a problem elsewhere, should I just ignore them? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. Instructions for managing your mailing list subscription are provided in the Listserv General Users Gui
Re: Do go looking for FDCs when "nothing" is wrong?
Peter, I bet you get responses all over the place on this one! Personally, while I usually only worry about looking at the FDCs right away at if there is a problem, I do have a script that runs regularly on each qmgr machine and checks for FDCs and lets me know if there are any. And then I will take a look at the them. And I have seen places that actively monitor the error directories for FDCs. --Rebecca Rebecca Bullock Computer Sciences Corporation MFCoE/Newark CS Team Educational Testing Service Account Princeton, NJ 08541 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Thursday, January 08, 2004 12:04 PM To: [EMAIL PROTECTED] Subject: Do go looking for FDCs when "nothing" is wrong? I was just poking around on one server, and I happened to find a ton of FDCs. I went to look at the QA version of this server, and there were FDCs. The production version - FDCs. I started looking at other unrelated queue managers - about half had at least one FDC! Some had 20 or 30, some in one day, other spread out over the years. All are 5.3 CSD04. Both Solaris and Windows. The worst ones were the queue managers participating in Microsoft Clusters. Based on this, I feel like there is a ton of stuff that needs fixing. The first thing you do when you have major problem is go look for the inevitable FDC. BUT, everything seems fine! There are no issues, MQ keeps working, all application areas are happy. Do you guys generally go looking for problems by trying to debug FDCs? Maybe even have monitoring tools alert you anytime any FDC is created anywhere? Or unless there is a symptom of a problem elsewhere, should I just ignore them? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
Hi Ok, add me to the list that DOES NOT go looking for trouble when there is no indication of any:) Actually, I have had many circumstances when FDC's get thrown on a regular basis but are not indicative of a "real" problem. For consistent ones, I would use MQSeries support to at least (hopefully!) verify the potential reasons for the FDC's. I have some systems that I have needed to run clean up scripts because the FDC's get quite annoying and take up a lot of space. The reasons vary (but are basically innocent) and with some diligence and maybe some application clean up work, you may be able to stop the causes but in our case, we threw in the towel on a few and just use the scripts to clean up. Thanks Dan -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (PLC, IT) Sent: Thursday, January 08, 2004 12:04 PM To: [EMAIL PROTECTED] Subject: Do go looking for FDCs when "nothing" is wrong? I was just poking around on one server, and I happened to find a ton of FDCs. I went to look at the QA version of this server, and there were FDCs. The production version - FDCs. I started looking at other unrelated queue managers - about half had at least one FDC! Some had 20 or 30, some in one day, other spread out over the years. All are 5.3 CSD04. Both Solaris and Windows. The worst ones were the queue managers participating in Microsoft Clusters. Based on this, I feel like there is a ton of stuff that needs fixing. The first thing you do when you have major problem is go look for the inevitable FDC. BUT, everything seems fine! There are no issues, MQ keeps working, all application areas are happy. Do you guys generally go looking for problems by trying to debug FDCs? Maybe even have monitoring tools alert you anytime any FDC is created anywhere? Or unless there is a symptom of a problem elsewhere, should I just ignore them? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Do go looking for FDCs when "nothing" is wrong?
I run a scheduled job that looks for FDC's, then renames them and emails me. I record the incidents in an Excel spreadsheet and, if they start to repeat, then I do research for a solution. "Potkay, Peter M (PLC, IT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: RTFORD.COM> Subject: Do go looking for FDCs when "nothing" is wrong? Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 01/08/2004 12:03 PM Please respond to MQSeries List I was just poking around on one server, and I happened to find a ton of FDCs. I went to look at the QA version of this server, and there were FDCs. The production version - FDCs. I started looking at other unrelated queue managers - about half had at least one FDC! Some had 20 or 30, some in one day, other spread out over the years. All are 5.3 CSD04. Both Solaris and Windows. The worst ones were the queue managers participating in Microsoft Clusters. Based on this, I feel like there is a ton of stuff that needs fixing. The first thing you do when you have major problem is go look for the inevitable FDC. BUT, everything seems fine! There are no issues, MQ keeps working, all application areas are happy. Do you guys generally go looking for problems by trying to debug FDCs? Maybe even have monitoring tools alert you anytime any FDC is created anywhere? Or unless there is a symptom of a problem elsewhere, should I just ignore them? Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
