Hi Alejandro,
I've taken a look to the link you provided. It's essentially the same thing we are configuring but 2 items are different for us:
1) We are using the printer driver provided with Ghostscript instead of Ricoh printer used in your documentation. The driver is called ghostpdf and it is available in the lib subdir of your ghostscript installation. When you install the printer browse to the ghostscript lib subdir and you will find it!
2) In "Multi File Port Monitor" we are configuring the file name to be generated as %t.pdf. With this configuration the PDF file is assuming as name the instance name of your printing Uniface component; in this way any Uniface application can easily recognize the PDF file is generating and its name can be uniquely driven by the programmer to avoid any overwriting.
About PDF file with size equal 0 (zero), defining your PDF generation you should take in consideration the asyncronous execution of printing jobs on ALL platforms:
when a printjob is executed is taken in charge from spooling subsystem; when your Uniface application is getting back control to your ProcScript it does NOT mean your PDF is already completed. You should wait a little bit for its completition (convertion from PS to PDF is taking place); syncronization between the two subsystems (your Uniface application and spooling subsystem) is up to you and could be implemented in many different ways. It is a best practice to include this waiting stage in a global proc to be generically called to "print to PDF file".
With this configuration a shared printer on a server can be easily used at LAN level.
Hope again it helps...
Gianni