MSIR.0682 LONGSTRING error: truncation, no Sirius debug info: Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 5: | Line 5: | ||
To get more debugging info such as the procedure and line number in which the error occurred, rerun the request with the DEBUGUL user parameter set or the 1 bit set in the SIRFACT system parameter. The latter can only be done if ''[[SirFact]]'' is installed. | To get more debugging info such as the procedure and line number in which the error occurred, rerun the request with the DEBUGUL user parameter set or the 1 bit set in the SIRFACT system parameter. The latter can only be done if ''[[SirFact]]'' is installed. | ||
[[Category:Sirius Mods | [[Category:Sirius Mods messages]] | ||
Revision as of 17:58, 19 April 2013
A longstring variable, or $function or method result was used in a context that would result in the longstring being implicitly truncated. The most common examples of this are assignment of a longstring to a shorter, non-longstring variable, and the passing of a longstring longer than 255 bytes to a non-longstring capable $function. One somewhat unusual but confusing case that can produce this error is assignment of a longstring with trailing blanks to an image item with STRIP set (the default). Because STRIP results in the trailing blanks effectively disappearing, this is considered a truncation error.
Longstring truncation issues, and methods for avoiding truncation errors, are covered on the Longstrings page.
To get more debugging info such as the procedure and line number in which the error occurred, rerun the request with the DEBUGUL user parameter set or the 1 bit set in the SIRFACT system parameter. The latter can only be done if SirFact is installed.