SCO OpenServer Enterprise System Release 5.0.6, 5.0.7 
          SCO OpenServer Host System Release 5.0.6, 5.0.7 
          SCO OpenServer Desktop System Release 5.0.6, 5.0.7 
          SCO OpenServer Release 6.0.0 
          SCO Open UNIX 8 Release 8.0.0 
          Unixware 7 Release 7.0.0, 7.0.1, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4 

          SCO Unix systems provide a sophisticated user licensing
          scheme to allow customers to purchase a license closely tailored to
          their requirements.  Which networking commands will consume user
          licenses?

          This Technical Article describes which networking utilities consume
          user licenses.  It does not address the legal issue of user
          definition as defined by the Software License Agreement.  In some
          cases, there may be discrepancies between what the operating system
          counts as a user and what is legally defined as a user.  For more
          information on the legal definition of a user, see the Software
          License Agreement that accompanies all SCO products, or contact
          your SCO reseller.

          User licenses are requested by the login(M) command.  Various
          networking commands invoke login(M) to fulfill the user's request.
          The login(M) command determines whether to request a user license
          based on the 'type' of login.

          None of the various networking utilities consume licenses directly.
          That is to say, none of the commands request a user license from the
          Policy Manager.  User licenses are only requested when login(M) is
          invoked.

          The table below details example commands, whether that command
          invokes login(M), and whether the login(M) command consumes user
          licenses on that command's behalf.

               Utility                 Utility Consumes   login(M) Consumes
                                                License             License

               1.  telnet                            NO                YES
               2.  rlogin                            NO                YES
               3.  rcmd <machine>                    NO                YES
               4.  rcmd <machine> <command>          NO                 NO
               5.  rcp                               NO                 NO
               6.  ftp                               NO                 NO
               7.  dynamic PPP link                  NO                 NO
               8.  static PPP link                   NO                 NO
               9.  login over PPP link               NO                YES
               10. uucp (uucico)                     NO                YES
               11. cu login                          NO                YES
               12. POP Mail                          NO                 NO
               13. ssh utilities                     NO                YES

          Please note the following:

          1. Neither telnet(TC) nor telnetd(ADMN) consume licenses; it is the
             login(M) program run on the remote system that requests the user
             license and authorizes the login.

          2. Neither rlogin(TC) nor rlogind(ADMN) consume licenses: it is the
             login(M) program run on the remote system that requests the user
             license and authorizes the login.

          3. rcmd <machine> is the same as rlogin <machine>. Neither 
rcmd(TC)
             nor rlogind(ADMN) consume licenses; it is the login(M) program
             run on the remote system that requests the user license and
             authorizes the login.

          4. rcmd <machine> <command> does not cause login(M) to be run 
on the
             remote system.  Neither rcmd(TC) nor rshd(ADMN) consume licenses.

          5. rcp does not cause login(M) to be run on the remote system.
             Neither rcp(TC) nor rshd(ADMN) consume licenses.

          6. ftp does not cause login(M) to be run on the remote system.
             Neither ftp(TC) nor ftpd(ADMN) consume licenses.

          7. The dynamic PPP links use chat scripts and do, as part of the
             bring-up process, log into the remote system as a user, and cause
             the login(M) program to be run.  The PPP login is treated as a
             special case to prevent, for example, an rlogin(TC) over PPP
             requiring two licenses.  The login(M) program does not request a
             user license for the PPP login.

             The act of 'bringing up' the PPP interface does not consume
             a user license.  Networking commands running over the link may
             consume licenses as noted above.

          8. Static PPP links do not use chat scripts and do not log into the
             remote system during interface initialization. This means that
             login(M) is not run and no license is consumed.

             Networking commands running over the link may consume licenses
             as noted above.

          9. Login over a PPP link will consume user licenses as noted above.

          10. UUCP links (a login with uucico(ADM) as the shell) cause login(M)
              to be run and consume a user license.

          11. cu(C) causes login(M) to be run and will consume a user license.

          12. POP Mail does not cause login(M) to be run on the remote system.
              Neither pop3 nor pcipop(ADMN) consume licenses.

          The SCO OpenServer Desktop version, this is a Single User license.
          However, you can log in an additional user as root for system
          maintenance.

          Run "brand -t" to determine how many total user licenses are 
          available on a server.

          Run "brand -u" to determine how many of those licenses are currently
          consumed.

           The feature (-u) has been feature requested for UnixWare7.