🚀 go-pugleaf

At the two sites that I have managed I used the following assumptions for 
what was in the system-wide login.com
  1) If it is a network login, bypass the entire login.com; but do execute
the users login.com (so he can bypass it if he wants).  This was done for
speed.  Most of the network accesses do not need the logicals and symbols.
They could define what they needed.
  2) for Batch jobs I skipped over the definiton of symbols and logicals that
would only be used in interactive modes.  These included INQUIRES, setting
terminal, and some processes that only run interactively.  

The sample login.com provided to each user likewise had the tests for the
various classes of user so that they could learn to group the symbols by where 
they would be executed.  

I feel that it is often best to define a symbol that will load the symbols
needed by a program, rather than force everyone to incurr the overhead of 
loading all of the sysmbols needed for each software package on the system.
One of the systems I have to occasionally use, takes over 10 cpu seconds
(some times this is 1-2 minutes wall clock) to execute the system-wide login.com
All of this just so I can check and see if I have any mail.  I
definitely do not need to have all of the symbols loaded so that I can
run Eunice, Oracle, Ada, Issco, DI300, SAS, VIS1ON, MASS-11 and a
bunch of locally developed packages.  If a few symbols had been
defined to point to the initialization files, the user could at login
or later select what symbols he wanted to load.


 
     
*
*---Art
*
*Arthur T. McClinton Jr.     ARPA: ART@MITRE.ARPA
*Mitre Corporation MS-Z305   Phone: 703-883-6356
*1820 Dolley Madison Blvd    Internal Mitre: ART@MWVMS or M10319@MWVM
*McLean, Va. 22102           DECUS DCS: MCCLINTON
*

  =-=- This note is in response to yours which follows -=-=



Our system-wide login.com procedure does a variety of site-dependant things
for users.  We bypass it entirely for network logins (if f$mode() .eqs.
"NETWORK" then $exit).  This is nice and quick for remote file access, and
it avoids problems with user login.com files doing things like $INQUIRE;
however it means that system-wide symbols and user generated symbols and
logicals are not available.  What do other people do?  Any comments?

								John Child