Pathmaker Reference Manual

PMPROJECT Utility
Utilities
067869 Tandem Computers Incorporated 5–29
When you are ready, choose (C) to continue. PMPROJECT adds the project, reporting
its progress as it goes:
Creating project catalog files in $PROJECT.SUBVOL ...
Creating Pathway configuration in $PROJECT.SUBVOL.T9154CFG..
Project TEST-PROJECT added
Cold starting project TEST-PROJECT ...
Project TEST-PROJECT started
Moving a Project to Another System
Assume that you want to move a project, TEST-PROJECT, to another Tandem system
and add the project to the new system's Pathmaker project list. Assume that the
custom source file (formerly called a transaction copy library) refers to a copy library
that is not a registered in the project catalog. To move this project to another system,
you must use the following series of commands:
PMPROJECT DOWN project-name <-- If the project
is running
PMPROJECT EXPORT project-name <-- To move the files
TO new-location
FUP DUP copy-library-file , <-- Because you used
new-location a copy library that
is not a registered
macro
PMPROJECT IMPORT project-name FROM <-- Because you
catalog-location moved the files
from another
system
In the following example, assume that you are moving a project from
\TEST.$PROJECT.SUBVOL to \REAL.$DATA. The project you would like to move is
named TEST-PROJECT and you would like to name it REAL-PROJECT at the new
location. The copy library to which you referred from within the custom source file is
named CPYLIB03.
The text in boldface shows the text that you would enter. The symbol ↵ means that
you type only a carriage return (RETURN or ENTER).
23> PMPROJECT DOWN test-project
Project TEST-PROJECT shut down
24> PMPROJECT EXPORT test-project TO \real.$data
Locating files referenced by catalog in $PROJECT.SUBVOL …
Project TEST-PROJECT exported
25> FUP DUP $project.subvol.cpylib03, \real.$data.subvol.*