Digital

NAME

acms − Runs the ACMSxp client to invoke STDL procedures

SYNOPSIS

acms [ alias | -p procedure-name [-g tg-name] [-n ns-name] [-v m[.n]] ]
 

DESCRIPTION

The acms utility allows you to invoke an STDL procedure.  You can originate an ACMSxp request from a terminal login session or from a DECterm window, the DECwindows Session Manager Applications Menu, or a Motif window manager (mwm) applications menu. From the system prompt, run the ACMSxp client in either single mode or interactive mode. If you are going to invoke several procedures, it is more efficient to use the interactive mode. 

If you enter the acms command without arguments, the ACMSxp client runs, enters interactive mode, and displays its prompt. For example:

acms>

In interactive mode, the ACMSxp client supports command line recall and editing. Get help by typing the help command. Exit the client by typing Ctrl/C or the exit or quit command.
 
In interactive mode, if you enter the -p flag with a procedure name as an argument, the ACMSxp client runs the specified procedure. The procedure is the name of a task in a currently running task server within the same cell as the principal invoking the procedure. For missing flags, the software uses the values of environment variables (see below). If you supply an optional flag and the related environment variable is defined, the ACMSxp client uses the value supplied with the flag.
 
If you enter the acms command and an argument with no flags, the ACMSxp client checks for an alias name in an alias file that matches the argument. The value of the ACMS_ALIAS_FILE environment variable gives the full path and name of the alias file. An equivalence string associated with the alias in the file supplies the arguments for invoking a procedure.
 
The format for records in the alias file is:

alias-name:equivalence-string

The equivalence string must be a syntactically correct invocation argument list. White space between the tokens is ignored and can be included for readability. For example:

vm_ltk:-p vm_list_task -g vm_task_grp -n "/.:/acmsxp/avertz_rent" -v 01

Do not use acms commands such as exit and quit as aliases. Arguments not specified in flags on the alias equivalence string are taken from the related environment variables.
 

FLAGS

-pprocedure-name
 
Identifies the application procedure to execute.
 
If the flag is omitted, any argument specified is treated as an alias. You must specify either an alias or a procedure name if you specify any arguments on the command line.
 

-gtg-name
 
Identifies the task group name for the application procedure.
 
If the flag is omitted, the value of the environment variable ACMS_DEFAULT_INTERFACE is used.
 

-nns-name
 
Specifies the DCE namespace name for looking up the specified interface. For example, the TPsystem default profile entry or the namespace entry of the server supporting the interface.
 
If the flag is omitted, the value of the environment variable RPC_DEFAULT_ENTRY is used.
 

-vmj [.mn]
 
Specifies the major version number of the interface and optionally the minor version number.
 
If omitted, the highest version number of the interface is used.
 

Client Setup

To set up the client to run server procedures, do the following:

     1.Create the server interface directory. Place in this directory the interface descriptor files for all the server procedures to be invoked from the ACMSxp client. 

     2.Define the environment variable ACMS_INTERFACE_PATH to point to the directory or directories containing the interface descriptor files. 

     3.Define any environment variables needed. See below. 

     4.Copy the interface descriptor files to the directory you created. 

     5.Create the alias file if you are using command line aliases. 

     6.Create a DCE user principal under which the logged-in user can invoke an ACMSxp procedure (if you are not using unauthenticated access to your servers). 
 

Environment Variables

The following environment variables are used:

       •ACMS_ALIAS_FILE (Optional)
 
A full path and name for the file containing the aliases and equivalence strings for the command line arguments.

       •ACMS_EVENT_FILTER (Optional)
 
One of the following values for the events described:
 
   FAULT         Logs fault events only (the default if ACMS_LOG_FILE
                 is defined)
   FAULT,TRACE   Logs fault and trace events if ACMS_LOG_FILE
                 is defined
   TRACE         Logs trace events only  if ACMS_LOG_FILE
                 is defined
  If ACMS_LOG_FILE is defined and ACMS_EVENT_FILTER is not defined, only fault events are logged.

       •ACMS_INTERFACE_PATH (Required)
 
A path name for the directory containing the server interface descriptor files.

       •ACMS_LOG_FILE (Optional)
 
A path name for the file in which events are written. If it is not set, no events are logged. If it is defined, the software checks the ACMS_EVENT_FILTER environment variable to see whether to log trace events. If ACMS_EVENT_FILTER is not defined, only fault events are logged.
 

       •LANG (Optional)
 
The natural language of the user and the human language in which error and informational messages are displayed and logged, for example, ENGLISH or en_US.

       •NLSPATH (Optional)
 
A path name for the directory holding the ACMSxp message catalogs. The script acms_set_version defines this environment variable.

       •RPC_DEFAULT_ENTRY (Optional)
 
Entry point in the DCE namespace directory. Specify a namespace name, for example, a TP system profile entry or a server entry for an ACMSxp task server.
 

Processing

The ACMSxp client cannot support exchange I/O. 
 
Error and informational messages are displayed on this terminal in the user’s natural language.
 
Application procedures execute synchronously. Wait until a procedure completes and then invoke the next procedure. The user cannot cancel an application procedure after it starts. If the communications link is dropped during an invocation, the ACMSxp system attempts to cancel the invoked procedure. The client displays both system exception information and application-defined exceptions. The client uses the ACMSxp message catalog and the application-defined message catalog to map all exceptions.
 
When an invoked procedure completes, the client clears the screen, regardless of the status returned from the procedure.
 

EXAMPLES

acms -p vm_list_task -g vm_task_grp -n /.:/acmsxp/avertz_rent
 

acms vltk
 

RELATED INFORMATION

Commands: acmsadmin(1), acmsdbx(1), acmslog(1), gwlog(1), stdl(1)

Scripts: acms_create_tpsystem(1), acms_delete_tpsystem(1), acms_set_version(1), acms_start_tpsystem(1)

acmsxp_introduction(1)