This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
David, Check to make sure you haven't imposed a cpu limit on the executable size in your shell environment. Use the "limits" command. If you are restricting executable program sizes to say 8MB, then Garp may exceed that- especially if you have changed sizes in the .prm file. Presumably when you changes the .prm sizes, you completely removed all the library files in the $GEMLIB directory and rebuilt them from scratch- or else, you woul;d have problems with differing array sizes etc between newly compiled objects and previously compiled library routines. Steve CHiswell Unidata User SUpport On Mon, 10 Jan 2000, David S. Myers wrote: > Hi, > > We've got a DEC alpha that had been running garp which had been customized > a little (.PRM file edited a small amount to allow larger number of > gridpoints) > I've tried to patch that garp, with the y2k package, and now it won't > recompile. This may have something to do with the customization, but I > haven't figured it out. garp will build cleanly, but then on execution I get > the message > > 712:/scidata/NAWIPS/bin/osf/garp: /sbin/loader: Fatal Error: Program datasize > exceeds process datasize limit. > > Any ideas? > > -david myers >