When you use the PRODB utility, the target database you create maintains the same pathname convention, relative or absolute, as the source database. For example, if you use PRODB to create a database and name it example1, and use a relative path database such as sports2020 as the source database, PRODB maintains the pathname convention of sports2020 (the source database), and example1 (the target database) becomes a relative path database. Conversely, if the source database is an absolute path database, the target database you create with PRODB will also be an absolute path database. Use PROSTRCT LIST to verify whether the pathname is relative or absolute. For example:

prodb example1 sports2020 
prostrct list example1

In the following sample output of the PROSTRCT LIST utility, note dot (.) notation of the relative 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: ./example1.db

Area Name: Primary Recovery Area, Type 3, BlockSize 8192, Extents 1
   Ext # 1, Type VARIABLE, Size 2176, Name: ./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: ./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: ./example1_7.d1