• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
We do not have the PASSWORD-NO-USE-PERIOD defined yet in the tab100. We hope to implement this soon and in preparation for this ran some SQL reports against the z66. We find a LOT of records with 0 as the last login date. The earliest date I find is 20080103 and the latest is 20100216.

If we do not have this implemented, how are there dates in this field?

Resolution:
Looking at the v20 programs, I see that the Z66_LAST_LOGIN_DATE is populated only when the tab100 PASSWORD-NO-USE-PERIOD is not zero. Looking on other servers -- which also do not have PASSWORD-NO-USE-PERIOD defined --, I see that there are also cases where the Z66_LAST_LOGIN_DATE is populated, but mostly, as in your case, they are zeroes. (Perhaps the PASSWORD-NO-USE-PERIOD was temporarily changed to > 000 at some point? Or possibly the programs were different in the past.)

In any case, clearly, when you set PASSWORD-NO-USE-PERIOD > 000, the system starts checking and updating the Z66_LAST_LOGIN_DATE.

When the PASSWORD-NO-USE-PERIOD has passed, currently Aleph just gives the user an error message and blocks them from logging in. (They do *not* get prompted to change their password.)

• Article last edited: 10/8/2013