Resolution:
Description:
============
The Hotfix maintenance is packaged such that some minor JCL revisions must be made prior to running your SMP/E JCL to receive and apply Hotfix maintenance. One such revision concerns whether or not you are using the IBM WebSphere MQ messaging interface. The hotfix JCL typically has comments such as:


//*---------------------------------------------------------------*
//* The next DD stmt points to the MQ SERIES library used as      *
//* CALLLIBS. If MQ SERIES is not installed in your site, leave   *
//* the SCSQLOAD DD stmts as they are. If you have installed      *
//* Websphere MQ SERIES, delete the first SCSQLOAD DD stmt and    *
//* uncomment the second one. Rename it to match your site's      *
//* convention as required.                                       *
//*---------------------------------------------------------------*
//SMP.SCSQLOAD DD DSN=$HLQNONV$.V5R0M0.DIST.OBJECT,                
//*SMP.SCSQLOAD DD DSN=$MQMLIB$.SCSQLOAD,                          
//             DISP=SHR                                            

The first JCL statement references a "dummy" stub used by non-MQ Series installations whereas the second statement references the true MQ Series interface module if you are using and have installed that interface.

If you inadvertently link in the dummy stub, you will not be able to access MQ messages from the Object Service Broker. Function can only be restored if the correct interface module is linked into your system. Typically, the failure will be:
  Exception "MOM_NO_MQSSTUB" signaled  


Environment:
==========
-TIBCO Object Service Broker for z/OS installed and executing on z/OS
-TIBCO Object Service Broker session accessing MQ Series messages


Symptoms:
=========
The exception:
   Exception "MOM_NO_MQSSTUB" signaled  
will be raised if an attempt is made to access MQ Series messages.  



Cause:
=====
If the dummy interface stub is accidentally linked into your SMP/E environment, accessing the MQ Series messaging system will not be functional.

Resolution:
=========
The correct MQ Series interface stub must be linked into your executable library by SMP/E. To do this, you can modify the original SMP/E USERMOD(S6BU50M) as documented below and re-apply the S6BU50M usermod to your SMP/E environment:

1) change the ++USERMOD statement in &ltHLQ>.&ltINSTVER>.WMQ.INSTALL(S6J3APLY)
   from
     ++USERMOD(S6BU50M) REWORK(0) .  
   to
     ++USERMOD(S6BU50M) REWORK(1) .  

2) change the APPLY statement from in &ltHLQ>.&ltINSTVER>.WMQ.INSTALL(S6J3APLY)
     APPLY S(S6BU50M) .  
   to
     APPLY S(S6BU50M) REDO.

Make sure your DD statement is pointing to the MQ Series library and not the "dummy" version:

//*---------------------------------------------------------------*
//* NEXT DD STMT POINTS TO THE MQSERIES LOAD LIBRARY USE AS       *
//* CALLLIBS. RENAME IT TO MATCH YOUR SITE'S CONVENTION AS        *
//* REQUIRED.                                                     *
//*---------------------------------------------------------------*
//SMP.SCSQLOAD DD DSN=$MQMLIB$.SCSQLOAD,                            
//             DISP=SHR                                            

3) run &ltHLQ>.&ltINSTVER>.WMQ.INSTALL(S6J3APLY) to reapply the SMP/E USERMOD(S6BU50M)which will install the correct MQ Series interface stub.


References:
==========
TIBCO® Object Service Broker for z/OS External Environments
TIBCO® Object Service Broker for z/OS Hotfix READMEs
TIBCO® Object Service Broker for z/OS Installing and Operating

After applying TIBCO Object Service Broker for z/OS Hotfix maintenance and accidentally linking the dummy IBM WebSphere MQ messaging interface stub instead of the real interface, how can I correct my SMP/E load library?