1 1 - Procedure for Converting Distribution 2 Disk Packs to Distribution 3.0 Format - This procedure will produce new disk packs containing all files from the old packs that do not need to be changed for the new file routines. Those files that need to change (e.g., *CATALOG) will be replaced with new versions. It is estimated that the conversion will take at least 2 hours per disk pack, and it will not be possible to run MTS for any other purpose while it is in progress from step 3 on. You should read this entire description and be familiar with it before you attempt to start the conversion process. Otherwise you may make mistakes that will be hard to undo. 0 1. Restore the disk pack included with the distribution onto an extra 2314 pack. This pack should not be one of the regular MTS disk packs so that it can be used for setting up the new system without affecting the operation of the old system. Use the TSS DASDI and DUMPRESTORE provided. 0 2. Use the pack restored above to get the new version of MTS working to your satisfaction. This will require changing TABLES slightly to conform to Distribution 3 format (see writeup on TABLES), and adding any local modifications to the resident system. The TABLES Deck Generator Program can be used to produce a new TABLES. The pack restored in step 1 contains enough files to run MTS more or less normally, but does not contain many non-essential programs. If additional programs are needed move them from the old packs by copying them to tape or cards. Do not attempt to use the the new MTS with the old packs. 0 3. Use component 104/51, or a modification of it if you have changed the accounting file format, to generate Distribution 3 accounting files in private files. Comments in the source describe what this program does and how to run it. Run it with the old ACCLIST and other + ___ accounting subroutines. 0 4. Save all old disk packs with stand-alone DUMP/RESTORE. These tapes will probably not be used, but it would be foolish to proceed with the conversion without some back- up. If enough disk packs are available so that the old ones do not need to be reused until the conversion is complete, it will not be necessary to save them on tape. Simply be sure that some back-up exists, either on tape or disk. From this point until the conversion is complete it will not be possible to run regular MTS, so be sure enough time is available to complete the conversion. 0 5. If the MTS001 pack restored in step 1 has been changed in the process of getting the new MTS working it would be a good idea to restore it again, unless you are positive that none of the files you have added or changed is 1 2 - important to the conversion. 0 6. Save all files on the old disk packs on tape using FILESAVE running in the old system. Do not try to run FILESAVE in the new system. It won't work. The tapes created in this step will be used as input to the conversion process. 0 7. If the contents of *STATISTICS is needed for billing or any other purpose, run *STA to save it on tape (or use whatever program you normally use for this). The contents of *STATISTICS will be lost during conversion. 0 8. DASDI the packs that will be used for MTS002 and up, using the TSS DASDI on the restore tape. They should be VAM2 public volumes with public volume numbers of 2 for MTS002, 3 for MTS003, etc. This step may of course be done earlier unless the same packs are to be used that were saved in step 6. It is not necessary to DASDI an MTS001, since the pack restored from tape will be used for this. 0 9. IPL the new MTS using MTS001 from the restore tape and clean packs for the rest of public storage. 0 10. Signon from the operator's console as userid RSTR. You must use this userid since files belonging to whatever userid you use may not be permitted correctly after the conversion. 0 11. Run the program in RST . This is the new version of the standard restore program. It will be used to restore all files from the old disk packs that have not changed due to the new file routines. 0 12. When it asks for the files to be restored enter the line 0 $CONTINUE WITH EXC RETURN 0 When it comes back to read the operator's console after this, enter cancel (alt code 0). This will enter a list of files not to be restored because they have changed. A listing of EXC is attached to the Restore Tape File List (documentation item 1012). Some of the files in EXC are included mainly because they are important to running MTS, not because they contain changed programs. Some of them will be restored later after the other files have been successfully restored. Some files on the restore pack are not included in the except list. They were added for convenience during installation of the distribution. They are: files for *ASMG, *OBJSCAN, *UPDATE, *FORMAT, *TAPECOPY, *TAPEDUMP, *TASKS, *DOWNDATE, *UNEDIT, *AMENDS. The tapes produced in step 6 should be used as input for this restore. The new restore program is capable of reading the old format restore tapes. 0 13. For each of the files listed below give the following 1 3 - commands: 0 $PERMIT myfile LIKE *file $DESTROY *file $RENAME myfile *file 0 where "*file" is the public file and "myfile" is the private copy of it created in step 3. The files are: 0 *PROJECT *PRJDIRECTORY *ACCOUNTING *ACCOUNTING1 *ACCOUNTING2 *ACCOUNTING3 *ACCOUNTING4 *ACCOUNTING5 0 If you have to reload while doing this, don't let INIT run. 0 14. Signon at the operator's console under userid MTS and enter: 0 $RUN FILEUPD 0 This will update file storage records for all userids. It is important that this be done, since many userids will be incorrect. 0 15. Add any local modules to *LIBRARY. Do not simply replace the new one with your old one, but rather merge the two. 0 16. Add any local messages to *SMDS. Again, do not just replace the new one with your old one, as there are several new messages in it. If there are conflicts between our new messages and your added messages, the Message Manual can be used to find out where each FMSG is issued in the Distribution 3.0 MTS. 0 17. Because of the change in disk formats, files with note/point information must be regenerated. Libraries created by *GENLIB with DIR or POINT options are the most common in public files. The affected libraries at our installation are given in the following list. Any you have installed in this form, plus other libraries in similar state, must be cranked through *GENLIB again. GENLIB will read the old version, ignoring the note/point information, so just run *GENLIB using the old version as input and a private file as output, destroy the old version, and then rename the private file as the appropriate public file. Our libraries were: 0 *CSMPLIB *GASP *SIM2LIB 1 4 - *KDFLIB *APLLIB *PL1LIB *NEWPL1LIB *PLI *PLOTSYS *COBLIB 0 The file *PL1DIRECTOR may require special handling. See distributed PL1 installation notes (506/15). 0 18. Change the Segment 2 Loader driver file (SEG2:S2FILES) as required. The Segment 2 Loader on the restore pack will load what it does at UM, except that the Data Concentrator DSR, Audio Response Unit DSR, Merit DSR, and TSS Assembler have been removed. (To cut the size down)