Subject: RE: LE in ASM...programs
From: Meyer, Kenneth J (Kenneth.Meyer@ca.com)
Date: Mon Aug 08 2011 - 09:53:26 EDT
Sorry about being so cryptic, but it was sort of an inside joke between Martin and me. BEAR stands for Breaking-Event-Address Recording. Whenever an instruction other than the next one in sequential order is executed, the address of the instruction that causes the change is saved in the breaking-event-address register, which is moved to x'110' whenever a program check occurs. The instructions that alter this value are explained in the z/architecture Principle of Operations manual. Generally when there is a problem with a program, you can check the save area chain and determine how the program arrived at the event that caused the program check by using the values in the registers. With baseless coding, this can be much more difficult unless you from time to time save some indication of where you have been and where you are going. This could be an address, list of routines the code has executed, etc. Just something that would let it be determined what steps were taken that resulted in the ABEND. Ken -----Original Message----- From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Frank M. Ramaekers Sent: Monday, August 08, 2011 8:30 AM To: VSE Discussion List Subject: RE: LE in ASM...programs Ken, can you elaborate, "BEAR"? For the ones who are just now picking up on the Branch Relative instructions. snip..
This archive was generated by hypermail 2b25 : Wed Aug 31 2011 - 23:50:10 EDT