Using GETUDC [ Migration Process Guide ] MPE/iX 5.0 Documentation
Migration Process Guide
Using GETUDC
Initiate GETUDC by running the program file GETUDC.PUB.SYS either
interactively or in batch mode. GETUDC progresses through the following
steps in order to accomplish its task:
1. Asks you for an MPE file name, then creates and opens an EDIT/V
compatible text file you can later use as an indirect STORE file.
2. After writing the name COMMAND.PUB.SYS to the indirect STORE file,
GETUDC reads system-recognized UDC file names from a temporary
copy of COMMAND.PUB.SYS and writes the names to the indirect STORE
file.
3. Asks you to append to the indirect STORE file additional file
names you plan to store to the STORE portion of the SYSDUMP tape.
Once these steps are accomplished, GETUDC saves the indirect STORE file,
then terminates.
Creating the Indirect STORE File
GETUDC prompts you for a file name which will hold the gathered UDC file
names:
Enter file name to hold UDC file names [enter ? for help]
>>
The possible responses to this prompt are:
* Any legal MPE file designator, followed by a Return. The default
group and account are the logon group and account. If the account
is specified, it must be that of the user's logon account. You
can specify the file designator with a leading asterisk (*) if you
want to backreference a file equation in order to override default
file characteristics.
* A question mark (?) displays pertinent HELP text, then returns
you to the prompt.
* A Return terminates GETUDC (a file is not created).
If you specify an illegal file name, or if a duplicate file name already
exists on the system, GETUDC displays an error message and prompts you
again for a file name.
Once a file name is selected, GETUDC creates an EDIT/V-compatible text
file you can later use as an indirect STORE file at the appropriate
SYSDUMP prompt.
Gathering UDC File Names
In order to minimize possible impact upon system users, GETUDC copies the
contents of COMMAND.PUB.SYS to a temporary file. GETUDC reads UDC file
names from this temporary file.
The file name COMMAND.PUB.SYS is copied to the first line of the indirect
STORE file. GETUDC then displays the following progress message:
0000 Number of UDC Files Collected in The System
The number in the progress message automatically increments to indicate
the number of UDC file names collected from the temporary copy of
COMMAND.PUB.SYS and placed (on a file name per line basis) in the
indirect STORE file.
To ensure system security, GETUDC does not write lockwords to the
indirect STORE file. (Lockwords will not be required for SYSDUMP to
successfully STORE the files.)
GETUDC displays the following message after it finishes writing UDC file
names:
All #nnnn UDC file names are stored in file filename
A lockword, if previously specified, is not displayed in the above
message.
Appending Other File Sets
You can append additional file names to the indirect STORE file. When
the indirect STORE file name is used as a response to the ENTER DUMP FILE
SUBSETS prompt of the SYSDUMP, these files will be stored in the STORE
portion on the SYSDUMP tape immediately following COMMAND.PUB.SYS and UDC
files.
NOTE The ENTER DUMP FILE SUBSETS prompt of SYSDUMP is not repeated after
the first time you specify the filesets (or indirect file name
containing the file sets) you want stored. It is recommended that
you place in the indirect STORE file the names of all the file sets
you want SYSDUMP to store.
GETUDC displays this prompt:
Enter any file sets you want to append [ enter ? for help ]
>>
The possible responses to this prompt are:
* Any STORE/RESTORE-compatible file set name. Please enter this
data correctly, as GETUDC does not check for incorrect names. You
are prompted repeatedly until you press Return without entering a
file set name.
* A question mark (?) displays pertinent HELP text, then returns
you to the prompt.
* A Returncauses GETUDC to save and close the indirect STORE file,
terminate.
NOTE When running in batch mode, a blank line in the job file (instead
of a file set name) is treated as a Return.
GETUDC Execution Example
Example F-1 illustrates a typical execution of the GETUDC utility. User
input is highlighted.
:RUN GETUDC.PUB.SYS
GETUDC G.03.01 COPYRIGHT HEWLETT-PACKARD CO. 1987.
Enter file name to hold UDC file names [ enter ? for help ]
>>TESTFILE/LOCK
0123 Number of UDC Files Collected in The System
All 123 UDC file names are stored in file TESTFILE.
Enter any file sets you want to append [ enter ? for help ]
>> @.PUB.SYS
>> @M
>> A@#ACCT@
>> @.@.FINANCE
>> Return
END OF PROGRAM
:
Example F-1. GETUDC Execution Example
MPE/iX 5.0 Documentation