|
  
SafeAccess Migration
This section summarizes the process of migrating CMS minidisks to SFS. The migration process is first described as it would typically be done without SafeAccess. This is followed by a summary of how SafeAccess greatly simplifies the migration process.
Summary of procedure used for typical minidisk to SFS migration
- Identify the minidisks to be migrated.
- Identify all applications that interact with each minidisk. This includes examining all applications and user's execs that might use each minidisk. This step is often the first point of failure for an SFS migration because it is just too large of a job, often on par with the evaluation necessary for the "Y2K" problem.
- Identify existing access control - who is allowed to link each minidisk and in what mode?
- Convert existing access control into SFS access control, which is CMS authorizations (or Grants, as they are often called). This step is another point where SFS migrations fail because SFS doesn't provide a hierarchy of access control rules or ACIGROUP support.
- Update applications that interact with each minidisk. At this point all of the applications from step 2 need to be changed to remove CP commands and functions, such as LINK, DETACH, and Diagnose 88 and to handle CMS changes such as ACCESS dirid instead of ACCESS vdev or to use QUERY ACCESSED instead of QUERY DISK. This is the final point at which SFS migrations tend to fail because of the huge effort required to make, test, and distribute these changes.
- Train users and developers on SFS and its changes.
- Migrate the data from minidisk to SFS.
- Coordinate all of these items.
SafeAccess simplifies the migration steps listed above in the following ways:
- SafeAccess gathers usage information that enables you to determine which minidisks are CMS formatted and which are good SFS migration candidates.
- SafeAccess dynamically converts Minidisk access methods into SFS methods. Applications do not need to be changed which means they do not need to be identified.
- SafeAccess, along with SafeSFS, converts various minidisk access controls into SafeSFS rules that simulate existing access control, including minidisk link passwords and ACIGROUPs.
- See 3 above.
- SafeAccess dynamically converts minidisk access methods, eliminating the need to update applications.
- SafeAccess dynamically converts minidisk access methods, so your users can still use LINK, ACCESS, QUERY DISK, and others just as they always have done.
- SafeAccess provides a migration facility that includes moving the data.
- SafeAccess dynamically addresses migration issues, eliminating the need for anything to coordinate. As soon as a minidisk is entered into the SafeAccess database, users start using the SFS version of the minidisk.
|
