Next Previous Contents

3. An overview of the migration project

Here is a brief list of the steps needed to carry out the migration from MVS to Unix. Do not be deceived by the apparent order and logic of the steps in the list. Unexpected stumbling blocks were found at each step that delayed the completion of the step or required a change of tactics. If you are carrying out a migration yourself, expect the unexpected.

  1. write a bare-bones JCL to Perl translator (expect to be only running SAS programs)
  2. prepare some JCL scripts (by removing special formatting)
  3. transfer (FTP) some test scripts from MVS to Unix
  4. debug the text file preparation and transfer process
  5. translate some test scripts
  6. debug the translator until the test scripts run
  7. debug test scripts to remove system incompatibilities
  8. prepare enough support files (CPORTing of SAS datasets) to get the test scripts producing correct results
  9. transfer support files from MVS to Unix with ftp
  10. CIMPORT the support files into development directories
  11. run the scripts with the support files
  12. debug the support file preparation and transfer process
  13. translate (by hand) the STAT menu system to a Unix shell script
  14. debug the translated menu system until it runs
  15. prepare to erase or change TSO calls in SAS programs
  16. prepare all JCL scripts for transfer (get them out of cartridge storage and remove formatting)
  17. prepare all support files (CPORT the SAS datasets) for transfer
  18. PKZIP all of the STAT directories
  19. transfer PKZIPped files to Unix with FTP
  20. unzip(1) files into the /data/stat/test directory
  21. (OPTIONAL) create symbolic links in / to emulate MVS prefix structure
  22. CIMPORT the SAS datasets
  23. translate accented characters in NOTES file (and any other files) via SAS export, tr(1), and then SAS import (if this is not acceptable CPORT will have to be fixed by SAS Institute or TRANSLATE option of CPORT must be used)
  24. run JCL to Perl translator on all scripts
  25. erase or change TSO calls in SAS programs
  26. test and debug currently-used scripts (leave the others for STAT to check and debug at a future date)
  27. finish debugging the STAT menu system
  28. resolve printing solutions (maybe a big job, probably not)
  29. test and debug the ensemble with V and an "ordinary" STAT user
  30. arrange daily backups with system administrator
  31. copy everything to /data/stat/prod and check
  32. stop all data entry on MVS
  33. prepare all of the latest support files (CPORT the SAS datasets) for transfer
  34. PKZIP all of the latest STAT directories
  35. transfer latest PKZIPped files to Unix with FTP
  36. unzip latest files into the /data/stat/test directory
  37. CIMPORT the latest SAS datasets
  38. translate accented characters in latest NOTES file
  39. test to make sure everything is still working correctly (use a checklist of previous bugs as a regression test)
  40. copy everything to /data/stat/prod and check
  41. create accounts for data entry personnel
  42. do a demonstration for the data entry personnel and give each of them a copy of this report
  43. data entry starts again on the Unix system
  44. *** END OF MIGRATION ***
  45. Next project: replace DCF report generation with LaTeX

Next Previous Contents