<snip> when you say not every CDE is built by z/os are you referring to the IDENTIFY Macro...? </snip>
No I am not. IDENTIFY is part of z/OS. I am referring to non-z/OS programs that obtain storage for CDE's and chain them into the z/OS control structures such as the job pack queue TCBJPQ. <snip> Also I noticed that the retry address is only 4 bytes. I guess then to you would have to retry to a label in the program that has RP instruction And have your recovery set it up before returning to RTM </snip> You noticed correctly. Neither retry addresses nor (more broadly) recovery routines can be above 2G. However, your guess is not what anyone is likely to do. The CVTBSM0F field was provided for this purpose. You set up 64-bit retry reg 15 to the address of your above-the-bar retry address. You make sure that that reg 15 will be used for retry (SETRP with RETRY15=YES, if an FRR; RETRY15 does not apply for ESTAE-type retry so that case is fine without RETRY15=YES). You set up the retry address to the address of CVTBSM0F (not the contents of CVTBSM0F, that would not work). You make sure retry is AMODE 64. Retry goes to CVTBSM0F, the instruction there which is BSM 0,X'F' takes you to the target located by reg 15. The system trace entry for that retry contains the value from reg 15, not the address of CVTBSM0F. Aside from the trace entry manipulation, you could accomplish this by yourself with some other register if you had a need. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
