Enter the fields of this wizard to create a Screen or the
derived instance of a Screen.
- Project
- Select a project in the list or enter the name of the project
in which the instances are to 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 can
be built, shared, or stored as a version.
A Pacbase project
contains a subset of files, which correspond to the models and the
generated sources that make up an application.
There can be
various projects for each location (a location is the equivalent of
a database).
- Package
- A package corresponds to a logical group of information in a project.
If
you are maintaining a Pacbase application, selecting a package is
not advised. The instance override mechanism is then made easier because
the overriding instance is always in the same package as the overridden
instance. You do not need to manage the presence of both the instances
in the same package, which is the requirement of an override.
- Name
- Enter the Screen name here. It must be six characters long, the
first two characters being the Dialog name.
The Dialog must have
been previously defined.
If the Derive box
is checked, you can use the whole length of the edit field. The name
of the derived instance can start with the name of its reference instance.
If you have selected a Design derivation, the
name can also include the generation Library. If you do not enter
a name 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
- Click Browse to select the Dialog to which
the Screen belongs, and validate.
The Dialog name is displayed
in this field.
- Dialog type
- In this field, you initialize the Dialog or Screen type as a standard
online type or a TUI type.
- 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 Browse.
- Label
- Enter the label, which identifies the new instance. It constitutes
a search criterion for a subsequent search.
- Open editor on finish
- Select this check box if you want the editor of the instance you
are creating to open up automatically. The editor opens up on the Overview tab.
From there, you can access the other tabs to specify all the characteristics
of the instance.
- Derive
- Select this check box if you want to create a derived instance
which points to a reference instance. The derived instance contains
a link to the reference instance and possibly a link to a generation
Library. From the derived instance, you can generate the reference
instance without duplicating its design. If you select this box, two
fields are displayed:
- Derivation type. Depending on the entity,
there can be one or two derivation types:
- Design derivation is available on Programs,
Dialogs/Screens, Server Dialogs/Servers, Data Structures (for the
generation of the Copybooks). With this derivation type, you 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 produce a COBOL source
different from the source generated from the Library of the reference
instance.
- Code derivation is available on entities
which can contain specific code: Programs, Screens, and Servers. With
this derivation type, you use the derived instance to generate the
reference Program, Screen, or Server. The complete source code (the
generated code and the specific code) of the reference instance becomes
the generated code in the derived instance. Moreover this generated
code is reconciled 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
the reference instance, which contains the design and, possibly, the
specific code needed by the derived instance