Running the Customization Verification Program (CVP)

This is part of the larger task of creating a broker on z/OS.

Before you start

Before starting this step, you must have completed Copying the broker started task procedure

Submit the BIP$JCVP job from your PDSE. Check the job log for messages and return codes. If you did not get any error messages, all the steps in the job had return code 00, and the BAD step was flushed, the CVP ran successfully. Move to the next step.

The Customization Verification Program (CVP) consists of two steps:

CVP step 1: check set up

The shell script mqsichecksetup checks the following:
  1. That the root directory of the component directory exists.
  2. The customization log file <ComponentDirectory>/output/Customizelog for errors. The customization process logs its progress and return codes in this file.
  3. The structure of the component directory tree.
  4. Registry entries against values in mqsicompcif.
  5. The contents of the environment file ENVFILE against values in mqsicompcif.
  6. The contents of the ODBC initialization file dsnaoini against values in the mqsicompcif (broker only).
The result of all these checks is logged in <ComponentDirectory>/output/cvpslog. Error messages are written to <ComponentDirectory>/output/cvpserr.

CVP step 2: DB2 and WebSphere MQ checks

This step checks whether DB2 and WebSphere MQ resources are set up correctly. These checks use the component's environment file ENVFILE and the ODBC initialization file dsnaoini located in the root directory of the component directory. The following checks are performed:
  1. Use ODBC to select all component tables (broker only).
  2. Put and get messages to and from all component queues.
The result of all checks is logged in <ComponentDirectory>/output/cvpplog. Error messages are written to <ComponentDirectory>/output/cvpperr.

After running the CVP

Check the console, job listings, and the cvpslog and the cvpserr files in the /output subdirectory of your broker. For example from TSO, issue:
obrowse /var/wmqi/MQP1BRK/output/cvpslog

Successful completion of the CVP is indicated by rc=0 on all the job steps of BIPJCVP.

Problems running the CVP

You should investigate any of the following errors further:
CVP job step Return code Description Action
1 4 Indicates that not all the customization steps have been performed. This is not considered an error because the customization is not yet complete. Finish the customization steps.
1 8 Indicates that at least one of the customization steps has reported an error. Check the following log files:
  • <ComponentDirectory>/output/Customizelog
  • <ComponentDirectory>/output/cvpslog
  • <ComponentDirectory>/output/cvpserr
  • <ComponentDirectory>/output/cvpplog
  • <ComponentDirectory>/output/cvpperr
Take the appropriate actions. A recustomization might be needed.
2 8 Indicates that either access to the broker database or access to the WebSphere MQ queues has failed. Check the following log files:
  • <ComponentDirectory>/output/Customizelog
  • <ComponentDirectory>/output/cvpslog
  • <ComponentDirectory>/output/cvpserr
  • <ComponentDirectory>/output/cvpplog
  • <ComponentDirectory>/output/cvpperr
Take the appropriate actions. A recustomization might be needed.
Related concepts
Brokers
Broker domains