HP 3000 Manuals

Loading Definitions [ HP System Dictionary XL Gen. Ref. Vol. 2-Part 3 SDCONV ] MPE/iX 5.0 Documentation

HP System Dictionary XL Gen. Ref. Vol. 2-Part 3 SDCONV

Loading Definitions

When the LOAD command is issued, the data residing in the Dictionary/V
dictionary is retrieved through the IMAGE intrinsics. SDCONV first
converts the entity definitions in the Dictionary/V database. After all
the entity definitions are loaded, the relationships contained in the
detail data sets of the Dictionary/V dictionary are loaded into the
System Dictionary. The following paragraphs provide detailed information
about how the Dictionary/V data is mapped into the System Dictionary
data.

Loading Entities

SDCONV retrieves entity definitions from the data sets in the following
sequence:

DATA-ELEMENT
DATA-FILE
DATA-CATEGORY
DATA-GROUP
DATA-CLASS
DATA-PROCEDURE
DATA-LOCATION

The master data sets listed above are read serially by the DBGET
intrinsic. Some of these data sets contain passive links, e.g. the
DESCRIPTION-KEY on most of the data sets above. For these passive links,
a chained read into the linked detail sets (FILE-PATH, FILE-SORT,
DESCRIPTION-TEXT) is performed to retrieve the actual value. The
following paragraphs describe, in detail, the loading process for
entities.

DATA-ELEMENT. This data set contains the definitions of elements.
Entries in this data set are assigned the ELEMENT entity type. Each
field is mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. Only if SCOPE-OWNER = RESPONSIBLE and ELEMENT-RESP is not empty.

2. The date-created and date-changed System Dictionary attributes are
set by the System Dictionary intrinsics. Therefore, DATA-CREATE
and DATE-CHANGE are not mapped.

3. Only if SCOPE-OWNER = IDENTITY-CREATE or SCOPE-OWNER = RESPONSIBLE
and the responsible user field is blank.

4. Scope-changed is assigned the same value as scope-owner by the
System Dictionary intrinsics. Therefore, IDENTITY-CHANGE is not
mapped to the scope-changed attribute.

5. The passive link will be searched to get the actual description.

DATA-FILE. This data set contains the definitions of files. The entity
type depends on the value of the FILE-TYPE field. Each field in this set
is mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. The following mapping will be used:

FILE-TYPE entity type attributes to set
---------------------------------------------------------------------------------------

BASE IMAGE-DATABASE ***
MAST IMAGE-DATASET image-dataset-type = MANUAL
AUTO IMAGE-DATASET image-dataset-type = AUTOMATIC
DETL IMAGE-DATASET image-dataset-type = DETAIL
KSAM KSAMFILE ***
MPEF FILE file-type = SEQUENTIAL
MPER FILE file-type = RELATIVE
VPLS FORMSFILE ***
FORM FORM ***

If FILE-TYPE is not 'BASE', 'VPLS', or 'FORM', then the file name
is used to create a RECORD entity. The byte-length attribute will
be filled in later when the FILE-ELEMENT detail set is converted.

2. Only if SCOPE-OWNER = RESPONSIBLE and FILE-RESP is not empty.

3. Only if SCOPE-OWNER = IDENTITY-CREATE or SCOPE-OWNER = RESPONSIBLE
and the responsible user field is blank.

4. The passive link will be searched to get the actual description.

5. The value of this field is converted to the System Dictionary
format only if the destination entity type is FILE or KSAMFILE. If
so, following mapping will be used:

FILE-REC-FORMAT record-format
---------------------------------------------------------------------------------------

0 FIXED
1 VARIABLE
2 UNDEFINED
4 SPANNED

6. The value of this field is ignored, unless the destination entity
type is FILE. If it is FILE, the following mapping is used:

FILE-DATA-TYPE char-type
---------------------------------------------------------------------------------------

0 ASCII
1 EBCDIC

7. The value of this field is ignored, unless the destination entity
type is FILE. If it is FILE, the following mapping is used:

FILE-REC-MODE recording-mode
---------------------------------------------------------------------------------------

0 ASCII
1 BINARY

8. The FILE-REC-SIZE field has two sub-items. The first sub-item
will be mapped to the min-record-size attribute in the System
Dictionary. It is zero if the file has fixed or spanned record
format. The second sub-item is mapped to the max-record-size
attribute. The mapping just described will occur, only if the
destination entity type is FILE or KSAMFILE. Otherwise, this field
is ignored.

9. FILE-BK-FACTOR has three sub-items; the first one is mapped to the
blocking-units attribute in the System Dictionary; 0 is mapped to
RECORDS and 1 to CHARACTERS. The second sub-item is mapped to the
blocking-min attribute. The third sub-item is mapped to the
blocking-max attribute. The mapping just described will occur,
only if the destination entity type is FILE or KSAMFILE.
Otherwise, this field is ignored.

10. If the destination entity type is FILE, FILE-DEVICE field in
Dictionary/V is used as the DEVICE-CLASS name in the FILE uses
DEVICE-CLASS relationship. Otherwise, this field is ignored. If
the DEVICE-CLASS does not exist in System Dictionary, it will be
created. Then, the FILE uses DEVICE-CLASS relationship is created
with the cctl-flag attribute initialized as shown in 12.

11. If the destination entity type is FILE, FILE-DEV-CLASS is mapped
to the file-dev-class attribute. Otherwise, this field is
ignored. For FILEs, the value of FILE-DEV-CLASS is mapped to the
file-dev-class attribute according to the following table:

FILE-DEV-CLASS file-dev-class meaning
---------------------------------------------------------------------------------------

0 A Mass storage device
1 R Unit record device
(e.g. card reader)
2 T Utility device (e.g. tape drive)

12. This field is used only for the FILE entity type; it is used to
initialize the cctl-flag attribute on the FILE uses DEVICE-CLASS
relationship. If the value of this field is 1, cctl-flag is set
to TRUE. Otherwise, it is set to FALSE.

DATA-CATEGORY. This data set contains the definitions of categories.
Entries in this data set are mapped to the CATEGORY entity type in the
System Dictionary. Each field in the data set is mapped according to the
following table:

------------------------------------------------------------------------------------------

| CATEGORY entity name |
| CATEGORY-NAME entity-long-name attribute |
| CATEGORY-TYPE category-type attribute |
| CATEGORY-RESP scope-owner attribute |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE-CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See DATA-ELEMENT. |
| DESCRIPTION-KEY description attribute |
------------------------------------------------------------------------------------------

DATA-GROUP. This data set contains the definitions of Inform groups.
Entries in this data set are assigned the INFORM-GROUP entity type. Each
field is mapped according to the following table:

------------------------------------------------------------------------------------------

| GROUP entity name |
| GROUP-NAME entity-long-name attribute |
| GROUP-TYPE inform-group-type attribute |
| GROUP-RESP scope-owner attribute |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE-CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See DATA-ELEMENT. |
| DESCRIPTION-KEY description attribute |
------------------------------------------------------------------------------------------

DATA-CLASS. This data set contains the definitions of IMAGE and Inform
user classes. It is also used to document the MPE, VPLUS forms file, and
KSAM file lockwords. In order to map the entries in this data set
correctly, the following method is used: First, the value of the
CLASS-TYPE field is examined. If it is INFO, then the entry is mapped to
the INFORM-CLASS entity type. If not, the value of FILE-KEY is examined.
If the key is not zero, the entry is mapped to the IMAGE-CLASS entity
type. Otherwise, the value of CLASS is used to search the CLASS-FILE
detail data set to see if the class is related with an IMAGE database or
data set. If so, the class is mapped to the IMAGE-CLASS entity type. If
the class is only related to non-IMAGE files, the entry is merely
documenting a file lockword. In this case, no entity is created in
System Dictionary and the file's lockword will be updated when the
CLASS-FILE data set is mapped. If no file is related to this class,
i.e., no entry is found in CLASS-FILE, the entry will be assumed to be an
IMAGE-CLASS. Each field in this set is mapped according to the following
table:

------------------------------------------------------------------------------------------

| CLASS entity name |
| CLASS-NAME entity-long-name attribute |
| CLASS-TYPE image-class-type attribute*1 |
| CLASS-PASSWORD password attribute |
| CLASS-RESP scope-owner attribute |
| FILE-KEY IMAGE-DATABASE contains IMAGE-CLASS*2 |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE-CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See DATA-ELEMENT. |
| DESCRIPTION-KEY description attribute |
------------------------------------------------------------------------------------------

Notes

1. Only if the entity type is determined to be IMAGE-CLASS, will this
mapping be performed.

2. Only if FILE-KEY is non-zero, will FILE-PATH data set be searched
to create this relationship. The FILE-PATH detail set is searched
to find the name of the IMAGE-DATABASE.

DATA-PROCEDURE. This data set contains the definitions of program
modules. Entries in this data set are assigned the MODULE entity type.
Each field is mapped according to the following table:

------------------------------------------------------------------------------------------

| PROCEDURE entity name |
| PROCEDURE-LANG language attribute |
| PROCEDURE-NAME entity-long-name attribute |
| PROCEDURE-TYPE module-type attribute |
| PROCEDURE-RESP scope-owner attribute |
| DATA-CREATE Not mapped. See DATA-ELEMENT |
| DATE-CHANGE Not mapped. See DATA-ELEMENT |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See DATA-ELEMENT. |
| DESCRIPTION-KEY description attribute |
------------------------------------------------------------------------------------------

DATA-LOCATION. This data set contains the definitions of locations.
Entries in this data set are assigned the LOCATION entity type. Each
field is mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. SDCONV first examines the contents of LOCATION-GROUP and
LOCATION-ACCOUNT. If both of them are blank, then no LOCATION
names MPE-GROUP MPE-ACCOUNT relationship is created. If not, then
SDCONV uses the non-blank field values to create MPE-GROUP and/or
MPE-ACCOUNT, if they did not already exist in System Dictionary.
Then, the LOCATION names MPE-GROUP MPE-ACCOUNT relationship is
created.

2. If this field is non-blank, the value is used to create a NODE
entity, if it did not already exist. Then, the LOCATION names
NODE NETWORK-DOMAIN NETWORK-ORGANIZATION four-way relationship is
created, with blank entries for the NETWORK-DOMAIN and
NETWORK-ORGANIZATION.

Loading Relationships

The relationship data is retrieved from the following Dictionary/V detail
sets:

ELEMENT-ELEMENT
ELEMENT-REFTYPE
FILE-ELEMENT
FILE-EL-SECOND
FILE-FILE
CATEGORY-CATEGORY
CATEGORY-ELEMENT
GROUP-GROUP
GROUP-ELEMENT
CLASS-GROUP
CLASS-ELEMENT
CLASS-CLASS
CLASS-FILE
PROCEDURE-ELEMEN
PROCEDURE-PROCED
PROCEDURE-LOCATI
FILE-LOCATION
REPORT-LIST

When converting relationship data, note that the POSITION field is not
mapped. SDCONV simply reads the entries from detail sets in the sorted
sequence (by POSITION) and writes to the System Dictionary in the same
order. Therefore, the relationship-position System Dictionary attribute
automatically generated by the intrinsics is sufficient.

The following paragraphs describe, in detail, the loading process for
relationships from the Dictionary/V data sets to the System Dictionary
data sets.

ELEMENT-ELEMENT. This data set contains the information about
relationships between two elements. This data set requires special
handling since it is the data set which contains information about
redefining COBOL elements in Dictionary/V. SDCONV first reads the
DATA-ELEMENT master set serially, and, with the name of the element,
chains into the ELEMENT-PARENT search item of this ELEMENT-ELEMENT detail
set. If the element does not have a child element of the name
$REDEFINES, then each detail set entry retrieved is mapped to the ELEMENT
contains ELEMENT relationship, and each field in the data set is mapped
to the corresponding System Dictionary attribute according to the
following table:

------------------------------------------------------------------------------------------
| |
| ELEMENT-PARENT entity name of the left operand |
| |
| ELEMENT-CHILD entity name of the right operand |
| |
| ELEMENT-POSITION byte-offset attribute |
| |
| DATA-CREATE See note 1 |
| |
| DATE-CHANGE See note 2 |
| |
| IDENTITY-CREATE scope-owner attribute*3 |
| |
| IDENTITY-CHANGE See note 4 |
| |
| DESCRIPTION-KEY description attribute*5 |
| |
| POSITION Not mapped |
| |
| ELEMENT-ALIAS-E alias as specified by the ALIAS parameter |
| |
| |
------------------------------------------------------------------------------------------

Notes

1. date created is reset by the system dictionary intrinsics.

2. date changed is reset by the system dictionary intrinsics.

3. Only if SCOPE-OWNER = IDENTITY-CREATE or SCOPE-OWNER =
RESPONSIBLE.

4. Scope-changed is assigned the same value as scope-owner by the
System Dictionary intrinsics.

5. The passive link will be searched to get the actual description.

6. If the BACK-REFERENCE parameter is OFF, then some of the child
ELEMENT entity's attributes are retrieved to initialize the
following relationship attributes:

relationship attribute value assigned
back-reference-flag false
element-type ELEMENT-TYPE from child ELEMENT
display-length ELEMENT-SIZE from child ELEMENT
decimal ELEMENT-DEC from child ELEMENT
blank ELEMENT-BLANK from child ELEMENT
justify ELEMENT-JUST from child ELEMENT
edit-mask (variable) ELEMENT-EDIT from child ELEMENT
entry-text (variable) ELEMENT-ENTRY from child ELEMENT
heading-text (variable) ELEMENT-HEAD from child ELEMENT

If the parent element does have a child element named $REDEFINES, the
following will occur:

* All children which appear before the $REDEFINES child will be loaded
according to the above method.

* When reaching the $REDEFINES, SDCONV will create an entity of type
ELEMENT, with attributes corresponding to the table above, and with
the addition of the BYTE-ELEMENT attribute. The name of this entity
will be contained in ELEMENT-ALIAS from the ELEMENT-ELEMENT
relationship.

* An ELEMENT redefines ELEMENT relationship will then be created
between the created element and the parent element.

The same process can occur for all following children with one exception:
since there is only one child element named $REDEFINES, and therefore
only one ELEMENT-ALIAS name to create redefining elements with, the
ELEMENT-ALIAS name will be suffixed and incremented as needed, as shown
below.

name-1, name-2, name-3, etc.

ELEMENT-REFTYPE. This data set contains the relationships that describe
how one element references another element. SDCONV reads the
DATA-ELEMENT master set serially and chains into the ELEMENT search item
of this detail set. Each entry retrieved is mapped to the ELEMENT
references ELEMENT relationship. Each field in the data set is mapped to
System Dictionary attributes according to the following table:

------------------------------------------------------------------------------------------

| ELEMENT entity name of the left operand |
| ELEMENT-RTYPE entity name of the right operand |
------------------------------------------------------------------------------------------

The following table is used to initialize some of the attributes
associated with the relationship:

attribute value to assign
scope-owner logon scope of the dictionary
date-created provided by the SD intrinsic
date-changed provided by the SD intrinsic
scope-changed logon scope of the dictionary
sensitivity sensitivity specified in the DICT3000 command

FILE-ELEMENT. This data set contains all the relationships between files
and elements. As such, a careful analysis is made to determine the
correct destination relationship type; hence, this data set is further
broken down according to the file type of the file. The file type is
obtained from the FILE-TYPE field of DATA-FILE. Note that the file type
cannot be BASE or VPLS. Entries in this data set are retrieved by first
reading the DATA-FILE master set serially, and then chaining into the
detail set.

MAST File Type. If the FILE-TYPE field in DATA-FILE contains 'MAST', the
file in question is an TurboIMAGE manual master data set. In that case,
the FILE-KEY field in the detail set contains either 0 or -1. The
following definitions are created:

1) IMAGE-DATASET contains RECORD relationship
2) RECORD contains ELEMENT relationship
3) IMAGE-DATASET key ELEMENT, if FILE-KEY = -1

The fields are mapped according to the following table:

-------------------------------------------------------------------------------------------

Notes

1. ELEMENT is used as the element name in the RECORD contains ELEMENT
relationship. It is also used as the search key into DATA-ELEMENT
data set. The element entity information retrieved from
DATA-ELEMENT is used to initialize the relationship attributes if
the BACK-REFERENCE = OFF. In that case, the following mapping is
used:

attribute value assigned
element-type ELEMENT-TYPE from DATA-ELEMENT
byte-offset generated by SDCONV (starts from 1)
display-length ELEMENT-SIZE from DATA-ELEMENT
decimal ELEMENT-DEC from DATA-ELEMENT
byte-length ELEMENT-LENGTH from DATA-ELEMENT
count ELEMENT-COUNT from DATA-ELEMENT
units ELEMENT-UNITS from DATA-ELEMENT
sign ELEMENT-SIGN from DATA-ELEMENT
blank ELEMENT-BLANK from DATA-ELEMENT
justify ELEMENT-JUST from DATA-ELEMENT
synchronize ELEMENT-SYNC from DATA-ELEMENT
edit-mask (variable) ELEMENT-EDIT from child ELEMENT
entry-text (variable) ELEMENT-ENTRY from child ELEMENT
heading-text (variable) ELEMENT-HEAD from child ELEMENT

2. When the file type is MAST, FILE-KEY can have either 0 or -1. If
it is -1, the element is the search item for the master; hence,
the IMAGE-DATASET key ELEMENT relationship is established with the
attributes initialized in the normal manner.

AUTO File Type. If the FILE-TYPE field in DATA-FILE contains 'AUTO', the
file in question is an IMAGE automatic master data set. The following
definitions are created:

1) IMAGE-DATASET contains RECORD relationship
2) RECORD contains ELEMENT relationship
3) IMAGE-DATASET key ELEMENT

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

2. Note that automatic master sets contain only one element and that
element is used to create the IMAGE-DATASET key ELEMENT
relationship.

DETL File Type. If the FILE-TYPE field in DATA-FILE contains 'DETL', the
file in question is an IMAGE detail data set. The following definitions
are created:

1) IMAGE-DATASET contains RECORD relationship
2) RECORD contains ELEMENT relationship
3) IMAGE-DATASET ELEMENT IMAGE-DATASET IMAGE-DATABASE chains
relationship, if FILE-KEY > 0

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

2. When the file type is DETL, FILE-KEY can have any non-negative
value. If it is 0, the element is not a search item for the
detail data set. Therefore, no chain relationship is created. On
the other hand, if it is >0, then the element is a search item for
the data set, and the chain relationship involving IMAGE-DATASET,
ELEMENT, ELEMENT, IMAGE-DATASET, and IMAGE-DATABASE is created.
In the relationship, the first IMAGE-DATASET is the detail data
set; the data set name is taken from the FILE field. The next
entity (ELEMENT) is the search item for the detail set; the
element name is taken from the ELEMENT field. The next is the
sort item for the path, whose name can be retrieved through the
ELEMENT-KEY field. If it is 0, the sort item is left blank.
Otherwise, the FILE-SORT detail data set is searched with the key
to find the sort item's actual name. The next entity is the
master data set of the path. The file link in FILE-KEY is used to
search the FILE-PATH detail set, in order to find the master data
set's actual name. The last entity is the database to which the
path belongs. In order to find the database name, the FILE-FILE
data set is searched with FILE-CHILD = the detail set name. For
each database related to the detail set, SDCONV checks to see if
the database also contains the master set. If so, the chain
relationship is created. Therefore, many chain relationships
involving different databases can be created.

3. This field contains the link for the sort item. See above.

MPEF or MPER File Type. If the FILE-TYPE field in DATA-FILE contains
'MPEF' or 'MPER', the file in question is an MPE sequential or an MPE
relative file. The following definitions are created:

1) FILE contains RECORD relationship
2) RECORD contains ELEMENT relationship

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

2. The destination alias is determined from the value of the ALIAS
parameter of the DICT3000 command.

3. The primary-record attribute of the FILE contains RECORD
relationship is initialized to TRUE.

KSAM File Type. If the FILE-TYPE field in DATA-FILE contains 'KSAM', the
file in question is a KSAM file. The following definitions are created:

1) KSAMFILE contains RECORD relationship
2) RECORD contains ELEMENT relationship
3) KSAMFILE key ELEMENT, if FILE-KEY = -1

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

2. The destination alias is determined from the value of the ALIAS
parameter of the DICT3000 command.

3. If FILE-KEY = -1, then the element is a key for the KSAM file. In
this case, the KSAMFILE key ELEMENT relationship is created with
the attributes initialized as follows:

attribute value to assign
relationship-position set by SD intrinsic
primary-flag true if ELEMENT-PRIMARY = 1
false if ELEMENT-PRIMARY = 0
unique true if KEY-DUPLICATES = 0
false if KEY-DUPLICATES = 1

4. If ELEMENT-PRIMARY = 1, then the primary-flag attribute is set to
TRUE. If ELEMENT-PRIMARY = 0, then the primary-flag is false in
the KSAMFILE key ELEMENT relationship.

5. If KEY-DUPLICATES = 0, the unique attribute is set to TRUE.
Otherwise, unique is set to false in the KSAMFILE key ELEMENT
relationship.

6. The primary-record attribute is initialized to TRUE.

FORM File Type. If the FILE-TYPE field in DATA-FILE contains 'FORM', the
file in question is a VPLUS form. The following definitions are created:

1) FORM contains ELEMENT.

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. For the FORM contains ELEMENT relationship type, the
back-reference-flag attribute is not included as one of the
relationship attributes. Therefore, the value of the
BACK-REFERENCE parameter will be ignored.

2. Note that some relationship attribute values are retrieved from
the ELEMENT's entity level attributes as shown below:

relationship attribute value assigned
element-type ELEMENT-TYPE field from DATA-ELEMENT
byte-offset calculated by SDCONV (starts from 1)
display-length ELEMENT-SIZE field from DATA-ELEMENT
decimal ELEMENT-DEC field from DATA-ELEMENT
field-number FILE-FIELD-NO field from FILE-ELEMENT
edit-mask (variable) ELEMENT-EDIT field from DATA-ELEMENT
entry-text (variable) ELEMENT-ENTRY field from DATA-ELEMENT
heading-text (variable) ELEMENT-HEAD field from DATA-ELEMENT

FILE-EL-SECOND. This detail data set contains the secondary record
format definitions for MPER, MPEF, and KSAM file types. Note that the
primary-record attribute is always set to FALSE in the FILE/KSAMFILE
contains RECORD relationship, since the record format contained in this
data set is not primary.

* If the file type is KSAM, the following relationships are created:
1) RECORD entity, if it does not exist in System Dictionary
2) KSAMFILE contains RECORD relationship
3) RECORD contains ELEMENT relationship

* If the file type is MPEF or MPER, the following relationships are
created:

1) RECORD entity, if it does not exist in System Dictionary
2) FILE contains RECORD relationship
3) RECORD contains ELEMENT relationship

SDCONV performs a serial read through DATA-FILE, and chains into the FILE
search item in FILE-EL-SECOND. The value of each field is mapped to the
System Dictionary according to the following:

------------------------------------------------------------------------------------------

| FILE entity name for the FILE entity |
| ELEMENT entity name for the ELEMENT entity*1 |
| ELEMENT-ALIAS See note 2 |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

Notes

1. ELEMENT is used first to create a RECORD entity if it does not
exist already. When creating it, the byte-length attribute is
initialized with the value of the ELEMENT's ELEMENT-LENGTH. Then,
ELEMENT is used as the second entity of the entity list in the
RECORD contains ELEMENT relationship. Note that if BACK-REFERENCE
= OFF, then the ELEMENT entity information retrieved from
DATA-ELEMENT is used to initialize some of the relationship
attributes. The following table shows how the attributes are
initialized if BACK-REFERENCE = OFF:

attribute value assigned
type ELEMENT-TYPE from DATA-ELEMENT
byte-offset generated by SDCONV (starts from 1)
display-length ELEMENT-SIZE from DATA-ELEMENT
decimal ELEMENT-DEC from DATA-ELEMENT
byte-length ELEMENT-LENGTH from DATA-ELEMENT
count ELEMENT-COUNT from DATA-ELEMENT
units ELEMENT-UNITS from DATA-ELEMENT
sign ELEMENT-SIGN from DATA-ELEMENT
blank ELEMENT-BLANK from DATA-ELEMENT
justify ELEMENT-JUST from DATA-ELEMENT
synchronize ELEMENT-SYNC from DATA-ELEMENT
edit-mask (variable) ELEMENT-EDIT from child ELEMENT
entry-text (variable) ELEMENT-ENTRY from child ELEMENT
heading-text (variable) ELEMENT-HEAD from child ELEMENT

2. The destination alias is determined from the value of the ALIAS
parameter of the DICT3000 command.

FILE-FILE. This data set contains the parent-child relationships between
two files. The parent files in this data set should have either the BASE
or VPLS type. If the parent file type is BASE, then the child file type
is either MAST, AUTO, or DETL. If it is VPLS, the child type should be
FORM. According to the parent and child file type, either:

IMAGE-DATABASE contains IMAGE-DATASET

FORMSFILE contains FORM

relationship is created. SDCONV first reads DATA-FILE serially, and then
chains into FILE-PARENT in FILE-FILE. The fields are mapped according to
the following table:

------------------------------------------------------------------------------------------

Notes

1. FILE-PARENT is used as the IMAGE-DATABASE/FORMSFILE entity name.

2. FILE-CHILD is used as the IMAGE-DATASET/FORM entity name.

3. FILE-ALIAS-F is used as the image-alias attribute if the
relationship to create is IMAGE-DATABASE contains IMAGE-DATASET.
If the relationship is FORMSFILE contains FORM, then this field is
mapped to the vplus-alias attribute.

4. FILE-SIZE is mapped to the capacity attribute only if the
relationship is IMAGE-DATABASE contains IMAGE-DATASET.

5. FILE-BLOCK is mapped to the blocking-factor attribute only if the
relationship is IMAGE-DATABASE contains IMAGE-DATASET.

CATEGORY-CATEGORY. This data set relates one category to another.
Entries in this data set are retrieved through chained read on
CATEGORY-PARENT and are mapped to the CATEGORY contains CATEGORY
relationship. The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| CATEGORY-PARENT parent CATEGORY entity name |
| CATEGORY-CHILD child CATEGORY entity name |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

CATEGORY-ELEMENT. This data set relates a CATEGORY to ELEMENTs.
Therefore, entries are mapped to the CATEGORY contains ELEMENT
relationships and are retrieved through chained read on CATEGORY. The
fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| CATEGORY entity name for CATEGORY |
| ELEMENT entity name for ELEMENT |
| ELEMENT-ALIAS-C alias as specified by the ALIAS parameter |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

Note that when converting CATEGORY-CATEGORY and CATEGORY-ELEMENT detail
sets, SDCONV reads serially through DATA-CATEGORY, and then, with each
CATEGORY name found, chains into CATEGORY-PARENT in CATEGORY-CATEGORY and
into CATEGORY in CATEGORY-ELEMENT, i. e., SDCONV alternates between
these two sets and converts definitions.

GROUP-GROUP. This data set relates one group to another. Entries in the
data set are retrieved through chained read on GROUP-PARENT and are
mapped to the INFORM-GROUP contains INFORM-GROUP relationship. The
fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| GROUP-PARENT parent INFORM-GROUP entity name |
| GROUP-CHILD child INFORM-GROUP entity name |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

GROUP-ELEMENT. This data set contains information about relationships
between GROUPs and ELEMENTs. Entries in the data set are retrieved
through chained read on GROUP. The destination relationship type depends
on a number of factors:

1. If FILE-KEY field contains 0, then the entry is mapped to a
INFORM-GROUP contains ELEMENT FILE three-way relationship.

2. If FILE-KEY field contains a non-zero value, then the key value is
used to chain into the FILE-PATH detail set. Then the file name
found is used to find the FILE-TYPE from DATA-FILE.

3. If the FILE-TYPE is either MAST, AUTO, or DETL, the INFORM-GROUP
contains ELEMENT IMAGE-DATASET IMAGE-DATABASE relationship is
created. If the FILE-PARENT-KEY field is non-zero, that number is
used to retrieve the IMAGE-DATABASE name.

4. If the FILE-TYPE is KSAM, then the INFORM-GROUP contains ELEMENT
KSAMFILE relationship is created.

5. Otherwise, the INFORM-GROUP contains ELEMENT FILE relationship is
created.

The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. If the value of this field is 0, the element-display attribute is
set to TRUE. Otherwise, it is set to FALSE.

Note that when converting GROUP-GROUP and GROUP-ELEMENT detail sets,
SDCONV reads serially through DATA-GROUP and, for each GROUP found,
chains into GROUP-GROUP and GROUP-ELEMENT, i.e., SDCONV alternates
between these two files and converts definitions.

CLASS-GROUP. This data set relates Inform user classes to Inform groups.
Entries in the data set are retrieved through chained read on CLASS and
are mapped to the INFORM-CLASS contains INFORM-GROUP relationship. The
fields are mapped according to the following table:

------------------------------------------------------------------------------------------

CLASS-ELEMENT. This data set relates Inform classes to elements. The
entries are retrieved through chained read on CLASS and are mapped to the
ELEMENT contains IMAGE-CLASS relationship. The fields are mapped
according to the following table:

------------------------------------------------------------------------------------------

CLASS-CLASS. This data set relates Inform classes to IMAGE user classes.
The entries are retrieved through chained read on CLASS-PARENT and are
mapped to the INFORM-CLASS contains IMAGE-CLASS relationships. The
fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| CLASS-PARENT entity name for INFORM-CLASS |
| CLASS-CHILD entity name for IMAGE-CLASS |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

CLASS-FILE. This data set relates Inform/IMAGE classes to files. The
FILE field in this data set is used to obtain the type of the file, which
determines the relationship to map. The following table shows the
variety of relationships that can map to entries of this data set:

file type relationship to map
--------------------------------------------------------------------------------------

BASE IMAGE-DATABASE contains IMAGE-CLASS*1

MAST |
AUTO > IMAGE-DATASET contains IMAGE-CLASS
DETL |

KSAM |
MPEF > No relationship.*2
MPER |
VPLS |

Note the following:

1. The IMAGE-DATABASE contains IMAGE-CLASS relationship may have
already been created when DATA-CLASS was mapped. (See the
"Data-Class" section under "Loading Entities".) In that case, no
new relationship is created.

2. In these cases the file's lockword is initialized with the
CLASS-PASSWORD field value in DATA-CLASS.

Entries in the data set are retrieved through chained read on CLASS. The
fields are mapped according to the following table:

------------------------------------------------------------------------------------------

Notes

1. As explained above, if the file type is IMAGE-DATABASE or
IMAGE-DATASET, the value in this field is used as the IMAGE-CLASS
name. Otherwise, this field is not mapped.

2. The value of this field is used to search DATA-FILE. Then, the
file type found in the DATA-FILE master data set is used to
determine the destination relationship type.

3. This mapping occurs only if the file is an IMAGE data set of the
type MAST, AUTO, or DETL.

4. Note that SDCONV reads serially through DATA-CLASS, and, for each
CLASS found, chains into CLASS-GROUP, CLASS-ELEMENT, CLASS-CLASS,
and CLASS-FILE, i. e., SDCONV alternates among these sets and
converts definitions.

PROCEDURE-ELEMEN. This data set relates procedures, or program modules,
with elements. The entries are retrieved through chained read on
PROCEDURE and are mapped to the MODULE processes ELEMENT relationship.
The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| PROCEDURE entity name for MODULE |
| ELEMENT entity name for ELEMENT |
| ELEMENT-ALIAS-P alias as specified by the ALIAS parameter |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

PROCEDURE-PROCED. This data set contains parent-child relationships
among program modules. The entries are retrieved through chained read on
PROCEDURE-PARENT and are mapped to the MODULE contains MODULE
relationships. The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

| PROCEDURE-PARENT entity name for the parent MODULE |
| PROCEDURE-CHILD entity name for the child MODULE |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

PROCEDURE-LOCATI. This data set relates program modules to locations.
The entries are retrieved through chained read on PROCEDURE and are
mapped to the LOCATION contains MODULE relationships. The fields are
mapped according to the following table:

------------------------------------------------------------------------------------------

| LOCATION entity name for LOCATION |
| PROCEDURE entity name for MODULE |
| PROCEDURE-ALIAS alias as specified by the ALIAS parameter |
| DATA-CREATE Not mapped. See DATA-ELEMENT. |
| DATE CHANGE Not mapped. See DATA-ELEMENT. |
| IDENTITY-CREATE scope-owner attribute |
| IDENTITY-CHANGE Not mapped. See ELEMENT-ELEMENT. |
| DESCRIPTION-KEY description attribute |
| POSITION Not mapped |
------------------------------------------------------------------------------------------

Note that SDCONV first reads serially through the DATA-PROCEDURE master
set, and, for each PROCEDURE found, chains into PROCEDURE-ELEMEN,
PROCEDURE-PROCED, and PROCEDURE-LOCATI, i. e., SDCONV alternates among
these sets and converts definitions.

FILE-LOCATION. This data set relates files to locations. The entries
are mapped to a variety of relationships in the System Dictionary. The
destination relationship is determined by the file type, as explained in
the table below:

file type relationship to map
BASE LOCATION contains IMAGE-DATABASE
VPLS LOCATION contains FORMSFILE
KSAM LOCATION contains KSAMFILE
MPER LOCATION contains FILE
MPEF LOCATION contains FILE

SDCONV reads serially through DATA-FILE, and, for each FILE, chains into
FILE-LOCATION. The fields are mapped according to the following table:

------------------------------------------------------------------------------------------

REPORT-LIST. This data set contains information about INFORM-REPORTs
SDCONV reads the DATA-REPORTLOC master set serially, and then chains into
REPORT-LIST through the REPORT-LOC search item. Each entry in
REPORT-LIST is converted to IMAGE-REPORT entities in the System
Dictionary. The data items in the detail set are mapped as follows:

------------------------------------------------------------------------------------------

Notes

1. REPORT-LOC specifies the location in the <group>.<account> format.
SDCONV first attempts to create MPE-GROUP and MPE-ACCOUNT with the
group/account name. Because a period (.) is an illegal System
Dictionary character, it will be mapped according to the value
associated with it in the current mapping table.

2. REPORT is used to create an INFORM-REPORT entity. Then, a
LOCATION contains INFORM-REPORT relationship is created.

MPE/iX 5.0 Documentation