Error messages: IBM® WebSphere® MQ on IBM® z/OS®

Certain error messages might be displayed while you are using IBM® WebSphere® MQ on IBM® z/OS® systems.

Message title Explanation Severity System action Response

RIT100I HCL DevOps Test Integrations and APIs (Test Integrations and APIs) for z/OS®, component 5725G79IT

This message is issued when the Test Integrations and APIs job starts.

RIT001S load of message module RITMSG failed

The Test Integrations and APIs job was unable to load the module RITMSG by using the C runtime FETCH function. The SYSOUT dataset contains a message that gives the reason.

For example: Load of RITMSG: EDC5239S Fetched module not found. (errno2=0xC4070044)

 12

The Test Integrations and APIs job ends.

Determine why the module failed to load. Resolve the problem and restart the job.

RIT002I Abnormal end detected

The Test Integrations and APIs job detected that it was canceled, or an ABEND was detected.

 0

The Test Integrations and APIs job ends.

Resolve the problem and restart the job.

RIT003I Clean up successful

After message RIT002I, the Test Integrations and APIs job was able to recover and shut down successfully.

 0

The Test Integrations and APIs job ends.

 None

RIT004I Recovery routine entered

The Test Integrations and APIs job detected an error occurred and entered a recovery routine.

 0

The Test Integrations and APIs job retries the operation. If it is unable to recover, the job ends.

Restart the job if required.

RIT005S RIT Error recovery routine: RIT now inactive

The Test Integrations and APIs intercept exit detected that an error occurred and entered a recovery routine.

 0

The Test Integrations and APIs exit is set to inactive and stops intercepting messages.

A dump is produced.

RIT010I LPA module information HRVMMQF 5725G79IT V800 Fix:30794 11/22/12 12.30

The Test Integrations and APIs job reports information about the HRVMMQF module in the LPA. In this case, HRVMMQF 5725G79IT V800 Fix:30794 11/22/12 12.30, where 5725G79IT is the component number. You need this if you have to contact your service representative. V800 is the version. Fix:30794 is the fix number of the module. 11/22/12 12.30 is the date and time that the module was generated.

 0

You can use this to verify that you are using the correct version.

RIT100E Required parameter is missing QM(aaaa)

The required queue manager name was not specified at the Test Integrations and APIs job start.

 8

The Test Integrations and APIs job ends.

Specify the queue manager name by using the format QM(name) and restart the job.

RIT101E Invalid QM(value) specified. Where value is a string of length 1-4 characters.

The QM parameter was specified, but had an invalid value. The value is a string of characters 1 - 4 characters in length.

 8

The Test Integrations and APIs job ends.

Specify the queue manager name correctly and restart the job.

RIT102E Invalid TRACE(value) specified. Value must be a number in range 0-9.

The optional TRACE parameter was specified, but had an invalid value. The value must be a number in the range 0-9.

 8

The Test Integrations and APIs job ends.

Specify the correct value and restart the job.

RIT103E Unknown parameter (1) ignored

An unknown parameter (1) was specified at startup.

 8

The Test Integrations and APIs job ends.

Remove the invalid parameter and restart the job.

RIT104I Queue Manager: (1)

The Test Integrations and APIs job reports the value (1) of the specified queue manager to be used.

 0

None

RIT105I Trace: (1)

The Test Integrations and APIs job reports the value (1) of the specified TRACE parameter to be used.

 0 None

RIT110E MQCONN to (1) cc (2) rc (3) (4)

The Test Integrations and APIs job was unable to connect to the specified queue manager.

  • Queue manager name (1)
  • MQ Condition code (2)
  • Reason code value (3)
  • Reason code description(4)

For example

RIT110E MQCONN to MQPA cc 2 rc 2059 MQRC_Q_MGR_NOT_AVAILABLE

 8

The Test Integrations and APIs job ends.

Resolve the problem and restart the job.

RIT111E MQOPEN for (1) cc (2) rc (3) (4)

The Test Integrations and APIs job was unable to open the queue.

  • Queue name (1)
  • MQ Condition code (2)
  • Reason code value (3)
  • Reason code description(4)

For example


RIT111E MQOPEN for COM.GREENHAT.COMMAND.QUEUE cc 2 rc 2085 
MQRC_UNKNOWN_ OBJECT_NAME
8

The Test Integrations and APIs job ends.

Resolve the problem and restart the job.

RIT112E MQGET from (1) cc (2) rc (3) (4)

RIT was unable to get from the queue,

  • Queue name (1)
  • MQ Condition code (2)
  • Reason code value (3)
  • Reason code description (4)
 8

The Test Integrations and APIs job ends.

Resolve the problem and restart the job.

RIT113I Queue Sharing Group: (1)

 RIT determined that the queue manager belongs to a queue sharing group named (1). 0 None

RIT114E Error encountered while querying Queue Sharing Group name.

 RIT was unable to successfully query the queue manager. 8 The Test Integrations and APIs job ends. Verify that the user id associated with the job has sufficient authority to issue the DISPLAY QMGR QSGNAME command.
RIT115I Queue sharing namelists not found. Shared queue support disabled. The queue manager is part of a queue sharing group, however, the following Test Integrations and APIs namelists required to support shared queues do not exist:
  • COM.GREENHAT.INTERCEPT.qqqq
  • RIT.DIVERT.RULES.qqqq

where qqqq is the four- character name of the queue manager.

 4 The Test Integrations and APIs job continues, but some messages placed on shared queues may not be captured or diverted. If there is a requirement to capture or divert messages placed on a shared queue from any queue manager in the queue sharing group, ensure that the required Test Integrations and APIs namelists and queues have been created for each queue manager in the group. For details, see Setting up IBM WebSphere MQ and installing the HRVMMQF agent .

RIT116E Required namelists not found. Unable to continue.

 Neither the Test Integrations and APIs namelists required for queue managers that are part of a queue sharing group, nor the Test Integrations and APIs namelists required for stand alone queue managers exist. 8 The Test Integrations and APIs job ends. Create the namelists required by Test Integrations and APIs. For details, see Setting up IBM WebSphere MQ and installing the HRVMMQF agent.

RIT201E (1) is not APF authorized

The RIT STEPLIB libraries need to be APF authorized. Check that all datasets in STEPLIB are APF authorized. (1) is the name of the program that needs to be APF authorized

 8

The Test Integrations and APIs job ends.

An authorized person can use the MVS™ operator command.


D PROG APF,DSN=.....

to display the APF status of the specified dataset.

Resolve the problem and restart the job.

RIT202E Unable to get lock - is there an instance that is running?

The Test Integrations and APIs job obtains a lock that is based on the queue manager name to ensure that there is only one instance of the job that is running. It was unable to get the lock.

 8

The Test Integrations and APIs job ends.

Check to see if another instance of the Test Integrations and APIs job is running with same queue manager specified.

RIT203E Unable to locate HRVMMQF in LPA

The Test Integrations and APIs job requires module HRVMMQF to be in the LPA. The job was not able to locate it.

 8

The Test Integrations and APIs job ends.

Check to see whether RITLINK library was added to the LPA. An authorized person can issue the MVS™ operator command D PROG,LPA,MODNAME=HRVMMQF to display information about the module in the LPA.

RIT204E CSVQUERY return code (1) locating HRVMMQF in LPA.

The MVS™ CSVQUERY macro was used to locate the module in the LPA. The request was unsuccessful, and the return code was (1).

 8

The Test Integrations and APIs job ends.

Resolve the problem and restart the job.

RIT205S Internal error function (1) (2) code (3) trace (4)

The Test Integrations and APIs job was unable to start successfully due to an internal error.

 8

The Test Integrations and APIs job ends.

RIT205E Unable to start RIT job. Return code (1) trace (2)

The Test Integrations and APIs job was unable to start successfully due to an internal error.

 8

The job ends.

RIT300I No queues being monitored

A display command was issued, but there are no queues that are being monitored.

RIT301I Output from Display command

The display command produces several lines of output for each queue that is being monitored. There are two or three header lines and multiple sections of two or three lines each. With each intercepted queue, the output includes the queue name itself, the destination queue name, and the queue manager name.

If a destination queue is on the local queue manager, the queue manager name is not displayed.


RIT301I Output from Display command 
Queue Name                                   successful errors 
   Target Queue Name                     successful errors
CP0000                                            2      0
   XCP0000                                      2      0
   Last successful put at 2012/10/17,14:50:23 
CP0001                                2      0
   XCP0001                                      0      2
   MQ Reason code 2085, MQRC_UNKNOWN_OBJECT_NAME at 2012/09/   
06,16:47:45

This shows that two queues were intercepted, CP0000 and CP0001. One message was successfully put to queue CP0000. This was successfully put to the destination queue XCP0000.

One message was successfully put to queue CP0001, but there was an error put this to destination queue XCP0001.

The last error that is detected is MQ reason code 2085, which is MQRC_UNKNOWN_OBJECT_NAME. Which occurred on 2012/09/06 at 16:47:45.

If there is at least one instance where the queue manager for the destination queue is not the name of the local queue manager, the output is as follows:


RIT301I Output from Display command 
Queue Name                 successful    errors
   Target Queue Name     successful    errors
      Target Queue Manager Name
CP0000          1      0
   XCP0000                1      0
   Last successful put at 2012/11/05, 09:59:22
INPUTQ*                             0      0
   XCP00002                         0      0
      MQ004
MQ04 Where MQ04 is the remote queue manager.

If there was a problem with putting the message to the destination queue, information about the error is displayed, for example:


RIT301I Output from Display command 
Queue Name              successful    errors
   Target Queue Name    successful   errors
CP0000         2      0
   XCP0000        0      2
MQ Reason code 2051, MQRC_PUT_INHIBITED at 2012/09/12,08:31:25

Where the time (08:31:25) is local time. If the problem is resolved and puts to this queue are successful, this message continues to be displayed.

Check the last successful put at... to see if the problem was resolved.

If the refresh command is issued these errors are reset.

 0

RIT307E Unable to allocate storage - display command failed

The Test Integrations and APIs job was unable to allocate storage to process the display command.

 8

No data is displayed. The job continues to run.

Increase the region size on the EXEC PGM statement in the Test Integrations and APIs JCL and restart the job.

RIT311W Zero MQMD pointer on MQPUT at (1)

This can occur when you are using message properties.

This message is produced when a Display command is issued.

(1) Is the time when the most recent occurrence occurred.

 4

The application request is not copied to the target queue

To intercept these requests, change the application to specify an MQMD.

RIT312W Unsupported level of MQPMO at (1)

An MQPUT or MQPUT1 request was issued by using an unsupported level of the MQPMO.

This message is produced when a Display command is issued.

(1) Is the time when the most recent occurrence occurred.

 4

The application request is not copied to the target queue.

RIT320I Invalid DIS command, syntax is DIS, DIS ALL, or DIS ERROR.

An invalid DIS command was issued. The following commands are valid:

DIS ALL Displays information about all queues that are being monitored.

DIS ERROR Displays information about those queues, which had an error.

DIS Displays queues that processed messages.

 0

Enter the correct syntax.

RIT321E Problem allocating storage during intercept request.

When the RIT exit was intercepting a message, it was unable to allocate storage for a copy of the message.

 8

No data is displayed. The Test Integrations and APIs job continues to run.

Increase the region size of the job that is putting the message and restart this job.

RIT322I No records found matching request

A display DIS or DIS ERRORs command was issued, but no queues were used, so there were none to display.

 0

To display information about all queues, use the DIS ALL command.

RIT331I RIT interception is active.

The Test Integrations and APIs job is active and able to intercept messages.

 0 None

RIT332W RIT interception is inactive

The Test Integrations and APIs job is active, but the exit is not intercepting messages. The exit detected a problem and deactivated further interceptions.

 4

Look for RIT005S messages and resolve any problems.

Issue the F ritjob,REFRESH command to reload the current list of queues and reactivate the interception.

RIT400S MQOPEN for Namelist (1) cc (2) rc (3) (4)

The Test Integrations and APIs job was unable to open the following.

  • Namelist (1)
  • MQ Condition code (2)
  • Reason code value (3)
  • Reason code description(4)
 8

The Test Integrations and APIs job shuts down.

Resolve the problem and restart the job.

RIT401S MQINQ for Namelist (1) cc (2) rc(3) (4)

The Test Integrations and APIs job was unable to INQ on the following.

  • Namelist (1)
  • MQ Condition code (2)
  • Reason code value (3)
  • Reason code description (4)
 8

The Test Integrations and APIs job shuts down.

Resolve the problem and restart.

RIT402W No entries in name list (1)

The Test Integrations and APIs job namelist exists, but contains no entries.

 4

Configure queues to be monitored.

RIT403E Namelist (1) has invalid number of entries(2)

The Namelist (1) has entries for each queue monitoring. The number of entries in the namelist is not a multiple of 3.

 8

The namelist is ignored.

Resolve the problem.

RIT404I Refresh queue list successful using list from (1) at (2)

The monitored queue list was refreshed, by using the namelist that was last altered at time (2) on date (1).

For example: RIT404I Refresh queue list successful using list from 2012-09-01 at 13.52.34

 0

RIT405E Refresh queue list unsuccessful rc (1)

The Test Integrations and APIs job was unable to replace the list of queues to be monitored, which is an internal error.

 8

RIT410E Unable to decode character (1) in string (2) in Namelist

There is an invalid character (1) in the entry (2) in the namelist.

 8

The namelist is ignored.

Re-create the namelist.

RIT450E Internal error processing command (1) (2)

An internal error occurrs when you are processing a command

 8

The Test Integrations and APIs job ends.
RIT512S (or RIT511S, RIT513S, or RIT514S) Failure while checking authorization. The Test Integrations and APIs job encountered an error while checking authorization. 8 The Test Integrations and APIs job continues to run, however, the recording or stubbing rule is ignored. This message should be accompanied by RIT501I and RIT502I messages listing the RACROUTE return code, the SAF return code, and the RACF reason code. Review these return codes to determine the cause of the problem.

RITM709S QAREA length error, Test Integrations and APIs now inactive.

The HRVMMQF LPA module does not match the level of the HRVMSTRT module within the RITAUTH data set.

 12

RIT recording is deactivated.

Restart the Test Integrations and APIs Agent by using the RITAUTH data set that was obtained from the same IBMWebSphereMQz.zip file as the HRVMMQF LPA module.

RIT8806E Failed to start proxy route: An exception occurred while adding a rule to the rules namelist [RIT.DIVERT.RULES]

When you use a queue for the stub update locking mechanism, the stub fails to start with RIT8806E shown.

To find the cause, go to the JVM console to see the following message.

WARNING: Could not lock namelist as could not access the queue: RIT.DIVERT_RULES_LCK. com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2085'.

As an administrator either create the queue named in the JVM console, or to give the RIT user sufficient authority to create queues.

Note that in the former case, where the queue manager is in a Queue Sharing Group, a shared queue should be created.