MSIR.0799 Null object passed as non-allowNull parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
Line 3: | Line 3: | ||
</blockquote> | </blockquote> | ||
{{Template:MSIR.0799 footer}} | |||
[[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]] | [[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]] |
Revision as of 21:59, 11 July 2016
A Null was specified as an argument in a method invocation but the method declaration did not specify AllowNull for the corresponding parameter. If there are good reasons to be passing a null object to the method, correct the method declaration to indicate AllowNull. Otherwise, correct the method invocation to pass an appropriate object.
Specifying an object that will be null at evaluation time will only shift the problem from a compile-time error to an evaluation time error, since a null object passed as a non-AllowNull argument will result in request cancellation.
Message attributes:
RETCODEO=0 | Sets online return code |
---|---|
RETCODEB=4 | Sets batch (single user) return code |
CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
AUDITER | Writes the message with line type ER to the audit trail |
COUNT | Increments the error count (ERCNT) parameter |
ECHO | Displays the line that caused the error |