HP OpenVMS Systems Documentation
OpenVMS Record Management Utilities Reference Manual
For DECnet for OpenVMS operations, the maximum record size is
determined by the DCL command SET RMS/NETWORK_BLOCK_COUNT.
The SHARING section allows you to specify whether you want to allow multiple readers or writers to access your file at the same time. The SHARING keyword takes no values; it serves only to define this section.
The following table lists the SHARING secondary attributes and their default values. Note that all SHARING secondary attributes are run-time attributes.
4.12 SYSTEM Section
The SYSTEM section consists of system identification information and can be used to help document your FDL file. The SYSTEM keyword takes no values; it serves only to define this section.
4.13 TITLE and IDENT Attributes
If you use EDIT/FDL to create your FDL file, the utility prompts you for a title during the session. The title is a string that you can place at the beginning of the FDL file. The character string you supply is for comment purposes only. It can be up to 132 characters long, including the TITLE keyword.
When the Edit/FDL and Analyze/RMS_File utilities create an FDL file, they place a header called the IDENT section after the TITLE in the FDL file. The IDENT attribute specifies the date and time of the creation of the FDL file, and it specifies the name of the utility that created it (either EDIT/FDL or ANALYZE/RMS_FILE).
However, you can also specify the header in the IDENT section. The character string that you supply can be up to 132 characters long, including the IDENT keyword.
TITLE Sequential organization, variable records up to 320 bytes IDENT 25-SEP-1993 13:08:17 OpenVMS FDL Editor SYSTEM SOURCE VMS FILE ALLOCATION 5050 BEST_TRY_CONTIGUOUS yes EXTENSION 505 ORGANIZATION sequential RECORD BLOCK_SPAN yes CARRIAGE_CONTROL carriage_return FORMAT variable SIZE 320
The Create/FDL utility uses the specifications in an existing FDL file to create a new, empty data file. You can supply the Create/FDL utility with the file specification of the new data file, or the Create/FDL utility can use the specification given in the FDL file itself.
These data files can use the full set of RMS creation-time options and they can be used by all the native OpenVMS high-level languages. This capability gives the high-level language user a tool for creating efficient data files that use a minimum amount of system resources.
The FDL routines (FDL$CREATE, FDL$GENERATE, and FDL$PARSE) also use FDL
files. FDL$CREATE invokes the functions of the Create/FDL utility
(CREATE/FDL) to create a file from an FDL specification and then to
close the file. FDL$GENERATE produces an FDL specification from the RMS
control blocks your program supplies, and then writes it to either an
FDL file or a character string. FDL$PARSE parses an FDL specification,
allocates RMS control blocks (FABs, RABs, or XABs), and then fills in
the relevant fields.
CREATE/FDL Usage Summary
The Create/FDL utility uses the specifications in an existing FDL file to create a new, empty data file.
CREATE/FDL= fdl-filespec [filespec]
Usage Summary To invoke the Create/FDL utility, enter the CREATE/FDL command at the DCL command level. The Create/FDL utility produces the empty data file specified by the CREATE/FDL command or by the FDL file. To exit the Create/FDL utility, let it run to successful completion.
fdl-filespecSpecifies the FDL file from which to create the data file.
filespecSpecifies an optional file specification for the created file. If you specify a complete file specification, it overrides any contained in the FDL file.
The CREATE/FDL command has only one qualifier: the /LOG qualifier. It
does not affect the execution of the utility; it only produces an
This qualifier controls whether the Create/FDL utility displays the file specification of the data file it has created. By default, the utility does not display the file specification.
$ CREATE/FDL=INVENTORY/LOG DISK$:[COMPANY.ORDERS]PARTS.DAT %FDL-I-CREATED, DISK$:[COMPANY.ORDERS]PARTS.DAT;1 CREATED
This command produces the empty output file PARTS.DAT from the specifications in the FDL file INVENTORY.FDL. Because the /LOG qualifier is used in the command, the Create/FDL utility returns an informational message stating the file specification for the file that was created.
$ CREATE/FDL=INVENTORY PARTS.DAT
This command produces the empty output file PARTS.DAT from the specifications in the FDL file INVENTORY.FDL. Because the /LOG qualifier was not used with the CREATE/FDL command, no informational message is returned.
On Alpha systems, the Edit/FDL utility and its qualifiers contain capabilities that allow them to use the features provided by extended file specifications. Extended file specifications offer extended file naming and handling capabilities that enable OpenVMS Alpha systems to store, manage, serve, and access files across both OpenVMS and Windows NT systems in a PATHWORKS environment. Specifically, extended file specifications provide the following features:
For more information, see the OpenVMS Guide to Extended File Specifications.
6.1 Creating FDL Files with the Edit/FDL Utility
One way to create FDL files easily is with the Edit/FDL utility (also known as the FDL editor). You can use the EDIT/FDL command to design FDL files that define commonly needed data files and then to create the data files when they are needed. The Edit/FDL utility has some special features that simplify the process of creating an FDL file. It recognizes FDL syntax and informs you of syntax errors immediately. It also lets you model the data file to be created and change attribute values to find the most efficient design.
Alternatively, you can use the ANALYZE/RMS_FILE command to create an
FDL file from an existing data file which can then be used with the
Optimize script to determine the optimum design of the data file.
6.1.1 Validity Rules
The Edit/FDL utility (EDIT/FDL) and the Analyze/RMS_File utility (ANALYZE/RMS_FILE) place the attributes in their correct format and order automatically. If you use the CREATE command or a text editor to create an FDL file, you must observe the following validity rules:
!"This line is okay; there are quotes setting off the comment"
The Edit/FDL utility (EDIT/FDL) can help you create FDL files. The Edit/FDL utility was developed especially to manipulate FDL files. It has special features designed to simplify the process of creating an FDL file and should be used in most cases.
Usage Summary To invoke the Edit/FDL utility, enter the EDIT/FDL command at the DCL command level. The Edit/FDL utility produces a new version of the input file unless the /OUTPUT qualifier is used to direct the output to a different file. To exit the Edit/FDL utility, enter either the EXIT command or the QUIT command. (Pressing Ctrl/Z has the same effect as entering the EXIT command, and Ctrl/C has the same effect as the QUIT command.)
fdl-filespecUse this parameter to specify the FDL file to be created, modified, or optimized during this session. If you specify an existing FDL file for modification or for optimization, the output file is the next higher version of the file being modified or optimized. In all cases, you have the option of using the /OUTPUT qualifier to specify the output FDL file. The default file type is .FDL.
When you enter the EDIT/FDL command, the system refers to a reserved logical name, EDF. Do not use this logical name.
The DCL command EDIT/FDL begins an interactive session during which you
can create or modify an FDL file. You can give the editor file design
decisions and it will supply values for the FDL attributes or you can
assign values to the attributes yourself. This section describes the
EDIT/FDL qualifiers and how you use them to select the utility
functions. Unless otherwise noted, these qualifiers do not take a
This qualifier specifies an FDL file obtained from a file analysis. See Chapter 1 for more information about analyzing files.
fdl-filespecSpecifies the particular FDL file obtained from a file analysis that is to be used as an input to the Optimize script. The default is a null file specification.
$ EDIT/FDL/ANALYSIS=Q1_SALES Q2_SALES
This command begins an interactive session in which the analysis information in the file Q1_SALES.FDL is used, together with the input FDL file Q2_SALES.FDL, to obtain an optimized output file, which the system designates as the next higher version of Q2_SALES.FDL.
This qualifier allows you to create an output file without an existing input file.
Using the /CREATE qualifier, you can create an output file directly without the Edit/FDL utility notifying you that the file is to be created. The Edit/FDL utility does not attempt to open the specified file for input when you use the /CREATE qualifier. The Edit/FDL utility assumes that either the file does not exist or that you want the utility to ignore it.
$ EDIT/FDL/CREATE SALES_DATA
This command begins a session in which SALES_DATA.FDL is created. The Edit/FDL utility does not issue the informational message stating that the new file SALES_DATA.FDL will be created.