Resetting a broker on z/OS

You might want to reset the broker back to the state it was in after it was customized for the first time. For example, if you have a test system and want to delete all data to make it a production system.

The job BIPJRSTC in the component PDSE resets the broker to the state it was in after customizing for the first time and before any execution groups were deployed. This job deletes all rows in the DB2 tables for the broker. You will lose all publications or subscriptions that users have requested. You must stop the broker before submitting the job. This job:
  1. Deletes the contents of locks, log, and errors directories.
  2. Resets the ENVFILE and dsnaoini to their state after initial creation and customization; you will lose any changes you made to these files.
  3. Deletes all rows from the broker tables based on the BrokerUUID key. This includes any Publish/Subscribe subscriptions applications might have made.
  4. Deletes all messages from the WebSphere MQ queues.
  5. Resets internal files to their state after initial creation and customization. The output of this job is stored in ComponentDirectory/output/rstclog, ComponentDirectory/output/rstcerr, and in the job output.

After submitting BIPJRSTC, you must redeploy any flows, and applications must resubmit their Publish/Subscribe requests.

Related concepts
Brokers
Related reference
z/OS utility jobs