Fill in all the fields of this wizard to create a Data Element.
A project represents the physical distribution of your instances in your workspace. It groups directories and files. It is used to organize resources which will be built, shared or versioned.
A Pacbase project contains a sub-set of files which correspond to the models and/or generated sources making up a Pacbase application.
There can be various projects for each location (a location is the equivalent of a database).
A package corresponds to a logical group of information.
The logical resources contained in a package can be distributed into various projects.
In the 'Navigator' view of the 'Design' perspective, you will see that the packages represent the branches of your projects. Each package contains its own instances.
For the resources transferred from Pacbase, the naming convention of a package will be {Repository Name}.{Library Path}.{Library Name} So respecting this naming when you create a package is a good idea. To reflect the library hierarchy, you can enter the library names (starting from the highest-level library), and separate each with a period (ex: 'COM.CIF'). This way, the 'Navigator' view will display a first-level branch, COM, with its instances, and a second-level branch, CIF, with its own instances.
This name consists of alphabetic or numeric characters only. The following table lists the Data Element names that cannot be created:
Name | Reserved for |
---|---|
FILLER | Field alignment |
ENPR GRPR ERUT |
Error check fields on transaction files (options
of the Batch Function) Data Element error check Segment error check User-defined errors |
All Data Elements from the same 'family' are logically linked in the Database. A child Data Element cannot be a parent as well. The inheritance tree of the current instance is displayed on the right of the tab. This tree displays its parent, if any, as well as its children, if any.
To specify a parent Data Element, click the Change button and select a Data Element in the selection wizard.
The internal format is used when the Data Element is called in:
You must ensure the compatibility between the input and internal formats.
Symbolic value | Meaning |
---|---|
D | Without century (DDMMYY or MMDDYY) |
I | Without century (YYMMDD) |
E | Without century (DD/MM/YY or MM/DD/YY) |
S | With century (CCYYMMDD) |
C | With century (DDMMCCYY or MMDDCCYY) |
M | With century (DD/MM/CCYY or MM/DD/CCYY) |
G | Gregorian format (CCYY-MM-DD) |
T | Time format (HH:MM:SS) |
TS | Timestamp format |
For details on the use of the formats with the various types of database blocks, see the summary tables in chapter 'Columns: Data Elements' of the 'Relational SQL Database Description' Manual at this URL:
http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477
You select the library by clicking the Browse... button.