De nada. The bottom line would appear to be that if you want the user name, then control block chasing to the ACEE and picking up the ACEEUNAM seems to be a supported programming interface and should be safe.
Be aware of all of the potential issues of multiple ACEEs, no ACEE, etc. But for @Cameron's sort of situation -- "I have a batch COBOL program that runs every night and it wants to know the name of the user that owns the job" then control block chasing to ACEEUNAM should be fine. Charles On Wed, 31 Jan 2024 13:06:06 +0000, Peter Relson <[email protected]> wrote: >I had written ><snip> >At least in the past (I don't know if still true), there are cases where the >ACEE might be what, very loosely, is referred to as encrypted in which case it >would not be readable as-is. It's not truly encrypted such that you need some >cryptography to decrypt it, but the intent is that the security product know >what to do to provide you the "decrypted" info ></snip> > >Charles M helped me realize that I was mis-thinking. It's the utoken that can >be "encrypted", not the ACEE. >Thanks, Charles. > >Peter Relson >z/OS Core Technology Design > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
