19 replies to this topic

[TomWhite]

We're trying to set up Bus and Task Processing in a Linux environment with windows clients using the latest versions - After much trial and error we've got the task communicating with the kernel at least. The problem we have now is it returns an error saying the function execution failed - how descriptive. We are able to run the function directly in VIP logged on as the same user the task is using - ruling out any type of security issues - does anyone have any experience with tasks and debugging these types of issues?
Thanks in advance for your responses.

[Rick Young]

Debugging this, is a right royal P.I.T.A.


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

-Rick

[TomWhite]

We've tracked this down to a - Cannot successfully open print file error - output is defined to go to 'API:OUTFMT=D' in $SPOOL. Is there somewhere else to check settings for this?

Thanks.

[Rick Young]

I chose to only use the API:OUTFMT=XE for outputting XML. For "real reports" (i.e. stuff to print on physical printers), I use @RPTOPT in either the function immediately preceding the R/GR function or in the Logic In of the R function.

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.

[TomWhite]

This function is being called solely from a task so the output option is hard coded - there's no need to set it up through @RPTOPT - I was just wondering if there was anywhere you have to set up something specific for tasks other than $SPOOL.

[Joseph Bove]

Tom,

I can't answer the bus and task side of this. However, CANNOT SUCCESSFULLY OPEN PRINT FILE is almost always a permissions error.

hth,

Joseph

[TomWhite]

Not sure what/where permissions would need to be set - it's my understanding that this should just return a CSV to the caller - not create a file/print job. Right now we're just using a VB task tester to call it.

[Rick Young]

Regardless of the fact that it ought not be "necessary"...try:
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.

[TomWhite]

Rick - I tried setting @RPTOPT in logic in as this report is the only function called from the task - the results were the same

[TomWhite]

Thanks Rick - but the 'dummy' update calling the report meets with the same results. You're right, it's definitely a report output issue - we've been successful with updates returning parameters. If anyone has any suggestions they would be most welcome.

Thanks in advance.

[TomWhite]

We are also on 4.11 of v5.5 - Tom

[Mike Schoen]

Tom,

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?

Mike