| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Manager Starting Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| kalimaacool |
 Posted: Sun Jun 20, 2010 6:47 am Post subject: Queue Manager Starting Problem |
 |
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
Facing a problem in starting the queue manager HKCNM1P1.
The normal method to start this queue manager is by
1. Log in as isismqmp
2. start the service IBMMqseries in the services window
Normal reaction to this would be, that the queue manager status changes to UP, and after which we can start the TDE client for file transfer purposes
This above method is not working
The service is being started, but the queue manager does not start
There is one thing to note, when we start the queue manager via command line using strmqm, it is running fine, but queue manager goes down once session is closed.
[code]
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun June 20 20:21:00 China Standard Time 2010 |
| Host Name :- HKGWKGPANCMS02 (Windows Server 2003, Build 3790: |
| Service Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005025 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| SCCS Info :- cmd/zmain/amqzxmb0.c, 1.377.1.37 |
| Line Number :- 6839 |
| Build Date :- May 12 2008 |
| CMVC level :- p600-204-080509 |
| Build Type :- IKAP - (Production) |
| UserID :- g.in.cfsuadmin.001 |
| Process Name :- E:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00003976 |
| Thread :- 00000001 |
| QueueManager :- HKCNM1P1 |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Major Errorcode :- zrcX_PROCESS_MISSING |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5008 |
| Probe Severity :- 2 |
| Probe Description :- AMQ5008: An essential WebSphere MQ process 996 |
| (amqrrmfa.exe) cannot be found and is assumed to be terminated. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 996 3e4 |
| Comment1 :- amqrrmfa.exe |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ExecCtrlrMain---< AO "Object Catalogue" >-----
SessionAnchor
{
Flags: 0X20F
SessionId 4C1E0795
Location: E:\Program Files\IBM\WebSphere MQ\qmgrs\HKCNM1P1
ObjCatRecoveryFlags: None
OCCB.StrucId AOCB
hmtxObjCat.RequestCount 23
hmtxObjCatX.RequestCount 5
ActivityQ[0].hmtx.RequestCount 1
ActivityQ[0].hmtxC.RequestCount 1
MaxReserveBytes 67108864
ATM.StartedFlag: 0X1
ATM.NextTranNum: 0.143504
ATM.RMidGenerator: 32793
ATM.CRecLSN: 0.0.0.0
ATM.CRecFlags: atmRECFLAG_NONE
ATM.TRecFlags: atmRECFLAG_NONE
TCBDepth 2
SLDepth 1
hmtxTranTable.RequestCount 72
hmtxRMid.RequestCount 13
hmtxNextTranNum.RequestCount 10
hmtxTranCursor.RequestCount 5
hmtxTxnCache.RequestCount 4
{
}adtTRANCURSOR
}
alipGData
{
ALM.Flags: altGFHLGSTARTED
ALM.ChkPtTime 2010-06-20 20:20:38.407
ALM.ChkPtTimeLong 663208
ALM.ChkPtTimeShort 663208
ALM.WaitTimeLong 0
ALM.WaitTimeShort 0
ALM.ChkPtOwner 2644
ALM.ChkPtOpCount 150
ALM.ChkPtOpMax 10000
ALM.ChkPtOpMin 100
ALM.ChkPtByteCount 1580
ALM.ChkPtByteLimit 966367641
ALM.ChkPtCompleteIndex 1
ALM.hmtxData.RequestCount 3
ALM.CrashRecRestartLSN 0.2.6434.51778
}
aiiThread->StructID: "AIIT"
AgentFlags: 7
apipThread
{
LockFlags 0
QLockCount 0
ThreadFlags 0
atm.pLDatatm.pLData
{
RMState : 0X1FFFFFFF
RMid : 32771
Association : 0
TranDataState : 0
}
}
aqi.pLData.Init 1
aqi.pLData.InTran 0
aqi.pLData.Logged 1
aqi.pLData.PrevLSN 0.2.6435.40716
-----< H "Logger" >-----
Global Data
{
InitCount: 4
StateFlags: 1
LogThresholdPercentage: 80
LogThreshold: 1710384640
LogPacePercentage: 90
LogPacePerFile: 120261420
LogPaceTotal: 1924182720
AnchorMutex.RequestCount: 24
}
dbcb
{
{
counter1: 29753
counter2: 29753
logactive: 8
loginactive: 8
logsize 32768
baselsn: 0.2.6144.0
nextlsn: 0.2.6435.40944
lowtranlsn: 0.2.6435.39796
minbufflsn: 0.2.6435.39364
headlsn: 0.2.6435.39364
taillsn: 0.2.6435.40943
hflag1 NONE
HeadExtentID: 3
LastEID: 1223288395
LogID: 1223288374
FirstArchNum: -1
LastArchNum: -1
nextArcFile: -1
FileCount: 8
filenum [3,4,5,6,7,0,1,2
]
LastCId: 1223288378
softmax: 134217728
}logfhdr
{
counter1: 29753
counter2: 29753
logactive: 8
loginactive: 8
logsize 32768
baselsn: 0.2.6144.0
nextlsn: 0.2.6435.38536
lowtranlsn: 0.2.6435.37796
minbufflsn: 0.2.6435.37364
headlsn: 0.2.6435.37364
taillsn: 0.2.6435.38535
hflag1 NONE
HeadExtentID: 3
LastEID: 1223288395
LogID: 1223288374
FirstArchNum: -1
LastArchNum: -1
nextArcFile: -1
FileCount: 8
filenum [3,4,5,6,7,0,1,2
]
LastCId: 1223288378
softmax: 134217728
}logfhdr_hardened
logstate: MQLP_OK
flag1: NEW_LOG_LOGIC|WRITE_LOW|READ_LOW
flag2: NONE
partialFlags: MQLPG_PARTIAL_LOW
tailPingPongCount: 6
NextAppendBuf: 6
logBufSz; 128
softmax: 100
logprimary: 8
logsecond: 8
LastBufferLsn: 0.0.0.0
lastdisklsn: 0.2.6435.40259
LastRecLsn: 0.2.6435.40259
TailIndex: 0
TailPage: 4665
TotalLogSpace: 1069019154
LogBytesInUse: 19027936
LogBytesInUseHWM: 1069019154
LogReserveCushion 21380464
logFull: FALSE
NextFormatExtNum: 0
DeletePendingLow: 0
DeletePendingHigh: 0
currentIOLsn: 0.2.6435.40259
WriteToLsn: 0.2.6435.40259
totalIOCount[1]: 6
WriteSizeShort : 4096
WriteSizeLong : 4096
WriteSizeMax : 4096
WriteTimeShort : 117
WriteTimeShortMax: 124
WriteTimeLong : 117
WriteTimeLongMax : 124
WriteTimeMax : 127
mqlp_dbcb_sem.RequestCount: 88
LastDiskLsnSem.RequestCount: 40
IOTaskSem.RequestCount: 1
AppendSem.RequestCount: 16
gasn_latch.RequestCount: 31
gasn_request_qhead: 0.0.0.0
gasn_request_qtail: 0.0.0.0
transsem.RequestCount: 6
FormatRequestHistory [0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0
]
FormatResponseHistory [(0,0),(0,0),(0,0),(0,0),(0,0),(0,0),(0,0),(0,0),
(0,0),(0,0),(0,0),(0,0),(0,0),(0,0),(0,0),(0,0)
]
}
-------< R "Remote - LQM" >-------
InSignalHandler:0
HighDetail: 0
ThreadState: 0
Component: 34
Function: 5
Work Control Block
{
QueueManager
User
bKillPending FALSE
AuthToken 0
PoolThreads 0
rmid 0
xid 0
DebugOptions 00000001
Config Control Block
{
Init FALSE
Options 0x0
MaxChannels -1
MaxActiveChannels -1
MaxTries -1
MaxTriesIntvl -1
MaxActiveChannelsInUse FALSE
ChinitDiscInt -1
CanConvert TRUE
MaxInitiators -1
XOptions -1
AdoptType -1
AdoptCheck -1
AdoptTimeout -1
QueueCacheSize -1
CommsTraceBufferSize -1
PipeLineDelay -1
RequesterTimeout -1
Priority -1
ClientIdle -1
NpmBatchInt -1
OptThreads -1
MaxThreads -1
OptProcesses -1
MaxProcesses -1
Options 0
Raw cccCONFIG struct
00D526F0 00000000 00000000 ........
00D52700 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00D52710 00000000 FFFFFFFF 01000000 FFFFFFFF ....ÿÿÿÿ....ÿÿÿÿ
00D52720 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00D52730 to 00D52740 suppressed, lines same as above
00D52750 FFFFFFFF FFFFFFFF ÿÿÿÿÿÿÿÿ
}
-------------------------------------
Environment Variables
AGENTWORKS_DIR=E:\NSM
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\g.in.cfsuadmin.001\Application Data
AW_LANG=English
BMRDIR=E:\Program Files\VERITAS\BareMetal\
CAI_CAFT=E:\NSM
CAI_MSQ=E:\NSM
CLIENTNAME=INDH173981
ClusterLog=C:\WINNT\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=HKGWKGPANCMS02
ComSpec=C:\WINNT\system32\cmd.exe
COUNTRY=hk
CYGWIN=tty
ENV=prd
FP_NO_HOST_CHECK=NO
FTF_CONFIG_FILE=E:\prd\isis\hk\ini\ftfconfig.ini
FTF_EXIT_PATH=E:\e-Adapter\bin
FTF_IFILE=E:\prd\isis\hk\ini\ftf.ini
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\g.in.cfsuadmin.001
HORCMINST=0
ISIS_HOME=E:\prd\isis\hk
LOGONSERVER=\\HKMGADOMR02
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=E:\Program Files\IBM\WebSphere MQ\Java\lib;E:\oracle\product\10.2.0\client_1\bin;E:\Perl\bin\;C:\Program Files\VERITAS\NetBackup\bin\;C:\WINNT\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\Dell\SysMgt\RAC5;C:\Program Files\Dell\SysMgt\oma\bin;E:\Program Files\SSH Communications Security\SSH Tectia\SSH Tectia AUX/Support binaries;C:\Program Files\Java\jdk1.5.0_07\bin;c:\winnt\temp;E:\Program Files\IBM\WebSphere MQ\bin;E:\TIVOLI~1\bin;;E:\Program Files\WinZip;E:\Program Files\SSH Communications Security\SSH Tectia\SSH Tectia Broker;E:\Program Files\SSH Communications Security\SSH Tectia\SSH Tectia Client;E:\Program Files\OpenSSH\bin;C:\Program Files\HITACHI\DynamicLinkManager\bin;C:\Program Files\HITACHI\DynamicLinkManager\lib;C:\Program Files\Common Files\Hitachi;C:\Program Files\HDVM\HBaseAgent\bin;C:\Program Files\HDVM\HBaseAgent\util\bin;E:\CA_APPSW;E:\NSM\services\bin;E:\NSM\agents\bin;E:\NSM\services\tools;E:\NSM\help;E:\Program Files\OpenSSH\bin;E:\psoft\bin\client\winx86;E:\APPS\orac92\bin;e:\apps\orac92\jre\1.4.2\bin\client;e:\apps\orac92\jre\1.4.2\bin;E:\Program Files\Oracle\jre\1.1.8\bin;E:\Program Files\Oracle\jre\1.3.1\bin;E:\Perl\bin\;E:\Program Files\VERITAS\NetBackup\bin\;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Common Files\Hitachi;E:\Program Files\HITACHI\DynamicLinkManager\bin;E:\Program Files\HITACHI\DynamicLinkManager\lib;E:\Program Files\Symantec\pcAnywhere\;e:\apps\bea\Tuxedo8.1\bin;E:\PROGRAM FILES\GEMS_TOOLS\CA_APPSW;E:\APPS\GEMS_TOOLS\NSM\services\bin;E:\APPS\GEMS_TOOLS\NSM\agents\bin;E:\APPS\GEMS_TOOLS\NSM\services\tools;E:\APPS\GEMS_TOOLS\NSM\help;I:\test\winzip;E:\Program Files\OpenSSH\bin;E:\Program Files\HITACHI\HDVM\HBaseAgent\bin;E:\Program Files\HITACHI\HDVM\HBaseAgent\util\bin;E:\Program Files\BMC Software\CONTROL-M Agent\Default\EXE\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PRJ=isis
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 11, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f0b
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=RDP-Tcp#1
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=C:\DOCUME~1\g.in.cfsuadmin.001\Local Settings\Temp\1
TMP=C:\DOCUME~1\g.in.cfsuadmin.001\Local Settings\Temp\1
USERDNSDOMAIN=SCB.NET
USERDOMAIN=ROOT-SCBNET
USERNAME=g.in.cfsuadmin.001
USERPROFILE=C:\Documents and Settings\g.in.cfsuadmin.001
windir=C:\WINNT
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sun June 20 20:21:00 China Standard Time 2010 |
| Host Name :- HKGWKGPANCMS02 (Windows Server 2003, Build 3790: |
| Service Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.4 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005030 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| SCCS Info :- cmd/zmain/amqzxmb0.c, 1.377.1.37 |
| Line Number :- 6901 |
| Build Date :- May 12 2008 |
| CMVC level :- p600-204-080509 |
| Build Type :- IKAP - (Production) |
| UserID :- g.in.cfsuadmin.001 |
| Process Name :- E:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00003976 |
| Thread :- 00000001 |
| QueueManager :- HKCNM1P1 |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Major Errorcode :- zrcX_PROCESS_MISSING |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5008 |
| Probe Severity :- 2 |
| Probe Description :- AMQ5008: An essential WebSphere MQ process 5684 |
| (amqzfuma.exe) cannot be found and is assumed to be terminated. |
| FDCSequenceNumber :- 1 |
| Arith1 :- 5684 1634 |
| Comment1 :- amqzfuma.exe |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ExecCtrlrMain
zxcProcessChildren
xcsFFST
Last edited by kalimaacool on Sun Jun 20, 2010 8:01 pm; edited 1 time in total |
|
| Back to top |
|
 |
| kalimaacool |
| Posted: Sun Jun 20, 2010 6:49 am Post subject: |
|
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
This is live production problem
Help will be greatly appreciated |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jun 20, 2010 8:42 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Please do not paste the whole stack, most of which is only relevant/understandable by 3rd line support...
1. The process that is missing is the cluster repository process, so is this queue manager in a cluster?
2. Why are you manually starting the service? (and under a different user to what I'd expect).
3. What do the queue manager logs say?
You may also want to have a look at THIS.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jun 20, 2010 1:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kalimaacool wrote: |
| This is live production problem |
Then why are you posting here & not raising a PMR with IBM
| kalimaacool wrote: |
| Help will be greatly appreciated |
And it will arrive when it arrives if it arrives. This is a forum run by volunteers not a support desk.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jun 20, 2010 1:31 pm Post subject: Re: Queue Manager Starting Problem |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kalimaacool wrote: |
| There is one thing to note, when we start the queue manager via command line using strmqm, it is running fine, but queue manager goes down once session is closed. |
This is perfectly normal and well expected. Use amqmdain instead of strmqm.
Also, you're on Windows. Try rebooting.
Exerk did a fine job of doing your job for you and searching on ibm's website for the probeid in the FFSTs you posted. However, that issue appears to be fixed in 6.0.2.3, and you're already running 6.0.2.4. Try upgrading to 6.0.2.9 and see if that helps. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Jun 20, 2010 3:31 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| kalimaacool wrote: |
This is live production problem
Help will be greatly appreciated |
First, why you are starting mqseries Services to start the queue manager?
If you have not changed start up attribute of the queue manager, the restarting the services does not restart/start the queue manager
when you log out the qmgr does down because this is what is supposed to be. you have to use amqmdain start command. |
|
| Back to top |
|
|
| kalimaacool |
| Posted: Sun Jun 20, 2010 7:58 pm Post subject: |
|
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
| Vitor wrote: |
| kalimaacool wrote: |
| This is live production problem |
Then why are you posting here & not raising a PMR with IBM
| kalimaacool wrote: |
| Help will be greatly appreciated |
And it will arrive when it arrives if it arrives. This is a forum run by volunteers not a support desk. |
We are co ordinating with IBM as well. |
|
| Back to top |
|
|
| kalimaacool |
| Posted: Sun Jun 20, 2010 8:04 pm Post subject: |
|
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
| exerk wrote: |
Please do not paste the whole stack, most of which is only relevant/understandable by 3rd line support...
1. The process that is missing is the cluster repository process, so is this queue manager in a cluster?
2. Why are you manually starting the service? (and under a different user to what I'd expect).
3. What do the queue manager logs say?
You may also want to have a look at THIS. |
I ve cut down the stack trace.
Well, the service starts once the server is booted.
BUt, it is not starting the queue manager, So trying to start manually |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jun 20, 2010 10:37 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I'll ask again, what do the queue manager logs state? I ask this mostly out of curiosity now because as you have IBM on the case, at this point any advice we give becomes redundant as it may upset/affect anything IBM may suggest you implement.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| kalimaacool |
| Posted: Sun Jun 20, 2010 10:44 pm Post subject: |
|
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
| exerk wrote: |
| I'll ask again, what do the queue manager logs state? I ask this mostly out of curiosity now because as you have IBM on the case, at this point any advice we give becomes redundant as it may upset/affect anything IBM may suggest you implement. |
Sorry , missed giving you the extract
| Code: |
6/21/2010 12:29:28 - Process(4156.1) User(hkcnmft) Program(ftfmgr.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager HKCNM1P1.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4156.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 804 --------------------------------------------------------
6/21/2010 12:29:28 - Process(4156.1) User(hkcnmft) Program(ftfmgr.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Subpool Server 1
pid[2472] has terminated while application connected.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 766 --------------------------------------------------------
6/21/2010 12:29:28 - Process(4156.1) User(hkcnmft) Program(ftfmgr.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager HKCNM1P1.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4156.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 804 --------------------------------------------------------
6/21/2010 12:29:28 - Process(4156.1) User(hkcnmft) Program(ftfmgr.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Failed to complete
request to Shared Storage Server)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 766 --------------------------------------------------------
|
IBM has not suggested anything. they are still pointing fingers on which particular team will fix this..blah blah etc |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jun 20, 2010 10:51 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
ftfmgr.exe is Tivoli Data Exchange, or a part of it?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| kalimaacool |
| Posted: Sun Jun 20, 2010 11:01 pm Post subject: |
|
|
Newbie
Joined: 20 Jun 2010
Posts: 6
|
| exerk wrote: |
| ftfmgr.exe is Tivoli Data Exchange, or a part of it? |
Yes sir . |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
