MSIR.0139 OUTONLY invalid, Janus Open Client support not linked in: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
This message indicates that the OUTONLY parameter was specified in a [[JANUS DEFINE]] command for a [ | This message indicates that the <var>OUTONLY</var> parameter was specified in a <var>[[JANUS DEFINE]]</var> command for a [[Media:JosrvrNew.pdf|Janus Open Server]] port (type <var>OPENSERV</var>) but [[Media:JoclrNew.pdf|Janus Open Client]] support is not linked into the load module being run. Since, <var>OUTONLY</var> indicates that the port could only be used for Open Client applications, specifying this parameter when <var class="product">Janus Open Client</var> is not linked in does not make any sense. | ||
{{Template:MSIR.0139 footer}} | |||
[[Category:MSIR.0001 - MSIR.0199]] |
Latest revision as of 23:00, 3 March 2017
This message indicates that the OUTONLY parameter was specified in a JANUS DEFINE command for a Janus Open Server port (type OPENSERV) but Janus Open Client support is not linked into the load module being run. Since, OUTONLY indicates that the port could only be used for Open Client applications, specifying this parameter when Janus Open Client is not linked in does not make any sense.
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 |