Uses output from the CREATE command to build a database file that ACMS can run. When used with the /STDL qualifier---first BUILD GROUP /STDL, then BUILD APPLICATION /STDL---to translate ACMS task group information to STDL format, first builds an intermediate-format World Wide Web (web) database file and then, using the web database file, builds an STDL source file.

Format

Keywords

APPLICATION

Builds an application database.

GROUP

Builds a task group database.

MENU

Builds a menu database.

Parameters

path-name

The CDD path name of the definition you want the BUILD command to process. When used with the BUILD GROUP /STDL command, path-name is the task group name; when used with the BUILD APPLICATION /STDL command, path-name is the application name.

database-file-spec

The file specification for the database file that the BUILD command creates. This output file is a database file that ACMS uses at run time. The BUILD command can create an application, task group, or menu database file; a special intermediate-format web database file; or a special application STDL file.

If you do not name a database file when you build an application, task group, or menu definition, ADU uses the file named in the DEFAULT FILE clause of the definition. If the definition does not name a default database file, ACMS uses the full given name (including dollar signs and underscores) of the given name of the application, task group, or menu you are building.

The database produced by the BUILD command depends on the type of definition you are building.

When you build an application definition, the BUILD command produces an application database (.ADB) file with a default .ADB file type.

When you build a menu definition, the BUILD command produces a menu database (.MDB) file with a default .MDB file type.

When you build a task group definition, the BUILD command produces:

• A task database file---default file type: .TDB
• One or more procedure server transfer module files---default file type: .OBJ

When you use the /STDL qualifier in two special processing stages -- group_task translation, then application_group translation---to translate ACMS task group information to STDL format, allowing you subsequently to build a Windows NT client interface that enables ACMS applications to be accessed by NT clients, the BUILD command produces:

1. An intermediate-format web database file, produced by the group_task translation initiated with BUILD GROUP /STDL, containing task, task group, and record information and used as input in application_group translation processing---default file type: .WDB
2. An STDL source file, produced by the application_group translation initiated by BUILD APPLICATION /STDL, containing a task group specification and related data type and record definitions and using as input an intermediate web database file from group_task translation processing---default file type: .STDL

For example:

ADU> BUILD APPLICATION PERSONNEL PERS.ADB

The default directory is your current default directory. The default device is SYS$DISK, which must translate to a device name.

Qualifiers

/AUDIT [=audit-list]/NOAUDIT

The /AUDIT and /NOAUDIT qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]DEBUG

Makes the contents of workspaces available for you to examine or deposit during a debugging session. Use this qualifier only when building a task group.

The /NODEBUG qualifier makes the contents of workspaces unavailable during a debugging session.

The default is /NODEBUG.

/LIST [=list-file-spec]/NOLIST

The /LIST and /NOLIST qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]LOG

The /[NO]LOG qualifier is common to several ADU commands. See Section 1.4 which describes common qualifiers.

/OBJECT=(file-spec [,...] ) /NOOBJECT

The /OBJECT and /NOOBJECT qualifiers control whether or not object modules are searched for global symbol resolution during build group processing. You can use the /OBJECT qualifier to point to message files. The default is /NOOBJECT.

/[NO]PRINT

The /[NO]PRINT qualifier is common to several ADU commands. See Section 1.4 which describes common qualifiers.

/[NO]STDL

Translates an ACMS application's task headers and task group, task, and record definitions extracted from the CDD to an STDL task group specification, data type definitions, STDL record definitions, and task group headers with records as arguments. The translation takes place in two processing stages: group_task translation, which is initiated by the BUILD GROUP /STDL command, and application_group translation, which is initiated by the BUILD APPLICATION /STDL command. You use the STDL output file to create the client interface that enables Windows NT clients to access ACMS applications.

/[NO]SYSLIB

The /[NO]SYSLIB qualifier controls whether or not to search the default system libraries SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB to resolve global symbols during build group processing. The default is /SYSLIB. The system libraries are not searched if you use the /NOSYSLIB qualifier. If you use both the /NOSYSLIB and /SYSSHR qualifiers, the /SYSSHR qualifier is ignored.

/[NO]SYSSHR

The /[NO]SYSSHR qualifier controls whether or not to search SYS$LIBRARY:IMAGELIB.OLB to resolve global symbols during build group processing. The default is /SYSSHR.

/USERLIBRARY=(file-spec [,...] ) /NOUSERLIBRARY

The /USERLIBRARY and /NOUSERLIBRARY qualifiers control whether or not to search user-specified object libraries and shared image libraries to resolve global symbols during build group processing. The default is /NOUSERLIBRARY. If you use the /NOSYSLIB or /NOSYSSHR qualifier, you can specify the default system libraries SYS$LIBRARY:IMAGELIB.OLB or SYS$LIBRARY:STARLET.OLB with the /USERLIBRARY qualifier.

Notes

Before you can start an application, that application's database file must be in the directory associated with the logical name ACMS$DIRECTORY. The two ways to put the database file in that directory are:

• Use the DCL COPY command to copy the database file into the directory that ACMS$DIRECTORY points to. This requires that you have write access to ACMS$DIRECTORY.
• Use the ACMS/INSTALL operator command to put the application database file into ACMS$DIRECTORY. You must be authorized to use the ACMS/INSTALL command.

A menu database file can be in any directory. However, its location must match the file specification of the user definition file (ACMSUDF.DAT) named by the User Definition Utility /MDB qualifier. In general, keep menu database files in the directory pointed to by ACMS$DIRECTORY. See Compaq ACMS for OpenVMS Managing Applications for details about using the User Definition Utility.

A task group database file (.TDB) can be in any directory. However, its location must match the file specification that is used in the TASK GROUPS clause of the application definition.

The BUILD MENU command moves all subordinate menus into the menu database, as well as the menu (top menu) that you name in the BUILD command.

When you build a task group, ADU produces one task group database. ADU produces one procedure server object module for each procedure server named in the task group definition. The object module for each server is named in the DEFAULT OBJECT FILE subclause for that server. However, if you do not use the DEFAULT OBJECT FILE subclause for a server, ADU derives the name of the object file from the unique name of the server. ADU uses the full given name, including dollar signs ($) and underscores (_), for the default name of the object file.

To resolve global symbols, ACMS first searches, in order, the files specified with the /OBJECT qualifier. If the global symbol is not found, ACMS searches, in order, the libraries specified with the /USERLIBRARY qualifier. If the symbol is still not found, ACMS then searches the default system libraries SYS$LIBRARY:IMAGELIB.OLB and SYS$LIBRARY:STARLET.OLB, in that order. Once a global symbol is found, the search stops.

The /STDL qualifier translates an ACMS application's task headers and task group, task, and record definitions (extracted from the CDD) to an STDL task group specification, data type definitions, STDL record definitions, and task group headers with records as arguments. The translation takes place in two processing stages: group task translation, which is initiated by the BUILD GROUP /STDL command, and application group translation, which is initiated by the BUILD APPLICATION /STDL command. You use the STDL output file to create the client interface that enables Windows NT® clients to access ACMS applications.

Group Task Translation

Group task translation produces a temporary binary file containing ACMS task and task group information. Group task translation must be performed for the ACMS task group that comprises the application. The command syntax is:

BUILD GROUP acms_group_name [/STDL]

In this format, acms_group_name refers to the name of the ACMS task group.

The /STDL qualifier directs ADU to output task and record information that is used for completing the translation to STDL format. The output file produced by the /STDL qualifier has a name in the format group.WDB.

The .WDB file type indicates the intermediate-format web database file. The BUILD GROUP command writes the file to the default directory. (See DEFAULT TASK GROUP FILE Clause (Task Group).)

The /NOSTDL qualifier instructs ADU not to produce the intermediate-format file. The default qualifier is /NOSTDL.

Application Group Translation

Application group translation reads the task group name as specified in the application and translates the intermediate-format task group file built from the group_task translation. The command syntax is:

BUILD APPLICATION application_name [/STDL]

In this format, application_name refers to the name of an ACMS application.

The /STDL qualifier directs the translator during the processing initiated by the ADU BUILD APPLICATION command to generate STDL code using the intermediate-format group file that was created during the ADU BUILD GROUP compilation. The output is a file with a name in the format application_name.STDL.

ADU generates in the default directory an STDL source file containing a task group specification and related data type and record definitions. You use this file to create the client interface that enables Windows NT clients to access ACMS applications.

Examples

ADU> SET DEFAULT DISK1:[CDDPLUS]APPLICATION
ADU> BUILD APPLICATION PERSONNEL PERSONNEL.ADB /LOG
%ACMSCDU-I-BLDSRVNAM, Building server EMPLOYEE_SERVER
%ACMSCDU-I-BLDTSKNAM, Building task EMPLOYEE
%ACMSCDU-I-BLDTSKNAM, Building task DATR
%ACMSCDU-I-BLDTSKNAM, Building task EDTR
%ACMSCDU-I-BLDTSKNAM, Building task MAIL
%ACMSCDU-I-WRITEADB, Writing ADB
-ACMSCDU-I-BYTESWRIT, 1180 bytes (3 blocks)
%ACMSCDU-S-APPBUILT, Application DISK1:[CDDPLUS]APPLICATION.PERSONNEL 
built into file
'EXAMPLES$:[EXAMPLES]PERSONNEL.ADB;1'
ADU>
      

After setting the default CDD directory to DISK1:[CDDPLUS]APPLICATION, use the BUILD command to process the Personnel application. The /LOG qualifier displays messages about the build operation and returns you to the ADU> prompt. The last message indicates that the BUILD command created the database file and put it in the PERSONNEL.ADB file located in your current default directory.

ADU> BUILD MENU DISK1:[CDDPLUS]EXAMPLES.EMPLOYEE_MENU MENU.MDB /LOG
%ACMSCDU-I-PROCTASK, Processing task 'EMPLOYEE'
%ACMSCDU-I-MENUNAME, Menu named 'EMPLOYEE_MENU'
%ACMSCDU-I-LODMENNAM, Loading menu
%ACMSCDU-I-MENPTHLOD, Menu CDD object 'DISK1:[CDDPLUS]EXAMPLES.EMPLOYEE_ 
MENU' loaded
%ACMSCDU-I-PROCMENU, Processing menu 'UTILITY_MENU'
%ACMSCDU-I-PROCTASK, Processing task 'DATR'
%ACMSCDU-I-PROCTASK, Processing task 'EDTR'
%ACMSCDU-I-PROCTASK, Processing task 'MAIL'
%ACMSCDU-I-WRITEMDB, Writing MDB
-ACMSCDU-I-BYTESWRIT, 1128 bytes (3 blocks)
%ACMSCDU-S-MENBUILT, Menu DISK1:[CDDPLUS]EXAMPLES.EMPLOYEE_MENU built 
into file
'EXAMPLES$:[EXAMPLES]MENU.MDB;1'
      

The BUILD command in this example builds a menu using the menu definition in the CDD directory EXAMPLES with the given name EMPLOYEE_MENU. The /LOG qualifier confirms that the output database file MENU.MDB is in your default directory and that the associated tasks and submenus were built using the main menu definition.

ADU> BUILD GROUP AVERTZ_CDD_GROUP:VR_TASK_GROUP -
_ADU>  AVERTZ_TDB:VR_TASK_GROUP.TDB/OBJECT=AVERTZ_OBJ:VRMSG.OBJ 
      

The BUILD command in this example builds a task group using the task group definition in the CDD directory AVERTZ_CDD_GROUP with the given name VR_TASK_GROUP. The /OBJECT qualifier instructs ADU to use the VRMSG.OBJ message file to resolve symbols during processing.

Checks an application, task group, menu, or task definition for syntax errors, and writes the compilation results to a file.

Format

Keywords

APPLICATION

Compiles an application definition.

GROUP

Compiles a task group definition.

MENU

Compiles a menu definition.

TASK

Compiles a task definition.

Parameters

reference-name

The name by which the ACMS entity to be compiled should be referenced in other definitions.

For tasks, this name is used in the following ways:

• In a task definition when the task is called from another task (CALL TASK <task-name>)
• In a group definition in the TASK DEFINITION IS <task-name> clause.

For menus, this name is used when a menu entry is another menu (MENU IS <menu-name>).

definition-file-spec

The file specification of the source definition file.

Qualifiers

/DIAGNOSTICS [=diagnostics-file-spec]
/NODIAGNOSTICS

Tells ADU to produce a diagnostics file that LSE uses when you issue the LSE REVIEW command. ADU places the diagnostics file in your default directory. If you use the /DIAGNOSTICS qualifier without specifying a diagnostics file specification, ADU creates a diagnostics file that has the entity name with a file type .DIA.

/NODIAGNOSTICS is the default in batch or interactive mode.

/LIST [=list-file-spec]
/NOLIST

The /LIST and /NOLIST qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]LOG

The /[NO]LOG qualifier is common to several ADU commands. See Section 1.4, which describes common qualifiers.

/OUTPUT [=output-file-spec]
/NOOUTPUT

The default file specification to use to determine the file in which to put the results of the compilation. The /NOOUTPUT qualifier allows you to check for compilation errors without producing an output file.

/[NO]PRINT

The /[NO]PRINT qualifier is common to several ADU commands. See Section 1.4, which describes common qualifiers.

Notes

Use the COMPILE command to submit a source definition to ADU interactively or from a command file. ADU compiles the definition. If ADU finds no syntax errors, it stores the compilation results in a file. ADU determines the output file specification using several pieces of information. The defaults are as follows:

• The device defaults to the current device.
• The directory defaults to the current directory.
• The file name defaults to the name parameter.
• The file extension defaults to .ABJ for application result files, .GBJ for task group result files, .MBJ for menu result files, and .TBJ for task result files.

Any of the components of the file specification can be overridden by supplying them with the /OUTPUT qualifier.

Examples

ADU> COMPILE TASK PERSONNEL PERSONNEL.TDF
ADU> 
      

This command processes a task source definition in the PERSONNEL.TDF file in your current directory and puts the compilation results in the PERSONNEL.TBJ file.

ADU> COMPILE GROUP INVENTORY_GROUP INVENTORY /OUTPUT = USERD$:[INVENTORY.OBJ]
ADU>
      

This command processes a task group source definition in the INVENTORY.GDF file in your current directory and puts the compilation results in USERD$:[INVENTORY.OBJ]INVENTORY_GROUP.GBJ.

Creates a copy of a definition. Use this command to copy a definition in your own directory or in a different dictionary directory. Instead of rewriting an entire definition, you can save time by copying a definition of source code. Then change parts of the definition to suit your specific application.

You can also use the COPY command to convert definitions from Dictionary Management Utility (DMU) to Common Dictionary Operator (CDO) format.

Format

Keywords

APPLICATION

Makes a copy of an application definition.

GROUP

Makes a copy of a task group definition.

MENU

Makes a copy of a menu definition.

TASK

Makes a copy of a task definition.

Parameters

src-path-name

The CDD path name of the definition you want to copy.

dst-path-name

The CDD path name to use for storing the definition you are copying.

Qualifiers

/AUDIT [=audit-list]
/NOAUDIT

The /AUDIT and /NOAUDIT qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]LOG

The /[NO]LOG qualifier is common to several ADU commands. See Section 1.4, which describes common qualifiers.

Notes

To convert a definition from DMU format to CDO format:

1. Copy the definition to a temporary dictionary directory.
2. Delete the original source definition.
3. Copy the definition from the temporary directory back to the source directory.
4. Delete the temporary directory by deleting its contents.

You must use the temporary directory because the CDD dictionaries share name space.

Example

ADU> SET DEFAULT DISK1:[CDDPLUS]APPLICATION
ADU> COPY APPLICATION UPDATE_ONE UPDATE_TWO/LOG
%ACMSCDU-S-APPCOPIED, Application DISK1:[CDDPLUS]APPLICATION.UPDATE_ONE
copied to DISK1:[CDDPLUS]APPLICATION.UPDATE_TWO
ADU>
      

This COPY command creates a copy of the dictionary definition UPDATE_ONE in your default CDD directory. To use the new definition, set your default to DISK1:[CDDPLUS]APPLICATION and use the given name UPDATE_TWO. The /LOG qualifier confirms that the COPY command successfully created a new copy of the application definition. Control returns to the ADU> prompt.

Checks an application, task group, menu, or task definition for syntax errors, and stores valid new definitions in the dictionary. Use this command to create the components of an ACMS application.

Format

Keywords

APPLICATION

Creates an application definition.

GROUP

Creates a task group definition.

MENU

Creates a menu definition.

TASK

Creates a task definition.

Parameters

path-name

The CDD path name that the CREATE command uses to store the processed definition.

file-spec

The file specification of the source definition file.

Qualifiers

/AUDIT [=audit-list]
/NOAUDIT

The /AUDIT and /NOAUDIT qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/DIAGNOSTICS [=diagnostics-file-spec]
/NODIAGNOSTICS

Tells ADU to produce a diagnostics file that LSE uses when you issue the LSE REVIEW command. ADU places the diagnostics file in your default directory. If you use the /DIAGNOSTICS qualifier without specifying a diagnostics file specification, ADU creates a diagnostics file that has the entity name with a file type .DIA.

/NODIAGNOSTICS is the default in batch or interactive mode.

/LIST [=list-file-spec]
/NOLIST

The /LIST and /NOLIST qualifiers are common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]LOG

The /[NO]LOG qualifier is common to several ADU commands. See Section 1.4, which describes common qualifiers.

/[NO]PRINT

The /[NO]PRINT qualifier is common to several ADU commands. See Section 1.4, which describes common qualifiers.

Notes

Use the CREATE command to submit a source definition to ADU interactively or from a command file. ADU compiles the definition. If ADU finds no syntax errors, it stores the new object definition in the dictionary.

When you use the CREATE command interactively, ADU displays the ADUDFN> prompt for you to type the definition. If you make typing mistakes, use the EDIT command at the ADU> prompt and correct your errors without retyping the entire definition. ADU does not store a definition containing errors in the dictionary.

If you do not include a file specification for your definition, ADU assigns the default file type of .ADF for application source files, .GDF for task group source files, .MDF for menu source files, and .TDF for task definition source files.

When you create a new definition, it is a good idea to use the REPLACE command in a command file instead of the CREATE command. The REPLACE command stores new definitions or replaces existing definitions in the dictionary. The CREATE command processes new definitions only.

If you use the /DIAGNOSTICS qualifier, ADU creates an LSE diagnostics file every time you issue the command. LSE uses the diagnostics file to help you debug your definitions with the LSE REVIEW command.

If you use the /DIAGNOSTICS qualifier in a command file, ADU creates a diagnostics file every time you run the command file. To save disk space, use the DCL PURGE or DCL DELETE command to reduce the number of versions in your default directory or delete unneeded diagnostics files.

Examples

ADU> CREATE APPLICATION EMPLOYEE PERSONNEL.ADF
ADU>
      

This command processes an application source definition in the file PERSONNEL.ADF in your default directory and puts the definition in the dictionary.

ADU> SET DEFAULT DISK1:[CDDPLUS]DEPARTMENT
ADU> CREATE GROUP GROUP_ONE TSK/LOG
%ADU-S-TGPCREATE, task group GROUP_ONE created
ADU>
      

After setting the default to DISK1:[CDDPLUS]DEPARTMENT, you can specify the path name with just the given name GROUP_ONE. This saves you the trouble of specifying the entire path name each time you use the dictionary. The keyword to use in creating a task group is GROUP. The CREATE command finds the source definition file in TSK.GDF in your default directory. (Because you omit the file type from the source definition file specification, the ADU assigns a file type of .GDF.) ADU displays a message indicating that the create operation was successful.