PROCOPY uses absolute pathnames

When you use the PROCOPY utility, the target database you create always has an absolute pathname regardless of the pathname convention used by the source database.

For example, if you use PROCOPY to create a database, name it example1, and use a relative path database such as sports2020 as the source database, example1 will have an absolute pathname even though the source database, sports2020, uses a relative pathname. Use PROSTRCT LIST to verify the absolute pathname of your target database, as shown:

procopy sports2020 example1
prostrct list example1

In the following sample output of the PROSTRCT LIST utility, note the absolute pathname of the database, example1.db:

Area Name: Control Area, Type 6, BlockSize 4096, Extents 1, Records/Block32, 
Cluster Size 1
   Ext # 1, Type VARIABLE, Size 32 KByte, Name: /usr1/V10/example1.db

Area Name: Primary Recovery Area, Type 3, BlockSize 8192, Extents 1
   Ext # 1, Type VARIABLE, Size 2176, Name: /usr1/V10/example1.b1

Area Name: Schema Area, Type 6, BlockSize 4096, Extents 1, Records/Block 32, Cluster Size 1
   Ext # 1, Type VARIABLE, Size 960 KByte, Name: /usr1/V10/example1.d1

Area Name: Info, Type 6, BlockSize 4096, Extents 1, Records/Block 32, Cluster Size 1
   Ext #1, Type VARIABLE, Size 192 KByte, Name: /usr1/V10/example1_7.d1