m204wiki - User contributions [en]

VIEW FILEORG command

2026-08-20T17:51:50Z

Snehal: /* VIEW/DISPLAY Command Now Identifies In-Memory and Imagine Files */

== VIEW/DISPLAY Command Now Identifies In-Memory and Imagine Files ==

This change was made in '''Model 204 Version 8.0'''.

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

== Benefit ==

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

== Compatibility Notes ==

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:51:10Z

Snehal:

== VIEW/DISPLAY Command Now Identifies In-Memory and Imagine Files ==

This change was made in Model 204 '''Version 8.0.'''

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

== Benefit ==

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

== Compatibility Notes ==

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:47:46Z

Snehal:

Introduced in: Model 204 Version 8.0

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

== Benefit ==

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

== Compatibility Notes ==

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:28:49Z

Snehal:

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

== Benefit ==

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

== Compatibility Notes ==

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:28:04Z

Snehal:

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

===== Before this change: =====

FILEORG X'0008' (Hashed) File organization

===== After this change: =====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== Benefit ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

=== Compatibility Notes ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:17:19Z

Snehal:

== What's New ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== Benefit ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

=== Compatibility Notes ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T17:15:21Z

Snehal:

VIEW FILEORG command

2026-08-20T17:14:08Z

Snehal: /* What's New */

== What's New ==

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

==== Before this change: ====

FILEORG X'0008' (Hashed) File organization

==== After this change: ====

- In-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
- Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

=== '''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T16:09:57Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''

FILEORG X'0008' (Hashed) File organization

'''After this change,'''

in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
Imagine file:

FILEORG X'0008' (Hashed,Imagine) File organization
'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

=== '''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.

• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T16:01:09Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''

= FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:

=FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T16:00:32Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T16:00:21Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
= FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T16:00:03Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
=== FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T15:59:40Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

For Example:

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.
===
'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T15:59:06Z

Snehal:

=== '''What's New''' ===

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

Example

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

=== '''Benefit''' ===

In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.
===
'''Compatibility Notes''' ===

• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T15:58:20Z

Snehal:

'''What's New'''

The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

Example

'''Before this change:'''
FILEORG X'0008' (Hashed) File organization

'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

'''Benefit'''
In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes'''
• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

VIEW FILEORG command

2026-08-20T15:57:41Z

Snehal: Created page with "'''What's New''' The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident. Example '''Before this change:''' FILEORG X'0008' (Hashed) File organization '''After this change,'..."

'''What's New'''
The VIEW and DISPLAY commands now indicate when a file's organization (FILEORG) corresponds to an In-Memory file or an Imagine file. This information is shown directly alongside the existing file organization description, so you no longer need to check the original DEFINE command or other sources to determine whether a file is memory-resident.

Example
'''Before this change:'''
FILEORG X'0008' (Hashed) File organization
'''After this change,'''
for an in-memory file:
FILEORG X'0008' (Hashed,In-Memory) File organization
or, for an Imagine file:
FILEORG X'0008' (Hashed,Imagine) File organization

'''Note:''' Files that are not in-memory or Imagine files continue to display exactly as before — no change in output for standard disk-resident files.

'''Benefit'''
In-memory and Imagine files behave differently from traditional disk-resident files, particularly with respect to I/O and recovery. This enhancement lets administrators and support staff quickly confirm a file's storage type using the standard VIEW FILEORG command, without needing to reference the file's original definition.

'''Compatibility Notes'''
• No new command syntax is introduced; existing VIEW/DISPLAY FILEORG commands and procedures continue to work unchanged.
• Scripts or automation that parse the FILEORG description text should be reviewed if they assume a fixed format, since the description may now include an additional ,In-Memory or ,Imagine qualifier for applicable files.

Release notes for Model 204 version 8.0

2026-08-20T15:54:51Z

Snehal: /* New and changed commands */

==Overview==
These release notes contain installation and features information for the Rocket Model 204 version 8.0 release. Before beginning your installation, please read through this information about product installation and changes.

==New in this release==

==Operating system and hardware requirements==

===Operating system requirements===

===Hardware requirements===

===Connect★ compatibility with Model 204===

==SOUL (User Language) enhancements==

==External Call Facility enhancements==

==System enhancements==

==Editor enhancements==

==AUDIT204 enhancements==

==Recovery enhancements==

==Security enhancements==

==Janus product enhancements==

===TLS 1.3 support===
Janus SSL ports now support TLS 1.3 (RFC 8446) for both client and server connections. TLS 1.3 provides improved security and performance over TLS 1.2, including a simplified handshake with fewer round trips, and the removal of legacy features such as renegotiation.

The following TLS 1.3 cipher suites are supported:
<ul>
<li><code>TLS_AES_128_GCM_SHA256</code></li>
<li><code>TLS_AES_256_GCM_SHA384</code></li>
</ul>

Key exchange is performed using X25519 (Curve25519 Elliptic Curve Diffie-Hellman, per RFC 7748). Certificate authentication uses RSA-PSS signatures.

Key derivation uses the HKDF-based key schedule defined in RFC 8446, replacing the PRF-based approach of earlier TLS versions.

TLS 1.3 is enabled by default on ports that allow TLS 1.2. To restrict a port to earlier protocol versions, use the existing <var>SSLVERSION</var> parameter on the <var>[[JANUS DEFINE]]</var> command.
==== Client-side TLS 1.3 and post-handshake authentication ====

Janus client connections (for example, clients built with the <var class="term">$SOCK</var>
functions or the equivalent <var class="term">Socket</var> class methods, and Janus
Web Server outbound HTTPS requests) now negotiate and complete a full TLS 1.3
handshake as the client, including X25519 key exchange, the HKDF-based key
schedule, and RSA-PSS certificate verification of the server.

Client certificate authentication is supported both during the initial handshake
and after it completes. When a TLS 1.3 server sends a post-handshake
<code>CertificateRequest</code> (RFC 8446 Section 4.6.2) — for example, when a
server application requests a client certificate on a connection that did not
originally require one — the Janus client automatically responds with its
<code>Certificate</code>, <code>CertificateVerify</code>, and <code>Finished</code>
messages, allowing the authenticated request to proceed without interrupting the
connection.

No application changes are required. Post-handshake authentication is used
automatically when a server requests it and a client certificate is available for
the port.

===Imagine Transparency support===
A new facility called [[Imagine Transparency]] is now available to allow files in an <var class="product">Imagine</var> database to be accessed from <var class="product">Model 204</var> as if they were native files.

A new port type, [[JANUS_DEFINE#IMAGINET|IMAGINET]], is now available. It allows <var class="product">Model 204</var> files to be stored on an Imagine server rather than in operating system files. A new parameter is now available on the [[DEFINE DATASET command#IMAGINE|ALLOCATE]] command to indicate that a file is to be accessed via the <var>IMAGINET</var> port rather than from operating system files.

==Debugger enhancements==

==Performance enhancements==

===Hardware-accelerated deflate/inflate compression===
The SOUL compression functions (<var>Deflate</var>, <var>Inflate</var>, <var>Gzip</var>, <var>Gunzip</var>, <var>Zip</var>, and <var>Unzip</var>) now exploit the IBM z15 (and above) DFLTCC (Deflate Conversion Call) hardware instruction when available. This provides significant performance improvement for compression and decompression of longstrings without any application code changes.

Hardware acceleration is used automatically when the processor supports it. On processors without DFLTCC support, the existing software implementation continues to be used transparently.

The DFLTCC instruction handles both the deflate (compress) and inflate (expand) operations natively in hardware, including CRC-32 computation, providing throughput improvements that scale with data size.

==New and changed commands==
<var>[[DISPLAY DSNAMES command]]</var>

<var>[[VIEW FILEORG command]]</var>

==New and changed parameters==

==New and changed statistics==

==Compatibility issues==

==Notes for system manager and installer==

==New products==

==New and changed messages==

[[Category: Release notes]]

Release notes for Model 204 version 8.0

2026-08-20T15:54:26Z

Snehal: /* New and changed commands */

==Overview==
These release notes contain installation and features information for the Rocket Model 204 version 8.0 release. Before beginning your installation, please read through this information about product installation and changes.

==New in this release==

==Operating system and hardware requirements==

===Operating system requirements===

===Hardware requirements===

===Connect★ compatibility with Model 204===

==SOUL (User Language) enhancements==

==External Call Facility enhancements==

==System enhancements==

==Editor enhancements==

==AUDIT204 enhancements==

==Recovery enhancements==

==Security enhancements==

==Janus product enhancements==

===TLS 1.3 support===
Janus SSL ports now support TLS 1.3 (RFC 8446) for both client and server connections. TLS 1.3 provides improved security and performance over TLS 1.2, including a simplified handshake with fewer round trips, and the removal of legacy features such as renegotiation.

The following TLS 1.3 cipher suites are supported:
<ul>
<li><code>TLS_AES_128_GCM_SHA256</code></li>
<li><code>TLS_AES_256_GCM_SHA384</code></li>
</ul>

Key exchange is performed using X25519 (Curve25519 Elliptic Curve Diffie-Hellman, per RFC 7748). Certificate authentication uses RSA-PSS signatures.

Key derivation uses the HKDF-based key schedule defined in RFC 8446, replacing the PRF-based approach of earlier TLS versions.

TLS 1.3 is enabled by default on ports that allow TLS 1.2. To restrict a port to earlier protocol versions, use the existing <var>SSLVERSION</var> parameter on the <var>[[JANUS DEFINE]]</var> command.
==== Client-side TLS 1.3 and post-handshake authentication ====

Janus client connections (for example, clients built with the <var class="term">$SOCK</var>
functions or the equivalent <var class="term">Socket</var> class methods, and Janus
Web Server outbound HTTPS requests) now negotiate and complete a full TLS 1.3
handshake as the client, including X25519 key exchange, the HKDF-based key
schedule, and RSA-PSS certificate verification of the server.

Client certificate authentication is supported both during the initial handshake
and after it completes. When a TLS 1.3 server sends a post-handshake
<code>CertificateRequest</code> (RFC 8446 Section 4.6.2) — for example, when a
server application requests a client certificate on a connection that did not
originally require one — the Janus client automatically responds with its
<code>Certificate</code>, <code>CertificateVerify</code>, and <code>Finished</code>
messages, allowing the authenticated request to proceed without interrupting the
connection.

No application changes are required. Post-handshake authentication is used
automatically when a server requests it and a client certificate is available for
the port.

===Imagine Transparency support===
A new facility called [[Imagine Transparency]] is now available to allow files in an <var class="product">Imagine</var> database to be accessed from <var class="product">Model 204</var> as if they were native files.

A new port type, [[JANUS_DEFINE#IMAGINET|IMAGINET]], is now available. It allows <var class="product">Model 204</var> files to be stored on an Imagine server rather than in operating system files. A new parameter is now available on the [[DEFINE DATASET command#IMAGINE|ALLOCATE]] command to indicate that a file is to be accessed via the <var>IMAGINET</var> port rather than from operating system files.

==Debugger enhancements==

==Performance enhancements==

===Hardware-accelerated deflate/inflate compression===
The SOUL compression functions (<var>Deflate</var>, <var>Inflate</var>, <var>Gzip</var>, <var>Gunzip</var>, <var>Zip</var>, and <var>Unzip</var>) now exploit the IBM z15 (and above) DFLTCC (Deflate Conversion Call) hardware instruction when available. This provides significant performance improvement for compression and decompression of longstrings without any application code changes.

Hardware acceleration is used automatically when the processor supports it. On processors without DFLTCC support, the existing software implementation continues to be used transparently.

The DFLTCC instruction handles both the deflate (compress) and inflate (expand) operations natively in hardware, including CRC-32 computation, providing throughput improvements that scale with data size.

==New and changed commands==
<var>[[DISPLAY DSNAMES command]]</var>
<var>[[VIEW FILEORG]]</var>

==New and changed parameters==

==New and changed statistics==

==Compatibility issues==

==Notes for system manager and installer==

==New products==

==New and changed messages==

[[Category: Release notes]]