HP 3000 Manuals HP 3000 Manuals
Creating the Migration Planning Tool Database You must create the MPTDB database before you can generate MPT migration planning reports. Two MPT programs, MPT.MPT.TELESUP and MPTRTM.MPT.TELESUP, are used to create the database and load it with data collected from files located on the system being analyzed. Normally, you need only create the database once for each system being analyzed. If the database already exists from a previous run, new information is appended. It is recommended that you create the MPTDB database using the MPTJOB .MPT.TELESUP job stream file supplied by the MPT/3000 product. (Refer to "Running MPT in Batch Mode" for details.) This batch job will also generate a set of migration planning reports and an installed product report.
NOTE You should run the RTM before running MPT. Migration event data placed by RTM in system log files can be collected by MPT into the MPTDB database and accessed whenever MPT generates migration reports. MPT can be run without benefit from RTM but the quality of the reports is greatly improved if this data is available.
To create the MPTDB database, follow the steps outlined below. Some of the steps are not required, but all must be considered:. 1. Run RTM: For details on using RTM, refer to Appendix C, "Using the Run Time Monitor". 2. Size the Database: In order to properly size the data sets in this database, MPT must know approximately how many disk files the database will hold. If the database is built too small, MPT or successive programs will abort with database errors. To avoid errors, size the database slightly larger than the estimated need. MPT determines the maximum allowable size of the database by checking the MAXFILES Job Control Word (JCW). If the default value for MAXFILES (30,000) is unsuitable for your needs, you will have to set it to your selected value prior to running MPT. For example, to create a database large enough to hold 50,000 files you would enter the following command prior to running MPT: : SETJCW MAXFILES=50000 3. Create and Load the Database: During this step, it is recommended that all other users be off the system, as the system will be extremely busy, and disk files should not be accessed by other programs. You must have System Manager (SM) capability prior to running the MPT program. _________________________________________________________________ NOTE Schedule adequate time to run the MPT program. The MPT program may take anywhere from thirty minutes to eight hours to create and load the MPTDB database, depending upon the number and types of disk files on your system. _________________________________________________________________ Run the MPT.MPT.TELESUP program to create and load the MPTDB database used by MPT. Normally, MPT scans all disk files on the system including those on mounted and enabled private volumes. You can optionally limit the number of files scanned by MPT by using the INFO= parameter of the :RUN command to specify the MPE fileset you want scanned. The following example executes the MPT program, specifying that only files in the ACCTING account are to be scanned: : RUN MPT.MPT.TELESUP;INFO="@.@.ACCTING" The MPT program creates a database (MPTDB) to contain the results of the analysis. Information regarding each file scanned is logged in the MPTDB database. The information logged can vary depending on the type of file. It includes some classification to identify the type of the file. The disk capacity requirement for the file is projected for each of the following MPE/iX modes: CM, NM, and Translated Mode As each disk file is opened and scanned, program files, SL files, job stream files, and UDC files are examined more closely to see if they contain any migration events. If so, these events will also be logged in the database. 4. Load RTM Events: Run the MPTRTM program by entering: :RUN MPTRTM.MPT.TELESUP At the prompt LOG FILES ON TAPE OR DISC?, you must respond with DISC. At the prompt LOG FILES TO BE SCANNED?, respond with either of the following: ALL MPTRTM scans through all log files found on the system. m,n MPTRTM scans through the system log files numbered m to n. When RTM events are found recorded in the selected log files, they are entered into the MPTDB database. This concludes the data collection portion of MPT. You now use the MPTREPT program to generate migration planning reports.