CMS is good about protecting its segments.

CMS loads several segments at startup (QUERY SEGMENT).  The macroes
that get storage should not get storage in use by the segments.

If the program needs no other segments while runnnig.  It should be
fine.  If you need a segment not loaded, then SEGMENT LOAD segment_name

You should only need to make sure the userids running the program have
enough virtual storage.  In today's world, 32M-64M and larger is not
a problem as it was back in the HPO days.

Others much more knowledgable about ASSEMBLY programming may give you
better answers.

Jim

Reply via email to