"It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts." - Arthur Conan Doyle
The ball is in his court to provide the raw data. Until then, that's a reasonable conjecture that needs to be verified. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jon Perryman <[email protected]> Sent: Monday, June 30, 2025 4:36 PM To: [email protected] <[email protected]> Subject: Re: Tried exec pgm= External Message: Use Caution On Mon, 30 Jun 2025 18:54:18 +0000, Seymour J Metz <[email protected]> wrote: > Telling us what TCB he's running under would narrow things down. Why make this so difficult at this point? It's almost guaranteed he's running in the wrong TCB otherwise none of the CMDAUTH programs would be working. As I suggested, a successful LISTUSER xxxx will tell us that TSO authorization is still functioning correctly and it's passing authorized commands to the correct task. He could also try using DITTO to look at disk. Ditto has to run authorized for a lot of functionality. I also suggested renaming ISRJ to LISTUSER to easily verify using a proven valid CMDAUTH entry. If he still gets an S047 calling it as LISTUSER, then a dump will probably be necessary. If Joseph was comfortable looking at dumps, then he would have been using it by now. ---------------------------------------------------------------------- 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
