[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1063.0. "Problem with DECW$LOGICAL_NAMES " by EGAV02::MMCMULLIN (Ag senim ceol le poca� folamh) Wed Jul 05 1989 08:49

    
    I have a problem with the DECwindows logicals. DECdecision falls over
    with an error about not being able to open a file in
    decw$system_defaults. When I look at the logicals this is what I get.
    
    Egav02>dir decw$system_defaults:
    %DIRECT-E-OPENIN, error opening DECW$SYSTEM_DEFAULTS:[MMCMULLIN]*.*;*
    as input
    -RMS-F-DEV, error in device name or inappropriate device type for
    operation
    
    Egav02>show log decw$system_defaults/table = decw*
       "DECW$SYSTEM_DEFAULTS" = "SYS$COMMON:[DECW$DEFAULTS.USER]" (DECW$LOGICAL_NAMES)
            = "SYS$COMMON:[DECW$DEFAULTS.SYSTEM]"
            = "SYS$LIBRARY:"
    Egav02>
    
    SDC VMS v5.1.
    This happens on the boot node (6240) and workstation (GPX/II).
    
    Rgds,
    Maurice.
    

T.RTitleUserPersonal
Name
DateLines
1063.1Check RMS's logical table search list?KOAL::DUNCANWill Duncan -- Landover SICThu Jul 06 1989 07:3429
    We kinda had the same problem here . . . we were redefining the
    search list that RMS uses when doing its thing
    
    Try showing the logical names in the LNM$PROCESS_DIRECTORY table
    and be sure that DECW$LOGICAL_NAMES is there.
          
    It should look somthing like this
    
    $ show log /tab=lnm$process_directory

(LNM$PROCESS_DIRECTORY)

  "LNM$FILE_DEV" = "LNM$PROCESS"
	= "LNM$JOB"
	= "LNM$GROUP"
	= "LNM$SYSTEM"
	= "DECW$LOGICAL_NAMES" 
    
  "LNM$GROUP" = "LNM$GROUP_000044"
  "LNM$JOB" = "LNM$JOB_80412090"
  "LNM$PROCESS" = "LNM$PROCESS_TABLE"
  "LNM$PROCESS_DIRECTORY" [table] = ""
  "LNM$PROCESS_TABLE" [table] = ""
             
    What we were doing was stepping on the entry that DECW$Logicals.com
    makes in this table
          
    --Will

1063.2DECW$FORMAT_* logicals for processesBISTRO::CONNOLLYThu Jul 27 1989 07:2023
    I am also having a problem with the DECW$ logicals, or at least things
    are not working the way I would like them to.

    I have a system where several users are performing printing from such
    applications as MAIL. Since each user has its own printing requirements
    they are each using a different printer. Fine, they can select the
    desired printer and print as they wish. The problem arises when they
    try to set this printer up as their default printer. The printer must
    be reselected each time they enter the application. I was hoping to be
    able to define the default printer for each user through the use of the
    DECW$FORMAT_* logicals but they are only defined in logical table
    DECW$LOGICAL_NAMES which on my system is in LNM$SYSTEM_DIRECTORY not
    LNM$PROCESS_DIRECTORY as indicated in the previous reply.
    
    Is it possible to define the DECW$_FORMAT_* logicals for each login
    session, without privs, so they will take effect for process level
    application without chaning the system level definitions?

    Was the prior reference to DECW$LOGICAL_NAMES being in
    LNM$PROCESS_DIRECTORY a possible solution to this problem? If so how
    can I set up my system to contain DECW$LOGICAL_NAMES table in
    LNM$PROCESS_DIRECTORY instead of LNM$SYSTEM_DIRECTORY.

1063.3YesR2ME2::GRASSSteve GrassThu Jul 27 1989 10:459
>   Is it possible to define the DECW$_FORMAT_* logicals for each login
>   session, without privs, so they will take effect for process level
>   application without chaning the system level definitions?

Yes.  Users can override the default DECW$PRINTER_FORMAT_* logicals in their 
local LOGIN.COM file...

				steve