One thing I'm not clear on is what you mean by "allow our clients to pull reports to the web server". I can think of 3 scenarios:
1. Individual client PCs have PCL reports stored on them (perhaps generated and transferred from the A-Shell/UNIX server), and you want to provide a means for the users to upload them to the web server for conversion to PDF and then download them for viewing. Here, you would probably need some kind of web app that can handle the upload operation and pass the file through the converter. (Or, perhaps someone has a PCL-to-PDF converter that can be downloaded from the webserver to the PC to operate there?)
2. The reports on the the application server, and you want users to somehow access them via the web server and convert them to PDFs for viewing. This is a little simpler, since no upload operation is needed. You just need a CGI script to run the conversion, perhaps copying the PDF to some web-accessible spec, and then create a new page with a link to it. You might also just decide to convert every report to PDF and archive them in advance, perhaps copying them to some secure area of your web server, in which case the users can just log in and browse their reports.
3. The reports have not been generated yet when the user requests to view them. In this case, an A-Shell CGI process makes the most sense - it launches an instance of A-Shell to generate the report, convert it to PDF (perhaps via some kind of XCALL HOSTEX call to whatever PCL-to-PDF tool you use), then generate a page that links to it.
As for the best PCL-to-PDF tool, I'm not sure, but I expect we'll hear from someone with a recommendation before too long...