Chapter 2:  Naming Conventions

This chapter describes naming conventions, which cover all namable ACCENT R objects.

ACCENT R supports the file name syntax allowed on each system on which it operates; therefore, the naming conventions, for the ACCENT R objects that exist as separate files, depend on the specific system being used.  These objects include:

Those objects that exist only within a Data Base Library (DBL) have a different syntax from that of the external files, but the syntax is the same on all operating systems.  These objects include:

A third naming convention exists for data fields and aliases.

Name Syntax for separate file DBL Objects

PURPOSE:  ACCENT R supports the expanded file name syntax of each operating system under which it operates for those objects that exist as separate files.  Those objects are Data Base Libraries (DBL), Data Sets (DS) Data Indexes (DI), Control Files (CF), Find Subsets (FS), and System Files (SF).  Optional elements of the total file specification can be supplied when these objects are named, and they are stored in the DBL.  All components are supplied by default if the user does not provide them; however, only those given by the user are cataloged in the ACCENT R DBL.

SYNTAX

["node::"]
[device:]]
[<dir_name>]
[filename]
[.ext]

ACCENT R limits the total file specification to 39 characters.  Components supplied by default are not included in the 39-character limit.  The objects can all vary in length within that limit.

["node::"]

is a string of up to 39 letters and digits, ended with a double colon, that identifies the network location of the system.  It may be referenced with quotes in ACCENT R.  The node may appear as an embedded part of a logical name.  The node name is referenced without the quotes at the Digital Command Language (DCL) level used with OpenVMS.

[device:]

is a string of up to 15 letters and digits, ended with a single colon, that identifies the physical device on which the file is stored used with OpenVMS.

[<dir_name>]

is a string of up to 39 letters and digits including hyphen and period.  The directory name must be enclosed by a pair of square brackets [ ].  If this element is supplied with no content, i.e. [ ], the default directory name is supplied and must be included in the character count used with OpenVMS.

[filename]

is a string of up to 39 letters and digits.  The file name can begin with a letter, a digit, or with three pound signs.  If the file name begins with ###, ACCENT R changes the pound signs to a base-34 number representation of the Process Identification number (PID) when the file is accessed.  The base-34 number uses the letter A through Z except D and E.

However, ACCENT R catalogs the file in the DBL with ###.  If the filename contains only digits, it should be enclosed in quotes when specified in ACCENT R.

[.ext]

is a string of up to 39 characters and digits preceded by a period, that defines the file type or provides further identification.  If omitted, ACCENT R supplies one of the following default extensions:

The default extensions need not be expressed in normal usage, even if they are supplied when the file is named.

EXTENSION

FILE TYPE

CF

Control File

DBL

Data Base Library

DS

Data Set

DI

Data Index

FS

Find Subset

LOG

Log file created by USE SF...LOG

CMD

System File created by DEFINE SF

REP

System File created as a report in a PM

DAT

System File created by SAVE ON clause

ERR

System File of invalid records created by ENTER

NOTES:  ACCENT R does not recognize the version number as part of the file specification.  It always uses the file with the latest version number.

Access Control List support

All files created by ACCENT R will now adhere to previously defined OpenVMS ACCESS CONTROL LISTS for files and directories.  Once a Data Base Library, Data Set, or other System File is created, copied, or rebuilt by the user through ACCENT R, that file’s Access Control List will be maintained in the new version of the file.

Name Syntax for Objects Exclusive to ACCENT R

Purpose:  Those objects that exist only within a Data Base Library (DBL) are Schema Definitions (SD), Process Modules (PM), Command Modules (CM), Global Storage (GS) definitions, Code Segments (CS), Index Definitions (ID), and System Information (SI).  They have a common naming convention.

DEFINITION

an object name

is a string of up to 39 letters and digits, including periods and underscores.  The first character must be a letter.  Embedded spaces are not allowed.

Example

STORES_DBM2 OLD.PART.NO DISCOUNT FIELD123

NOTES:  The names of Global Storage definitions should not begin with “ACC” because this prefix is used by the ACCENT R utilities that use Global Storages.

Avoid giving two Global Storages in different DBL’s the same name.  You cannot use two different Global Storages in different DBL’s that have the same name at the same time.  Also, Global Storages with the same name can cause problems when using the Instant Data Access feature.

Name Syntax for Fields

PURPOSE:  Data field names in record definitions, Global Storage definitions (GS), and DECLARE section in Process Modules (PM) have a common naming convention.

DEFINITION

name a field name

is a string of up to 39 characters.  The first character must be an alphabetic (A through Z) in either upper or lower case.  The characters following may be alphabetic, numeric, underscores, or periods.  Spaces and hyphens are not allowed in field names.

The reserved words listed in Appendix B cannot be used as field names.

Example

All of the following are acceptable field names:

PRICE TITLE_TEXT FIELD2 B.DATE E_DATE

LOGICAL NAME

Any system file may be addressed by an equated logical name.  The assigned logical can be defined with the @DEFINE.LOGICAL function within ACCENT R or defined at the system level before calling ACCENT R.

DBL objects which can be addressed with logicals are DBL’s, Data Sets, Data Indexes, Control Files and System Files.

A logical may proceed the actual name in order to select a version of the object where there are more than one of that name or to specifically locate that object in an account.

Example

CREATE DBL INV:
Where INV is defined as a valid file name
CREATE DBL ACCTING:PAYABLESCREATE DS BILLS: SD IS PAYABLESCREATE DI EXP: ENTRY ONLY

NOTES:  Do not define NIS or NISUTL as these are already defined for use by ACCENT R.  All Global Storage field names must be proceeded by a %.