There is some compatiblity/migration: if you run RACF with the exit active ( i.e. the passwords are hashed in the RACF DB). When you remove the exit, new passwords will be DES encrypted, but RACF still recognizes the hashed passwords.
But, once you ran RACF without the exit, there is no way back. So, each time one reinstalls RACF one must manually remove the exit or users can not logon. -- Kris Buelens, IBM Belgium, VM customer support 2007/5/26, Thomas Kern <[EMAIL PROTECTED]>:
It should be shipped with AES encryption as the default with DES and this exit as options. There should, of course, be large warnings about what defaults/options may be incompatible with prior releases of the product. It would be nice if the product could sense if the current settings are incompatible with the current database and provide some conversion mechanism to bring the old database up to the new settings. /Tom Kern
