I wouldn't be concerned with the capacity error message. That is one of those good old SGML days errors. I'm not even sure why Epic still allows it (other than the parser deals with it).
Capacity in the days before memory was abundant was a critical value. It could be changed in the SGML declaration (in fact the DOD upped the value in their declaration in 28001 long time ago).
There are a couple of other similar errors, litlen comes to mind, that are also now pretty much no longer needed.
---- "Benton wrote:
> I got this question from a co-worker:
> When I compile our CAEWriter doctype, I now get a capacity. For the moment, I've stopped using the -cap arg. Should I be concerned?
> From my ANT log:
> [exec] Current OS is Windows XP
> [exec] Setting environment variable: APTCATPATH=
> [exec] Executing 'D:\program files\Arbortext\Editor\bin\dtgen' with arguments:
> '-//LMSSC//DTD XML//CAEWriter Minimal Revisable Units 2.1.1//Vulcan//EN'
> The ' characters around the executable and arguments are
> not part of the command.
> [exec] Writing file F:\AdvSysBuildArea\VulcanRelease\Builds\informal\Ancillary\doctypes\caewriter\211\vulcan-cae.ptd
> [exec] Dtgen Parser Warning:
> [exec] While parsing file F:\AdvSysBuildArea\VulcanRelease\Builds\informal\Ancillary\doctypes\caewriter\210\cae-procedure.elm:
> [exec] Total program capacity exceeded.
> [exec] The value now required is 250;
> [exec] the total capacity used so far is 999799
> [exec] and the declared maximum is 1000000
> [exec] (err:515 line:101 pos:5542)
> [exec] Result: 1
> [copy] vulcan-cae.dec added as vulcan-cae.dec doesn't exist.
> [copy] vulcan-cae.pro added as vulcan-cae.pro doesn't exist.
> [copy] vulcan-cae.ptd added as vulcan-cae.ptd doesn't exist.
> WE used to get string capacity warnings(errors?) when we had a SGML doctype. This was caused by having too many entities in our doctype. I don't think that this is the cause of this "problem". Does anyone have any experience or knowledge about this "program capacity exceeded" error?