T.R | Title | User | Personal Name | Date | Lines |
---|
279.1 | No idea | SIOG::T_REDMOND | Thoughts of an Idle Mind | Thu Mar 19 1992 14:54 | 5 |
| I have no idea why the script bombed out. It's ALL-IN-1 that is
ACCVIO'ing and so many things may have caused it. Did you clear all the
previous run details before starting to run the CART?
Tony
|
279.2 | CART resolution script Acc Vios here too! | AIMTEC::DONOHUE_F | | Mon Mar 23 1992 14:18 | 24 |
|
In an ALL-IN-1 V3.0 pilot training class, we ran the CART on
a system that had few customizations, then ran this script and
the first time it ran for a fairly long time then also failed
with an Access violation!
As there is no logging done by the procedure, it was almost impossible
to determine what it had done and what still needed to be done
so that only the necessary part could be rerun again.
It would be very helpful if the procedure could write to a log
as it processes each element, just in case it fails so that it
would be easy to go back and edit the procedure and process only
thoses elements that it didn't get to.
As this script is VERY large, can you give some ideas as to what
if any process quotas to look at that could be causing the
failure?
Any hints in troubleshooting a failure to complete this script
would be helpful.
Faith
|
279.3 | Something to look at | SIOG::T_REDMOND | Thoughts of an Idle Mind | Mon Mar 23 1992 14:23 | 5 |
| FILLM, BYTLM, PGFLQUOTA, WSEXTENT would be good parameters to increase.
I normally double these whenever trouble strikes - an inelegant but
mostly effective approach.
Tony
|
279.4 | Good idea - do it. | FAILTE::LAAHS | Two Cute Celts are better than one | Tue Mar 31 1992 13:58 | 13 |
| >It would be very helpful if the procedure could write to a log
>as it processes each element, just in case it fails so that it
>would be easy to go back and edit the procedure and process only
>thoses elements that it didn't get to.
The script can be edited before you run it to do this.
For each element in conflict the script calls the relevant
CM_CART_SCRIPT_<x>.SCP. and acts upon the element defined in #CM_KEY.
Therefore merely putting a print to a log file or an OA$DISPLAY in these
scripts will do what you want.
Kevin
|