Conference iosg::all-in-1_v30

2019.0. "New OA$DATA Logical to point to NETWORK.DAT?" by MSAM00::DOUGLASBURKE (Fleeting Edge of Technology?) Mon Dec 28 1992 02:03

    Customer question:
    
    Is it possible to allow only one small group of users access to
    NETWORK.DAT, instead of all ALL-IN-1 users?
    
    The question stems from the fact that they have higher-level management
    to whom they want to allow the ability to "see" special addressees, and
    at the same time wish to restrict others in the organization from
    having those addressees appear on GOLD-L's etc.  (As an aside, this
    customer does not and cannot use DDS).
    
    I suggested to them that they might be able to accomplish this through
    the use of logicals.  In otherwords, for that special group of users,
    they could have another OA$DATA logical search list which contains 
    another directory holding it's own special NETWORK.DAT.
    
    We tried this approach by creating an ALL-IN-1 logical name table, and
    pointing to it within the users table.  The actual tables, their order
    of appearance (search and translation) and contents are all shown below.
    
    Unfortunately, what we found is that ALL-IN-1 does not seem to look at
    this new logical name table for translation of OA$DATA.
    
    Therefore I have two questions:
    
    1.	Am I barking up the wrong tree...ie. can anyone suggest another
        approach?
    
    2.	Is ALL-IN-1 specifically looking at the SYSTEM logical name table
        for the translation of OA$DATA, and if not, what are we doing
        wrong?
    
    ----------------------------------------------------------------------
    
(LNM$PROCESS_TABLE)	[kernel]
			[no protection information]

(OA$LOGICAL_TABLE)	[exec]  [shareable]
			[Protection=(RWED,RWED,,RE)]  [Owner=[ALLIN1]]

  "OA$DATA" [exec] = "USER_DISK1:[TEST]"
	= "OA$SITE_DATA_SHARE"
	= "OA$SITE_DATA_LLV"
	= "OA$DATA_SHARE"
	= "OA$DATA_LLV"

(LNM$GROUP_000560)	[kernel]  [shareable,group]
			[Protection=(RWED,R,R,)]  [Owner=[560,0]]

(LNM$SYSTEM_TABLE)	[kernel]  [shareable,system]
			[Protection=(RWE,RWE,R,R)]  [Owner=[SYSTEM]]

  "OA$DATA" [exec] = "OA$SITE_DATA_SHARE"
	= "OA$SITE_DATA_LLV"
	= "OA$DATA_SHARE"
	= "OA$DATA_LLV"
  "OA$DATA_LLV" [exec] = "A1$DATADISK:[ALLIN1.DATA_ENGLISH]"
  "OA$DATA_SHARE" [exec] = "A1$DATADISK:[ALLIN1.DATA_SHARE]"

(DECW$LOGICAL_NAMES)	[exec]  [shareable]
			[Protection=(RWED,RWED,R,R)]  [Owner=[SYSTEM]]

    Hello,
    
    NETWORK.DAT is accessed throught form NETWORK.
    This form contains a pointer to the file which uses OA$DATA_SHARE,
    not OA$DATA   ......
    
    ;;.FILE;;
    
    OA$DATA_SHARE:NETWORK.DAT,OA$LIB_SHARE:NETWORK.FDL
    
    Regards,
    
    Jan
    

    .1's observation could give you a clue that you could give the
    "special" users their own version of the NETWORK form pointing to a
    special version of the file.
    
    Generally, we won't translate logicals out of tables other than the
    SYSTEM table, unless it's a co-existent/parallel system. This might be
    another avenue to explore.
    
    Remember to fix up the housekeeping utilities that convert/fdl and
    update across the network the NETWORK.DAT file to include your version
    to if necessary.
    
    Graham