| Author |
Message
|
| LouML |
 Posted: Thu Nov 10, 2005 10:06 am Post subject: HELP: MQLQMAG problems on MQ 5.1, 4 CPU NSK Tandem S74000 |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Hello. I'm new to this board. Any help or direction would be greatly appreciated.
We're having a problem that I hope someone can shed some light on. Some backrground. We're running MQ5.1 on a 4 CPU S74000, running G06.17. We have our queue manager set up to run an EC in each CPU.
Occasionally, we get FFST's. When I check the process, it turns out it's the MQLQMAG program. I can't tell which application these are associated with. We don't get any application errors. These messages will continue until we stop the process.
The following are the Viewpoint details.
2005-11-10 08:50:56 \TEL.$X4P2:327302837 IBM.MQSeries.2 006 MQSeries Error
Error Code : 6118
Function : zcpSystemMessage
Probe ID : 825
FFST File : $DATA15.PQMAST.FD90080
2005-11-10 08:50:56 \TEL.$X4P2:327302837 IBM.MQSeries.2 001 MQSeries FFST
from component COMP_ZC
Error Code : 6118
Severity : error
Module Name : zcpSystemMessage
Probe ID : 825
Error Text :
Program Abended zcpSystemMessage825
$DATA15.PQMAST.FD90080
I use our homegrown ANCESTOR and PPDETAIL programs to give me some info (I know these would be easier to read with a Courier New fixed font, but I can't figure out how to change that)
RUN $SYSTEM.UTIL.ANCESTOR $X4P2 DETAIL
Process Primary Backup Ancestor Process Created Process Program Name
$X4P2 1,507 $Y44R 11-10-2005 08:50:44 $DATA15.ZMQSEXE.MQLQMAG
RUN $SYSTEM.UTIL.PPDETAIL $X4P2
Process Ancestor Program Name Process Created
\TEL.$X4P2 \TEL.$Y44R $DATA15.ZMQSEXE.MQLQMAG 11-10-2005 08:50:44
\TEL.$Y44R \TEL.$QMST $DATA15.ZMQSEXE.MQEC 10-22-2005 09:49:08
\TEL.$QMST \TEL.$Y44G $SYSTEM.SYSTEM.PATHMON 10-22-2005 09:49:04
A PSTATE of the process looks like:
RUN $SYSTEM.UTIL.PSTATE $X4P2
PSTATE (14OCT99) Unsupported by Ian Stephenson @UK
PSTATE for Guardian Q06
Target process: pin 00507 in cpu 01, \TEL.$X4P2:327302837 (Primary)
program: \TEL.$DATA15.ZMQSEXE.MQLQMAG
library: $DATA15.ZMQSLIB.MQSRLLIB
srl: \TEL.$SYSTEM.SYS00.ZCRESRL
: \TEL.$SYSTEM.SYS00.ZI18NSRL
: \TEL.$SYSTEM.SYS00.ZICNVSRL
: \TEL.$SYSTEM.SYS00.ZCRTLSRL
: \TEL.$SYSTEM.SYS00.ZINETSRL
: \TEL.$SYSTEM.SYS00.ZOSSKSRL
: $DATA15.ZMQSLIB.MQSRLLIB
swap: \TEL.$DATA15.#0
extended swap:
selectable segment: Id: 00010 \TEL.$DATA15.PQMASTD.CCSIDMEM
selectable segment: Id: 00011 \TEL.$DATA15.PQMASTD.QMINIMEM
selectable segment: Id: 01101 \TEL.$DATA15.#0012498
home terminal: \TEL.$VHJ
Initial priority was 165, current priority is 165.
Process Wait State: %100005
waiting on : LSIG LDONE LREQ
Process access ID (PAID): MQM .MANAGER , 250,255
Process State: %000002
RUNNABLE
Creator proc : \TEL.$Y44R:286486709, Id: MQM .MANAGER , 250,255
Process Creation Time: November 10, 2005 08:50:44.064899 (LCT)
Process Execution Time: 0000:00:03.924466
Only the process creator may stop this process.
No-one has tried to stop this process.
Fnum Filename Type Styp Lsterr
---- --------------------------------------- ----------- ---- ------
0008 \TEL.$DATA15.#0012498 Disc 42 00000
No outstanding I/O
Access mode is Read only Shared
Accessing Unstructured File without key.
0007 \TEL.$Y44R:286486709 Process 00 00000
Current operations: Writeread
Access mode is Read/Write Shared
0006 \TEL.$DATA15.PQMASTD.SHUTDOWN Disc 42 00000
Current operations: Control
Access mode is Read only Shared
Accessing Unstructured File without key.
0005 \TEL.$DATA15.PQMASTD.SHUTDOWN Disc 42 00000
No outstanding I/O
Access mode is Read only Shared
Accessing Unstructured File without key.
0004 \TEL.$DATA15.PQMASTD.TRACEOPT Disc 42 00000
Current operations: Control
Access mode is Read only Shared
Accessing Unstructured File without key.
0003 \TEL.$TMP 21 TMF 04 00000
No outstanding I/O
Access mode is Read/Write Shared
0002 \TEL.$VHJ Process 30 00000
No outstanding I/O
Access mode is Read/Write Shared
0001 \TEL.$VHJ Process 30 00000
No outstanding I/O
Access mode is Write only Shared
0000 $RECEIVE $RECEIVE 00 00000
Current operations: Readupdate
Access mode is Read/Write Shared
EDIT: Added these FD items
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- November 10 8:50:53 2005 |
| Host Name :- \TEL |
| PIDS :- 5724A39 |
| LVLS :- 510 |
| Product Long Name :- MQSeries for Compaq NonStop Kernel |
| Vendor :- IBM |
| Probe Id :- ZC010825 |
| Application Name :- MQM |
| Component :- zcpSystemMessage |
| Build Date :- Sep 12 2005 |
| Exe File Name :- \TEL.$DATA15.ZMQSEXE.MQLQMAG |
| UserID :- -1281 |
| Process File Name :- \TEL.$X4P2:327302837 |
| Node number :- 1 |
| CPU :- 1 |
| PIN :- 507 |
| QueueManager :- PQMAST |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6118 |
| Probe severity :- Severity 2: error |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred (0)ÿ |
| Comment1 :- error 0000000000 in function 0000000010 |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- November 10 8:50:54 2005 |
| Host Name :- \TEL |
| PIDS :- 5724A39 |
| LVLS :- 510 |
| Product Long Name :- MQSeries for Compaq NonStop Kernel |
| Vendor :- IBM |
| Probe Id :- ZC010825 |
| Application Name :- MQM |
| Component :- zcpSystemMessage |
| Build Date :- Sep 12 2005 |
| Exe File Name :- \TEL.$DATA15.ZMQSEXE.MQLQMAG |
| UserID :- -1281
| Process File Name :- \TEL.$X4P2:327302837 |
| Node number :- 1 |
| CPU :- 1 |
| PIN :- 507 |
| QueueManager :- PQMAST |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6118 |
| Probe severity :- Severity 2: error |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred (0)ÿ |
| Comment1 :- error 0000000000 in function 0000000010 |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| LuisFer |
| Posted: Fri Nov 11, 2005 9:47 am Post subject: Re: HELP: MQLQMAG problems on MQ 5.1, 4 CPU NSK Tandem S7400 |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
What's your Level CSD & Efix? Now is CSD3 EFIX 3.
You can see with a VPROC of the MQSRLLIB file too.
Regards |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 10:59 am Post subject: Re: HELP: MQLQMAG problems on MQ 5.1, 4 CPU NSK Tandem S7400 |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
|
| Back to top |
|
|
| LouML |
| Posted: Fri Nov 11, 2005 11:28 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Permanent queues.
VPROC - T9617G03 - (14 DEC 2001) SYSTEM \TEL Date 11 NOV 2005, 14:25:34
Copyright Compaq Computer Corporation 1986 - 2001
$DATA15.ZMQSLIB.MQSRLLIB
GMT Binder timestamp: 12SEP2005 19:18:26
Version procedure: T8432D44_01JUL97_CRTLNS
Version procedure: T0085D45_29OCT2004_MQILIB_51
Version procedure: T0085D45_29OCT2004_ECBLIB_51
Version procedure: T0085D45_29OCT2004_ECLIB_51
Version procedure: T0085D45_07DEC2004_CMDLIB_51
Version procedure: T0085D45_19AUG2005_LQMLIB_51
Version procedure: T0085D45_16JUN2005_REMLIB_51
Version procedure: T0085D45_29OCT2004_COMMLIB_51
Version procedure: T0085D45_11MAR2005_ZSLIB_51
Version procedure: T0085D45_29JUL2005_ZSTLIB_51
Version procedure: T0085D45_03MAY2005_DCLIB_51
Version procedure: T0085D45_29OCT2004_IPCLIB_51
Version procedure: T0085D45_21JUN2005_CSLIB_51
Version procedure: T0085D45_19AUG2005_MQSCLIB_51
Version procedure: T0085D45_29OCT2004_NSRLIB_51
Version procedure: T0085D45_29OCT2004_NSPLIB_51
Version procedure: T0085D45_19AUG2005_QSLIB_51
Version procedure: T0085D45_09FEB2005_QSALIB_51
Version procedure: T0085D45_21JUL2005_SSLIB_51
Version procedure: T0085D45_29OCT2004_SSALIB_51
Version procedure: T0085D45_25MAY2005_ZILIB_51
Version procedure: T0085D45_29OCT2004_AILIB_51
Native Mode: runnable file |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 11:44 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Ok the level is CSD3 ¿Efix 2?.
Well, i remember a problem with our QMgrs with a corruption with the Qfiles on Temp/dyn queues (using for RUNMQSC , MQAI, or the Screen Cobol pathway program MQMC) and SYMPTOM are very, very equal.
Look for Queues prefixed MQAI (or other no aplications), using DSPMQFLS display the Qfiles, & looking for this on $vol.<QMGR>M($DATA15.PQMASTM) if no exits this one FUP CREATE LIKE (other QFile),
I think that this help you |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Nov 11, 2005 12:36 pm Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| LuisFer wrote: |
Ok the level is CSD3 ¿Efix 2?.
Well, i remember a problem with our QMgrs with a corruption with the Qfiles on Temp/dyn queues (using for RUNMQSC , MQAI, or the Screen Cobol pathway program MQMC) and SYMPTOM are very, very equal.
Look for Queues prefixed MQAI (or other no aplications), using DSPMQFLS display the Qfiles, & looking for this on $vol.<QMGR>M($DATA15.PQMASTM) if no exits this one FUP CREATE LIKE (other QFile),
I think that this help you |
Can you explain further? I'm not sure I understand what you are suggesting.
I've never used DSPMQFLS before. What do I put in the GenericObject argument?
Would it help to delete the queues and re-add them? |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 1:06 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Sorry, english is not my native lang.
Well, the DSPMQFLS is a control Command, it works under tacl
TACL 1> DSPMQFLS -m PQMAST -t q MQAI*
This one displays the files asociated with the Queues, there are 3 Qfiles (for Queue) The overflowfile , the Touchfile and the Qfile. In our case , don't have the TouchFile.
When using MQMC (example) the program creates a Temporary Queue (with their Qfiles) and ocasionally the QMgr routines don't work well and dont' delete The queue but the qfiles are erased. This one is an inconsistency and the QMgr wants delete this queue newly (using a MQLQMAG).
You have to create the Qfile (out of QMgr) with a FUP CREATE the Qfile with the name of th DSPMQFLS display ( fup create oxxxx, like (other Qfile).
In the $data15.pqmastm ALL the files (code 25a) are Qfiles.
Example:
$data00.mq33 32> dspmqfls -m mq33 -t q PR*
$data00.mq33 32..
MQSeries Display MQ Files
CONNECTING.
QLOCAL PRUEBAS.PETICIONES.1
$data00.mq33m.QOIPXPRU
$data00.mq33m.OOIPXPRU
$data00.mq33M.TOIPXPRU
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
On the mq33m subvolume:
$data00.mq33M 35> fi *oipxpru
$data00.mq33M
CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
OOIPXPRU O 25A 12288 04SEP2005 15:05 002,255NCNU 50 100
QOIPXPRU O 25A 12288 04SEP2005 15:05 002,255 NCNU 50 100
TOIPXPRU O 25A 0 04SEP2005 15:05 002,255 NCNU 2 2
Supose that the QOIPXPRU don't exit, then FUP CREATE QOIPXPRU, like (other type QXXXXXXXX) . |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Nov 11, 2005 1:36 pm Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| LuisFer wrote: |
Sorry, english is not my native lang.
Well, the DSPMQFLS is a control Command, it works under tacl
TACL 1> DSPMQFLS -m PQMAST -t q MQAI*
This one displays the files asociated with the Queues, there are 3 Qfiles (for Queue) The overflowfile , the Touchfile and the Qfile. In our case , don't have the TouchFile.
When using MQMC (example) the program creates a Temporary Queue (with their Qfiles) and ocasionally the QMgr routines don't work well and dont' delete The queue but the qfiles are erased. This one is an inconsistency and the QMgr wants delete this queue newly (using a MQLQMAG).
You have to create the Qfile (out of QMgr) with a FUP CREATE the Qfile with the name of th DSPMQFLS display ( fup create oxxxx, like (other Qfile).
In the $data15.pqmastm ALL the files (code 25a) are Qfiles.
Example:
$data00.mq33 32> dspmqfls -m mq33 -t q PR*
$data00.mq33 32..
MQSeries Display MQ Files
CONNECTING.
QLOCAL PRUEBAS.PETICIONES.1
$data00.mq33m.QOIPXPRU
$data00.mq33m.OOIPXPRU
$data00.mq33M.TOIPXPRU
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
On the mq33m subvolume:
$data00.mq33M 35> fi *oipxpru
$data00.mq33M
CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
OOIPXPRU O 25A 12288 04SEP2005 15:05 002,255NCNU 50 100
QOIPXPRU O 25A 12288 04SEP2005 15:05 002,255 NCNU 50 100
TOIPXPRU O 25A 0 04SEP2005 15:05 002,255 NCNU 2 2
Supose that the QOIPXPRU don't exit, then FUP CREATE QOIPXPRU, like (other type QXXXXXXXX) . |
No problem 
When I try it on my system, I get the following:
\TEL 26> DSPMQFLS -m PQMAST -t QL MQAI*
MQSeries Display MQ Files
AMQ7024: Arguments supplied to a command are not valid.
Usage: dspmqfls [-m QMgrName] [-t ObjType] GenericObjName
\TEL 27> |
|
| Back to top |
|
|
| JT |
| Posted: Fri Nov 11, 2005 1:42 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Try:
| Quote: |
| DSPMQFLS -m PQMAST -t ql MQAI* |
|
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 1:44 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| JT wrote: |
Try:
| Quote: |
| DSPMQFLS -m PQMAST -t ql MQAI* |
|
Sorry dspmqfls -m PQMAST -t q MQAI* |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Nov 11, 2005 1:54 pm Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| JT wrote: |
Try:
| Quote: |
| DSPMQFLS -m PQMAST -t ql MQAI* |
|
Thanks. Now I get this. I don't see anything missing a file.
\TEL 26> DSPMQFLS -m PQMAST -t ql MQAI*
MQSeries Display MQ Files
CONNECTING.
No objects processed.
\TEL 27> DSPMQFLS -m PQMAST -t ql *
MQSeries Display MQ Files
CONNECTING.
QLOCAL APEX.TO.MAST
$DATA15.PQMASTM.QAPEXXTO
$DATA15.PQMASTM.OAPEXXTO
$DATA15.PQMASTM.TAPEXXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL ASGQM2
$DATA15.PQMASTM.QASGQM2
$DATA15.PQMASTM.OASGQM2
$DATA15.PQMASTM.TASGQM2
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL CHASE.TO.MAST.DATA
$DATA15.PQMASTM.QCHASEXT
$DATA15.PQMASTM.OCHASEXT
$DATA15.PQMASTM.TCHASEXT
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL CXA.ASG.TO.MAST.REQUESTS
$DATA15.PQMASTM.QCXAXASG
$DATA15.PQMASTM.OCXAXASG
$DATA15.PQMASTM.TCXAXASG
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL DQMAST
$DATA15.PQMASTM.QDQMAST
$DATA15.PQMASTM.ODQMAST
$DATA15.PQMASTM.TDQMAST
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL FPS.TO.MAST
$DATA15.PQMASTM.QFPSXTOX
$DATA15.PQMASTM.OFPSXTOX
$DATA15.PQMASTM.TFPSXTOX
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL GTSHUB01
$DATA15.PQMASTM.QSJ3B6D1
$DATA15.PQMASTM.OSJ3B6D1
$DATA15.PQMASTM.TSJ3B6D1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL GTSHUB02
$DATA15.PQMASTM.QGTSHUB0
$DATA15.PQMASTM.OGTSHUB0
$DATA15.PQMASTM.TGTSHUB0
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL HUD.TO.TEL
$DATA15.PQMASTM.QHUDXTOX
$DATA15.PQMASTM.OHUDXTOX
$DATA15.PQMASTM.THUDXTOX
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL LMBB.TO.MAST
$DATA15.PQMASTM.QLMBBXTO
$DATA15.PQMASTM.OLMBBXTO
$DATA15.PQMASTM.TLMBBXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL M1MQ01
$DATA15.PQMASTM.QM1MQ01
$DATA15.PQMASTM.OM1MQ01
$DATA15.PQMASTM.TM1MQ01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL MICS.TO.MAST.SETTLE.ACTIVITY
$DATA15.PQMASTM.QMICSXTO
$DATA15.PQMASTM.OMICSXTO
$DATA15.PQMASTM.TMICSXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL MIN.TO.MBD
$DATA15.PQMASTM.QMINXTOX
$DATA15.PQMASTM.OMINXTOX
$DATA15.PQMASTM.TMINXTOX
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL MQ09
$DATA15.PQMASTM.QMQ09
$DATA15.PQMASTM.OMQ09
$DATA15.PQMASTM.TMQ09
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL MQ15
$DATA15.PQMASTM.QMQ15
$DATA15.PQMASTM.OMQ15
$DATA15.PQMASTM.TMQ15
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL MSTG.TO.MAST
$DATA15.PQMASTM.QMSTGXTO
$DATA15.PQMASTM.OMSTGXTO
$DATA15.PQMASTM.TMSTGXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL NEONAP1P
$DATA15.PQMASTM.QNEONAP1
$DATA15.PQMASTM.ONEONAP1
$DATA15.PQMASTM.TNEONAP1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL NYHUB2P
$DATA15.PQMASTM.QNYHUB2P
$DATA15.PQMASTM.ONYHUB2P
$DATA15.PQMASTM.TNYHUB2P
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL NYHUB2P.MAST
$DATA15.PQMASTM.QW1K0171
$DATA15.PQMASTM.OW1K0171
$DATA15.PQMASTM.TL3K0171
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL NYHUB2P.MBSC
$DATA15.PQMASTM.QWGO0171
$DATA15.PQMASTM.OWGO0171
$DATA15.PQMASTM.TWGO0171
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL NYHUB2P.MLCS.XQ
$DATA15.PQMASTM.QG16QV01
$DATA15.PQMASTM.OG16QV01
$DATA15.PQMASTM.TJIBQV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL OLTP.TO.MAST
$DATA15.PQMASTM.QOLTPXTO
$DATA15.PQMASTM.OOLTPXTO
$DATA15.PQMASTM.TOLTPXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL PQMAST.DEAD.LETTER.QUEUE
$DATA15.PQMASTM.QPQMASTX
$DATA15.PQMASTM.OPQMASTX
$DATA15.PQMASTM.TPQMASTX
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL PSTTRDP
$DATA15.PQMASTM.QPSTTRDP
$DATA15.PQMASTM.OPSTTRDP
$DATA15.PQMASTM.TPSTTRDP
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SIAC.TO.MBSCC.INPUT
$DATA15.PQMASTM.QSIACXTO
$DATA15.PQMASTM.OSIACXTO
$DATA15.PQMASTM.TSIACXTO
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SWIFT.TO.MST
$DATA15.PQMASTM.QSWIFTXT
$DATA15.PQMASTM.OSWIFTXT
$DATA15.PQMASTM.TSWIFTXT
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.ADMIN.CHANNEL.EVENT
$DATA15.PQMASTM.QO9ZPV01
$DATA15.PQMASTM.OO9ZPV01
$DATA15.PQMASTM.TO9ZPV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.ADMIN.COMMAND.QUEUE
$DATA15.PQMASTM.QIG1QV01
$DATA15.PQMASTM.OIG1QV01
$DATA15.PQMASTM.TIG1QV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.ADMIN.PERFM.EVENT
$DATA15.PQMASTM.QTPF0171
$DATA15.PQMASTM.OTPF0171
$DATA15.PQMASTM.TTPF0171
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.ADMIN.QMGR.EVENT
$DATA15.PQMASTM.QFBBQV01
$DATA15.PQMASTM.OFBBQV01
$DATA15.PQMASTM.TFBBQV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CHANNEL.INITQ
$DATA15.PQMASTM.QCHZPV01
$DATA15.PQMASTM.OCHZPV01
$DATA15.PQMASTM.TCHZPV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CHANNEL.SYNCQ
$DATA15.PQMASTM.QW83QV01
$DATA15.PQMASTM.OW83QV01
$DATA15.PQMASTM.TW83QV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CICS.INITIATION.QUEUE
$DATA15.PQMASTM.QV01QV01
$DATA15.PQMASTM.OV01QV01
$DATA15.PQMASTM.TV01QV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CLUSTER.COMMAND.QUEUE
$DATA15.PQMASTM.QRV1B6D1
$DATA15.PQMASTM.ORV1B6D1
$DATA15.PQMASTM.TRV1B6D1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CLUSTER.REPOSITORY.QUEUE
$DATA15.PQMASTM.QTZRA6D1
$DATA15.PQMASTM.OTZRA6D1
$DATA15.PQMASTM.TTZRA6D1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.CLUSTER.TRANSMIT.QUEUE
$DATA15.PQMASTM.QCKTA6D1
$DATA15.PQMASTM.OCKTA6D1
$DATA15.PQMASTM.TCKTA6D1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.DEAD.LETTER.QUEUE
$DATA15.PQMASTM.QBN8QV01
$DATA15.PQMASTM.OBN8QV01
$DATA15.PQMASTM.TBN8QV01
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.DEFAULT.INITIATION.QUEUE
$DATA15.PQMASTM.QY8LFQU
$DATA15.PQMASTM.TY8LFQU
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL SYSTEM.DEFAULT.LOCAL.QUEUE
$DATA15.PQMASTM.QSYSTEMX
$DATA15.PQMASTM.OSYSTEMX
$DATA15.PQMASTM.TSYSTEMX
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL TEST.INBOUND
$DATA15.PQMASTM.QTESTXIN
$DATA15.PQMASTM.OTESTXIN
$DATA15.PQMASTM.TTESTXIN
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL TEST.OUTBOUND
$DATA15.PQMASTM.QTESTXOU
$DATA15.PQMASTM.OTESTXOU
$DATA15.PQMASTM.TTESTXOU
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL TRN.BAM.TO.MAST
$DATA15.PQMASTM.QTRNXBAM
$DATA15.PQMASTM.OTRNXBAM
$DATA15.PQMASTM.TTRNXBAM
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL TRN.GTCS.TO.MAST
$DATA15.PQMASTM.QTRNXGTC
$DATA15.PQMASTM.OTRNXGTC
$DATA15.PQMASTM.TTRNXGTC
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL TRNMQS1P
$DATA15.PQMASTM.QTRNMQS1
$DATA15.PQMASTM.OTRNMQS1
$DATA15.PQMASTM.TTRNMQS1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL XML5.MQX4ML.TO.TNDM.BRDCST
$DATA15.PQMASTM.QXML5XMQ
$DATA15.PQMASTM.OXML5XMQ
$DATA15.PQMASTM.TXML5XMQ
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
QLOCAL XML5.MQX4ML.TO.TNDM.RESPNS
$DATA15.PQMASTM.QM2YA6D1
$DATA15.PQMASTM.OM2YA6D1
$DATA15.PQMASTM.TFRZA6D1
Queue/Status Server : DEFAULT
Queue Server Options : C
Message overflow threshold : 200000 bytes
\TEL 28> |
|
| Back to top |
|
|
| JT |
| Posted: Fri Nov 11, 2005 1:56 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| I believe MQAI.Reply queues have a type of QLOCAL, so either '-t q' or '-t ql' should be acceptable. |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 2:15 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| JT wrote: |
| I believe MQAI.Reply queues have a type of QLOCAL, so either '-t q' or '-t ql' should be acceptable. |
I think equal.
Well , review the fdc i see this one :
"Program Abended zcpSystemMessage825"
825 (0825) is (Decimal) 2085 = MQRC_UNKNOWN_OBJECT_NAME.(this one is an interpret for me).
Follow this one |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Nov 11, 2005 4:19 pm Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| LuisFer wrote: |
| JT wrote: |
| I believe MQAI.Reply queues have a type of QLOCAL, so either '-t q' or '-t ql' should be acceptable. |
I think equal.
Well , review the fdc i see this one :
"Program Abended zcpSystemMessage825"
825 (0825) is (Decimal) 2085 = MQRC_UNKNOWN_OBJECT_NAME.(this one is an interpret for me).
Follow this one |
How does 825 convert to Reason Code 2085? I can't imagine it's an unknown object. These are not dynamic queues. These are static queues, defined long ago. Besides, at the time of these errors, no application reports an error.
Can someone explain just what the MQLQMAG program actually does? The MQ NSK books don't do such a good job. |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Nov 11, 2005 10:49 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
0825 (Hex) = 2085 (Dec).
The permanent Queues are good, i always reference to Temp/Dynamic Queues.
The Local Queue MQ Message Agent (LQMQMAG) is called for a Local Application to perform the MQ Calls. A local aplication is (by example) the MQMC, PCFs.
I should open a PMR to IBM with this problem.
Sorry |
|
| Back to top |
|
|
|
|
