Apparently, they are different, because it didn't find it.
Using the STC name as the logonid for an STC goes back to the 1970s.
Also, it looks like you don't have a default STC name, which is fine.
But bottom line, at some point if you don't provide an acceptable logonid, you get:
ACF01004 LOGONID xxxxxxxx NOT FOUND.------------------------------
Fred Shay
Lead Mainframe Security Administrator
Email:
Fred.Shay@ensono.comM: +1 (815) 341-4876
www.ensono.com------------------------------
Original Message:
Sent: Aug 08, 2022 09:48 AM
From: Kevin Kinney
Subject: ACF01004
It's my understanding this is only necessary if the STC name is different than the ACF2 id.
In my question, the STC name is the same as the ACF2 id.
Thank you for your response.
Original Message:
Sent: Aug 04, 2022 10:54 AM
From: Fred Shay
Subject: ACF01004
You need to build an STCxxxxx record in GSO.
That's where you specify that the STC name and the logonid for it are different.
INSERT the record and refresh the GSO records.
Then start the STC to test it.
------------------------------
Fred Shay
Lead Mainframe Security Administrator
Email: Fred.Shay@ensono.com
M: +1 (815) 341-4876
www.ensono.com
Original Message:
Sent: Aug 03, 2022 03:33 PM
From: Kevin Kinney
Subject: ACF01004
Hello, we have a new ACF2 admin. I need a new test STC id based on the production id. i've verified he set it up, but I'm still getting the following -
IEF196I ACF01004 LOGONID xxxxxxxx NOT FOUND
ACF01004 LOGONID xxxxxxxx NOT FOUND
Under RACF, I'd exec a "SETR xxxxxx REFRESH" and I suspect he has to do something similar. I don't know the format.
How to we get ACF2 to acknowledge a newly defined ACF2 id?
Thank you.