HTTP problems

I'm running Apache on V5R1 and have been for some time.  Last Sunday we
loaded a PTF and now Apache encounters thread errors several times a day
and suts itself down.

The job log reports the following errors (in an 1100+ page joblog ):

CPF9898    Information             40    QZHBCGI        CGILIB     
*STMT    QZHBCGI      CGILIB       *STMT

>From module . . . . . . . . :   CGIPARSE
 From procedure  . . . . . . :   ErrorExit__FiPc
 Statement . . . . . . . . . :   470
To module . . . . . . . . . :   CGIPARSE

To procedure  . . . . . . . :   ErrorExit__FiPc
 Statement . . . . . . . . . :   470
 Message . . . . :   QzhbCgiParse: Error: No matching field name found.
.      
 Cause . . . . . :   This message is used by application programs as a
general
   escape message.


    MCH6902    Escape                  40      
#hmfremi                   000268   QZHBCGI    CGILIB       *STMT

To module . . . . . . . . . :   CGIPARSE 
 To procedure  . . . . . . . :   CGIParse_send_error__Fv
 Statement . . . . . . . . . :   476          *PRCLT
 Message . . . . :   The requested heap space operation is invalid.
 Cause . . . . . :   The requested heap space operation is invalid. The
heap
   space identifier is 0. The activation group mark is 1. The activation
group
   mark will be zero if the heap space is not associated with an
activation   
   group. The error type is 2. The error type indicating why the heap
space   
   request is invalid is defined as follows: 0001-Attempt to destroy the
   default heap space; 0002-Attempt to free or reallocate heap space
storage   that is not allocated; The heap space identifier and
activation group mark
   may not be valid for this error type; 0003-Access to the heap space
is not
   allowed; 0004-Attempt to mark a heap space that cannot be marked;


The first error should be no big deal, we test for form parameters that
aren't sent all the time.  The second message is what kills the job.

Has anyone seen anything like this?  My BP is checking for another ptf
but it doesn't look promising.  Have the rules changed for CGI_PARSE ???

Thanks,

Joel