APSYSUFFIX (JANUS DEFINE parameter)
APSYSUFFIX x — Specify Application System suffix for IMAGINET port routing
APSYSUFFIX is a 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
APSYSUFFIX x
Where:
- x 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 ALLOCATE filename WITH IMAGINE, the third character of the filename identifies the APSY suffix of the broker that serves that file. For example:
- A file named ROXDATA has suffix X (third character), so it can only be accessed through a broker running with
APSYSUFFIX X. - A file named ROTDATA has suffix T, and is served by a broker with
APSYSUFFIX T. - A file named ROLDATA has suffix L, and is served by a broker with
APSYSUFFIX L.
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
- 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
dbsNameanddbsPortbroker 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 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:
JANUS DEFINE IMGPORT 12231 IMAGINET 50 APSYSUFFIX JANUS ADDSUFFIX IMGPORT T db JANUS ADDSUFFIX IMGPORT L larry JANUS ADDSUFFIX IMGPORT U lulu
On the Imagine side, brokers are started with corresponding suffix and DBS name options:
startBroker --apsySuffix=T --dbsName=db --dbsPort=7777 startBroker --apsySuffix=L --dbsName=larry --dbsPort=7778 startBroker --apsySuffix=U --dbsName=lulu --dbsPort=7779
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").