m204wiki - Recent changes [en]

User:Prajput2

Glw — Thu, 27 Aug 2026 10:37:44 GMT

User account Prajput2 was created by Glw

User:Mslater2

Glw — Thu, 27 Aug 2026 10:36:44 GMT

User account Mslater2 was created by Glw

User:Kng2

Glw — Thu, 27 Aug 2026 10:35:40 GMT

User account Kng2 was created by Glw

User:Agorasia

Glw — Thu, 27 Aug 2026 10:33:51 GMT

User account Agorasia was created by Glw

Release notes for Model 204 version 8.0

Alex — Thu, 27 Aug 2026 04:12:35 GMT

Add missing 8.0 content from full git-log scan: SOUL enhancements (Imagine/BrokerCallError classes, Record RecordId retrieval, $LISTFINDI_MULT), TCP keep-alive, Security (SUBSYSMGMT/DICTADMIN), new commands (PUSHPARM/POPPARM, MINUTABLE/MINUGLOBAL), changed commands (VIEW/UTABLE/MONITOR/SWITCH/DEFINE DATASET, fractional-second stats), New and changed parameters (RESRQST/ECMAXCPU/EVALOPT/COMPOPT/MAXBG/TEMPPAGE), Discontinued features (SHAPE)

Show changes

Category:Janus SSH

Alex — Thu, 27 Aug 2026 03:01:59 GMT

Create Janus SSH category page (model on Category:Janus Sockets/Web Server)

New page

<var class="product">[[Janus SSH]]</var> is part of the [[Janus TCP/IP Base#The Janus family|Janus]] family of products that provides connectivity to the <var class="product">Model 204</var> database. It provides a built-in SSH (Secure Shell) server for encrypted terminal access to a <var class="product">Model 204</var> Online.

==PDF of category pages==
You can <b><span class="plainlinks">[{{fullurl:{{FULLPAGENAMEE}}|action=pdfbook}} use this link]</span></b> to create a PDF file that contains all the pages in this category. If this category contains a "Subcategories" section, the PDF will also contain a linked list of the pages that belong to each subcategory listed in the "Subcategories" section.

<p class="note"><b>Note:</b> The resulting PDF is not optimized for online use. All blue links except for those in the table of contents (TOC) take you outside of the PDF (typically to http://m204wiki.rocketsoftware.com), so you must rely on the PDF bookmarks and TOC for online navigation. Hovering your mouse over a link will reveal its destination. </p>

Imagine Transparency

Alex — Thu, 27 Aug 2026 01:42:19 GMT

Expand: SOUL access model, RELEASE IMAGINE RECORDS, IMAGINE EXTRACT/SYNC/ENDSYNC + DISPLAY IMAGINESYNC, restrictions, See also, category

← Older revision		Revision as of 01:42, 27 August 2026
Line 9:		Line 9:
	</p>		</p>
	Once this is done, any reference to <var>SOMEFILE</var> in a<var class="product">Model 204</var> application (including in file groups) would access the data from <var class="product">Imagine</var> via the <var>IMAGINET</var> port. Note that a single <var class="product">Model 204</var> file can corresponding to many <var class="product">Imagine</var> files if record types are used.		Once this is done, any reference to <var>SOMEFILE</var> in a<var class="product">Model 204</var> application (including in file groups) would access the data from <var class="product">Imagine</var> via the <var>IMAGINET</var> port. Note that a single <var class="product">Model 204</var> file can corresponding to many <var class="product">Imagine</var> files if record types are used.

			==Accessing Imagine files from SOUL==
			No application changes are required to read or update a Transparency file. Ordinary SOUL statements such as <var>FIND</var>, <var>FOR EACH RECORD</var>, <var>FIND AND PRINT COUNT</var>, <var>STORE RECORD</var>, <var>CHANGE</var>, <var>ADD</var>, and <var>DELETE</var> operate on a Transparency file exactly as they do on a native <var class="product">Model 204</var> file. <var class="product">Model 204</var> transparently sends the corresponding requests to the <var class="product">Imagine</var> broker over the <var>IMAGINET</var> port and returns the results to the application.

			To reduce broker round trips, <var class="product">Model 204</var> caches the results of Transparency finds and prefetches records from find result sets. Cached finds are automatically deoptimized and revalidated when records they reference are changed, so applications always see a consistent view of the data.

			===Releasing held records===
			Records retrieved from <var class="product">Imagine</var> are held on a Transparency thread for the duration of the request. The <var>RELEASE IMAGINE RECORDS</var> statement releases those held records and frees the Transparency thread. Specify the <var>CLEARLISTS</var> option to also clear any <var class="term">$lists</var> and <var class="term">StringLists</var> that reference the released records:
			<p class="pre">RELEASE IMAGINE RECORDS CLEARLISTS
			</p>

			==Populating and synchronizing Imagine files==
			Before a <var class="product">Model 204</var> file can be switched to Transparency mode, its data must be loaded into <var class="product">Imagine</var>. The <var>[[IMAGINE command]]</var> extracts the data from an existing <var class="product">Model 204</var> file and loads it into <var class="product">Imagine</var>:
			<ul>
			<li><var>IMAGINE EXTRACT</var> copies the file's records to <var class="product">Imagine</var> as a one-time operation.</li>
			<li><var>IMAGINE SYNC</var> copies the records and then keeps <var class="product">Model 204</var> and <var class="product">Imagine</var> in sync, so that subsequent updates are also applied to <var class="product">Imagine</var>. This makes it feasible to switch a file to Transparency mode with a minimal outage.</li>
			<li><var>IMAGINE ENDSYNC</var> ends a SYNC or EXTRACT for the file.</li>
			</ul>
			The <var>[[DISPLAY IMAGINESYNC command]]</var> lists all files that are currently in <var>IMAGINE SYNC</var> mode.

			==Restrictions==
			The following operations are not supported against an <var class="product">Imagine</var> Transparency file:
			<ul>
			<li><var>DEFINE FIELD</var> — field definitions are determined by the underlying <var class="product">Imagine</var> file and cannot be changed from <var class="product">Model 204</var>.</li>
			<li><var>FOR EACH RECORD IN ORDER</var> — ordered retrieval is not supported for Transparency files.</li>
			</ul>

			==See also==
			<ul>
			<li><var>[[IMAGINE command]]</var></li>
			<li><var>[[DISPLAY IMAGINESYNC command]]</var></li>
			<li><var>[[JANUS DEFINE]]</var> (the <var>IMAGINET</var> port type)</li>
			<li><var>[[DEFINE DATASET command]]</var> (allocating a file <var>WITH IMAGINE</var>)</li>
			<li>[[Release notes for Model 204 version 8.0#Imagine Transparency support\|Model 204 version 8.0 release notes]]</li>
			</ul>

			[[Category:File management]]

Janus SSH

Alex — Thu, 27 Aug 2026 01:40:53 GMT

Create Janus SSH page: SSH server port type, RSA public-key trusted login, JANUS TRUST/DELTRUST/DISPLAYTRUST/DISTOFU/SSHKEY commands, TOFU (new in 8.0)

New page

<var class="product">Janus SSH</var> is part of the Janus family of products that provides connectivity to the <var class="product">Model 204</var> database. A Janus SSH port is a built-in SSH (Secure Shell) server that lets users connect to a <var class="product">Model 204</var> <var class="product">Online</var> from a standard SSH client over an encrypted connection, obtaining an interactive <var class="product">Model 204</var> command session.

Janus SSH was introduced in <var class="product">Model 204</var> version 8.0. Like the other Janus products, it requires the <var class="product">[[Janus TCP/IP Base]]</var>.

The SSH server implements the standard SSH transport, authentication, and connection protocols (RFC 4250, RFC 4253, and RFC 4254). The following algorithms are supported:
<table>
<tr class="head"><th>Function</th>
<th>Algorithm</th></tr>
<tr><td>Key exchange</td><td><code>diffie-hellman-group14-sha256</code></td></tr>
<tr><td>Host and user keys</td><td><code>rsa-sha2-256</code> and <code>ssh-rsa</code> (RSA)</td></tr>
<tr><td>Encryption</td><td><code>aes256-ctr</code></td></tr>
<tr><td>Message authentication</td><td><code>hmac-sha2-256</code></td></tr>
</table>

==Defining a Janus SSH port==
An SSH port is defined with the <var>[[JANUS DEFINE]]</var> command, using the <var>SSH</var> port type. The server's host key is supplied by an <var>SSL PROFILE</var>, in the same way as for Janus SSL ports. For example:

JANUS DEFINE SSHPORT 5996 SSH 10 IBSIZE 4096 OBSIZE 8192 -
SSL PROFILE SSH.PKEY SSLCACHE 80 SSLIBSIZE 16512 SSLOBSIZE 4096

In this example, <code>SSHPORT</code> is the port name, <code>5996</code> is the TCP port number, <code>SSH</code> is the port type, and <code>10</code> is the maximum number of concurrent connections. The <var>SSL PROFILE</var> names the certificate profile that provides the server's RSA host key.

Once the port is started with the <var>[[JANUS START]]</var> command, users can connect with any standard SSH client:

ssh -p 5996 myuserid@myhost.example.com

==Authentication==
Janus SSH supports two forms of user authentication:
<ul>
<li><b>Password authentication</b> — the user supplies a <var class="product">Model 204</var> userid and password, which are validated the same way as for any other <var class="product">Model 204</var> login.</li>
<li><b>Public-key (trusted) authentication</b> — the user is authenticated by an RSA SSH public key that has been registered as trusted for that userid on the port, so no password is required.</li>
</ul>

==Trusted public-key login==
With trusted public-key login, an RSA public key is associated with a <var class="product">Model 204</var> userid on a specific SSH port. When a user connects and offers a private key whose public key is registered for the userid, the user is logged in without a password.

The following commands manage trusted keys. Each command applies to SSH ports only.

<table>
<tr class="head"><th>Command</th>
<th>Description</th></tr>
<tr>
<td nowrap><var>JANUS TRUST</var> ''portname userid base64key''</td>
<td>Registers a trusted SSH public key for ''userid'' on the named SSH port. ''base64key'' is the base64-encoded public key blob (the middle field of an OpenSSH <code>id_rsa.pub</code> line). The key data may be continued across command lines.</td></tr>
<tr>
<td nowrap><var>JANUS DELTRUST</var> ''portname userid''</td>
<td>Removes the trusted key for ''userid'' on the named port.</td></tr>
<tr>
<td nowrap><var>JANUS DISPLAYTRUST</var> [''portname'']</td>
<td>Displays the trusted keys registered on the named port, or on all ports if ''portname'' is omitted or is <code>*</code>. <var>DISTRUST</var> is an accepted abbreviation.</td></tr>
<tr>
<td nowrap><var>JANUS DISTOFU</var> [''portname'']</td>
<td>Displays keys that were automatically registered by trust-on-first-use (TOFU). <var>DISPLAYTOFU</var> is a synonym.</td></tr>
<tr>
<td nowrap><var>JANUS SSHKEY</var></td>
<td>Displays the SSH public key that the current user authenticated with. This is a convenient way for a user to obtain the exact key blob to hand to an administrator for a <var>JANUS TRUST</var> command.</td></tr>
</table>

For example, to trust a user's key on the port defined above:

JANUS TRUST SSHPORT MYUSER AAAAB3NzaC1yc2EAAAADAQAB...

==Trust-on-first-use (TOFU)==
Trust-on-first-use lets an SSH port automatically register a user's public key the first time that user connects and authenticates, so that subsequent connections use public-key login without further administration.

TOFU is enabled by specifying the <var>TOFU</var> option on the <var>[[JANUS DEFINE]]</var> command for an SSH port, with a maximum number of keys to retain (1 to 9999):

JANUS DEFINE SSHPORT 5996 SSH 10 SSL PROFILE SSH.PKEY TOFU 100

Keys registered by TOFU are shown by the <var>JANUS DISTOFU</var> command. When the maximum count is reached, the least recently used TOFU key is evicted to make room for a new one. Keys added explicitly with <var>JANUS TRUST</var> are never evicted by TOFU.

==See also==
<ul>
<li><var>[[JANUS DEFINE]]</var></li>
<li><var>[[JANUS START]]</var></li>
<li><var class="product">[[Janus TCP/IP Base]]</var></li>
<li>[[Release notes for Model 204 version 8.0#Janus SSH server|Model 204 version 8.0 release notes]]</li>
</ul>

[[Category:Janus SSH]]
[[Category:Janus commands]]

Release notes for Model 204 version 8.0

Alex — Thu, 27 Aug 2026 01:39:20 GMT

Rewrite 8.0 release notes: add highlights table, promote Imagine Transparency, document TLS 1.3/Janus SSH, list new commands, remove empty section headers

Show changes

DISPLAY DSNAMES command

JDamon — Tue, 25 Aug 2026 23:13:45 GMT

← Older revision		Revision as of 23:13, 25 August 2026
Line 67:		Line 67:
	CCAGRP ROCKET1.CCAGRP.M204 M2P102 PS U 6184 6184 CYL 1		CCAGRP ROCKET1.CCAGRP.M204 M2P102 PS U 6184 6184 CYL 1
	CCASTAT ROCKET1.CCASTAT.M204 M2P103 PS U 13030 13030		CCASTAT ROCKET1.CCASTAT.M204 M2P103 PS U 13030 13030
			CCAIMEM1 M204 In-memory file 6184 6184 PGS 2500
			CCAIMEM2 M204 In-memory file 6184 6184 PGS 537
			CCAIMAG1 M204 Imagine file
	CCAIN ROCKET1.ROCKM80T.J0353345.D0000102.? ? FB 80 80		CCAIN ROCKET1.ROCKM80T.J0353345.D0000102.? ? FB 80 80

	[[Category:System manager commands]]		[[Category:System manager commands]]

User:Moe howard

Glw — Tue, 25 Aug 2026 23:06:14 GMT

Glw unblocked Moe howard

User:Moe howard

Glw — Tue, 25 Aug 2026 19:02:29 GMT

Glw blocked Moe howard with an expiration time of indefinite (account creation disabled, email disabled, cannot edit own talk page)

User:Moe howard

Glw — Tue, 25 Aug 2026 18:14:54 GMT

User account Moe howard was created by Glw test