The standard options are discussed in the following text.
By default the Dollar ($) option is reset. When the Dollar ($) option is set, all compiler control cards are listed. This option appears as $ SET $, $ $, or LISTDOLLAR.
ALIGNMENT Option
By default the ALIGNMENT option is reset. When the ALIGNMENT option is set, a DASDL warning message is generated for structures whose blocks are not aligned on multiples of 60-word boundaries. Warnings are generated whenever the database is generated or updated. The following text is the warning message:
WARNING: <structure name> is not
aligned for 60 word blocking.
This will impair performance if the
structure is allocated on a VSS-2 device.
By default the ALLINFO option is reset. When the ALLINFO option is set or reset, the DECKLIST, FILE, LAYOUT, STRUCTURE, and TEXT options are automatically set or reset.
ALWAYSBUMPLEVEL Option
By default the ALWAYSBUMPLEVEL option is reset. This feature is intended to aid in tracking changes between DASDL source compilations. When the ALWAYSBUMPLEVEL option is set the database update level will increase every time an update is compiled, regardless of the nature of the update. The ALWAYSBUMPLEVEL option is disallowed for model databases.
| Note: | The AUTOREORG option is no longer commonly used. The option was available for users migrating from V Series systems to MCP-based systems. |
By default the AUTOREORG option is reset. When the AUTOREORG option is set, any required reorganization is automatically performed. If no reorganization is required, the AUTOREORG option is ignored.
When the AUTOREORG option is set during a DASDL update compilation and a reorganization is required, the DASDL compiler creates a file containing BUILDREORG instructions for creating the reorganization program. The file is named <database usercode>/DMAUTOREORG/<database name>/<control file level>. The file is located on same pack as the control file.
When the AUTOREORG option is set, DASDL runs the correct WFL job to perform the necessary operation. If the ZIPFILE option is included, it indicates the WFL job that is started. If the ZIPFILE option specifies the incorrect WFL job for the operation, a syntax error occurs.
The WFL job DATABASE/WFL/AUTOREORG is included on the Enterprise Database Server release tapes. DATABASE/WFL/AUTOREORG is automatically initiated by the DASDL compiler if the AUTOREORG and the ZIP options are set and a reorganization is required. DATABASE/WFL/AUTOREORG compiles the Enterprise Database Server software and monitors the compiling of the DMSUPPORT and RECONSTRUCT libraries. When these libraries have successfully compiled, DATABASE/WFL/AUTOREORG starts the reorganization process. SYSTEM/BUILDREORG is initiated and the Reorganization program is compiled and initiated. When the Reorganization program has finished, the DMAUTOREORG file is removed.
DATABASE/WFL/AUTOREORG has seven parameters. The first string parameter identifies everything the DATABASE/WFL/COMPILEACR string parameter does except for Enterprise Database Server software titles. The second, third, fourth, and fifth string parameters identify Enterprise Database Server software titles, one title for each parameter. Available software titles are ACCESSROUTINES, DMSUPPORT, RECONSTRUCT, and RMSUPPORT. The sixth parameter supplies the Reorganization program name. The seventh parameter is optional and contains the DATAPATH string for a permanent directory database. For more information on these parameters and on DATABASE/WFL/COMPILEACR, refer to the Enterprise Database Server Utilities Operations Guide.
If you need to supply additional commands to SYSTEM/BUILDREORG (for example, COPY, ORDERED BY, or SEQUENCE commands), reset the ZIP option. When the AUTOREORG option is set and the ZIP option is reset, the DMAUTOREORG file is created, but the DATABASE/WFL/AUTOREORG job is not initiated.
By default the COBOL74 option is reset. When the COBOL74 option is set, a warning is issued for items that are declared as real items. The COBOL74 option also issues a warning for items whose names are COBOL74 reserved words.
DATASETLIMIT1500 Option
By default, the DATASETLIMIT1500 option is reset. When the DATASETLIMIT1500 is set, the maximum number of data sets allowed by the DASDL compiler is increased to 1500. This option does not affect databases with a maximum data set limit greater than 1500.
By default the DEBUG option is reset. The DEBUG option is an internal debugging aid. When the DEBUG option is set, the DASDL compiler produces additional line printer output which is used during compiler development.
A job file is automatically initiated to compile the Accessroutines and other software. By default, the DECKLIST option is reset. When the DECKLIST option is set, the parameters to this job file are listed.
This listing is also produced if the TEST option is set.
By default the DELETE option is reset. When the DELETE option is set, all input from the TAPE file, with the exception of compiler control options, is ignored. Input from the TAPE file is neither written to the NEWTAPE file nor listed on the line printer.
CARD file input continues to be processed and compiled. The DELETE option can be reset only from the CARD file.
DMCONTROL Option
By default the DMCONTROL option is set. When the DMCONTROL option is set, the DASDL compiler automatically initiates the SYSTEM/DMCONTROL program following an error-free compilation. SYSTEM/DMCONTROL creates or updates the database control file. If the initialize statement is specified and the ZIP compiler control option is set, the DMCONTROL option is ignored and the control file is updated.
When the DMCONTROL option is reset, SYSTEM/DMCONTROL is not initiated automatically and it must be run manually to create or update the control file.
The ERROR LIMIT (or ERRORLIMIT) option controls the number of syntax errors the DASDL compiler allows before terminating the compilation.
The compilation is terminated if the number of errors equals or exceeds the designated integer. An ERROR LIMIT of 0 allows any number of errors.
The default ERROR LIMIT value is 10 for compilations initiated through CANDE, and 100 otherwise.
By default the FILE option is reset. When the FILE option is set, storage requirements, file sizes, and physical characteristics for each structure are listed on the line printer.
The information listed by the DASDL compiler for each structure consists of the following:
-
File title and pack family
-
BUFFERS specification
-
Options including ADDRESSCHECK, CHECKSUM, and so on
-
RECORDSIZE and BLOCKSIZE attributes for data sets
-
Key entry size and TABLESIZE attributes for sets and subsets
-
SUBBLOCKSIZE attribute for ordered data sets
-
MODULUS attribute for random data sets and index random sets and subsets
-
Wasted space for each block or table
-
LOADFACTOR attribute for sets and subsets
-
AREAS, AREASIZE, and POPULATION attributes
Note: If the POPULATION attribute is included in DASDL, the specified value is printed as the population of the data set even though that might not be the same as the actual population, which is based on the AREAS and AREASIZE attributes. Otherwise, the population that is printed is based on the AREAS and AREASIZE attributes.
This listing is also produced if the STORE option is set.
HEADER Option
By default the HEADER option is reset. When the HEADER option is set and the LIST option is reset, only the standard header information and a compilation summary is listed. Source input is not listed.
By default the INCLNEW option is reset. When the NEW and INCLNEW options are set, included text is written to the NEWTAPE file in place of the INCLUDE option statement.
When the NEW option is set and the INCLNEW option is reset, included text is not written to the NEWTAPE file; however, $INCLUDE statements with the dollar sign ($) in column 2 are written to the file.
If the NEW option is reset, the INCLNEW option is ignored.
The INCLUDE option cannot be set or reset.
The INCLUDE option permits source language input from files other than the CARD and TAPE files. Each INCLUDE option specifies the title of the input file in double quotation marks (") and indicates which portion of the file is to be included. The included card images are compiled in place of the INCLUDE option. INCLUDE options can appear anywhere in the input. INCLUDE options must not be nested; that is, included input must not contain INCLUDE options.
The file name specifies the title of the file to be used as input. The base and limit specifications indicate which portion of the file is to be included. Base specifies the sequence number of the first card image to be included. Limit specifies the sequence number of the last card image to be included. If no base is stipulated, inclusion begins with the first record in the file. If no limit is indicated, then the last record of the file is the last record included. When neither is specified, the entire file is included.
Included input must have the same record size and format as the CARD file. Base and limit should only be used on properly sequenced files.
INITIALIZENEW Option
| Note: | The INITIALIZENEW option is no longer commonly used. This option was available for users migrating from V Series systems to MCP-based systems. |
Use the INITIALIZENEW option to automatically initialize newly added structures. By default the INITIALIZENEW option is reset. New disjoint data sets and their related structures that were added during the DASDL update compilation are initialized when the following conditions are met:
-
The INITIALIZENEW option is set.
-
The ZIP and DMCONTROL options are set.
-
No reorganization of the database is required as a result of the DASDL compilation.
If the preceding conditions are met, DASDL creates a file containing DMUTILITY INITIALIZE parameters. The name of this file is
<database\usercode>)DMINITIALIZE/
<database name>/<control file update level>The file is located on the same pack as the control file. DASDL then instructs SYSTEM/DMCONTROL to update the control file, and instructs the DATABASE/WFL/COMPILEDB job or the DATABASE/WFL/AUTOREORG job to run SYSTEM/DMUTILITY. SYSTEM/DMUTILITY initializes those structures specified in the DMINITIALIZE file, and the WFL job removes the DMINITIALIZE file. For more information about DATABASE/WFL/COMPILEDB, refer to the Enterprise Database Server Utilities Operations Guide. For more information about DATABASE/WFL/AUTOREORG, refer to the discussion of the AUTOREORG option earlier in this appendix.
The INITIALIZENEW option can be used instead of the INITIALIZE statement if the compilation is not an UPDATE compilation, and the ZIP and DMCONTROL options are set. In that case, the entire database is initialized, and a DMINITIALIZE file is not created.
By default the LAYOUT option is reset. When the LAYOUT option is set, items and key item offsets and sizes are listed on the line printer. The offsets provided by the LAYOUT option are for the memory record layout format. The data in an audit is in disk record layout format. Offsets for items other than key items might differ between the memory and disk record layout formats.
This listing is also produced if the TEST option or the STORE option is set.
By default the LIST option is set except for compilations initiated from CANDE, in which case the LIST option is reset. When the LIST option is set, source input is listed on the line printer. When the LIST option is reset, only syntax errors are listed.
By default the LISTDOLLAR option is reset. When the LISTDOLLAR option is set, all compiler control cards are listed. This option appears as $ SET $, $ $, or LISTDOLLAR..
By default the LISTP option is reset. When the LISTP option is set, CARD input is listed while TAPE input is not listed. The LISTP option is ignored when the LIST option is set.
By default the MERGE option is reset. When the MERGE option is set, input from the CARD file is merged with input from the TAPE file. If a CARD record has the same sequence number as a TAPE record, the CARD record replaces the TAPE record.
When the MERGE option is reset, only the CARD file is used as input.
The MIGRATEDB option allows you to dynamically add or delete one or more disjoint data sets and their spanning sets and subsets without bringing down the database. This feature does not support adding sets or subsets to an existing data set, continue to use reorganization.
You can dynamically add a data set in one step with specific DASDL options set, or complete it in multiple steps with specific DASDL options reset.
To perform this task automatically, perform the following steps:
-
Add new disjoint data set(s) to the DASDL.
-
Specify SET MIGRATEDB, ZIP and DMCONTROL DASDL options.
-
Perform a DASDL UPDATE compilation.
The DASDL UPDATE compile performs the following steps:
-
Creates backup copies of the current description file and the DMSUPPORT library.
-
Updates the description file.
-
Initiates DATABASE/ WFL/COMPILEDB. This WFL performs the following tasks:
-
Compiles a new DMSUPPORT Library.
-
Compiles a new RECONSTRUCT program.
-
Runs DMUTILITY with the MIGRATEDB command. Refer to the Enterprise Database Server Utilities Operations Guide for additional information about the MIGRATEDB command.
-
Runs SYSTEM/DMCONTROL to update the control file.
-
Using the automated procedure is recommended since it requires less manual steps and will encounter fewer configuration errors. You can break this procedure up in multiple steps and perform these steps at different times.
To perform this task manually, perform the following steps:
-
Add new data set(s) to the DASDL.
-
Specify the RESET ZIP and DMCONTROL DASDL options. The MIGRATEDB DASDL option can be SET or RESET for a manual MIGRATEDB, however, make sure the MIGRATEDB parameter for DATABASE/WFL/COMPILEDB is TRUE.
-
Perform a DASDL UPDATE compilation. This backs up the existing description file and creates a new description file.
-
Determine the correct DMSUPPORT library title for step 6. You will need to know the current control file update level +1. To determine this, perform a DMUTILITY WRITE on the control file and the control file update level is specified in the report. For example, if the current control file update level is 44, the DMSUPPORT library title will be DMSUPPORT/<database name>/45.
-
Ensure that your FAMILY DISK setting is correct.
-
Start DATABASE/WFL/COMPILEDB with the following parameters:
-
String parameter, DB statement
-
String parameter, ACR name/location
-
String parameter, DMSUPPORT name/location
-
String parameter, RECONSTRUCT name/location
-
String parameter, RMSUPPORT name/location
-
String parameter, DMUTILITY name/location
-
String parameter, path name
-
Boolean parameter, MIGRATEDB option, pass TRUE
-
Boolean parameter, XL database, TRUE/FALSE
-
For example:
START DATABASE/WFL/COMPILEDB("DB=(ABC)DB1 AUDIT=SET CF=APACK",
ACR = *SYSTEM/ACCESSROUTINES ON SYS571",
"DMSUPPORT = (ABC)DMSUPPORT/DB1/45 ON APACK",
"RECONSTRUCT= (ABC)RECONSTRUCT/DB1 ON APACK",
"",
"DMUTILITY=*SYSTEM/DMUTILITY",
"",
TRUE,
FALSE)You might receive the following warning:
10156000 INITIALIZE, ACRTITLE, ACRPACK,UTILPACK,
*
WARNING: USE OF PREDEFINED WORD COULD CAUSE UNEXPECTED RESULTS By default, the MIGRATEDB option is reset.
MIGRATEDB Actions based on DASDL Compiler Options
|
MIGRATEDB |
DMCONTROL |
ZIP |
Result |
|---|---|---|---|
|
SET |
SET |
SET |
Automatic MIGRATEDB |
|
SET |
SET |
RESET |
MIGRATEDB not supported |
|
SET |
RESET |
SET |
MIGRATEDB not supported |
|
SET |
RESET |
RESET |
Manual MIGRATEDB |
|
RESET |
SET |
SET |
MIGRATEDB not supported |
|
RESET |
SET |
RESET |
MIGRATEDB not supported |
|
RESET |
RESET |
SET |
MIGRATEDB not supported |
|
RESET |
RESET |
RESET |
Manual MIGRATEDB |
-
The MIGRATEDB option only supports disjoint data sets.
-
The MIGRATEDB option is not allowed for modeled databases.
-
The MIGRATEDB command is not supported for databases that have Remote Database Backup enabled.
-
The data set cannot be a restart data set or global data set.
-
The data set cannot contain a link item or a structure of a link item.
-
The data set cannot contain an embedded structure.
By default the NEW option is reset. When the NEW option is set, the updated symbolic file NEWTAPE is created. This file can be used as the TAPE input file during subsequent compilations.
The user can control which records are written to the NEWTAPE file by selectively setting and resetting the NEW and INCLNEW options. These options can be set or reset at any point in the input. Compiler control card images are only written to the new symbolic file if they contain a dollar sign ($) in column 2.
The NEWTAPE file is created whether syntax errors are present in the input.
By default the OMIT ($) option is reset. When the OMIT option is set, input from both the CARD and TAPE files is ignored except compiler control statements. Compiler control statements with the dollar ($) character in either column 1 or column 2 are recognized even if the OMIT option is set. Those with the dollar ($) character in column 3 are ignored. The omitted records are written to the NEWTAPE file if the NEW option is set, and to the LINE file if the LIST option is set; but the omitted statements are not compiled. Omitted records are denoted by the word OMIT on the listing.
A syntax error occurs if the dollar ($) character appears in a column other than 1, 2, or 3.
The PAGE option cannot be set or reset. If the LIST or LISTP option is set, the PAGE option causes the printer to skip to the top of a new page.
By default the RPG option is reset. The RPG option allows the checking of a DASDL source file for compatibility with the RPG user language interface to Enterprise Database Server databases. The RPG option can be set ($SET RPG), reset ($RESET RPG), or popped ($POP RPG) anywhere in the DASDL source file.
The RPG user language interface imposes the following restrictions:
-
The scale factor for real and number items cannot exceed 9 digits.
-
Data set identifiers cannot exceed 8 characters.
-
Other types of identifiers cannot exceed 6 characters, except that the database name can have a maximum of 17 characters.
-
Key item identifiers must be unique within the set of all identifiers.
-
Structure identifiers must be unique within the set of all identifiers.
-
Identifiers beginning with TAB must not occur.
The first eight restrictions listed in the preceding list are limitations inherent to the RPG language that cannot be circumvented. Therefore, if the RPG option is set and any of the first eight restrictions are detected in the DASDL source, error messages are generated. The last three restrictions, however, can be circumvented in the RPG language by not invoking global data or sets containing key data, and by renaming any data items that begin with TAB. Therefore, if the RPG option is set and any of the last three restrictions are detected in the DASDL source file, warning messages are generated.
Checking for these restrictions occurs when an item or structure is declared, but not when the item or structure is later referenced. For example, setting the RPG option only around a set declaration does not cause attribute checking for any key items or key data items, but does cause checking for the presence of key data.
To affect attribute checking for items, or the uniqueness of identifiers, the RPG option must be set around the data set or remap description that corresponds to the items. For example, in logical database declarations, setting the RPG option only around the logical database description does not cause checking of the data sets, remaps, or sets named. The RPG option must be set around each of these structures to affect checking.
By default the SEQUENCE option is reset. When the SEQUENCE is set, both the printed output and the NEWTAPE file are resequenced. The SEQUENCE option is effective only when the LIST or NEW options are also set.
When the SEQUENCE option is set and no sequence base and sequence increment are specified, sequencing begins at 1000 and continues in increments of 1000. The default action can be overridden by specifying a 1‑digit to 8‑digit sequence base and sequence increment. If a sequence base is given, but no sequence increment is specified, sequencing begins at the sequence base and continues in increments of 1000. If a sequence increment is specified, but no sequence base is given, sequencing begins at 1000 and the specified increment is used.
When the SEQUENCE option is reset, the original input sequence numbers are retained.
By default the SEQERR option is reset. When the SEQERR option is set, sequence errors in the input TAPE file are flagged as syntax errors. If sequence errors are detected, the description file is not locked and SEQUENCE ERROR messages appear on the listing.
SINGLE Option
By default the SINGLE option is reset. When the SINGLE option is set, printer output is single spaced; otherwise, output is double spaced.
By default the STORE option is reset. When the STORE option is set, the physical attributes of all database structures are listed. The information listed includes the areas, area size, block size, and so on.
By default the STRUCTURE option is reset. When the STRUCTURE option is set, structures are listed in hierarchical order. Associated data sets, sets, Accesses, and remaps are grouped together.
SYMBOLIC Option
The SYMBOLIC option cannot be set or reset. The SYMBOLIC option enables the user to specify the name of the database symbolic file used to compile the Accessroutines if designated in the ZIP deck.
SYMBOL/ACCESSROUTINES can be used as the default.
By default the TEST option is reset. When the TEST option is set, the following information is listed:
-
Depending on the type of data set record, either the disk record format or the working storage layout for each data set record
-
The ALGOL text used to tailor the Accessroutines
-
The order in which structures in the Accessroutines are to be compiled
-
The parameters to the job file that are automatically initiated to compile the Accessroutines and other software
By default the TEXT option is reset. When the TEXT option is set, all source statements generated by the DASDL compiler which are included in the Accessroutines are listed.
This listing is also produced if the TEST option is set.
The UDMLOAD option loads the Enterprise Database Server database schema in the repository. If the database schema being loaded already exists in the repository, a warning message appears. If you choose to continue, the database schema is replaced. The relationship between the application program and the original schema is deleted.
This option can be set during a DASDL update or standard compilation. The UDMLOAD option cannot be set if the UDMUPDATE option is set.
The loading is initiated by the DATABASE/WFL/UDM job using a stream file created by the DASDL compiler. The DATABASE/WFL/UDM job is automatically started by the DASDL compiler unless the UDMZIP option is reset. The stream file is called
UDM/<database name>/<YYYYMMDDhhmm>/LOAD/"SCRIPT.TXT")
The YYYYMMDDhhmm variable represents the compilation date and time. This stream file is removed after the schema is loaded, unless the UDMSAVEFILE option is set.
The UDMREPORT option generates from the repository a report of programs affected by the DASDL update process. This option can be set only during a DASDL update compilation.
If the UDMREPORT option is specified without the UDMUPDATE option, then only a syntax compilation is allowed.
The report generation is initiated by the DATABASE/WFL/UDM job using the stream file created by the DASDL compiler. The DATABASE/WFL/UDM job is automatically started by the DASDL compiler unless the UDMZIP option is reset. The stream file is called
UDM/<database name>/<YYYYMMDDhhmm>/REPORT/"SCRIPT.TXT"
The YYYYMMDDhhmm variable represents the compilation date and time. This stream file is removed after the report is generated, unless the UDMSAVEFILE option is set.
The UDMSAVEFILE option is reset by default. This option can be set to save the stream files from being automatically removed after the DATABASE/WFL/UDM job runs successfully.
The UDMUPDATE option updates the Enterprise Database Server database schema in the repository.
This option can be set only in a DASDL update compilation. The UDMUPDATE option cannot be set if the UDMLOAD option is set.
The update is initiated by the DATABASE/WFL/UDM job using the stream file created by the DASDL compiler. The DATABASE/WFL/UDM job is automatically started by the DASDL compiler unless the UDMZIP option is reset. The stream file is called
UDM/<database name>/<YYYYMMDDhhmm>/UPDATE/"SCRIPT.TXT"
The YYYYMMDDhhmm variable represents the compilation date and time. This stream file is removed after the schema is updated, unless the UDMSAVEFILE option is set.
The UDMZIP option is set by default. The DATABASE/WFL/UDM job is included on the Enterprise Database Server release media. If the UDMZIP option is set, the DATABASE/WFL/UDM job is automatically started by the DASDL compiler. The job is started if UDMLOAD, UDMUPDATE, or UDMREPORT is set; there are no syntax errors; and there is information to load, update, or report.
The UDMZIP option can be reset to suppress the automatic start-up of the DATABASE/WFL/UDM job. This job can be manually started as follows:
START DATABASE/WFL/UDM ("DASDL","<file 1>","<file 2>")The <file 1> variable is the name of the stream file from the UDMUPDATE or UDMLOAD option. The <file 2> variable is the name of the stream file from the UDMREPORT option. Either <file 1> or <file 2> can be null, but at least one file must be specified.
The report is generated before the schema is loaded or updated
The DATABASE/WFL/UDM job does not provide specifications that control aspects of the job when it is run. If there are special requirements when running this WFL job, examine the requirements and consider setting the following job options:
-
Class specification
-
Family specification
-
Usercode specification
-
Fetch specification
-
Job attribute assignment
The job DATABASE/WFL/UDM contains an include file called DATABASE/WFL/UDM/CONFIG. This file contains server configuration information that you need to maintain. This includes the name of the repository, the name of the server directory (where the script file is to be copied and used), the Internet Protocol (IP) address of the server, the UREPTIMEOUT parameter value, the usercode and password for the File Transfer Protocol (FTP), and the usercode and password for the repository.
The default value for UREPTIMEOUT is 600 seconds. This parameter controls the amount of time the UDMUTILITY program waits for the load, update, or report activities. If this time is exceeded, the UDMUTILITY program returns a timeout error. You can increase this value if the database or program is too large, and needs more than 600 seconds of elapsed time.
The UDMUTILITY program creates files that indicate whether the repository has successfully loaded after the DASDL and COBOL compilation. You can check the presence of these files in the WFL job that compiles the DASDL and COBOL programs.
When a DASDL compilation is performed with the UDMREPORT option set, one of the following files is created:
UDM/<database name>/REPORT/SUCCESS UDM/<database name>/REPORT/FAILED
When a DASDL compilation is performed with the UDMLOAD/UDMUPDATE option set, one of the following files is created:
UDM/<database name>/TRACK/SUCCESS UDM/<database name>/TRACK/FAILED UDM/<database name>/TRACK/WARNED
| Note: | When the WARNED file is created, the DATABASE/WFL/UDM job might require user input to continue.When a COBOL compilation is performed, one of the following files is created:UDM/<program identifier>/SUCCESS UDM/<program identifier>/FAILED |
Examples
The following example loads the database schema in the repository:
START DATABASE/WFL/UDM
("DASDL",
"UDM/PAYROLLDB/1999030518252/LOAD/""SCRIPT.TXT""",
"",
);The following example generates a report of affected programs and then updates the database schema in repository:
START DATABASE/WFL/UDM
("DASDL",
"UDM/PAYROLLDB/199903051852/UPDATE/""SCRIPT.TXT""",
"UDM/PAYROLLDB/199903051852/REPORT/""SCRIPT.TXT"""
);
The VERSION option cannot be set or reset. The VERSION option enables the user to specify an initial version number or to replace or increment an existing version number.
Version is a 2‑digit unsigned integer; cycle and patch are 3‑digit unsigned integers.
The VERSION option is initially inserted in the DASDL symbolic file by setting the NEW option and including a VERSION statement with the dollar sign ($) in column 2 of the CARD input file. During subsequent compilations, the version can be updated by setting the MERGE and NEW options and including a VERSION statement in the CARD file.
Two techniques are available for updating the VERSION card. When plus (+) signs precede the version and cycle numbers in the CARD file, the existing cycle and version numbers in the TAPE file are incremented by the specified values. When plus signs are not specified, the version information from the CARD file replaces the existing version information. In either case, the updated VERSION card is written to the new symbolic file.
The VERSION option in the CARD file must have a lower sequence number than that in the TAPE file. If more than one VERSION option appears in the CARD file, the one with the highest sequence number is used.
Patch numbers are optional. The new patch number is the patch number in the CARD file, if any; otherwise, it is the patch number in the TAPE file. If neither VERSION option contains a patch number, the patch number is omitted in the new symbolic file.
By default the VOIDT option is reset. When VOIDT is set, all input from the TAPE file, with the exception of compiler control cards, is ignored. Input from the TAPE file is neither written to the NEWTAPE file nor listed on the line printer.
CARD input continues to be processed and compiled. The VOIDT option can only be reset from the CARD file.
By default the WARNING option is reset. When WARNING is set, a warning message is issued for each identifier which is a COBOL reserved word.
By default the ZIP option is set. A WFL job, DATABASE/WFL/COMPILEDB, is included on the Enterprise Database Server release media. DATABASE/WFL/COMPILEDB is automatically initiated by the DASDL compiler if the compiler control option ZIP is set in the DASDL source. The function of this WFL job is identical to DATABASE/WFL/COMPILEACR except that it accepts six string parameters. The first string parameter identifies everything the DATABASE/WFL/COMPILEACR string parameter does except for Enterprise Database Server software titles. The second through fifth strings are used to identify Enterprise Database Server software titles (one title for each parameter). Currently, the software titles that can be chosen are ACCESSROUTINES, DMSUPPORT, RECONSTRUCT, and RMSUPPORT. The sixth parameter is optional, and if it is included, it is DATAPATH.
Both DATABASE/WFL/COMPILEACR and DATABASE/WFL/COMPILEDB can be used to compile Enterprise Database Server software. If DATABASE/WFL/COMPILEACR is used, the string parameter cannot exceed 256 characters. If DATABASE/WFL/COMPILEDB is used, a null string ("") is required for each program that is not being compiled. DATABASE/WFL/COMPILEACR is the recommended job to use when manually compiling the Enterprise Database Server software.
If the ZIP option is set and no syntax errors are detected, the DASDL compiler automatically initiates a WFL file titled DATABASE/WFL/COMPILEDB to compile the DMSUPPORT library. For audited databases, the RECONSTRUCT program is also compiled.
No compilations are initiated when the ZIP option is reset.
DATABASE/WFL/COMPILEACR, DATABASE/WFL/COMPILEDB, and DATABASE/WFL/AUTOREORG do not provide job specifications that control aspects of the job when they are run. If there are special requirements when running these WFL jobs, examine the requirements and consider setting the following job options:
-
Class specification
-
Family specification
-
Usercode specification
-
Fetch specification
-
Job attribute assignment
In addition, the security statement can also be added after a successful compilation to change the security of the compiled code.
For a list of job file inputs, refer to “WFL Job File Inputs” later in this appendix. For detailed information about JOB ATTRIBUTE specifications and the security statement, refer to the WFL Reference Manual.
For more information about DATABASE/WFL/COMPILEDB and DATABASE/WFL/COMPILEACR, refer to the Enterprise Database Server Utilities Operations Guide.
User Options
User options need not be explicitly declared. They are defined by their first appearance on a compiler control card. Do not use UPDATE and REORGANIZE as user options. An error message results if either are used. By default, all user options are reset.
