Format @file-spec
1 – Parameters
1.1 – file-spec
Specifies the CDO command file to execute. File-spec can be a fully qualified path name, a relative path name, or a logical name. The default file type is .CDO.
2 – Description
The @ (at sign) command reads and executes the CDO commands contained in the specified file as if you had entered these commands at the terminal. The file can contain any valid CDO commands, including other @ commands. By default, CDO does not echo commands and comments in your file to the standard output location. You can override this default by including the SET VERIFY command as the first command in your file. By default, CDO exits the file when it encounters an error. You can override this default by including the ON command in your file. When CDO executes an EXIT command in the file, or reaches the end of the file, control returns to the command stream that invoked the file. That command stream can be the terminal or a previous file containing CDO commands. You can issue the @ command at the CDO prompt (CDO>). After the CDO commands execute, the CDO prompt returns. You can issue the @ command as a foreign command at the system level. You can append the @ command to the REPOSITORY OPERATOR command. You can also include the REPOSITORY OPERATOR @ command in an OpenVMS command procedure. To execute a CDO command procedure with a default file type of .CDO, you do not need to specify the file type. If the file type for a CDO command procedure is not .CDO, you must specify the file type to execute the command procedure. After the CDO commands execute, the system prompt returns. If you intend to use your file as an initialization file, you need not issue the @ command. Instead, name your file CDO$INIT.CDO and place it in the directory from which you invoke CDO. CDO then automatically executes this file at the start of each CDO session. You can also define CDO$INIT as a logical name specifying a device, directory, and file name. If you use such a logical name, the file does not need to be in your default directory when you invoke CDO.
3 – Examples
1.$ DEFINE CDO$INIT SYS$LOGIN:CDO$INIT.CDO $ SET VERIFY $ SET DEFAULT USER$DISK:[BOB.DICT] $ SHOW DEFAULT CDO> DIRECTORY In this example, the CDO$INIT.CDO initialization file sets your default repository directory. Oracle CDD/Repository automatically executes the initialization file when you invoke CDO from the OpenVMS directory that contains it. 2.CDO> @START CDO> SET DEFAULT USER$DISK:[BOB.DICT] CDO> DIRECTORY Directory USER$DISK:[BOB.DICT] CDDPLUS DIRECTORY CDO> The START.CDO command procedure in this example places you in the [BOB.DICT] directory, then lists the definitions in that directory. The SET VERIFY command in the previous example instructs CDO to display each subsequent command on the terminal screen before execution. 3.CDO> @EMPLOYEES.PROCEDURE In this example, the @ (at sign) command executes the CDO commands in the EMPLOYEES.PROCEDURE command procedure. 4.CDO> @CDDNODE::SYS$DISK:[SMITH.REP]CHANGE.PROCEDURE In this example, the file specification incorporates a fully qualified path name and a user-supplied file type. The @ (at sign) command executes the CHANGE.PROCEDURE file. 5.CDO> @START In this example, the file specification incorporates a file name and the default file type (.CDO). The @ (at sign) command executes the START.CDO file. 6.$ DEFINE CDO$INIT SYS$LOGIN:CDO$INIT.CDO $ TYPE SYS$LOGIN:CDO$INIT.CDO $ SET VERIFY $ SET DEFAULT device:[CDDPLUS]MYDIR $ SHOW DEFAULT $ REPOSITORY OPERATOR In this example, when CDO is invoked, SYS$LOGIN:CDO$INIT.CDO is executed immediately before the CDO prompt is displayed.