APSYSUFFIX (JANUS DEFINE parameter) - Revision history

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

2026-04-15T22:17:20Z

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

← Older revision		Revision as of 22:17, 15 April 2026
Line 1:		Line 1:
	APSYSUFFIX x — Specify Application System suffix for IMAGINET port routing		APSYSUFFIX ''x'' — Specify Application System suffix for IMAGINET port routing

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

			==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:

			* 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>.
			* 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>.

			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.

	==Usage==		==Usage==
	* When APSYSUFFIX is specified, the ~~broker sends~~ the suffix character ~~and the associated~~ DBS name to Model 204 ~~during~~ the ~~IMAGINET connection handshake. Model 204 uses this information to route requests~~ to the ~~correct DBS instance~~.		* 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.
	* Without APSYSUFFIX, all IMAGINET connections are routed to a single, default DBS instance.		* 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.		* 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.		* 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.		Valid only for [[JANUS DEFINE#type\|IMAGINET]] port types. This parameter is new as of Model 204 version 8.0.

	==Example==		==Example==
	In the Imagine ~~broker configuration~~, ~~a broker~~ started with suffix ~~"T"~~ and DBS name ~~"db" would communicate this to Model 204 via the IMAGINET port~~:		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:

	<pre>		<pre>
	startBroker --apsySuffix=T --dbsName=db --dbsPort=7777		startBroker --apsySuffix=T --dbsName=db --dbsPort=7777
			startBroker --apsySuffix=L --dbsName=larry --dbsPort=7778
			startBroker --apsySuffix=U --dbsName=lulu --dbsPort=7779
	</pre>		</pre>

	~~On the~~ Model 204 ~~side, the IMAGINET port~~ is ~~defined normally. The suffix routing is driven by~~ the broker, ~~not by the JANUS DEFINE itself. The APSYSUFFIX keyword on JANUS DEFINE enables the IMAGINET port~~ to ~~accept and process~~ suffix ~~information from connecting brokers~~.		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==
	* [[Imagine Transparency]]		* [[Imagine Transparency]]
			* [[JANUS ADDSUFFIX]]
			* [[JANUS DELETESUFFIX]]
			* [[JANUS DISPLAYSUFFIX]]
	* [[List of Janus commands]]		* [[List of Janus commands]]
	* [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]		* [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]

Alex: Add documentation for APSYSUFFIX parameter

2026-04-15T22:11:36Z

Add documentation for APSYSUFFIX parameter

← Older revision	Revision as of 22:11, 15 April 2026
Line 1:	Line 1:
		APSYSUFFIX x — Specify Application System suffix for IMAGINET port routing

		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.

		==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.

		==Usage==
		* When APSYSUFFIX is specified, the broker sends the suffix character and the associated DBS name to Model 204 during the IMAGINET connection handshake. Model 204 uses this information to route requests to the correct DBS instance.
		* Without APSYSUFFIX, all IMAGINET connections are routed to a single, default DBS instance.
		* 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.

		==Example==
		In the Imagine broker configuration, a broker started with suffix "T" and DBS name "db" would communicate this to Model 204 via the IMAGINET port:

		<pre>
		startBroker --apsySuffix=T --dbsName=db --dbsPort=7777
		</pre>

		On the Model 204 side, the IMAGINET port is defined normally. The suffix routing is driven by the broker, not by the JANUS DEFINE itself. The APSYSUFFIX keyword on JANUS DEFINE enables the IMAGINET port to accept and process suffix information from connecting brokers.

		==See also==
		* [[Imagine Transparency]]
		* [[List of Janus commands]]
		* [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]

Alex: Add transparency filename suffix convention

2026-04-14T03:35:21Z

Add transparency filename suffix convention

← Older revision		Revision as of 03:35, 14 April 2026
Line 1:		Line 1:
	~~<span class="pageSubtitle">APSYSUFFIX: Enable per-suffix routing on IMAGINET ports</span>~~

	~~<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==~~
	~~<p class="syntax"><span class="literal">JANUS DEFINE</span> <span class="term">portname</span> ... <span class="literal">APSYSUFFIX</span></p>~~

	~~==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]]~~

Alex: Create APSYSUFFIX parameter page

2026-04-14T03:20:24Z

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]]