About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Quick Test After Installing Service
Last Updated: 2011-12-06 (Subscribe to updates)The test instructions in Appendix G 'Test the Installation/Service for DirMaint' of the z/VM Directory Maintenance Facility Tailoring and Administration Guide version 6 release 2 are specifically designed to systematically test the functions of the DirMaint product in a sequence such that the point of failure, if any, isolates the cause and identifies the necessary corrective action. After a period of production, there is a small likelihood that this procedure will encounter any problem, and is unnecessarily involved for routine regression testing.
This procedure provides an easier alternative. If the test is successful, testing is complete. If the test fails, there is no indication of the cause; return to and follow the more detailed steps to isolate the cause and identify the solution.
You may use these same instructions for DirMaint FL540 and FL610 by replacing 6VMDIR20 in the commands below with 5VMDIR40 and 6VMDIR10 respectively.
-
Switch the DirMaint service machines from using the
production code to use the code to be tested.
Create a PROD2TST DVHBATCH file, for example, containing the following commands:
OFFLINE DATAMOVE SHUTDOWN SATELLITE SHUTDOWN FOR DATAMOVE LINK 6VMDIR20 491 191 DELETE FOR DATAMOVE LINK 6VMDIR20 11F 11F DELETE FOR DATAMOVE LINK 6VMDIR20 492 192 DELETE FOR DATAMOVE LINK 6VMDIR20 41F 21F DELETE FOR DIRMSAT LINK 6VMDIR20 491 191 DELETEE FOR DIRMSAT LINK 6VMDIR20 11F 11F DELETEE FOR DIRMSAT LINK 6VMDIR20 492 192 DELETEE FOR DIRMSAT LINK 6VMDIR20 41F 21F DELETEE FOR DIRMAINT LINK 6VMDIR20 491 191 DELETE FOR DIRMAINT LINK 6VMDIR20 11F 11F DELETE FOR DIRMAINT LINK 6VMDIR20 492 192 DELETE FOR DIRMAINT LINK 6VMDIR20 41F 21F DELETE FOR DATAMOVE LINK 6VMDIR20 492 191 RR FOR DATAMOVE LINK 6VMDIR20 41F 11F RR FOR DATAMOVE LINK 6VMDIR20 491 192 RR FOR DATAMOVE LINK 6VMDIR20 11F 21F RR FOR DIRMSAT LINK 6VMDIR20 492 191 RRR FOR DIRMSAT LINK 6VMDIR20 41F 11F RRR FOR DIRMSAT LINK 6VMDIR20 491 192 RRR FOR DIRMSAT LINK 6VMDIR20 11F 21F RRR FOR DIRMAINT LINK 6VMDIR20 492 191 MR FOR DIRMAINT LINK 6VMDIR20 41F 11F MR FOR DIRMAINT LINK 6VMDIR20 491 192 MR FOR DIRMAINT LINK 6VMDIR20 11F 21F MR FOR DATAMOVE REVIEW NOPROF FOR DIRMSAT REVIEW NOPROFF FOR DIRMAINT REVIEW NOPROF CP MSG your_id PROD2TST IS DONE!
-
Submit this batch job to the DIRMAINT server using the
following command:
DIRM BATCH PROD2TST DVHBATCH
-
When the job has completed successfully, and you have
reviewed the returned reader files verifying the LINK statements are
correct, issue:
DIRM DIRECT DIRM SHUTDOWN
-
Then issue the following commands:
CP XAUTOLOG DIRMAINT CP SLEEP 1 MIN CP XAUTOLOG DIRMSAT CP XAUTOLOG DATAMOVE
-
Run a test that exploits most of DirMaint's critical code paths.
Issue the following commands:
DIRM ONLINE DIRM FOR any_id AMDISK 555 3390 AUTOG 1 groupname M
You may substitute other values for the virtual address, device type, size, or groupname; as appropriate for your installation. This tests the communication paths between the originating user and the DIRMAINT server, the parser, message handler, and the path between DIRMAINT and the DIRMSAT servers, if any. -
Reverse the previous step by
issuing the following command:
DIRM FOR any_id DMDISK 555 CLEAN
This retests the same paths as the previous step, and adds the communication paths between DIRMAINT and the DATAMOVE server, and from DATAMOVE back to DIRMAINT. -
Switch the DirMaint service machines from using the
test code back to use the production code.
Create a TST2PROD DVHBATCH file, for example, containing the following commands:
OFFLINE DATAMOVE SHUTDOWN SATELLITE SHUTDOWN FOR DATAMOVE LINK 6VMDIR20 492 191 DELETE FOR DATAMOVE LINK 6VMDIR20 41F 11F DELETE FOR DATAMOVE LINK 6VMDIR20 491 192 DELETE FOR DATAMOVE LINK 6VMDIR20 11F 21F DELETE FOR DIRMSAT LINK 6VMDIR20 492 191 DELETEE FOR DIRMSAT LINK 6VMDIR20 41F 11F DELETEE FOR DIRMSAT LINK 6VMDIR20 491 192 DELETEE FOR DIRMSAT LINK 6VMDIR20 11F 21F DELETEE FOR DIRMAINT LINK 6VMDIR20 492 191 DELETE FOR DIRMAINT LINK 6VMDIR20 41F 11F DELETE FOR DIRMAINT LINK 6VMDIR20 491 192 DELETE FOR DIRMAINT LINK 6VMDIR20 11F 21F DELETE FOR DATAMOVE LINK 6VMDIR20 491 191 RR FOR DATAMOVE LINK 6VMDIR20 11F 11F RR FOR DATAMOVE LINK 6VMDIR20 492 192 RR FOR DATAMOVE LINK 6VMDIR20 41F 21F RR FOR DIRMSAT LINK 6VMDIR20 491 191 RRR FOR DIRMSAT LINK 6VMDIR20 11F 11F RRR FOR DIRMSAT LINK 6VMDIR20 492 192 RRR FOR DIRMSAT LINK 6VMDIR20 41F 21F RRR FOR DIRMAINT LINK 6VMDIR20 491 191 MR FOR DIRMAINT LINK 6VMDIR20 11F 11F MR FOR DIRMAINT LINK 6VMDIR20 492 192 MR FOR DIRMAINT LINK 6VMDIR20 41F 21F MR FOR DATAMOVE REVIEW NOPROF FOR DIRMSAT REVIEW NOPROFF FOR DIRMAINT REVIEW NOPROF CP MSG your_id TST2PROD IS DONE!
-
Submit this batch job to the DIRMAINT server by issuing
the following command:
DIRM BATCH TST2PROD DVHBATCH
-
When the job has completed successfully, and you have
reviewed the returned reader files verifying the LINK statements are
correct, issue
the following commands:
DIRM DIRECT DIRM ONLINE DIRM SHUTDOWN
Note: The FOR DATAMOVE commands in this batch file must be duplicated for each DATAMOVE server, and the FOR DIRMSAT commands must be duplicated for each defined satellite server.
Note: A CP XAUTOLOG command must be issued for all configured DATAMOVE and DIRMSAT servers.
Note: The FOR DATAMOVE commands in this batch file must be duplicated for each DATAMOVE server, and the FOR DIRMSAT commands must be duplicated for each defined satellite server.
If you'd like to contact DirMaint development and support, you can
e-mail
Patricia Rando
(
randopm@us.ibm.com ), DirMaint Team Leader.
Thank you for visiting this web page. Please visit again next month and check out the latest news. (Or, subscribe to future updates.)