JANUS RELOAD: Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:JANUS RELOAD}} | {{DISPLAYTITLE:JANUS RELOAD}} | ||
<span class="pageSubtitle"><section begin="desc" /> | <span class="pageSubtitle"><section begin="desc" />Reload SQL mapping<section end="desc" /></span> | ||
This reloads the ''Model 204'' to SQL mappings from the JANCAT file into virtual storage and CCATEMP. | |||
==Syntax== | ==Syntax== | ||
<p class="syntax"><section begin="syntax" /> JANUS RELOAD portname | <p class="syntax"><section begin="syntax" /> JANUS RELOAD portname | ||
| Line 11: | Line 10: | ||
</p> | </p> | ||
Where '''portname''' is the name of the port(s) to reload. JANUS DEFINE must have been used to define the port and JANUS START must have been used to start the port before reloading it via JANUS RELOAD. | |||
<p class="code"> JANUS RELOAD SDS* | <p class="code"> JANUS RELOAD SDS* | ||
</p> | </p> | ||
In the above example all ports whose names begin with SDS have their ''Model 204'' to SQL mappings reloaded from the appropriate JANCAT file. The reload can only happen when there are no in flight transactions (updating or retrieval) on the port. A long running Specialty Data Store request can cause a significant delay in the processing of the JANUS RELOAD command. After a JANUS RELOAD command is issued, all new Specialty Data Store requests will have to wait for the reload to complete before being processed. | In the above example all ports whose names begin with SDS have their ''Model 204'' to SQL mappings reloaded from the appropriate JANCAT file. The reload can only happen when there are no in flight transactions (updating or retrieval) on the port. A long running Specialty Data Store request can cause a significant delay in the processing of the JANUS RELOAD command. After a JANUS RELOAD command is issued, all new Specialty Data Store requests will have to wait for the reload to complete before being processed. | ||
If the AUTOLOAD switch is turned on for a port definition, the JANUS RELOAD need not be executed. AUTOLOAD (see ) causes table mappings to be loaded to the port automatically at the first user connection subsequent to any change to the ''[[Janus Specialty Data Store]]'' catalog file. | If the AUTOLOAD switch is turned on for a port definition, the JANUS RELOAD need not be executed. AUTOLOAD (see ) causes table mappings to be loaded to the port automatically at the first user connection subsequent to any change to the ''[[Janus Specialty Data Store]]'' catalog file. | ||
See: [[List of Janus commands]] | |||
[[Category:Janus commands|JANUS RELOAD]] | [[Category:Janus commands|JANUS RELOAD]] | ||
[[Category:Sirius commands]] | [[Category:Sirius commands]] | ||
Revision as of 14:12, 2 March 2011
<section begin="desc" />Reload SQL mapping<section end="desc" />
This reloads the Model 204 to SQL mappings from the JANCAT file into virtual storage and CCATEMP.
Syntax
<section begin="syntax" /> JANUS RELOAD portname <section end="syntax" />
JANUS RELOAD command syntax
Where portname is the name of the port(s) to reload. JANUS DEFINE must have been used to define the port and JANUS START must have been used to start the port before reloading it via JANUS RELOAD.
JANUS RELOAD SDS*
In the above example all ports whose names begin with SDS have their Model 204 to SQL mappings reloaded from the appropriate JANCAT file. The reload can only happen when there are no in flight transactions (updating or retrieval) on the port. A long running Specialty Data Store request can cause a significant delay in the processing of the JANUS RELOAD command. After a JANUS RELOAD command is issued, all new Specialty Data Store requests will have to wait for the reload to complete before being processed.
If the AUTOLOAD switch is turned on for a port definition, the JANUS RELOAD need not be executed. AUTOLOAD (see ) causes table mappings to be loaded to the port automatically at the first user connection subsequent to any change to the Janus Specialty Data Store catalog file.