When the Directory Server linkage facility is used, the pdgrprfl command updates to the most recent status the user and role information maintained in memory by HiRDB.

You should execute the pdgrprfl command in the following situations:

• When you have added, changed, or deleted a user or role with the Directory Server
• When you have added, changed, or deleted a member in a role

This command enables you to establish connection with the HiRDB using the most recent user information provided by the Directory Server. It also enables you to use table access privileges on the basis of the most recent role information in the Directory Server.

For details about the Directory Server linkage facility, see the HiRDB Version 8 System Operation Guide.

HiRDB administrator

pdgrprfl

None

1. You can execute the pdgrprfl command while HiRDB is active.
2. You can execute the pdgrprfl command on the server machine containing the single server or the server machine where the system manager is located.
3. The pdgrprfl command is available only when the Directory Server linkage facility is used.
4. Do not execute more than one pdgrprfl command at any one time.
5. If you execute the pdgrprfl command, the buffer hit rate for the table definition information and user privilege information reduces temporarily.

1. Return code 0 for the pdgrprfl command indicates normal termination, and return code 8 indicates abnormal termination.

1. You can execute the pdgrprfl command whether or not a front-end server is running. However, if there is a front-end server that is preparing to start or stop, the pdgrprfl command terminates with an error.
2. If you execute the pdgrprfl command when it cannot be determined whether or not a front-end server other than a recovery-unnecessary front-end server is running, an error results because the user or role information in the front-end servers cannot be updated. If you execute the pdgrprfl command when it cannot be determined whether or not a recovery-unnecessary front-end server is running, the command skips that front-end server. Its user or role information is updated to the most recent status later when it is restarted.
3. The following table provides details of the relationship between the front-end server activity status and the pdgrprfl command:
   

   pdls -d svr command execution result		Front-end server status	pdgrprfl command execution result
   Unit	Server		Recovery- unnecessary front-end server	Other front-end server
   STARTING	STOP	Initial status	Command terminated with error.	Command terminated with error.
   STARTING	STARTING	Preparing to start	Command terminated with error.	Command terminated with error.
   ACTIVE	STARTING
   STARTING	STARTING	Preparing to start (server process has already started)	Command terminated with error.	Command terminated with error.
   ACTIVE	STARTING
   ACTIVE	STARTING	Ready to start	Command processing executed.	Command processing executed.
   ACTIVE	SUSPEND
   ACTIVE	ACTIVE	Running	Command processing executed.	Command processing executed.
   ACTIVE	TRNPAUSE
   STOP		Stopped due to reduced mode operation	Command processing skipped.	Command processing skipped.
   ACTIVE	STOP	Stopped by individual server stop command
   STOP(N)		Stopped by normal termination	Command processing skipped.	Command processing skipped.
   STOP(F)		Stopped by forced termination	Command processing skipped.	Command processing skipped.
   STOP(A)		Server activity status unknown because unit shutdown was detected	Command processing skipped.	Command terminated with error.
   STOPPING		Preparing to stop	Command terminated with error.	Command terminated with error.
   ACTIVE	STOP	Ready to execute the database recovery utility (after executing the pdstart -r command)	Command terminated with error.	Command terminated with error.

Legend:

: Not applicable