Posted 15 August 2005 - 06:38 PM
Thanks in advance for your responses.
Posted 16 August 2005 - 03:33 PM
Some things to check:
/var/adm/syslog/syslog.log (or equivalent file for your 'nix flavour)
/etc/rc.log (or equiv...)
[Pro4 Bus] section in .ini - P4EVENTREPORTLEVEL=4 to try and aid in reporting.
TRACEGEN and TRACEDAEMON vars - I honestly can't remember there purpose, I'd have to re-read the manual for those.
Hope this helps in some small way
Posted 16 August 2005 - 03:47 PM
I also found that SET_RPTOPT seemed to be unreliable within Bus & Tasks environment, but the same function within the normal environment, it worked fine.
Edited by Rick Young, 16 August 2005 - 03:50 PM.
Posted 16 August 2005 - 04:19 PM
Posted 16 August 2005 - 06:23 PM
Example 3 from B&T manual in the DSL section. To use @RPTOPT. Set the device type (first field) to 10, and set the report device name to “API:OUTFMT=D” in the second field:
@RPTOPT = “10,API:OUTFMT=D,,,,,,Y,Y,Y”
The last three “Y”s are used to suppress the page header, the standard first line, and the initial page
eject, as those are not normally required. You can specify them if you wish.
Posted 16 August 2005 - 11:22 PM
I've found p4task a great tool for pinning down such things.
Although I've never struck your problem (where you are obviously producing printer output from a report), I encountered the opposite (where what should have been sent to a printer, instead got XML'd back out to the API).
No matter how illogical, have you tried creating basically a "dummy" U function for the Task to call, which in turn calls the R function?
Out of ideas
Posted 17 August 2005 - 11:55 AM
Thanks in advance.
Posted 17 August 2005 - 04:01 PM
I dont know if this helps or not, but I have seen non bus/task functions give the error "cannot successfully open print file" when the report generates no data, ie print for an empty select range etc.
Is it possible that you are not getting any output at all?
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users