Archives of the TeradataForum
Message Posted: Fri, 08 Jun 2001 @ 15:21:35 GMT
| Subj: | | Re: Multiload Errors on V2R4.0.1 |
| |
| From: | | Keith Roloson |
I agree that the theory/explanation offered by Roland here is plausible. I have seen cases where the MTDP on a remote server "assumed"
that its inability to complete its operation was due to a DBC / Teradata restart. The faulty / inaccurate description & error code
provided in such a situation is likely due to a lack of error messages to choose from, and an inability by the MTDP to properly diagnose
where the break in the connection really is. In other words, it is a generic message noting it has an inability to complete its processing,
due to a condition outside of the sending system.
I have not seen this problem or message type on MVS TDP platforms, only on sites where the processing request originated in a network-
attached [LAN / WAN] server.
Having said that, I can NOT explain Carmen's comment that it only occurs with transactions exceeding 10k records. So while the above is
a general tip, it may not necessarily apply to Carmen's situation, noted below.
Keith Roloson
Teradata Tech Svcs
IBM Global Services/AT&T Acct
Alpharetta Control Center
| 
