PSRR Notes (Primary Server Route Repository)
Setting PSRR=Y (the default) indicates that if repository data cannot be retrieved locally, a request should be sent to the server to retrieve the data.
Setting PSRR=N turns off this feature.
To turn off this option it is recommended that you:
- Put PSRR=N into a profile file
- In your connection routine, put a USE SET_SESSION_VALUE (PSRR N) command to set the value on the fly. This should be done before you define and make the connection.
If you use the DEFINE_XXXXXXXX_SERVER BIF to connect to the server, the lock objects value can be set to R (which means route lock requests, route authority requests, and repository requests). To turn off, routing repository requests, set the lock objects value to something other than R AND do one of the above recommendations to set PSRR to N.
Some examples of the information that can be automatically retrieved from the server repository are messages, partition definition, help text and object descriptions for the help index.
Things you should know about using PSRR=Y (or an equivalent option) include:
- The use of PSRR=Y (or equivalent) has a performance impact because more trips to the server are required. For best performance, repository information needs to be available locally, in the *.xq* files or in a local database.
- Automatic help generation data is NOT retrieved from the Server if it is not found locally.
- System definitions and partition language definitions are NOT retrieved from the Server if they are not found locally. However, this information will be set to defaults and processing will continue.
- Only missing information is retrieved from the Server during application execution, as the server request is only generated if the data is not found locally. Therefore, changed information will not be retrieved. If definitions have changed, they need to be redeployed to the client.
For further information on this feature, please refer to 18.7 The .XQ* Files.