Jump to: navigation, search

GVP MCP:log:messagefile

Line 2: Line 2:
 
|hidden=false
 
|hidden=false
 
|default=
 
|default=
|valid=[string].lms (message file name)
+
|valid=[string].lms (message file name)
 
|takeseffect=Immediately, if an application cannot find its *.lms file at startup
 
|takeseffect=Immediately, if an application cannot find its *.lms file at startup
 
|shortdesc=Specifies the file name for application-specific log events. The name must be valid for the operating system on which the application is running. The option value can also contain the absolute path to the application-specific *.lms file. Otherwise, an application looks for the file in its working directory.
 
|shortdesc=Specifies the file name for application-specific log events. The name must be valid for the operating system on which the application is running. The option value can also contain the absolute path to the application-specific *.lms file. Otherwise, an application looks for the file in its working directory.
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}
 
 
 
 
 
  
 
{{PubExtended}}
 
{{PubExtended}}
 
 
 
 
  
 
{{DraftExtended}}
 
{{DraftExtended}}
 
 
 
 
 
  
 
{{OptionCreate
 
{{OptionCreate

Revision as of 20:39, July 3, 2019



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

messagefile

Default Value:
Valid Values: [string].lms (message file name)
Changes Take Effect: Immediately, if an application cannot find its *.lms file at startup


Specifies the file name for application-specific log events. The name must be valid for the operating system on which the application is running. The option value can also contain the absolute path to the application-specific *.lms file. Otherwise, an application looks for the file in its working directory.

Draft Option

No draft option

Comments or questions about this documentation? Contact us for support!