HP 3000 Manuals HP 3000 Manuals
Using DIRMIG (Continued)
Migrating Private Volume Environments
DIRMIG displays the Private Volume Migration Menu shown in Example G-5
after one of the following actions has occurred:
* You selected option 3 from the Main Menu, and private volume
definitions were appended to the file PVASSIST.PUB.SYS when you
migrated one or more accounts to MPE/iX using DIRMIG's Directory
Migration Menu.
* You selected option 7 from the Main Menu, and the file
PVASSIST.PUB.SYS exists.
The data and environment found on MPE V/E private volume disk packs are
not directly transportable to an MPE/iX system. In order to
migrate/recreate an MPE V/E private volume environment on your MPE/iX
system, it is necessary that you initialize the MPE/iX volumes using
VOLUTIL, MPE/iX's volume management utility. The main purpose of
DIRMIG's Private Volume Migration Menu is to assist the private volume
migration process by generating command files for VOLUTIL. These files
contain the appropriate commands which, when supplied to VOLUTIL,
initialize MPE/iX volume media with MPE V/E directory information.
NOTE Read Overview of "Private Volume Migration" before using DIRMIG's
Private Volume Migration Menu to generate VOLUTIL command files.
For more information concerning VOLUTIL and volume management on
MPE/iX, refer to the Volume Management Reference Manual
(32650-90045).
Overview of Private Volume Migration.
The Private Volume Migration Menu serves the purpose of generating
command files you can use later with VOLUTIL, the MPE iX volume
management utility. These command files enable you to recreate an MPE
V/E private volume environment on your MPE/iX system. Private volume
migration is a two-step process:
1. Using DIRMIG's Private Volume Migration Menu to generate VOLUTIL
command files.
2. Using VOLUTIL to initialize MPE/iX volume media with MPE V/E
directory information. Refer to Using VOLUTIL to "Complete
Private Volume Migration" for details on this step of the private
volume migration process.
Using DIRMIG's Private Volume Migration Menu, you can create VOLUTIL
command files. These command files contain VOLUTIL commands that are
necessary to recreate the MPE V/E private volume environment on MPE/iX.
If desired, the command files can contain MPE/iX commands that will build
groups and accounts on the MPE/iX volumes. The command files are built
based on the MPE V/E volume set information archived in the MPE/iX file
PVASSIST.PUB.SYS. (PVASSIST is a binary file whose format is understood
only by DIRMIG.)
DIRMIG archives MPE V/E volume set information into PVASSIST.PUB.SYS from
every Dirmig-migrated account containing volume set information. As
additional accounts are migrated to MPE/iX, volume set information is
appended to PVASSIST.PUB.SYS. By providing a central location of MPE V/E
volume set information, you have the flexibility of migrating private
volume information to MPE/iX at your leisure.
You can restore the files associated with a private volume after you have
successfully recreated that private volume's directory structure on
MPE/iX.
Two Types of Command Files.
The Private Volume Migration Menu provides options to build two types of
command files. The first type of file is a general command file that
will migrate the entire MPE V/E private volume environment to MPE/iX. The
name of this file is PVSUMARY.PUB.SYS. Before it can be used by VOLUTIL,
however, you must customize it by providing specific logical device
numbers. The second type of command file is called the volume set
command file. Here, each command file will migrate one specific MPE V/E
volume set to MPE/iX. The following points contrast the two types of
files:
* For each appropriate VOLUTIL command in PVSUMARY.PUB.SYS, logical
device numbers are denoted by unique place holders; in volume set
command files, the logical device numbers are included with the
VOLUTIL commands.
* Volume set command files contain a subset of information from
PVSUMARY.PUB.SYS; specifically the commands to migrate one volume
set to MPE/iX.
* Volume set command files may be used with VOLUTIL as soon as they
are created, while PVSUMARY.PUB.SYS must be customized first.
Once created, either file type can be customized (edited) and/or used at
any time. Refer to Using VOLUTIL to "Complete Private Volume Migration"
for a description of customizing DIRMIG command files and using these
files with VOLUTIL to complete private volume migration.
NOTE Use volume set command files if the number of disk drives available
on your MPE/iX-based system is less than the number of private
volumes to be migrated. This facilitates incremental volume set
creation.
New MPE/iX Volume Management Feature.
A feature of MPE/iX volume management that sets it apart from its MPE V/E
counterpart is that only the master of a volume set need be mounted to
logically initialize several member volumes. Logically initializing
member volumes means that the member volume information is written to the
master volume, but the member volumes need not be mounted. When
additional disk drives are configured, member volumes may be physically
initialized with VOLUTIL.
For example, suppose an MPE/iX-based system has only two disk drives
configured for volumes and a particular volume set consists of one master
and more than one member. As long as the master volume remains mounted,
each member may be consecutively mounted, physically initialized, and
dismounted in the other disk drive. No consecutive mounting and
dismounting is necessary if the number of available disks/disk drives
equal the number of members plus the master. Understanding this concept
will facilitate both volume set command file generation and the
customization of PVSUMARY.PUB.SYS. Command file customization is detailed
in Using VOLUTIL to "Complete Private Volume Migration".
Selecting Your Menu Option.
From the Private Volume Migration Menu shown in Figure G-7 , you can
choose the Private Volume migration option you wish.
_________________________________________________________________________________
| |
| |
| PRIVATE VOLUME MIGRATION |
| ------------------------ |
| CHOOSE FROM PRIVATE VOLUME OPTIONS BELOW: |
| |
| 0 - EXIT/(No Volume Set Migration) |
| 1 - HELP |
| 2 - LIST VOLUME SETS |
| 3 - VISIT VOLUME SETS/ (Specified Accounts) |
| 4 - GENERATE PVSUMARY COMMAND FILE/ (Specified Accounts) |
| |
| ENTER PRIVATE VOLUME OPTION |
| >> |
| |
_________________________________________________________________________________
Figure G-7. Private Volume Migration Menu
DIRMIG prompts you to select one of the above options. Entering only
Return at the ENTER PRIVATE VOLUME OPTION prompt returns you to the same
prompt. The following headings explain the different options available
to you through the Private Volume Migration Menu.
Exit/No Volume Set Migration (Option 0).
If you select option 0 from the Private Volume Migration Menu, DIRMIG
does not generate VOLUTIL command files. DIRMIG's next action is
dependent upon which option you previously selected in the Main Menu:
* If you selected option 3 from the Main Menu and you successfully
migrated one or more accounts using DIRMIG's Directory Migration
Menu, DIRMIG takes you to the UDC Environment/User Files Migration
Menu (refer to "Migrating the UDC Environment and User Files").
* If you selected only option 7 from the Main Menu, DIRMIG
terminates.
HELP (Option 1).
If you select option 1 from the Private Volume Migration Menu, the HELP
facility is invoked. When you exit the HELP facility, you return to the
ENTER PRIVATE VOLUME OPTION prompt of the Private Volume Migration Menu.
List Volume Sets (Option 2).
If you select option 2 from the Private Volume Migration Menu, DIRMIG
displays all volume set information contained in PVASSIST.PUB.SYS. When
DIRMIG finishes listing this information, you return to the ENTER PRIVATE
VOLUME OPTION of the Private Volume Migration Menu.
If you are running DIRMIG interactively, DIRMIG enables you to redirect
output to an offline listing by prompting you with the following message:
OFFLINE LISTING (YES/[NO])?
>>
* If you enter Y or YES at the prompt, DIRMIG redirects output to
the device associated with the file LIST. The default device
specification for LIST is LP, but a file equation can be created
prior to running DIRMIG that redirects output to an alternate
device (refer to "Redirecting DIRMIG Output").
* If you enter N, NO or Return or if DIRMIG is running in batch
mode, output is directed to $STDLIST.
If you are running DIRMIG interactively, DIRMIG allows you to specify the
output format you want by prompting you with the following message:
LONG FORMAT (YES/[NO])?
>>
* If you enter Y or YES at the prompt, or if DIRMIG is run in batch
mode, DIRMIG generates an output listing similar in format to the
MPE V/E command :
LISTVS @.@.@,1
* If you enter N or NO, or Return, DIRMIG generates an output
listing similar in format to the MPE V/E command:
LISTVS @.@.@,0
Visit Volume Sets (Option 3).
If you select option 3 from the Private Volume Migration Menu, DIRMIG
allows you to generate a command file for each specific MPE V/E volume
set you want migrated to MPE/iX. Before generating command files, DIRMIG
allows you to specify the accounts associated with the volume sets you
want migrated. DIRMIG issues the prompt:
ENTER ACCOUNT SUBSETS
>>
At this prompt, you can enter subsets, if the form of "accountsets", of
the MPE V/E structures at the account level followed by Return (you
cannot. specify group and user subsets). If you enter only Return at
this prompt (without specifying any accountsets) DIRMIG returns you to
the ENTER PRIVATE VOLUME OPTION prompt of the Private Volume Migration
Menu.
Accountsets are defined to be one or more MPE V/E account names, where:
* MPE wild cards are allowed; for example, M@ specifies all accounts
beginning with the letter "M".
* Minus subsets are allowed for example, A@-ACCT@ specifies all
accounts beginning with the letter "A" except for those accounts
beginning with the four-letter string "ACCT".
* Accountsets must be separated by commas.
* You can enter as many accountsets as desired up to a maximum of
280 characters.
You are repeatedly prompted for accountsets until you enter only Return
at the ENTER ACCOUNT SUBSETS prompt.
Once DIRMIG completes account selection, DIRMIG scans PVASSIST.PUB.SYS
and locates all volume set definitions associated with the accounts you
specified. For each volume set encountered, DIRMIG then displays the
Volume Set Options Menu shown in Example G-6. DIRMIG will display this
menu for each volume set definition located.
Selecting a Volume Set Migration Option.
If you selected option 3 from the Private Volume Migration Menu and
specified account name(s) for volume set migration, DIRMIG will find all
volume sets within the account(s) entered. DIRMIG displays the Volume
Set Options Menu (shown in Figure G-8 ) for each volume set
encountered, allowing you to generate a VOLUTIL command file for each MPE
V/E volume set you want migrated to an MPE/iX system.
______________________________________________________
| |
| |
| CHOOSE VOLUME SET OPTION BELOW: |
| |
| 0 - EXIT (No Volume Set Migration) |
| 1 - HELP |
| 2 - LIST VOLUME SET DEFINITION |
| 3 - GENERATE A COMMAND FILE |
| 4 - DELETE VOLUME SET DEFINITION |
| 5 - NEXT VOLUME SET DEFINITION |
| |
| ENTER VOLUME SET OPTION |
| >> |
| |
______________________________________________________
Figure G-8. Volume Set Migration Menu
DIRMIG prompts you to select one of the above options. Entering only
Return at the ENTER VOLUME SET OPTION prompt returns you to the same
prompt. The following headings explain the different options available
to you through the Volume Set Options Menu.
Exit/No Volume Set Migration (Option 0).
If you select option 0 from the Volume Set Options Menu, DIRMIG does not
generate a VOLUTIL command file for the selected volume set definition.
Instead, DIRMIG returns you to the ENTER PRIVATE VOLUME OPTION prompt of
the Private Volume Migration Menu.
HELP (Option 1).
If you select option 1 from the Volume Set Options Menu, the HELP
facility is invoked. When you exit the HELP facility, you return to the
ENTER VOLUME SET OPTION prompt of the Volume Set Options Menu.
List Volume Set Definition (Option 2).
If you select option 2 from the Volume Set Options Menu, DIRMIG displays
to $STDLIST information about the currently selected volume set
definition, including:
* The volume set name.
* The names of volume set's member volumes.
* The names of the volume set's member volume classes.
NOTE Volume member type information is displayed for consistency with
the MPE V/E :NEWVSET syntax. This information is not required for
creating volume sets in MPE/iX.
Generate a Command File (Option 3).
If you select option 3 from the Volume Set Options Menu, DIRMIG prompts
you for a a command file name, where you can enter any legal MPE file
designator (optionally qualified by group and account):
ENTER COMMAND FILE NAME
>>
DIRMIG creates a command file for the currently selected volume set
definition.
DIRMIG prompts for logical device numbers in order to customize the
command file for VOLUTIL use:
ENTER LDEV NUMBER FOR INITIALIZING MASTER volume name
>>
ENTER LDEV NUMBER FOR INITIALIZING MEMBER volume name>
>>
ENTER LDEV NUMBER FOR INITIALIZING MEMBER volume name
>>
The following rules apply for these prompts:
* The logical device number of zero for the master volume is not
allowed. A command file will not be built if a zero is input for
the master volume logical device number.
* A logical device number of zero or Return for member volumes.
DIRMIG generates commands which will result in the logical
initialization of those volumes when the command file is used with
VOLUTIL.
* A logical device number of 1...255 for member volumes when the
command file is used with VOLUTIL.
* A logical device number may be repeated for member volumes. (The
logical device number assigned to the master volume may not be
repeated.)
After prompting for logical device information, DIRMIG prompts for
spanning information of all home group.accounts matching the current
volume set name. For each group and account found DIRMIG issues the
prompt:
SPAN group.acct TO VOLUME SET volume set name
(YES/[NO])?
>>
Affirmative responses place MPE/iX commands in the command file to create
groups and accounts on the volume set. The spanning commands are added
to the command file.
NOTE MPE/iX does not support spanning of volume classes. DIRMIG will
not prompt for spanning information of home volume classes found
within the current volume set name. All groups and accounts found
in PVASSIST.PUB.SYS with home volume class information will be
logged.
Delete Volume Set Definition (Option 4).
If you select option 4 from the Volume Set Options Menu, DIRMIG deletes
from PVASSIST.PUB.SYS the currently selected volume set definition.
Specify this option when you do not want to migrate the current volume
set definition.
Next Volume Set Definition (Option 5).
If you select option 5 from the Volume Set Options Menu, DIRMIG displays
the next volume set in the pool of available migratable volume sets (as
bounded by the accounts you selected). DIRMIG displays the Volume Set
Options Menu for the newly selected volume set definition. A command
file may now be created for the currently selected volume set.
DIRMIG displays a Volume Set Options Menu for each volume set definition
located, allowing you to choose your own migration option for each volume
set definition. When no more volume set definitions are found in
PVASSIST.PUB.SYS, DIRMIG returns you to the ENTER PRIVATE VOLUME OPTION
prompt of the Private Volume Migration Menu.
Generate PVSUMARY Command File (Option 4).
If you select option 4 from the Private Volume Migration Menu, DIRMIG
generates the command file PVSUMARY.PUB.SYS for MPE V/E private volume
environments associated with selected accounts (you may specify volume
sets at the account level only). DIRMIG issues the prompt:
ENTER ACCOUNT SUBSETS
>>
At this prompt, you can enter subsets, in the form of "accountsets", of
the MPE V/E structures at the account level followed by Return (you
cannot specify group and user subsets). If you enter only Return at this
prompt (without specifying any accountsets) DIRMIG returns you to the
Enter Private Volume Option of the Private Volume Migration Menu.
Accountsets are defined to be one or more MPE V/E account names, where:
* MPE wild cards are allowed; for example, M@ specifies all accounts
beginning with the letter "M".
* Minus subsets are allowed for example, A@-ACCT@ specifies all
accounts beginning with the letter "A" except those accounts
beginning with the four-letter string "ACCT".
* Accountsets must be separated by commas.
* You can enter as many accountsets as desired up to a maximum of
280 characters.
You are repeatedly prompted for accountsets until you enter only Return
at the ENTER ACCOUNT SUBSETS prompt.
Once DIRMIG completes account selection, DIRMIG proceeds to generate
PVSUMARY.PUB.SYS. If PVSUMARY.PUB.SYS already exists, you are prompted
for a new command file name. DIRMIG displays the following progress
messages:
PVSUMARY FILE CREATION IN PROGRESS...
PVSUMARY FILE COMPLETED.
NOTE The VOLUTIL command file PVSUMARY.PUB.SYS contains all the commands
necessary to recreate the private volume environments for the
volume sets associated with the specified accounts. However, this
file must be customized in order to make it usable by VOLUTIL.
Refer to "Using VOLUTIL to Complete Private Volume Migration" for
details on customizing PVSUMARY.PUB.SYS and using it with VOLUTIL.
DIRMIG's next action is dependent upon which option you previously
selected in the Main Menu:
* If you selected option 3 from the Main Menu and you have
successfully migrated one or more accounts using DIRMIG's
Directory Migration Menu, DIRMIG takes you to the UDC
Environment/User Files Migration Menu.
* If you selected only option 7 from the Main Menu, DIRMIG
terminates.
Migrating the UDC Environment and User Files
DIRMIG displays the UDC Environment/User Files Migration menu shown in
Example G-7 only after one of the following actions has occurred:
* You selected option 3 from the Main Menu and you have successfully
migrated one or more accounts from the Directory Migration Menu.
* You selected option 6 from the Main Menu and you have successfully
migrated one or more accounts from the Directory Migration Menu.
Selecting Your Menu Option.
From the UDC Environment/User Files Migration Menu (shown in Figure G-9
(*)), you can choose the UDC and user files migration option you wish.
________________________________________________________________________
| |
| |
| UDC ENVIRONMENT/USER-FILES MIGRATION |
| ------------------------------------ |
| CHOOSE FROM UDC/RESTORE OPTIONS BELOW; |
| |
| 0 - EXIT/No UDC Environment/User-Files Migration) |
| 1 - HELP |
| 2 - MIGRATE UDC ENVIRONMENT ONLY |
| 3 - MIGRATE UDC ENVIRONMENT/RESTORE USER FILE SUBSETS |
| 4 - MIGRATE UDC ENVIRONMENT/RESTORE ALL FILES |
| |
| ENTER UDC/RESTORE OPTION |
| >> |
| |
________________________________________________________________________
Figure G-9. Environment Migration Menu
DIRMIG prompts you to select one of the above options. If you enter only
Return at the ENTER UDC/RESTORE OPTION prompt, DIRMIG returns you to the
same prompt. The following headings explain the different options
available to you through the UDC Environment/User Files Migration Menu.
NOTE Options 2,3, and 4 of the UDC Environment/User Files Migration Menu
follow the same sequence of five steps to accomplish UDC
environment migration. The only difference between these three
options lies in the choices DIRMIG gives you concerning restoration
of user files associated with the accounts you migrated from the
MPE V/E SYSDUMP tape (using DIRMIG's Directory Migration Menu).
For this reason, options 2, 3, and 4 are discussed together under
the common heading "Migrate UDC Environment/Restore User Files".
Exit/No UDC Environment/User Files Migration (Option 0).
If you select option 0 from the UDC Environment/User Files Migration
Menu, DIRMIG does not migrate UDC environments and user files. DIRMIG
terminates.
HELP (Option 1).
If you select option 1 from the UDC Environment/User Files Migration
Menu, the HELP facility is invoked. When you exit the HELP facility, you
return to the ENTER UDC/RESTORE OPTION prompt of the UDC Environment/User
Files Migration Menu.
Migrate UDC Environment/Restore User Files (Options 2, 3, 4).
If you select option 2, 3, or 4 from the UDC Environment/User Files
Migration Menu, DIRMIG proceeds to migrate the UDC environments
associated with the account structures you successfully migrated during
directory migration (refer to "Migrating the Directory Structure").
NOTE DIRMIG invokes the RESTORE facility twice during UDC migration. If
you used the MPE V/E GETUDC utility to place UDC environment files
at the beginning of the RESTORE portion of the SYSDUMP tape, DIRMIG
takes substantially less time to restore UDC environment files.
(Refer to Appendix F, "Using the GETUDC Utility."
In addition to migrating the UDC environment, DIRMIG gives you the
opportunity to:
* Restore selected file subsets (if you select option 3).
* Restore all file subsets (if you select option 4).
If you are running DIRMIG interactively, DIRMIG allows you to
redirect output to an offline listing by prompting you with:
OFFLINE LISTING FOR FILES TO BE RESTORED (YES/[NO])?
>>
* If you enter Y or YES at the prompt, DIRMIG redirects output to
the device associated with the file LIST. The default device
specification for LIST is LP, but a file equation can be created
prior to running DIRMIG that redirects output to an alternate
device (refer to "Redirecting DIRMIG Output").
* If you enter N, NO, or Return, or if DIRMIG is running in batch
mode, output is directed to $STDLIST.
UDC migration is divided into five steps, described below.
1. Obtain MPE/iX UDC environment information. If COMMAND.PUB.SYS
exists on the MPE/iX system, DIRMIG performs these actions on
COMMAND.PUB.SYS to obtain MPE/iX UDC information and to preserve
the current MPE/iX UDC environment:
* Copies UDC information from COMMAND.PUB.SYS to a temporary
data structure.
* Renames COMMAND.PUB.SYS to SAVECMD.PUB.SYS. DIRMIG later
modifies SAVECMD.PUB.SYS when migrating the MPE V/E UDC
environment to MPE/iX.
* Copies the contents of COMMAND.PUB.SYS to the file
COPYCMD.PUB.SYS. DIRMIG can return the original version of
COMMAND.PUB.SYS if an error occurs during UDC environment
migration.
If the MPE/iX COMMAND.PUB.SYS has an EOF equal to zero, the file
is purged and DIRMIG continues with the assumption that there is
no UDC environment on the MPE/iX system.
2. Obtain MPE V/E UDC environment from the SYSDUMP tape. DIRMIG
prompts you to mount the SYSDUMP tape in order to restore the MPE
V/E file COMMAND.PUB.SYS:
MOUNT MPE SYSDUMP TAPE AND PLACE TAPE DRIVE ON-LINE
After the SYSDUMP tape is mounted on the tape device and placed
online, DIRMIG displays the following progress messages to
indicate success of file restoration:
RESTORING COMMAND.PUB.SYS
RESTORE OF COMMAND.PUB.SYS SUCCESSFUL
After the MPE V/E system file COMMAND.PUB.SYS is successfully
restored on the MPE/iX system, DIRMIG collects the names of the
UDC files for those accounts and users successfully migrated.
These are the UDC files that are restored during Step 3 (see
below). Once these names are collected, DIRMIG purges the
COMMAND.PUB.SYS file restored from the SYSDUMP tape and
renames the MPE/iX file SAVECMD.PUB.SYS (see Step 1) back to
COMMAND.PUB.SYS.
3. Restore UDC files/user files from the SYSDUMP tape. Step 3 varies
depending upon whether you selected option 2, option 3, or option
4 from the UDC Environment/User Files Migration Menu. In all
three cases, DIRMIG restores those UDC files whose names were
collected in Step 2. DIRMIG restores files by invoking the
:RESTORE facility with the KEEP and OLDDATE options enabled.
(Refer to the :RESTORE command in the MPE/iX Commands Reference
Manual (32650-90003) for details.)
_________________________________________________________________
NOTE DIRMIG assumes disk file space limits for group and account
entries will be sufficient. DIRMIG lists files that are not
restored because of insufficient disk space.
_________________________________________________________________
* Migrate UDC Environment Only (Option 2). DIRMIG proceeds
to restore from the MPE V/E SYSDUMP tape the UDC files
whose names were collected in Step 2. DIRMIG does not
restore user files from the SYSDUMP tape. DIRMIG prompts
you to mount the SYSDUMP tape:
MOUNT MPE SYSDUMP TAPE AND PLACE TAPE DRIVE ON-LINE
After the SYSDUMP tape is mounted and placed online, DIRMIG
displays the following messages to indicate progress and
success of UDC file restoration:
RESTORING UDC FILES
RESTORE OF UDC FILES SUCCESSFUL
* Migrate UDC Environment/Restore User File Subsets (Option
3). DIRMIG displays the following prompt:
ENTER FILE SUBSETS
>>
At this prompt you can enter file subsets you want to
migrate. File subsets are defined to be one or more MPE
V/E file names (valid to the MPE/iX :RESTORE command),
where file subsets are separated by commas, and MPE wild
cards are allowed; for example, M@#.@.@ specifies all files
beginning with the letter "M" and ending with a numeric
character.
You are repeatedly prompted for filesets until you enter
only Return at the ENTER FILE SUBSETS prompt. DIRMIG
prompts you to mount the SYSDUMP tape:
MOUNT MPE SYSDUMP TAPE AND PLACE TAPE DRIVE ON-LINE
After the SYSDUMP tape is mounted and placed online, DIRMIG
displays the following messages to indicate progress and
success of UDC file restoration:
RESTORING UDC FILES/USER-DESIGNATED FILES
RESTORE OF UDC FILES/USER-DESIGNATED FILES SUCCESSFUL
* Migrate UDC Environment/Restore all Files (Option 4).
DIRMIG proceeds to restore from the MPE V/E SYSDUMP tape
the UDC files whose names were collected in Step 2, as well
as all user files associated with the accounts migrated
during directory migration (except those files in PUB.SYS).
DIRMIG prompts you to mount the SYSDUMP tape:
MOUNT MPE SYSDUMP TAPE AND PLACE TAPE DRIVE ON-LINE
After the SYSDUMP tape is mounted and placed online, DIRMIG
displays the following messages to indicate progress and
success of UDC file restoration:
RESTORING UDC FILES/ALL USER-FILES
RESTORE OF UDC FILES/ALL USER-FILES SUCCESSFUL
4. Modify the MPE/iX UDC Environment. DIRMIG modifies the MPE XL
COMMAND.PUB.SYS file to include UDC environment information
migrated from the MPE V/E system.
_________________________________________________________________
NOTE If an MPE/iX user also exists on the MPE V/E SYSDUMP tape,
that user's MPE/iX UDC environment is replaced by the MPE
V/E UDC environment found on the MPE V/E SYSDUMP tape.
_________________________________________________________________
5. Update the MPE/iX Directory. User and account entries within the
MPE/ iX directory are updated to reflect the information found in
the new MPE/iX system file COMMAND.PUB.SYS. This action enables
the MPE/iX UDC environment without the need to use the :SETCATALOG
command.
Once DIRMIG has completed updating the MPE/iX directory, DIRMIG
terminates.
Exiting DIRMIG
Each menu in DIRMIG has an optional selection that allows you to exit
DIRMIG normally.
CAUTION You should not interrupt or abnormally terminate DIRMIG once it
is started, since it is running in Privilege Mode updating
MPE/iX system tables and allocating directory space. Use exit
options provided to exit DIRMIG safely.
Redirecting DIRMIG Output
When you select the offline option available through several DIRMIG
menus, you direct the text output to the DIRMIG list file LIST. By
default this file is assigned to the system line printer (DEV=LP). If you
want to redirect the output to a different device, you must, prior
to running DIRMIG, create an MPE file equation to redefine the
characteristics for LIST. This file equation is invoked only when you
respond Y or YES to an OFFLINE LISTING (YES)/[NO]) prompt. For example,
the file equation below redirects output to device name EPOC:
:FILE OTHER;DEV=EPOC
:FILE LIST=*OTHER
NOTE When DIRMIG is run in batch mode, the output always defaults to
:$STDLIST; the detailed format is to be used where applicable.
Examining DIRMIG Log Files
DIRLOGnn.PUB.SYS, DIRMIG's log file, is created to track the progress of
each component's migration. You should always examine DIRLOGnn after
running DIRMIG. This file provides information for debugging and
troubleshooting if a problem occurs. The files are numbered (maximum
number 99) so you can maintain a log file history of every run of DIRMIG.
DIRMIG searches only for the maximum sequence numbered DIRLOG file before
creating a new log file. For example, if DIRMIG finds that the log file
DIRLOG01.PUB.SYS already exists, DIRMIG creates DIRLOG02.PUB.SYS.
If DIRLOG99.PUB.SYS already exists, DIRMIG disables the logging facility
and asks you if you want to continue execution with logging disabled:
* If your enter Y or YES to the prompt, DIRMIG continues execution
with logging disabled.
* If you enter N, NO, to the prompt, DIRMIG terminates. You can
purge or rename DIRMIG log files (highest to lowest), then rerun
DIRMIG.
DIRLOGnn contains:
* Progress messages displayed to $STDLIST.
* Progress messages for directory migration.
* Error messages indicating a component has not been migrated.
Verifying Directory Migration
To verify that the correct data has been migrated check the system
components, listed in the first column, by using the commands listed in
the second column.
To check: Use:
RINs :SYSGEN (MISC Configurator)
User-Logging IDs :LISTLOG
Directory :REPORT :LISTACCT :LISTGROUP :LISTUSER
Mountable Volumes :DSTAT :VOLUTIL
UDCs :SHOWCATALOG
Files :LISTFILE or :LISTF