HP 3000 Manuals HP 3000 Manuals
THE DICTCDE MAIN PROMPT
When the copylib file is either accepted or created by DICTCDE, the main
prompt used for generating source code and for changing the DICTCDE
options is issued:
File, Element, Parameters, Options, or Exit (F/E/P/O/EX)>
The responses allowed for this prompt indicate the following:
F begins the prompting cycle for generating source code
for IMAGE, VPLUS, KSAM, MPEF and MPER file definitions.
E begins the prompting cycle for generating source code
for element definitions.
P begins the prompting cycle for generating source code
for IMAGE, VPLUS, and KSAM standard parameters. (These
parameters are discussed later in this section.)
O begins the prompting cycle for changing the options
provided by DICTCDE. (These options are discussed in
detail later in this section.)
EX exits DICTCDE.
Each of the above responses (except the EX response) generates additional
prompts. The additional prompts are shown as each response is discussed
in more detail.
Note that if ], ]], [[CONTROL]] Y, or [[RETURN]] is entered in response
to the main prompt, DICTCDE will reissue the prompt.
Generating Code for Files
To generate source code for file definitions, enter F in response to the
main prompt.
DICTCDE will then prompt for the file name as follows:
File name>
Enter the name of the file to be extracted from the Dictionary. Only one
file may be extracted at a time. (You may not enter multiple file names
in response to this prompt.) Note that if the file to be extracted is an
IMAGE data set or a VPLUS form, you may qualify the data set or form by
its parent file. To do so, enter the name of the database or forms file
in parenthesis next to the file name as shown below:
File name> filename (parent filename)
When a file is identified by its parent file, then DICTCDE will generate
the code for the file using the file's alias (if any) within the parent
file if the alias option is enabled. (The alias option is discussed in
more detail later in this section.)
DICTCDE then displays the file type of the specified file and continues
to prompt for information. The prompts that are issued by DICTCDE depend
on the type of the file specified.
IMAGE Database Files. If the specified file is an IMAGE database,
DICTCDE will issue the following message and prompts:
File filename is an IMAGE database
Define all data sets in one module (N/Y)>
Enter Y if the generated source code for all the data sets is to be
written to one copylib module. This module will also contain the source
code for the IMAGE special parameters. These are the IMAGE special
name-constant parameters that identify the database and password for use
by the IMAGE intrinsics. To generate the IMAGE standard parameters, see
the discussion for the P (Parameters) response to the main prompt. (The
IMAGE standard parameters include the DB-STATUS array definition, the
eight MODES as constants, and the various LIST parameters.)
When all data sets are to be defined in one module, DICTCDE will prompt
for the copylib module for the database definition:
Copylib module for database name>
Enter the name of the copylib module (8 characters maximum). DICTCDE
then begins the generation process. The generated source code is echoed
to the terminal as it is written to the copylib module. If [[RETURN]] is
pressed in response to this prompt, DICTCDE will reissue the main prompt
and no source code would be generated for the database.
If the source code generated for the data sets is to be written to
different copylib modules, enter N or press [[RETURN]] in response to
Define all data sets in one module (N/Y)>. DICTCDE will then prompt for
the copylib module for each of the data sets in turn and for the IMAGE
special parameters as shown:
Copylib module for database name special parameters>
Enter the copylib module to which you will direct the source code for the
IMAGE special parameters. If [[RETURN]] is pressed in response to this
prompt, the code for the IMAGE special parameters will not be generated
and DICTCDE will issue the next prompt.
Copylib module for data set name>
Enter the copylib module for the data set specified by DICTCDE in data
set name. If [[RETURN]] is pressed in response to this prompt, the
source code for this data set will not be generated and DICTCDE will
prompt for the copylib module for the next data set that belongs to the
specified database. Once [[RETURN]] has been pressed in response to a
prompt for a data set, that data set is skipped (code can not be
generated for that data set). If ] is entered in response to this
prompt, DICTCDE will again prompt for a file name.
After a copylib module has been defined for a data set, DICTCDE issues
the following prompt:
Prefix for data items in data set name>
This prompt allows you to enter a prefix which is used in the COBOL
identifier for each data item in the specified data set. The prefix you
choose can be 8 characters maximum and must begin with a letter to be a
valid COBOL identifier. If you would like a hyphen between the prefix
and the data item name, be sure to include it as part of the prefix.
(See Examples of Generated Code later in this section for an example of
data items generated with prefixes.) When a prefix is assigned to a data
item name, those data items can be referred to uniquely in a COBOL
program without using the COBOL OF clause.
If [[RETURN]] is pressed in response to this prompt, the source code for
that data set is generated without a prefix assigned to the data items.
The code is echoed to the terminal as it is written to the copylib
module. After the code for this data set is generated, DICTCDE will
continue to prompt for copylib modules and prefixes for the remaining
data sets in the database.
After prompting for each data set in the specified database, DICTCDE will
return to the main prompt.
IMAGE Data Set Files. If the specified file is an IMAGE data set,
DICTCDE will issue the following message and prompts:
File filename is an IMAGE MASTER data set.
(DICTCDE also tells you what type of data set the file is.)
Copylib module for data set name>
Enter the name of the copylib module (8 characters maximum). If
[[RETURN]] is pressed in response to this prompt, DICTCDE will return to
the main prompt and no code will be generated.
Once the copylib module for the specified data set has been entered,
DICTCDE will prompt for the following:
Prefix for data items in data set name>
Enter the prefix to be used in the COBOL identifier for the data items in
the data set. The prefix you choose can be up to 8 characters and must
begin with a letter to be a valid COBOL identifier. If you would like a
hyphen between the prefix and the data item name, be sure to include the
hyphen as part of the prefix. (See Examples of Generated Code later in
this section for an example of data items generated with prefixes.) When
a prefix is assigned to a data item, that data item can be referred to
uniquely in a COBOL program without qualification.
If [[RETURN]] is pressed in response to this prompt, the source code for
the data set is generated without a prefix assigned to the data items.
The code is echoed to the terminal as it is written to the copylib
module.
After the source code has been generated for the data set, DICTCDE will
return to the main prompt.
VPLUS Forms Files. If the specified file is a VPLUS forms file, DICTCDE
will issue the following message and prompts:
File filename is a VPLUS forms file.
Define all forms in one module (N/Y)>
Enter Y if the generated source code for all the forms in the forms file
is to be written to one copylib module. This module will also contain
the source code for the forms file name. DICTCDE will then prompt for
the copylib module for the source code for the entire forms file as
follows:
Copylib module for forms file name>
Enter the name of the copylib module. DICTCDE will then issue the next
prompt:
Define field number tables (N/Y)>
Enter Y to generate a field number table for each form in the forms file.
The field number tables are useful in calls to some of the VPLUS
intrinsics, such as VSETERROR. The tables provide the field numbers for
each field in the form. Each field in the form is represented by a data
item in the table. The data items are COMP variables initialized to the
field number. (See the Examples of Generated Code later in this section
for examples of the field number tables.) Enter N or press [[RETURN]] in
response to this prompt if you do not want field number tables generated
for the forms.
The data items defined as numeric VPLUS fields in the Dictionary only
appear as ASCII fields in the VPLUS buffer. Because of this, DICTCDE
asks whether these fields are to be defined as PIC 9 or PIC X when the
code is generated:
Define numeric fields as PIC 9 or PIC X (9/X)>
Enter X to define every numeric field in the forms file as ASCII
alphanumeric (PICTURE CLAUSE PIC X). Enter 9 or press [[RETURN]] to
define every numeric field as ASCII numeric only (PICTURE CLAUSE PIC 9).
If field edits have been defined for the numeric fields in the forms
file, it may be more appropriate to define the numeric fields as PIC 9.
However, if you choose to define the numeric fields as PIC 9, the forms
must only allow numeric data to be entered in those fields.
DICTCDE will then begin the generation process. The generated code is
echoed to the terminal as it is written to the copylib module.
If the source code generated for the forms is to be written to different
copylib modules, enter N or press [[RETURN]] in response to Define all
forms in one module (N/Y)>. DICTCDE will then issue the following
prompts:
Copylib module for forms file name constant>
Enter the copylib module to which you are directing the source code for
the forms file name. DICTCDE will echo the code generated for the forms
file name to the terminal as it is written to the copylib module. If
[[RETURN]] is pressed in response to this prompt, this code will not be
generated and the next prompts will be issued.
The next two prompts apply to all the forms in the forms file to be
generated. These are the same prompts issued when the entire forms file
is to be defined in one copylib module.
Define field number tables (N/Y)>
Enter Y to generate field number tables for each form to be generated.
Enter N or press [[RETURN]] if you do not want to generate field number
tables.
Define numeric fields as PIC 9 or PIC X (9/X)>
Enter X to define every numeric field in every form generated as PIC X.
Enter 9 or press [[RETURN]] to define every field as PIC 9. (Remember,
if 9 is entered in response to this prompt, the forms must only allow
numeric data to be entered in those fields.)
DICTCDE then begins prompting for copylib modules for each of the forms
in the forms file.
Copylib module for formname>
Enter the copylib module for the form specified by DICTCDE in formname.
If [[RETURN]] is pressed in response to this prompt, the source code for
this form will not be generated. (The field number tables will not be
generated for that form either.) Once [[RETURN]] has been pressed in
response to the copylib module for a form, that form is skipped (code can
not be generated for that form) and DICTCDE will then prompt for the
copylib module for the next form in the forms file.
After the copylib module has been defined for a form, DICTCDE issues the
following prompt:
Prefix for data items in formname>
Enter a prefix to be used in the COBOL identifier for the data item in
the form. The prefix you choose can be up to 8 characters long and must
begin with a letter to be a valid COBOL identifier. If you would like a
hyphen between the prefix and the data item name, be sure to include the
hyphen as part of the prefix you enter. (See Examples of Generated Code
later in this section for an example of data items generated with
prefixes.) When a prefix is assigned to a data item, that data item can
be referred to uniquely in a COBOL program without using the COBOL OF
clause.
If [[RETURN]] is pressed in response to this prompt, the source code for
the data set is generated without a prefix assigned to the data items.
The code is echoed to the terminal as it is written to the copylib
module. DICTCDE then prompts for the copylib module for the next form in
the forms file.
After the source code has been generated for the forms file, DICTCDE will
return to the main prompt.
VPLUS Forms. If the specified file is a VPLUS form, DICTCDE will issue
the following message and prompts:
File formname is a VPLUS form.
Note that the next prompts are also issued when the file is a forms file.
Define field number tables (N/Y)>
Enter Y to generate field number tables for the specified form. Enter N
or press [[RETURN]] if you do not want field number tables generated.
Define numeric fields as PIC 9 or PIC X (9/X)>
Enter X to define every numeric field in the specified form as PIC X.
Enter 9 or press [[RETURN]] to define every numeric field as PIC 9.
(Remember, if 9 is entered in response to this prompt, the form must only
allow numeric data to be entered in those fields.)
DICTCDE next prompts for the copylib module.
Copylib module for formname>
Enter the copylib module for the specified form. If [[RETURN]] is
pressed in response to this prompt, the source code for this form will
not be generated and DICTCDE will reprompt for a file name. (The field
number tables will not be generated for the form either.)
After the copylib module has been defined for a form, DICTCDE issues the
following prompt:
Prefix for data items in formname>
Enter a prefix to be used in the COBOL identifier for the data items in
the form. The prefix you choose can be up to 8 characters long and must
begin with a letter to be a valid COBOL identifier. If you would like a
hyphen between the prefix and the data item name, be sure to include the
hyphen as part of the prefix you enter. (See Examples of Generated Code
later in this section for an example of data items generated with
prefixes.) When a prefix is assigned to a data item, that data item can
be referred to uniquely in a COBOL program without using the COBOL OF
clause.
If [[RETURN]] is pressed in response to this prompt, the source code for
the form is generated without a prefix assigned to the data items. The
code is echoed to the terminal as it is written to the copylib module.
After the source code has been generated for the form, DICTCDE will
return to the main prompt.
MPEF and MPER Files. If the specified file is defined in the Dictionary
as MPEF, DICTCDE will issue the following message:
File filename is an MPE file.
If the specified file is defined in the Dictionary as MPER, DICTCDE will
issue the following message:
File filename is an MPE relative file.
The next prompts issued by DICTCDE allow you to choose what COBOL program
sections are to be defined for the file. DICTCDE allows you to generate
source code for the ENVIRONMENT DIVISION and the DATA DIVISION of a COBOL
program.
Copylib module for SELECT statement>
Enter the copylib module for the code generated for the SELECT statement.
The SELECT statement identifies the file to be used in a program and is
part of the ENVIRONMENT DIVISION of a COBOL program. When a copylib
module is entered in response to this prompt, DICTCDE will then prompt
for the copylib module for the next program section. If [[RETURN]] is
pressed in response to this prompt, no SELECT statement will be
generated, and DICTCDE will continue to prompt for the copylib module for
the next program section.
Copylib module for FILE SECTION entry>
Enter the copylib module for the code generated for the FILE SECTION
entry. The FILE SECTION defines the file to be used in the program and
is part of the DATA DIVISION of the program. The record layout for the
file (the source code for the data items in the file) is defined in this
section. However, you may choose to generate the record layout for the
file in WORKING-STORAGE, instead of in the FILE SECTION. If a copylib
module is entered for the FILE SECTION, but you choose to generate the
record layout for the file in WORKING-STORAGE, the FD statement would
contain a single, 01-level definition. This definition is generated to
serve as a buffer for READs and WRITEs to the file. If a copylib module
is not entered for the FILE SECTION, the record definition for the file
may still be generated in WORKING-STORAGE.
If [[RETURN]] is pressed in response to this prompt, no FILE SECTION
entry will be generated and DICTCDE will continue to prompt for the
copylib module for the next program section. When a copylib module is
entered for the FILE SECTION, DICTCDE prompts for the following:
Define filename in FILE SECTION as an FD or SD file (F/S)>
Enter F to define filename as a data file. Enter S to define filename as
a sort file. If [[RETURN]] is pressed in response to this prompt,
filename will be defined as a data file.
Note that the FILE SECTION for an MPER file can only be generated as an
FD file. (Therefore, this prompt is not issued for MPER files.)
DICTCDE then issues the next prompt:
Copylib module for WORKING-STORAGE record>
Enter the copylib module for the WORKING-STORAGE record. The WORKING
STORAGE record will contain the record layout for the file. If a copylib
module was entered in response to the prompt for the FILE SECTION entry,
and [[RETURN]] is pressed in response to this prompt, the record layout
of the file will be defined in the FILE SECTION. If no copylib module was
entered in response to the prompt for the FILE SECTION entry, and
[[RETURN]] is also pressed in response to this prompt, no record layout
for the file will be generated.
If the copylib modules have been defined for either the FILE SECTION or
for WORKING-STORAGE, DICTCDE prompts for the following:
Prefix for data items in filename>
Enter the prefix to be used in the COBOL identifier for each data item in
the file. The prefix can be 8 characters maximum and must begin with a
letter to be a valid COBOL identifier. This prefix can be used to
uniquely identify the data items to the file. (See Examples of Generated
Code which is discussed later in this section for an example of data
items generated with prefixes.)
If [[RETURN]] is pressed in response to this prompt, the source code for
the file is generated without a prefix assigned to the data items. The
code is echoed to the terminal as it is written to the copylib module.
DICTCDE then returns to the main prompt.
KSAM Files. If the specified file is a KSAM file, DICTCDE will issue the
following message and prompts:
File filename is a KSAM file.
DICTCDE allows you to use KSAM files in two ways. First, you may use the
KSAM support provided by COBOL II. To do so, you would generate the
SELECT statement and FILE SECTION, but you would not generate the record
layout in WORKING STORAGE. Second, you may use the intrinsics supplied by
KSAM for use by COBOL. To do this, you would generate the record layout
in WORKING STORAGE to serve as a data buffer parameter to the KSAM
intrinsics, but you would not generate the SELECT statement or the FILE
SECTION entry.
The next prompts issued by DICTCDE allow you to choose what COBOL program
sections are to be defined for the file. DICTCDE allows you to generate
source code for the ENVIRONMENT DIVISION and the DATA DIVISION of a COBOL
program as it did for an MPE file.
Copylib module for SELECT statement>
Enter the copylib module for the code generated for the SELECT statement.
The SELECT statement identifies the file to be used in a COBOL program
and is part of the ENVIRONMENT DIVISION for the program. When a copylib
module is entered in response to this prompt, DICTCDE will then prompt
for the copylib module for the next program section. If [[RETURN]] is
pressed in response to this prompt, no SELECT statement will be generated
and DICTCDE will continue to the next prompt.
Copylib module for FILE SECTION entry>
Enter the copylib module for the code generated for the FILE SECTION
entry. The FILE SECTION defines the file to be used in the program and
is part of the DATA DIVISION for a program. The record layout for the
file (the source code for the data items in the file) is also defined in
this section. However, you may choose to generate the record layout for
the file in WORKING-STORAGE, instead of in the FILE SECTION. If a copylib
module is entered for the FILE SECTION, but you choose to generate the
record layout for the file in WORKING-STORAGE, the FD statement would be
generated as a single, 01-level definition. This definition is generated
to serve as a buffer for READs and WRITEs to the file. If a copylib
module is not entered for the FILE SECTION, the record definition for the
file may still be generated in WORKING-STORAGE.
If [[RETURN]] is pressed in response to this prompt, no FILE SECTION
entry will be generated and DICTCDE will continue to prompt for the
copylib module for the next program section.
Copylib module for WORKING-STORAGE record>
Enter the copylib module for the WORKING-STORAGE record. The
WORKING-STORAGE record will contain the record layout for the file. If a
copylib module was entered in response to the prompt for the FILE SECTION
entry and [[RETURN]] is pressed in response to this prompt, the record
layout of the file will be defined in the FILE SECTION. If no copylib
module was entered in response to the prompt for the FILE SECTION entry,
and [[RETURN]] is pressed in response to this prompt, no record layout
for the file will be generated.
When a copylib module is defined for the WORKING-STORAGE record for a
KSAM file, the following prompt is also issued by DICTCDE:
Include KSAM FILETABLE parameter (N/Y)>
Enter Y to generate the KSAM FILETABLE parameter for this file. The KSAM
FILETABLE parameter is useful if you use the intrinsics provided by KSAM
for COBOL, rather than the KSAM support provided by COBOL II.
When the copylib modules have been defined for either the FILE SECTION or
for WORKING-STORAGE, DICTCDE prompts for the following:
Prefix for data items in filename>
Enter the prefix to be used in the COBOL identifier for each data item in
the file. The prefix can be 8 characters maximum and must begin with a
letter to be a valid COBOL identifier. This prefix can be used to
uniquely identify the data items to the file. (See Examples of Generated
Code later in this section for an example of data items generated with
prefixes.)
If [[RETURN]] is pressed in response to this prompt, the source code for
the KSAM file is generated without a prefix assigned to the data items in
the file. The code is echoed to the terminal as it is written to the
copylib module.
After the source code has been generated for the KSAM file, DICTCDE will
return to the main prompt.
Generating Code for Elements
To generate source code for element definitions, enter E in response to
the main prompt.
DICTCDE will then prompt for the element name:
Element name>
Enter the name of the element to be extracted from the Dictionary. Only
one element may be extracted at a time. (You may not enter more than 1
element name in response to this prompt.) DICTCDE then prompts for the
copylib module for the source code for the specified element:
Copylib module for element name>
Enter the name of the copylib module for this element. If [[RETURN]] is
pressed in response to this prompt, no code will be generated for this
element and DICTCDE will return to the main prompt.
After the copylib module has been defined for the element, DICTCDE will
prompt for the following:
Prefix for data items in element name>
Enter the prefix to be used as the COBOL identifier for any child
elements this element may have. The prefix can be up to 8 characters
long and must begin with a letter to be a valid COBOL identifier. When a
prefix is assigned to a child element, that element can be uniquely
identified with its parent element. For example, for the parent element
RECORD1, the following code is generated if the prefix REC1- is entered
in response to this prompt:
000100
000200 01 RECORD1.
000300 05 REC1-FIELD1 PIC X(2).
000400 05 REC1-FIELD2 PIC X(8).
000500 05 REC1-FIELD3 PIC X(6).
If the specified element does not have any related child elements, the
prefix will be ignored. If [[RETURN]] is pressed in response to this
prompt, the code is generated without any prefixes assigned to the child
elements (if there are any). The code is echoed to the terminal as it is
written in the WORKING-STORAGE record.
Generating Code for Standard Parameters
DICTCDE allows you to generate source code for the IMAGE, VPLUS, and KSAM
standard parameters. To generate this source code, enter P in response
to the main prompt. The code for the standard parameters is generated in
WORKING-STORAGE.
DICTCDE will issue the following prompt:
Copylib module for IMAGE standard parameters>
Enter the copylib module for the code generated for the IMAGE standard
parameters. The IMAGE standard parameters include the DB-STATUS array
declaration, the eight MODE declarations, and the utility LIST
declarations. The code for the IMAGE standard parameters is echoed to
the terminal as it is written to the copylib module. (See Examples of
Generated Code later in this section for an example of the code generated
for the IMAGE standard parameters.) If [[RETURN]] is pressed in response
to this prompt, the IMAGE standard parameters will not be generated.
DICTCDE next prompts for the copylib module for the VPLUS parameters:
Copylib module for VPLUS standard parameters>
Enter the copylib module for the code generated for the VPLUS standard
parameters. The VPLUS standard parameters include the VPLUS COMAREA
definition and a character string which identifies the terminal. (The
terminal identification string is passed to the VPLUS intrinsic
VOPENTERM.) The code for the VPLUS standard parameters is echoed to the
terminal as it is written to the copylib module. (See Examples of
Generated Code later in this section for an example of the code generated
for the VPLUS standard parameters.) If [[RETURN]] is pressed in response
to this prompt, the VPLUS standard parameters will not be generated.
DICTCDE will next prompt for the KSAM standard parameters:
Copylib module for KSAM standard parameters>
Enter the copylib module for the code generated for the KSAM standard
parameters. The KSAM standard parameters are useful if you use the
intrinsics provided by KSAM for COBOL, rather than the COBOL II KSAM
support. These parameters include a general KSAM FILETABLE parameter and
a STAT parameter. The general FILETABLE parameter does not reference
any file name and can be used for any file with the appropriate
initialization. The STAT parameter contains STATUS-KEY-1 and
STATUS-KEY-2 for use with the KSAM COBOL intrinsics. The code for the
KSAM standard parameters is echoed to the terminal as it is written to
the copylib module. (See Examples of Generated Code later in this
section for an example of the code generated for the KSAM standard
parameters.) If [[RETURN]] is pressed in response to this prompt, the
KSAM standard parameters will not be generated.
After the code has been generated for the standard parameters, DICTCDE
returns to the main prompt.
Changing the DICTCDE Options
DICTCDE provides a set of options which allows you to change the
Dictionary used, the copylib used, and the DICTCDE defaults; and it
allows you to run the COBOL copylib editor, COBEDIT.
To change any of the options offered by DICTCDE, enter an O in response
to the main prompt. DICTCDE will then issue a series of prompts which
allow you to change any of the options. Each of the prompts displays the
value currently being used by DICTCDE in either of two ways. For some of
the prompts, the current value is shown within parenthesis as a single
value. For example, the current value for the following prompt is
DICT.PUB:
Dictionary name (DICT.PUB)>
For prompts which ask a choice to be made, the current value is also
within parenthesis. It is the value to the left of the slash. In this
example, the current value is Y (Yes):
List definitions on the terminal (Y/N)>
When O is entered in response to the main prompt, DICTCDE issues the
following message:
Press RETURN to retain current value and move to the next option.
The following is a list of all the prompts which are used to change the
values for the options and a brief explanation of each of them. (A more
detailed explanation for each of these prompts follows the list.)
Dictionary name (current allows you to change the Dictionary from which
Dictionary)> you extract definitions.
Copylib file name allows you to change the copylib for the
(current copylib)> generated code.
Run COBEDIT (N/Y)> allows you to run the copylib editor, COBEDIT,
from within DICTCDE.
List definitions on the allows you to suppress the generated code from
terminal (Y/N)> being displayed on the terminal.
Comment the definitions allows you to generate comment lines for the
(N/Y)> extracted entities.
Use Primary name or allows you to use the aliases for the extracted
Alias COBOL identifier entities.
(P/A)>
Qualify data sets and allows you to use the name of the database or
forms with their parent forms file as the prefix for the data set or
files (N/Y)> form.
Use edit mask for allows you to create display fields from items
PICTURE clause (Y/N)> in the Dictionary that have edit masks.
Prompt for record data allows you to suppress the prompts for prefixes
item prefixes (Y/N)> for data items.
Prompt for all sections allows you to suppress the prompts for the
of MPE/KSAM definitions ENVIRONMENT DIVISION and FILE SECTION.
(Y/N)>
Prompt for VPLUS field allows you to suppress the prompts for
types and number tables selecting the VPLUS field types and the VPLUS
(Y/N)> field number tables.
DICTCDE will then issue the first option:
Dictionary name (current dictionary)>
Enter the Dictionary name, group and account to be opened and used for
further code generation. DICTCDE displays the current Dictionary being
used in (current dictionary). Data and file definitions are extracted
from the new Dictionary specified until this option is changed again.
When a new Dictionary name is specified, DICTCDE will also issue the
following prompt:
Dictionary password>
Enter the Dictionary password for the new Dictionary to be used. If the
new Dictionary specified is the same as the previous Dictionary, the
password prompt will not be issued. If [[RETURN]] is pressed in response
to this option, the Dictionary used will not change and DICTCDE will
continue to the next option as follows:
Copylib file name (current copylib)>
Enter the copylib file name (35 characters maximum) to be opened and used
for further code generation. DICTCDE displays the current copylib file
being used in current copylib. If the new copylib file already exists,
DICTCDE will open that copylib file and append any further source code
generated to the contents of that file. If the specified copylib file
name exists, but it is not in KSAM copylib format, DICTCDE will issue an
error message and reprompt for the copylib file name. If the specified
file name does not exist, DICTCDE will issue the following prompt:
File filename does not exist, create it (N/Y)>
If N is entered in response to this prompt, DICTCDE will reprompt for the
copylib file name. If Y is entered in response to this prompt, DICTCDE
will prompt for the key file name for the new KSAM copylib to be created:
Key file name>
Enter the key file name for the new copylib file (8 characters maximum).
If [[RETURN]] is pressed in response to this prompt, DICTCDE will
reprompt for the copylib file name.
Once a new copylib is accepted, or if [[RETURN]] is pressed in response
to the copylib file option prompt, DICTCDE would continue to the next
option as follows:
Run COBEDIT (N/Y)>
Enter Y to run the copylib editor COBEDIT from within DICTCDE. DICTCDE
will then close the current copylib file being used and invoke COBEDIT
for you. (For information on running COBEDIT, see the COBOL II Reference
Manual.) When you exit COBEDIT, DICTCDE will reopen the copylib file and
continue prompting for the next option.
If N is entered or [[RETURN]] is pressed in response to the COBEDIT
option prompt, DICTCDE will also prompt for the next option as follows:
List definitions on the terminal (Y/N)>
Enter N to suppress the generated code from being displayed at the
terminal (or printed in the job listing if DICTCDE is run from within a
job stream). Enter Y to echo the source code as it is generated to the
terminal (or printed in the job listing). If [[RETURN]] is pressed in
response to this option prompt, DICTCDE will continue to the next option.
Comment the definitions (N/Y)>
Enter Y to generate comment lines which describe the entities extracted
from the Dictionary. These comment lines are written to WORKING-STORAGE,
at the end of any other code generated for an entity. These comment
lines include the following information about the extracted entity:
entity the name of the entity extracted from the
Dictionary.
entity-name the entity long-name (as it was specified in
DICTDBM).
entity-resp the name of the person, department, or area
responsible for the integrity of the entity.
date-change the date of the latest change made to the
entity in the Dictionary.
date-create the date the entity was created in the
Dictionary.
identity-change the identity of the person, department, or area
who made the last change to the entity in the
Dictionary.
identity-create the identity of the person, department, or area
who created the entity in the Dictionary.
For example, the following code is generated as comments for the MPE file
ACCOUNT:
000100
000200* file : ACCOUNT
000300* file-name : CUSTOMER ACCOUNTS
000400* file-resp : MANAGER
000500* date-change : 83/11/01
000600* date-create : 83/11/15
000700* identity-change : MGR
000800* identity-create : MGR
Enter N in response to this prompt to suppress the comment lines from
being generated and to continue to the next prompt. If [[RETURN]] is
pressed in response to this prompt, DICTCDE will also continue to the
next option:
Use Primary name or Alias for COBOL identifier (P/A)>
Enter P to extract the Dictionary primary name to be used as the COBOL
identifier for an entity when code is generated. Enter A to extract the
Dictionary alias (whenever an alias is defined in the Dictionary) to be
used as the COBOL identifier for an entity when code is generated. Using
aliases as COBOL identifiers identifies the child entities by the names
that are known by the parent entities. Regardless of whether the primary
names or aliases are used as the COBOL identifiers, the constants used
for passing data set and search item names to IMAGE will be generated
using the aliases (if the aliases have been defined in the Dictionary).
If [[RETURN]] is pressed in response to this prompt, DICTCDE will
continue to the next option:
Qualify data sets and forms with their parent files (N/Y)>
Enter Y to use the parent file as a prefix in the COBOL identifier
generated for the data sets or forms. When generating code for a
database or forms file, DICTCDE allows you to qualify the related IMAGE
data sets or VPLUS forms by the name of the parent file. DICTCDE will
use the parent file name as a prefix in the COBOL identifier generated
for the related data sets or forms. This will help you to differentiate
between data sets and forms with common names. DICTCDE will also qualify
single data sets or forms by their parent file name, if the parent file
was specified, when the data set or form was extracted from the
Dictionary. (The parent file was entered in parenthesis next to the file
name in response to theFile name prompt.)
Note that if the prefixes, file name and suffixes in the COBOL identifier
total more than 30 characters, DICTCDE will truncate the COBOL identifier
to the allowable 30 characters. DICTCDE will truncate the suffix first,
then the prefix, so that the identifier does not exceed 30 characters.
Enter N if you do not wish to add the parent file name as a prefix in the
COBOL identifiers generated for data sets and VPLUS forms. If [[RETURN]]
is pressed in response to this prompt, DICTCDE will continue to the next
option:
Use edit mask for PICTURE clause (Y/N)>
Enter Y to generate display fields for the elements defined with edit
masks in the Dictionary. DICTCDE will convert the edit mask in the
Dictionary to a COBOL PICTURE clause. When code is generated for
elements with edit masks, the storage length is computed from the size of
the edit mask, not from the storage length information in the Dictionary.
However, the storage length is changed when the code is generated. For
entities which contain child elements with edit masks, the record layout
for the parent entity is also changed. Therefore, the byte offsets for
the elements with edit masks must be defined in the Dictionary according
to the edit mask size, not by the data storage requirements, if you wish
to use this option. (For more information on the code generated for edit
masks, see Edit Masks discussed under Examples of Generated Code later in
this section.)
Enter N to ignore any edit masks defined for the elements. The PICTURE
clause for an element will then be generated from the data type and
storage length defined in the Dictionary.
If [[RETURN]] is pressed in response to this prompt, DICTCDE will
continue to the next option:
Prompt for record data item prefixes (Y/N)>
Enter N to suppress the prompts asking for prefixes for the record data
items. Enter Y to have the prompts issued for data item prefixes
wherever DICTCDE normally issues them. If [[RETURN]] is pressed in
response to this prompt, DICTCDE will continue to the next option:
Prompt for all sections of MPE/KSAM definitions (Y/N)>
Enter N to suppress the prompts for the copylib modules for the SELECT
statement and the FILE SECTION entry for an MPEF, MPER, or KSAM file.
(Only the copylib for the WORKING-STORAGE record will be prompted for.)
Enter Y to prompt for the copylib modules for the SELECT statement, FILE
SECTION entry, and WORKING-STORAGE record for an MPEF, MPER, or KSAM file
as DICTCDE normally issues them.
If [[RETURN]] is pressed in response to this prompt, DICTCDE will
continue to the last option as follows:
Prompt for VPLUS field types and number tables (Y/N)>
Enter N to suppress the prompts for the VPLUS field types (PIC 9 or PIC
X) and for the VPLUS field number tables for the forms files and forms
extracted from the Dictionary. If these prompts are not issued, all the
forms extracted from the Dictionary will be generated without field
number tables, and the numeric fields in the forms will be generated as
PIC 9 numeric fields.
When a response is made, or [[RETURN]] is pressed in response to this
prompt, DICTCDE will reissue the main prompt.