Ken - From my notes at http://people.bu.edu/rbs/ADSM.QuickFacts :

ANS1075E *** Program memory exhausted ***
        *SM thinks: The program has exhausted all available storage.
        *SM recommendation: Free any unnecessary programs, for example,
        terminate and stay resident programs (TSRs), that are running and retry
        the operation. Reducing the scope of queries and the amount of data
        returned can also solve the problem.
        If a Unix system, check Unix Limits values.  Assure that the system is
        not running out of virtual storage.  If AIX, you may be in need of more
        than the single memory segment that AIX allows by default, which you can
        go beyond via Large Program Support conventions.  The scoop:
         The amount of memory that the process needs may exceed the size of one
         data segment (256 MB), which is the default number of segments a
         process may use.  The process is in this case killed by the system.
         The work-around for this is to enable the program to be able to use
         more than one data segment by enabling Large Program Support, using the
         following commands:
                cp -p <Pgm_Name> <Pgm_Name>.orig
                cd /usr/lpp/adsm/bin
                /usr/bin/echo '\0200\0\0\0' |
                 dd of=<Pgm_Name> bs=4 count=1 seek=19 conv=notrunc
         which causes the XCOFF o_maxdata field (see <aouthdr.h>) to be updated.
         This allows the program to use the maximum of 8 data segments (2 GB).
         Choose the string to use for a given number of data segments from
         the following table:
                # segments    vm size       string
                ------------------------------------------------
                8             2 GB          '\0200\0\0\0'
                6             1.5 GB        '\0140\0\0\0'
                4             1 GB          '\0100\0\0\0'
                2             512 MB        '\040\0\0\0'

 Richard Sims, BU