I'm just getting into really using relative addresses. In the past, I've basically only been using Branch Relative (BRC or J..) instructions. So, no problems, because instructions automatically align to a halfword boundry. But I've starting using LARL for getting addresses. And I consistently forget to force a halfword boundry. So I occassionally get:
ASMA058E Invalid relative address - optmsg1 And I'm puzzled as to what went wrong. I __assume__ the assembler knows the real reason, of the few possibilities. It would be nice if I would get something like: ASMA058E Invalid relative address - optmsg1 - not on halfword boundry for a "slap in the head". Yes, I'm getting used to it. But the very first time I got it, I was totally mystified. Yes, I did find the message in the book. But I would have saved myself a few minutes of searching if HLASM could have given me that reminder about the halfword boundry requirement. Not a big deal, since the problem is going away as I do more relative instructions. But for a newbie, it might be helpful. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * 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
