m204wiki - Recent changes [en]

Global features

JDamon — Thu, 23 Apr 2026 17:47:34 GMT

Syntax

← Older revision		Revision as of 17:47, 23 April 2026
(5 intermediate revisions by the same user not shown)
Line 554:		Line 554:
	Where:		Where:
	<ul>		<ul>
	<li>The <var>Global</var> option implies ~~Perm~~ and the position is retained in GTBL after the current request terminates. If <var>Global</var> is not specified, TEMP is implied and the position is cleared from GTBL after the current request terminates.</li>		<li>The <var>Global</var> option implies '''PERM''' and the position is retained in GTBL after the current request terminates. If <var>Global</var> is not specified, '''TEMP''' is implied and the position is cleared from GTBL after the current request terminates.</li>
	<p><b>NOTE:</B> The use of GLOBAL here must be consistent with the CLEAR GLOBAL POSITION statement. If the latter is specified with PERM:</p>		<p><b>NOTE:</B> The use of GLOBAL here must be consistent with the CLEAR GLOBAL POSITION statement. If the latter is specified with PERM:</p>
	<p>CLEAR GLOBAL POSITION <b>PERM</b> '~~objectname~~',</p>		<p>CLEAR GLOBAL POSITION <b>PERM</b> 'position_name',</p>
	<p>then the REMEMBER statement must specify GLOBAL because it implies PERM.</p>		<p>then the REMEMBER statement must specify GLOBAL because it implies PERM.</p>

	<li><var class="term">position_name</var> is a unique object name you assign to the <var>Remember</var> position. </li>		<li><var class="term">position_name</var> is a unique object name you assign to the <var>Remember</var> position. </li>
			<p><b>NOTE:</b>If the 'position_name' is mixed or lower case, be sure to enclose it here in single quotation marks. Do the same when referring to that name in other statements; e.g. CLEAR or POSITION.</p>

	<li><var class="term">foundsortset_name</var> or <var class="term">list_name</var> must be identical to the listname or label specified on the <var>For</var> loop:		<li><var class="term">foundsortset_name</var> or <var class="term">list_name</var> must be identical to the listname or label specified on the <var>For</var> loop:
Line 598:		Line 599:

	<li><var class="term">position_name</var> is a name that you assigned to the remembered position when you stored it on a previous <var>Remember</var> statement. </li>		<li><var class="term">position_name</var> is a name that you assigned to the remembered position when you stored it on a previous <var>Remember</var> statement. </li>
			<p><b>NOTE:</b>If the 'position_name' is mixed or lower case, be sure to enclose it here in single quotation marks. Do the same when referring to that name in other statements; e.g. CLEAR or REMEMBER.</p>
	</ul>		</ul>

	====Usage notes====		====Usage notes====
	<p>		<p>
Line 871:		Line 873:

	<li><var class="term">objectname</var> is the literal name of the specific global object to be cleared from GTBL. Enclose <var class="term">objectname</var> in single quotation marks.</li>		<li><var class="term">objectname</var> is the literal name of the specific global object to be cleared from GTBL. Enclose <var class="term">objectname</var> in single quotation marks.</li>
	<p><b>NOTE:</b> If the <i>objectname</i> is mixed case, be sure to ~~use the same name,~~ in single quotation marks, when referring to that name in other statements; e.g. REMEMBER or POSITION.</p>		<p><b>NOTE:</b> If the <i>'objectname'</i> is mixed or lower case, be sure to enclose it here in single quotation marks. Do the same when referring to that name in other statements; e.g. REMEMBER or POSITION.</p>

	<li><var class="term">%variable</var> contains a value that specifies the global object to be cleared from GTBL. </li>		<li><var class="term">%variable</var> contains a value that specifies the global object to be cleared from GTBL. </li>

Using system statistics

RPuszewski — Wed, 22 Apr 2026 17:58:35 GMT

Description of statistics

Show changes

RESRQST parameter

RPuszewski — Wed, 22 Apr 2026 15:43:45 GMT

Created page with "{{Template:RESRQST parameter subtitle}} ==Summary== <dl> <dt>Default value <dd>0 <dt>Parameter type <dd>System <dt>Where set <dd>View only <dt>Related products <dd>All <dt>Introduced <dd><var class="product">Model 204</var> version 8.0 </dl> ==Description== This parameter displays the number of active resident requests. This parameter is non-zero only when <var>RESPAGE</var> is greater than zero (resident requests in use). Category:Parameters Cate..."

New page

{{Template:RESRQST parameter subtitle}}
==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>System
<dt>Where set
<dd>View only
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204</var> version 8.0
</dl>

==Description==

This parameter displays the number of active resident requests.

This parameter is non-zero only when <var>RESPAGE</var> is greater than zero (resident requests in use).

[[Category:Parameters]]
[[Category:System parameters]]

Template:List of Model 204 parameters

RPuszewski — Wed, 22 Apr 2026 15:29:17 GMT

← Older revision		Revision as of 15:29, 22 April 2026
Line 1,946:		Line 1,946:
	<td xml:space="preserve">Number of resident N/QTBL ATB pages</td>		<td xml:space="preserve">Number of resident N/QTBL ATB pages</td>
	<td xml:space="preserve">User 0 parameter line</td>		<td xml:space="preserve">User 0 parameter line</td>
			</tr>
			<tr>
			<th xml:space="preserve"><var>[[RESRQST parameter\|RESRQST]]</var></th>
			<td xml:space="preserve">Active number of resident requests</td>
			<td xml:space="preserve">Viewable only</td>
	</tr>		</tr>
	<tr>		<tr>

CMD (JANUS DEFINE parameter)

Alex — Wed, 15 Apr 2026 22:23:03 GMT

Add IMAGINET to valid port types

← Older revision		Revision as of 22:23, 15 April 2026
Line 17:		Line 17:

	For <var>WEB</var> ports, the commands specified by <var>CMD</var> are executed after all rules are executed except the <var>ON</var> rules. The specified commands can be used to invoke an <var class="product">APSY</var> subsystem when using the <var class="product">Janus Web Server</var> [[Janus Web Server $functions\|$functions]] or to reset <var>UTABLE</var> and other parameters.		For <var>WEB</var> ports, the commands specified by <var>CMD</var> are executed after all rules are executed except the <var>ON</var> rules. The specified commands can be used to invoke an <var class="product">APSY</var> subsystem when using the <var class="product">Janus Web Server</var> [[Janus Web Server $functions\|$functions]] or to reset <var>UTABLE</var> and other parameters.

			For <var>IMAGINET</var> ports, the commands specified by <var>CMD</var> are executed when an [[Imagine Transparency]] connection is established. This can be used to set parameters or open files needed for transparency processing.

	Examples of some valid <var>CMD</var> clauses:		Examples of some valid <var>CMD</var> clauses:
Line 27:		Line 29:
	'''Note:''' The command only needs to be quoted if it contains blanks or special characters.		'''Note:''' The command only needs to be quoted if it contains blanks or special characters.

	Valid for <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>TNSERV</var>, <var>SDS</var>, or <var>~~OPENSERV~~</var> port types, this parameter is required for <var>SRVSOCK</var> and <var>OPENSERV</var> port types. This parameter is '''not''' valid on an <var>FTPSERVER</var> port definition.		Valid for <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>TNSERV</var>, <var>SDS</var>, <var>OPENSERV</var>, or <var>[[JANUS DEFINE#type\|IMAGINET]]</var> port types, this parameter is required for <var>SRVSOCK</var> and <var>OPENSERV</var> port types. This parameter is '''not''' valid on an <var>FTPSERVER</var> port definition.

	==See also==		==See also==
	<ul>		<ul>
			<li>[[Imagine Transparency]]
	<li>[[List of Janus commands]]		<li>[[List of Janus commands]]
	<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]		<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]

OPEN (JANUS DEFINE parameter)

Alex — Wed, 15 Apr 2026 22:22:42 GMT

Add IMAGINET to valid port types

← Older revision		Revision as of 22:22, 15 April 2026
Line 27:		Line 27:
	</p>		</p>

	This parameter is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, OPENSERV and <var>[[JANUS DEFINE#type\|~~SDS~~]]</var> port types.		This parameter is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, <var>OPENSERV</var>, <var>[[JANUS DEFINE#type\|SDS]]</var>, and <var>[[JANUS DEFINE#type\|IMAGINET]]</var> port types. For <var>IMAGINET</var> ports, the <var>OPEN</var> parameter can be used to open files or set up the environment for [[Imagine Transparency]] connections.

	This parameter is '''not''' valid on an <var>[[JANUS DEFINE#type\|FTPSERVER]]</var> port definition.		This parameter is '''not''' valid on an <var>[[JANUS DEFINE#type\|FTPSERVER]]</var> port definition.
Line 33:		Line 33:
	==See also==		==See also==
	<ul>		<ul>
			<li>[[Imagine Transparency]]
	<li>[[List of Janus commands]]		<li>[[List of Janus commands]]
	<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]		<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]

APSYSUFFIX (JANUS DEFINE parameter)

Alex — Wed, 15 Apr 2026 22:17:20 GMT

Add suffix-to-filename relationship, JANUS ADDSUFFIX links, multi-suffix example

← Older revision		Revision as of 22:17, 15 April 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	~~<span class="pageSubtitle">~~APSYSUFFIX~~: Enable per-~~suffix routing ~~on IMAGINET ports</span>~~		APSYSUFFIX ''x'' — Specify Application System suffix for IMAGINET port routing

	~~<var>~~APSYSUFFIX~~</var>~~ is a parameter ~~on <var>~~[[JANUS DEFINE]]~~</var>~~ that ~~enables~~ per-suffix routing ~~on IMAGINET ports~~, allowing multiple DBS ~~(Database Server~~) instances ~~to be served by a single port~~.		APSYSUFFIX is a [[JANUS DEFINE#parmlist\|parameter]] of the [[JANUS DEFINE]] command, which defines and sets characteristics of a Janus port. APSYSUFFIX specifies a single-character suffix that identifies the Application System (APSY) instance associated with a broker connection. This suffix is sent to Model 204 during the [[Imagine Transparency]] handshake to enable per-suffix routing, allowing a single IMAGINET port to serve multiple Imagine Database Store (DBS) instances.

	~~This~~ is a ~~flag parameter; it takes no value~~.		==Syntax==
			<p class="syntax">APSYSUFFIX <span class="term">x</span>
			</p>

			Where:
			:<var>x</var> is a single alphanumeric character (A-Z or 0-9) that identifies the APSY suffix for this broker instance.

	When <~~var~~>~~APSYSUFFIX~~</~~var~~> ~~is set~~, ~~each connecting Imagine broker~~ identifies ~~itself with a single-character suffix and a DBS name during~~ the ~~handshake. The~~ suffix~~-to-DBS mappings are managed at runtime via~~ the ~~<var>[[JANUS ADDSUFFIX]]</var>, <var>[[JANUS DELETESUFFIX]]</var>, and <var>[[JANUS DISPLAYSUFFIX]]</var> commands~~.		==Suffix and transparency file naming==
			The APSYSUFFIX value is directly related to Model 204 transparency file naming conventions. When a Model 204 file is allocated with <code>ALLOCATE ''filename'' WITH IMAGINE</code>, the third character of the filename identifies the APSY suffix of the broker that serves that file. For example:

	~~==Syntax==~~		* A file named <b>ROXDATA</b> has suffix <b>X</b> (third character), so it can only be accessed through a broker running with <code>APSYSUFFIX X</code>.
	<~~p class="syntax"~~><~~span class="literal"~~>~~JANUS DEFINE~~</~~span~~> <~~span class="term"~~>~~portname~~</~~span~~> ... <~~span class="literal"~~>~~APSYSUFFIX~~</~~span~~></p>		* A file named <b>ROTDATA</b> has suffix <b>T</b>, and is served by a broker with <code>APSYSUFFIX T</code>.
			* A file named <b>ROLDATA</b> has suffix <b>L</b>, and is served by a broker with <code>APSYSUFFIX L</code>.

	~~==Applicability==~~		This naming convention allows Model 204 to automatically route each file access request to the correct broker and DBS instance based on the file name alone. The suffix-to-DBS mapping is registered on the IMAGINET port using the [[JANUS ADDSUFFIX]] command.
	~~<var>APSYSUFFIX</var>~~ is ~~valid only for~~ IMAGINET ~~type ports~~.

	==Usage==		==Usage==
	~~Use~~ <~~var~~>~~APSYSUFFIX~~</~~var~~> ~~when~~ a ~~single IMAGINET port must serve multiple~~ DBS ~~instances~~. ~~Each broker connecting~~ to ~~the port sends~~ a ~~single-character~~ suffix ~~(A-Z, 0-9) and~~ a ~~DBS name during the handshake~~. The suffix-to-~~DBS~~ mappings ~~are registered~~ with <~~var~~>[[JANUS ADDSUFFIX]]</~~var~~>.		* When APSYSUFFIX is specified on the JANUS DEFINE, the [[JANUS ADDSUFFIX]] command can then be used to register suffix-to-DBS name mappings on the port. Each mapping associates a suffix character with a specific DBS instance name.
			* When a Model 204 application accesses a transparency file, the system extracts the suffix from the filename, looks up the corresponding DBS name in the port's suffix table, and routes the request to the appropriate broker.
			* Without APSYSUFFIX, all IMAGINET connections are routed to a single, default DBS instance, and only one set of transparency files can be served.
			* APSYSUFFIX is typically used in conjunction with the <code>dbsName</code> and <code>dbsPort</code> broker options to associate each suffix with a specific DBS instance. For example, suffix "T" might connect to a test DBS instance, while suffix "L" connects to a live instance.
			* The suffix value is case-insensitive; it is converted to uppercase before being sent to Model 204.

			Valid only for [[JANUS DEFINE#type\|IMAGINET]] port types. This parameter is new as of Model 204 version 8.0.

			==Example==
			A typical multi-suffix configuration involves defining the IMAGINET port, registering suffix mappings, and starting brokers with matching suffixes:

			<pre>
			JANUS DEFINE IMGPORT 12231 IMAGINET 50 APSYSUFFIX
			JANUS ADDSUFFIX IMGPORT T db
			JANUS ADDSUFFIX IMGPORT L larry
			JANUS ADDSUFFIX IMGPORT U lulu
			</pre>

			On the Imagine side, brokers are started with corresponding suffix and DBS name options:

	~~The suffix character for the current connection is available in~~ <~~var class~~=~~"product">Model 204</var> User Language via the <var>[[ApsySuffix (Imagine property)\|ApsySuffix]]</var> method, and the DBS name via the <var>[[DbsName (Imagine property)\|DbsName]]~~</~~var~~> ~~method.~~		<pre>
			startBroker --apsySuffix=T --dbsName=db --dbsPort=7777
			startBroker --apsySuffix=L --dbsName=larry --dbsPort=7778
			startBroker --apsySuffix=U --dbsName=lulu --dbsPort=7779
			</pre>

	~~This~~ is ~~new as of <var class=~~"~~product~~"~~>Model 204</var> version 8.0~~.		With this configuration, a Model 204 file named ROTDATA is routed to the broker with suffix T (DBS "db"), while ROLDATA is routed to suffix L (DBS "larry").

	==See also==		==See also==
	~~<ul>~~		* [[Imagine Transparency]]
	~~<li>~~[[JANUS ADDSUFFIX]]~~</li>~~		* [[JANUS ADDSUFFIX]]
	~~<li>~~[[JANUS DELETESUFFIX]]~~</li>~~		* [[JANUS DELETESUFFIX]]
	~~<li>~~[[JANUS DISPLAYSUFFIX]]~~</li>~~		* [[JANUS DISPLAYSUFFIX]]
	~~<li>~~[[~~ApsySuffix (Imagine property)\|ApsySuffix~~]]~~</li>~~		* [[List of Janus commands]]
	~~<li>~~[[~~DbsName (Imagine property)~~\|~~DbsName]]</li>~~		* [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]
	~~</ul>~~

	~~[[Category:~~JANUS DEFINE parameters~~\|APSYSUFFIX~~]]

List of Imagine methods

Alex — Tue, 14 Apr 2026 03:23:26 GMT

Add ApsySuffix and DbsName methods

← Older revision		Revision as of 03:23, 14 April 2026
Line 6:		Line 6:
	<table class="wikitable">		<table class="wikitable">
	<tr><th>Method</th><th>Description</th></tr>		<tr><th>Method</th><th>Description</th></tr>
			<tr><td valign="top">[[ApsySuffix (Imagine property)\|ApsySuffix]]</td><td valign="top">Return the APSY suffix character for the current connection</td></tr>
	<tr><td valign="top">[[Call (Imagine function)\|Call]]</td><td valign="top">Run Imagine code on the Transparency Broker</td></tr>		<tr><td valign="top">[[Call (Imagine function)\|Call]]</td><td valign="top">Run Imagine code on the Transparency Broker</td></tr>
			<tr><td valign="top">[[DbsName (Imagine property)\|DbsName]]</td><td valign="top">Return the DBS name for the current connection</td></tr>
	</table>		</table>
	</div>		</div>

Janus commands

Alex — Tue, 14 Apr 2026 03:22:50 GMT

Add ADDSUFFIX, DELETESUFFIX, DISPLAYSUFFIX commands

← Older revision		Revision as of 03:22, 14 April 2026
Line 77:		Line 77:
	<tr><th><var>[[JANUS ADDCOORDINATOR\|ADDCOORDINATOR]]<br/>[[JANUS ADDCOORDINATOR\|ADDCOORD]]</var></th>		<tr><th><var>[[JANUS ADDCOORDINATOR\|ADDCOORDINATOR]]<br/>[[JANUS ADDCOORDINATOR\|ADDCOORD]]</var></th>
	<td>Adds a two-phase commit coordinator to a port.</td></tr>		<td>Adds a two-phase commit coordinator to a port.</td></tr>

			<tr><th><var>[[JANUS ADDSUFFIX\|ADDSUFFIX]]<br/>[[JANUS ADDSUFFIX\|ADDSUFF]]</var></th>
			<td>Adds a suffix-to-DBS name mapping to an APSYSUFFIX port.</td></tr>

	<tr><th><var>[[JANUS CHARSET\|CHARSET]]</var></th>		<tr><th><var>[[JANUS CHARSET\|CHARSET]]</var></th>
Line 107:		Line 110:
	<tr><th><var>[[JANUS DELETECOORDINATOR\|DELETECOORDINATOR]]<br/>[[JANUS DELETECOORDINATOR\|DELCOORDINATOR]]<br/>[[JANUS DELETECOORDINATOR\|DELETECOORD]]<br/>[[JANUS DELETECOORDINATOR\|DELCOORD]]</var></th>		<tr><th><var>[[JANUS DELETECOORDINATOR\|DELETECOORDINATOR]]<br/>[[JANUS DELETECOORDINATOR\|DELCOORDINATOR]]<br/>[[JANUS DELETECOORDINATOR\|DELETECOORD]]<br/>[[JANUS DELETECOORDINATOR\|DELCOORD]]</var></th>
	<td>Deletes a two-phase commit coordinator from a port.</td></tr>		<td>Deletes a two-phase commit coordinator from a port.</td></tr>

			<tr><th><var>[[JANUS DELETESUFFIX\|DELETESUFFIX]]<br/>[[JANUS DELETESUFFIX\|DELSUFFIX]]<br/>[[JANUS DELETESUFFIX\|DELSUFF]]</var></th>
			<td>Removes a suffix-to-DBS name mapping from an APSYSUFFIX port.</td></tr>

	<tr><th><var>[[JANUS DELETEIPGROUP\|DELETEIPGROUP]]<br/>[[JANUS DELETEIPGROUP\|DELIPGROUP]]<br/>[[JANUS DELETEIPGROUP\|DELETEIPG]]<br/>[[JANUS DELETEIPGROUP\|DELIPG]]</var></th>		<tr><th><var>[[JANUS DELETEIPGROUP\|DELETEIPGROUP]]<br/>[[JANUS DELETEIPGROUP\|DELIPGROUP]]<br/>[[JANUS DELETEIPGROUP\|DELETEIPG]]<br/>[[JANUS DELETEIPGROUP\|DELIPG]]</var></th>
Line 132:		Line 138:
	<tr><th><var>[[JANUS DISPLAYREMOTE\|DISPLAYREMOTE]]<br/>[[JANUS DISPLAYREMOTE\|DISPLAYREM]]<br/>[[JANUS DISPLAYREMOTE\|DISREMOTE]]<br/>[[JANUS DISPLAYREMOTE\|DISREM]]<br/></var></th>		<tr><th><var>[[JANUS DISPLAYREMOTE\|DISPLAYREMOTE]]<br/>[[JANUS DISPLAYREMOTE\|DISPLAYREM]]<br/>[[JANUS DISPLAYREMOTE\|DISREMOTE]]<br/>[[JANUS DISPLAYREMOTE\|DISREM]]<br/></var></th>
	<td>Displays remoter server definitions.</td></tr>		<td>Displays remoter server definitions.</td></tr>

			<tr><th><var>[[JANUS DISPLAYSUFFIX\|DISPLAYSUFFIX]]<br/>[[JANUS DISPLAYSUFFIX\|DISSUFFIX]]<br/>[[JANUS DISPLAYSUFFIX\|DISPLAYSUFF]]<br/>[[JANUS DISPLAYSUFFIX\|DISSUFF]]</var></th>
			<td>Displays suffix-to-DBS name mappings for an APSYSUFFIX port.</td></tr>

	<tr><th><var>[[JANUS DISPLAYSOCK\|DISPLAYSOCK]]<br/>[[JANUS DISPLAYSOCK\|DISSOCK]]<br/></var></th>		<tr><th><var>[[JANUS DISPLAYSOCK\|DISPLAYSOCK]]<br/>[[JANUS DISPLAYSOCK\|DISSOCK]]<br/></var></th>

JANUS DEFINE

Alex — Tue, 14 Apr 2026 03:22:07 GMT

Add APSYSUFFIX parameter

← Older revision		Revision as of 03:22, 14 April 2026
Line 159:		Line 159:

	<tr><td>[[ANONUSER (JANUS DEFINE parameter)\|ANONUSER]]</td><td>Lets you change the name of the anonymous user, <var>ANONUSER</var> may be specified only if <var>ANONYMOUS</var> is also specified.</td></tr>		<tr><td>[[ANONUSER (JANUS DEFINE parameter)\|ANONUSER]]</td><td>Lets you change the name of the anonymous user, <var>ANONUSER</var> may be specified only if <var>ANONYMOUS</var> is also specified.</td></tr>

			<tr><td>[[APSYSUFFIX (JANUS DEFINE parameter)\|APSYSUFFIX]]</td><td>Enables per-suffix routing on IMAGINET ports, allowing multiple DBS instances to be served through a single port.</td></tr>

	<tr><td>[[AUDTERM (JANUS DEFINE parameter)\|AUDTERM]]</td><td>Controls whether the server thread sends "non-compiler terminal output" to the audit trail.</td></tr>		<tr><td>[[AUDTERM (JANUS DEFINE parameter)\|AUDTERM]]</td><td>Controls whether the server thread sends "non-compiler terminal output" to the audit trail.</td></tr>

DbsName (Imagine property)

Alex — Tue, 14 Apr 2026 03:21:33 GMT

Create DbsName Imagine method page

New page

DbsName: Return the DBS name for the current connection

The <var>DbsName</var> method returns the DBS name for the current Imagine connection as a String.

If no DBS name was sent by the broker, an empty string is returned.

This is a shared, read-only method.

==Syntax==
%name = %(imagineObject):DbsName

==Return value==
A String containing the DBS name for the current connection (up to 63 characters), or an empty string if no DBS name was provided.

==Usage==
Use <var>DbsName</var> to determine which DBS instance the connecting broker requested during the handshake. This is useful in APSY code that needs to identify the target DBS on a port with <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> defined.

This is new as of <var class="product">Model 204</var> version 8.0.

==Example==
%dbsName = %(system):DbsName
If %dbsName NE '' Then
Print 'DBS: ' %dbsName
End If

==See also==
<ul>
<li>[[ApsySuffix (Imagine property)|ApsySuffix]]</li>
<li>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</li>
<li>[[List of Imagine methods]]</li>
</ul>

[[Category:Imagine methods]]

ApsySuffix (Imagine property)

Alex — Tue, 14 Apr 2026 03:21:21 GMT

Create ApsySuffix Imagine method page

New page

ApsySuffix: Return the APSY suffix character for the current connection

The <var>ApsySuffix</var> method returns the APSY suffix character for the current Imagine connection as a String.

If no suffix is active (the port does not have <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> defined, or the broker did not send a suffix), an empty string is returned.

This is a shared, read-only method.

==Syntax==
%suffix = %(imagineObject):ApsySuffix

==Return value==
A String containing the single-character APSY suffix (A-Z, 0-9) for the current connection, or an empty string if no suffix is active.

==Usage==
Use <var>ApsySuffix</var> to determine which suffix the connecting broker presented during the handshake. This is useful in APSY code that needs to vary its behavior based on which DBS instance the connection is targeting.

This is new as of <var class="product">Model 204</var> version 8.0.

==Example==
%suffix = %(system):ApsySuffix
If %suffix NE '' Then
Print 'Suffix: ' %suffix
End If

==See also==
<ul>
<li>[[DbsName (Imagine property)|DbsName]]</li>
<li>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</li>
<li>[[List of Imagine methods]]</li>
</ul>

[[Category:Imagine methods]]

JANUS DISPLAYSUFFIX

Alex — Tue, 14 Apr 2026 03:21:05 GMT

Create JANUS DISPLAYSUFFIX command page

New page

JANUS DISPLAYSUFFIX: Display suffix-to-DBS name mappings

The <var>JANUS DISPLAYSUFFIX</var> command displays the suffix-to-DBS name mappings for a port that has <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> defined.

==Syntax==
JANUS DISPLAYSUFFIX portname [suffix]

Where:
<ul>
<li><var>portname</var> is the name of a <var>[[JANUS DEFINE]]</var> port with <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> set.</li>
<li><var>suffix</var> is an optional single suffix character. If specified, only that mapping is shown. Otherwise all mappings for the port are displayed.</li>
</ul>

==Synonyms==
<var>JANUS DISSUFFIX</var>, <var>JANUS DISPLAYSUFF</var>, and <var>JANUS DISSUFF</var> are synonyms for <var>JANUS DISPLAYSUFFIX</var>.

==Usage==
The display includes the suffix character, DBS name, and queue counts.

This is new as of <var class="product">Model 204</var> version 8.0.

==Example==
JANUS DISPLAYSUFFIX MYPORT
JANUS DISPLAYSUFFIX MYPORT A

==See also==
<ul>
<li>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</li>
<li>[[JANUS ADDSUFFIX]]</li>
<li>[[JANUS DELETESUFFIX]]</li>
</ul>

[[Category:Janus commands]]

JANUS DELETESUFFIX

Alex — Tue, 14 Apr 2026 03:20:53 GMT

Create JANUS DELETESUFFIX command page

New page

JANUS DELETESUFFIX: Remove a suffix-to-DBS name mapping

The <var>JANUS DELETESUFFIX</var> command removes a suffix mapping from a port that has <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> defined.

==Syntax==
JANUS DELETESUFFIX portname {suffix | *}

Where:
<ul>
<li><var>portname</var> is the name of a <var>[[JANUS DEFINE]]</var> port with <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> set.</li>
<li><var>suffix</var> is a single suffix character to remove, or <code>*</code> to remove all suffix mappings for the port.</li>
</ul>

==Synonyms==
<var>JANUS DELSUFFIX</var> and <var>JANUS DELSUFF</var> are synonyms for <var>JANUS DELETESUFFIX</var>.

==Usage==
Specify a single suffix character to remove one mapping, or <code>*</code> to remove all suffix mappings for the port.

This is new as of <var class="product">Model 204</var> version 8.0.

==Example==
JANUS DELETESUFFIX MYPORT A
JANUS DELETESUFFIX MYPORT *

==See also==
<ul>
<li>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</li>
<li>[[JANUS ADDSUFFIX]]</li>
<li>[[JANUS DISPLAYSUFFIX]]</li>
</ul>

[[Category:Janus commands]]

JANUS ADDSUFFIX

Alex — Tue, 14 Apr 2026 03:20:38 GMT

Create JANUS ADDSUFFIX command page

New page

JANUS ADDSUFFIX: Register a suffix-to-DBS name mapping

The <var>JANUS ADDSUFFIX</var> command registers a suffix character and DBS name pair for a port that has <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> defined.

==Syntax==
JANUS ADDSUFFIX portname suffix dbsname

Where:
<ul>
<li><var>portname</var> is the name of a <var>[[JANUS DEFINE]]</var> port with <var>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</var> set.</li>
<li><var>suffix</var> is a single alphanumeric character (A-Z, 0-9).</li>
<li><var>dbsname</var> is the name of the DBS instance, up to 63 characters.</li>
</ul>

==Synonyms==
<var>JANUS ADDSUFF</var> is a synonym for <var>JANUS ADDSUFFIX</var>.

==Usage==
A port can have multiple suffix mappings. The suffix must be unique for the port. If the suffix already exists for the specified port, an error is produced.

<var>APSYSUFFIX</var> must be specified on the <var>[[JANUS DEFINE]]</var> for the port before suffix mappings can be added.

This is new as of <var class="product">Model 204</var> version 8.0.

==Example==
JANUS ADDSUFFIX MYPORT A DBSALPHA
JANUS ADDSUFFIX MYPORT B DBSBETA

==See also==
<ul>
<li>[[APSYSUFFIX (JANUS DEFINE parameter)|APSYSUFFIX]]</li>
<li>[[JANUS DELETESUFFIX]]</li>
<li>[[JANUS DISPLAYSUFFIX]]</li>
</ul>

[[Category:Janus commands]]

APSYSUFFIX (JANUS DEFINE parameter)

Alex — Tue, 14 Apr 2026 03:20:24 GMT

Create APSYSUFFIX parameter page

New page

APSYSUFFIX: Enable per-suffix routing on IMAGINET ports

<var>APSYSUFFIX</var> is a parameter on <var>[[JANUS DEFINE]]</var> that enables per-suffix routing on IMAGINET ports, allowing multiple DBS (Database Server) instances to be served by a single port.

This is a flag parameter; it takes no value.

When <var>APSYSUFFIX</var> is set, each connecting Imagine broker identifies itself with a single-character suffix and a DBS name during the handshake. The suffix-to-DBS mappings are managed at runtime via the <var>[[JANUS ADDSUFFIX]]</var>, <var>[[JANUS DELETESUFFIX]]</var>, and <var>[[JANUS DISPLAYSUFFIX]]</var> commands.

==Syntax==
JANUS DEFINE portname ... APSYSUFFIX

==Applicability==
<var>APSYSUFFIX</var> is valid only for IMAGINET type ports.

==Usage==
Use <var>APSYSUFFIX</var> when a single IMAGINET port must serve multiple DBS instances. Each broker connecting to the port sends a single-character suffix (A-Z, 0-9) and a DBS name during the handshake. The suffix-to-DBS mappings are registered with <var>[[JANUS ADDSUFFIX]]</var>.

The suffix character for the current connection is available in <var class="product">Model 204</var> User Language via the <var>[[ApsySuffix (Imagine property)|ApsySuffix]]</var> method, and the DBS name via the <var>[[DbsName (Imagine property)|DbsName]]</var> method.

This is new as of <var class="product">Model 204</var> version 8.0.

==See also==
<ul>
<li>[[JANUS ADDSUFFIX]]</li>
<li>[[JANUS DELETESUFFIX]]</li>
<li>[[JANUS DISPLAYSUFFIX]]</li>
<li>[[ApsySuffix (Imagine property)|ApsySuffix]]</li>
<li>[[DbsName (Imagine property)|DbsName]]</li>
</ul>

[[Category:JANUS DEFINE parameters|APSYSUFFIX]]

SSLPROT (JANUS DEFINE parameter)

Tom — Mon, 13 Apr 2026 20:46:38 GMT

Description

← Older revision		Revision as of 20:46, 13 April 2026
Line 27:		Line 27:
	<tr><th>X'10'</th>		<tr><th>X'10'</th>
	<td>TLS 1.2 support. Available as of <var class="product">Model 204</var> 7.5.</td></tr>		<td>TLS 1.2 support. Available as of <var class="product">Model 204</var> 7.5.</td></tr>

			<tr><th>X'20'</th>
			<td>TLS 1.3 support. Available as of <var class="product">Model 204</var> 8.0.</td></tr>

	<tr><th>X'07'</th>		<tr><th>X'07'</th>

Global features

JDamon — Mon, 13 Apr 2026 20:08:20 GMT

Syntax

← Older revision		Revision as of 20:08, 13 April 2026
(One intermediate revision by the same user not shown)
Line 554:		Line 554:
	Where:		Where:
	<ul>		<ul>
	<li>The <var>Global</var> option ~~retains~~ the ~~<var>Remember</var>~~ position after the current request terminates. If <var>Global</var> is not specified, the position ~~is temporary, and it~~ is cleared from GTBL after the current request terminates. </li>		<li>The <var>Global</var> option implies Perm and the position is retained in GTBL after the current request terminates. If <var>Global</var> is not specified, TEMP is implied and the position is cleared from GTBL after the current request terminates.</li>
			<p><b>NOTE:</B> The use of GLOBAL here must be consistent with the CLEAR GLOBAL POSITION statement. If the latter is specified with PERM:</p>
			<p>CLEAR GLOBAL POSITION <b>PERM</b> 'objectname',</p>
			<p>then the REMEMBER statement must specify GLOBAL because it implies PERM.</p>

	<li><var class="term">position_name</var> is a unique object name you assign to the <var>Remember</var> position. </li>		<li><var class="term">position_name</var> is a unique object name you assign to the <var>Remember</var> position. </li>
Line 565:		Line 568:
	</ul></li>		</ul></li>
	</ul>		</ul>

	====Usage notes====		====Usage notes====
	<p>		<p>
Line 864:		Line 867:
	<li><var>Global</var> clears a specific global object from GTBL. You cannot clear a global string variable created with the <var>$Setg</var> function using this form. </li>		<li><var>Global</var> clears a specific global object from GTBL. You cannot clear a global string variable created with the <var>$Setg</var> function using this form. </li>

			<li><var>Position [Perm \| Temp]</var> The use of PERM or TEMP must be consistent with GLOBAL in the REMEMBER statement. If GLOBAL is specified in the REMEMBER statement, then PERM is implied. If GLOBAL is omitted from the REMEMBER statement, TEMP is implied.
			</li>

	<li><var class="term">objectname</var> is the literal name of the specific global object to be cleared from GTBL. Enclose <var class="term">objectname</var> in single quotation marks.</li>		<li><var class="term">objectname</var> is the literal name of the specific global object to be cleared from GTBL. Enclose <var class="term">objectname</var> in single quotation marks.</li>
			<p><b>NOTE:</b> If the <i>objectname</i> is mixed case, be sure to use the same name, in single quotation marks, when referring to that name in other statements; e.g. REMEMBER or POSITION.</p>

	<li><var class="term">%variable</var> contains a value that specifies the global object to be cleared from GTBL. </li>		<li><var class="term">%variable</var> contains a value that specifies the global object to be cleared from GTBL. </li>

MAXBG parameter

RPuszewski — Wed, 08 Apr 2026 20:14:11 GMT

← Older revision		Revision as of 20:14, 8 April 2026
Line 8:		Line 8:
	<dd>System		<dd>System
	<dt>Where set		<dt>Where set
	<dd>User 0 CCAIN parameters		<dd>User 0 CCAIN parameters or reset by system manager
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All
Line 43:		Line 43:
	Setting <var>MAXBG</var> to 0 indicates that the default value of <var>MAXBG</var>, calculated from the number		Setting <var>MAXBG</var> to 0 indicates that the default value of <var>MAXBG</var>, calculated from the number
	of daemon threads, is to be used.		of daemon threads, is to be used.
	~~This means that~~ the ~~lowest explicit~~ value ~~of <var>MAXBG</var> that will~~ be ~~honored is 1~~.		Effective with Model204 version 8, the value may be reset to zero by a system manager if no daemon threads are to be allowed.

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

← Older revision		Revision as of 03:22, 14 April 2026
Line 159:		Line 159:

	<tr><td>[[ANONUSER (JANUS DEFINE parameter)\|ANONUSER]]</td><td>Lets you change the name of the anonymous user, <var>ANONUSER</var> may be specified only if <var>ANONYMOUS</var> is also specified.</td></tr>		<tr><td>[[ANONUSER (JANUS DEFINE parameter)\|ANONUSER]]</td><td>Lets you change the name of the anonymous user, <var>ANONUSER</var> may be specified only if <var>ANONYMOUS</var> is also specified.</td></tr>

			<tr><td>[[APSYSUFFIX (JANUS DEFINE parameter)\|APSYSUFFIX]]</td><td>Enables per-suffix routing on IMAGINET ports, allowing multiple DBS instances to be served through a single port.</td></tr>

	<tr><td>[[AUDTERM (JANUS DEFINE parameter)\|AUDTERM]]</td><td>Controls whether the server thread sends "non-compiler terminal output" to the audit trail.</td></tr>		<tr><td>[[AUDTERM (JANUS DEFINE parameter)\|AUDTERM]]</td><td>Controls whether the server thread sends "non-compiler terminal output" to the audit trail.</td></tr>