On 9/20/06, Schuh, Richard <[EMAIL PROTECTED]> wrote:
We have some vendor code, actually ESAWEB is being installed, that has a
pipeline in it that looks like this:
address 'COMMAND' 'PIPE stem xyz. | OUTPUT'
This is unique to the vendor's code. There is a pipeline filter
package that defines the 'output' stage which is what the CGI can use
to output data to the browser.
My guess would be that something bad happened earlier that caused an
abend in a stage of that package and CMS Pipelines then dropped the
filter package. If you look back in the console log of the web server
you may spot the original error. If I am correct, then restarting the
web server should make it go away.
But since you deserve better than me guessing at problems, I have left
it to the expert.
Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/
