OK. It is how I thought of it because it was available in all macros. Also, it seemed to act more like a global than a local in that it seemed to retain a value across macros. I guess I need to somehow adjust my concept of it.
-- 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 > -----Original Message----- > From: IBM Mainframe Assembler List > [mailto:[email protected]] On Behalf Of Binyamin Dissen > Sent: Monday, April 16, 2012 7:38 AM > To: [email protected] > Subject: Re: &SYSNDX label for variable > > It doesn't look like a global. > > On Mon, 16 Apr 2012 07:17:46 -0500 "McKown, John" > <[email protected]> wrote: > > :>I was writing on my tablet at home when I posted that. The > "strangeness" is that although it looks like a GLBA, and the > value is "incremented" if used by a nested macro, the value > within a given invocation of a macro is "unchanging", unless > specifically set by code in the macro. > > -- > Binyamin Dissen <[email protected]> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > >
