fP executables

[GCC Consulting]

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
> elestial.com] On Behalf Of Don Coleman
> Sent: Friday, January 26, 2007 2:56 PM
> To: 'Bob Rasmussen'
> Cc: 'filePro Mailing List'
> Subject: RE: fP executables
> 
> 
> Additional findings.  The CPU usage spikes to 30-50% while 
> the record is being written and spikes to 85-100% when the 
> form command is issued (from *clerk).  What I don't know is 
> if issuing the form command itself is spiking the processor 
> or if Print Wizard starting up (via PFPOSTPRINT in the
> environment) is spiking it.  Bob Rasmussen is assisting with 
> this (thanks
> Bob) and asked me to have Print Wizard print the file again 
> from a command line to check the CPU.  It did spike to 100% 
> for approx. 1 second and then returned to idle (2-6%).  
> 
> But what we noticed is in this table I issue the form 
> command, then do a quick gosub routine to post some printer 
> statistics and then return.  As soon as the return is 
> encountered and I return to the same line my gosub is on the 
> file I printed to is erased (0 bytes).  Bob says there is 
> nothing in Print Wizard erasing the contents of the file and 
> theorizes perhaps Print Wizard isn't quite done processing 
> the file and some function of fP is attempting to erase the 
> file, hence both are fighting for the file and causing a delay.
> 
> Any thoughts?
> 
> TYIA,
> 
> 
> Don Coleman
> Donald G. Coleman, Consultant

Don,

Try putting sleep "500" before the gosub to let printwizard finish what it
has to do.

The value is in milliseconds.

See if this helps.

Richard Kreiss
GCC Consulting