DB2 Test Database Generator output files
The output files that DB2 Test Database Generator
creates are listed by platform. There are slight differences in
the files created depending on the platform on which you are working.
z/OS
The
following files are created and used by DB2 Test Database Generator
when running on z/OS:
- userpath/data profile
name/log
- The DB2 Test Database Generator log file.
- userpath/data profile name/run
- A temp file that exists only while the DB2 Test Database Generator
server is running.
- userpath/data profile name/dataprofilename.griml
- The DB2 Test Database Generator Data Profile.
- userpath/data profile name/targetname.ddl
- If you elected to create matching DDL for the targets, each
target has its DDL in this file. This file type can be present only
after test data generation.
- userpath/data profile name/targetname.gen.ddl
- A file that shows the DDL created by Test Database Generator.
This file is used to determine which DDL has been successfully run
at the database. All DDL that has been successfully run will be
commented out in the file. Any DDL that was not successfully run
will not be commented out in the file. This file type can be present
only after test data generation.
- userpath/data profile name/targetname.sql
- The SQL output if the target is a table. This file type can
be present only after test data generation.
- userpath/data profile name/targetname.gen.sql
- A file that shows the SQL that is created by Test Database Generator.
This file is used to determine which SQL has been successfully run
at the database. All SQL that has been successfully run will be commented
out in the file. Any SQL that was not successfully run will not
be commented out in this file. This file type can be present only
after test data generation.
- userpath/data profile name/targetname.xml
- The XML if you decided to create an XML target. This file type
can be present only after test data generation.
- userpath/data profile name/targetname.csv
- The delimited text output. This file is present only when a
delimited text target is created. This file type can be present
only after test data generation.
- userpath/data profile name/generate.sh
- This is a shell script that is used by DB2 Test Database Generator
to generate test data.
- userpath/data profile name/generate.bat
- This is a batch file that is used by DB2 Test Database Generator
to generate test data. This file is used only when the DB2 Test
Database Generator server is installed on Windows platforms.
- userpath/data profile name/stderr.txt
- This file contains any error output created when generating
test data.
- userpath/data profile name/stdout.txt
- This file contains all output created when generating test data.
Where:
- userpath is the path where the DB2 Test Database Generator
data profiles are stored. The default userpath is: /proj/griv2r2
- user is the User ID used to login to DB2 Test Database
Generator.
- data profile name is the name of the Data Profile being
used.
- targetname is the name of the target that you are creating.
DB2
Test Database Generator can generate the following files when the
DB2 Load Format option is selected. These files are stored in MVS.
This is applicable only for z/OS databases:
- GRIDDL
- This file contains the DDL statements that UNLOAD the data.
- GRIPUNCH
- This file contains load control cards to be used when executing
LOAD utility.
- GRIPARM
- This file contains statements that define the parameters you
specified during the export process.
- GRInnnnn
- These files contain the data that is unloaded from the tables.
Attention:
The GRInnnnn files that
hold the data from the tables can require a great deal of space, depending
on your export options. DB2 Test Database Generator initially calculates
the maximum required space by length of record X row count for each
table. When finished, Test Database Generator releases any unused
space.
- LOAD file
- This JCL is stored in the PDS member that you specify on the
Build Job For Load Step panel. This JCL can be used to LOAD the
data contained in the GRInnnnn datasets into DB2 tables specified
in the GRIPUNCH dataset.
Windows
- installRoot\user\data
profile name\dataprofilename.griml
- The DB2 Test Database Generator Data Profile
- installRoot\user\data
profile name\log
- the DB2 Test Database Generator log file
- installRoot\user\data
profile name\run
- a temp file that exists only while the DB2 Test Database Generator
server is running
- installRoot\user\data
profile name\targetname.ddl
- if you elected to create matching DDL for the targets, each
target has its DDL in this file. This file type can be present only
after test data generation.
- installRoot\user\data
profile name\targetname.gen.ddl
- a file that shows the DDL that is created by DB2 Test Database
Generator. This file is used to determine which DDL has been successfully
run at the database. All DDL that has been successfully run will
be commented out in the file. Any DDL that was not successfully
run will not be commented out in the file. This file type can be
present only after test data generation.
- installRoot\user\data
profile name\targetname.sql
- the SQL output if the target is a table. This file type can
be present only after test data generation.
- installRoot\user\data
profile name\targetname.gen.sql
- a file that shows the SQL that is created by Test Database Generator.
This file is used to determine which SQL has been successfully run
at the database. All SQL that has been successfully run will be commented
out in the file. Any SQL that was not successfully run will not
be commented out in this file. This file type can be present only
after test data generation.
- installRoot\user\data
profile name\targetname.xml
- the XML if you decided to create an XML target. This file type
can be present only after test data generation.
- installRoot\user\data
profile name\targetname.csv
- the delimited text output. This file is present only when a
delimited text target is created. This file type can be present
only after test data generation.
- installRoot\user\data
profile name\generate.sh
- This is a shell script that is used by DB2 Test Database Generator
to generate test data.
- installRoot\user\data
profile name\generate.bat
- This is a batch file that is used by DB2 Test Database Generator
to generate test data. This file is used only when the DB2 Test
Database Generator server is installed on Windows platforms.
- installRoot\user\data
profile name\stderr.txt
- This file contains any error output created when generating
test data.
- installRoot\user\data
profile name\stdout.txt
- This file contains all output created when generating test data.
Where:
UNIX
- installRoot/user/data
profile name/dataprofilename.griml
- The DB2 Test Database Generator Data Profile
- installRoot/user/data
profile name/log
- the DB2 Test Database Generator log file
- installRoot/user/data
profile name/run
- a temp file that exists only while the DB2 Test Database Generator
server is running
- installRoot/user/data
profile name/targetname.ddl
- if you elected to create matching DDL for the targets, each
target has its DDL in this file. This file type can be present only
after test data generation.
- installRoot/user/data
profile name/targetname.gen.ddl
- a file that shows the DDL that is created by DB2 Test Database
Generator. This file is used to determine which DDL has been successfully
run at the database. All DDL that has been successfully run will
be commented out in the file. Any DDL that was not successfully
run will not be commented out in the file. This file type can be
present only after test data generation.
- installRoot/user/data
profile name/targetname.sql
- the SQL output if the target is a table. This file type can
be present only after test data generation.
- installRoot/user/data
profile name/targetname.gen.sql
- a file that shows the SQL that is created by Test Database Generator.
This file is used to determine which SQL has been successfully run
at the database. All SQL that has been successfully run will be commented
out in the file. Any SQL that was not successfully run will not
be commented out in this file. This file type can be present only
after test data generation.
- installRoot/user/data
profile name/targetname.xml
- the XML if you decided to create an XML target. This file type
can be present only after test data generation.
- installRoot/user/data
profile name/targetname.csv
- the delimited text output. This file is present only when a
delimited text target is created. This file type can be present
only after test data generation.
- installRoot/user/data
profile name/generate.sh
- This is a shell script that is used by DB2 Test Database Generator
to generate test data. This file is used only when the DB2 Test
Database Generator server is installed on UNIX platforms.
- installRoot/user/data
profile name/stderr.txt
- This file contains any error output created when generating
test data.
- installRoot/user/data
profile name/stdout.txt
- This file contains all output created when generating test data.
Where: