Changing RACF password phrases by using client messages
When IMS Connect is configured to call RACF® directly, users of the user message exit routines HWSSMPL0, HWSSMPL1, and HWSJAVA0 can change RACF password phrases by submitting a client message that includes the password phrase change request keyword.
To enable this feature, you must bind the HWSPWCH0 object code with the user message exit routine you are using. The HWSPWCH0 object code is stored in the IMS.ADFSLOAD member of the distribution library.
The password phrase change request is similar to a password change request and it uses the same keyword. Therefore, the password change request keyword must appear at the beginning of the application data section of the message and be followed by a blank, the old password phrase, a blank, the new password phrase, a blank, and the new password phrase again. The password phrases must be enclosed in single quotation marks. If a single quotation mark is part of a password phrase, a second single quotation mark must follow it. There must be at least one blank between the password phrases.
llllIRMllzzHWSPWCH 'old_ phrase' 'new_phrase' 'new_phrase'|llzz
llllIRMOTMAllzzHWSPWCH 'old_ phrase' 'new_phrase' 'new_phrase'|llzz
The password change request keyword that is defined in the sample user message exit routines is "HWSPWCH." You can change this keyword by modifying the user message exit routine. Any password change request keyword that you define must be followed by a blank as a delimiter.
IMS Connect returns a response message to the client application in one of the following formats:
llzzmessage_textCSMllzz
llllmessage_textCSMllzz
llllOTMAheadermessage_textllzz
The communication sequence for a password change request is:
Procedure
- Connect.
- Send the password change request.
- Receive message HWSC00xxy, where xx is the final two digits of the message number and y is the message type identifier. If you are using HWSJAVA0, the IMS TM Resource Adapter client application receives the HWSC00xxy message in the application data portion of the OTMA header and the appropriate return and reason codes in the user data portion of the OTMA header.