ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportQueued Pub/Sub Daemon failed, reason=00005800

Post new topicReply to topic Goto page 1, 2  Next
Queued Pub/Sub Daemon failed, reason=00005800 View previous topic :: View next topic
Author Message
Ulrik
PostPosted: Wed Aug 29, 2018 3:34 am Post subject: Queued Pub/Sub Daemon failed, reason=00005800 Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

Hi

z/os v2.2 , MQ v8 - both on RSU1711

At the end of startup of the QMGR this message is issued in the CHIN task:

CSQT855E QDSL CSQXFCTL Queued Pub/Sub Daemon failed, reason=00005800

I tried to look up the reason code. I can't find it. I tried to google and only related hit suggest that "The storage class for the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue was NOT defined."
But it is.

I saw in an other thread "hughson" asking for :

DISPLAY QMGR PSMODE

DISPLAY NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST) ALL

So here is output :

DISPLAY QMGR PSMODE
CSQM201I QDSL CSQMDRTC DISPLAY QMGR DETAILS
QMNAME(QDSL)
PSMODE(ENABLED)
END QMGR DETAILS
CSQ9022I QDSL CSQMDRTC ' DISPLAY QMGR' NORMAL COMPLETION


DISPLAY NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST) ALL
CSQM293I QDSL CSQMDRTC 1 NAMELIST FOUND MATCHING REQUEST CRITERIA
CSQM201I QDSL CSQMDRTC DISPLAY NAMELIST DETAILS
NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST)
NLTYPE(QUEUE)
QSGDISP(QMGR)
DESCR(A list of queues for the queued Pub/Sub interface to monitor)
NAMCOUNT(2)
NAMES(
SYSTEM.BROKER.DEFAULT.STREAM
SYSTEM.BROKER.ADMIN.STREAM
)
ALTDATE(2014-03-23)
ALTTIME(02.40.11)
END NAMELIST DETAILS
CSQ9022I QDSL CSQMDRTC ' DISPLAY NAMELIST' NORMAL COMPLETION


Pub/sub related messages that comes before in CHIN task log:


CSQT975I QDSL CSQXDPSC Distributed Pub/Sub Controller has started
disabled
CSQT975I QDSL CSQXDPSC Distributed Pub/Sub Fan Out Task has started
CSQT975I QDSL CSQXDPSC Distributed Pub/Sub Command Task has started
CSQT975I QDSL CSQXDPSC Distributed Pub/Sub Publish Task has started


Any ideas to how I can fix this?

Ulrik
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 29, 2018 5:10 am Post subject: Re: Queued Pub/Sub Daemon failed, reason=00005800 Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25310
Location: Ohio, USA

Ulrik wrote:
I tried to google and only related hit suggest that "The storage class for the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue was NOT defined."
But it is.


Post display statements for the queue and the storage class in question.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Aug 29, 2018 5:29 am Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8191
Location: US: west coast, almost. Otherwise, enroute.

Go to google. Search for 'CSQT855E CSQXFCTL reason=00005800' .
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
hughson
PostPosted: Wed Aug 29, 2018 2:39 pm Post subject: Re: Queued Pub/Sub Daemon failed, reason=00005800 Reply with quote

Sentinel

Joined: 09 May 2013
Posts: 840
Location: Bay of Plenty, New Zealand

Ulrik wrote:
CSQT855E QDSL CSQXFCTL Queued Pub/Sub Daemon failed, reason=00005800

If you look up message CSQT855E in the z/OS Messages and Codes part of Knowledge Center, you see the following explanation:-
IBM Knowledge Center wrote:
CSQT855E csect-name Queued Pub/Sub Daemon failed, reason=mqrc

Severity 8

Explanation

An attempt has been made to run the queued publish/subscribe interface (Queued Pub/Sub Daemon) but the interface has ended for reason mqrc.

If mqrc is a number in the range of 2000 - 3000, it is an API reason code. If it is of the form 5nnn, it is a queued publish/subscribe message code associated with the message CSQT nnnE, which is normally issued previously.

System programmer response

If mqrc is an API reason code, see API completion and reason codes for more information about the mqrc. If mqrc is a queued publish/subscribe message code, see the corresponding message explanation for more information. Where no such message exists, see Queued Publish/Subscribe message codes for the corresponding message number.

Determine why the queued publish/subscribe daemon ended. The message logs for the Channel Initiator might contain more detailed information about why the queued publish/subscribe daemon cannot be started. Resolve the problem that is preventing the daemon from completing and restart the Channel Initiator.


Since the reason provided in the message is a number 5nnn, it is not an MQRC number. Also there is no corresponding message CSQT5800, so you go to the page mentioned in the System programmer response and discover what the table on that page tells you. It tells you that it was an Unexpected Error.

If you have no other information in your CHINIT JOBLOG at all, then I suggest you raised a PMR with IBM. If you do have other information in your CHINIT JOBLOG, for example a SNAP DUMP or other error messages, please post them here.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Ulrik
PostPosted: Thu Aug 30, 2018 3:17 am Post subject: Re: Queued Pub/Sub Daemon failed, reason=00005800 Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

Vitor wrote:
Ulrik wrote:
I tried to google and only related hit suggest that "The storage class for the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue was NOT defined."
But it is.


Post display statements for the queue and the storage class in question.



qdsl display qlocal(SYSTEM.DURABLE.SUBSCRIBER.QUEUE) all
CSQM293I QDSL CSQMDRTC 1 QLOCAL FOUND MATCHING REQUEST CRITERIA
CSQM201I QDSL CSQMDRTC DISPLAY QLOCAL DETAILS
QUEUE(SYSTEM.DURABLE.SUBSCRIBER.QUEUE)
TYPE(QLOCAL)
QSGDISP(QMGR)
STGCLASS(SYSLNGLV)
PSID(1)
CFSTRUCT()
CLUSTER()
CLUSNL()
DESCR(Store of information about durable subscribers)
PUT(ENABLED)
DEFPRTY(0)
DEFPSIST(NO)
OPPROCS(0)
IPPROCS(0)
CURDEPTH(1)
MAXDEPTH(999999999)
PROCESS()
NOTRIGGER
MAXMSGL(104857600)
BOTHRESH(0)
BOQNAME()
INITQ()
USAGE(NORMAL)
SHARE
DEFSOPT(SHARED)
MSGDLVSQ(PRIORITY)
RETINTVL(999999999)
TRIGTYPE(FIRST)
TRIGDPTH(1)
TRIGMPRI(0)
TRIGDATA()
DEFTYPE(PREDEFINED)
NOHARDENBO
CRDATE(2014-03-23)
CRTIME(02.40.11)
GET(ENABLED)
DEFREADA(NO)
DEFPRESP(SYNC)
PROPCTL(COMPAT)
QDEPTHHI(80)
QDEPTHLO(40)
QDPMAXEV(ENABLED)
QDPHIEV(DISABLED)
QDPLOEV(DISABLED)
QSVCINT(999999999)
QSVCIEV(NONE)
INDXTYPE(CORRELID)
ACCTQ(QMGR)
MONQ(QMGR)
NPMCLASS(NORMAL)
DEFBIND(OPEN)
CLWLRANK(0)
CLWLPRTY(0)
CLWLUSEQ(QMGR)
TPIPE()
CUSTOM()
CLCHNAME()
ALTDATE(2018-07-26)
ALTTIME(14.47.23)
END QLOCAL DETAILS
CSQ9022I QDSL CSQMDRTC ' DISPLAY QLOCAL' NORMAL COMPLETION



QDSL DISPLAY STGCLASS(SYSLNGLV) ALL
CSQM293I QDSL CSQMDRTC 1 STGCLASS FOUND MATCHING REQUEST CRITERIA
CSQM201I QDSL CSQMDRTC DISPLAY STGCLASS DETAILS
STGCLASS(SYSLNGLV)
PSID(1)
QSGDISP(QMGR)
XCFGNAME()
XCFMNAME()
PASSTKTA()
DESCR()
ALTDATE(2017-01-08 )
ALTTIME(15.51.15)
END STGCLASS DETAILS
CSQ9022I QDSL CSQMDRTC ' DISPLAY STGCLASS' NORMAL COMPLETION
Back to top
View user's profile Send private message
Ulrik
PostPosted: Thu Aug 30, 2018 3:20 am Post subject: Re: Queued Pub/Sub Daemon failed, reason=00005800 Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

hughson wrote:
If you do have other information in your CHINIT JOBLOG, for example a SNAP DUMP or other error messages, please post them here.

Cheers,
Morag



I have this. I think it's related:

DATA AREAS PAGE NUMBER
----------- -----------
AREAS RELATED TO TCB AT: 009BDE88/.... 00000001
STORAGE AREAS......................... 00000001
END OF DUMP
JOB QDSLCHIN STEP QDSLCHIN TIME 123434 DATE 18241 CPUID = 0035BB472964 PAGE 00000001

PSW AT ENTRY TO SNAP 078D1000 9B3D3634 ILC 02 INTC 0033
-STORAGE
17B4F7C0 0000041C E285A2A2 89969540 C1958388 96990000 6E8697A2 * ....Session Anchor..>fps*
17B4F7E0 00000010 D8C4E2D3 40404040 40404040 40404040 40404040 40404040 40404040 *....QDSL *
17B4F800 40404040 40404040 40404040 40404040 40404040 00000000 00000000 00000000 * ............*
17B4F820 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................*
17B4F840 00000000 0000D8C4 E2D34040 40404040 40404040 40404040 40404040 40404040 *......QDSL *
17B4F860 40404040 40404040 40404040 40404040 40404040 40400000 009BDE88 009BDE88 * .....h...h*
17B4F880 00000000 00000000 00000000 00000000 00000000 00000000 00000000 E7C6E2E2 *............................XFSS*
17B4F8A0 00000000 00000000 1799B2B0 C6D4C5D4 179150D8 17B4C1A0 00000003 17915140 *.........r..FMEM.j&Q..A......j. *
17B4F8C0 00000000 00000001 00000003 40404040 40404040 40404040 40404040 40404040 *............ *
17B4F8E0 40404040 40404040 40404040 40404040 40404040 40404040 40404040 E2E8E2E3 * SYST*
17B4F900 C5D44BC2 D9D6D2C5 D94BC4C5 C6C1E4D3 E34BE2E3 D9C5C1D4 40404040 40404040 *EM.BROKER.DEFAULT.STREAM *
17B4F920 40404040 40404040 40404040 E2E8E2E3 C5D44BC2 D9D6D2C5 D94BD4D6 C4C5D34B * SYSTEM.BROKER.MODEL.*
17B4F940 E2E3D9C5 C1D40000 00000000 00000000 00000000 00000000 00000000 95968296 *STREAM......................nobo*
17B4F960 84A84040 40404040 00000000 00000001 00000001 00000001 00000001 00000001 *dy ........................*
17B4F980 00000000 00002710 0000000A 00000064 0000003C 00000005 00000200 00000080 *................................*
17B4F9A0 00000100 FFFFFFFF 000186A0 00000190 00000028 00000000 00000000 00000000 *..........f.....................*
17B4F9C0 00000000 00000000 40404040 40404040 40404040 40404040 40404040 40404040 *........ *
17B4F9E0 40404040 40404040 00000000 00000005 00000000 00000005 0000002D 00000080 * ........................*
17B4FA00 00000080 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................*
17B4FA20 00000000 00000000 00000000 00000000 00000000 00000000 00000000 FFFFFFFF *................................*
17B4FA40 E2E8E2E3 C5D44BC2 D9D6D2C5 D94BD7D9 C9D4C1D9 E84BE2E3 C1E3C500 00000000 *SYSTEM.BROKER.PRIMARY.STATE.....*
17B4FA60 00000000 00000000 00000000 00000000 E2E8E2E3 C5D44BC2 D9D6D2C5 D94BD7D9 *................SYSTEM.BROKER.PR*
17B4FA80 C9D4C1D9 E84BD9C5 E3C1C9D5 00000000 00000000 00000000 00000000 00000000 *IMARY.RETAIN....................*
17B4FAA0 C3F0F0F0 F2F7F740 40404040 00000000 00000000 00000000 00000000 00000000 *C000277 ....................*
17B4FAC0 00000000 00000000 00000000 54DA2770 00000000 00000000 00000000 00000000 *................................*
17B4FAE0 00000000 00000353 689DC1CD 00000115 00000000 00000000 00000000 00000000 *..........A.....................*
17B4FB00 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *................................*
LINES 17B4FB20-17B4FB60 SAME AS ABOVE
17B4FB80 00000000 00000000 00000000 00000000 00000000 00000000 E2E8E2E3 C5D44BC8 *........................SYSTEM.H*
17B4FBA0 C9C5D9C1 D9C3C8E8 4BE2E3C1 E3C54040 40404040 40404040 40404040 40404040 *IERARCHY.STATE *
17B4FBC0 40404040 40404040 00000000 00000000 00000000 00000000 16F24018 16F24018 * .................2 ..2 .*
17B4FBE0 000001F4 *...4 *
JOB QDSLCHIN STEP QDSLCHIN TIME 123434 DATE 18241 PAGE 00000002


It seems that this forum removes some blanks. Hope you can read it anyway.
Back to top
View user's profile Send private message
Ulrik
PostPosted: Thu Aug 30, 2018 3:32 am Post subject: Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

bruce2359 wrote:
Go to google. Search for 'CSQT855E CSQXFCTL reason=00005800' .


This leads to a 6 year old fix for MQ version 7

How ever the local fix description, made me try some things.

LOCAL FIX:
=========
The missing system objects need to be defined.
There needs to be both queue and topic objects defined for
SYSTEM.BROKER.ADMIN.STREAM and
SYSTEM.BROKER.DEFAULT.STREAM.

I tried to run the sample jobs CSQ4INSG and CSQ4INSR found in SCSQPROC

I did this to check if something else was missing. (note: that I did not install this QMGR, so I have no idea if there was problems during installation)

It defined 4 new objects and also stated some objects already exited but of different type. Maybe this an error. I'm looking into this now. But we are end end of month freeze until Wednesday, so my hands are somewhat tied. (Not allowed to restart the QMGR and so on)
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Aug 30, 2018 4:07 am Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8191
Location: US: west coast, almost. Otherwise, enroute.

Have you opened a PMR with IBM?
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
Ulrik
PostPosted: Thu Aug 30, 2018 4:43 am Post subject: Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

bruce2359 wrote:
Have you opened a PMR with IBM?


Nope. I wanted to check here first. I am in the mindset, that the QMGR is missing a simple definition here.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Aug 30, 2018 6:26 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25310
Location: Ohio, USA

Ulrik wrote:
bruce2359 wrote:
Have you opened a PMR with IBM?


Nope. I wanted to check here first. I am in the mindset, that the QMGR is missing a simple definition here.


You posted the definitions.

You need a PMR.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
hughson
PostPosted: Fri Aug 31, 2018 12:20 am Post subject: Reply with quote

Sentinel

Joined: 09 May 2013
Posts: 840
Location: Bay of Plenty, New Zealand

Ulrik wrote:
I tried to run the sample jobs CSQ4INSG and CSQ4INSR found in SCSQPROC

I did this to check if something else was missing. (note: that I did not install this QMGR, so I have no idea if there was problems during installation)

It defined 4 new objects and also stated some objects already exited but of different type. Maybe this an error. I'm looking into this now. But we are end end of month freeze until Wednesday, so my hands are somewhat tied. (Not allowed to restart the QMGR and so on)
Which objects and what type are they? Can you post the current definitions?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Ulrik
PostPosted: Fri Aug 31, 2018 5:44 am Post subject: Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

hughson wrote:
Which objects and what type are they? Can you post the current definitions?


Here are the 4 objects that was missing before I ran the sample job.

The last one is a "replace".

DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.CRLLDAP' ) +
AUTHTYPE( CRLLDAP ) +
QSGDISP( QMGR ) +

* Authentication information attributes
DESCR( ' ' ) +
CONNAME( ' ' ) +
LDAPUSER( ' ' ) +
LDAPPWD( ' ' )
CSQN205I COUNT= 2, RETURN=00000000, REASON=00000000
CSQ9022I QDSL CSQMAPRO ' DEFINE AUTHINFO' NORMAL COMPLETION



DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.OCSP') +
AUTHTYPE( OCSP ) +
QSGDISP( QMGR ) +

* Authentication information attributes
DESCR( ' ' ) +
OCSPURL( ' ' )
CSQN205I COUNT= 2, RETURN=00000000, REASON=00000000
CSQ9022I QDSL CSQMAPRO ' DEFINE AUTHINFO' NORMAL COMPLETION


DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.IDPWOS' ) +
AUTHTYPE( IDPWOS ) +
QSGDISP( QMGR ) +

* Authentication information attributes
DESCR( ' ' ) +
ADOPTCTX( NO ) +
CHCKCLNT( OPTIONAL ) +
CHCKLOCL( OPTIONAL ) +
FAILDLAY( 1 )
CSQN205I COUNT= 2, RETURN=00000000, REASON=00000000
CSQ9022I QDSL CSQMAPRO ' DEFINE AUTHINFO' NORMAL COMPLETION


DEFINE QMODEL( 'SYSTEM.MQEXPLORER.REPLY.MODEL' ) +
QSGDISP( QMGR ) +
DEFTYPE( TEMPDYN ) +
DEFREADA( YES ) +

* Common queue attributes
DESCR( 'MQ Explorer reply-to queue' ) +
LIKE( 'SYSTEM.COMMAND.REPLY.MODEL' ) +
REPLACE
CSQN205I COUNT= 2, RETURN=00000000, REASON=00000000
CSQ9022I QDSL CSQMAQLC ' DEFINE QMODEL' NORMAL COMPLETION
Back to top
View user's profile Send private message
Ulrik
PostPosted: Fri Aug 31, 2018 5:53 am Post subject: Reply with quote

Novice

Joined: 13 Dec 2017
Posts: 12

hughson wrote:
Which objects and what type are they? Can you post the current definitions?


The definitions that was already there but differnt type are posted here.

They are defined as QALIAS now because of a monitor we have. That collects these events. However I dont think this is the reason since the pub/sub daemon runs fine with this setup on many other different QMGR's.


DEFINE QLOCAL( 'SYSTEM.ADMIN.QMGR.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System queue-manager related event queue' ) +
PUT( ENABLED ) +
DEFPRTY( 0 ) +
DEFPSIST( YES ) +
CLUSTER( ' ' ) CLUSNL( ' ' ) DEFBIND( OPEN ) +
CLWLRANK( 0 ) CLWLPRTY( 0 ) CLWLUSEQ( QMGR ) +

* Local queue attributes
GET( ENABLED ) +
NOSHARE +
DEFSOPT( EXCL ) +
MSGDLVSQ( PRIORITY ) +
RETINTVL( 999999999 ) +
MAXDEPTH( 999999999 ) +
MAXMSGL( 4194304 ) +
NOHARDENBO +
BOTHRESH( 0 ) +
BOQNAME( ' ' ) +
STGCLASS( 'DEFAULT' ) +
USAGE( NORMAL ) +
INDXTYPE( NONE ) +
CFSTRUCT( ' ' ) +
MONQ( OFF ) ACCTQ( OFF ) +

* Event control attributes
QDPMAXEV( DISABLED ) +
QDPHIEV( DISABLED ) +
QDEPTHHI( 80 ) +
QDPLOEV( DISABLED ) +
QDEPTHLO( 40 ) +
QSVCIEV( NONE ) +
QSVCINT( 999999999 ) +

* Trigger attributes
NOTRIGGER +
TRIGTYPE( FIRST ) +
TRIGDPTH( 1 ) +
TRIGMPRI( 0 ) +
TRIGDATA( ' ' ) +
PROCESS( ' ' ) +
INITQ( ' ' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC QLOCAL(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS
A DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION



DEFINE QLOCAL( 'SYSTEM.ADMIN.PERFM.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System performance related event queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.CONFIG.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System configuration related event queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.COMMAND.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System command related event queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.CHANNEL.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System channel related event queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.TRACE.ROUTE.QUEUE' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System trace route recording queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.ACTIVITY.QUEUE' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System activity recording queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION

**************************************************

DEFINE QLOCAL( 'SYSTEM.ADMIN.PUBSUB.EVENT' ) +
QSGDISP( QMGR ) +

* Common queue attributes
DESCR( 'System pub/sub related event queue' ) +
LIKE( 'SYSTEM.ADMIN.QMGR.EVENT' )
CSQN205I COUNT= 5, RETURN=0000000C, REASON=00000008
CSQM099I QDSL CSQMAQLC LIKE(SYSTEM.ADMIN.QMGR.EVENT) NAME IN USE AS A
DIFFERENT TYPE
CSQM090E QDSL CSQMAQLC FAILURE REASON CODE X'00D44001'
CSQ9023E QDSL CSQMAQLC ' DEFINE QLOCAL' ABNORMAL COMPLETION
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Aug 31, 2018 8:31 am Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 8191
Location: US: west coast, almost. Otherwise, enroute.

Is the qmgr part of a QSG? If so, you will need to specify QSG group name.
_________________
I would tell you a UDP joke, but you might not get it.
Back to top
View user's profile Send private message
hughson
PostPosted: Fri Aug 31, 2018 1:23 pm Post subject: Reply with quote

Sentinel

Joined: 09 May 2013
Posts: 840
Location: Bay of Plenty, New Zealand

Ulrik wrote:
hughson wrote:
Which objects and what type are they? Can you post the current definitions?


Here are the 4 objects that was missing before I ran the sample job.

DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.CRLLDAP' ) +
DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.OCSP') +
DEFINE AUTHINFO( 'SYSTEM.DEFAULT.AUTHINFO.IDPWOS' ) +
DEFINE QMODEL( 'SYSTEM.MQEXPLORER.REPLY.MODEL' ) +

None of these objects are related to the running of the Queued Pub/Sub Daemon.
Ulrik wrote:
hughson wrote:
Which objects and what type are they? Can you post the current definitions?


The definitions that was already there but differnt type are posted here.

They are defined as QALIAS now because of a monitor we have. That collects these events. However I dont think this is the reason since the pub/sub daemon runs fine with this setup on many other different QMGR's.


DEFINE QLOCAL( 'SYSTEM.ADMIN.QMGR.EVENT' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.PERFM.EVENT' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.CONFIG.EVENT' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.COMMAND.EVENT' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.CHANNEL.EVENT' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.TRACE.ROUTE.QUEUE' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.ACTIVITY.QUEUE' ) +
DEFINE QLOCAL( 'SYSTEM.ADMIN.PUBSUB.EVENT' ) +

It is perfectly legitimate to recreate event queues as another queue type. These objects are also not used by the Queued Pub/Sub Daemon.

It would seem that none of the Queue Pub/Sub Daemon definitions were missing or incorrect?

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:
Post new topicReply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum IndexGeneral IBM MQ SupportQueued Pub/Sub Daemon failed, reason=00005800
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.