Fill in all the fields of this wizard to create a Screen
or the derived instance of a Screen.
- Project
- Choose a project in the dropdown list or enter the name of the
project in which the instance will be saved.
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).
- Package
- Choose a package in the dropdown list or enter the name of a new
package.
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.
- Name
- Enter the Screen name here. It must be 6 characters long, the
first two characters being the Dialog name.
The Dialog must have
been previously defined.
If you are creating the derived
instance of a Screen (via the Derive box),
you may use the whole length of the edit field to enter the name.
So, for example, the name of the derived instance may start with the
name of its reference instance, followed by the generation library
if you are using a Library substitution derivation
type. If you do not enter anything here and if you check the Derive box
and specify a reference instance in the Screen
to derive field, the name is automatically initialized
with the name of the reference instance.
- Parent Dialog
- Use the Browse button to select the Dialog
to which the Screen belongs.
Once you have validated, the Dialog
name, followed by the package name, is displayed in this field.
- Generation parameters
- Generation parameters are specified in libraries. These parameters
are related to the adaptation to the operating system in use.
You
select the library by clicking the Browse... button.
- Label
- Enter the label, which identifies the new instance. It will then
constitute a search criterion for a subsequent search.
- Open editor on finish
- Check this box if you want the editor of the instance you are
creating to open up automatically. The editor will open up on the Overview tab.
From there, you will be able to access the other tabs to specify all
the characteristics of the instance.
- Derive
- Check this box if you want to create a derived instance which
will point to a reference instance. From this derived instance, which
will only contain a link to the reference instance and possibly a
link to a generation library, you will be able to generate the reference instance without duplicating its design. Checking
this box displays two fields:
- Derivation type. Depending on the entity,
there can be one or two derivation types:
- Library substitution is available on Programs,
Screens, Data Structures (for the generation of the Copybooks) and
Dialogs (for the generation of the error messages). With this derivation
type, you will use the derived instance to generate the reference
instance from a different library, without duplicating its design.
The generation parameters of the library indicated in the derived
instance will output a Cobol source different from that generated
from the library of the reference instance.
- Source inheritance is available on entities
which can contain specific code: Programs and Screens. With this derivation
type, you will use the derived instance to generate the reference
Program or Screen. The complete source code (i.e. the generated code
and the specific code) of the reference instance becomes the generated
code in the derived instance and this generated code is then reconcilied
with the specific code of the derived instance. In turn, the derived
instance can also become the reference instance for a new derived
instance and the same process applies.
- <Entity> to derive. In the wizard, <Entity> can
be Program, Screen, Data
Structure or Dialog. You select
here the reference instance, which contains the design and, possibly,
the specific code needed by the derived instance