Manage Learn to apply best practices and optimize your operations.

Follow-Up To "Let Your Agents Tell You When They Crashed"

Ok, using some code in your scheduled agents to enable them to tell you they
crashed and which line contains the problem is pretty cool.

But what do you do when you get the dreaded email ? First you read it to know
what'up. Then you figure out that the problem is at line # X (the line number
is written in the mail if you used the code in the tip "Let your agents tell
you when they crashed".

Now, tell me ... are you jumping in your script and scrolling down one line at
a time to figure out which line is causing the problem ? Here's another idea
you can use :

Go to your code, select it all and copy it to the clipboard [Edit-Copy].

Now, start Excel and paste it. Remove the first line [which is usually your Sub
Function_Name] and voila ! You can now scroll down to the appropriate line to
figure out which line is causing your problem.

I think that in R5, there is a line counter so you don't need to do that. This
is generally usefull for thoses, like me, who's infrastructure hasn't been
moved to R5 yet.

This was last published in November 2000

Dig Deeper on Domino Resources - Part 2

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

Search400

  • iSeries tutorials

    Search400.com's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...

SearchDataCenter

SearchContentManagement

Close