Makes sense. They are becoming fewer as I gain experience. -- John McKown Systems Engineer IV IT
Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Assembler List > [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of John Ehrman > Sent: Monday, January 09, 2012 3:58 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Wish list for message ASMA058E > > There are three main reasons for flagging a relative target > address: odd > boundary (as you noted), too far away, or in a different > control section. > At the time HLASM added relative-address support, we thought that the > frequency of such addressing errors would be very low, so > that separate > messages wouldn't be necesary. >
