Ref: 03050003
Title: An Explanation of "&cmd" Errors When Running 3SIS Scripts
Date: 3/7/90

Copyright 3Com Corporation, 1991.  All rights reserved.

Occasionally, users will get an "&cmd" error when running 3SIS --
usually while installing a service or feature.

3Com has received reports of such errors when users are installing
3+Open Name 1.1 (using the 3NAME.INS script) or while installing
3+Open Mail 1.1 (using the 3MAIL2.INS script).  In the case of
installing Name, the error encountered looks like this:

(355) '&cmd /c net admin \\%server% /c ...' [xxx]

In the case of Mail, the error is similar but begins "(387) ...."

All of the "&cmd" 3SIS errors begin with a number in parentheses, followed
by a string, and end with another number within square brackets.  The
initial number is the line number of the 3SIS script file where 3SIS
encountered an error.  The remainder of the error message, except for the
ending number, is the text of the offending line.  (The ending number is
not important for this discussion.)  For example, the 3NAME.INS script file,
line number 355, has a line that begins

"&cmd /c net admin \\%server% /c ...."

The script directs 3SIS to call up an OS/2 shell (CMD.EXE) and pass it
this command line to execute:  "net admin \\%server% /c ...."  In other
words, the command processor is being asked to execute NET.EXE, and the
parameter passed to the NET program -- namely, "admin" -- tells it
in turn to call up NETADMIN.EXE, both of which may be found in:

        C:\3OPEN\SERVER\LANMAN\NETPROG      on a server, or
        C:\3OPEN\OS2WKSTA\LANMAN\NETPROG    on an OS/2 workstation

But if your PATH environment variable does not include the appropriate
NETPROG directory, you will see an error of the "&cmd" type when installing
3+Open Name or Mail 1.1.

The solution is to make sure that your PATH includes the appropriate
directory stated above (depending on whether you are running 3SIS from
an OS/2 workstation or 3+Open server).  Another way to avoid the problem
is to change to a directory on your OS/2 workstation or to a linked
directory on your server where the NET.EXE and NETADMIN.EXE programs
reside before starting up 3SIS.

If you see "&cmd" 3SIS errors while installing services other than
Name or Mail, look at the error string beyond the "&cmd /c" portion, and
identify what command CMD.EXE is supposed to be executing.  Whatever
command that is should be in your PATH or in the current directory.  Also
make sure that the command processor CMD.EXE is available in your PATH or
the current directory.

