


GLB_OBJ.TXT(5)     Headers, Tables, and Macros     GLB_OBJ.TXT(5)



NNNNAAAAMMMMEEEE
     ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt - file specifying the object UUID of the  Global
     Location Broker

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     ////eeeettttcccc////nnnnccccssss////ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt  (Apollo  workstations  at  SR10.2   or
     later)
     ////eeeettttcccc////nnnnccccssss////ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt (other UNIX systems)
     nnnnccccssss$$$$eeeexxxxeeee::::ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt (VMS systems)
     \\\\nnnnccccssss\\\\ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt (MS-DOS systems)

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     The Global Location Broker (GLB) is an object identified  by
     a  Universal  Unique  Identifier  (UUID).   This  UUID has a
     default value.  The ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file allows you to  override
     the  default value by specifying a different GLB object UUID
     for a particular host.

     The ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file is used only in special  configurations
     that  require  several disjoint GLB databases (each of which
     is possibly replicated).  In most  networks  and  internets,
     there  is  only  one GLB database (possibly replicated), and
     hosts do not need to have a ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file.

     If a host has a ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file, the UUID in the file iden-
     tifies the GLB object to which that host will direct lookups
     and updates.  If  the  host  runs  a  GLB  daemon  (ggggllllbbbbdddd  or
     nnnnrrrrggggllllbbbbdddd),  the UUID also identifies the GLB object managed by
     that daemon, and the daemon will accept lookups and  updates
     only  for  that  object.  By specifying different GLB object
     UUIDs on different sets of hosts, you can partition  a  net-
     work or internet into Location Broker

     Location Broker cells have independent GLB databases.   Each
     cell  can  be  serviced by one ggggllllbbbbdddd, one nnnnrrrrggggllllbbbbdddd, or a set of
     ggggllllbbbbdddd replicas.  All hosts in a cell use the same GLB  object
     UUID.   Cells  need not correspond in any way to physical or
     logical network topology.

     _M_a_n_a_g_i_n_g _N_C_S _S_o_f_t_w_a_r_e describes how to set up  a  configura-
     tion that uses Location Broker cells.

     A ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file consists of one line containing the  tex-
     tual  representation  of a UUID, such as is generated by the
     uuuuuuuuiiiidddd____ggggeeeennnn utility.  The contents of ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt are identical
     on all hosts in a cell.

     If a host does not have a ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt file, it will use  the
     default value for the GLB object UUID.

EEEEXXXXAAAAMMMMPPPPLLLLEEEE
     The   following    is    a    sample    ggggllllbbbb____oooobbbbjjjj....ttttxxxxtttt    file:



NCS Configuration         Last change:                          1






GLB_OBJ.TXT(5)     Headers, Tables, and Macros     GLB_OBJ.TXT(5)



     _4444_3333_7777_ffff_2222_8888_eeee_7777_2222_0000_0000_0000_...._0000_dddd_...._0000_0000_...._0000_0000_...._ffff_bbbb_...._4444_0000_...._0000_0000_...._0000_0000_...._0000_0000

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     _M_a_n_a_g_i_n_g _N_C_S _S_o_f_t_w_a_r_e



















































NCS Configuration         Last change:                          2



