Ambiguous Error Messages
Posted: Tue Oct 12, 2004 7:30 am
I'm having a good deal of difficulty finding meaningful information in the PX error messages. Most of the error messages I am getting at run time seem to give no information as to which field, row, or sometimes even which stage the error is pertaining. This is causing development and testing to take A LOT longer than using other developmet tools. Management is even considering dropping the use of Ascential in favor of other tools.
To be fair, I know a lot of this has to do with my lack of experience with the tool, but, these error messages are a real struggle. Am I missing something? Is there some "magic" setting or technique to making sense of these messages? There are numerous that I am having trouble with, but, I'll post a few examples:
A2 is the stage name, but which field? In this case I was able to figure it out from the precision and scale since i only have one 10, 0 field, but that is not always the case.
Any help you can provide on understanding these messages (and others) will be greatly appreciated.
Thanks,
Bob
To be fair, I know a lot of this has to do with my lack of experience with the tool, but, these error messages are a real struggle. Am I missing something? Is there some "magic" setting or technique to making sense of these messages? There are numerous that I am having trouble with, but, I'll post a few examples:
Code: Select all
A2,9: Failure during execution of operator logic
A2,9: Fatal Error: APT_Decimal::assignFrom: src (179,769,313,486,232,
000,000,000,000,000,000,000,000,000,000,000,000,
000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,
000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,
000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,
000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,
000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,
000) out of range for decimal with precision 10 and scale 0
Code: Select all
A2,13: Internal Error: (value >= 0.0): decimal/decimal_impl.h: 543
Traceback: pureAssertion__13APT_FatalPathFPCcPCci() at 0xd3761afc
APT_decimalCheckRound__FdbQ2_11APT_Decimal9RoundMode() at 0xd38ad50c
assignFromDFloat__11APT_DecimalFdQ2_11APT_Decimal9RoundModeP10APT_Status() at 0xd38ad00c
__as__13APT_StatValueFRCd() at 0xd52f1394
reset__Q2_15APT_StatReducer11AccumulatorFv() at 0xd52f721c
end__15APT_StatReducerFPv() at 0xd52f24c0
runLocally__24APT_SortedGroup2OperatorFv() at 0xd5375688
run__15APT_OperatorRepFv() at 0xd39a1a3c
runLocally__14APT_OperatorSCFv() at 0xd3b35f40
runLocally__Q2_6APT_SC8OperatorFUi() at 0xd39679ac
Thanks,
Bob