VMS Help DCE_RPC, Application Routines, rpc_ns_mgmt_inq_exp_age  *Conan The Librarian (sorry for the slow response - running on an old VAX)

 NAME

   rpc_ns_mgmt_inq_exp_age - Returns the application's global expiration
                             age for local copies of name service data

   Used by client, server, or management applications.

 SYNOPSIS

   #include <dce/rpc.h>

   void rpc_ns_mgmt_inq_exp_age( unsigned32 *expiration_age,
                                 unsigned32 *status );

 PARAMETERS

   Input

   None.

   Output

   expiration_age
       Returns the default expiration age (in seconds). All the RPC Name
       Service Interface (NSI) read operations (all the next operations)
       use this value.

   status
       Returns the status code from this routine.  This status code
       indicates whether the routine completed successfully or, if not,
       why not.  The possible status code and its meaning is as follows:

       rpc_s_ok              Success.

 DESCRIPTION

   The rpc_ns_mgmt_inq_exp_age() routine returns the global expiration
   age that the application is using.  The expiration_age parameter
   represents the amount of time, in seconds, that a local copy of data
   from a name service attribute can exist before a request from the
   application for the attribute requires updating the local copy.  When
   an application begins running, the RPC runtime specifies a random
   value of between 8 and 12 hours as the default expiration age.  The
   default is global to the application.

   The RPC NSI next operations, which read data from name service
   attributes, use an expiration age.  A next operation normally starts
   by looking for a local copy of the attribute data that an application
   requests.  In the absence of a local copy, the next operation creates
   one with fresh attribute data from the name service database. If a
   local copy already exists, the operation compares its actual age to
   the expiration age being used by the application.  If the actual age
   exceeds the expiration age, the operation automatically tries to update
   the local copy with fresh attribute data from the name service database.
   If updating is impossible, the old local data remains in place and the
   next operation fails, returning the rpc_s_name_service_unavailable
   status code.

   Applications normally use only the default expiration age.  For special
   cases, an application can substitute a user-supplied global expiration
   age for the default by calling rpc_ns_mgmt_set_exp_age().  The
   rpc_ns_mgmt_inq_exp_age() routine returns the current global expiration
   age, whether it is a default or a user-supplied value.

   An application can also override the global expiration age temporarily
   by calling rpc_ns_mgmt_handle_set_exp_age().

   Permissions Required

   No permissions are required.

 RETURN VALUES

   No value is returned.

 RELATED INFORMATION

   Functions: rpc_ns_mgmt_handle_set_exp_age
              rpc_ns_mgmt_set_exp_age