Pathmaker Reference Manual

PMPROJECT Utility
Utilities
067869 Tandem Computers Incorporated 5–23
! Tells PMPROJECT to overwrite files at the new location with the
same name as the exported file. If you omit this option and there is a
name conflict, PMPROJECT cancels the operation with an error
message listing the first file of the exported project whose name
conflicts with a name at the new location.
Tandem recommends that you omit the exclamation point, as a check
for duplicate file names at the new location. Omitting the
exclamation point gives you a chance to save files if there are name
conflicts. Then you can repeat the export, using the exclamation
point option to overwrite the files if appropriate.
To move a project to another Tandem system first export it, then use IMPORT on
the target system to add the project to the Pathmaker system there. The systems
must be connected and you must have remote passwords for the target system. If
you do not have remote passwords you will get a security violation error. If you
cannot use remote passwords, move your project on tape, and then import the
project to the new system.
To move all your project files to one volume, first use the DOWN command to stop
the projects, and then export them.
EXPORT copies these files:
Project catalog files
Generated application configuration files
Requester files: skeleton files, listing files, Screen COBOL source-code files,
object files, and copy library files.
Service files: custom source file (formerly transaction copy library files),
skeleton files, generated source-code files, object files, and listing files.
Server files: skeleton files, source-code files, object files, and listing files.
EXPORT does not copy:
Target application database files.
Target application command files.
Copy libraries or macros that are not registered in the project catalog but are
referred to by a requester copy library or the custom source file.
If copy libraries or macros are not registered in the project catalog, they are not
directly linked to the Pathmaker software. Thus, if you refer to copy libraries from
within requester libraries and the custom source file, you must use this command
sequence to export a project:
PMPROJECT DOWN project-name
FUP DUP copy-library-file ,new-location
PMPROJECT EXPORT project-name TO new-location
Note that you can register copy libraries and macros in the project catalog using
the Macro Registration screen.