PRINT DOCUMENT is a server-based function that outputs the document to the Lpt1 port or designated print queue on an AwareIM server. You would only use this function if your AwareIM server is running on a local intranet and serving a particular print queue for users on the LAN
The fact that you are developing on your local machine and your AwareIM server is also local, PRINT DOCUMENT seems to work, but it won't work when you go to the cloud or WAN. This is probably what's confusing you. Forget about using PRINT DOCUMENT
As to DISPLAY DOCUMENT, this is all that you have to work with. When you DISPLAY DOCUMENT a PDF, it automatically opens the PDF in your browser because you have a PDF reader installed on your machine and its associated to the default file extension .pdf . If you had no PDF reader installed, the result of a DISPLAY DOCUMENT action would be a pop up window prompting you to "save file" or "open with" or autosaving in the background to a given folder,depending on browser settings. So it depends on how your users browser is set up and also if there is a default association with regards to the application(in this case) that opens a .csv file. (normally a .csv file does not have a default association). So the behaviour is, download file in background or prompt users to save. The same goes for a .DOC file , if WORD is not installed on the users machine it would prompt the user to " Save or Open with"
Also bear in mind , if there is no default association to the file extension on the users machine and the Browser Download settings are set to automatcally download to a specific folder, there would be no prompting of the user to "open or save to" it just goes ahead with the download in the background.
I cant see why you have 2 x DISPLAY DOCUMENT in your process - so I can't comment on the this one, but hopefully what i have described above, puts things in a better perspective for you to resolve your problem