MVSFORUMS.com

errolvs

Hi Folks. We have upgraded the TOR from TS1.3 to TS3.1 and get an Abend DFHSN0001 683/AKEB when running a local signon Trans from the TOR itself. The AORs are still 1.3 but that should not matter because the signon is local to the TOR. The abend code 683 indicates that a RACROUTE REQUEST=VERIFY was not APF authorised, yet the issuing module is in an APF authed library. I have found a similar error from someone running ACF2 in IBMs problem database in which the solution was to add the MUSASS attribute to the Adress Space ACF2 ID.
We run our regions from a batch startup for historical reasons, so I wonder if TS3.1 does not allow this anymore

kolusu · Posted: Wed Nov 22, 2006 3:06 pm Post subject:

errolvs,

Look up issues 7 thru 10 in the below link and see if they are applicable to you

http://www.ibm.com/Search/?q=AKEB&v=14&lang=en&cc=us&en=utf

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

errolvs · Posted: Thu Nov 23, 2006 9:52 am Post subject:

Thanks kolusu! I have already checked that out and the only relevant problem was the ACF2 (very close match but we run RACF) and the solution is not applicable to a RACF shop. We have sent a dump to IBM