Instructions to Synchronize the Dispatch OV and LDS files
Article ID: 280810
Updated On:
Products
Issue/Introduction
You've received a Dispatch or CADDSPLx environment related error and have been instructed by Support to execute the OV / LDS synchronization utility. What are the best practices for executing this utility when messages similar to the following are being received:
DCD0153E - LDSRPT RPT Name Does Not Match
DCD0153E - LDSRPT RPT Name Does Not Match
DCD0152E - LDS Function GETRP Unsuccessful
DCD0037E Bad return code from module CADSVMSG return code was #04
Environment
Dispatch, 11.7, 11.6, z/OS, out of sync, lds, ov, utility synchronization
Cause
An out of synchronization condition exists between the data being stored in the Dispatch LDS files and the OV database file which contains the pointers to that data in the LDS's.
Resolution
* Instructions to Synchronize the OV and LDS files.
* CRITICAL *
- MUST HAVE APAR RO29290 applied if 11.6 BEFORE EXECUTING SYNC UTILITY
- MUST HAVE APAR RO58875 applied if 11.7 BEFORE EXECUTING SYNC UTILITY
* Make sure that that you meet the following required PRE-EXECUTION criteria before executing the "SYNC" utilities.
* Meeting PRE-EXECUTION CRITERIA requires that the CADZSPLx TASK be ACTIVE.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Detailed instructions for meeting the PRE-EXECUTION CRITERIA...
- You need to make sure that before beginning the resolution process, that all data that has already been pulled into the
existing LDS files gets processed by the various Dispatch subtasks and ARCHIVED to tape. To do this, with both Dispatch
and the CADZSPLn tasks active...
1. Disable any new data from coming into the LDS by turning off the dynamic INTERCEPT function and stopping the SAPI tasks.
* Take a SCREEN PRINT of the VOPMI100 screen first!! You can use this screen print as a reference for turning
dynamic intercept back on and restarting the SAPI tasks.
- To turn off the DYNAMIC INTERCEPT, tab down next to any task on the VOPMI100 screen (option 8.1 from main menu) and type
an 'I' next to any task that shows a status of "ON". Don't worry if the status shows ACTIVE or NOT ACTIVE at this
point. What's important is that the tasks show "OFF" Example:
ARCH1 ACTIVE Off
ARCH2 Not Act Off
ARCH3 Not Act Off
EXTRACT ACTIVE
RPI1 ACTIVE Off
RPI2 Not Act Off
RPI3 Not Act Off
- To stop the SAPI tasks, tab down next to any of the SAPInnnn tasks on this same screen and type an 'E" next to the task.
They should all show as:
SAPIRPI1 Not Active
SAPIRPI2 Not Active
SAPIRPI3 Not Active
SAPIMSG Not Active
SAPIARCH Not Active
2. Access Dispatch and go through the various queues under RIDF (option 8.2 from main menu). Check the RPI, MSG, ARCHIVE,
ARCHDUP and ARCHRES queues under RIDF. Make sure all data has been processed. These queues must all be EMPTY prior to
executing the SYNC utilities.
3. Access the VRDMU820 screen (option 8.3.1 from main menu) and make sure all active bundles have been closed and written to
the JES2 queue. The screen should show a DC900044 THERE ARE NO ACTIVE BUNDLES message before continuing the process.
...
4. Once all of the above criteria has been met, if you are going to execute a version of the SYNC utility that runs with Dispatch
down, you can now issue the STOPCADS command to initiate the shutdown process. Make sure Dispatch comes down CLEAN.
5. If running the SYNC utility with MODE=DELETE, consider running DFDSS (or a similar product) backups of ALL Dispatch database and
LDS files just in case.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Instructions for executing the SYNC utilities...
Customers who need to run the LDS/OV Synchronization Utility should refer to the Dispatch documentation, which is documented in the UTILITIES chapter 13 of the System Programmers Guide. We suggest you run the utility with ALL 3 control parms coded in the DSOVSYNC member. If we only SUSPECT that you have an "out of sync" condition, you should execute the utility will all three control parameters specifying MODE=TEST. The CADZSPL task MUST be active and CANNOT be QUIESCED.
Example of PPOPTION/CAIOPTN/CADSOPTN library member DSOVSYNC:
TYPE=OVSYNC,MODE=TEST,DATE=NONE
TYPE=LDSSYNC,MODE=TEST,DATE=NONE
TYPE=ORPHAN,MODE=TEST,DATE=NONE
If the output from the SYNC utility run in TEST mode lists ANY reports under any of the control parameters as being "out of sync", Or, if we ALREADY KNOW
that an "out of sync" condition exists, then you should execute the utility with the CADZSPLx task ACTIVE (and not QUIESCED) and all three control
parameters specifying MODE=DELETE.
EXAMPLE of PPOPTION/CAIOPTN/CADSOPTN library member DSOVSYNC:
TYPE=OVSYNC,MODE=DELETE,DATE=NONE
TYPE=LDSSYNC,MODE=DELETE,DATE=NONE
TYPE=ORPHAN,MODE=DELETE,DATE=NONE
* KEEP ANY ONLINE VIEWING ONLY REGION SHUT DOWN WHILE THIS PROCESS IS EXECUTING.
There are versions of the SYNC utility that run with Dispatch active and versions that run with Dispatch down. See chapter 13 for details. Since
you will be running with all 3 control parms, it doesn't really matter which job you run, just make sure you execute the correct proc depending
on the status of the Dispatch STC.
Additional Information
- If you are running release 11.6 of CA Dispatch you must have APAR RO29290 applied before executing the SYNC utility.
- If you are running release 11.7 of CA Dispatch you must have APAR RO58875 applied before executing the SYNC utility.
- The LDS/OV Synchronization Utilities are documented in the CA Dispatch System Programmers Guide in chapter 13 entitled UTILITIES.
- Link to the legacy CA Dispatch documentation bookshelf can be found HERE.
Feedback
