Testing CA Disk after Installing › Testing the CA Disk Auto-Restore Feature › Forcing an Auto-Restore to be Initiated › Testing Auto-Restore in a Production Environment

Testing Auto-Restore in a Production Environment

Many possible job combinations can be run to simulate production environments. The following list details possible tests that can be run. The output reports created by the system task DMSAR should be routed to hard copy so you can review. All data set references in the examples are to non-existent data sets; that is, no format-1 DSCBs exist for the data set.

1. Run a test specifying a data set that can be found in the archives index, and one that cannot.
2. Execute two auto-restore tasks simultaneously by forcing two jobs to execute at the same time (their job names must be different), each job requesting a different archived data set.
3. Try running the test as in 2 above, but this time reference different data set names that reside on the same archive tape volume (you will have to do a LISTD on an archive volume to find a suitable pair of data sets).
4. If you are supplying an ARESPREX screening exit, or using other options to tailor the function to your environment, try running a few conditions that test your implementation. Make sure the restore requests are processed as expected.