Progress® OpenEdge® Compilation Tools
Overview :: Download :: Screenshots :: Documentation :: JavaDoc :: Links

General

Tasks

Types

Selectors

PCTCreateBase task -- <pct:db_create />

Description

Creates Progress database.

Parameters

Attribute Description Type Requirement Default value
DBName Database name String Required No default value
DestDir Destination directory where to create the database File Optional Current directory
schemaFile Initial dump file(s) to load into database. Separate dump filenames with commas. Files are resolved first as an absolute path, then relative to base directory. String Optional No default value
StructFile Structure description file File Optional No default value
BlockSize Block size in kilobytes (1, 2, 4 or 8) Integer Optional 8
NoInit No initialization of database schema (procopy emptyX dbName) Boolean No False
Overwrite Overwrites database if exists Boolean No False
Codepage Copy empty database from a prolang subdirectory. So database use a specific codepage instead of the undefined codepage String No No default value (undefined)
wordRules Assign a specific word rules table to a database (ie runs a proutil dbname -C word-rules XXX). This command is run before loading schema (if available). This command is not run if parameter not defined. Integer No No default value (undefined)

PCTCreateBase inherits attributes from PCT.

Parameters as nested elements

propath (org.apache.tools.types.Path)

Creates a nested propath, and adds it to the implicit propath. The propath is only used during schema update.

OracleHolder (com.phenix.pct.OracleHolder)

Creates a new Oracle schema holder inside a database. If a schema holder is defined, no schema can be loaded in the main database.

MSSHolder (com.phenix.pct.MSSHolder)

Creates a new SQL Server schema holder inside a database. If a schema holder is defined, no schema can be loaded in the main database.

ODBCHolder (com.phenix.pct.ODBCHolder)

Creates a new ODBC schema holder inside a database. If a schema holder is defined, no schema can be loaded in the main database.

Examples

<PCTCreateBase dbName="MyDB" dlcHome="${env.DLC}"/>

Creates an empty database named MyDB in current directory. Command line used is procopy empty8 MyDB

<PCTCreateBase dbName="MyDB" destDir="MyDir" dlcHome="${env.DLC}" schemaFile="/home/test/MySchema.df,YourSchema.df" wordRules="1" />

Creates an empty database named MyDB in MyDir subdir of the current directory, then load proword.1 word break table (_proutil MyDB -C word-rules 1), and then loads schema from files /home/test/MySchema.df and YourSchema.df. /home/testMySchema.df will be resolved as an absolute filename, and if it's not found, PCT will search a file of the same name in the ${basedir} directory. Same thing will happen with YourSchema.df

<echo file="test.st">
  b test.b1 f 1024
  b test.b2 v 2048
  d "Schema Area":6,64 test.d1 f 1024
  d "Schema Area":6,64 test.d2 v 2048
</echo>
<PCTCreateBase dbName="test" dlcHome="${env.DLC}" structFile="test.st" codepage="utf"/>

Creates a database structure from test.st file (_proutil prostrct create test test.st) and then procopy $DLC/prolang/utf/empty8 test.

<PCTCreateBase dbName="test" dlcHome="${env.DLC}">
  <OracleHolder dbName="ora1" oracleVersion="8" codepage="iso8859-1" collation="BASIC" schemaFile="oradump.df" />
</PCTCreateBase>

Creates a new empty database, containing a schema holder for an ora1 oracle database, using a specific codepage and collation table, and loads oradump.df into database. The .df file should be generated using prodict/ora/_gendsql.p program (prodict.pl package in $DLC), or using the not-developed-yet DFConvert task