Data Build Manual

Using the Project Utility
Setting Up the Project Environment
099331 Tandem Computers Incorporated 3–3
1. Define the conversion project. Determine the input files from the source system to
convert and get the name of each input file. Use this information to fill out the
Project Utility Worksheet, available in Appendix C.
2. Volume to the Data Build install subvolume.
3. Run the Project utility to create a conversion project subvolume.
4. Check the spooler and correct any errors.
5. Volume to the conversion project subvolume on the Tandem system.
6. If the input data is in IXF format, go to step 10. With IXF data, Data Build creates
the NonStop SQL tables and the Source Record Descriptions files for you.
7. If the conversion is to Enscribe, go to step 9.
8. Create a NonStop SQL table for each input file.
9. Prepare a Source Record Descriptions file for each input file.
10. Modify the DEFINES and PATHCNFG files. For example, you must describe the
conversion environment using TACL DEFINEs.
Using the Project
Utility
Each Data Build conversion project produces a unique COBOL85 conversion program
for that project. You use the Project utility, located on the Data Build installation
subvolume, to create the working subvolume for a conversion project. Each
conversion project requires a subvolume on your Tandem system for all the files
needed for that conversion. You can have more than one conversion project on a
single system, but the files for each data conversion project must be separate from the
others; you must run the Project utility for each unique conversion project.
This subsection describes the information you need for a conversion project, explains
the worksheet used for collecting this information, and describes how to create a new
conversion project subvolume.
Before You Run Project Before you run the Project utility, you need to decide on the names of two subvolumes:
Name of the project subvolume
Name of the NonStop SQL catalog subvolume
Note that you must specify the NonStop SQL catalog subvolume even if you are not
converting data to NonStop SQL format.
Example
You might want to identify each subvolume with your initials and a number so you
can keep track of multiple projects. For instance, if your initials are “CC,” you might
want to name your first project subvolume:
$data.ccproj1