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.
So naming a package after a library 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.
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).
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 |
The internal format is used when the Data Element is called:
The internal format must be coded like a COBOL picture (without print characters).
If the format of a numeric Data Element is more than 10 characters long, you must omit the ’9’ that would normally be entered after the ’V’ (for example: S9(10)V9(3) must be entered as S9(10)V(3)). This way of coding must not be used when the format is shorter than 10 characters.
Symbolic value | Meaning |
---|---|
D | Without century (DDMMYY or MMDDYY) |
C | With century (DDMMCCYY or MMDDCCYY) |
I | Without century (YYMMDD) |
S | With century (CCYYMMDD) |
E | Without century (DD/MM/YY or MM/DD/YY) |
M | With century (DD/MM/CCYY or MM/DD/CCYY) |
G | Gregorian format (CCYY-MM-DD) |
T | 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-1.ibm.com/support/docview.wss?rs=37&context=SSEP67&uid=swg27005478
You select the library by clicking the Browse... button.