cdsbrowser(1m) [hpux man page]

cdsbrowser(1m)															    cdsbrowser(1m)

NAME

       cdsbrowser - Starts the CDS Browser utility on the local system

SYNOPSIS

       cdsbrowser

DESCRIPTION

       The cdsbrowser command starts the CDS Browser utility on the local system.  This utility runs on workstations with windowing software based
       on the OSF/Motiftm graphical user interface.  Using a mouse to manipulate pull-down menus, you can view the directory structure of a names-
       pace,  view child directories of a particular directory, view the object entries and soft links in a directory, and set a filter to display
       only object entries of a particular class. (For users who do not have windowing software, similar functions are available with the  control
       program.)  When you use the CDS Browser, it sets the confidence level of clerk calls to low.

   Privilege Required
       None

EXAMPLE

       The following command starts the CDS Browser utility on the local system: $ cdsbrowser

RELATED INFORMATION

       Books: OSF DCE Administration Guide

																    cdsbrowser(1m)

nondcesvc(4)															      nondcesvc(4)

NAME

       nondcesvc - file for dceping(8) that lists non-DCE services.

DESCRIPTION

       dceping will ping services named in nondcesvc.

       Supported naming conventions for this file are:

	 o  CDS Name. Example entry:

	    /.:/hosts/foo/someService NAMESPACE PROMPT
	    /.:/hosts/foo/someService NAMESPACE NOPROMPT

	    You can find CDS namespace entries by using the cdsbrowser(8) command.

	 o  RPC String Binding. Example entry:

	    ncacn_ip_tcp:foo.entity.company.com[1755] STRING_BINDING

	    You  can  obtain  string  bindings from the endpoint map maintained by rpcd.  Use the command: rpccp show mappings. Note that the host
	    name (foo.entity.company.com in the example) can be replaced with the IP address.

	 o  RPC Service Interface ID. Example entry:

	    someOtherService INTERFACE_ID hostname

	    When using this form of name, also include the same entry in the wellknownif file.

       Note in the examples above that NAMESPACE, STRING_BINDING, and INTERFACE_ID are literal strings that identify which  naming  convention	is
       being  used.   PROMPT is a literal string that will associate a login context with the NAMESPACE Entry.	This keyword will cause dceping to
       prompt the user for a principal and password that has sufficient rights to access the Entry.  NOPROMPT does not	cause  prompting.   PROMPT
       and NOPROMPT are supported by the NAMESPACE naming convention only.

       Environment  Variables  are  supported  in  the	Service Name.  Use of these is similar to environment variable usage in the shell with the
       exception that the variable must reference an absolute name, and not another environment variable.  Use of environment  variables  is  sup-
       ported in all naming conventions.

	 o  Environment Variable Name. Example entry:

	    /.:/hosts/foo/$SOME_SERVICE NAMESPACE PROMPT
	    /.:/hosts/foo/bankServer$(CITY)$(STATE) NAMESPACE NOPROMPT
	    $(SECD_STRING_BINDING) STRING_BINDING
	    $(SECD_INTERFACE_ID) INTERFACE_ID hostname

       If you do not know the names of services that you want to ping before dceping is run, and/or you would like to determine such names at run-
       time by providing your own function, you may do so through an entry of the following form in nondcesvc:

       full_path_name_of_your_executable BUILD_SVCNAMES

       You specify your function's full path name in full_path_name_of_your_executable followed by the literal string BUILD_SVCNAMES.  Your  func-
       tion  should  generate,	on its stdout, a file identical to the nondcesvc file with one difference. The output of the executable should not
       have any BUILD_SVCNAMES entry. It can however have any number of NAMESPACE, STRING_BINDING or INTERFACE_ID types of entries.

       Blank lines or lines beginning with # are ignored. You can use either spaces or tabs to separate items in a line. The string, endNonDCESvc,
       must occur in the last line of the file as an end of file indicator.

FILE

       /opt/dcelocal/hpadmin/etc/nondcesvc (for HP-UX version 9.x)
       /etc/opt/dce/hpadmin/etc/nondcesvc (for HP-UX version 10.x)

SEE ALSO

       dceping(8), wellknownif(4), rpccp(8), cdsbrowser(8)

HP DCE
																      nondcesvc(4)