OSI/MHS Management Programming Manual

Password Server Interfaces
OSI/MHS Management Programming Manual—424824-001
7-10
Password Server Process Failures
As with the MS process, the MHS manager performs a WRITEREADX to send an
SPI-formatted request to the password server process, and receives back an
SPI-formatted reply. However, this is implemented as a true nowaited interface
whereby the MHS manager can perform other processing and service requests made on
it before the password server replies. The MHS manager does impose a timeout on
requests to the password server.
The MS password server process does not inherit any TMF transactions from either the
MS or the MHS manager processes.
Password Server Process Failures
If the MHS manager fails to communicate with the password server process (either
because of a process failure or a timeout), then it is not possible to add, alter, or delete
an APPL object whose MS group is configured to use that password server process.
If the MS process fails to communicate with the password server process (either because
of a process failure or a timeout), then it is not possible for that MS APPL object to bind
to the MS or to use the register-MS service.
In the event of a process failure, retry the command to make sure the request succeeded.
In the case of an MS register command, retry with the old password and then with the
new password.
Command and Response Definitions
There are five types of SPI requests and five types of responses. All contain the
standard SPI command and response header, where the fields are defined as:
•
SSID — the OSI/MHS subsystem ID
•
Header type — the value of ZSPI-VAL-CMDHDR
•
Command — the value of 0
All requests contain the following tokens:
ZMHS-MAP-PASSW-SERVICE
ZMHS-MAP-PASSW-COMMAND
ZMHS-MAP-APPL-NAME
Command and Response Tokens
The definitions of SPI commands and responses for the MS password server interface
are as follows:
Tokens in Command Buffer
ZMHS-MAP-PASSW-SERVICE
def ZMHS-DDL-PASSW-SERVICE.
02 ZVALUE token-type ZSPI-TYP-INT.
end.