MSIR.0825 SUBSYSTEM without NONPRE doesn't make sense for SUBSYSTEMSET: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
A <tt>SIRMETH</tt> command was issued that indicated the <tt>SUBSYSTEM</tt> parameter but did not have a subsystem name qualified with the <tt>NONPRE</tt> keyword. Since pre-compiled requests in a subsystem can always set subsystem strings or globals, it is only meaningful to issue this command to allow non-pre-compiled requests to do the same. As such, it makes no sense to issue such a command without a subsystem name or wildcard string followed by the <tt>NONPRE</tt> keyword. See the ''Janus SOAP Reference Manual'' for more information about the <tt>SIRMETH</tt> command. | A <tt>SIRMETH</tt> command was issued that indicated the <tt>SUBSYSTEM</tt> parameter but did not have a subsystem name qualified with the <tt>NONPRE</tt> keyword. Since pre-compiled requests in a subsystem can always set subsystem strings or globals, it is only meaningful to issue this command to allow non-pre-compiled requests to do the same. As such, it makes no sense to issue such a command without a subsystem name or wildcard string followed by the <tt>NONPRE</tt> keyword. See the ''Janus SOAP Reference Manual'' for more information about the <tt>SIRMETH</tt> command. | ||
[[Category:Sirius Mods | [[Category:Sirius Mods messages]] | ||
Revision as of 18:00, 19 April 2013
A SIRMETH command was issued that indicated the SUBSYSTEM parameter but did not have a subsystem name qualified with the NONPRE keyword. Since pre-compiled requests in a subsystem can always set subsystem strings or globals, it is only meaningful to issue this command to allow non-pre-compiled requests to do the same. As such, it makes no sense to issue such a command without a subsystem name or wildcard string followed by the NONPRE keyword. See the Janus SOAP Reference Manual for more information about the SIRMETH command.