To be clear: are you saying that when you did not specify SDWALSLV at all you get 60D-14, and when you specified it with a value of 1 you did not?
<snip> This what I see for 60d .... </snip> It is just ridiculous that you continually ignore what someone writes, and then post only what you think matters instead of everything. The "explanation" is one piece of the information in the documentation. There are also the "actions". They are relevant too. Read them. In particular the one I referred to. You never described the order of SETFRR (or implied SETFRR if you scheduled the SRB to be given control with an FRR) vs BAKR vs PC. That must be understood. If the order is SETFRR A BAKR PC to IARV64 PR PR Then if you want to retry within the BAKR code you would need SDWALSLV = 1. If you want to retry prior to code running without that linkage stack level, then SDWALSLV should be left 0. If the order is BAKR SETFRR A PC to IARV64 PR SETFRR D PR It would be 100%y WRONG for you to retry with SDWALSLV=1. That would be considered a system integrity error. The retry address has to be owned by you and the retry has to be at the linkage stack level associated with that address. 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
