We have reports stop in the middle of a listing (PDF and Excel), but then the next time you run them they are fine. It seems to be sporadic, but has been happening more often. It seems to be something to do with out environment, but we aren't sure where/how to look.

This message has been edited. Last edited by: <Kathryn Henning>,

Are they large, or taking a long time to load ?

Could it be timing out somewhere (Browser/Web Server, etc)

Use EXIT before PDF display(you can break at multiple places) and check if any warnings/errors. You can also check in webconsole, monitor agents for any error message.
Could be data problem, when you run next time or you executing with same filters?
Thanks,
Ram

quote:

Originally posted by Waz:
Are they large, or taking a long time to load ?

Could it be timing out somewhere (Browser/Web Server, etc)

They are both large and small reports. I don't see any time out errors, but I'm not sure exactly where to look. I also monitor the service agents, but it's not easy to tie them to the report/user that is being run.

quote:

Originally posted by Ram Prasad E:
Use EXIT before PDF display(you can break at multiple places) and check if any warnings/errors. You can also check in webconsole, monitor agents for any error message.
Could be data problem, when you run next time or you executing with same filters?
Thanks,
Ram

We can run it exactly the same two times and once it will work and the next time it will end in the middle. I have tried monitoring the agents, but have trouble tying which agent it is that belongs to that report/user.

so at the top of every fex

FILEDEF MYAGENT DISK DOCUMENTATION.TXT
-RUN
-WRITE MYAGENT &FOCFEXNAME &DATE &TOD

now in your agent you'll have a little text file called documentation that you have written to.
you can issue lots more -WRITE statements
eg
-WRITE after 1st extract lines are &LINES
and you can issue a
SLEEP 60
command in your code to make the processing stop for 60 seconds (any N), so you can read the little .txt file.

I put that "write" into one of my execs and it appeared to work fine, but I don't see it where I check the data service agents. I look at "data service agents" under the "workspace" tab on the database server. I know that our environment is a little different because our data (tables) are in Unix, but our execs are in Windows.

oh, you need to use Windows Explorer, have a drive mapped to the server
oh wait , you're in Unix
whats the equivalent in Unix, not Putty, the other thing, oh yeah, winscp its called.
Use winscp to Go look at your server
ibi/srv76/wfs/edatemp/ts{nnnnnn}
where each ts directory is a session, an agent.
go inside the highest numbered one, and if you only see stderr.log and stdout.log, then that agent isn't in use. Look at the next one up, until you find the one with your stuff in it.
In that directory you'll see your documentation.txt, your interim hold files and masters. That agent empties out when the report is done, but the SLEEP command will keep it from emptying for some number of seconds.

oh wait, your server is windows???
then you should update your signature to windows instead of unix.
How your data can be in Unix i don't quite get.
but anyway....
if your server is windows, then use Windows Explorer, and have a drive mapped to your server, and do the above steps.
very handy technique, this poking about inside your agents.