On 10/29/2014 7:50 AM, [email protected] wrote:
I appreciate all of the responses. I did a profile prefix(atljp), which fixed
the problem. I have never seen such an odd occurrence in ISPF before.
John
John,
This is not an ISPF issue. The corruption of the PREFIX data is a
serious issue affecting your external security manager (ESM, such as
RACF, ACF2, or TopSecret). I'm assuming you have an ESM and are not
using UADS. The TSO PROFILE PREFIX command can't corrupt the data and
store a value > 8 characters. This is a bad problem to have, and you
should continue to research to figure out what happened. The earlier
suggestion to unload your ESM database to check the prefix value is a
good one. You should check to see if other prefix values are corrupted,
and if so, open a PMR with your ESM vendor
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
