AUTOLOAD (JANUS DEFINE parameter) - Revision history

JAL: minor formatting

2016-06-08T18:17:12Z

minor formatting

← Older revision		Revision as of 18:17, 8 June 2016
Line 5:		Line 5:
	This parameter indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.		This parameter indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.

	<var>AUTOLOAD</var> does have a few disadvantages, however. First, if several table definitions are being changed while SQL requests are being processed on a port, Janus might end up performing the reload process several times where issuing a JANUS RELOAD command at the end of all the changes would result in a single reload. Doing multiple reloads could be a significant expense if the number of <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var> table definitions is large. The other disadvantage of <var>AUTOLOAD</var> is that the reload doesn't happen until a request arrives on the port. This means that the user issuing the request could encounter a significant delay as the Janus port is reloaded. A JANUS RELOAD command before the request comes in would ensure that the table definitions would already be loaded so no extra delay would be encountered.		<var>AUTOLOAD</var> does have a few disadvantages, however. First, if several table definitions are being changed while SQL requests are being processed on a port, Janus might end up performing the reload process several times where issuing a <code>JANUS RELOAD</code> command at the end of all the changes would result in a single reload. Doing multiple reloads could be a significant expense if the number of <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var> table definitions is large. The other disadvantage of <var>AUTOLOAD</var> is that the reload doesn't happen until a request arrives on the port. This means that the user issuing the request could encounter a significant delay as the Janus port is reloaded. A <code>JANUS RELOAD</code> command before the request comes in would ensure that the table definitions would already be loaded so no extra delay would be encountered.

	Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.		Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.

JALWiccan: Automatically generated page update

2013-04-16T21:38:35Z

Automatically generated page update

← Older revision		Revision as of 21:38, 16 April 2013
Line 1:		Line 1:
	<span class="pageSubtitle"~~><section begin="desc" /~~>Automatically reload table definitions on an SDS port~~<section end="desc" />~~</span>		<span class="pageSubtitle">Automatically reload table definitions on an SDS port</span>

	<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 22:15, 29 February 2012

2012-02-29T22:15:52Z

← Older revision		Revision as of 22:15, 29 February 2012
Line 9:		Line 9:
	Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.		Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.

	Valid only for <var>[[JANUS DEFINE#type\|SDS]]</var> (also known as <var>~~[[JANUS DEFINE#type\|~~OMNI]]</var> or OAS) ports.		Valid only for <var>[[JANUS DEFINE#type\|SDS]]</var> (also known as <var>OMNI</var> or <var>OAS</var>) ports.

	==See also==		==See also==

JAL2 at 21:42, 29 February 2012

2012-02-29T21:42:27Z

← Older revision		Revision as of 21:42, 29 February 2012
Line 1:		Line 1:

	<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>

	<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter, indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.		This parameter indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.

	<var>AUTOLOAD</var> does have a few disadvantages, however. First, if several table definitions are being changed while SQL requests are being processed on a port, Janus might end up performing the reload process several times where issuing a JANUS RELOAD command at the end of all the changes would result in a single reload. Doing multiple reloads could be a significant expense if the number of <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var> table definitions is large. The other disadvantage of <var>AUTOLOAD</var> is that the reload doesn't happen until a request arrives on the port. This means that the user issuing the request could encounter a significant delay as the Janus port is reloaded. A JANUS RELOAD command before the request comes in would ensure that the table definitions would already be loaded so no extra delay would be encountered.		<var>AUTOLOAD</var> does have a few disadvantages, however. First, if several table definitions are being changed while SQL requests are being processed on a port, Janus might end up performing the reload process several times where issuing a JANUS RELOAD command at the end of all the changes would result in a single reload. Doing multiple reloads could be a significant expense if the number of <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var> table definitions is large. The other disadvantage of <var>AUTOLOAD</var> is that the reload doesn't happen until a request arrives on the port. This means that the user issuing the request could encounter a significant delay as the Janus port is reloaded. A JANUS RELOAD command before the request comes in would ensure that the table definitions would already be loaded so no extra delay would be encountered.

JAL2 at 21:41, 29 February 2012

2012-02-29T21:41:55Z

← Older revision		Revision as of 21:41, 29 February 2012
Line 1:		Line 1:
	~~{{DISPLAYTITLE:AUTOLOAD}}~~
	<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>

JAL2 at 21:41, 29 February 2012

2012-02-29T21:41:45Z

← Older revision		Revision as of 21:41, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>

	<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port~~. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]~~.		<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter, indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.		This parameter, indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.

JALWiccan: 1 revision

2012-02-29T21:14:03Z

1 revision

← Older revision	Revision as of 21:14, 29 February 2012
(No difference)

JAL2 at 21:14, 29 February 2012

2012-02-29T21:14:02Z

← Older revision		Revision as of 21:14, 29 February 2012
Line 10:		Line 10:
	Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.		Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.

	Valid only for <var>[[JANUS DEFINE#type\|SDS]]</var> (also known as OMNI or OAS) ports.		Valid only for <var>[[JANUS DEFINE#type\|SDS]]</var> (also known as <var>[[JANUS DEFINE#type\|OMNI]]</var> or OAS) ports.

	==See also==		==See also==

JAL2 at 19:06, 29 February 2012

2012-02-29T19:06:01Z

← Older revision		Revision as of 19:06, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>

	<var>AUTOLOAD</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>AUTOLOAD</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter, indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.		This parameter, indicates that the incore copy of Janus tables are to be reloaded at the first request subsequent to a table redefinition. This eliminates the need to issue JANUS RELOAD commands to reload table definitions after changes have been made.

JAL2 at 19:05, 29 February 2012

2012-02-29T19:05:43Z

← Older revision		Revision as of 19:05, 29 February 2012
Line 1:		Line 1:
	{{DISPLAYTITLE:AUTOLOAD}}		{{DISPLAYTITLE:AUTOLOAD}}
	<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an ~~<var>[[JANUS DEFINE#type\|~~SDS~~]]</var>~~ port<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Automatically reload table definitions on an SDS port<section end="desc" /></span>

	<var>AUTOLOAD</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>AUTOLOAD</var> is a parameter on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].
Line 10:		Line 10:
	Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.		Note that it is perfectly valid to issue a JANUS RELOAD command on an <var>AUTOLOAD</var> port.

	Valid only for SDS (also known as OMNI or OAS) ports.		Valid only for <var>[[JANUS DEFINE#type\|SDS]]</var> (also known as OMNI or OAS) ports.

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[List of Janus commands]] \| [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<li>[[List of Janus commands]]
			<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]
			</ul>

	[[Category:JANUS DEFINE parameters\|AUTOLOAD]]		[[Category:JANUS DEFINE parameters\|AUTOLOAD]]