Return
-
Title
Mainframe TS accounts failing to check password but change password is successful -
Description
Mainframe TS accounts failing to check password but change password is successful. -
Cause
The problem account may not have access to the dataset specified in the Custom Command field found on the Connection tab of the system.
The check password process uses the setbutteraddress command to check that the password is correct. It will set the buffer address to the value found in the Custom Command field.TPAM uses a command like this when checking the password:
enter(23,27) setbufferaddress(23,23) 'customCommandFieldValue'
If the account does not have access to that dataset an error like this will be presented:
field(protected,intensified) 'testUser userid logoffb% not authorized to use customCommandFieldValue ' setbufferaddress(3,1) startfield(protected,intensified) ' ' setb
-
Resolution
Create a new system with matching settings for everything besides the Custom Command field being set to blank or to the value that will make it work for the account that is failing to check its password.