The IVP is split into eight stages; each stage must complete with a zero completion code before the next stage is run. The IVP generates a report, listing:
A sample report is provided in Figure 5
For an explanation of the completion and reason codes, see the WebSphere MQ for z/OS Messages and Codes manual.
Some stages have more than one WebSphere MQ call and, in the event of failure, a message is issued indicating the specific WebSphere MQ call that returned the failure. Also, for some stages the IVP puts explanatory and diagnostic information into a comment field.
The IVP job requests exclusive control of certain queue manager objects and therefore should be single threaded through the system. However, there is no limit to the number of times the IVP can be run against your queue manager.
The functions performed by each stage are:
To do this, the sequence of calls is:
On successful completion of this stage, the name of the system-command input queue is displayed in the comment field.
This queue is opened at this stage in anticipation of a trigger message, which arrives as a result of the command server replying to the request from Stage 5. The queue must be opened for input to meet the triggering criteria.
Upon successful completion of this stage, the name of the permanent dynamic queue is indicated in the comment field.
A message of type MQMT_REQUEST is written to the system-command input queue requesting a display of process CSQ4IVP1. The message descriptor for the message specifies the permanent dynamic queue created in Stage 4 as the reply-to queue for the command server's response.
After running the IVP, you can delete any objects that you no longer require.
If the IVP does not run successfully, try each step manually to find out which function is failing.
DATE : 2005.035 IBM WebSphere MQ for z/OS - V6 PAGE : 0001 INSTALLATION VERIFICATION PROGRAM PARAMETERS ACCEPTED. PROGRAM WILL CONNECT TO : CSQ1 ,OBJECT QUALIFER : CSQ4IVP1 INSTALLATION VERIFICATION BEGINS : STAGE 01 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR BRIDGE EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS EXCP FOR CHANNEL EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR SSL EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR INHIBITED EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR LOCAL EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR PERFORMENCE EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR REMOTE EVENTS STAGE 02 INFO: QMGR EVENT SWITCH IS OFF FOR START/STOP EVENTS STAGE 02 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 SYSTEM.COMMAND.INPUT STAGE 03 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 STAGE 04 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 CSQ4IVP1.BAB9810EFEAC8980 STAGE 05 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 STAGE 06 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 STAGE 07 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 STAGE 08 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 CSQ4IVP1.BAB9810F0070E645 STAGE 09 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 CSQ4IVP1.BAB9812BA8706803 STAGE 10 COMPLETE. COMPCODE : 0000 REASON CODE : 0000 >>>>>>>>>> END OF REPORT <<<<<<<<<<
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq83jz |