The queue and queue manager values are required in
SAS applications that use the WebSphere MQ functional interface. In
the previous examples, the queue manager is named MYQMGR, and the
queue is named REQUEST. These values are used as follows in the SAS
DATA step application:
hConn=0;
Name="MYQMGR";
compCode=0;
reason=0;
CALL MQCONN(Name, hConn, compCode, reason);
action = "GEN";
parms="OBJECTNAME";
objname="REQUEST";
call mqod(hod, action, rc, parms, objname);
options="INPUT_SHARED";
call mqopen(hconn, hod, options, hobj, compCode,
reason);
If a SAS application is running as a WebSphere MQ Client,
then you must include the following line of code before making any
calls using the WebSphere MQ Functional Interface. This line should
be placed at the beginning of the application, before the DATA step,
as shown in the following example:
%let MQMODEL=CLIENT;
data _null_;
...
run;
Common WebSphere MQ Application Error Codes
|
|
|
|
A connection handle
is invalid.
|
A connection handle
that is created by an MQCONN call must be used within the same DATA
step where it was created.
|
|
The user is not authorized
to perform the attempted action.
|
Verify that you are
connecting to the correct queue and queue manager. Verify that you
are authorized to connect to the queue manager. If error is reported
to a client connecting to a queue manager, you might need to set the
user ID under the MCA tab in the server connection channel definition
properties to a user ID that has permission to access the queue manager
on the server machine.
|
|
There is an error in
the queue manager name.
|
Check spelling and case
of the queue manager name that is used in the application and is defined
in the queue manager.
|
|
The queue manager is
not available.
|
Restart the queue manager.
|
|
The object name is unknown.
|
Check spelling and case
of the queue name that is used in the application and is defined in
the queue manager.
|
|
|
See WebSphere
MQ Messages at www.ibm.com .
|