|
HP OpenVMS Systemsask the wizard |
|
The Question is: Current System: Digital microVAX 3900 running on VMS 5.5. Only one system disk; all users' data resides on the system disk. New System: Digital VAX 4000-108 running on OpenVMS 5.5-2. Has one system disk and two other hard disks. I am encountering problems with the migration from the current system to the new system of which the requirement is to place the users' data on a separate hard disk and not in the system disk as in the old system. I have performed an image backup of the current system and restored to the first hard disk (dka100:) of the new system. The problem is, the old system disk, as in every VMS system disk, have a [sys0.syscommon] directory. Once we restored to dka100:, all t he users' applications are unable to compile and run properly as in the old system, the [sys0.syscommon] directory is "hidden" (since VMS uses logical pointer) but in dka100: in the new system, it is "visible". Is there any solution pertaining to our situation? The Answer is : Please contact the customer support center, as there is not enough information here to determine what you specifically mean by "hidden" and "visible". [There have been few changes of any major significance made to the system disk directory structure since V3.0.] If the applications contain explicit references to the system directories on the old system disk -- references that are incompatible with the contents of the new system disk -- then you will need to decide to update the applications, or to decide to update the contents of the new system disk, or to use some other (potential) solution specific to the particular problems beeing seen by the application programmers. When contacting the customer support center, expect to be asked for specific information on the compilation and run-time errors. Also expect to be asked for the specific BACKUP/IMAGE command used to create the BACKUP, and the BACKUP/IMAGE command used to restore it.
|